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

Translation Project – Proofreading Glossary File

I was told that now you are away, so this info is for the moment you’ll get back. We decided to keep track of proofreading hours as they come to ease the accounting later.

Therefore, please submit the proofreading hours in a message in your Z_Get ticket on OT when informing about completion of the file.

In BODY of the message please write:

German/French, your name, file name, proofreading hours/minutes.

Please do not submit this info as attachment, I want to be able to see this directly from notification message in my e-mail.

Thank you!

 

—————————-

 

We decided to keep track of proofreading hours as they come to ease the accounting later.

Therefore, please submit the proofreading hours in a message in your Z_Get ticket on OT when informing about completion of the file.

In BODY of the message please write:

German/French, your name, file name, proofreading hours/minutes.

Please do not submit this info as attachment, I want to be able to see this directly from notification message in my e-mail.

Thank you!

 

—————————-

 

We decided to keep track of proofreading hours as they come to ease the accounting later.

Therefore, please submit the proofreading hours in a message in your Z_Get ticket on OT when informing about completion of the file.

In BODY of the message please write:

German/French, your name, file name, proofreading hours/minutes.

Please do not submit this info as attachment, I want to be able to see this directly from notification message in my e-mail.

Thank you!

 

—————————-

 

We decided to keep track of proofreading hours as they come to ease the accounting later.

Therefore, please submit the proofreading hours in a message in your Z_Get ticket on OT when informing about completion of the file.

In BODY of the message please write:

German/French, your name, file name, proofreading hours/minutes.

Please do not submit this info as attachment, I want to be able to see this directly from notification message in my e-mail.

Thank you!

 

—————————-

 

I am not familiar with any problem with your files and as such I’m forwarding your mail to .

I check files really quick for misalignment, untranslated sections, and tag mistakes. Yours aren’t perfect, but still normal. I can’t even remember any details because normal files get forgotten right away.

The files then get forwarded to proofreaders.

Since I don’t remember any problem with the data structure of your translation, if there’s any problem it must be with the actual translation. Maybe a proofreader feels you made too many conjugation errors, or does not follow the client’s capitalisation request, I don’t know.

The proofreaders make reports on every file they read and ‘s the one who reads them all. So I’m asking about it.

There’s also the possibility that it’s your actual proofreading that’s the problem. But as I recall you only proofread 1 file, and that’s a duplication due to my mistake.

Not that there’s any file to translate yet. moved to another country, and this delayed things a lot.

 

—————————-

 

what kind of details do you need exactly? Those were my first files to proofread so all I have written down is:

10h – Website localization

12h ¢‚¬œ files 1a, 1b, 2a, 2b, 2d, 3a, 3c, 4b

1h ¢‚¬œ 4d

= 23h (1380min)

Was in February but don’t know the exact dates.

Best wishes

 

—————————-

 

Please contact me on the issues of quality or communication with proofreaders. You can contact on technical issues and issues related to files.

I believe I had already sent you proofreader’s comments on one of your files.

In case I didn’t here it is again:

_________________________

 

Proofreading Report ¢‚¬œ

JD_100201_Localize_13n

Translation:

As long as the meaning is simple and the sentence structure is identical in French, the translation is decent. When the text becomes more complicated, the translation becomes confusing or makes no sense.

The translator does not seem to have a good enough knowledge of English to understand the English text. The meaning of some segments has nothing to do with the original text.

Too many terms were not translated according to the glossary, creating numerous inconsistencies.

Many segments were left untranslated but marked as translated.

There is a tendency to literal translation, the text often lacks fluency.

Grammar:

There are too many spelling errors, they could have been avoided with a spellcheck.

Plural agreements were regularly missing for glossary terms.

There were many occurrences of misconjugated verbs.

Grammar agreements: plural and feminine agreements omitted.

Punctuation:

Some final punctuation was missing.

Place names were sometimes not capitalized.

The translation is bad. The translator struggled with the meaning of the text. The translation of some segments had nothing to do with the English text. There were also many spelling/grammar errors and the translator frequently forgot to apply the guidelines.

______________________________

 

My suggestion would be to proofread very carefully the file after completing the translation, may-be to proofread it even more then once. It increases greatly the quality. Also copying the text to Word and spellchecking adds to the overall impression. I would also suggest to reduce speed for the sake of quality, checking well each segment for meaning, punctuation and only then passing to the next. Speed is good, but quality is much more important.

Now there are new guidelines for this project about to be published today or tomorrow, please make sure to read them throughly and understand them before you take files for this project.

