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

Translation and Proofreading of French Glossary Files

Thanks for the update and I wish you good luck for finishing this first project and starting (again) the second one.

I’ve open my JD_quality.report and I have to reply, so please forward to the appropriate person if not you. It is very important to me to defend unfair critics of the quality of my work when those critics should be addressed to another translator (as far as I can understand from the JD_quality.report).

I hope that this email will clear any doubt on the quality of my work.

I’m currently available part time for correcting any French files if need/wanted.

In this JD_quality.report, only two files appeared:

– 18L: please see below the comments I’ve sent along with the file upon translating it:

French_JD_100201_Localize_18L (translated)

18L was a bad file to translate! Be aware that it has been extremely difficult and frustrating to work on this file, because the already translated segments (nothing I can do about them) did not respect the tags position, and so it went for the fuzzy matches. Your proofreader will have a lot to go through to put everything back to normal. When my segment was extremely similar to the fuzzy match, I’ve used it, even if I did not agree with the offered translation, as I think it will be easier for your proofreader to change everything at the same time. There are also some translations I’ve found very bad, even completely wrong in some instances.

Please find here below a few comments on my translation for the file in subject:

1. directly related to the above comment, a large number of already translated segments (by another translator) did not respect at all the tags’ position within the segment, for example segments 94, 118, 269a¢¢¬‚¦ Same for the fuzzy matches, for example segments 76, 139a¢¢¬‚¦ In segment 1120, the “f” of “passif” was behind the tag, which split the word into 2 parts. As it is part of the already translated segments, I assume there are many occurrences of this problem.

2. “heals” has been translated by another translator as “hurts”, so the French meaning is the opposite of the intended one! Might be worth to check across files for heal, healinga¢¢¬‚¦

3. the word “yard” has sometimes be left untranslated by other translators. I would recommend to simply change it into m’‚¨tre, as the difference between those two units are very small and thus would not have any negative impact.

4. “caster” has been already translated by another translator into “lanceur”, which makes sense if limited bt the number of digits, otherwise, I believe that “lanceur du sort” would be more appropriate. “damage skill” has been translated by another translator into “les dommages de la comp’‚©tence”, which to me doesn’t make any sense, maybe “capacit’‚© de dommages” would be better (even if not great). “cloud awareness” has been translated by another translator into “sensibilisation nuage”, which to me doesn’t make any sense, maybe “nuage de conscience” would be better. But I kept all of them for consistencya¢¢¬‚¦

5. I have used a few + when unsure about a translation

6. I’ve left 2 segments untranslated: 314 and 709

Good luck for the proofreading on this one, I believe it won’t be easy!

Hope this helps

As always, I’m happy to receive feedback on this work

– 15n: file translated by Alex, not me!

 

—————————-

 

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.

 

———

 

Thanks for the update and I wish you good luck for finishing this first project and starting (again) the second one.

I’ve open my JD_quality.report and I have to reply, so please forward to the appropriate person if not you. It is very important to me to defend unfair critics of the quality of my work when those critics should be addressed to another translator (as far as I can understand from the JD_quality.report).

I hope that this email will clear any doubt on the quality of my work.

I’m currently available part time for correcting any French files if need/wanted.

In this JD_quality.report, only two files appeared:

– 18L: please see below the comments I’ve sent along with the file upon translating it:

French_JD_100201_Localize_18L (translated)

18L was a bad file to translate! Be aware that it has been extremely difficult and frustrating to work on this file, because the already translated segments (nothing I can do about them) did not respect the tags position, and so it went for the fuzzy matches. Your proofreader will have a lot to go through to put everything back to normal. When my segment was extremely similar to the fuzzy match, I’ve used it, even if I did not agree with the offered translation, as I think it will be easier for your proofreader to change everything at the same time. There are also some translations I’ve found very bad, even completely wrong in some instances.

Please find here below a few comments on my translation for the file in subject:

1. directly related to the above comment, a large number of already translated segments (by another translator) did not respect at all the tags’ position within the segment, for example segments 94, 118, 269a¢¢¬‚¦ Same for the fuzzy matches, for example segments 76, 139a¢¢¬‚¦ In segment 1120, the “f” of “passif” was behind the tag, which split the word into 2 parts. As it is part of the already translated segments, I assume there are many occurrences of this problem.

2. “heals” has been translated by another translator as “hurts”, so the French meaning is the opposite of the intended one! Might be worth to check across files for heal, healinga¢¢¬‚¦

