Please make LyX native language well formed and valid XML

Dr Eberhard W Lisse nospam at lisse.NA
Wed Jan 20 22:48:43 UTC 2021


I like XML out of principle, but besides that I find the tone of the
request a bit over the top, especially for such a huge undertaking, it
is rare to require LyX documents to be both manually and
programmatically editable.

Messing with the LyX file is admittedly difficult, why do it in the
first place?

I do a lot of LyX stuff with Perl templating (such as prescription
writing) and if that doesn't work have Perl generate LaTeX directly
(such as filling out (tax) forms).

That said, I am rather looking forward to try the new docbook 5 support.
I am sure one will be able to come up with an epub exporter (script)
that can be used as usual from LyX.

And if not, since epub is probably only going to be used for larger
projects (like my handbook), I'll just add a few lines to my Makefile of
502 lines :-)-O.

greetings, el

On 2021-01-20 14:33 , Pavel Sanda wrote:
> On Wed, Jan 20, 2021 at 03:23:37AM -0500, Steve Litt wrote:
>> Even if the Docbook exporter were perfectly semantic and kept styles
>> intact, unlike the HTML exporter, Docbook is just a lillypad in the
>> middle of the stream, and to reach LaTeX, PDF, HTML or ePub, I'd need
>> to use the infamous black box Pandoc.  Yuck!
> I did not push you to use pandoc. You wanted something more xml-based
> for home-baked conversions of the document. Docbook might help and it
> would be more helpful to give some feedback than offer scathing
> metaphores for dev(s) who made that happen.
> .xml based format of lyx is not going to happen for 2.4.
> Pavel

More information about the lyx-users mailing list