I am always available for any support issues here on CS or on OT on “Help desk to existing translators” category. Whatever questions arise, I always prefer to resolve them BEFORE translation gets delivered. Therefore, please feel free to address me with any project-related questions.

 

—————————-

 

Thank you,

 

—————————-

 

I think the google spreadsheet is a good way to share our thoughts on (dictionary) terms. During proofreading I’ve come across some terminology issues and a google spreadsheet would be fantastic for having other opinions on this (instead of uploading doc-files all the time)

I think as long as the spreadsheet follows a certain logic and does not become confusing it could be of great help.

 

—————————-

 

I went through the whole glossary dictionary file again and made some changes in order to make everything even more consistent.

Just relaized that the file I just sent has the same name as the file I sent previously. Hope you can keep them apart.

So, now only 01_G and 05_G are left. I should manage them until Sunday at the latest.

 

—————————-

 

I have a few comments regarding consistency.

In the file 02_Glossary, you translated greavese by jambierese. I used grevese so far because to me, jambierese can be either a piece of clothing or a piece of armour, while grevese is solely used as a reference to a piece of armour.

In other files, Tree of Lifee was translated by Arbre-Mondee, while you chose Arbre du Mondee. I think Arbre du Mondee sounds better.

Celebeame was translated by Faisceau Celestee in other files, and you chose Rayon Celestee, which sounds more appropriate.

You translated Bashe by Coupe, while I used Commotione. This is the name of a skill, and I think it might be better to use something stronger than coupe.

So far, I used Assassine to translate Slayere, but you chose Tueure.

In some files, Maguse was translated by Maguse, in others, by Magee.

I think pointstrikee was translated by coup de pointe in some files. Your translation ¢‚¬œ coup ciblee ¢‚¬œ seems more accurate.

Instancee was sometimes translated by exemplee, circonstancee or instancee. I do not think instancee is appropriate, so -depending on the context ¢‚¬œ exemplee or circonstancee should be favored.

You had two different translations for Moremoorse, Morimoruse and Morimortuse. I assumed the latter had a typo and retained the former.

Since you are in charge of these issues, this is your call. I did not modify any of the above ¢‚¬œ unless stated ¢‚¬œ so you will have to decide which terms to retain.

Anyway, please let me know which terms you would rather use so that we do not create unnecessary consistency issues.

Let me know if you have questions.

JM

 

—————————-

 

I believe the smaller file is the most recent, right?

I’m somewhat confused by you resending Names_et_al

Is this just for back-up? Is all the change made to Names are reflected already in the main glossary?

 

—————————-

 

Yes indeed, I received and read the notes on the very first file (13n) I translated, but I’ve translated many since and have no idea what’s wrong with those…

I proofread the next ones (I had a huge problem with transit while I was working on the first file and finally installed the software on another computer and since then it worked normally for the next files) them and copied them in word for the spelling and I haven’t read any remarks on the other files I translated since the first one.

Please tell me if there is something wrong with all the other files I translated except for 13n.

Are the new instructions already available?

Thank you.

 

—————————-

 

Ok thanks, I’ve had an answer from (for the moment they only talked about the very first file 13n when I had problems with the software and had to install it on another computer for the next ones) but don’t know yet what is supposed to be wrong with my other files…

I’m waiting for an answer.

Have the new instructions been published yet?

 

—————————-

 

Yes, the smaller dictionary file is the more recent and up-to-date one!

As for names and places, I sent it again as I had to do some changes (I think I labeled the file revised)

All changes made are reflected in the dictionary.

Do you think it is possible to send you the whole batch of files in one run (and to take the other files from the online server in the meantime)?

There are a few terms I’d like to check in all files again, if possible (really minor issues).

 

—————————-

 

Thank you for the feedback. Here are a few details about the choices I made:

– Regarding “jambieres” I considered “greves” too but I assumed that jambieres was more accurate precisely because we are dealing with armor parts. Besides, I think “jambieres” might be easier to understand for the players who will probably be pretty young.

– The “Tree of Life” thing sounds odd to me, I think I would have translated it as “Arbre de Vie” there might be an issue somewhere or the translation might have been already there and I just fixed it to make it sound better (Arbre-Monde – Arbre du Monde)

– Regarding “Bash” I agree, something stronger than “coup” could be more appropriate. If there wasn’t any context surrounding it, I probably went with “Coup” because it’s short, therefore it eases the process of keeping translations within the 31 character limits.

