Yakov Lerner <[EMAIL PROTECTED]> wrote: > On 5/17/06, Luc Hermitte <[EMAIL PROTECTED]> wrote: > > I have a problem with an old hack that works fine in latin1, but starts > > to cause problems in UTF-8. > > [...] > > What is quite odd is that I have a workaround on Linux (by calling > > iconv()) which has no, useful, effect on Windows (win32 build). > > > > The problem has existed for a long time. The iconv() workaround works > > correctly with vim 7.0.012 on linux, but not with vim 7.0.000 (default > > win32 build) on windows. > > Maybe it has to do with vaule of &scriptencoding ?
It was set to latin1 (I did not copy-paste the corresponding line in the example I've provided), and it had no effect on Windows. -- Luc Hermitte
