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; eg to have "aacute" it used to be <Multi_key> <a> <apostrophe> it now is <Multi_key> <apostrophe> <a>. Is there some reason for that?
Also, breve accent mnemotechnic char changed from <parenleft> into <b>, caron changed from <less> to <c> etc. And some combinaitions are impossible and conflictings; eg: <Multi_key> <period> <z> is defined twice, once to produce a z-dot-below, and once to produce a z-dot-above! Several combinaisons have been drop, like <Multi_key> <i> <j>, <Multi_key> <n> <g>, <Multi_key> <d> <h>,... 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 ? Thanks -- Ki ça vos våye bén, Pablo Saratxaga http://chanae.walon.org/pablo/ PGP Key available, key ID: 0xD9B85466 [you can write me in Walloon, Spanish, French, English, Italian or Portuguese]
msg01276/pgp00000.pgp
Description: PGP signature