– Same thing for “Slayer”, I went with “Tueur” to keep it simple and, more importantly, short. We can change it if needed. We just need to make sure that “Assassin” for instance isn’t used elsewhere.

– “Instance” was and is still a real issue. I did some research and it turns out Instance is a technical term here. Let me try to explain what it refers to.

Every player/group of player wants to explore the dungeon, slay the monsters and rescue the princess in the game. However, since there is only a limited amount of dungeons in the game, and thus a limited amount of monsters to slay, and princess to save, the programmers had to find a way to make these tasks available to everyone.

Whenever a player/group of player enter a dungeon, the game creates a “copy” of the dungeon exclusively for these players. Hence they can explore the whole dungeon without being disturbed by other groups of players.

This process of creating “parallel areas” is called “Instancing”. Despite my research, I haven’t found any French word for this. As far as I know, the term “Instance” is used in French too to describe this process. If you find a more appropriate term though, please let me know. I have a lot of work to catch up on so I couldn’t spend too much time researching this.

– Yes, Morimortus was a typo, thanks for correcting it. “Moremoors” is the name of a scorpion boss so I came up with Mori (dead(s) in Latine) and morus (a scorpion species I think). I htought it would fit here.

Okay, since I am still proofreading files as I write this message, the easier solution might be to keep all these remarks somewhere and, once the glossary is completed, we will do the necessary fixes before inserting the terms in the other files.

Please let me know if you need anything in the meantime, I will send a copy of this message to and so that they are informed about the situation too.

With many thanks

 

—————————-

 

This is just for your information.

—————————————-

Thank you for the feedback. Here are a few details about the choices I made:

– Regarding “jambieres” I considered “greves” too but I assumed that jambieres was more accurate precisely because we are dealing with armor parts. Besides, I think “jambieres” might be easier to understand for the players who will probably be pretty young.

– The “Tree of Life” thing sounds odd to me, I think I would have translated it as “Arbre de Vie” there might be an issue somewhere or the translation might have been already there and I just fixed it to make it sound better (Arbre-Monde – Arbre du Monde)

– Regarding “Bash” I agree, something stronger than “coup” could be more appropriate. If there wasn’t any context surrounding it, I probably went with “Coup” because it’s short, therefore it eases the process of keeping translations within the 31 character limits.

– Same thing for “Slayer”, I went with “Tueur” to keep it simple and, more importantly, short. We can change it if needed. We just need to make sure that “Assassin” for instance isn’t used elsewhere.

– “Instance” was and is still a real issue. I did some research and it turns out Instance is a technical term here. Let me try to explain what it refers to.

Every player/group of player wants to explore the dungeon, slay the monsters and rescue the princess in the game. However, since there is only a limited amount of dungeons in the game, and thus a limited amount of monsters to slay, and princess to save, the programmers had to find a way to make these tasks available to everyone.

Whenever a player/group of player enter a dungeon, the game creates a “copy” of the dungeon exclusively for these players. Hence they can explore the whole dungeon without being disturbed by other groups of players.

This process of creating “parallel areas” is called “Instancing”. Despite my research, I haven’t found any French word for this. As far as I know, the term “Instance” is used in French too to describe this process. If you find a more appropriate term though, please let me know. I have a lot of work to catch up on so I couldn’t spend too much time researching this.

– Yes, Morimortus was a typo, thanks for correcting it. “Moremoors” is the name of a scorpion boss so I came up with Mori (dead(s) in Latine) and morus (a scorpion species I think). I htought it would fit here.

Okay, since I am still proofreading files as I write this message, the easier solution might be to keep all these remarks somewhere and, once the glossary is completed, we will do the necessary fixes before inserting the terms in the other files.

Please let me know if you need anything in the meantime, I will send a copy of this message to and so that they are informed about the situation too.

With many thanks

 

—————————-

 

This is just for your information

———————————

Thank you for the feedback. Here are a few details about the choices I made:

– Regarding “jambieres” I considered “greves” too but I assumed that jambieres was more accurate precisely because we are dealing with armor parts. Besides, I think “jambieres” might be easier to understand for the players who will probably be pretty young.

– The “Tree of Life” thing sounds odd to me, I think I would have translated it as “Arbre de Vie” there might be an issue somewhere or the translation might have been already there and I just fixed it to make it sound better (Arbre-Monde – Arbre du Monde)

– Regarding “Bash” I agree, something stronger than “coup” could be more appropriate. If there wasn’t any context surrounding it, I probably went with “Coup” because it’s short, therefore it eases the process of keeping translations within the 31 character limits.

