Angus Leeming <[EMAIL PROTECTED]> writes: > > Jean-Marc Lasgouttes <Jean-Marc.Lasgouttes <at> ...> writes: > > Enrico> my reading of it is that you need the three compilations only > > Enrico> if you want an internationalized iconv program, i.e., if you > > Enrico> want translated messages from iconv. I personally think that > > Enrico> building libiconv with --disable-nls and then LyX with > > Enrico> --with-included-gettext is sufficient. But I may be wrong > > > That seems very reasonable indeed. > > It may seem "reasonable", but that's what I did (apart from the --disable-nls > bit) and, as I mention, I get garbage instead of Russian or Polish menus. Is > the > explicit --disable-nls important? Presumably not, since libiconv's configure > will work out that it can't see a gettext.
Angus, I don't know if you solved this problem, but I just got aware of a gettext env var (OUTPUT_CHARSET) which may be related to it. I have the correct output when I start a native LyX (compiled with -mno-cygwin) as $ LANG=ru_RU /c/Programmi/LyX-1.4.0/bin/lyx-1.4.0win32 but I get garbage when I do $ OUTPUT_CHARSET=UTF-8 LANG=ru_RU /c/Programmi/LyX-1.4.0/bin/lyx-1.4.0win32 Anyway, OUTPUT_CHARSET=iso-8859-1 seems to work fine for me. Here are a couple of links which may be useful: http://www.mail-archive.com/cygwin@cygwin.com/msg37340.html http://www.linuxdocs.org/HOWTOs/Unicode-HOWTO-3.html HTH -- Enrico
