Julian Bradfield writes:
Is there any thought on the future of Quail in XEmacs?
Not really. From the user point of view, most XEmacs users use
platform input methods (eg, compose keys, AltGr, etc) for non-ASCII
characters. Asian users typically have many options (eg, for Japanese
I use either Canna or Anthy), and Japanese Quail doesn't work at all
because it uses features that were introduced into GNU Emacs
specifically to support advanced features in Japanese Quail.
I only ever use Quail for the occasional accented character in
European names, so I don't know much about it. Maybe Aidan knows a
lot more, though.
I had to modify quail anyway, so I wondered: if I were to bring some
of the FSF changes into quail and isearch, would you take them up?
Yes, but there's a possible problem: for isearch in 21.4 you need to
negotiate with Vin "21.4 Gatekeeper" Shelton. I don't know if he
would admit a potentially destabilizing change, isearch is a central
feature of Emacsen. For quail and 21.5, you'll need to wait for GPLv3
versions before it can be distributed.
Should be real soon now (Jerry, Mike and Mats have done their parts),
but you know that maxim about organizations being doomed to produce
software whose structure reflects their T/O? Well, Quail is a perfect
example, and I think the model was my employer. Life sucks
XEmacs-Beta mailing list