LixD icon indicating copy to clipboard operation
LixD copied to clipboard

Translate key names

Open Wuzzy2 opened this issue 6 years ago • 2 comments

Key names should be translated as well, e.g. “Delete”, “Enter”, “Space”, “Control”, “Shift”…

Wuzzy2 avatar Jun 22 '18 02:06 Wuzzy2

Interesting idea.

Translating key names isn't as straightforward as translating other string. The key names come from Allegro 5 (a library) and aren't internationalized. I'd have to write extra code here.

I prefer the English key names even when I'm talking to other Germans. But I don't know how prevalent this is. Is "Umschalt" really more understandable in German than "Shift"? Do you prefer German key names because they're clearer to you, or because you're astonished by German UI with English key names?

SimonN avatar Jun 22 '18 19:06 SimonN

The keyboard keys do have established (!) German names, they are prevalent and are printed in German names or abbreviations on the actual keyboard. So there's no excuse to keep them English on purpose. This just defeats the point of having a German translation in the first place.

Wuzzy2 avatar Jun 22 '18 22:06 Wuzzy2

I apologize for leaving you hanging here, and for having been unclear 5 years ago.

So there's no excuse to keep them English on purpose.

The excuse was not about my personal preference. I've set Lix to English.

The excuse was: It's hard to implement because neither Lix nor Allegro have easy support for key translations. I'll have to write better custom language support in Lix to get it done. And in 2018, other things had higher priority than that.

Recently, for i18n, I've looked into #335 (translating skills). When that is done and released, I can look into translating the keys.


Can I use this image as a reference for the established key names, or do you suggest other names? https://info-ag.coderdojo-saar.de/wp-content/uploads/2021/01/Screenshot-2021-01-01-at-13.36.01.png

Tab, backspace, enter: Lix shows these as arrows, e.g., ⌫ for backspace. They need no translation.

What do we do with shift and caps lock? Lix's keymapping buttons abbreviates the names to 2-5 characters when you bind mutiple keys to the same function. Should we translate "LShift", "RShift", "Caps Lock" to "LUmschalt", "RUmschalt", "Feststelltaste" and accept "LUm"/"LU" as abbreviations?

Maybe I should look for some unicode symbols, nice fat arrows, and have "L(fat up arrow)" for LShift. I think that's better if room is tight.

SimonN avatar Oct 29 '23 18:10 SimonN

The keyboard image is correct. "LUmschalt" and "RUmschalt" is also OK. But "LUm" and "LU" are bad abbreviations, nobody uses or know that.

Wuzzy2 avatar Nov 09 '23 15:11 Wuzzy2

I agree, "LUm" or "LU" don't feel appropriate, and "LUmsch" is too long for the existing system.

I'll call shift keys "L⇧" and "R⇧" with the unicode UPWARDS WHITE ARROW (U+21E7). Caps Lock can become the single symbol "⇩" (DOWNWARDS WHITE ARROW, U+21E9).

SimonN avatar Nov 09 '23 17:11 SimonN

Yes, Unicode is great (assuming the font supports these glyphs :D ).

Wuzzy2 avatar Nov 09 '23 18:11 Wuzzy2

Fixed in 0.10.17, which released today. I resorted to "⇧" instead of "L⇧".

Feel free to re-open or file new bugs if keys are wrong. I don't have German keyboards here to test, and I don't have a German-language computer setup. I'll see when I can find a German Windows machine for testing.

SimonN avatar Nov 21 '23 04:11 SimonN