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

English Translation of French Segments in Glossary File

Thank you so much for resolving this segment – it was a great help, we were really stuck with this file.

Since we got few more days from the client, we are trying to upgrade little the rest of the files.

We have some files form the better translators we decided not to proofread due to shortage of time. But these files were translated in the very beginning of the project, and contain numerous + marks. If you are NOT proofreading now, can you take these files to resolve issues and to spellcheck them? Now I have 2-3 files of this type.

Please let me know.

 

Sorry for keeping you waiting for so long.

I was working offline and couldn’t have your message in real time. Here’s my proposal for the segment you indicated:

SOURCE SEGMENT:

Look at this place! What a pit! It figures! We leave the Divine Realm for HUNDREDS OF YEARS, and yet we SOMEHOW manage to come back JUST as the whole thing is in the middle of “gettin’ it up the giggie with a wah-wah brush.”

MY TRANSLATION:

Regardez cet endroit ! Quel aba®me ! Rien d’etonnant ! Nous quittons le royaume divin pour des centaines d’annees, et pourtant nous le retrouvons on ne sait par quel mystere, juste au moment oa¹ tout est sur le point de partir a la derive.

 

—————————-

 

Since we got few more days from the client, we are trying to upgrade little the rest of the files.

We have some files from the better translators we decided not to proofread due to shortage of time. But these files were translated in the very beginning of the project, and contain numerous + marks. If you are NOT proofreading now, can you take these files to resolve issues and to spellcheck them? Now I have 2-3 files of this type.

Please let me know.

 

—————————-

 

Right now, I am proofing 1b, and I think I can complete it later today.

You can just indicate the right file(s), and I’ll pick it (them) up as soon as I submit this one. Since we’re all rushing against tight deadlines, it would not be fair to remain idle for a long time.

My main problem is that I cannot get rid of the HYPHENS initially used by other translators, and transformed into TAGS by Transit.

I guess such details can be handled during the last but one/exportation phase…

Anyway, I available so long as we can put our hands and minds together to wrap it up.

 

—————————-

 

I am not sure we should modify the glossary at the very end of the project, it would create inconsistencies with the processed files.

The updates created were section 18 specific (spells). If you really want to modify the glossary, you should ask to care care of it by himself since he has been in charge of the glossary since the very beginning. I had no input in the glossary and I tried to follow the established glossary as much as possible whan I translated or proofed files (basically, column B of the French reduced file).

Let me know what you think.

 

1 still need to proof 18m. Did you already process 18 h i j l? sent me a glossary update for this section and I would need to change some things for the files I already sent.

After that, I will take care of 8 h i j l m n o since wants section 8 taken care of.

Okay.

18 h i j l are already processed and I am not going to pull and redo it. There isn’t time, even after the extension that miraculously procured.

In fact, let’s take a look at the glossary first, since the proofreading of section 1-5 are getting bottlenecked by the glossary. If you and can look at the glossary and give me a definite glossary, I can turn it into a dictionary file. It can even be in separate files. I can handle merging the Excel files myself. But I absolutely need a single French translation for each English term.

(A similar email has been sent to, but he hasn’t replied yet.)

Incidentally, says that “Faceless” is better translated as “anonyme” rather than “sans facette” (Any spelling error here is due to my non-existent French, not’s.)

I also notice that “Aura” is offered as a possible/new translation of “Array” and “Refuge” as a translation of “Bedlam” in the French reduced glossary. If you two can take a look at it and make sure it’s correct, great.

 

—————————-

 

I am not sure we should modify the glossary at the very end of the project, it would create inconsistencies with the processed files.

The little things like anonyme vs. sans facette can be ignored, but there are sections of the glossary that goes:

English: Bedlam Aga Armor

French1: Armure de Bedlam Aga

French2: Armure du Refuge Aga

Which one to use? The convention is that the 2nd one is the latest version. But Refuge is not a translation of Bedlam. Later on I will find sections where the 2nd one is a better translation than the 1st French translation.

One proofreader already asked me “which one to use?”

Moreover, the client wants a glossary, and we must give them a merged and paired glossary. That is, a French term (and only one) for each English term.

