Jean-Marc Lasgouttes wrote:

>>>>>> "Georg" == Georg Baum
>>>>>> <[EMAIL PROTECTED]>
>>>>>> writes:
> 
> Georg> Juergen Spitzmueller wrote:
>>> Works for me as well.
> 
> Georg> Fine. Is this OK for 1.4.0?
> 
> I do not like the hardcoding of lyx13x.

Me neither, but I fear that the other possibility that I outlined in the
comment might have side effects for other export paths. The only side
effect that this one could have is that a format that formerly was not
exportable becomes now exportable, because a converter from lyx to that
format exists. This actually does not happen since we have no such
converter in our default configuration.
Theoretically we could simply add lyx as first backend. I thought about
that, too, but I am not sure whether it is not implicitly assumed somewhere
else that the tex/docbook backend is the first one (e.g. in
GetExportableFormats). If somebody can explain what the different handling
of the first format here means we could of course consider this option
instead of hardcoding lyx13.

> If you are going to do that, 
> why not directly add lyx13x to the list of backends? Wouldn't that be
> less code?

I don't think so. Then we would need to hardcode the lyx2lyx invocation in
the handling of this backend, so we are trading in ~ two lines for other ~
two lines.


Georg

Reply via email to