-The main output routines now more or less work.
+TODO:
+1. The counter patch, and better output for InsetRef.
+2. Better output for citations, meaning better labels. Numerical, as said below,
+ should be easy, and author-year oughtn't to be THAT hard. But it'll need a
+ bit of work.
+3. CSS needs work in several places, mostly floats. Maybe check elyxer on that.
+4. MathML
-Known issues:
-* InsetLine normally appears in a standard environment, which puts <hr /> inside
- <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. 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, Include, Info,
- Label, Line, Listings, Marginal, Note, Newline, Newpage, Quotes, Space,
- SpecialChar, Wrap
-
-These insets do nothing for XHTML:
- ERT, OptArg, Phantom
These insets work but still need work:
InsetBibtex: There are a few issues here.
in the way BibTeX does. To do so, we'd need to move the sorting routine out
of InsetBibtex so we could do it before we print the citations. See below.
InsetBox: The CSS isn't there yet.
- InsetCitation: This has two limitations as of 11 VI 2009. The first is that we
+ InsetCitation: This has two limitations as of 20 XI 2009. The first is that we
ignore the citation style and output square brackets, no matter what. The
second is that, with BibTeX, we simply use the BibTeX key as the citation
string, thus ignoring numerical, author-year, etc. It will not be too hard
the bbl file, which of course is the only fully general solution.
InsetFlex: I think this one is OK, but it needs some testing.
InsetFloat: This seems to work OK, but it will need testing and tweaking.
+ InsetGraphics: This works in a pretty primitive way, in that it outputs the graphic
+ and appropriate img tag. But we don't yet do any sort of scaling, rotating, and
+ so forth. That won't be hard, since we can just call ImageMagick to do this for
+ us, but appropriate routines will need to be written.
+ InsetRef: At present, we just use the label name as associated text, and put it
+ into square brackets. It'd be nice to be able to do more, but for that we'd need to
+ associate counters with the labels, and we don't have that yet.
+ InsetTabular: Works reasonably well, but we don't do anything with any of the
+ arguments provided for longtable. There are probably other limitations, too,
+ since I'm very much not an expert with tables.
+ InsetTOC: This now works pretty well, but only for the table of contents, not for
+ any other TOC-like lists. Getting those to work shouldn't be too bad, as we can
+ do almost exactly the same thing. That said, though, we might want to do things
+ slightly differently, and have the links target actual *insets*, rather than just
+ target paragraphs. That'd mean doing a bit of work on TocBackend, etc.
+ InsetXYMatrix: So far as I can tell, using this in LyX effectively involves using a
+ lot of ERT, within the matrix, to get the arrow effects. At present, it just prints
+ as an InsetMathGrid, from which it inherits, and so as a simple table. I don't know
+ how much more we can do.
+
+Math
+ We have a fair bit of math now working via MathML output, but there are still some
+ isues, and not all the insets work. Here are the ones I know still need work:
+ - AMSArray
+ - Array
+ - Box: There is a general issue here with text mode nesting. See the FIXME attached
+ to the SetMode class.
+ - Lefteqn
+ - Par?
+ - Phantom: There is some support for this in MathML....
+ - Ref: Needs to be deferred.
+ - Size: Unclear if we want to do anything here, though we could. See
+ lib/symbols for the commands supported, of course.
+ - Space: Needs checking.
+ - SpecialChar: Needs checking.
+ - Split: See lib/symbols, for split insets.
+ - Substack: This is a stack of however many cells, all in a smaller style.
+ Probably do something with <mover>, again.
+ - Tabular: This is more or less a text-like table in math. Probably output it
+ as a table, but set the font.
+
These insets do not work and are not yet scheduled to work:
InsetExternal: It may be that this won't be too hard, but I don't understand
May need to make use here of TocWidget::itemInset, which should then be moved
to TocBackend.
-These do not yet work and need some attention:
- InsetGraphics: This should be fairly straightforward, but I'll need to learn a bit
- about export formats, etc, to get it completely right. We'll also want to make
- some use of the params, eg, on width and height. I guess there is also some
- issue about converting the graphics formats?
- 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.
- InsetTabular: This shouldn't be too hard, but will need doing.
- InsetTOC: We should just be able to use what we have in the TOC. To get links to
- work, though, we'll need to co-ordinate the writing of anchors in the sections,
- which won't actually happen until later.
-
MATH
Regarding math, the view seems to be that we should in the first instance just use what
we get from instant preview and copy those over to the output directory, and then try
projects / lyx.git / blobdiff