Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
> SL Baur <steve(a)vmailer.xemacs.org> writes:
>> difficult job[1] and sometimes things get missed. Other than Stefanie
>> Teufel (if I recall correctly), I don't know of anyone who reads the
>> German Linux groups.
> I do read them (Hello Holger!). Unfortunately they suffer from a low
> signal-to-jost-ratio.
O.K. Cool.
There is definitely going to be a public/pre-release made prior to
official 21.0. Instead of a goat, maybe I'll name it "Jamie and Mly
get your bitching done now instead of after the release" ... :-)
We should take the same care in translation we do with regular
announcements.
>> > In german linux groups people quite often report problems with using
>> > Xkb-Extensions of Xfree86 and XEmacs[1]. For me, this is not a real
>> > problem, since I don't use the extensions.
> I think we are talking about the dead key problems, i.e. x-compose .
> These are not really due to the Xkb-extensions but they reinforce it.
> Because of all the trouble in German linux groups Martin and I did all
> the rewriting of it.
O.K.
> At the time I sent of a lot versions of x-compose out to people to
> test including AIX and XFree86 users with both french and german
> keyboards. Unfortunately they all used 19.15 to test and there is
> slight difference between x-compose in 20.4 and that version that
> breaks it ruining all the work :-(. As far as I know these are fixed
> in 21.x
O.K.
> AFAIK the XEmacs 19.16 version should give no problems. The problem is
> that XFree86 seems to have versions using hyphens and and versions
> underscores in the keysyms (i.e, dead-tilde and dead_tilde). To add to
> that the XEmacs code remaps underscores to hyphens for keybindings,
> but x-keysym-on-keyoard-p in 20.4 wants the unremapped name.
> This is fixed 21.0. It would be very nice if somebody with a German
> linux installation (preferably something that comes directly out of a
> SUSE box), could try this out one more time before release to make
> sure we get the same debacle as in 20.4. Holger, could you find
> someone?
Yes, please. This counts as a show-stopper. Let's get this resolved
*now* rather after the release.
