XHTML output for InsetListings.

[lyx.git] / development / HTML / HTML.notes

diff --git a/development/HTML/HTML.notes b/development/HTML/HTML.notes
index bf7a870ebf77e5cdf23eba325171c8dd482a53fc..7f8a77a28146db09350b05a9aec60239fdda1184 100644 (file)
--- a/development/HTML/HTML.notes
+++ b/development/HTML/HTML.notes
@@ -5,14 +5,17 @@ Known issues:
        <p>, in violation of the DTD. I guess we could close the paragraph and then do
        the <hr />, but isn't there a better solution? There's actually a LyX bug here, 
        I think, since a line surely ought not appear in a normal paragraph?
-* The same issue arises with InsetVSpace, unsurprisingly.
+* The same issue arises with InsetVSpace, unsurprisingly. And also with the inline
+       version of InsetListings. 
+* One option here, actually, would be to use just <div> and never use <p>, setting
+       the spacing and such via CSS.
 * The code that manages the nesting of tags is pretty primitive. It needs a lot
        of work.
 
 These insets are basically done, though there are probably issues here and there,
        and there are even some FIXMEs:
        Bibitem, Branch, Caption, Collapsable, Footnote, Hyperlink, Info, Label, Line, 
-       Marginal, Note, Newline, Newpage, Quotes, Space, SpecialChar, Wrap
+       Listings, Marginal, Note, Newline, Newpage, Quotes, Space, SpecialChar, Wrap
 
 These insets do nothing for XHTML:
        ERT, OptArg, Phantom
@@ -58,7 +61,6 @@ These do not yet work and need some attention:
        InsetInclude: I think we just want to include it, straightforwardly. Probably will
                base this more on the latex() routine, then. Another possibility, maybe with a
                flag of some sort, would be to do it as a separate file, to which we link.
-       InsetListings: Probably just output it as <pre>.
        InsetRef: Presumably, this is an internal link. But what should the text be, and how
                should we get it? Probably some validation thing again, where labels tell us where 
                they are. Alternatively, we could parse the aux file.