Joost Verburg wrote: > Angus Leeming wrote: >> This is what libiconv is meant to give us. >> It should take a .po file encoded in >> iso8859-2 and produce cp1250-encoded >> strings.
> Have you tested this? I always compile binaries with > libiconv. No, I haven't run LyX for a long, long time. However, when I last compiled LyX I did so against libiconv also and there were reports that this magic conversion was not happening. I was (am) too busy to investigate further but assumed that the problem was at my end. It seems that the problem is more subtle than just a general f**k up by the packager ;-) What is interesting here is that Uwe "resolved" the problem by repackaging the pl.po file with cp1250 encoding and that, apparently, *did* work. So the problem is definitely with (LyX's use of) libiconv. On Windows, at least. Perhaps more generally, since I suspect that Posix users don't actually leverage libiconv at all --- maybe not; what about people running pl_PL.UTF-8? Jean-Marc, perhaps this is all starting to make sense? People have reported for ever that they have problems with LyX's rendering of menus when they are running a .UTF-8 localization. Angus Regards, Angus
