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

Translation Project of Glossary Terms

Do you know what’s going on now? I contacted yesterday but he didn’t answer, is there something I can do?

Do you know when we’ll be able to start working on the next project?

 

—————————-

 

Might be useful as reference. Hopefully the French names aren’t very long, because the 31 character limit should still be in effect.

Fwd from

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

This game seems to be based on Greek mythology, or at least, the part

I am translating refers to Greek mythology.

Please remind all translators to research the name of the characters

in French, because most of the time they are different. This would

help avoid creating inconsistencies from the very beginning and would

save us time towards the end of the project.

I am very excited about this project. We learned a lot with JD and I

am sure that this time, the quality of the French files will be

excellent.

 

—————————-

 

Might be useful as reference. Hopefully the French names aren’t very long, because the 31 character limit should still be in effect.

Fwd from

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

This game seems to be based on Greek mythology, or at least, the part

I am translating refers to Greek mythology.

Please remind all translators to research the name of the characters

in French, because most of the time they are different. This would

help avoid creating inconsistencies from the very beginning and would

save us time towards the end of the project.

I am very excited about this project. We learned a lot with JD and I

am sure that this time, the quality of the French files will be

excellent.

 

—————————-

 

I’m available now, if you still need help with translation, proofreading or spell-checking

Please wait for a few days while we create the glossary first. We don’t want a repeat of last time’s glossary headache, so this time we’ll get the glossary done first.

 

—————————-

 

Thank you for keeping me up to date, very appreciated. I’m on a one-week project now, so let me know when you have more info about timelines on the new project.

 

—————————-

 

Do you know what’s going on now? I contacted yesterday but he didn’t answer, is there something I can do?

Do you know when we’ll be able to start working on the next project?

 

We are organizing now the files for the next one. Once there are files we will contact translators to distribute them.

 

—————————-

 

replied, thank you!

 

Do you know what’s going on now? I contacted yesterday but he didn’t answer, is there something I can do?

Do you know when we’ll be able to start working on the next project?

 

We are organizing now the files for the next one. Once there are files we will contact translators to distribute them.

 

—————————-

 

thanks for the info – there were more references to Egyptian mythology in my part of the glossary though, so maybe it’s a mix of both 🙂

I agree, let’s research the names anyway to produce a high quality translation.

Might be useful as reference. Hopefully the French names aren’t very long, because the 31 character limit should still be in effect.

Fwd from

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

This game seems to be based on Greek mythology, or at least, the part

I am translating refers to Greek mythology.

Please remind all translators to research the name of the characters

in French, because most of the time they are different. This would

help avoid creating inconsistencies from the very beginning and would

save us time towards the end of the project.

I am very excited about this project. We learned a lot with JD and I

am sure that this time, the quality of the French files will be

excellent.

 

—————————-

 

Hello I’m going to write you a letter now, and wait 10 minutes on my computer… Actually, I think its better to write longer letters on the computer. I usually use Word, because it has squiggly spellcheck. Anyway, I’ll keep this CS open for a while and get back to it occasionally. Maybe you have cookies blocked. You’re using Firefox? I used to use that for a long time.

 

—————————-

 

I am proofreading the glossary translation and have come across a few issues I would like to adress with you.

Firstly, I would like to ask you about hyphenation: in the guidelines to the previous project, we agreed to hyphenate the following:

Hellish Beast becomes Hullische Bestie

Hell Beast becomes Hullen-Bestie (not Hullenbestie)

Hellbeast becomes Hullenbestie (not Hullen-Bestie).

Likewise, we translated things like Celeplume as Himmelfeder, whereas Celestial Plume would become EITHER Himmlische Feder OR Himmels-Feder but NEVER Himmelsfeder

In the BOI-glossary (the new one) I find lots of deviations from this simple building rule:

Ice Resistance Eisbestandigkeit

AttackRangeAngriffsbereich

Movement Speed Fortbewegungstempo

What is the reasoning behind NOT using hyphens here? Please explain to me.

