This report was about LyX's *native* XHTML export (LyXHTML). Offlist I wrote Alex some similar emails about eLyXer.
By the way, I don't necessarily view what I reported as issues, I'm just asking the design intent before I make a filter that: 1) Makes the HTML more ePub friendly 2) Removes the styles from the HTML in preparation for them to go in the ePub's Styles section 3) Maps LyX Part Chapter Section etc to the desired <h1> <h2> <h3>, with the mapping configurable in a Yaml file. 4) Creates most of the guts of the toc.ncx 5) Creates an HTML table of contents Thanks, SteveT Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance On Tue, 9 Jul 2013 08:25:27 +0000 (UTC) Guenter Milde <[email protected]> wrote: > Dear Steve, > > thanks for reporting issues with LyX HTML export back. I think this > feedback is important to get the best out of the effort of the coders > and is valued by both. > > However, please make it *very* clear in your posts, whether you report > about LyX's "native HTML export" or the external "eLyXer" program: > > On 2013-07-09, Steve Litt wrote: > > > I'm making a postprocessor to make the output of LyX's LyXHTML > > xhtml export more compatible with ePub. > > ... [all the important questions] ... > > > This one feature of eLyXer's xhtml conversion, ... > > I know that, from a users point, the difference in calling the export > is just one line in the menu. However the inner working and the > philosophy of native LyX export vs. eLyXer is sometimes orthogonal. > > While both authors monitor this list and respond to questions and > requests, trying to fix a problem of the *other* tool (and then > realizing that the description does not fit) has the potential to > turn your valuable feedback into an irritant to (at least) one of > them. > > > Günter > > >
