Introduce a return value for mathmlize(). We will need this to be able

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

diff --git a/development/HTML/HTML.notes b/development/HTML/HTML.notes
index 3c96a775e6d922027858f8fad49ecd0f66ea1de7..b9750e3043f8f9620246863b0551286a2e5d862c 100644 (file)
--- a/development/HTML/HTML.notes
+++ b/development/HTML/HTML.notes
@@ -1,11 +1,10 @@
 TODO:
-1. InsetTabular
-2. The counter patch, and better output for InsetRef.
-3. Better output for citations, meaning better labels. Numerical, as said below,
+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.
-4. CSS needs work in several places, mostly floats. Maybe check elyxer on that.
-5. MathML
+3. CSS needs work in several places, mostly floats. Maybe check elyxer on that.
+4. MathML
 
 
 These insets work but still need work:
@@ -41,12 +40,50 @@ These insets work but still need work:
        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.
 
+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
+       - Big: Not sure if we can actually do anything here. Probably they should
+               just be treated as delimiters.
+       - BoldSymbol: Should be easy.
+       - Box
+       - Cases
+       - Diff: Code exists, but I do not know if it is right.
+       - Font
+       - Binom (in Frac): None of these tags exist in MathML 2.0. We'll
+               just output a fraction with delimiters.
+       - Lefteqn
+       - MBox: Use <mtext>.
+       - Overset: Use <mover>.
+       - 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
+       - Stackrel: Use <mover>, probably.
+       - 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.
+       - Underset: Use <munder>.
+       - XArrow: Contents above and below an arrow. Use...?
+       - XYMatrix: Not sure how this differs from ordinary ones.
+
+
 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 
                these so am not sure what to do. For now, it is disabled.
@@ -58,9 +95,6 @@ These insets do not work and are not yet scheduled to work:
 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:
-       InsetTabular: This shouldn't be too hard, but will need doing.
-
 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