4 ms·
Back when I was making WIN32 apps (that at the time didn't have a layout manager), the hardest languages to localize for were: * German, simply because the Ger
by AndrewStephens 2y ago
Back when I was making WIN32 apps (that at the time didn't have a layout manager), the hardest languages to localize for were:
* German, simply because the German translations we were using were twice as long. I don't speak German so I couldn't judge if all those extra words were required.
* Simplified Chinese, because the default font in that language was huge - single characters would take twice the width (and more irritatingly, height) of an English character.
* Japanese, partly because the default font was also large but mostly because the multibyte character codes (this was before unicode support) for common words included bytes that were commonly used for separators in other languages. So things like backslash path seperators (which Japan didn't use) would have to be handled with extreme care in the code.
- stop50 2y agoIn german words are often concanated resulting in words like Bodenseeschifferpatent(an license to drive boats with an bigger motor or an bigger sail). When you localise something german is easily one of the longest translations,
- AndrewStephens 2y agoYep, and it is not just the overall length of the text either. At least text with lots of short words can be have flexible line breaks. I remember having to design dialogs with lots of empty space to accommodate the German translation.