|
From: Michael P. <mic...@gm...> - 2013-05-02 14:30:12
|
David Goodger <goodger <at> python.org> writes: > > Thanks, I added something like that. > Having read, the extensive followup to this thread from Goodger and Gruber, I would add my own request for further attention on this issue. I am using reST as the markup format for a specialized wiki application based on the python Bottle micro framework. (Presumably the advantages of reST need not be repeated here: Python native (extensive code base with documentation), rich formatting, programmable, and parse-able. I would like to add a print button with decent formatting (like the mediawiki) for the rendered html pages. Ideally this would have robust translation for the full range of markup (like the mediawiki) The available solutions are not ideal: Rst2pdf does a great job with almost all html renderable rst markup -- especially tables -- but its math pdf rendering (apparently done with reportlab and mathplotlab) is inadequate. Pandoc provides the complement: good text body and math rendering via latex but less than great figure handling and -- at least in my trials --pretty much across the board failure with tables. Rst2latex is still in my view the best option. The latex source is easily tweaked so I can can get it closest to my ideal of best pdf output. But the table translation remains a real stumbling block. (I have other requests for the command line options notably optional inclusion of the latex wrapfigure environment to approximate the realy nice text flow around figures produced by the html writer with the align parameter -- but for another day) So back to the cheatsheet -- perhaps using the cheatsheet to identify which markup subset works with both the latex and html writers would be a more user meaningful short term solution than indicating that cheetsheet should be read as text. Bringing the non-html writers (especially the latex writer) up to the full range of markup translation of the html writer might be a longer term goal Michael |