But if this is’s job, then I’ll email him again.

 

—————————-

 

Can you please take the time in-between files to review the glossary?

In particular, the three columns format must be reduced to two columns.

So things like:

English: Bedlam Aga Armor

French1: Armure de Bedlam Aga

French2: Armure du Refuge Aga

Must be reduced to a single translation. (By the way, why translate Bedlam into Refuge? And Array to Aura? They don’t look accurate.)

I can do the merging and also turn it into a dictionary so the other proofreaders can use it for Section 1-5. If you can get me the definite glossary in xls format, I can do it while you work on the files assigned you.

Thank you.

 

—————————-

 

I am currently working on file 18m and the translator did not respect the tag positions and added plenty of extra tags in the file. So far, I proofread 20 segments in 20 minutes. At this rate, it will take me forever to fix this file. Is there a quick and easy way to fix this mess?

Please let me know.

 

—————————-

 

I am currently working on file 18m and the translator did not respect the tag positions and added plenty of extra tags in the file. So far, I proofread 20 segments in 20 minutes. At this rate, it will take me forever to fix this file. Is there a quick and easy way to fix this mess?

There’s none. Work on some other file for now and I will see what I can do.

 

—————————-

 

Thank you for letting me know.

I moved on to files 8 h i j l m n o.

JM

 

I am currently working on file 18m and the translator did not respect the tag positions and added plenty of extra tags in the file. So far, I proofread 20 segments in 20 minutes. At this rate, it will take me forever to fix this file. Is there a quick and easy way to fix this mess?

There’s none. Work on some other file for now and I will see what I can do.

 

—————————-

 

Spent 30 minutes exporting the file to Excel so I can compare it easier with the English. My conclusion: 18m is so bad that it’s unusable.

I’ll ask to retranslate, this time paying attention to the tags. If he’s unwilling or unable, I’ll have somebody else do it.

 

—————————-

 

I have bad news. The file 18m you submitted is unusable. I can’t speak of the translation quality, but the tags are completely messed up. This won’t do. The tags tell the eventual game what font to use and where certain variables go, so the placement of the tags are critical for this project.

I believe you have used the “Hide Tags” feature of Transit. That won’t do for this project. I recommend that instead you use at least the Short Tags view during translation and Full tags view when you there’s a lot of tags.

Would it be possible to redo 18m within the next 24 hours counting from the time I hit the send button of this email? I’m sorry I can’t give you more time, but the deadline’s technically past already. Also, if I don’t hear from you within the next 12 hours, I’ll scrap your translation and have someone else translate it instead. Again, sorry for the short time, but in case you are on vacation and don’t even get to see this email, I have to have a back-up plan ready.

Please reply ASAP.

 

—————————-

 

I had just uploaded two rar files to translators files server to FTP folder -“Comments and files” subfolder.

First file is 15onspelling_issue_resolving.rar ¢‚¬œ these are the two unproofread files for spellchecking and issue resolving. When spellchecking in Excel, please mark only the French column to speed up the process (otherwise it jumps also to English).

Additionally I uploaded for_issue_resolving18il.rar, which contains 2 proofread and probably spellchecked files. In them, there are 2 small issues in each:18l in lines 27 and 78; file 18i in lines 276 and 282. Please check them, resolve the issues, but no need to spellcheck.

Thank you for help!

 

Right now, I am proofing 1b, and I think I can complete it later today.

You can just indicate the right file(s), and I’ll pick it (them) up as soon as I submit this one. Since we’re all rushing against tight deadlines, it would not be fair to remain idle for a long time.

My main problem is that I cannot get rid of the HYPHENS initially used by other translators, and transformed into TAGS by Transit.

I guess such details can be handled during the last but one/exportation phase…

Anyway, I available so long as we can put our hands and minds together to wrap it up.

 

—————————-

 

Thank you for your concern, though I was the one who made the corrections to the glossary so, obviously, if I translated Array as Aura or Bedlam as Refuge I had good reasons.

Here are the reasons why (which I already explained to and Jennifer when I organized the change)

