Jean-Marc Lasgouttes schrieb:
We can support it. Other developers added support for new features to tex2lyx
as well.
Which ones?
I remember commits by Richard and Pavel, but haven't looked at the log files
yet to say it exactly.
The tex2lyx that comes with LyX 1.6 can handle this because don't
convert ERT in lyx2lyx, so \hspace is not touched. tex2lyx is
basically fileformat 247 and lyx2lyx will convert it to the latest
one. As \hspace isn't touched, you get the right result for LyX 1.6.
You can test this with the TeX test file I updated yesterday evening
in SVN.
We already had this discussion. We cannot add features beyond 249
until the unicode part is done.
I don't ageree. We had this discussion indeed and I fully agree that we need Unicode for tex2lyx.
But I don't remember that we cannot add support for things that are not Unicode related (space
commands don't contain non-ASCII characters) and not touched by lyx2lyx. When you are importing TeX
files with tex2lyx that is shipped with LyX 1.6, you will as result get a LyX file that is in the
latest fileformat as lyx2lyx is run afterwards automatically, so you get a valid file. You could
convince me when showing the opposite.
When the result is a LyX file not in the latest file format, then you are right. But as said, this
is the tex2lyx that comes with LyX 1.6. You can see with the test TeX files from SVN that tex2lyx
works fine on them - so I don't see a problem.
Concerning Unicode, I have asked for help several times but nobody could help me to implement this -
so I guess it will not happen the next years.
regards Uwe
