[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lyx-devel
Subject:    Re: Progress on the MS Word to LyX conversion (xml)
From:       Abdelrazak Younes <younes () lyx ! org>
Date:       2008-07-24 13:51:23
Message-ID: 488888DB.9060207 () lyx ! org
[Download RAW message or body]

Pavel Sanda wrote:
> Abdelrazak Younes wrote:
>    
>> Because XML is easy to transform. That is really the *main* reason. For
>> example the transformation to TEI will be very, very simple, believe me.
>>      
>
> Abdel, you have some practical experience with that?

I do :-)

>   I have been in project,
> where more easier xml format was used the we would have and it was pain
> to debug those conversion through xslt. From those times all those easy-to-do
> transformations between different xml formats become an urban legend to me,
> although i understand that one can't make definitive generalization from
> one experience...
>    

In my previous job we generated XML reports in C++. Those XML reportq 
were transformed to html and SVG before being published in our web 
server. They were also transformed to XSL-FO and published as pdf thanks 
to FOP. We also did multiple XML reports combination for data fusion and 
statistics. All of this using XSL.

But note that the use of XSL is not mandatory. One could just use the 
XML python library and do whatever needed transformation by hand.

> also that is the reason why i consider those plans that xml-isation will at the
> end turn into having some complete lyx<->odf converter, as only theoretical, or say
> marketing speech :)
>    

We'll see. But odf is not our gold goal, at least it is not mine. For 
some of my (future) projects, I would personally like to be able to 
generate .lyx file programatically. OK, I know I could do this with 
current format but a clearly defined XML format together with a python 
library (lyx2lyx) would ease the path to that goal. That is just one use 
case were XML would be profitable.

Abdel.

[prev in list] [next in list] [prev in thread] [next in thread]