See dependencies.
Version: unspecified
Severity: enhancement
Description
Description
Details
Details
- Reference
- bz46517
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | MarkTraceur | T48517 Alternative export formats for Parsoid (tracking) | |||
| Declined | • GWicke | T39933 Parsoid: Export as LaTeX | |||
| Declined | • GWicke | T39934 Parsoid: Export as TEI XML | |||
| Declined | MarkTraceur | T48518 DocBook export for Parsoid | |||
| Declined | MarkTraceur | T48519 Markdown import/export | |||
| Declined | MarkTraceur | T48516 Generalise the Parsoid structure and internal representations. |
Event Timeline
Comment Actions
There are already capable tools for format conversions like pandoc. They could be improved by adding support for our RDFa information, but I doubt that it makes sense for us to get into the HTML to X conversion business.
Comment Actions
My reasoning is explained more thoroughly in bug 46516, and I'd be up for chatting about it in IRC :)
Comment Actions
Closing as wontfix, as we don't currently plan to tackle this as part of the Parsoid project.
We are providing a rich HTML/RDFa DOM instead, which can be converted to other formats using tools like pandoc. See http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec for more information. Let us know if any information you need for a conversion is missing in the DOM.
Comment Actions
dirk.hunniger wrote:
I wrote a solution for the export from mediawiki to latex it here
http://de.wikibooks.org/wiki/Benutzer:Dirk_Huenniger/wb2pdf
Comment Actions
[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704]