As far as I am concerned, we could agree on a rule that game-technical terms (those which will not normally appear in in-game spoken texts) need not be hyphenated, as there will probably be fewer problematic terms such as Vim Skill (Vimfahigkeit is far from being a German word, but Vim-Fahigkeit is absolutely acceptable). Otherwise I strongly recommend (for standardization and consistency) using hyphens according to the above rule.

Furthermore, Movement Speed may refer to Fortbewegung, but until you have checked that in the game and confirmed it, please try to use a more general translation (I assume this refers rather to in-combat movement speed than to run speed, but I don’t know either yet, so Bewegungs-Geschwindigkeit would be the safe translation as opposed to Fortbewegungstempo).

Please tell me your thoughts on this.

Consistency: Ice Resistance and Physical Resistance (also, e.g. attributes, translated as Eigenschaften and as Attribute, among other such examples) most probably refer to the same set of skills/attributes. Therefore, they MUST be translated consistently: Eisbestandigkeit and Physische Resistenz is NOT acceptable. Here, I would plead for Widerstand: Eis-Widerstand, Kurperlicher Widerstand, but at least it has to be the same term. Please state your thoughts.

Accuracy: Critstrike has been translated as Kritischer Schaden, while Critstrike Damage has also been translated that way. They are certainly not the same, so please try to be as accurate as possible. In the last game we decided on leaving such game-technical, made-up terms in English, if there is only a distorting German term (such as Kritschlag). We can of course discuss this, but it needs to be consistent and meaningful.

Other accuracy issues:

Herb of Light should be Licht-Kraut or Kraut des Lichts, but not Licht-Krauter

Fountain of Healing is possibly better translated as Heilungs-Brunnen, or Brunnen der Heilung than Heil-Brunnen, while Fountain of Mana refers to mana as a term for in-game power (common in many video games), so Brunnen von Mana is not as accurate as Mana-Brunnen.

Grundlegend is rarely an accurate translation for Basic when referring to concrete items, “einfach” or “Basis-” is probably better.

This is not to criticize your work but to try and achieve the highest possible quality and consistency as early in the project as possible, because this will help all of us making less avoidable mistakes and take a great load of the proofreading budget. This message goes to all three translators who have worked on the glossary, so not all of the above may apply to you.

 

—————————-

 

I am proofreading the glossary translation and have come across a few issues I would like to adress with you.

Firstly, I would like to ask you about hyphenation: in the guidelines to the previous project, we agreed to hyphenate the following:

Hellish Beast becomes Hullische Bestie

Hell Beast becomes Hullen-Bestie (not Hullenbestie)

Hellbeast becomes Hullenbestie (not Hullen-Bestie).

Likewise, we translated things like Celeplume as Himmelfeder, whereas Celestial Plume would become EITHER Himmlische Feder OR Himmels-Feder but NEVER Himmelsfeder

In the BOI-glossary (the new one) I find lots of deviations from this simple building rule:

Ice Resistance Eisbestandigkeit

AttackRangeAngriffsbereich

Movement Speed Fortbewegungstempo

What is the reasoning behind NOT using hyphens here? Please explain to me.

As far as I am concerned, we could agree on a rule that game-technical terms (those which will not normally appear in in-game spoken texts) need not be hyphenated, as there will probably be fewer problematic terms such as Vim Skill (Vimfahigkeit is far from being a German word, but Vim-Fahigkeit is absolutely acceptable). Otherwise I strongly recommend (for standardization and consistency) using hyphens according to the above rule.

Furthermore, Movement Speed may refer to Fortbewegung, but until you have checked that in the game and confirmed it, please try to use a more general translation (I assume this refers rather to in-combat movement speed than to run speed, but I don’t know either yet, so Bewegungs-Geschwindigkeit would be the safe translation as opposed to Fortbewegungstempo).

Please tell me your thoughts on this.

Consistency: Ice Resistance and Physical Resistance (also, e.g. attributes, translated as Eigenschaften and as Attribute, among other such examples) most probably refer to the same set of skills/attributes. Therefore, they MUST be translated consistently: Eisbestandigkeit and Physische Resistenz is NOT acceptable. Here, I would plead for Widerstand: Eis-Widerstand, Kurperlicher Widerstand, but at least it has to be the same term. Please state your thoughts.

