For websites, http://l20n.org seems the most natural version so far. Or is there something better?
You might want to checkout http://l10ns.org
A Localization Horror Story: It Could Happen to You
61–70 of 257 posts
Re: A Localization Horror Story: It Could Happen to You
#62Earlier quoted context omitted.
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.
Thanks for bringing back to my mind where I snatched this one up! Yep, it's Ender's Game. :) What is the meaning of the Chinese (?) symbol?
It's a japanese character (from hiragana script), and AFAIK used like this it means something like "isn't it?"/"shouldn't it?".
Re: A Localization Horror Story: It Could Happen to You
#63Earlier quoted context omitted.
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.
An amateur error perhaps but hardly limited to free software. 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…
Or the classic: http://news.bbc.co.uk/1/hi/7702913.stm
Re: A Localization Horror Story: It Could Happen to You
#64Article is from 1998 and very much out of date. Read: http://blogs.perl.org/users/aristotle/2011/04/stop-using-mak...
It is funny to have such a good article with so many comments at the end that disagree. The issue does not seem to be so clear cut.
Miyagawa makes two claims.
1. L::M::L::G enables PO-based work-flow. This is not correct except for trivial lexicons. L::M::L::G cannot parse the plural extract from the article, so it is incompatible with properly working PO emitters.
2. Maketext is used on typepad and "works really well". This claim is not backed by any evidence. The verifiable facts from the article pointing out the pluralisation problems of L::M still stand unchallenged.
Re: A Localization Horror Story: It Could Happen to You
#65Earlier quoted context omitted.
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.
Thanks for bringing back to my mind where I snatched this one up! Yep, it's Ender's Game. :) What is the meaning of the Chinese (?) symbol?
Re: A Localization Horror Story: It Could Happen to You
#66Earlier quoted context omitted.
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.
Thanks for bringing back to my mind where I snatched this one up! Yep, it's Ender's Game. :) What is the meaning of the Chinese (?) symbol?
It's a Japanese sentence ending, used to seek agreement/confirmation. Similar to "right?" or "isn't it?" in English.
Re: A Localization Horror Story: It Could Happen to You
#67I love this article, and used t send it to none-technical people all the time. <3 Sean Burke, the author
Re: A Localization Horror Story: It Could Happen to You
#68The two Turkish letters dotted and dotless i are often confused by users of poorly localised software. Wikipedia links to a murder case allegedly caused by this:
http://en.wikipedia.org/wiki/Dotted_and_dotless_I
A real horror story.
(Less seriously, Unicode has counterintuitive case-changing behaviours with those letters. If you are working outside the Turkish locale and uppercase a dotless I and then lowercase it, it gains a dot. I am curious about this design decision, since it seems like a basic error in operating a the level of glyphs rather than symbols. Or maybe the opposite.)
Re: A Localization Horror Story: It Could Happen to You
#69I wonder if it isn't better to generate the messages as an AST, and have a language generator, the back-end of a compiler really, that generates strings for each language. I'm sure there will be less edge cases that way.
/edit: wow, downvotes.
Re: A Localization Horror Story: It Could Happen to You
#70Edit: Disregard, turns out things have improved > The %g slots are in an order reverse to what they are in English. You wonder how you'll get gettext to handle that. I learned C/++ after C# and this is one thing that really got to me. String interpolation in C++ is extremely primitive, which would be fine only if more recent iterations of stdlib had something that wasn't so completely incompetent. For those who don't…
[deleted]