2 1. The counter patch, and better output for InsetRef.
3 2. Better output for citations, meaning better labels. Numerical, as said below,
4 should be easy, and author-year oughtn't to be THAT hard. But it'll need a
6 3. CSS needs work in several places, mostly floats. Maybe check elyxer on that.
10 These insets work but still need work:
11 InsetBibtex: There are a few issues here.
12 - One is that the output is not very nice. This will be solved, though, by
13 a patch of mine I seem to have forgotten to finish. To get output that
14 accorded with the BibTeX style, of course, we'd have to parse the bbl file.
15 I don't know if that's worth it.
16 - Another issue concerns cross-references. At the moment, we simply use the
17 xref information for every entry, rather than listing the xref separately and
18 then referencing it. That should not be terribly hard, but it would take a bit
20 - A third issue concerns the labels. At present, we use the BibTeX key as the
21 citation label. It would not be too hard, I think, to use numerical labels,
22 in the way BibTeX does. To do so, we'd need to move the sorting routine out
23 of InsetBibtex so we could do it before we print the citations. See below.
24 InsetBox: The CSS isn't there yet.
25 InsetCitation: This has two limitations as of 20 XI 2009. The first is that we
26 ignore the citation style and output square brackets, no matter what. The
27 second is that, with BibTeX, we simply use the BibTeX key as the citation
28 string, thus ignoring numerical, author-year, etc. It will not be too hard
29 to make numerical work. To do this, we need to collect information on the
30 used citations, alphabetize them, and then assign numerical labels via the
31 BibTeXInfo::label() method. A similar strategy will work for author-year and
32 the like, but calculating labels will be more complex---unless we just parse
33 the bbl file, which of course is the only fully general solution.
34 InsetFlex: I think this one is OK, but it needs some testing.
35 InsetFloat: This seems to work OK, but it will need testing and tweaking. There is
36 also no CSS yet for these.
37 InsetFloatList: Seems to work well, but may need testing.
38 InsetGraphics: This works in a pretty primitive way, in that it outputs the graphic
39 and appropriate img tag. But we don't yet do any sort of scaling, rotating, and
40 so forth. That won't be hard, since we can just call ImageMagick to do this for
41 us, but appropriate routines will need to be written.
42 InsetRef: At present, we just use the label name as associated text, and put it
43 into square brackets. It'd be nice to be able to do more, but for that we'd need to
44 associate counters with the labels, and we don't have that yet.
45 InsetTabular: Works reasonably well, but we don't do anything with any of the
46 arguments provided for longtable. There are probably other limitations, too,
47 since I'm very much not an expert with tables.
51 We have a fair bit of math now working via MathML output, but there are still some
52 isues, and not all the insets work. Here are the ones I know still need work:
53 - Array: Should be able to use alignment information via appropriate attributes, for
54 mtable, mrow, and mtd.
55 - Box: There is a general issue here with text mode nesting. See the FIXME attached
57 - Lefteqn: For this, and numbering in general, probably need mlabeledtr, which may
58 mean we always need to output <mtable>.
60 - Phantom: There is some support for this in MathML....
61 - Ref: Needs to be deferred.
62 - Size: Unclear if we want to do anything here, though we could. See
63 lib/symbols for the commands supported, of course.
64 - Space: Needs checking.
65 - SpecialChar: Needs checking.
66 - Split: There are some alignment issues here, but it basically works.
67 - Substack: This is a stack of however many cells, all in a smaller style.
68 Probably do something with <mover>, again.
69 - Tabular: This is more or less a text-like table in math. Probably output it
70 as a table, but set the font.
74 - Need to handle the equation hull type by outputting a counter. But that will
75 have to wait for the counter patch. The counter probably goes with mlabeledtr,
76 which may mean we always need to output <mtable>.
77 - Similar issues about eqnarray.
78 - It's not clear if we need to do much about the other hull types.
79 - XYMatrix: So far as I can tell, using this in LyX effectively involves using a
80 lot of ERT, within the matrix, to get the arrow effects. At present, it just prints
81 as an InsetMathGrid, from which it inherits, and so as a simple table. I don't know
82 how much more we can do.
85 These insets do not work and are not yet scheduled to work:
86 InsetExternal: It may be that this won't be too hard, but I don't understand
87 these so am not sure what to do. For now, it is disabled.
88 InsetIndex and InsetPrintIndex: An "advanced" case. What really would be cool
89 would be to collect all of these and then write the index as a series of links
90 back to the occurrences. But not now.
91 InsetNomencl and InsetPrintNomencl: Also "advanced".
93 May need to make use here of TocWidget::itemInset, which should then be moved