Accuracy: Critstrike has been translated as Kritischer Schaden, while Critstrike Damage has also been translated that way. They are certainly not the same, so please try to be as accurate as possible. In the last game we decided on leaving such game-technical, made-up terms in English, if there is only a distorting German term (such as Kritschlag). We can of course discuss this, but it needs to be consistent and meaningful.

Other accuracy issues:

Herb of Light should be Licht-Kraut or Kraut des Lichts, but not Licht-Krauter

Fountain of Healing is possibly better translated as Heilungs-Brunnen, or Brunnen der Heilung than Heil-Brunnen, while Fountain of Mana refers to mana as a term for in-game power (common in many video games), so Brunnen von Mana is not as accurate as Mana-Brunnen.

Grundlegend is rarely an accurate translation for Basic when referring to concrete items, “einfach” or “Basis-” is probably better.

This is not to criticize your work but to try and achieve the highest possible quality and consistency as early in the project as possible, because this will help all of us making less avoidable mistakes and take a great load of the proofreading budget. This message goes to all three translators who have worked on the glossary, so not all of the above may apply to you.

 

—————————-

 

I am proofreading the glossary translation and have come across a few issues I would like to adress with you.

Firstly, I would like to ask you about hyphenation: in the guidelines to the previous project, we agreed to hyphenate the following:

Hellish Beast becomes Hullische Bestie

Hell Beast becomes Hullen-Bestie (not Hullenbestie)

Hellbeast becomes Hullenbestie (not Hullen-Bestie).

Likewise, we translated things like Celeplume as Himmelfeder, whereas Celestial Plume would become EITHER Himmlische Feder OR Himmels-Feder but NEVER Himmelsfeder

In the BOI-glossary (the new one) I find lots of deviations from this simple building rule:

Ice Resistance Eisbestandigkeit

AttackRangeAngriffsbereich

Movement Speed Fortbewegungstempo

What is the reasoning behind NOT using hyphens here? Please explain to me.

As far as I am concerned, we could agree on a rule that game-technical terms (those which will not normally appear in in-game spoken texts) need not be hyphenated, as there will probably be fewer problematic terms such as Vim Skill (Vimfahigkeit is far from being a German word, but Vim-Fahigkeit is absolutely acceptable). Otherwise I strongly recommend (for standardization and consistency) using hyphens according to the above rule.

Furthermore, Movement Speed may refer to Fortbewegung, but until you have checked that in the game and confirmed it, please try to use a more general translation (I assume this refers rather to in-combat movement speed than to run speed, but I don’t know either yet, so Bewegungs-Geschwindigkeit would be the safe translation as opposed to Fortbewegungstempo).

Please tell me your thoughts on this.

Consistency: Ice Resistance and Physical Resistance (also, e.g. attributes, translated as Eigenschaften and as Attribute, among other such examples) most probably refer to the same set of skills/attributes. Therefore, they MUST be translated consistently: Eisbestandigkeit and Physische Resistenz is NOT acceptable. Here, I would plead for Widerstand: Eis-Widerstand, Kurperlicher Widerstand, but at least it has to be the same term. Please state your thoughts.

Accuracy: Critstrike has been translated as Kritischer Schaden, while Critstrike Damage has also been translated that way. They are certainly not the same, so please try to be as accurate as possible. In the last game we decided on leaving such game-technical, made-up terms in English, if there is only a distorting German term (such as Kritschlag). We can of course discuss this, but it needs to be consistent and meaningful.

Other accuracy issues:

Herb of Light should be Licht-Kraut or Kraut des Lichts, but not Licht-Krauter

Fountain of Healing is possibly better translated as Heilungs-Brunnen, or Brunnen der Heilung than Heil-Brunnen, while Fountain of Mana refers to mana as a term for in-game power (common in many video games), so Brunnen von Mana is not as accurate as Mana-Brunnen.

Grundlegend is rarely an accurate translation for Basic when referring to concrete items, “einfach” or “Basis-” is probably better.

This is not to criticize your work but to try and achieve the highest possible quality and consistency as early in the project as possible, because this will help all of us making less avoidable mistakes and take a great load of the proofreading budget. This message goes to all three translators who have worked on the glossary, so not all of the above may apply to you.

 

