Quote:
Originally Posted by anywho
One of the reasons I was wanting it is because of the easy step from multimarkdown to full LaTeX documentation to create really nice documentation or books as PDF. I think multimarkdown would have a nice advantage there.
|
You misunderstand how calibre's conversion process works. Multimarkdown as a program doesn't fit into calibre at all.
Calibre's input plugins convert to OEB. OEB is the intermediate format. All output plugins take OEB and convert it to the output format. In this way any supported input format can be converted to any supported output format. Multimarkdown as a perl script simply does not work with calibre. Also, compared to calibre it's quite limited as a conversion solution.
Quote:
Originally Posted by anywho
Basically it's really nice to have a portable write-once solution. The meta-data that you can put into multimarkdown is quite handy where the markdown solution that I think you support does not. You explicitly have to specify things such as author, title, etc etc whilst in MMD you don't.
|
This is not an issue of calibre not allowing you to specify metadata in the file itself. It's an issue of calibre not supporting the metadata extension to the markdown syntax at this time.
Quote:
Originally Posted by anywho
Did you have a look at the metadata attributes at all?
|
Again, the metadata format is an extension to the markdown format that's already supported by Python Markdown (which calibre uses internally for parsing markdown input). That extension is simply not enabled at this time. Hence the comment about allowing users to enable additional extensions in addition to the two that are by default and always enabled.