Richard Heck wrote:
Paul A. Rubin wrote:
I'll skip over the forensic steps (and the "what was I drinking that
made me even think of them" part) and cut to the chase scene. My
layout file is coded (according to Notepad++) "ANSI as UTF-8". Yours
is coded UTF-8. Turns out either ANSI or "ANSI as UTF-8" works fine,
but LyX apparently can't read a non-ANSI UTF-8 layout file and keep a
straight face. (Developers are free to weigh in here with corrections
if I'm wrong.)
There's a bug report along these lines: LyX can't read non-UTF8 text
file. I think it's been addressed in a recent fix, but I'm not sure.
I'll confess I'm still a bit confused as to what actually went on with
Dave's file. Notepad++ had it marked as UTF-8. I'm not sure what the
difference between "UTF-8" and "ANSI as UTF-8" is, but apparently there
is one. So maybe it's more than LyX just not reading non-UTF-8; maybe
there's only one flavor of UTF-8 it reads?
This is a huge issue, and we will have bugs here. One of the biggest
changes with 1.5.x is the switch to unicode. ALL layout files need to be
changed to unicode. See the release notes.
Am I right that all layout files shipping with LyX 1.5.x are already
unicode, and this just means that people who rolled their own will need
to convert theirs to unicode?
/Paul