—————————-

 

Thank you for keeping me up to date, very appreciated. I’m on a one-week project now, so let me know when you have more info about timelines on the new project.

You’ll be free until Friday, maybe even Sunday. We seem to be going at 20 files/day out of 100. Later parts seem to be more difficult, hence the Sunday.

 

—————————-

 

Hmmm, maybe I may as well ask you to translate a short file too. About 2000 words.

http://translationstop.com/files/BOI/French/02_glossary_French.PXF

 

—————————-

 

Firstly, I would like to ask you about hyphenation: in the guidelines to the

(…)

Very good to know. I wasn’t aware of this distinction, so my strategy so far was to hyphenate as much as possible (even Hellbeast – Hullen-Bestie). None of the terms you mention here were translated by me (I think), but I will keep this in mind for the future.

As far as I am concerned, we could agree on a rule that game-technical terms

(those which will not normally appear in in-game spoken texts) need not be

hyphenated, as there will probably be fewer problematic terms such as Vim

Skill (Vimfahigkeit is far from being a German word, but Vim-Fahigkeit is

absolutely acceptable).

I think hyphenation should be used for all noun+noun combinations, even technical terms such as Vim-Fahigkeit, unless they are common German words (e.g. I remember translating Snow Bear as “Schneebar”. Even if this isn’t a real German word, it is close enough to “Eisbar” to be acceptable, I think).

Even if we hyphenate more often than is *required* by german spelling rules, it will be easier to read for the player (at a glance), and consistent with the rest of the game. Long words composed of multiple nouns can be very difficult to read, especially on screen.

I guess a bit of analytic/theoretical thinking could also be useful here: Vim-Fahigkeit contains two different concepts that are both important: “Vim”, as opposed to other factions, and “Fahigkeit”, as a game-mechanical concept.

But a fantasy name like “Schneebar” is acceptable, in my opinion: it is a type of animal, but neither the snow-part nor the bear-part are important enough to be emphasized by way of separating and capitalizing them. Unless there are also Eis-Baren and Frost-Baren: In this case, one should use Schnee-Bar, to differentiate the different types of bears.

Just a few thoughts. This may be too complicated to be an “official guideline” for the project.

Furthermore, Movement Speed may refer to Fortbewegung, but until you have

checked that in the game and confirmed it, please try to use a more general

translation (I assume this refers rather to in-combat movement speed than to

run speed, but I don’t know either yet, so Bewegungs-Geschwindigkeit would

be the safe translation as opposed to Fortbewegungstempo).

Please tell me your thoughts on this.

Agreed.

Consistency: Ice Resistance and Physical Resistance (also, e.g. attributes

translated as Eigenschaften and as Attribute, among other such examples)

most probably refer to the same set of skills/attributes. Therefore, tMUST be translated consistently: Eisbestandigkeit and Physische Resistenz is

NOT acceptable. Here, I would plead for Widerstand: Eis-Widerstand

Kurperlicher Widerstand, but at least it has to be the same term. Please

state your thoughts.

I used “Kurperlich” for “Physical”, because I found it fitting in light of the dichotomy between Physical and Magical that I inferred from my portion. I think it is a much better choice than “Physisch”.

“Widerstand” was used in the last project, so I think we should stick with it, although personally, I like “Resistenz” better.

Accuracy: Critstrike has been translated as Kritischer Schaden, while

Critstrike Damage has also been translated that way. They are certainly not

the same, so please try to be as accurate as possible. In the last game we

decided on leaving such game-technical, made-up terms in English, if there

is only a distorting German term (such as Kritschlag). We can of course

discuss this, but it needs to be consistent and meaningful.

I suggest leaving Critstrike in English (as a technical term), but obviosly, Damage is Schaden. So “Critstrike”, and “Critstrike-Schaden” (with a hyphen 🙂 ) OR “Kritischer Schaden”. But NOT “Kritschlag”.

(…)

Grundlegend is rarely an accurate translation for Basic when referring to

concrete items, “einfach” or “Basis-” is probably better.

I had multiple terms with Basic, Medium, Advanced, Super OR Supreme. I am not sure whether they all belong to the same scale, but we should nevertheless translate them consistently. My suggestion is

