I’m now ready to start, but I’ve got one issue with the segments marked as already translated, as they haven’t actually been translated and the “insert all terms form dictionary” didn’t work for those. Would you have any piece of advice for me?
Could you please confirm that I’ve got to check every single term in my file with the Excel spreadsheet (or is it only for the terms not found in the dictionary?)
Thanks in advance
… And I’ve added the file xxx_1d.ENU in the ref materials (I’ve been allocated the file xxx_1d), but none of the segments (even very short and easy, e.g. “don’t ask”) have a fuzzy matches, so I guess it didn’t work. Any idea why?
Thanks in advance
There’s a big problem: I followed carefully all the instructions in the Instructions.doc files, but the file remains untranslated, none of the segments have been translated. I never had this problem with Transit before, I really don’t know what happens…
Can you help me?
I noticed that the apostrophe/simple quote symbol used very frequently in French, is considered as 6 characters in Transit. For instance, “l’Ã¢me” = 10 characters in the Transit position counter (bottom of the window), instead of 5. Do I have to consider it as one single character or 6 characters?
Please answer as soon as possible, as I could be forced to double check everything.
Some words are translated in different ways in the glossary, for example the word “frenzy” is alternatively translated as “de frÃ©nÃ©sie”, “frÃ©nÃ©tique” or even “de ferveur” (which is wrong).
Do I have to choose one single translation in order to have something coherent?
Sorry but proper names are not translated, even after following instructions. It’s always been the biggest problem I had. And I can’t find a list (like an XL file) anywhere, so I don’t want to screw up your quality rate by re=creating my own translations for proper names.
Please advise: should I translate everything that is not proper names or do you want me to do nothin?
I’m going to spend the whole day on one single file, as I have to translate everything… I guess there should be some pre-translated segments, but that’s not the case.
Please tell me if it’s normal or not, I guess it isn’t, and I don’t want to spend 8 hours on a file if it can be done in 1 or 2 hours.
I was offline for a while, so didn’t get to see your question right away.
If you need to mark everything, and I do mean everything as untranslated, load up the file in question (xxx_1d), and then go to Options -> File Status -> Untranslated. You’ll be ask if you want to replace everything with the source language. Since it’s all in English already, you can save time by saying no.
Only check terms not found in the dictionary (and also for terms that seems odd to you. The guy who made the glossary is human too, and may have made a mistake).
As the the .ENU, check to make sure you have placed both *_1d.ENU and *_1d.FRA from the TM.zip in the directory. You only have to select the .ENU file from Transit, but both files have to be present for it to actually work.
It’s not normal.
, the 1-5all.PXF is the raw untranslated sections.
The TM files are the translated version.
What we are trying to do with the translated version is force Transit to insert the terms from the Dictionary and Glossary first, and only then insert terms from the translated version. This is because the translated files were done some 2-3 months ago, and therefore as far as terms go, are outdated. We want to change this so that overall the project will be consistent, and that the same term is always translated the same way throughout the project.
I’ll digest the rest of your posts in a minute and send you further updates. In the meanwhile, stop your work, take 15 minutes, and I don’t know, play with your cat and relax. I’ll have something more detailed after that.
Alright, I’m waiting for further details.
As I told you I followed the instructions.doc file and it didn’t work, I hope you’ll find a way to solve this issue.
I don’t have a cat hehe, but I’ll relax for a while.
First, as for the apostrophe issue, both are correct. I do not know the exact technical details, but there are two ways Transit renders the apostrophe character. The first is as the single byte ‘ character. The second one is as the 6 characters tag “'” (without the quote). Both are displayed as the apostrophe, but if you look carefully the first type are displayed black while the second one as blue. (You can change the colour coding from the Options menu, I think.)
As to why Transit does it… I have not a clue. The manual never explains why they do things a certain way and thus we’re forced to make guesses and create shortcuts.
Okay back to work, start with the untranslated file. Load it up. Put the cursor at the very beginning of the French side. Make sure the dictionary is attached. Now accept all terms from the dictionary. Save.
Put the *_2c.ENU and *_2c.FRA from the TM.zip into a reference folder somewhere. Name the folder whatever, it doesn’t matter. Go to Project->Settings->Reference Material.
Pick Add File and select the 2c files that you’ve put in the Reference folder. Save Project. Reload the now-partially translated 2c.
Have the glossaries (both of them) open somewhere.
Start using Fuzzy matching to translate.
Okay, this part is a bit fuzzy now.
When you encounter a variant, refer to the glossary to see what’s the standard translation supposed to be. If there’s none, use the version offered by the TM file (in your case, 2c). If there are still variants, pick whatever, but make sure it’s consistent throughout.
Once you are done, save. Now take a look at the file and see if there’s anything that needs to be fixed. Perhaps conjugation. Perhaps the dictionary has an error. Glossary too (we’re working on a corrected, merged, definitive glossary). If there are tags, make sure it’s in the right place. (You may want to tell Transit to display tags. At least the short versions.)
If you’re done, upload the file to the PR folder.
that was my fault: I did CTRL+ENTER instead of clicking on Insert all terms from dictionary…
Sorry for the loss of time, I’ll reset my time counter so you have a good idea of my productivity, I’ll do my best.
” If you encounter any more technical problems, let me know right away. I’ll be here, oh, all evening, maybe up to midnight.
Alright, “A question: when a term is mistaken in French, do I still follow the glossaries? For example, “faceless” is translated as “sans facettes”, but faceless means “anonyme”, which doesn’t mean the same thing at all…
No, when there’s an error, please correct it.
The glossary has errors in it. I’ve caught some myself, even though I don’t know that much French. Some errors are to be expected, given that we’re all human, but we’re working on an updated, corrected glossary.
We don’t want you to wait for the new glossary though. Keep working with the current less-than-perfect glossary and make the corrections as you go.
Sorry, was offline for some time.
First, stop work. We don’t want you working when something’s clearly wrong.
Next, can you describe what aren’t translated? Examples, please.
Third, there’s an outdated glossary (from April) at
download also the text file and read it.
I think those are the Excel files you are looking for.
Again, please give examples of what aren’t translated so I can check and make sure I’m giving you the right solution.
” Alright “Thanks for pointing me to these files: very helpful!
Wish I had known about those earlier.
I was looking for translations for things like:
Pitch Black Coronal
Looks like I am all set, so I get back to it.
I attach some files for spellchecking. I don’t attach a separate comments file, just please scroll the files to see if there are any comments in the third column. If there are any – please resolve them. Take in mind, that vettors don’t speak French, therefore if the sentence is OK, please do not change it.
For spellchecking please select only the French column in Excel.
When completed, please delete any remaining comments, and rename the file adding _Spelled_ after the vettor’s name.
I confirm reception of those. I’ll send them back as soon as possible.