Abdelrazak Younes <[EMAIL PROTECTED]> writes: > > Jean-Marc Lasgouttes wrote: > >>>>>> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: > > > > Abdelrazak> Why should we? I am probably missing something but... > > Abdelrazak> isn't it enough to tell to the users that their layout > > Abdelrazak> needs to be converted to utf8? Of course we should say it > > Abdelrazak> big and loud but I reckon that users that are able to > > Abdelrazak> change a layout are also able to change the encoding of > > Abdelrazak> their layout. Especially so if the big goal of 1.5 is > > Abdelrazak> unicode. > > > > And then, what about their old .lyx files that contain layouts with latin1 > > names? Or am I missing something? > > As for the layouts, they should also convert their LyX file to utf8. If > they can convert their layouts, they can also convert their LyX files. > They should do that in any case. > For any users (especially users not using latin-1 encoding), I reckon > there should be a strong recommendation to convert all their old LyX > file to UTF-8. If it is not the announcement, it should be.
>From the user point of view, it's different for lyx files and for layouts: - for lyx files, you can do it manually with lyx2lyx, or by loading the old file format thet you should be able to use right out of the box. You can even keep the lyx file in the old format if you do not edit it, but it will be Unicoded all right if you save it (including style names); - for layouts, the python script layout2layout.py does format conversion between layouts (and again, old format layouts are converted on the fly), but layout2layout.py knows nothing about Unicode, so you have to convert it manually with iconv (see the older thread about 1.4 to 1.5 upgrade). This is required anyway for isolatin characters spreading around in local layouts. So the user HAS to convert his own layouts to Unicode. So from the user point of view, nothing else to do with lyx files than loading in 1.5, manual format/unicode conversion of user layouts required. The problems comes from the fact that with both layout and lyx files in Unicode, lyx crashes on this: Assertion triggered in const lyx::docstring lyx::from_ascii(const char*) by failing check "static_cast<unsigned char>(*c) < 0x80" in file docstring.cpp:32 Abort This would not happen with the gettext translation mechanism (name the styles in ascii, translate in the .po file), but it seems agreed that this is too complicated for user layouts. -- Jean-Pierre
