In order to avoid these pitfalls, usually I get out of "sentence" mode to "label" mode. For instance: "Directories scanned: 12". Probably not well suited for all cases, but usually good enough for mine, though actually I only have to support pt-BR, es-ES and en-US so maybe that's not saying much.
A Localization Horror Story: It Could Happen to You
51–60 of 257 posts
Re: A Localization Horror Story: It Could Happen to You
#52Funny 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
Re: A Localization Horror Story: It Could Happen to You
#53Funny 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,…
Re: A Localization Horror Story: It Could Happen to You
#54Slightly 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.
In a particularly expensive piece of enterprise software for the finance sector that was translated into German a form field was labelled 'Hauptstadt', which translates back into 'capital (city)' as in Washington, D.C.
Now, this kind of geographic information doesn't make sense at all in financial software but the well-paid developer (who had to double as the software's translator because hiring a proper translator would of course have been too expensive ...) simply couldn't be bothered to look up the different words 'capital' translates to in German, one of which also is the right choice in that case: 'Kapital' (meaning 'capital' as in 'asset).
Re: A Localization Horror Story: It Could Happen to You
#55Earlier quoted context omitted.
Cool example, but I think "ne" is the "correct" way to romanize ね.
If it's intended to be a romanization of ね, then yes, "ne" is more common. Alternatively it could be a reference to Ender's Game, where "neh" is used in the same way.
What is the meaning of the Chinese (?) symbol?
Re: A Localization Horror Story: It Could Happen to You
#56Re: A Localization Horror Story: It Could Happen to You
#57I did some work on bringing it to JavaScript and making it HTML-aware, and since then Santhosh Thottingal has vastly extended it and it's become pervasive at Wikipedia. More projects should use it, or at least learn from it.
Re: A Localization Horror Story: It Could Happen to You
#58Funny 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…
Re: A Localization Horror Story: It Could Happen to You
#59Earlier 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…
ICU's messageformat solves this easily. One project that supports ICU's messageformat is L10ns http://l10ns.org
Re: A Localization Horror Story: It Could Happen to You
#60I remember being hit in the head by gettext manual and told something about translators not knowing how to code.
Heck, I still think it's a neater idea than gettext.