Translation of developer utilities themselves is the final layer of hell. I’m not hearing anybody out about this kinda stuff - after microsoft decided to TRANSLATE THE EXCEPTION MESSAGES IN .NET WITH NO WAY TO BYPASS IT making them unclear, unusable and ungoogleable, I realized what a terrible idea it is to fragment developer knowledge by language.
That’s why I always select “English (US)” when installing an OS or creating an account online. No bad or missing translation, no mangled UI because of longer words, and of course easily searchable error messages.
Yeah the only drawbacks is I later have trouble giving remote support to family members because their shit is in another language so I don’t know what does the option specifically say hahaha
Translation of developer utilities themselves is the final layer of hell. I’m not hearing anybody out about this kinda stuff - after microsoft decided to TRANSLATE THE EXCEPTION MESSAGES IN .NET WITH NO WAY TO BYPASS IT making them unclear, unusable and ungoogleable, I realized what a terrible idea it is to fragment developer knowledge by language.
Let’s just stick to a lingua franca, please.
That’s why I always select “English (US)” when installing an OS or creating an account online. No bad or missing translation, no mangled UI because of longer words, and of course easily searchable error messages.
Yeah the only drawbacks is I later have trouble giving remote support to family members because their shit is in another language so I don’t know what does the option specifically say hahaha
Yeah, that’s why unlocalize.com exists (or… existed? Dunno, seems down from here!) Or you can have used the official Microsoft Language Portal… until they removed it and replaced it with the worse https://learn.microsoft.com/en-us/globalization/reference/microsoft-language-resources (but it’s still usable, I guess…)
It’s not down for me
Yeah, it’s working now for me as well, probably just some temporary problem.