“Array” actually refers to a specific kind of spells in the game. Either they grant the user with stat boost + inflict abnormal states to enemies who come nearby at the cost of constant SP loss (think of it as the character starts to glow, loses his SP quickly while the enemies around take damage without even being physically attacked). Or it refers to huge “magic shields” which can be set to protect an entire city.

I thought “Aura” was, in French, a better alternative to “parure”, “faisceau”, “etalage”, “ordre”, and other mistranslations scattered everywhere in the files.

Bedlam is meaningless in French with this spelling. Bedlam actually means Bethleem which is the town where JC was born. Bedlam is actually often takes the meaning of “Asylum” (for the sick) which can be translated in French as Asile or… Refuge. I also considered Sanctuary but it’s already used in WoW and I thought both games were similar enough already.

Now, maybe you have done all this research work already and have come up with better French translations for both these terms, in which case I would be happy to hear them. I already received the approval of both and Jennifer a month ago regarding these two specific corrections. I thought it was enough, but I’ll make sure to run all the glossary corrections by you from now on.

 

Can you please take the time in-between files to review the glossary?

In particular, the three columns format must be reduced to two columns.

So things like:

English: Bedlam Aga Armor

French1: Armure de Bedlam Aga

French2: Armure du Refuge Aga

Must be reduced to a single translation. (By the way, why translate Bedlam into Refuge? And Array to Aura? They don’t look accurate.)

I can do the merging and also turn it into a dictionary so the other proofreaders can use it for Section 1-5. If you can get me the definite glossary in xls format, I can do it while you work on the files assigned you.

Thank you.

 

—————————-

 

Allright, I’ll take a look and try to sorth this out.

I hope the deadline is still Sunday because I’m quickly getting completely swamped.

 

Can you please take a short time from your proofreading work and take a look at the merged glossary. I’m at a loss here.

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

Basically, I don’t think the alternative translation of Array-Aura and Bedlam-Refuge are correct. But I don’t have the expertise to decide this myself. You do.

Rather than asking everytime I run into alternatives, can you instead you go through the merged glossary and every time you run across alternates, decide which one to use, copy it to the 2nd column (if necessary), and so on. Oh, watch out for misalignment too. If there’s no alternates, just keep going. It’s only alternates we’re worried about.

Once you are done, just delete the entire 3rd column and email me. I’ll try then to convert it into a .ENU/.FRA pair that people can use as Reference Material for section 1-5.

 

—————————-

 

Thanks, I’ll send you a quick quality overview when I’m done with the proofreading.

 

I am looking for file 18q

Here:

http://translationstop.com/files/Proofreading/New.files_2/French/

The file called 18a,b,d,q actually contains a,b,d,g (which I delivered an hour ago)

Ooops. Typo. I must have misread the letter g as q. I have renamed that file and uploaded the q file. You’ll find it in the above site.

Let me know how good/bad that file is.

 

—————————-

 

Here are the reasons why (which I already explained to and Jennifer when I organized the change)

I don’t know Jennifer and if I ask you know very well he’ll just tell me to ask you. I asked first and she’s also puzzled. So it’s back to you.

(snip good reasons)

Now, maybe you have done all this research work already and have come up with better French translations for both these terms, in which case I would be happy to hear them. I already received the approval of both and Jennifer a month ago regarding these two specific corrections. I thought it was enough, but I’ll make sure to run all the glossary corrections by you from now on.

Let’s cooperate instead of fight. I know you are very busy and I’m trying to help out by doing the dictionary thing, which sparked the question. I can’t just ignore the dictionary thing, because the proofreaders of section 1-5 is taking an average of 6 hours per file, and that’s very slow and costly. They aren’t as experienced as you,. It’s going to be less frustrating for everyone if I can get the dictionary updated, and then insert everything first before sending it to them.

Now, if there is any specific thing I did that offended you, please list it so I won’t do it again.

 

—————————-

 

I checked and files from 18 section are probably not spellchecked. Can you please also sellcheck them?

If you will have time, please spellcheck these files

For Spelling FRA 18hjdg.rar

Uploaded to same place on translators server (1:/Comments and files/).

If you don’t have time – no problem, just please let me know.

Thank you.

 