3. the word “yard” has sometimes be left untranslated by other translators. I would recommend to simply change it into m’‚¨tre, as the difference between those two units are very small and thus would not have any negative impact.

4. “caster” has been already translated by another translator into “lanceur”, which makes sense if limited bt the number of digits, otherwise, I believe that “lanceur du sort” would be more appropriate. “damage skill” has been translated by another translator into “les dommages de la comp’‚©tence”, which to me doesn’t make any sense, maybe “capacit’‚© de dommages” would be better (even if not great). “cloud awareness” has been translated by another translator into “sensibilisation nuage”, which to me doesn’t make any sense, maybe “nuage de conscience” would be better. But I kept all of them for consistencya¢¢¬‚¦

5. I have used a few + when unsure about a translation

6. I’ve left 2 segments untranslated: 314 and 709

Good luck for the proofreading on this one, I believe it won’t be easy!

Hope this helps

As always, I’m happy to receive feedback on this work

– 15n: file translated by Alex, not me!

 

—————————-

 

I received a mail from today, saying there were in fact big quality problems on the French translation, and that it could take a few weeks to resolve these issues. Can I help in anything? I wish I can, if I can speed this process up in any way please let me know.

 

—————————-

 

I received a mail from today, saying there were in fact big quality problems on the French translation, and that it could take a few weeks to resolve these issues. Can I help in anything? I wish I can, if I can speed this process up in any way please let me know.

 

—————————-

 

I just got an e-mail from with the following details:

Total earnings for translation: 1,164

Total earning for proofreading and other hourly work: 1,410

Combined total: 2,574

What you have been paid so far: 796

Total owed remaining: 1,777

of which 75%: 1,333

 

This (the earnings for proofreading) is not correct. I proofread 7025minutes (117 hours and 5 minutes) so the earing for proofreading should be 1,755.

Best wishes

 

—————————-

 

if you have 6 hours to spare, I’d like you to do spot check on the Jade Dynasty German files.

We need to ascertain whether we need to spend more effort with our German files and if we do, in what respect.

To that end, I’d like you to download the German translation from the following site.

http://translationstop.com/files/German-JD/

When you unzip it, you’ll end up with 255 Excel files.

I want you to randomly pick 1 file out of each section and then read it through. Spend 15 minutes on each file, paying particular attention to capitalisation and consistency of terms (see glossary for what the official terms should be). Watch out the hyphenation and spelling too.

Write a report on each file and let us know your assessment regarding the quality. Do not bother fixing errors and stuff like that. That is not what we are asking you to do at this moment.

There are 19 sections. Add a 20th file from one of the longer sections. Again, pick it at random.

Your report will be used in deciding what to do with the German files. Because of that, we’d like it as soon as possible.

The last JD glossary can be found here.

http://translationstop.com/files/FTP/

Oh, is proofing 4b, 4c, and 4d, so for section 4, check 4a instead of picking a random file.

The Report should be uploaded here:

http://001yourtranslationservice.com/newsystem/cgi-bin/up_1001_PR.cgi

Make sure to put your name in the file name. In the report itself, write down your name, id code, how much time you spent doing this assessment, and which files you checked. Write down also your assessment of the condition of each file and then also a general assessment for the project as a whole. At 15 minutes per file, I estimate 5 hours for 20 files, and another hour for writing the report, for a total of 6 hours. But write down the actual hours anyway.

 

—————————-

 

Sure. I will have them done asap.

All the

—————————-

 

I understand your doubts. I remember you have 7025 minutes of proofreading hours. But I am not dealing with accounting any more (at least till will assign me again). I have forwarded your letter to him, so please unless I state you with opposite contact directly for solving payment’s questions.

All the

 

—————————-

 

I just heard from that you are already looking at parts of JD, and he suggested I write to you so we can co-ordinate.

I have not yet skimmed over all the files, but I will do that in the evening. Should you already have specific ideas or a strategy, maybe you could give me some hints. Otherwise, I will just skim over the files and try to identify problems and share my ideas with everybody.

As I am writing this, tells me that will be checking random files from each section over the next hours to identify problems, so we may know more soon.

 

—————————-

 

good to hear from you. Yeah, I have just started skimming over the first file (4b) und I think spelling and formatting is ok but I have found several glossary deviations already.

My strategy is to sort the glossary in alphabetic order, then skim for different translations of the same term first,and check those in the most recent glossary (German_Main__2504) and correct terms if necessary.

