Comment 19 for bug 418939

Revision history for this message
Sorin Paliga (sorin-paliga) wrote :

So:
1. People commenting here basically agree with the idea that the politically-based architecture of Linux keyboard layouts is not good, and that it should be done more flexible. If this is not obvious if referring to modern, contemporary languages, it all becomes clear if we wish to add extinct and / or classical languages, which are not politically-based keylayouts, as the ones mentioned.
2. Something must be also done with (and for) such isolated keylayouts like Crimean Tartar even if, frankly, I still cannot see the argument for placing them under Romanian! (Crimean Tartar is indeed an Altaic language akin to Mongolian and to all other Altaic languages, going as far as—very probably—Korean and Japanese as a very remote expression of an easternmost expansion of the Altaic group). Note: I do not have close contacts with Tartars in Dobrudja, I once had, but—frankly—I doubt any of them, even if close to me in this moment, may be of any help here. But I assume that those who created those keylayous must have had some contacts, otherwise I cannot imagine a scenario that they put the keylayouts there without having any contact with the issue. Or am I wrong here? Or adding keylayouts in Linux is like a political dance? This problem is NOT a political one and I regret noting that, in time, Linux developers lost the initial philosophy: simple, free, flexible.
3. Adding too many variants under a basic, reference variant is not a good idea, because to many people this may be confusing. There should be 1-3 variants at the most, exceptionally more, but adding additional keylayouts should be simple and flexible, ideally Mac OS style or any similar simple method. Also, a simple to use keylayout creator, similar to UKELELE, should be implemented, together with a simple way for installing the keylayouts. THIS would solve many issues, allowing users to create / adapt existing keylayouts for specific needs.

Let us move at least one step forward with solutions. I for one have my solutions for Mac OS, am not technically competent here, but am ready to discuss and suggest methods based on what I know.