> (I was just arguing against *country-only* based keymap names. That's > the whole point. I don't mind country based keymaps, if there are also > language based keymaps)
As soon as you mentioned this, I agreed. What I'm suggesting now is 2-letter national code keymaps and 3-letter linguistic code keymaps. > > I think this is a bad idea. Differentiating based on case can be > > problematic (as was pointed out). However, I would think that using > > ISO 3166 2-letter national codes and ISO 639 3-letter codes would > > work OK. Besides, most of the current entries already follow this. > > Depending on how you look at this :-) > > I've already pointed out that many of the languages (uhm, nations) you > mentioned actually use the ISO 639 two-letter code ;-) Or was it the > ISO 3166 country code? > If we don't ask the authors, we can only guess -- and guess what? My > guess is different from your guess ;-) True, but my guess leads to less work. :) Just changing the Group description of all the 2-letter files from the language name to the nation name is less than moving the file to another name. And the Group description name is reall cosmetic, but might help when someone contributes a new keymap. > I know I'll be a bit boring, but if case differentiation is a problem, > I'd go for providing new namespaces for each: nation/ and language/ > (perhaps in shorter forms of "n/" and "l/"). I'd rather not add new namespaces. > > > Of course, this would cause *major* breakage for old applications > > > which rely on one layout being there with a specific name. > > > > The only applications that should care would be the installation > > programs. > > If systems are single-user, which defeats the purpose of X network > transparency. In multi-user environments, you cannot expect every user > to use the same language in every occasion. I imagine that most X deployments are single-user. Plus I imagine that nearly all the multi-user environments (with X-terminals with no local storage) all have the same keyboard layout -- probably the same keyboard *model* as well. I think I'll write up a proposal for the patch I intend to submit. Frank _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