– Same thing for “Slayer”, I went with “Tueur” to keep it simple and, more importantly, short. We can change it if needed. We just need to make sure that “Assassin” for instance isn’t used elsewhere.

– “Instance” was and is still a real issue. I did some research and it turns out Instance is a technical term here. Let me try to explain what it refers to.

Every player/group of player wants to explore the dungeon, slay the monsters and rescue the princess in the game. However, since there is only a limited amount of dungeons in the game, and thus a limited amount of monsters to slay, and princess to save, the programmers had to find a way to make these tasks available to everyone.

Whenever a player/group of player enter a dungeon, the game creates a “copy” of the dungeon exclusively for these players. Hence they can explore the whole dungeon without being disturbed by other groups of players.

This process of creating “parallel areas” is called “Instancing”. Despite my research, I haven’t found any French word for this. As far as I know, the term “Instance” is used in French too to describe this process. If you find a more appropriate term though, please let me know. I have a lot of work to catch up on so I couldn’t spend too much time researching this.

– Yes, Morimortus was a typo, thanks for correcting it. “Moremoors” is the name of a scorpion boss so I came up with Mori (dead(s) in Latine) and morus (a scorpion species I think). I htought it would fit here.

Okay, since I am still proofreading files as I write this message, the easier solution might be to keep all these remarks somewhere and, once the glossary is completed, we will do the necessary fixes before inserting the terms in the other files.

Please let me know if you need anything in the meantime, I will send a copy of this message to and so that they are informed about the situation too.

With many thanks

 

—————————-

 

Have a look at the currect glossary (28 May).

The excel file.

I notice some terms aren’t translated the same.

Potion of Percision Trank der Perzision

Potion of Precision Prazisions Trank

Percision is a mispelling of Precision, and it should be translated as Prazisions Trank too.

There are several others that I saw just by scanning the file.

Constellation Card Sternbild Karte

Constellation Card swb Sternzeichen Karte swb

Please allot some time going through the glossary to catch stuff like this before going to 5 & 1.

The glossary has been sorted alphabetically to make catching this sort of error easier on you.

 

—————————-

 

Could you upload the 28may.xls again, please.

It cannot be downloaded.

 

—————————-

 

In which file did you find those examples?

Potion of Percision Trank der Perzision

Potion of Precision Pr’‚¤zisions Trank

Constellation Card Sternbild Karte

Constellation Card swb Sternzeichen Karte swb

 

—————————-

 

I was wondering why I haven’t received a new file assigment yet. Have there been any quality issues with my previous translation? It would nice to get notified in such a case, so I have the chance to correct things. Or are you guys working on the glossary? Let me know please.

Thanks

 

—————————-

 

28may.xls is corrupt and has been taken down.

Instead, use http://translationstop.com/files/Glossary/Glossary_DEU_28May.rar

The error I described can be found in that glossary file. Exactly which file it came from is not relevant, since they’re all combined into a single glossary anyway.

 

—————————-

 

I’m not the right person to ask about quality issues. Proofreaders forward their comments to not to me.

However, we are working on the glossary.

Long story short,’s (lead translator/proofer) taking a vacation. I didn’t know until the last minute. Glossary went unproofed, and the project stalled.

has been asked to fill in. And he’s doing well. He has turned in 60% of the glossary proofed, and the remainder is promised over the weekend.

 

—————————-

 

Ok, thanks for the info.

 

—————————-

 

OK, thank you.

I have made some more changes to the dict file.

I’ll upload the xls file.

 

—————————-

 

Is it possible to get some feedback on the quality of my previous translations (JD project)? It would be helpful to see what the proofreaders said, also in regard to the new project.

Many thanks

 

—————————-

 

Just wanted to let you know that I’m available to translate about 3,000 words a day or 18,000 words a week for the next couple of months.

 

—————————-

 

Sorry that I contact you but it is impossible to get in touch with . He has blocked the access to his inbox and all emails are coming back…

In his last mass email he wrote that you already started with the second project and those who have not yet been contacted is because of quality problems with their files.

Please, could you tell me quickly what is going on with my files and what I did wrong??? As I have not been contacted I suppose that I will not be “on board” for the next project, right?

Thank you.

 

—————————-

 

is slowly trying to move things off himself and his mailbox.

I don’t know if he actually blocked access. Which email address are you talking about? If it’s the gmail account, eh, that’s a spam-trap anyways.

Now, about the quality….

