On Wednesday, 5 April 2017 21.48.21 WEST Uwe Stöhr wrote: > El 05.04.2017 a las 22:08, Enrico Forestieri escribió: > > Most probably you have some non-ascii characters in a \DeclareLaTeXClass > > line in some of your layout files. Now those files are explicitly read as > > utf-8 encoded. If this is so, the attached patch should help. > > Yes. This is necessary. Moreover all open() commands must replaced by > io.open() to assure that we use the right encoding.
In the cases were we need to care. And with python3 the distinction is more present since the default strings have an encoding associated (they are unicode) while for python2 that is not true. > However, I am not very familiar with Python. I only acted because after > José's commits I could no longer even start LyX. Actually my commits were unrelated to the problems you described. :-) > > Another consequence of the recent changes is that if someone has old > > layouts containing latin1 characters then configure will now misteriously > > fail. > > I thought layout2layout takes care of this. If not, then this is > necessary to add this feature for LyX 2.3. I agree. I would expect for our files to have the same encoding after lyx 1.6 (utf-8). > regards Uwe -- José Abílio
