On Sun, May 04, 2008 at 09:52:10PM +0200, Uwe Stöhr wrote:
> Andre Poenitz schrieb:
>
>> And, instead of assuming 7 bit ASCII we should assume UTF-8. This would
>> be a uniformly better guess.
>
> No it won't, most programs still produces TeX-output in plain ASCII.
Sure, and all plain ASCII is als
Andre Poenitz schrieb:
And, instead of assuming 7 bit ASCII we should assume UTF-8. This would
be a uniformly better guess.
No it won't, most programs still produces TeX-output in plain ASCII. We assume currently 8-bit
latin1 btw.
regards Uwe
On Wed, Apr 30, 2008 at 08:14:54PM +0200, Uwe Stöhr wrote:
> rgheck schrieb:
>
>>> 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.
>>>
>> I'd be happy to help with this, if I knew what it was abo
rgheck schrieb:
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.
I'd be happy to help with this, if I knew what it was about and had
relevant abilities. We really should try to bring tex2lyx up
Jürgen Spitzmüller wrote:
> If there are changes in
> tex2lyx that do not follow this rule (which ones?), they have to be
> reverted.
I checked the situation, and there are several changes that corrupt the file
format:
- hspace
- href
- newcommandx
- nocite
I hope, I haven't missed anything.
T
Uwe Stöhr wrote:
> 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.
The problem is that tex2lyx
Uwe Stöhr wrote:
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.
I made some changes, but they were only d
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
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
> Don't let us start this discussion again. We decided that we do not want
> tex2lyx to produce a corrupted file format. So all features that came in
> after file format 247 have to be imported as ERT. If there are changes in
> tex2lyx that do not
Uwe Stöhr <[EMAIL PROTECTED]> writes:
>> We cannot support \hspace, can we? This feature has been introduced after the
>> current file format of tex2lyx.
>
> We can support it. Other developers added support for new features to tex2lyx
> as well.
Which ones?
> The tex2lyx that comes with LyX 1.
Uwe Stöhr wrote:
> We can support it. Other developers added support for new features to
> tex2lyx as well. 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
> We cannot support \hspace, can we? This feature has been introduced after the
> current file format of tex2lyx.
We can support it. Other developers added support for new features to tex2lyx
as well.
The tex2lyx that comes with LyX 1.6 can handle this because don't convert ERT in lyx2lyx, so \h
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
> uwestoehr wrote:
>> tex2lyx/text.cpp: support for \hspace
>
> We cannot support \hspace, can we? This feature has been introduced after the
> current file format of tex2lyx.
You are right. We have to be careful with versions.
JMarc
uwestoehr wrote:
> tex2lyx/text.cpp: support for \hspace
We cannot support \hspace, can we? This feature has been introduced after the
current file format of tex2lyx.
Jürgen
14 matches
Mail list logo
