On Tuesday 27 November 2007 15:05:16 Uwe Stöhr wrote:
> > The process is not that you dump a big tex2lyx patch and then others
> > are required to try it out. A better approach would have been first to
> > implement the missing features in 245 that you could fix (actually, we
> > are probably at 24
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Juergen Spitzmueller wrote:
>> I would suggest to implement those features that are covered by 245
>> (\inputencoding and such) and then move on upwards. When we reach 247, we
>> _have_ to implement unicode in a first step, then move ahead.
>
> We sh
Juergen Spitzmueller wrote:
I would suggest to implement those features that are covered by 245
(\inputencoding and such) and then move on upwards. When we reach 247, we
_have_ to implement unicode in a first step, then move ahead.
We should probably define what does "implement unicode" mean...
Uwe Stöhr wrote:
> But you have to give me a chance to work on tex2lyx!:
Certainly. And I really appreciate your effort.
> - When I introduce support for a LyX 1.5 or 1.6 feature and leave the
> fileformat to 245, you complain that tex2lyx may produce incorrect output
> (Have you tested that thi
> So tex2lyx produces an invalid LyX file now. This is not a way we should go,
> IMO.
But you have to give me a chance to work on tex2lyx!:
- When I introduce support for a LyX 1.5 or 1.6 feature and leave the fileformat to 245, you
complain that tex2lyx may produce incorrect output (Have you t
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>
> Uwe Stöhr wrote:
>
> > Yes, things that are already in the latest fileformat won't be touched in
> > lyx2lyx as far as I tested. So except of probably only a few cases where
> > lyx2lyx changes the file to a wrong format, we can support LyX's
Uwe Stöhr wrote:
> Yes, things that are already in the latest fileformat won't be touched in
> lyx2lyx as far as I tested. So except of probably only a few cases where
> lyx2lyx changes the file to a wrong format, we can support LyX's 1.6's
> features and the old ones are converted by lyx2lyx.
So
> I don't understand. Here
> http://www.lyx.org/trac/changeset/21813
> I see that you use \font_sc, \use_hyperref and other parameters that have been
> introduced after 245.
Yes, things that are already in the latest fileformat won't be touched in lyx2lyx as far as I
tested. So except of probabl
Jean-Marc Lasgouttes schrieb:
Sure, but if we declare that a file is in some version, it should
really be of this version. We are going to have problems otherwise.
lyx2lyx does the rest.
Also, since we have new font scheme and you just introduced framed.sty
support (right?) the format can pr
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> This tex2lyx version id for LyX 1.6 and not for LyX 1.4.
Sure, but if we declare that a file is in some version, it should
really be of this version. We are going to have problems otherwise.
>> The process is not that you dump a big tex2lyx patch and then
Jean-Marc Lasgouttes schrieb:
It is not. I do not think that LyX 1.4.x will be able to read a file
that pretends to be 245 but uses nomenclature support or the new
format for bibtex inset.
This tex2lyx version id for LyX 1.6 and not for LyX 1.4.
The process is not that you dump a big tex2lyx
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes schrieb:
>
>>> http://www.lyx.org/trac/changeset/21813
>>
>> As you probably know, we cannot go beyond format 249 if we do not
>> change to unicode support. I do not see this in your patch. What is
>> the format you output here? It is no
Uwe Stöhr wrote:
> As I stated in the commit note that it is still 245 (LyX 1.4.0).
I don't understand. Here
http://www.lyx.org/trac/changeset/21813
I see that you use \font_sc, \use_hyperref and other parameters that have been
introduced after 245.
Jürgen
Jean-Marc Lasgouttes schrieb:
http://www.lyx.org/trac/changeset/21813
As you probably know, we cannot go beyond format 249 if we do not
change to unicode support. I do not see this in your patch. What is
the format you output here? It is not really 245, is it?
As I stated in the commit note
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> Some time ago I started to overhaul tex2lyx to be able to create a
> version that will support the fileformat of LyX 1.6.0.
>
> I added support for lots of commands and updated existing support to
> the current actual trunk fileformat:
> http://www.lyx.org/t
15 matches
Mail list logo
