And what options are available when I right click on a .zip/.postcode file? Say, perhaps I wished to uncompress it?
And what options are available when I right click on a .zip/.postcode file? Say, perhaps I wished to uncompress it?
Your programming language reserved keywords changing depending on your selected language was a big facepalm.
Searching for this problem on the web doesn't produce any valid relevant results, so the web has forgotten or maybe the horror has been plastered over.
I remember seeing the dictionary to translate between German and English function names[1], one time I googled for "Excel German translation" and Google proudly showed the Translate interace pre-filled with "English: excel / German: übertreffen"
[1] https://www.perfectxl.com/excel-glossary/what-is-excel-funct...
Where it went wrong is that as soon as you choose a language you were stuck with that. It should have been a display option.
=CERCA.VERT(B2;C2:E7;3;VERO)
[0] https://support.microsoft.com/it-it/office/cercare-valori-co... Nej.
1
2
i18n is HARD. But it's not THIS step that is hard. This is day one of i18n school. You can't translate from english terms. Just stop translating things from english, translate from a neutral key! key en-US sv-SE
num_short "No." "No."
yesno_no "No" "Nej"
yesno_yes "Yes" "Ja"I don't remember exact occurrences but I've noticed quite a few similar problems on macOS that are just the result of words being translated out of context.
On a popular forum software I used to do support for, "flag" (for moderation) was translated in French as "drapeau" for example. Which is technically correct I suppose, drapeau does mean flag, but the wavy kind of flag that countries like to use as symbols. Nothing else. And it's not a verb.
In this case, there is simply the string "zip" somewhere that is used both in some address forms and for the file type, and the translator just happened to translate the first occurrence probably without even knowing that is was also used in another context as well. Or without any means to ask the dev team to separate them into two terms. Which might not even be possible if they used too simplistic a translation system.
Translators usually just get to see the string they are translatinbg, and if they're lucky a 1 sentence explanation written by a programmer.
With no context, a "Zip file" might indeed mean a "postcode file" - perhaps it is a file for storing all the zip codes, and now it will be used for storing all the postcodes?
It doesn't help that a lot of developers probably never translated an application; when I added translations the first thing I did was translate it myself, but that's not really feasible for larger systems and/or with people who don't speak a second language well enough to actually do translations.
https://media.discordapp.net/attachments/323831494718128130/...
This is French, English, German and JavaScript all in one sentence.
Two trillion dollar company.
So, you have to understand 2 languages to understand these listings.
Oh yes, the classic "I just picked the string from my IDE's dropdown list, it was there so it's fine right?"