The correct person to ask is actually . I check incoming files for alignment and untranslated words, and if I have the time, spot-check the tags. I then forward them to the proofreaders. The proofreaders correct the translation if necessary, but either way the report is passed to . So she knows the details.

I do notice that your 4d has 208 words untranslated and had to take over the file.

To complicate matters, the French side’s situation is so bad that it threatens the German side.

Basically, we didn’t have enough people in the French group and had to make do with new untested people. A few of the new people worked okay, but quite a bit more are crap. This in turn caused the client to get angry at us in general, regardless of the language.

‘s talking to them. Wish him the best.

 

—————————-

 

Sorry that I contact you but it is impossible to get in touch with . He has blocked the access to his inbox and all emails are coming back…

In his last mass email he wrote that you already started with the second project and those who have not yet been contacted is because of quality problems with their files.

Please, could you tell me quickly what is going on with my files and what I did wrong?? As I have not been contacted I suppose that I will not be “on board” for the next project, right?

Thank you.

 

—————————-

 

I just wanted to let you know that I have started working on section 16 of JD. The whole section hasn’t been proofread so it looks like a good place to start.

knows this already and I advised him to inform you about the files he will work on so as you can organize the file distribution with everyone. I haven’t checked with the other proofreaders though.

With many thanks

 

—————————-

 

I’ll be absent for the next four (4) days, so please don’t assign to me no any urgent file in that period, thank you.

Respectfully

 

—————————-

 

Alex, I haven’t heard from yet but a copy of this is also emailed to him so he can stay informed.

Currently the rough plan goes like this:

1. Proofread all the files that weren’t before if possible.

2. Search through all the files for inconsistent names and replace them all with a single consistent translation.

3. Use an Excel macro to go through the files and search for certain terms and replace it with the same term but with the proper capitalisation.

However, your input on how to best do bring the quality of our translation project up will be much appreciated. We aren’t above scrapping the above methods if you have something better in mind.

Currently and can help immediately. Just tell them what to do. is available Monday, but not Tuesday-Thursday, but will be back again on Friday and onward. is not available until Friday, but will help us then.

Unless you suggest otherwise, I am suggesting that we use the Excel files, which are easier to handle for search/replace. I’m also suggesting that after section 16, we move on to section 10.

 

—————————-

 

This is a copy of an email sent to. It’s sent to you so you can keep abreast of the latest information.

Currently the rough plan goes like this:

1. Proofread all the files that weren’t before if possible.

2. Search through all the files for inconsistent names and replace them all with a single consistent translation.

3. Use an Excel macro to go through the files and search for certain terms and replace it with the same term but with the proper capitalisation.

However, your input on how to best do bring the quality of our translation project up will be much appreciated. We aren’t above scrapping the above methods if you have something better in mind.

Currently and can help immediately. Just tell them what to do. is available Monday, but not Tuesday-Thursday, but will be back again on Friday and onward. is not available until Friday, but will help us then.

Unless you suggest otherwise, I am suggesting that we use the Excel files, which are easier to handle for search/replace. I’m also suggesting that after section 16, we move on to section 10.

 

—————————-

 

Yes, that’s probably our best course of action.

JM and I have already started working on the files. I told him I was working on section 16 but I don’t know which files he picked. Once he gets back to me I’ll inform the other proofreaders of the available files.

Like I said to numerous times, I think the capitalization thing is a lost cause. Even with the time extension, the search and replace method won’t work because of the many discrepancies there are. Plus I strongly doubt we will have enough time to review the entire project to correct all consistency issues.

As far as I can tell, all area names like “IncenseValley” or “Doom Bog” for instance have been capitalized in French too, as well as the game interface and commands. So even if the translations are not 100% consistent with the glossary, at least we have this covered.

If we start changing the caps now for all items in the files, we risk ending up with a half done job which would be worse than the current situation. Again, this is something that should have been decided at the beginning of the project, not now that it’s almost complete. We cannot possibly be liable for the sudden change of mind of the client.

If the client still wants us to do it though, even if we get an additional delay, I think it would be wise to check with about the costs of such an operation. I can already tell this is going to be extremely expensive and time consuming. The search and replace thing is also a very risky bet since the smallest mistake could alter thousands of words across the whole project which would be almost impossible to fix.

Please discuss this seriously with because whatever you guys decide, we will need to know as soon as possible since we have already started with the proofreading.

With many thanks

 

—————————-

 

Hello

When will you know which translators from the previous team you will take along the ride for the new project.

A short email – even if it is a negative confirmation – would be appreciated.

