Tag Info

New answers tagged

1

To avoid a lot of problems, ensure the entire application tier from the web layer to the database uses the UTF-8 character set exclusively. On a related note, ensure Server times and all references thereof (storage, etc) are done using GMT (UTC+0). Otherwise overlaps in daylight savings times, localized references etc will likely corrupt time-stamps, logic, ...


2

Currency formats: Make sure that the currency format actually matches the currency that you are talking about! If I tell you that I had a $500 hotel bill in New York, and you translate that into German, changing the $500 bill to €500 would be a very bad idea. Translating to 500 Yen might be harmless because the Japanese readers will know that the number ...


4

You can save yourself a lot of time by knowing more about your application. First, many of the issues dealing with currency formats, number formats, measurement system, long and short date formats, long and short time formats, calendar, first day of week, and also sort order are handled by the operating system if the developer is utilizing the OS APIs ...


2

This may be something you consider "obvious", but given that it's the single most common translation problem we have, I think it's important to mention. It's less a bug, and more something that gets completely overlooked: Words often aren't used in the same order as the base language. For example: Say you want to translate Welcome, [name]. The naive ...


2

These days I fix localization bugs every day for an Android app. The most common error I encounter is corrupted keywords/variables. Examples: <![CDATA[ becomes <![CDATA [ %2$d%%\n becomes %2$d%%\n This is made worse by pre-translation software, which uses Google Translate or equivalent to provide a first shot for the translator to improve. Such ...


4

We got burned by a limited input field for income. Because I live in germany, values up to 100000 € where perfectly ok for our testers. But the website got translated for countries like russia, where 100000 rubel is not really much....


3

Typical bugs which described in many qa forums are: text expansion, resulting in truncated strings GUI alterations, resulting in overlaps of GUI elements and controls or their misalignment automatic hotkeys assignment, resulting in duplicated hotkey hard-coded strings, resulting in untranslated strings unsupported code pages, resulting in garbage missing ...


7

Some of the things I've run into: Currency formats are locale dependent. You can also have issues with different locale-based keyboards. I've seen issues where a problem only occurs when the language and the keyboard are configured for a specific locale (this was Turkish language and Turkish keyboard). For German, you'll want to watch your line breaks - ...



Top 50 recent answers are included