Live data from Hacker News

A Localization Horror Story: It Could Happen to You

search.cpan.org

21–30 of 257 posts

Re: A Localization Horror Story: It Could Happen to You

#21
Having quite well in mind the most common problems with localization I tend to use strings like this:

Directory searched: 10. Files found: 0.

They are not shiny but a direct translation is OK in Italian and it could be OK in the other languages of the post (Chinese, Arabic and Russian).

Re: A Localization Horror Story: It Could Happen to You

#22
I've long found that "externalized" translations in po files (or any equivalent) are more trouble than they're worth, for exactly this reason. Translations need to be functions, so they need to be written in a format that's good for writing functions - i.e. a programming language. What we want is a MessageSource interface, and a bunch of language-specific implementations.

Fortunately I work in Scala, so it's very easy to have an "embedded DSL" that's ordinary, first-class code but not much harder for non-technical translators to read or write than the .po format; we can write helpers for grammatical case or numbers or similar. But having the full power of a programming languages there means that when you hit a case you haven't thought of (and you will), you can fall back to just an if/else.

Re: A Localization Horror Story: It Could Happen to You

#23
Interesting, but I am wondering if it is really worth going through all this trouble, just to support a few edge cases.

Personally, I usually don't even notice small mistakes like "1 directories" (or similar mistakes in my native language). Sometimes I will see the correct version somewhere and think "Oh, nice that they thought of that" but I definitely don't expect it.

Are the possible returns of having a "perfect" translation really high enough to justify investing in a much more complex system? I am sure translators who can code functions instead of just putting values into an Excel table will come at quite a premium as well...

Re: A Localization Horror Story: It Could Happen to You

#24
post #12
post #2

Article is from 1998 and very much out of date. Read: http://blogs.perl.org/users/aristotle/2011/04/stop-using-mak...

Should be reflected in the title, if possible, neh?

Cool example, but I think "ne" is the "correct" way to romanize ね.

Re: A Localization Horror Story: It Could Happen to You

#26
post #10

Funny how Slovene seems to tick all the complications checkboxes :D We have 4 grammatical numbers (singular, dual, plural for 3 and 4, plural for 5 and above), they repeat at mod 100 (so 101 is singular, 102 dual,…), it's an inflectional language with 3 grammatical genders, sentence should take a different form depending on whether the user is male or female,…

I was just trying to think of how it would work out in Polish.... directory is "katalog" in Polish, and it would be: 1 katalog 2 katalogi 3 katalogi 4 katalogi 5 katalogów 6 katalogów ....(it doesn't change for any number greater than 5) But if you wanted to say "X files were found in Y directories" then you would have to say: ....1 katalogu ....2 katalogach ....3 katalogach ....1000 katalogów (for 1001 even I am not…

> Compared to the grammar of Slavic languages, English is super easy.

And thus is solved the mystery all us Slavic speakers have such good English. Especially on the online. Because nobody had the guts to localize to our languages.

If they did localize to our languages "Omg this looks weird and smells off", we all cried. And switched our interfaces to English. Admit it, you did this in High School or even Middle School because the translation just didn't make sense.

And so all of us who are now in a position to localize these interfaces don't because it seems silly and pointless.

We come full circle. Younglings after us use computers in English because no good localization exists.

Re: A Localization Horror Story: It Could Happen to You

#27
post #20

Earlier quoted context omitted.

I was just trying to think of how it would work out in Polish.... directory is "katalog" in Polish, and it would be: 1 katalog 2 katalogi 3 katalogi 4 katalogi 5 katalogów 6 katalogów ....(it doesn't change for any number greater than 5) But if you wanted to say "X files were found in Y directories" then you would have to say: ....1 katalogu ....2 katalogach ....3 katalogach ....1000 katalogów (for 1001 even I am not…

1 imenik 2 imenika 3 imeniki 4 imeniki 5 imenikov 6 imenikov … 101 imenik 102 imenika 103 imeniki … 201 imenik … 1001 imenik … Slavic languages are f*d up :D

Not to mention that I would never realise that "imenik" means directory. An imenik is a phone book. Potentially the Contacts app on my phone. But never a directory.

I think this has to do with vocabulary registers as well. We've learned to use English words for computer things. Using Slovene translations just feels weird unless they're a bastardisation of the English word. Similar to how English uses French words for foods because cuisine was a thing of the elite and they didn't eat pig, they ate porc.

Re: A Localization Horror Story: It Could Happen to You

#28
post #7

Slightly OT, mi favourite localization error was in Ubuntu when they had that nice netbook interface (that later would become Unity). The network icon label was "Rojo" in the Spanish localization, that is the word for "red" color. What? Well, if you translate "Net" to Spanish you get "Red"; and if you translate that again (by mistake), you get "Rojo". There you are :)

That's an error only an amateur translator would make. Guess who makes free software translations... A professional translator makes sure to check the context of the translation, it doesn't go blindly translating sentences and words without context.

To be fair it was a beta of the "Ubuntu Netbook Remix" and that bug was shortly fixed.

I took some screenshots because I really liked the interface, but none of them show the bug because I usually stick to en_GB and the problem was spotted in my wife's netbook (she's Spanish teacher and likes to have the OS interface in Spanish to amuse the kids).

Re: A Localization Horror Story: It Could Happen to You

#29
post #6

Just in case people are wondering about the horror story: use ngettext which is a function in the gettext library.

Indeed, this is a solved problem. Use ngettext, see its page for all different language variations (even the Slovenian four different forms) https://www.gnu.org/software/gettext/manual/html_node/Plural...

How does ngettext handle "Your query matched %g files in %g directories"?

Re: A Localization Horror Story: It Could Happen to You

#30
post #10

Funny how Slovene seems to tick all the complications checkboxes :D We have 4 grammatical numbers (singular, dual, plural for 3 and 4, plural for 5 and above), they repeat at mod 100 (so 101 is singular, 102 dual,…), it's an inflectional language with 3 grammatical genders, sentence should take a different form depending on whether the user is male or female,…

Wikipedia mention only singular, dual and plural ? What is the one for 3 and 4 ?

http://en.wikipedia.org/wiki/Slovene_grammar

Post reply on HN