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