Basic = Einfach

Medium = Mittel

Advanced = Besser (NOT Fortgeschritten!!!)

Super = difficult. I left it as “Super” so far, although I find that anti-atmospheric.

Supreme = I translated this as “Edel” at least once, which is a very free translation, but there is no satisfactory direct translation (i.e. an adjective) which I am aware of(?).

This is not to criticize your work but to try and achieve the highest

possible quality and consistency as early in the project as possible

because this will help all of us making less avoidable mistakes and take a

great load of the proofreading budget. This message goes to all three

translators who have worked on the glossary, so not all of the above may

apply to you.

Thank you very much for taking the time to write this and discuss it. I joined the last project only after the glossary stage, and many things have never been so carefully discussed (not that I am aware of, and I DID read the instruction files). When trying to find the best translations for important terms, I was often confused, and had to search and guess a lot. Also, I never got feedback from proofreaders, although I always tried to send in comments about terms I wasn’t sure about. So I guess my translations were acceptable most of the time, but it is hard to imagine that everything was perfect. So please continue to send feedback!

So I am very open for more discussion, and I hope that we will have a very good glossary this time, and also a seperate file with instructions on hyphenating and other stylistic issues. I also think a list with the most important game terms (skills, attributes, combat-related values etc.), compiled seperately, might help everybody to be aware of the few dozen terms that must not, under ANY circumstances, be translated inconsistently.

 

—————————-

 

I am proofreading the glossary translation and have come across a few issues I would like to adress with you.

Firstly, I would like to ask you about hyphenation: in the guidelines to the previous project, we agreed to hyphenate the following:

Hellish Beast becomes Hullische Bestie

Hell Beast becomes Hullen-Bestie (not Hullenbestie)

Hellbeast becomes Hullenbestie (not Hullen-Bestie).

Likewise, we translated things like Celeplume as Himmelfeder, whereas Celestial Plume would become EITHER Himmlische Feder OR Himmels-Feder but NEVER Himmelsfeder

In the BOI-glossary (the new one) I find lots of deviations from this simple building rule:

Ice Resistance Eisbestandigkeit

AttackRangeAngriffsbereich

Movement Speed Fortbewegungstempo

What is the reasoning behind NOT using hyphens here? Please explain to me.

As far as I am concerned, we could agree on a rule that game-technical terms (those which will not normally appear in in-game spoken texts) need not be hyphenated, as there will probably be fewer problematic terms such as Vim Skill (Vimfahigkeit is far from being a German word, but Vim-Fahigkeit is absolutely acceptable). Otherwise I strongly recommend (for standardization and consistency) using hyphens according to the above rule.

Furthermore, Movement Speed may refer to Fortbewegung, but until you have checked that in the game and confirmed it, please try to use a more general translation (I assume this refers rather to in-combat movement speed than to run speed, but I don’t know either yet, so Bewegungs-Geschwindigkeit would be the safe translation as opposed to Fortbewegungstempo).

Please tell me your thoughts on this.

Consistency: Ice Resistance and Physical Resistance (also, e.g. attributes, translated as Eigenschaften and as Attribute, among other such examples) most probably refer to the same set of skills/attributes. Therefore, they MUST be translated consistently: Eisbestandigkeit and Physische Resistenz is NOT acceptable. Here, I would plead for Widerstand: Eis-Widerstand, Kurperlicher Widerstand, but at least it has to be the same term. Please state your thoughts.

Accuracy: Critstrike has been translated as Kritischer Schaden, while Critstrike Damage has also been translated that way. They are certainly not the same, so please try to be as accurate as possible. In the last game we decided on leaving such game-technical, made-up terms in English, if there is only a distorting German term (such as Kritschlag). We can of course discuss this, but it needs to be consistent and meaningful.

Other accuracy issues:

Herb of Light should be Licht-Kraut or Kraut des Lichts, but not Licht-Krauter

Fountain of Healing is possibly better translated as Heilungs-Brunnen, or Brunnen der Heilung than Heil-Brunnen, while Fountain of Mana refers to mana as a term for in-game power (common in many video games), so Brunnen von Mana is not as accurate as Mana-Brunnen.

