StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Our game <a href="http://www.lobstersoft.com/gemsweeper/index.php" rel="nofollow noreferrer">Gemsweeper</a> has been translated to 8 different languages. Some things I have learned during that process:</p> <ul> <li><p><strong>If the translator is given single sentences to translate, make sure that he knows about the context that each sentence is used in.</strong> Otherwise he might provide one possible translation, but not the one you meant. Tools such as <a href="http://babelfish.yahoo.com/" rel="nofollow noreferrer">Babelfish</a> translate without understanding the context, which is why the result is usually so bad. Just try translating any non-trivial text from English to German and back and you'll see what I mean. </p></li> <li><p><strong>Sentences that should be translated must not be broken into different parts for the same reason.</strong> That's because you need to maintain the context (see previous point) and because some languages might have the variables at the beginning or end of the sentence. Use placeholders instead of breaking up the sentence. For example, instead of </p></li> </ul> <blockquote> <p>"This is step" "of our 15-step tutorial" </p> </blockquote> <p>Write something like: </p> <blockquote> <p>"This is step %1 of our 15-step tutorial"</p> </blockquote> <p>and replace the placeholder programmatically. </p> <ul> <li><p><strong>Don't expect the translator to be funny or creative.</strong> He usually isn't motivated enough to do it unless you name the particular text passages and pay him extra. For example, if you have and word jokes in your language assets, tell the translator in a side note not to try to translate them, but to leave them out or replace them with a more somber sentence instead. Otherwise the translator will probably translate the joke word by word, which usually results in complete nonsense. In our case we had one translator and one joke writer for the most critical translation (English). </p></li> <li><p><strong>Try to find a translator who's first language is the language he is going to translate your software to, not the other way round.</strong> Otherwise he is likely to write a text that might be correct, but sounds odd or old-fashioned to native speakers. Also, he should be living in the country you are targeting with your translation. For example a German-speaking guy from Switzerland would not be a good choice for a German translation.</p></li> <li><p><strong>If any possible, have one of your public beta test users who understands the particular translation verify translated assets and the completed software.</strong> We've had some very good and very bad translations, depending on the person who provided it. According to some of our users, the Swedish translation was total gibberish, but it was too late to do anything about it. </p></li> <li><p><strong>Be aware that, for every updated version with new features, you will have to have your languages assets translated.</strong> This can create some serious overhead.</p></li> <li><p><strong>Be aware that end users will expect tech support to speak their language if your software is translated.</strong> Once again, Babelfish will most probably not do. </p></li> </ul> <p><strong>Edit - Some more points</strong></p> <ul> <li><p><strong>Make switching between localizations as easy as possible.</strong> In Gemsweeper, we have a hotkey to switch between different languages. It makes testing much easier. </p></li> <li><p><strong>If you are going to use exotic fonts, make sure these include special characters.</strong> The fonts we chose for Gemsweeper were fine for English text, but we had to add quite a few characters by hand which only exist in German, French, Portughese, Swedish,... </p></li> <li><p><strong>Don't code your own localization framework.</strong> You're probably much better off with an open source framework like <a href="http://www.gnu.org/software/gettext/" rel="nofollow noreferrer">Gettext</a>. Gettext supports features like variables within sentences or pluralization and is rock-solid. Localized resources are compiled, so nobody can tamper with them. Plus, you can use tools like <a href="http://www.poedit.net/" rel="nofollow noreferrer">Poedit</a> for translating your files / checking someone else's translation and making sure that all strings are properly translated and still up to date in case you change the underlying source code. I've tried both rolling my own and using Gettext instead and I have to say that Gettext plus PoEdit were way superior. </p></li> </ul> <p><strong>Edits - Even More Points</strong> </p> <ul> <li><p><strong>Understand that different cultures have different styles of number and date formats.</strong> Numbering schemes are not only different per culture, but also per purpose within that culture. In EN-US you might format a number '-1234'; '-1,234' or (1,234) depending on what the purpose of the number is. Understand other cultures do the same thing.</p></li> <li><p><strong>Know where you're getting your globalization information from.</strong> E.g. Windows has settings for CurrentCulture, UICulture, and InvariantCulture. Understand what each one means and how it interacts with your system (they're not as obvious as you might think).</p></li> <li><p><strong>If you're going to do east Asian translating, really do your homework.</strong> East-Asian languages have quite a few differences from languages here. In addition to having multiple alphabets that are used simultaneously, they can use different layout systems (top-down) or grid-based. Also numbers in east Asian languages can be very different. In the en-US you only change systems for limited conditions (e.g. 1 versus 1st), there are additional numeric considerations besides just comma and period.</p></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload