I assumed from subsequent emails that docutils did not want this feature. I would have to go back and see show far I got, but if I remember correctly, this idea was very easy to implement and I had more or less completed it.


On Fri, Dec 16, 2011 at 3:16 PM, Guenter Milde <> wrote:
Dear Paul,

On 2011-11-01, Paul Tremblay wrote:
> On Tue, Nov 1, 2011 at 5:56 AM, Guenter Milde <>wrote:

>> However, this conversion is only required because the current XML writer
>> does not support raw content::

>>    <raw format="xml" xml:space="preserve">
>>        &lt;custonElement1&gt;
>>  &lt;customElement2&gt;
>>    </raw>

>> I'd prefer a more consistent way to deal with the problem: add this
>> capability to the XML writer. I know this means rather big changes to the
>> current XML writer, however

>> * this would bring it in a line with the other docutils writers,
>> * a lot of required code could be taken from other writers.


> As far as requiring a lot more code in the writer, I'm not so sure that is
> the case. I'm at work right now so I can't test this out, but I think you
> can simply iterate through the DOM, and print each element. When a math
> node is found, unescape this with the SAX.utils. unescpape function, and
> then print out that string. I'll have to see if this will work at home. If
> so, it would require very little additional code.

> I like your suggestion because it kills two birds with one stone--allowing
> for raw XML (my next suggested patch) and mathML, without the waste of
> conversion to a node and then to a string.

How far did you come with this approach?


Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for
developers. It will provide a great way to learn Windows Azure and what it
provides. You can attend the event by watching it streamed LIVE online.
Learn more at
Docutils-develop mailing list

Please use "Reply All" to reply to the list.