Jose Abilio Oliveira Matos a écrit :
> Several points, I didn't review all the package:
>
> 1) Although I would like to see sgml2xml.py and not perl :-) there is no
> point in reinventing the wheel.
> There is already a sgml2xml that is distributed with (open)jade that is
> from Norman (enough said :-). Look also for (o)sx that is the engine bellow
> sgml2xml.
I've tried the Clark's sgml2xml. I'm a bit disappointed:
* the XML output is really ugly, and in my opinion it cannot be seen as a decent
XML export result.
* with a multi-parts document, it produces a single file. It's not good if you
expect to have the same splitting output.
* I have problems with special chars (éèà, etc.).
* the <!DOCTYPE is empty (no public nor refernce id, etc.)
* I've tried a perl sgml2xml wrapper (in fact it's an sx wrapper), that allows to
define the publi and system ids to use. Unfortunately the output is still ugly
(underlying engine) and it fails with multi-parts doc.
At the moment my conclusion is that it isn't a good candidate for your SGML->XML
translation. In addition, the awaited changes are restricted since the LyX output
is almost XML compliant.
Jose, have you ever had experiences with sgml2xml? What do you think?
BG
