Re: [Texmacs-dev] Cyrillic encoding problem

[Joris van der Hoeven]

On Thu, Feb 07, 2008 at 12:39:54AM +0300, ????? ????????? wrote:
> Hello, all.
> 
>   I often use TeXmacs to write my papers.
>   I really like it! Many thanks to all developers.
>   But I have some troubles with Cyrillic encoding.
>   As far as I understand TeXmacs represents
>   cyrillic letters as unicode symbols.
>   For example, if I write "Hello!" (in russian "Privet!")
>   TeXmacs saves in tm-file the string:
>   "\<#41F\>\<#440\>\<#438\>\<#432\>\<#435\>\<#442\>!".
>   Maybe Unicode for internal representation is good but
>   it's very inconveniently for many reasons:

It is strange that things are encoded as Unicode;
in principle, Russian is encoded using the T2 encoding.
This must be a change in X. Please try to select some other
input method for Russian in the preferences

        Edit -> Preferences -> Keyboard -> Cyrillic input method

>   1) TeXmacs Hyphenation tables for russian language use TeX T2
>      encoding (very close to standard cp1251 windows encoding).
>      So it doesn't work.
>      
>   2) I can't use external editor to edit and view tm-files.
> 
>   3) I can't use spell-checker in TeXmacs.
> 
>   4) Import to Latex doesn't work. It writes empty string instead of
>      "Hello!" (in russian cp1251) but it produces valid header:
>      \usepackage[cp1251]{inputenc}
>      \usepackage[russian]{babel}
>      I also can read latex files in cp1251 encoding very well. But if I
>      save them in tm-format they store russian text in TeX T2A
>      encoding instead of unicode!
>      
> 
>   But if replace the sequence:
>   "\<#41F\>\<#440\>\<#438\>\<#432\>\<#435\>\<#442\>!" in tm-file
>   in external editor with "Hello!" (in russian in T2A
>   encoding) and read it by TeXmacs then all is OK. Hyphenation
>   works pretty good. So I deduce that TeXmacs can handle T2A encoding
>   pretty good.

Yes, things should work using the T2 encoding;
there must be a problem with the input method.
Anyway, the Russian support needs to be updated since a while.
We plan to really migrate to Unicode, but time time time...

Best wishes, Joris