Josà AbÃlio Oliveira Matos <[EMAIL PROTECTED]> writes:
< Hi Andreas,
< let us syncronize again our todo lists.
<
Unfortunately I got sidetracked this weekend and the last, so
there's no progress on my side. I just had some general thoughts
about factoring the bitmap generation for formulas out of the preview
generation and use it for both, previews and Docbook export.
So on my TODO list is:
* bitmap generation for equations, don't know when I get to it
* declaration of some MathML entities. I get two errors with
my de_Userguide about entities ⁢ and ⅆ.
Those should be declared analogous to lyxarrow or we would need a
hint how to declare those (if they are standard in the MathML DTD,
configure should test for this DTD and disable MathML output if not
found)
* Need to contact the db2latex guys about their practice to put
\ensuremath{...} and \[ ... \] around every equation. I made a bad hack
which omits our \begin{eqnarray} or equivalent in LyX' XML output,
but I think db2latex should be changed instead. TeX will complain
anyhow when it finds the '&' char in standard equations.
* Testing
If you want to pick any, just tell me before the next weekend :-)
My non-math-related TODO list would be:
* Support for Glossaries, Bibliographies and Indices
* better frontmatter / mainmatter separation
* ToCs
* Macros without args (entities)
* Bug #1682
* Messed up i18n on my PowerBook (don't know yet if it's a bug or if
I just messed up my configuration)
< I have applied you work on ids. I have applied also your patch for
< unnamed equations, give them a number.
<
< One of the problem of your implementation in linux is that tellp uses
< a long long int representation. I have applied instead the uniqueID function
< rescued from the graphics.
That's fine. You could also delete my comment about at least 60 chars in
math_hullinset.C since it is outdated now.
<
< What is missing?
<
< Regarding the escape of ids, I am still trying to find a simple way to
< propagate the correct sequence of escaped characters, probably the easiest
< will be putting it on the output parameters.
That's your latest patch, right? Looks ok to me.
I'm just not sure if it should be present in the tclass ... but we can still
change that later if at all necessary.
<
< Have a nice weekend,
Kind of over now :-)
Ciao
/Andreas
