[These pages concern interesting correspondence between our translators and project managers at KENAX, mostly concerning the famous Jade Dynasty translation project.]

File Proofreading French English Translation

I am pasting instructions:
We are managing a very big translation project (1500000 words). The project is translation of a Video Game from English into German and French. Each file goes roughly the following steps:
1. Is imported to Transit, special translation memory software, and then translated by German or French linguists.
2. Is proofread by proofreader.
3. Is exported back to Excel – the resulting file contains only the translation column.
4. Is going through vetting.
5. Is going through spellchecking with proofreader.

Sometimes in the process of transferring the file from one software to other happen small non linguistic mistakes, for example, some characters were replaced by other symbols prior to exporting to Transit because they were causing problems and now need to be replaced back. Sometimes is missing space between sentences, sometimes there are double or strangely located hyphens. Sometimes translators don’t pay attention and leave extra spaces, periods, or several capitalized characters in one word etc.

Here enters the process of vetting.
Usually you will download from a dedicated server a zipped file, containing a folder with proofread files and a folder with unproofread (sometimes called “translated”) files.

You will work only on those files, which I will assign to you.

We work in two steps.
First, we save the .xls files in txt format, open in Word and compare proofread files to unproofread files to see if the file had really been proofread.
If it was, we open the proofread file again in Excel, copy into it English source text, and start vetting.
So vetting is always done in Excel on proofread target (German/French) text against the source (English) text. The purpose of vetting is to find differences from the source, to see if anything is missing and to introduce these minor corrections, or, alternatively, to communicate these differences to proofreader.

Sometimes it is not clear if there is a small missed moment we can correct or a real linguistic mistake. For example, if in the source there is a question mark, but in the target there is a period, you can not just change the period to question mark, because in most languages the structure of the sentence would change. These kinds of cases are communicated to me, and I communicate them to proofreader.

Now, detailed instructions are attached. Please read them, and let me know when you are ready to try. I need you to begin ASAP, preferably even today.

———————-

I guess you know already form your friend what is the work about.
I am pasting bellow instructions.
Don’t forget to let me know how do you want to get paid. If you live in CZ, it may be possible to pay you either directly to bank account or to paypal or moneybookers.

We are managing a very big translation project (1500000 words). The project is translation of a Video Game from English into German and French. Each file goes roughly the following steps:
1. Is imported to Transit, special translation memory software, and then translated by German or French linguists.
2. Is proofread by proofreader.
3. Is exported back to Excel – the resulting file contains only the translation column.
4. Is going through vetting.
5. Is going through spellchecking with proofreader.

Sometimes in the process of transferring the file from one software to other happen small non linguistic mistakes, for example, some characters were replaced by other symbols prior to exporting to Transit because they were causing problems and now need to be replaced back. Sometimes is missing space between sentences, sometimes there are double or strangely located hyphens. Sometimes translators don’t pay attention and leave extra spaces, periods, or several capitalized characters in one word etc.

Here enters the process of vetting.
Usually you will download from a dedicated server a zipped file, containing a folder with proofread files and a folder with unproofread (sometimes called “translated”) files.

You will work only on those files, which I will assign to you.

We work in two steps.
First, we save the .xls files in txt format, open in Word and compare proofread files to unproofread files to see if the file had really been proofread.
If it was, we open the proofread file again in Excel, copy into it English source text, and start vetting.
So vetting is always done in Excel on proofread target (German/French) text against the source (English) text. The purpose of vetting is to find differences from the source, to see if anything is missing and to introduce these minor corrections, or, alternatively, to communicate these differences to proofreader.

Sometimes it is not clear if there is a small missed moment we can correct or a real linguistic mistake. For example, if in the source there is a question mark, but in the target there is a period, you can not just change the period to question mark, because in most languages the structure of the sentence would change. These kinds of cases are communicated to me, and I communicate them to proofreader.

Now, detailed instructions are attached. Please read them, and let me know when you are ready to try. I need you to begin ASAP, preferably even today.