Thanks and

 

—————————-

 

Fabian is a colleague of mine who has translated some files. If it is easier for you, you can just make all payments to him through me. If it is no big trouble though, I will forward you his word counts and rate.

Thank you much

 

—————————-

 

I think it would be best if you took care of the file distribution yourself. This way you’re on top of things and you can actually make sure that we don’t forget anything. I fear I will be in complete chaos if I have to deal with this in addition to the language issues and the side questions.

So far, JM is taking care of section 14 and I’m taking care of section 16.

I thought could deal with section 9 since she’s already done some of it previously. You can assign some files to too, I don’t know what is her capacity or availability.

I will send them both some instructions regarding how to proceed with the proofreading and provide them with the final excel glossary if they don’t have it already.

Since this is the fine tuning of the project it’s probably best to rely only on the cream of the crop. As far as the proofreading goes it might be good to keep it between the proofreaders mentioned since we are sure about the quality of their work.

Please let me know if you need anything

 

—————————-

 

I don’t know if has contacted you already but we will need your help to finish the proofreading of Jade Dynasty. He will assign you some files soon if he hasn’t.

In the meantime, I just wanted to send you some specific instructions regarding these next assignments.

We have decided to proofread the files in Excel format directly this time. This means we won’t have access to the Termstar Dictionary and we won’t be able to insert terms directly.

Instead, we will be using the complete glossary in Excel format. The entire success of this final proofreading is based on consistency between all of us proofreaders. Therefore, it is of utmost importance that you refer to the glossary at all times.

Even if you think you already know the translation of a specific term check the glossary. There are lots of translations in there that were added/changed only at the last minute.

Also, we won’t have time to fix this glossary so even if you notice a translation that could be improved or is downright wrong, use it nonetheless. This is our last chance to improve the overall consistency so we have to follow this blindly.

Finally, item names should be in LOWER CASE. Do not follow the same pattern as BOI. Just capitalize character names and area names (Bilu, Vallee de l’Encens, Marais Maudit, Shaw Danon, etc.) but leave the items in lower case (You found a Fire Sword – Vous avez trouve une epee de feu).

Please let me know if you have any questions, you should receive files shortly if you are available and we’ll get started.

You will find the glossary in the CS (the interface where you can write messages to me or the project managers) in the “Proofreader’s files” section. (File name: JD Glossary.zip).

With many thanks

 

—————————-

 

I don’t know if has contacted you but we will need your help to finish the proofreading of Jade Dynasty. He will assign you some files soon if he hasn’t already.

In the meantime, I just wanted to send you some specific instructions regarding these next assignments.

We have decided to proofread the files in Excel format directly this time. This means we won’t have access to the Termstar Dictionary and we won’t be able to insert terms directly.

Instead, we will be using the complete glossary in Excel format. The entire success of this final proofreading is based on consistency between all of us proofreaders. Therefore, it is of utmost importance that you refer to the glossary at all times.

Even if you think you already know the translation of a specific term check the glossary. There are lots of translations in there that were added/changed only at the last minute.

Also, we won’t have time to fix this glossary so even if you notice a translation that could be improved or is downright wrong, use it nonetheless. This is our last chance to improve the overall consistency so we have to follow this blindly.

Finally, item names should be in LOWER CASE. Do not follow the same pattern as BOI. Just capitalize character names and area names (Bilu, Vallee de l’Encens, Marais Maudit, Shaw Danon, etc.) but leave the items in lower case (You found a Fire Sword – Vous avez trouve une epee de feu).

Please let me know if you have any questions, you should receive files shortly if you are available and we’ll get started.

You will find the glossary in the CS (the interface where you can write messages to me or the project managers) in the “Proofreader’s files” section. (File name: JD Glossary.zip).

With many thanks

 

—————————-

 

I am currently tackling section 14. In file 14f, there are red boxes marked “Please check on plus”. There are usually strings of signs in the French translation box. Should I do anything about that ?

 

—————————-

 

The client is asking that we check our German files too (except that they haven’t even looked at it) and the only thing we can think of at this moment is proofing 4b, 4c, and 4d.

Earlier you said there wasn’t enough time to proof them. Do you think if I hand you Excel files of those 3 files you can proofread them by Friday or Saturday?

Please reply via the Open Ticket, by the way. That way and can see it and assign you the files if I’m not there.

 

—————————-

 

Please ignore this message if you’re not involved with translator quality assessment. If you are, please take a couple of minutes to read the following. Thanks in advance.

 

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