>There are more and less complicated ways to do this. You could >have a new format, like DocBook, but I think >what's really >wanted is something that would work more like laintext, so >that you can output any document as HTML. So we'd have a set >of ashtml() routines in the insets, etc, pretty much everywhere >we have latex() and plaintext(), and the overall structure >would be the same.
First, I'd not like to clutter the source with asHtml() functions everywhere. Can't we think of a smart way to group all these function in src/output/html/output_html.cpp or something like that ? Especially if someone is going to implement RTF-support, there would appear asRtf() functions. Second, having a look at tex output/input. Why is the latex output function everywhere in the source code, while the tex2lyx functions are grouped together. So, what if we want to read Rtf files ? Do we want an rtf2lyx project ? Do we want readRtf() functions in the src code ? Third, do you have ideas on what to do with LatexFeatures ? Do you want to (mis)use this class to know how the preamble of Html would look like ? Or are you planning to make a HtmlFeatures class ? Or maybe, we can generalize LatexFeatures a bit, such that it contains information on what is used, but does not explicitly say which LateX packages it corresponds to ? Again, if you choose HtmlFeatures, then we would also need a RtfFeatures etc. >Richard Vincent
