On 02/03/2014 11:34 AM, Steve Litt wrote:
On Mon, 3 Feb 2014 07:53:49 +0100
Liviu Andronic <landronim...@gmail.com> wrote:
Dear Steve and Alex,
On Mon, Feb 3, 2014 at 2:48 AM, Steve Litt
<sl...@troubleshooters.com> wrote:
On Fri, 31 Jan 2014 22:33:02 +0100
Alex Fernandez <ely...@gmail.com> wrote:
Ladies and gentlemen, if the preceding paragraph doesn't convince
us we need a good, solid, LyX to ePub and LyX to Mobi conversion
Last year we actually had a GSoC project specifically dealing with
ePub. Josh and Richard made progress on this front,
Did the progress include an Xhtml export that preserved semantics and
respected HTML semantics such as using <h?> for leveled headings, <p>
for paragraphs, and <pre> for lyx-code and environments derived from
it, and <span> for character styles? If you got that far and can write
it to disk, I can take it from there.
and the code
simply awaits someone with the motivation and the skills to finish the
job. The almost finished feature is available in several GIT branches
here: http://git.lyx.org/?p=gsoc.git;a=summary .
If I ever get a day or two to familiarize myself with it, I will. But
of course, I'm really lousy at C++, and in fact hate C++.
I think there are several missed opportunities:
1) If LyX insists on having a native format of XML, which by its nature
is human-confusing, it should at least be *well formed* XML so that
it can be handled by an XML parser, and if the programmer is more
skilled than I, XSLT. The day LyX native format is well formed, and
maybe even with a DTD, I'll make the converter: me, myself and I.
Unclear if this will ever happen. I started the project, but then got
busy with other things. It is pretty monumental. But the goal would be
to use Qt's built-in XML writing and reading, which means it will be
well-formed.
2) The ePub converter shouldn't be a part of LyX: Most of it should be
standalone. There's no reason for LyX to need to know *anything*
about ePub. Just provide a sane Xhtml export, one that doesn't
substitute <div> for <p>, or <p> for <h?>, and calls a <pre> a
<pre>. Don't throw away the semantics: Don't convert styles to
appearances, and don't use <div> instead of HTML structural elements
like <p>, <pre>, and <h?>. Give me that, and I can do the rest.
That is what Josh did last summer. The XHTML --> ePub converter is
written in Python.
Richard
