And I seriously couldn’t work without the international layout - using proper Unicode characters in my comments is just non-negotiable.
If developers would have thought more about localization, and made less dumb assumptions...
But there are even minecraft mods that don’t work on QWERTZ, because they are hardcoded to keys that are dead keys on DE layout.
Therefore in EN I can {code} and then alt+shift and {comment with proper Unicode characters}. My suggestion would be to have a setup of T1/EN. Code in EN and comment in T1.
Sorry if I'm not being clear or if I'm being confusing...
>If developers would have thought more about localization, and made less dumb assumptions...
I18N can be time-consuming. Especially to test on every conceivable keyboard layout. Dumb assumption allows the mod to exist. I'm all in favor of I18N (and help translate things when I can!) but honestly it is a lot more work for what is often very little gains.
Would you rather spend 10 hours adding I18N for 100~ players or spend 10 hours improving the rest of the code base and adding new features for 10,000 players? Most devs choose the latter. Which really sucks if you're in the group of 100~ players.
And switch EN and T1 is not very useful. I’d have to relearn blind typing completely again.
So I have æ, but not å.
Actually, I’m gonna switch to DE3.
Still doesn’t solve these special characters.