In answer to Pablo: I find that some of the limitations regarding XIM and Compose regrettable.
Let me take a concrete example: I know a teacher of Japanese as a foreign language that wants to type texts consisting of a mixture of French and Japanese. It would be impossible for her to do this in a single application: - if she starts with XMODIFIERS="@im=kinput2", she can get the Japanese but not the French dead accents - if the starts without it, the converse problem happens. [Possible workaround: copy & paste, but this is crude!] I also noticed that if XMODIFIERS="@im=kinput2", kinput2 still does not work if the application is not launched in a ja_JP.* locale (fr_FR.UTF-8 does not work). Side note: this arises from this stupid notion that an application is launched at one time to type in a single language, which totally ignores the need for quotations or linguistic explanations. Some things I thing should change: * It should be allowed to use several XIM methods in the same application at the same time. * The locale should bear no influence on whether an input method is used. David Monniaux http://www.di.ens.fr/~monniaux Laboratoire d'informatique de l'École Normale Supérieure, Paris, France _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