Grundlegend is rarely an accurate translation for Basic when referring to concrete items, “einfach” or “Basis-” is probably better.

This is not to criticize your work but to try and achieve the highest possible quality and consistency as early in the project as possible, because this will help all of us making less avoidable mistakes and take a great load of the proofreading budget. This message goes to all three translators who have worked on the glossary, so not all of the above may apply to you.

 

First of all, thanks for your thoughts on my translation. I think this will definitely help me to improve and to avoid mistakes in the future.

As for hyphenation, the rule you mentioned makes sense to me especially with regard to consistency. Unfortunately the agreement on this rule never reached me. So far I have almost always used hyphens for compound nouns. I only skipped the hyphen when the word looked more natural without than with a hyhen (as in Himmelsfeder).

I’ll stick to this rule in future translations and I think that this will make things less difficult.

I have spent a lot of time playing this game to gain a deeper understanding of the game and I must agree with your suggestions (Begewgungstempo, Mana-Brunnen)

As far as consistency is concerned, it is sometimes difficult to stick with one translation of a term that has dozens especially with compound nouns where one translation might be more appropriate in one linguistic context but not in another. However, I see how important it is to keep consistent with terminology to maintain full comprehension and logic. Hence, I’ll try to focus on that rather than absolute lingusitsic appropriateness.

This is of course especially difficult with words/phrases that are difficult to translate as Critstrike/Critstrike Damage. Maybe one could leave Critsrtike as it is and would have a term like Critstrike-Schaden then, which is consistent and plausible.

As for accuracy, the singular-plural-mixup was of course my mistake and absolutely avoidable! I also agree with your translation of ‘basic’.

With Heil-Brunnen and Heilungs-Brunnen I would still opt for the former as it sounds more German I think.

As I said, your thoughts were very helpful and will help me avoid these issues in future translations to keep the standard as high as possible.

 

—————————-

 

thank you for your very valuable comments and views. I will integrate your input into an update of the guidelines as soon as I can and also inform you of changes/adjustments made to the glossary and dictionary based on our discussion here.

 

—————————-

 

thank you for your very valuable comments and views. I will integrate your input into an update of the guidelines as soon as I can and also inform you of changes/adjustments made to the glossary and dictionary based on our discussion here.

 

—————————-

 

thank you very much for your feedback. You are absolutely right to tell us things like that, I don’t see that as criticism, because sometimes you gt into a routine that leads to not thinking about things anymore.

As far as I’m concerned, I’d like to say the following:

I hyphenated most noun-noun compounds, I admit sometimes I used compounds like, I can’t think of a good example right now, something like Himmelsfeder, because the hyphenated version seemed to be ugly and ridiculous. But you are right I will hyphenate all noun-noun compounds in the future. But I will not use hyphens for adjective-noun compounds like Hullische Bestie, I think a hyphen would not be acceptable in these cases.

Consistency: I used the word Widerstand for Resistance, it seems the best translation.

Accuracy: I used Critstrike and translated basic by einfach

Thanks again for your feedback and I appreciate your comments.

 

—————————-

 

I just uploaded section 3. I left a few ‚« + ‚» in the text to mark terms I was unsure of. Some of the English words seemed to be the contraction of two words that I could not always recognize for sure ( Gleameade, Magiclighteade, Holylighteade, CelCrystale, Fantseae).

For these, the translation should be okay, but somebody else might have a better idea.

There are also a few terms I am really unsure about and some terms that were so abbreviated due to the 31-character limitation that I want to be sure still make sense to other people.

Altogether, there are about 12 +e signs.

This is nothing major, but it might be wise to have somebody look into that to avoid errors and inconsistencies later in the project.

As I mentioned on the OT, I am available if you have more files to translate.

JM

 

—————————-

 

I’ve uploaded invoice for 19-23/04. I vetted files in April and now it’s May. Is it possible to receive payment for them by two invoices?

I am ready to vet files.

 

—————————-

 

Hallo

ich ubersetze gerade die Segmente 1 – 1110 vom Glossary und stose auf Satze wie:

Eliminate Evil

