Unfortunately I cannot see the path: as I was telling you, there is something wrong with this, but it’s how it is on my PC and there were lots of problems when we first installed Transit. I have Vista.
To find “Projects” folder go to My Computer->Program files->Transit XV->Projects->[the right project.]: the project folder only shows the Tutorial folder. It’s been like that from the start.I am forwarding you two screenshots in this mail: first one is to prove just what I told you above, so that you realise I know what I am talking about. Secondly, I have followed Karel’s exact instructions from the start. The problem it seems is that when I received the dictionary, it overwrites the language pair, my only way to get the file is to go to Open>Language Pair (which shows only the dictionary instead of the language pair)> Browse and select the ENU file: this is where something is wrong, but your instructions about receiving the dictionnary are the ones I followed, I don’t understand why it overwrites the language pair. So I translated inside the ENU file, and no FRA file was created.
I am sending you a second screenshot, so that you can see that the folders do appear when I open IN TRANSIT, and that there is no FRA file but the file I used to translate is the ENU file.
I do not know what to do. sHould I create a copy of the ENU file and rename it as FRA?
———————-
Thanks for the email. Let me reply just briefly for now, I will send you a more detailed message later.
I will try and add new suggestions into the add dict. soon.
Thanks for the positive feedback from the lead translator. I’m just curious why the comments are in a file with the name in it…? Isn’t this another translator? Or is this actually the name of the lead translator?
———————-
Well, the fact that you had been translating the ENU file could easily explain why TM did not work for fuzzies.
Now I am pretty sure that you should have tried to resolve it with me before beginning to translate in ENU file.
I think I know what happened. You Received the Glossary after you Received the Project, right? And you saved them under same project name. Therefore glossary overwritten the project. Is it possible?
———————-
is the name of the lead translator.
———————-
To translate other file, you need to Receive the project, and save it under different project name. For example 10001_15g.Then try to open language pair.
Please try it.
———————-
Remy
For the sake of consistency the ORDER of actions of installation is quite important there. Transit sees dictionaries as projects. Therefore they are installed separately, and once installed, Transit allows to have them activated while translating a “file”, or in Transit’s terms “a language pair”.
These are the instruction for that:- Go to the Glossary folder in the file server http://translationstop.com/files/, download the relevant and your language French_Main_dictionary.pxf or German_Main_dictionary.pxf.- Receive the glossary like a project in Transit by going to: Project ->Receive -> choose location of the .pxf file and follow program’s instructions.- Download and Receive the ADD_New.pxf glossary as well.- The Main dictionary is the one from which you import terminology into your project.- The Add dictionary is the one to which you add terms that in your opinion repeat often or need to be added to glossary for other reasons.
D. Receiving the Project files
1) Download the file you were assigned for the server how was explained before.2) In Transit go to Project ->Receive -> choose location of the .pxf dile and follow program’s instructions.3) To open the translation file (in Transit called “language pair”), click on “Open language pair” button under the main menu or go to File-> Open->Language pair.The program will open a window which will show you the files you can translate with this project.- If the downloaded .pxf file included only one assigned file – you will see only one file you can choose.- If your downloaded file combined several files you were assigned, you can choose which to translate first.4) Choose the file you want to translate and click “Open”.
Transit will open the language pair file in 2 windows – one for source and one for target languages. In Transit, the untranslated segments in Target window will appear in English!
3. Working on the file:3.1. Add the Main Glossary to the Project (you should have it downloaded)Go to Project -> Settings -> Term_Star Dictionaries Tab ->Add -> Choose French_Main_dictionary/German_Main_dictionary. At this point, it should be the ONLY glossary selected.
Now all terms form the glossary are colored red in the Target and Source windows.
3.2 Insert all terms from the Main GlossaryThe Main Glossary consists numerous common terms and Proper Names, which we want to keep consistent in all files of the project. Therefore, insert all terms from it BEFORE you begin to translate.
Open your language pair file, and put the cursor in the beginning of the first Target segment. Go to Edit > “Insert all terms from dictionary”.Ctrl+S save your file.
* Don’t forget to conjugate the inserted glossary terms (marked red) according to your language’s grammar.
* If you don’t like a term form the Glossary, you should use it anyway, as we need all files to be consistent. But in the same time make a note about it, and send it to (PM) when you deliver the translation. Comments to glossary are later forwarded to proofreaders.
3.3 Add the ADD_New dictionary (you should have it downloaded)The Add dictionary is for adding new terms. When you finish translating and Send your work, this glossary is sent as well. The terms you added are checked and transferred to the Main glossary.
Go again to Project -> Settings -> Term_Star Dictionaries Tab ->Add -> Choose the Add_New dictionary, make it the current dictionary (to make it easier to add to).
Now you can commence with your translation.
Are these steps clear for you? You MUST insert terms form the Main glossary BEFORE you start to translate.
———————-
Please let me know if you succeeded to open language pair – by saving translation project under a different name.Please let me know, I want to see if it got resolved.
” I’ll try this now. Sorry didn’t reply sooner. ”
I added my translated file to a new project, then sent the translation which said it successfully did it with about 20400KB, but when I try to open it, it’s not there.
Kind
———————-
actually, if I open the project path in Transit, I can see the French files this time. There is one that says LCK which I had never seen before(would that mean lock?).
I am sending you the screenshot, but I can’t retrieve the files…(I have tried, but it says the path cannot be found).
———————-
and now the French file which I managed to retrieve (the original 8d). I have other files with it a .BAS file and a AEXTR file, let me know if they should be sent too.
please let me know if it is correct.
You already have the dictionnaries.
———————-
So I see that you found the FRA file. Where did you find it?
It looks French translated to me, though I can not tell you more than that. You can open this kind of file in Notepad and check yourself, it is more safe that if I check it (I don’t speak French).
No it is enough to send FRA alone. Both this file AND the dictionaries you need to send to Karel, not to me, as he does all the file work, while I do support. So please send both to him.
Please, try to have next files Received correctly. I attach working steps with Transit (skip the installation instructions and read the rest). I hope it helps.
———————-
Welcome to OT.Yes, take your time. Now proofread files just begin to be submitted, therefore in this period it is more important to train and to develop the vetting “skill” and to focus on details, so that when files will start coming hundreds per day it will already be something that you do automatically. I prefer that at this point you will take more time and make the files carefully, with lot of attention to details.
I am going to go over at least one of your vetted files and let you know how it was.
By the way, as you can see, here you can easily attach files, so if you want to show me something you are not sure about, it can be easily done.
———————-
Oxana
Welcome to OT.
No, you do not need to do it with files you already vetted, only with new files I will assign today.
These are two separate things.Stage one – comparing:First, you save proofread and non proofread file as txt.Then you open the proofread one in Word and Compare to the non proofread file.Write report.
Stage two – vetting, what you had already done.In Excel, open REVIEWED file, paste on the left column the source, and vet.Write a report.
You can mark how you did, the third column. At this point, I would like you to mark red and to leave comment explaining what you did. If all you did was adding period in the end of a sentence, don’t mark and don’t write anything. But +, repeating words, double hyphens meantime please write. Additionally to comments inside the Excel file, prepare a Word file with comment table as I explained. All your tables can be in one Word doc, only make them clearly separated that I will understand what is what.
As to spaces before text, I do not understand what you mean. I checked unvetted file 15l, and in all the lines where you wrote that there is “space before text” there had been no space before text. So I would say, ignore it in one file and send me here indicating lines where you see it, and I will take a look. Again, what do you mean when you say “longer column”?
One more thing. I went over file 15l, what you did you did well, but I found many things you missed. Worst – you missed ~55~. It MUST be replaced by &. If we don’t do it, there will be an error in the game. Other things you missed are double hyphens in several places (–, + and ~55~ can be searched for using Ctrl+F), missing points and spaces. I would like to ask you to search for special characters BEFORE you begin to go over the whole file. Make Ctrl+F and search the file. It is very fast. Then look at it slowly.
Now proofread files just begin to be submitted, therefore in this period it is more important to train and to develop the vetting “skill” and to focus on details, so that when files will start coming 10-20 per day it will already be something that you do automatically. I prefer that at this point you will take more time and make the files carefully, with lot of attention to details.
By the way, as you can see, here you can easily attach files, so if you want to show me something you are not sure about, it can be easily done.
Files Project Glossary Language Transit
Projects 01Unfortunately I cannot see the path: as I was telling you, there is something wrong with this, but it’s how it is on my PC and there were lots of problems when we first installed Transit. I have Vista.
To find “Projects” folder go to My Computer->Program files->Transit XV->Projects->[the right project.]: the project folder only shows the Tutorial folder. It’s been like that from the start.
I am forwarding you two screenshots in this mail: first one is to prove just what I told you above, so that you realise I know what I am talking about. Secondly, I have followed Karel’s exact instructions from the start. The problem it seems is that when I received the dictionary, it overwrites the language pair, my only way to get the file is to go to Open>Language Pair (which shows only the dictionary instead of the language pair)> Browse and select the ENU file: this is where something is wrong, but your instructions about receiving the dictionnary are the ones I followed, I don’t understand why it overwrites the language pair. So I translated inside the ENU file, and no FRA file was created.
I am sending you a second screenshot, so that you can see that the folders do appear when I open IN TRANSIT, and that there is no FRA file but the file I used to translate is the ENU file.
I do not know what to do. sHould I create a copy of the ENU file and rename it as FRA?
———————-
Thanks for the email. Let me reply just briefly for now, I will send you a more detailed message later.
I will try and add new suggestions into the add dict. soon.
Thanks for the positive feedback from the lead translator. I’m just curious why the comments are in a file with the name in it…? Isn’t this another translator? Or is this actually the name of the lead translator?
———————-
Well, the fact that you had been translating the ENU file could easily explain why TM did not work for fuzzies.
Now I am pretty sure that you should have tried to resolve it with me before beginning to translate in ENU file.
I think I know what happened. You Received the Glossary after you Received the Project, right? And you saved them under same project name. Therefore glossary overwritten the project. Is it possible?
———————-
is the name of the lead translator.
———————-
To translate other file, you need to Receive the project, and save it under different project name. For example 10001_15g.
Then try to open language pair.
Please try it.
———————-
Remy
For the sake of consistency the ORDER of actions of installation is quite important there. Transit sees dictionaries as projects. Therefore they are installed separately, and once installed, Transit allows to have them activated while translating a “file”, or in Transit’s terms “a language pair”.
These are the instruction for that:
– Go to the Glossary folder in the file server http://translationstop.com/files/, download the relevant and your language French_Main_dictionary.pxf or German_Main_dictionary.pxf.
– Receive the glossary like a project in Transit by going to: Project ->Receive -> choose location of the .pxf file and follow program’s instructions.
– Download and Receive the ADD_New.pxf glossary as well.
– The Main dictionary is the one from which you import terminology into your project.
– The Add dictionary is the one to which you add terms that in your opinion repeat often or need to be added to glossary for other reasons.
D. Receiving the Project files
1) Download the file you were assigned for the server how was explained before.
2) In Transit go to Project ->Receive -> choose location of the .pxf dile and follow program’s instructions.
3) To open the translation file (in Transit called “language pair”), click on “Open language pair” button under the main menu or go to File-> Open->Language pair.
The program will open a window which will show you the files you can translate with this project.
– If the downloaded .pxf file included only one assigned file – you will see only one file you can choose.
– If your downloaded file combined several files you were assigned, you can choose which to translate first.
4) Choose the file you want to translate and click “Open”.
Transit will open the language pair file in 2 windows – one for source and one for target languages. In Transit, the untranslated segments in Target window will appear in English!
3. Working on the file:
3.1. Add the Main Glossary to the Project (you should have it downloaded)
Go to Project -> Settings -> Term_Star Dictionaries Tab ->Add -> Choose French_Main_dictionary/German_Main_dictionary. At this point, it should be the ONLY glossary selected.
Now all terms form the glossary are colored red in the Target and Source windows.
3.2 Insert all terms from the Main Glossary
The Main Glossary consists numerous common terms and Proper Names, which we want to keep consistent in all files of the project. Therefore, insert all terms from it BEFORE you begin to translate.
Open your language pair file, and put the cursor in the beginning of the first Target segment. Go to Edit > “Insert all terms from dictionary”.
Ctrl+S save your file.
* Don’t forget to conjugate the inserted glossary terms (marked red) according to your language’s grammar.
* If you don’t like a term form the Glossary, you should use it anyway, as we need all files to be consistent. But in the same time make a note about it, and send it to (PM) when you deliver the translation. Comments to glossary are later forwarded to proofreaders.
3.3 Add the ADD_New dictionary (you should have it downloaded)
The Add dictionary is for adding new terms. When you finish translating and Send your work, this glossary is sent as well. The terms you added are checked and transferred to the Main glossary.
Go again to Project -> Settings -> Term_Star Dictionaries Tab ->Add -> Choose the Add_New dictionary, make it the current dictionary (to make it easier to add to).
Now you can commence with your translation.
Are these steps clear for you? You MUST insert terms form the Main glossary BEFORE you start to translate.
———————-
Please let me know if you succeeded to open language pair – by saving translation project under a different name.
Please let me know, I want to see if it got resolved.
” I’ll try this now. Sorry didn’t reply sooner. “
I added my translated file to a new project, then sent the translation which said it successfully did it with about 20400KB, but when I try to open it, it’s not there.
Kind
———————-
actually, if I open the project path in Transit, I can see the French files this time. There is one that says LCK which I had never seen before(would that mean lock?).
I am sending you the screenshot, but I can’t retrieve the files…(I have tried, but it says the path cannot be found).
———————-
and now the French file which I managed to retrieve (the original 8d). I have other files with it a .BAS file and a AEXTR file, let me know if they should be sent too.
please let me know if it is correct.
You already have the dictionnaries.
———————-
So I see that you found the FRA file. Where did you find it?
It looks French translated to me, though I can not tell you more than that. You can open this kind of file in Notepad and check yourself, it is more safe that if I check it (I don’t speak French).
No it is enough to send FRA alone. Both this file AND the dictionaries you need to send to Karel, not to me, as he does all the file work, while I do support. So please send both to him.
Please, try to have next files Received correctly. I attach working steps with Transit (skip the installation instructions and read the rest). I hope it helps.
———————-
Welcome to OT.
Yes, take your time. Now proofread files just begin to be submitted, therefore in this period it is more important to train and to develop the vetting “skill” and to focus on details, so that when files will start coming hundreds per day it will already be something that you do automatically. I prefer that at this point you will take more time and make the files carefully, with lot of attention to details.
I am going to go over at least one of your vetted files and let you know how it was.
By the way, as you can see, here you can easily attach files, so if you want to show me something you are not sure about, it can be easily done.
———————-
Oxana
Welcome to OT.
No, you do not need to do it with files you already vetted, only with new files I will assign today.
These are two separate things.
Stage one – comparing:
First, you save proofread and non proofread file as txt.
Then you open the proofread one in Word and Compare to the non proofread file.
Write report.
Stage two – vetting, what you had already done.
In Excel, open REVIEWED file, paste on the left column the source, and vet.
Write a report.
You can mark how you did, the third column. At this point, I would like you to mark red and to leave comment explaining what you did. If all you did was adding period in the end of a sentence, don’t mark and don’t write anything. But +, repeating words, double hyphens meantime please write. Additionally to comments inside the Excel file, prepare a Word file with comment table as I explained. All your tables can be in one Word doc, only make them clearly separated that I will understand what is what.
As to spaces before text, I do not understand what you mean. I checked unvetted file 15l, and in all the lines where you wrote that there is “space before text” there had been no space before text. So I would say, ignore it in one file and send me here indicating lines where you see it, and I will take a look. Again, what do you mean when you say “longer column”?
One more thing. I went over file 15l, what you did you did well, but I found many things you missed. Worst – you missed ~55~. It MUST be replaced by &. If we don’t do it, there will be an error in the game. Other things you missed are double hyphens in several places (–, + and ~55~ can be searched for using Ctrl+F), missing points and spaces. I would like to ask you to search for special characters BEFORE you begin to go over the whole file. Make Ctrl+F and search the file. It is very fast. Then look at it slowly.
Now proofread files just begin to be submitted, therefore in this period it is more important to train and to develop the vetting “skill” and to focus on details, so that when files will start coming 10-20 per day it will already be something that you do automatically. I prefer that at this point you will take more time and make the files carefully, with lot of attention to details.
By the way, as you can see, here you can easily attach files, so if you want to show me something you are not sure about, it can be easily done.