3 ms·
Probably an issue during localization, where someone saw "zip" and assumed it meant "zip code" and so "translated" it to "postcode". This is a perfect example o
by supermatt 3y ago
Probably an issue during localization, where someone saw "zip" and assumed it meant "zip code" and so "translated" it to "postcode". This is a perfect example of why its important to also supply the context instead of just the raw strings you need translated!
It also brings to mind a translation issue from my home country, wales, where road signs must be bilingual (english and welsh). A request was sent to a welsh translation service asking for the translation for a specific phrase. The signwriters received the response, completed the sign and it was then erected. The problem: it was an out-of-office auto-reply! https://www.snopes.com/fact-check/mistranslated-welsh-traffic-sign/ https://www.snopes.com/fact-check/mistranslated-welsh-traffi...
- coin 3y agozip doesn’t translate to postal code. ZIP does.
- supermatt 3y agoI dont think you understand how localization works. They have a localization file and they send them off to a translation service. The translation service goes through the file and translates the individual strings (or string fragments). Either the translators made a mistake, and thought it was referring to a ZIP (regardless of capitalization) and translated accordingly, or a developer used the wrong key when assembling the string references - i.e. he used the equivalent of (this is pseudocode as I dont know how they handle localizations): localize("CompressToArchive", localize("Zip"), localize("File")) - i.e. with a reference to localization of "Zip" (or ZIP, or zip - the dev likely just searched for a string that matched what he wanted to localize) instead of localize("CompressToArchive", "Zip", localize("File")) - i.e. with a string of "Zip" where the strings are defined as: CompressToArchive: Compress to %1.%2 (same for us and uk) Zip: ZIP (us) or postcode (uk) File: File (same for us and uk)