You have acquired a …

You have used …

Wie sieht es mit den Anreden in diesem Spiel aus? Bleibt es bei der formellen Anrede “Ihr” fur den Spieler, zwischen Spielern und gegenuber Nicht-Spieler-Charakteren, und “Du”, wenn der Spieler als Individuum angesprochen wird (soweit man das unterscheiden kann)?

Danke und Grus

 

—————————-

 

Sorry about the delay, I’m still recovering from the last crazy month.

No worries, I’ll take care of it and I’m also ready for the proofreading.

I still have a couple of things to do on the side at the same time (sample assessments and quality reports to the client regarding the last project) so I need to sort things out.

With many thanks

 

Hmmm, maybe I may as well ask you to translate a short file too. About 2000 words.

http://translationstop.com/files/BOI/French/02_glossary_French.PXF

 

—————————-

 

I’ve started translating part of the glossary for BOI and I often come across that one problem: 31 characters limit.

As I’m not always sure which segments the limit actually applies to I did not try and shorten any of the translated terms. (It is hard to tell for some segments if they are long names or short instructions)

Are there any guidelines you could give me about how to shorten translated terms (do I even have to do it or do you like to wait and make global decisions about that once the glossary is close to complete in order to avoid inconsistencies?) or about how to decide if a noun is a proper noun (apart from the obvious ones) and therefore needs a capital letter? I’m thinking about terms like “scorpion” or “angel” which are common nouns (I didn’t put any capital letters to those so far) but seem to refer to more than that in the game context.

Thanks in advance for your help

 

—————————-

 

A lot of the items in the game use the possessive to differentiate themselves from each other. E.g., Berzerker’s Helmet, Siv’s Blood, General’s Longsword.

I am uncertain how to efficiently handle it for the glossary.

Previously we just translate line by line, but it may be more effective to separate those lines into its component, getting Berzerker’s, Siv’s, General’s, and Helmet, Blood, and Longsword. I’m thinking that this will allow us to translate any combination of the component, speeding things up.

But English and German may have different rules regarding possessive. Would the above approach work?

What if I deleted the ‘s, getting Berzerker, Siv, and General instead?

 

—————————-

 

A lot of the items in the game use the possessive to differentiate themselves from each other. E.g., Berzerker’s Helmet, Siv’s Blood, General’s Longsword.

I am uncertain how to efficiently handle it for the glossary.

Previously we just translate line by line, but it may be more effective to separate those lines into its component, getting Berzerker’s, Siv’s, General’s, and Helmet, Blood, and Longsword. I’m thinking that this will allow us to translate any combination of the component, speeding things up.

But English and French may have different rules regarding possessive. Would the above approach work?

What if I delete the ‘s, getting Berzerker, Siv, and General instead?

 

—————————-

 

Took several days, but translation for the French glossary 3 is done.

http://translationstop.com/files/Proofreading/French/03_glossary_FRA_tobe_proofed.PXF

If you’re already in the middle of translating 02, go ahead and finish that one first.

 

—————————-

 

http://translationstop.com/files/BOI/French/BoI%20Items.xls

That’s the list of items in the game.

Technically we ought to have done that first, but the client didn’t send it to us until yesterday. Nevertheless, should be useful as reference.

You’ll notice that 03_glossary has a lot of items. Well, too late to go back.

I’ve also created an Items_reduced.xls, which lists the items that isn’t already in 03_glossary and without all the crap like price, etc.

That’ll be translated next.

If you want to see Items_reduced, just look in that directory. As a reference document though, it’s nowhere near as useful as the BoI Items.xls

 

—————————-

 

http://translationstop.com/files/BOI/German/BoI%20Items.xls

That’s the list of items in the game.

Technically we ought to have done that first, but the client didn’t send it to us until yesterday. Nevertheless, should be useful as reference.

You’ll notice that 03_glossary has a lot of items. Well, too late to go back.

I’ve also created an Items_reduced.xls, which lists the items that isn’t already in 03_glossary and without all the crap like price, etc.

That’ll be translated next.

If you want to see Items_reduced, just look in that directory. As a reference document though, it’s nowhere near as useful as the BoI Items.xls

 

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