4 3. The counter patch, and better output for InsetRef.
5 4. Better output for citations, meaning better labels. Numerical, as said below,
6 should be easy, and author-year oughtn't to be THAT hard. But it'll need a
8 5. CSS needs work in several places, mostly floats. Maybe check elyxer on that.
12 These insets work but still need work:
13 InsetBibtex: There are a few issues here.
14 - One is that the output is not very nice. This will be solved, though, by
15 a patch of mine I seem to have forgotten to finish. To get output that
16 accorded with the BibTeX style, of course, we'd have to parse the bbl file.
17 I don't know if that's worth it.
18 - Another issue concerns cross-references. At the moment, we simply use the
19 xref information for every entry, rather than listing the xref separately and
20 then referencing it. That should not be terribly hard, but it would take a bit
22 - A third issue concerns the labels. At present, we use the BibTeX key as the
23 citation label. It would not be too hard, I think, to use numerical labels,
24 in the way BibTeX does. To do so, we'd need to move the sorting routine out
25 of InsetBibtex so we could do it before we print the citations. See below.
26 InsetBox: The CSS isn't there yet.
27 InsetCitation: This has two limitations as of 20 XI 2009. The first is that we
28 ignore the citation style and output square brackets, no matter what. The
29 second is that, with BibTeX, we simply use the BibTeX key as the citation
30 string, thus ignoring numerical, author-year, etc. It will not be too hard
31 to make numerical work. To do this, we need to collect information on the
32 used citations, alphabetize them, and then assign numerical labels via the
33 BibTeXInfo::label() method. A similar strategy will work for author-year and
34 the like, but calculating labels will be more complex---unless we just parse
35 the bbl file, which of course is the only fully general solution.
36 InsetFlex: I think this one is OK, but it needs some testing.
37 InsetFloat: This seems to work OK, but it will need testing and tweaking.
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.
46 These insets do not work and are not yet scheduled to work:
47 InsetExternal: It may be that this won't be too hard, but I don't understand
48 these so am not sure what to do. For now, it is disabled.
49 InsetIndex and InsetPrintIndex: An "advanced" case. What really would be cool
50 would be to collect all of these and then write the index as a series of links
51 back to the occurrences. But not now.
52 InsetNomencl and InsetPrintNomencl: Also "advanced".
54 May need to make use here of TocWidget::itemInset, which should then be moved
57 These do not yet work and need some attention:
58 InsetTabular: This shouldn't be too hard, but will need doing.
59 InsetTOC: We should just be able to use what we have in the TOC. To get links to
60 work, though, we'll need to co-ordinate the writing of anchors in the sections,
61 which won't actually happen until later.
64 Regarding math, the view seems to be that we should in the first instance just use what
65 we get from instant preview and copy those over to the output directory, and then try