From: Waylan L. <wa...@gm...> - 2009-01-11 02:47:27
|
On Sat, Jan 10, 2009 at 9:25 PM, Waylan Limberg <wa...@gm...> wrote: > On Sat, Jan 10, 2009 at 5:54 PM, Artem Yunusov <se...@sp...> wrote: >> >> >> Eric, If you want HTML output you can use ElementTree 1.3 [1] >> >> tree.write("out.html", method="html") >> > > For the record, ET 1.3 is still in alpha and the docs specifically > state that the HTML API is still in flux, so I doubt we will be adding > that support to Python-Markdown for the time being. Perhaps in a > future release. However, reviewing their code may be a good first step > in developing a list of changes that need to be made through > text-replacement in a postprocessor. While not the best solution, it > is better than nothing. > > It occurs to me that, with Fredrik Lundh's permission and a proper license and copyright notice, we could maintain and distribute a (perhaps slightly modified) copy of the _serialize_html function from ET 1.3. Then use that instead of tostring if the user requests html output. I haven't actually tried it, so I don't know how well it will work as I suspect it expects the other changes in ET 1.3, but it may be worth exploring. -- ---- Waylan Limberg wa...@gm... |