———————-

I think I’m ready to try right now!

———————-

Here are the files and you already know what to do with them 🙂

Karel asks that in you spellcheck in excel, please copy elsewhere the English column, otherwise Excel will jump also to English words. If you spellcheck copying to Word – no problem (if it just underlines the misspelled words).

Comments list attached as well.

———————-

Thank you for fast response! Yes, it’s clear, I could try today, at 16-17:00GMT. Will let you know as I start.

Nice day

———————-

I am ready to work at weekends from 10 to 14(16) and I can start working this sunday. Is it convenient for you?

———————-

ok
I re-vet file German 9b.
I know I could, but I was not sure should I give a sign of cases like this, when translators miss some information.
I re-sending you the file and comments in here, to escape confusions.
Hope on your comment of every mistake I do, to know what I am doing wrong.

———————-

Then let’s try file JD_100201_Localize_11f
It doesn’t need to be compared to unproofread file.

Go to http://translationstop.com/files_PM/ or connect to FTP server.
Download “Originals.rar”. go to folder Proofread -> French, and download the file 11a,f,h.rar. Unzip it. Your file is 11f. Please do not work on any other file.

Then open the PROOFREAD file in Excel, paste the Englsih and start vetting. First Ctrl+F for special characters: +; double hyphen –; ~55~; n/aa etc according to instructions. Then go over the file carefully looking for missing spaces between sentences, missing periods or periods which are not in the source etc. Comment each change you make in the third column and mark the comment cell red. Additionally add the comment to the vetting issues table. I know it slows you down, but this is how I can be sure you are doing everything right.

When finished – change the file name according to instructions and upload it to folder Proofread ->French -> vetted, and send me report (comparing report+vetting issues report) as ticket here.

Please be very careful with French punctuation and numbers format. Read carefully a related link in the useful links page.

Questions here are welcome.
Good luck.

———————-

I live at GMT+6. I hope to be sleeping when you think to begin working. You should try to find some moment when you can be available earlier. If you want, I can assign you file, you will do it, upload it and I will comment in the morning. But for effective training I really need you 2 days online in my waking hours.

———————-

I would also like to know if you are available on weekends, as we always have big volumes of work for Sat-Sun.

———————-

Comments in third column means to create a separate Word doc. and describe(Line Issue Outcome)? Or this is Vetting issues table? And If so than I must also comment in the third column of vetted file right in front of the Proofread and Unproofread texts?

———————-

!
Please let me know, which payment systems are preferable for you except PayPal!
Looking forward to your reply.

———————-

Another quick question, for which I didn’t find a specific answer in the guidelines: when translating creature names (e.g. ‘Spirit’), should I use capital letters as for place names and character names (‘Esprit’), or leave it in lower-case as for items (‘esprit’). My instinct says I should probably use a capital letter, but I wanted to check with you first.

.

———————-

You add a comment BOTH to a separate Word doc (the table) and in the Excel file in the third column.

And why in front of Proofread and Unproofread texts?

Please confirm that you are working on English/Proofread file!

———————-

We already sent two of these. I guess then it’s better to be consistent.

———————-

I’ve done vetting.
Now can you please repeat me what exactly I must send to you?
1. Vetted file.(on server to Proofread/French/Vetted French ?)
2. Vetting issues table(with comments).Into this ticket?
That’s all?

———————-

Oh, and something else I wanted to ask you: I sometimes get the following warning message in a ‘Fuzzy Index’ window that pops up:

Different count of segments in files: C:\Program Files (x86)\Transit XV\PROJECTS\

_JD_100201_Localize_13m\_EXTR_

Should I be worried about this? Any idea what it actually means? I haven’t touched formatting or segment marks or anything like that, so I don’t really understand it.

kenax

CEO at KENAX
Almost all the "articles" I have submitted to this wordpress site have been email correspondence with our translators on larger projects, so that anyone interested in starting a career as a translator might get an idea what it would be like.
by

Leave a Reply