>>
>>But the newest tex2lyx produces file format 243, and LyX 1.3.6 can only read
>>242. So the instructions on the wiki page should be modified:
>>
>>"You may have to replace LyX.py and lyx_1_4.py of LyX 1.3.6 with the
>>versions from here:
>>http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/lib/lyx2lyx/
>>"
>>
>>Jean-Pierre, it would be nice if you could do that and maaybe add some more
>>details. All files of lyx2lyx except lyx2lyx itself can be replaced with
>>their 1.4 counterpart without problems.

Both the Win tex2lyx bundle and the Solaris tex2lyx bundle provide 241 format,
so that copying the binary is enough.


>>Yes. But the syntax of the 1.4 layout files is changed. For example I could
>>not use beamer.layout with 1.4 but had to make some modifications. I'll
>>attach a diff so you can see the differences.

Right, I had to tex2lyx in the bundle after copying the 1.4 version to make it 
work,
otherwise I got this:
<log>
Ignoring options 'T1' of package fontenc.
LyX: Unknown TextClass tag `MaxCounter' [around line 15 of file c:\Program 
Fil\LyX-1.4\LyX\Resources\lyx\layouts\beamer.layout]
We failed to find the layout 'Standard' in the layout list. You MUST investiga!
Assertion triggered in const LyXLayout_ptr& LyXTextClass::operator[](const 
stdstring&) const by failing check "false" in file 
lyxtextclass.C:816

abnormal program termination
</log>

What's surprising is that the same operation performed on the same file on 
Solaris works fine
(and the lyx file is correct as the Solaris version includes your patch for bug 
#1910).

Anyway beamer is particular as it is not part of the LyX bundle, so we're off 
the baseline distrib here.

A round trip on a technical report including many formulas and graphics seems 
OK on both ports
(but round trip means that the tex files are formally correct because created 
by lyx export,
so that's not really a real life example which would exhibit translation of 
much varied LaTeX constructs).

Finally calling tex2lyx from lyx does not seem appropriate on the Win port 
since the log remains hidden
(I just get a popup about conversion error w the above example).
Decompressing the tex2lyx bundle, updating the PATH and executing in a MinGW 
window is more informative.

Correct me there if an monitoring when executing from LyX is possible.


-- 
Jean-Pierre

Reply via email to