—————————-

 

Files well received.

I’ll take the necessary steps for the files to be viable and ready for our client’s consumption within the defined deadlines.

 

—————————-

 

Thank you, I appreciate your effort very much.

To deliver spellchecked and issue resolved files, please open a ticket on OT (http://translationstop.com/OT/), and attach the files in the ticket. Please also write me the hours it took you to make it and the hourly rate. The system does not accept xls files, so please rar or zip them.

One more thing – please add _Spelled_ to file name after the vettors name after you finish working on the file.

Thank you!!!

 

Files well received.

I’ll take the necessary steps for the files to be viable and ready for our client’s consumption within the defined deadlines.

 

—————————-

 

Thank you, that helps alot.

I know you heard this question many times form me – but I need to know again if the files you delivered in the last days are spellchecked. No problem if they are not, but I want to know if they require this additional step before we deliver.

 

—————————-

 

OK

All well understood.

I imagine the stress you’ve been going through, handling such tremendous issues almost all alone.

Just try to relax a bit, and feel that the remainder is in good hands. I’ll try to handle it throughout the night.

I’ll be updating you in case of any trouble or difficulty, but so far so good. We’re too strong a team to let issues have the last word on us. We’ll have the last word on issues indeed.

See you soon.

 

—————————-

 

No worries, it’s just that it took us a lot of time to justify the changes to ‘s clients when I came up with the corrections so it pains me to start justifying everything again given the little time we have left before the deadline.

I wasn’t sure you were on the project at that point so I thought you were contesting the corrections after all this time. Obviously you weren’t there yet so it’s a legitimate question, my bad, I haven’t got any rest for weeks and it’s starting to get the best of me.

Things will be a lot better with the next project since everyone will be there from the beginning. Also, I think it could be great if there was a way to send you emails directly instead of going through this interface that keeps expiring on me. If there was a way to send you and CCs of the emails I exchange with it would probably keep everyone up to date more efficiently. I will talk to about this so that hopefully we can find a better way to communicate.

Allright, I am currently taking care of the glossary, I will send you the complete version in a few minutes.

Please let me know if you have further questions

 

Here are the reasons why (which I already explained to and Jennifer when I organized the change)

I don’t know Jennifer and if I ask you know very well he’ll just tell me to ask you. I asked first and she’s also puzzled. So it’s back to you.

(snip good reasons)

Now, maybe you have done all this research work already and have come up with better French translations for both these terms, in which case I would be happy to hear them. I already received the approval of both and Jennifer a month ago regarding these two specific corrections. I thought it was enough, but I’ll make sure to run all the glossary corrections by you from now on.

Let’s cooperate instead of fight. I know you are very busy and I’m trying to help out by doing the dictionary thing, which sparked the question. I can’t just ignore the dictionary thing, because the proofreaders of section 1-5 is taking an average of 6 hours per file, and that’s very slow and costly. They aren’t as experienced as you,. It’s going to be less frustrating for everyone if I can get the dictionary updated, and then insert everything first before sending it to them.

Now, if there is any specific thing I did that offended you, please list it so I won’t do it again.

 

—————————-

 

No, no spellcheck for the last files, I thought we had abandoned the spellcheck stage because of the lack of time.

I stated this in the email I sent to when I delivered the files and thought it would be enough. I will talk to him about finding a better way to communicate between the four of us because the current system is really messy.

Please let me know if you need anything else

 

Thank you, that helps alot.

I know you heard this question many times form me – but I need to know again if the files you delivered in the last days are spellchecked. No problem if they are not, but I want to know if they require this additional step before we deliver.

 

—————————-

 

I am currently working on file 18r and the English segments don’t match the French segments at some point and the remaining 3/4th of the file are thus misaligned.

Transit warns about different segment counts but doesn’t report the file as misaligned. Is there an easy way to fix this?

If you have the file at hand, the issue is between segments 450-453, then the following segments seem to be in the right order except that they are misaligned.

Please let me know if there is a way to fix this, otherwise I can try to proofread it like that.

Many thanks in advance

 

—————————-

 

Okay, I have merged column 2 and 3 and reuploaded the glossary in the CS (translator’s files – French Glossary Merged.xls)

Also, since I constantly keep track of the updates, I have uploaded the latest version of the glossary updates (recent -glossary updates.xls) It should also be added to the glossary file.

I tried to do it myself but I have no idea how to paste the third column while overwriting only the duplicates.

Anyway, please let me know if you need anything else, I will be working offline on the proofreading until tomorrow so I’ll get back to you when I log back in.

With many thanks

 

—————————-

 

Sorry for the delayed response, and for the tags mess up. Not too sure what happened, I believe the other files I did were ok.

Anyway, if you haven’t re-assigned it, I am happy to re-translate it within deadline.

Thanks

 

—————————-

 

Sorry for the delayed response, and for the tags mess up. Not too sure what happened, I believe the other files I did were ok.

Anyway, if you haven’t re-assigned it, I am happy to re-translate it within deadline.

Please redo the 18m file. I’m sorry for not replying immediately and hope you didn’t lose too much time waiting.

If you need a few more extra hours, just send me a notice. Now that I’m sure you’ll be working on it, I can wait a bit longer.

 

—————————-

 

I am currently working on file 18r and the English segments don’t match the French segments at some point and the remaining 3/4th of the file are thus misaligned.

Transit warns about different segment counts but doesn’t report the file as misaligned. Is there an easy way to fix this?

This is because the translator (or his Transit software) is trying to treat the Chinese characters as a single separate line. This causes extra segments to appear.

I’ve uploaded a fixed version at

http://translationstop.com/files/Proofreading/New.files_2/French/18_r_FRA_fixed_tobe_proofed.PXF

On the other hand the fix is actually quite simple, if a bit tedious.

When you encounter those Chinese characters, go to Options – Alignment – Start. Say yes to begin manual aligning. Place the cursor on the split segments and choose “Join Segment to Next”. Once the segments are joined, check to make sure the cell numbers match. If they do, save and reload, and continue proofreading. Repeat when you encounter the next Chinese lines. Alternatively, you can join or delete the extra segments and then from the Edit menu, mark the segment as untranslated and say yes when asked if you want to copy the whole source text. That will copy the segment from the .ENU file, tags included.

I think there’s about 8 of them, although I didn’t count for sure. It took me about 15 minutes to scan the whole file for Chinese lines and fix them.

If you’re already midway into proofing, just fix it yourself. Like I said, additional 15 minutes at most. If you haven’t started, just use the fixed version at the above link.

 

—————————-

 

Thank you very much for all your help in answering my previous questions, in a clear and simple way, very much appreciated. I’ve just uploaded the proofreading of 1d into the server.

Please find here after some comments about the translation:

I have translated “a thousand miles” by “un millier de kilometres” as I don’t think this would impair the meaning

I have translated all “LVxx” by “NVxx”

Some strings have been divided into 2 segments, but they shouldn’t have: segments 4116/4117, 4119/4120, 4199/4200, 4202/4203

From time to time, the fuzzy matches replaced the dictionary entry by its English equivalent, i.e. putting it back into English! I don’t know why, but very annoying.

Please also find here after my comments on some dictionary entries:

Ghost of Wilderness has been translated Spectre etendue sauvage, but should be Spectre etendue sauvage (accent missing)

Xxx Eloquence Hat has been translated Chapeau d’eloquence, but should be Chapeau d’eloquence (accent missing)

Xxx Scarlet xxx has been translated xxx ecarlate , but should be ecarlate (accent missing)

Xxx Fan has been translated eventail, but should be eventail (accent missing)

Equilibrium has been translated equilibre, but should be equilibre (accent missing)

Boree xxx has been translated xxx boree, but should be Plume de l’oiseau boree (accent missing)

“ame” takes an accent a¢ (a¢me)

“Supression” takes a double p (suppression)

“Tranquilite” takes a double l (Tranquillite)

“ireel(le)” takes a double r (irreel(le))

Flame Band (Recipe) has been translated (Rec.) Anneau de flame, but it should be (Rec.) Bandeau flamme

Xxx Flame Band has been translated Bandeau de flammes xxx, for consistency there shouldn’t be “de” and flame should not be plural (please check them all in the last Excel file)

Xxx Equilibrium Pinhat has been translated Couronne equilibre xxx ou Couronne d’equilibre xxx. Lack of consistency (please check them all in the last Excel file)

Some Wary xxx have been translated xxx (de) mefiance, but it should be xxx mefiante(s), for consistency with other terms

Mystic Bluewonder Stone has been translatedPierremerveille bleue myster., but it should bePierremerveille bleue mystique, for consistency with other terms

Serene Orb Tome has been translated Tome de l’orbe sereine, but it should be xxx serein, as orb is masculine in French

Hypostasis Cap Recipe has been translated Rec. Cervel. hypostase, but it should be Rec. coiffe hypostase, for consistency with other terms

Some Cap have been translated Cervelliere, but it should be Coiffe, for consistency with other terms (and for info Cerveliere does not take a double l)

Sword of Divined Order has been translated Epee d’ordre divine, but it should be xxx divin

Lack of consistency in using “de lin” or “en lin” when translating “Linen”, but I did not make any change

Ardent xxx has been translated xxx Ardent(e)(s) but should not take a capital letter

Plus other similar capital letter corrections, not documented here. Please note that not all capital letter errors have been corrected (mainly those after “Recettee¦”). Please advise if you really want me to correct them all (this would take some time tough)

Noumenon has been translated noumenon, but it should take a capital N (Noumenon) as it is a name

Moko Doctrine has been translated Doctrine moko, but it should take a capital M (Moko) as it is a name

Jino yanchee should take a capital Y (Yanchee) as it is a name

Zah wu should take a capital W (Wu) as it is a name

Kunlun 1S has been translatedKunlun1s, but it should take a capital S

Rec. chemise fluide de jade(NV75) too long, changed into Rec. chemise fluide jade(NV75)

Rec. chemise desir de gaiete(NV90) too long, changed into Rec. chem. desir gaiete(NV90)

Rec. Armure poeme fantume(NV90) too long, changed into Rec. Armure poeme fant.(NV90)

Rec.bottes parfum de paradis(NV75) too long, changed into Rec. bottes parf paradis(NV75)

Hope this helps

 

—————————-

 

No worries, I’ll get started very soon.

 

—————————-

 

I forgot to reply you about the hyphens. If they are protected by tags, and they are in the right location in the sentence – I guess they can stay that way. If not, you can temporarily disable tag protection and delete them, replacing with these 3 small circles (I don’t have them on key-board), and they will be easily replaced on vetting stage.

How is the condition of the files?

Please let me know.

 

Right now, I am proofing 1b, and I think I can complete it later today.

You can just indicate the right file(s), and I’ll pick it (them) up as soon as I submit this one. Since we’re all rushing against tight deadlines, it would not be fair to remain idle for a long time.

My main problem is that I cannot get rid of the HYPHENS initially used by other translators, and transformed into TAGS by Transit.

I guess such details can be handled during the last but one/exportation phase…

Anyway, I available so long as we can put our hands and minds together to wrap it up.

 

—————————-

 

Please find here after some comments about the translation:

I have translated “a thousand miles” by “un millier de kilometres” as I don’t think this would impair the meaning

I have translated all “LVxx” by “NVxx”

Cool.

Some strings have been divided into 2 segments, but they shouldn’t have: segments 4116/4117, 4119/4120, 4199/4200, 4202/4203

Ignore it. It’s the software thinking that the period represents the end of sentence, which usually is, except in abbreviations. We have a list of exceptions for Abbreviations, but sometimes new Abbreviations snuck up on us. It’s minor, because the export will rejoin them as long as nobody starts adding /Newlines or similar.

From time to time, the fuzzy matches replaced the dictionary entry by its English equivalent, i.e. putting it back into English! I don’t know why, but very annoying.

We have no idea why this happens too, and it’s very annoying to us. Ideally we’d love to be able to dissect the code and remove whatever it is that makes them reference the English, but that’s beyond us.

Your comment regarding French translations will be forwarded to, the lead translators. I can answer technical questions, but for the linguistic area,’s our man.

 

—————————-

 

Most of this are beyond me. Considering ‘s most recent instruction, what do you think about the capitalisation issue?

——————————————————————–

Please find here after some comments about the translation:

I have translated “a thousand miles” by “un millier de kilometres” as I don’t think this would impair the meaning

I have translated all “LVxx” by “NVxx”

Some strings have been divided into 2 segments, but they shouldn’t have: segments 4116/4117, 4119/4120, 4199/4200, 4202/4203

From time to time, the fuzzy matches replaced the dictionary entry by its English equivalent, i.e. putting it back into English! I don’t know why, but very annoying.

Please also find here after my comments on some dictionary entries:

Ghost of Wilderness has been translated Spectre etendue sauvage, but should be Spectre ’‚©tendue sauvage (accent missing)

Xxx Eloquence Hat has been translated Chapeau d’eloquence, but should be Chapeau d’’‚©loquence (accent missing)

Xxx Scarlet xxx has been translated xxx ecarlate , but should be ’‚©carlate (accent missing)

Xxx Fan has been translated eventail, but should be ’‚©ventail (accent missing)

Equilibrium has been translated equilibre, but should be ’‚©quilibre (accent missing)

Boree xxx has been translated xxx boree, but should be Plume de l’oiseau bor’‚©e (accent missing)

“ame” takes an accent ’‚¢ (’‚¢me)

“Supression” takes a double p (suppression)

“Tranquilit’‚©” takes a double l (Tranquillit’‚©)

“ir’‚©el(le)” takes a double r (irr’‚©el(le))

Flame Band (Recipe) has been translated (Rec.) Anneau de flame, but it should be (Rec.) Bandeau flamme

Xxx Flame Band has been translated Bandeau de flammes xxx, for consistency there shouldn’t be “de” and flame should not be plural (please check them all in the last Excel file)

Xxx Equilibrium Pinhat has been translated Couronne ’‚©quilibre xxx ou Couronne d’’‚©quilibre xxx. Lack of consistency (please check them all in the last Excel file)

Some Wary xxx have been translated xxx (de) m’‚©fiance, but it should be xxx m’‚©fiante(s), for consistency with other terms

Mystic Bluewonder Stone has been translatedPierremerveille bleue myst’‚©r., but it should bePierremerveille bleue mystique, for consistency with other terms

Serene Orb Tome has been translated Tome de l’orbe sereine, but it should be xxx serein, as orb is masculine in French

Hypostasis Cap Recipe has been translated Rec. Cervel. hypostase, but it should be Rec. coiffe hypostase, for consistency with other terms

Some Cap have been translated Cervelli’‚¨re, but it should be Coiffe, for consistency with other terms (and for info Cerveli’‚¨re does not take a double l)

Sword of Divined Order has been translated ue d’ordre divin’‚©, but it should be xxx divin

Lack of consistency in using “de lin” or “en lin” when translating “Linen”, but I did not make any change

Ardent xxx has been translated xxx Ardent(e)(s) but should not take a capital letter

Plus other similar capital letter corrections, not documented here. Please note that not all capital letter errors have been corrected (mainly those after “Recettea¢¢¬‚¦”). Please advise if you really want me to correct them all (this would take some time tough)

Noumenon has been translated noumenon, but it should take a capital N (Noumenon) as it is a name

Moko Doctrine has been translated Doctrine moko, but it should take a capital M (Moko) as it is a name

Jino yanchee should take a capital Y (Yanchee) as it is a name

Zah wu should take a capital W (Wu) as it is a name

Kunlun 1S has been translatedKunlun1s, but it should take a capital S

Rec. chemise fluide de jade(NV75) too long, changed into Rec. chemise fluide jade(NV75)

Rec. chemise d’‚©sir de gaiet’‚©(NV90) too long, changed into Rec. chem. d’‚©sir gaiet’‚©(NV90)

Rec. Armure po’‚¨me fant’‚’me(NV90) too long, changed into Rec. Armure po’‚¨me fant.(NV90)

Rec.bottes parfum de paradis(NV75) too long, changed into Rec. bottes parf paradis(NV75)

 

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