Skip to content
Fletcher T. Penney edited this page Apr 8, 2011 · 9 revisions

Known Issues

Non-ASCII characters require complete HTML document

In order for Non-ASCII characters to display properly in most browsers, there needs to be some indication of the character set being used. Without getting into too many technical details, the easiest way to get HTML output to display properly is to include metadata that will trigger a complete document, e.g. a Title.

OpenDocument doesn't properly support image dimensions

It's relatively easy to insert an image into ODF using fixed dimensions, but harder to get a scaled image without knowing the exact aspect ratio of the image.

For example, in LaTeX or HTML, one can specify that image should be scaled to 50% of the width, and have it automatically calculate the proper height. This does not work in ODF, at least not that I can find.

You have to manually adjust the image to fit your desired constraint. It's easy to do, simply hold down the shift key while adjusting the image size, and it will likely snap to match the specified dimension.

I welcome suggestions on a better way to do this.

Math Support lacking in OpenDocument

I figured out how to embed MathML in an OpenDocument file. There are several tools to convert LaTeX to MathML, including blahtex.

I'll probably start by writing a perl utility that can take a MMD-created ODF, and then parse the math "bits" out and put them back in as MathML.

Even better would be if I could figure out how to compile blahtex into multimarkdown as a library to do the processing internally.... Not sure how long that will take to get around to. Anyone with any particular skills in that area who wants to help - let me know!

Bibliography support lacking in OpenDocument

There is no automatic processing of citations when creating an OpenDocument file. Suggestions are welcome, as I would like to come up with a reasonable solution, if possible.

OPML doesn't handle "skipped" levels

When converting a MMD text file to OPML with the mmd binary, each level only contains it's direct children. For example:

# First Level #

## Second Level  ##

### Third Level ###

## Another Second Level ##

#### Fourth Level ####

When this is converted to OPML, the "Fourth Level" item will be deleted, since it skips a level from its parent, "Another Second Level".

It's possible to fix this, but it's going to take a more complicated algorithm than what I currently have and it's not a high priority for me to fix at the moment.

As always, suggestions welcome.