On Tue, Jan 07, 2003 at 04:57:03PM +0100, Pablo Saratxaga wrote: > Kaixo! > > The new auto-generated Compose file for UTF-8 brokens backward compatibility > with previous use of Multi_key, as the order of typing is inversed;
..[snip].. > Is all that done on purpose, and the new ordering will be the final one ? > (in such case, shouldn't also the 8bit Compose files be rewritten so they > are compatible, that is, the same key combination to produce an "aacute" > in all locales having that letter) > Or could the auto-generated latin blok be rewritten so that it used the > old keystroke order for Multi_key sequences ? I'll take this a bit further: is there anyone that actually likes the current, almost completely machine generated UTF-8 Compose file? Although such an approach might at first seem to have some advantages (consistency, maintainability, etc.), in reality its shortcomings are multiple, as Pablo already pointed out. And while I can't really comment on most of the file immediately, its parts about Greek leave a lot to be desired. IMHO, writing a good Compose file takes much more than transforming some Unicode data files to key sequences. The cultural conventions of many people need to be taken into account (and sometimes they are conflicting), and it might be even necessary to design new input methods from the beginning. Not that machine-generated parts aren't needed, but they should be carefully thought out as well. The current Compose file might be more complete, but the previous one just "feels" better. It would be nice if someone could combine the best of both worlds. P.S. Although Compose/el_GR.UTF-8 is of very limited use compared to en_US.UTF-8, it illustrates most of the above opinions rather nicely. -- Vasilis Vasaitis [EMAIL PROTECTED] +30976604701 _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
