On Mon, May 19, 2014 at 09:41:01AM -0400, Richard Heck wrote: > On 05/08/2014 02:42 PM, Enrico Forestieri wrote: > >On Thu, May 08, 2014 at 08:41:09AM +0200, Jürgen Spitzmüller wrote: > >>2014-05-08 8:29 GMT+02:00 Jürgen Spitzmüller <sp...@lyx.org>: > >> > >>>Don't see this with current branch. > >>> > >>Ah, you talk about opening in 2.0.x. Can you track it down further? > >Jürgen, it seems that there is a problem when inserting an EndFrame layout. > >Seemingly, these layouts are always enclosed in extra \end_layout and > >\end_deeper tags. The attached patch against stable let me export Pavel's > >example file to 2.0 correctly. However, I did no extra check, so I > >leave to you judging whether it is the right patch or not. > > This seems to help the situation, though the 2.0.x export of the > extremely complex file beamerlyxexample1.lyx still opens with errors > in 2.0.x: > > /cvs/lyx/ > lyx-20 beamerlyxexample1.20.lyx > Paragraph ended in line 350 > Missing \end_layout. > Paragraph ended in line 645 > Missing \end_layout. > Text.cpp (1766): Handling unknown body token: `\end_layout' > Paragraph ended in line 2704 > Missing \end_layout. > LyX: \end_deeper: depth is already null [around line 2704 of file > /music/cvs/lyx/beamerlyxexample1.20.lyx current token: '\end_deeper' > context: 'InsetText::read'] > Paragraph ended in line 3572 > Missing \end_layout. > Paragraph ended in line 3636 > Missing \end_layout. > Paragraph ended in line 3706 > Missing \end_layout. > Text.cpp (1766): Handling unknown body token: `\end_layout' > Paragraph ended in line 5939 > Missing \end_layout. > LyX: \end_deeper: depth is already null [around line 5939 of file > /music/cvs/lyx/beamerlyxexample1.20.lyx current token: '\end_deeper' > context: 'InsetText::read'] > Paragraph ended in line 6866 > Missing \end_layout. > > That's a lot fewer errors than without the patch, though. (See > below.) I'd go ahead and commit.
Some of the above "Missing \end_layout" are due to a thinko of mine and are caused by the conversion fron 475 to 474. I am going to commit a fix for those. After this patch, the errors get halved for me, and it should be easier tracking them. -- Enrico