As I said, I think consistency is the most important issue. Otherwise I haven’t come across any serious blunders yet…Knock on Wood!

While proofing, we should also use the 31-character-limitation macro to avoid another round of proofing.

At any rate, let’s share file problems, thoughts and ideas!

That’s it for now.

 

—————————-

 

just sent me the details regarding the next payment and there is a discrepancy in the earnings for translation.

Your count is:

Total earnings for translation: 1,394

Total earning for proofreading and other hourly work: 2,560

Combined total: 3,954

My count is:

Total earnings for translation: 1,983

Total earning for proofreading and other hourly work: 2,560

Combined total: 4,543

Here are the details for translation:

Please let me k now if you have questions.

 

—————————-

 

I am assigning you for proofreading files

Please try to have them done by tomorrow evening GMT. Let me know if you think you can’t complete proofreading by that time.

This time proofreading will be done on Excel files. You can download all French files here: http://translationstop.com/files/French/Finalized.French_ALL.zip (8MB file, let me know if you have a difficulty downloading large files).

Please proofread the file, putting special attention to consistency of the terminology used with the last glossary (French_Glossary_Merged2.xls and Recent -Glossary updates.xls if you don¢‚¬„¢t have these files download them here:1. http://translationstop.com/files/FTP/Recent%20-French%20Glossary%20updates.xls 2. http://translationstop.com/files/FTP/French_Glossary_Merged2.rar)

Please repair the capitalization when necessary (first letter of first word of each special term, such as special items etc.).

Additionally please pay attention that correct abbreviations are used for French:

SP (Spirit Points) – PE (Points d’Esprit) [sometimes also Spirit can be abbreviated PE, when matching the context]

AP (Attack Power) – PA (Puissance d’Attaque)

AOE (Area of Effect) – “Zone d’effet”

Please do not leave any unresolved issues. If you are not sure about something, you can contact or via CS. Any problems you think I may be able to help you with ¢‚¬œ feel free to contact me via OT or CS.

 

—————————-

 

I am assigning you for proofreading files

Please try to have them done by tomorrow evening GMT. Let me know if you think you can not complete proofreading by that time.

This time proofreading will be done on Excel files. You can download all French files here: http://translationstop.com/files/French/Finalized.French_ALL.zip (8MB file, let me know if you have a difficulty downloading large files).

Please proofread the file, putting special attention to:

1. consistency of the terminology used with the last glossary http://translationstop.com/files/FTP/French_Glossary_14May.xls

2. Please repair the capitalization when necessary (first letter of first word of each special term, such as special items etc.).

3. please take care also of the 31 char abbreviation in files 7e and 7f. Please download from here http://translationstop.com/files/FTP/31.rar the two macros in one sheet you may need for that:

1. 31 char macro: Open the excel file and have it open while proofreading. Press Ctrl+Q shortcut and the macro will color all lines which contain more then 31 characters yellow.

2. In same Excel file, in cell C5 I pasted the macro which detects number of characters in the cell on it’s left. It reacts to change in number of characters as you change it/as you type. Please paste it next to the terms which were colored yellow by the first macro, and it will help you fix it quickly and precisely.

All yellow coloring and extra column with the second macro removed before delivery – it should be a clean file.

4. Additionally please pay attention that correct abbreviations are used for French:

SP (Spirit Points) – PE (Points d’Esprit) [sometimes also Spirit can be abbreviated PE, when matching the context]

AP (Attack Power) – PA (Puissance d’Attaque)

AOE (Area of Effect) – “Zone d’effet”

HP – PV

DEF – DEF

EVA – EVA

LV¢‚¬œ NV

NPC ¢‚¬œ PNJ

CritNull – echecs critiques

CritStrike / assaut critique – coups critiques

CritShield – bouclier critique

route-auto – itineraire automatique

PVP ¢‚¬œ JcJ

Please do not leave any unresolved issues. If you are not sure about something, you can contact or via CS. Any problems you think I may be able to help you with ¢‚¬œ feel free to contact me via OT or CS.

 

—————————-

 

Ok got it, thanks!

 

—————————-

 

Correction for Glossary link:

http://translationstop.com/files/FTP/French_Glossary_14May.xls

Please use only this glossary.

 

—————————-

 

Sorry I’m bombing you with so many messages, we’ve been clarifying some things.

About capitalization issues, says:

“focus on Capitalisation First Word when you are

writing something from scratch, but don’t change manually if the word is okay.

A capitalization macro can be used near the end, once everything is more consistent, and we

can do it about a few days before the end to look at it and see if it is okay.”

So please don’t mind capitalization issue if the term is correct, but if you are repairing the term, please apply the agreed capitalization then. Main focus is consistency of the terminology with the glossary.

I would appreciate if you confirmed when you receive my messages.

Thank you.

 

—————————-

 

We’ve been clarifying some issues about capitalization.

About capitalization issues, says:

“focus on Capitalisation First Word when you are

writing something from scratch, but don’t change manually if the word is okay.

A capitalization macro can be used near the end, once everything is more consistent, and we

can do it about a few days before the end to look at it and see if it is okay.”

So please don’t mind capitalization issue if the term is correct, but if you are repairing the term, please apply the agreed capitalization then. Main focus is consistency of the terminology with the glossary.

I would appreciate if you confirmed when you receive my messages.

Thank you.

 

—————————-

 

I am not dealing with accounting any more. I have prepared some data for and he is finishing rest of accounting now.

I will forward your letter to him, and please contact for further clarifications directly.

 

—————————-

 

I did receive your two messages and am about to download all the files you assigned me as well as the final JD glossary.

I will get over the instructions again before I get started and will let you know if I think I can’t finish on time or if I run into any problem.

 

—————————-

 

Did you receive 2 update messages – 1 about capitalization and other about most updated glossary?

Please let me know.

 

—————————-

 

I did receive your messages, yes, thanks!

 

—————————-

 

and I are proofreading JD files. We would like to know if you are available to help us.

If already contacted you and assigned you files to work on, please disregard this message. Otherwise, contact me as soon as possible and I will assign you files.

So far, here is the battle plan.

Improve terminology consistency throughout the whole files.

updated the glossary, you can download it on your CS page (French_Glossary_Merged2).

We need to be extremely careful regarding consistency, we will therefore follow blindlye the glossary. Please check all terms against the glossary to ensure maximum consistency. If you encounter terms that do not appear in the glossary, contact me and I will try to help you.

Improve the quality of the translation

Some files were just poorly translated, some translators did not care and we have to fix their mess now. Please make sure that the translation sounds fluent in French. If it does not make sense to you, chances are it won¢‚¬„¢t make sense to the gamers either. Be extra careful with verb agreements and spelling, there are many errors to fix. When spellchecking the files, I will strongly encourage you to copy the B column (the translation column) onto an empty Word document and to spellcheck with Word, since it seems to pick up more errors than Excel.

Regarding capitalization, confirmed that item names do not have to be capitalized.

Place names and character names have to be capitalized however.

For example: Le Seigneur Wudu a laisse l¢‚¬„¢epee de brillance dans la Tour d¢‚¬„¢Epee Verite. ‚»

Also, remember to always write a report for the files you proof.

We will first focus on files that were not proofread in the first place and then move on to proofread files that need massive overhaul.

If you have ideas on how to speed up the whole process, please let me know.

I think I covered all the bases, but if you have questions, please let me know.

 

—————————-

 

and I are proofreading JD files. We would like to know if you are available to help us.

If already contacted you and assigned you files to work on, please disregard this message. Otherwise, contact me as soon as possible and I will assign you files.

So far, here is the battle plan.

Improve terminology consistency throughout the whole files.

updated the glossary, you can download it on your CS page (French_Glossary_Merged2).

We need to be extremely careful regarding consistency, we will therefore follow blindlye the glossary. Please check all terms against the glossary to ensure maximum consistency. If you encounter terms that do not appear in the glossary, contact me and I will try to help you.

Improve the quality of the translation

Some files were just poorly translated, some translators did not care and we have to fix their mess now. Please make sure that the translation sounds fluent in French. If it does not make sense to you, chances are it won¢‚¬„¢t make sense to the gamers either. Be extra careful with verb agreements and spelling, there are many errors to fix. When spellchecking the files, I will strongly encourage you to copy the B column (the translation column) onto an empty Word document and to spellcheck with Word, since it seems to pick up more errors than Excel.

Regarding capitalization, confirmed that item names do not have to be capitalized.

Place names and character names have to be capitalized however.

For example: Le Seigneur Wudu a laisse l¢‚¬„¢epee de brillance dans la Tour d¢‚¬„¢Epee Verite. ‚»

Also, remember to always write a report for the files you proof.

We will first focus on files that were not proofread in the first place and then move on to proofread files that need massive overhaul.

If you have ideas on how to speed up the whole process, please let me know.

I think I covered all the bases, but if you have questions, please let me know.

 

—————————-

 

I uploaded my report. Hope this helps.

All the

—————————-

 

already assigned me some files. (7efhi)

I started working on them today and I am writing down all the terms that I couldn’t find in the glossary (and therefore ended up choosing a possible translation by deduction) or that needed to be shortened (I put my suggestions down) so that I can send you the document once I have finished proofreading one file.

It does take an awful lot of time though, to check every single term and I am afraid I won’t be able to finish the four files assigned me by tomorrow evening GMT. I’ll do my best and see how I get on with it.

Thanks

 

—————————-

 

Thank you for letting me know. It is a time-consuming process, but this is the best way to ensure consistency. Do not hesitate to contact me if you have questions.

When you are done with your files, do not upload them yet, since you might need to change some terms later on.

 

—————————-

 

your idea (sorting alphabetically) is good, I also found some inconsistencies this way. I also found some longer sentences that are grammatically wrong, but overall, there were not too many issues.

I have now skimmed over 5a, 2a, and 2d; and copied all problems to a separate document. I wasn’t sure whether it makes sense to edit the xls files directly, because I was not sure which ones you were already processing?

Also, I wonder if some of the problems have spread over the whole project via automatic pretranslation, fuzzy suggestions etc.

So I was wondering if the following would make sense instead of editing each xls file separately:

Creating a new spreadsheet into which the ENG and GER terms or segments are copied, into columns A and B, with the new German version in column C, and a comment in note D. This could be done very quickly, one would actually just select the two cells in excel and copy them over to the new sheet, and add the other info.

This way, we could collect our corrections first, add to the list as we go through each file, and then, in a final search and replace fest, apply these changes to all the identical passages in the whole project. Also, we wouldn’t have to look for the same problem twice, if we find it again in different files.

What do you think?

 

—————————-

 

I have processed 4b and 4c so far and found some inconsitencies and three character limitation problems. Your spreadsheet idea is fab as it sharpens the view for issues that are likely to occur in all the files.

The thing is I am not sure we can do this for all files as there is hardly enough time to do so (that’s at least what I assume). However, this would mize issues and inconsistencies and maximize our chances for BOI and potentially following projects so we should go ahead with your idea.

said he could combine all the files to make global search easier. Having both a list of mistakes and all files combined, we could easily sort out everything by search and replace (even though we must make sure that everything remains conjugated correctly!!!)

 

—————————-

 

I just wanted to let you know that I won’t be able to finish proofreading the four files you assigned me. I have been working for a few hours now and I am not even half way through the first file 7e. The process of checking every single term in the glossary is extremely slow and I can’t think of a way to make it faster.

I will also have to get in touch with once I am done with the first file as there are a lot of terms I need confirmation on after I had to shorten them or couldn’t find them in the glossary.

So I am afraid this is going to take a while.

 

—————————-

 

Sorry I forgot to mention that I won’t be able to finish proofreading the files byGHT. I will carry on working on them in the coming days unless you tell me not to.

 

—————————-

 

this is just to inform you that I’m back from vacation and ready to take over dictionary work. Can you send me the latest excel or transit version of the current BOI glossary?

 

—————————-

 

I have just finished proofreading file 7e. It took me nearly 8 hours. There are still a lot of terms in the glossary that are longer than 31 char. and others that had no corresponding entries in the glossary.

I created a word document with all the changes I made that might need confirmation. It is quite long. How do you want me to send it to you?

Also, you said I shouldn’t send the file to you straight away. Are there other changes you want me to make on that file?

 

—————————-

 

I checked 7e, and since this is an item list, proofreading can be a long task to perform.

Do you use the “Replace” function? This might save a lot of time. If you do, please make sure to tick “Match case” under options. When replacing a term that is similar in English, highlight the translation column so that changes do not affect the English texT

Did the file require a lot of modifications? It looks like there should be a lot of pretranslation in there.

If you want me to check your Word document, please upload it on the CS. Just let me know how you named it. Feel free to contact me if you have questions.

 

—————————-

 

I uploaded the document on CS. It is called Proofreading Final JD 7e.

I didn’t use the ‘replace’ option you mentioned but I might have a chance to speed up the process a bit by trying that on the next file.

Also, I just realised recommended I use Glossary14may. Is this the same one you and told me about in your last messages?

Let me know what you think about the changes I made on 7e.

Thanks

 

—————————-

 

I am checking your notes, I will get back to you within 30 minutes.

JM

 

—————————-

 

How is progress? I saw you uploaded 7e already. Did you make the abbreviation work on the file?

I imagine files 7e and 7f are longest since it’s all terminology. Other two files are normal text.

We are relocating communication to OT to Z_Get category so that could be updated of the progress and answer your questions (may you have any) when I’m offline. Please open a ticket there and mention in the ticket title that the ticket is concerning JD French.

When do you think it could be completed?

 

—————————-

 

I just reviewed your notes. Since you are using the glossary as reference, your suggestions are fine.

For segment 147, for example, you wrote that “Skywalk Boots” does not have en entry in the glossary, which is technically correct. But in the glossary, “Skywalk” is consistently translated as “voie celeste”, so you can safely assume that “Skywalk Boots” is “Bottes de voie celeste”.

When you cannot find a whole set of words in the glossary, search the different words separately to get a better idea of the translation to use.

if you cannot find a translation for any of the terms, send me your suggestions and I will help you.

Regarding the Replace function, it will save you time, but be careful not to change words that do not need to be replaced. For example, if you decide to replace “Arc” by “Arbalete”, tick the match case box under “Options” otherwise all the “arc” will become “arbalete” in the file. For example, “mARCher” will become “mARBALETEher”. I hope you get the picture.

For the character limitation, you should ask, he will probably be more helpful than me.

Again, do not hesitate to contact me if you have questions and let me know how things work with the Replace function.

JM

 

—————————-

 

I finished proofreading file 7e (basically an item list) and had to shorten several terms or make decisions when there were no entries in the glossary.

So I created a word document with all the changes I made that might need confirmation. I uploaded it on the CS under the name Proofreading Final JD 7e and asked to have a look at it. He says it looks ok but that I should ask you about the abbreviations.

Could you check it to let me know if I can send it to ? Where should I upload it?

Also, recommended I use the glossary14May and I think and you mentioned another glossary. Is it alright if I carry on working with the 14May glossary?

 

—————————-

 

Just wondering: have any new files been sent out yet?

I have not received any and wanted to let you know that I’m still available.

 

—————————-

 

We got green light to continue German for BOI. is handling it, and he will have work distributed. Please make sure you request files on Z_Get category on OT.

 

—————————-

 

told me she was using a glossary called 14 may or something.

JM and I have been using a glossary called “glossary merged 2” that we have started to update.

Would you know by any chance which one is the most complete?

With many thanks

 

—————————-

 

May 14 is the day asked you to stop adding terms, therefore it’s one or two days more updated then “Merge2”.

It can be found here: http://translationstop.com/files/FTP/French_Glossary_14May.xls

I hope there wasn’t too much difference between these versions.

 

—————————-

 

Would you please let me know how is your progress, and if you need any help. You can contact and here on CS if you have any problems and questions.

 

—————————-

 

I am back working on BOI, but I wanted to share the following with you:

jd_comments_for_.doc

uploaded here in the CS.

It contains my notes on the files I skimmed over. I just copied the segments to it that I thought were in need of fixing, but I haven’t actually fixed anything in the files. So since I hear that you are now continuing to polish JD, I thought I’d just share them with you?

 

—————————-

 

Thank you for your elaborate report on these file. I have just checked the issues you’ve come across.

 

I guess it would have been wiser if we had agreed on making the changes in the file directly, as the GS idea is only feasable if there is such a system and if there are more than one or two people working with it. Neither is the case.

Now we actually have to work on the same file twice as the corrections have not been incorporated yet.

I am really busy proofreading the next sections as Sunday is the deadline, so it would be great if you could change some of the files accordingly and upload them.

I would take file 5a and incorporate the changes.

Could you do the others?

Thank you for your help

 

—————————-

 

During working on the glossary and rep files I’ve come across inconsistencies concerning the

very similar terms

Amulet

Charm

Talisman

I was wondering whether I can take it for granted that these terms really occur in the Game and not result from previous translation mistakes (translation into English).

said that all three terms are used but in different contexts. In the rep and glossary files I worked on I handled these terms systematically in the following way:

talisman- Talisman

amulet- Amulett

charm – Glucksbringer

I think these terms should be kept consistent in one way or other throughout the whole project.

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