Re: Making multi-layout the default (was Re: [I18n]Farsi Keyboard Layout)
On Mon, Nov 18, 2002 at 08:45:20PM -0500, David Dawes wrote: OK, it's clear from this and other reponses that there's still a lot of open issues, many of which are definitely beyond the scope of 4.3.0 and are things we should try to solve for a later release. Would it be reasonable to change the default to the new maps (and provide a way of forcing the old ones) for the next few weeks, so that the new ones can get more exposure? We can then decide at that time whether to change the default back to the old maps before for the release. With this method we'd keep the old ones around unless we are confident by 30 Nov that we can replace them completely with the new ones. To summarise a timetable: - Change the default to the new maps now, so more people will be exposed to them. - No major structural change (like removing old maps) after 30 November - Changes accepted to maps until ~mid December - Choose which are the default (for Option XkbLayout us) by ~mid December. - Come up with a plan to address the other issues after 4.3.0. Comments? - I suggest to make a new tree where only clean stuff would go (new maps, only needed files), the current map tree should be left (preferably) as is with a reasonable 'force old' option in xfree configuration - Also a new directory/tree for 3rd party stuff would be nice - Some maps are still not all correct. Speaking for myself, cz_qwerty map is missing, for instance. Should I add it (is it used to be in 4.2.1) or not (I mean -- the role of 'variants' is not very clear now)? Your plan itself sounds very reasonable to me. That exposing may do some goodness as some apps (Java apps for example) still don't work with xkb groups - this would be more crucial with multi-layout ... Kamil ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: Making multi-layout the default (was Re: [I18n]Farsi Keyboard Layout)
To summarise a timetable: - Change the default to the new maps now, so more people will be exposed to them. - No major structural change (like removing old maps) after 30 November - Changes accepted to maps until ~mid December - Choose which are the default (for Option XkbLayout us) by ~mid December. - Come up with a plan to address the other issues after 4.3.0. Comments? No objection. I can make a patch in nearest days. But there is one issue. In existent layouts all non-latin layouts actually are two-level (two groups) maps where the first level is an US English and the second one is the national layout itself. Should I make the same defaults for the new maps (it's possible but means a lot of lines in the rules file) or let the national layout now means the layout itself and nothing more? (None that now it can be easy conbined with any other layout.) The first approach is more habitual for X users but the second one seems to me more logical. -- Ivan U. Pascal | e-mail: [EMAIL PROTECTED] Administrator of | Tomsk State University University Network | Tomsk, Russia ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: Making multi-layout the default (was Re: [I18n]Farsi Keyboard Layout)
Comments? - I suggest to make a new tree where only clean stuff would go (new maps, only needed files), the current map tree should be left (preferably) as is with a reasonable 'force old' option in xfree configuration I agree. But we talk about which ones should be default. - Also a new directory/tree for 3rd party stuff would be nice - Some maps are still not all correct. Speaking for myself, cz_qwerty map is missing, for instance. Should I add it (is it used to be in 4.2.1) or not Oh, sorry. I can't guess how I missed it. (I mean -- the role of 'variants' is not very clear now)? What is wrong with variants? I should explain. Like the XkbOption now can be a list of layiouts the XkbVariant can be a list of variants too. But since not all layouts need a variant the list can looks like XkbVariant ,,qwertz I know it seems ugly but I can't invent something better. On the other hand in most cases you can specify the variant directly with the layout XkbLayout us, cz(qwerty), ru(winkeys) (It's a rather trick becouse the variant is not necessarily a subsection of a symbols file. But in most cases it is.) -- Ivan U. Pascal | e-mail: [EMAIL PROTECTED] Administrator of | Tomsk State University University Network | Tomsk, Russia ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: Making multi-layout the default (was Re: [I18n]Farsi Keyboard Layout)
On Tue, Nov 19, 2002 at 08:38:16PM +0600, Ivan Pascal wrote: - Also a new directory/tree for 3rd party stuff would be nice - Some maps are still not all correct. Speaking for myself, cz_qwerty map is missing, for instance. Should I add it (is it used to be in 4.2.1) or not Oh, sorry. I can't guess how I missed it. Bah, no problem to add it. The only problem is where to... (I mean -- the role of 'variants' is not very clear now)? What is wrong with variants? There is nothing wrong with variants as such. Not even with maybe funny looking but perfectly logical XkbVariant list you introduced below. But (as you can see on your own example below) are mostly about some minor changes (winkeys, missing usefull keys or so) but it's not about layout changes. Maybe there is no such other braindead map as cz/cz_qwerty but it doesn't seem obvious to me. For example: cz(winkeys) looks okay, but cz_qwerty(winkeys) is also meaningful. How would this look if qwerty was a variant of cz? I should explain. Like the XkbOption now can be a list of layiouts the XkbVariant can be a list of variants too. But since not all layouts need a variant the list can looks like XkbVariant ,,qwertz I know it seems ugly but I can't invent something better. On the other hand in most cases you can specify the variant directly with the layout XkbLayout us, cz(qwerty), ru(winkeys) (It's a rather trick becouse the variant is not necessarily a subsection of a symbols file. But in most cases it is.) Kamil ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: [I18n]Unicode / 16-Bit
Is the X (4.x) supporting Unicode/16 Bit encoding ? How ? Yes, to some degree. To get started, try: http://www.cl.cam.ac.uk/~mgk25/unicode.html Markus -- Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK Email: mkuhn at acm.org, WWW: http://www.cl.cam.ac.uk/~mgk25/ ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
