From: Dave Kuhlman <dkuhlman@pa...> - 2011-04-18 17:17:57
----- Original Message ----
> From: Arfrever Frehtes Taifersar Arahesis <arfrever.fta@...>
> To: Docutils Development <docutils-develop@...>
> Sent: Sat, April 9, 2011 4:22:48 PM
> Subject: [Docutils-develop] [PATCH] Support Python 3.2 in
> I'm attaching the patch, which adds support for Python 3.2 in
> This patch is needed independently from the configparser-related patch.
> Arfrever Frehtes Taifersar Arahesis
I've applied your patch and checked it into the SVN repository.
However a question or two:
(1) Does this patch have the effect,
under Python 3.2, of generating an .odt file containing unicode
(2) If so, wouldn't we actually want utf-8 as the encoding? Or does
oowriter actually understand unicode?
I apologize that I do not understand the use of unicode in
Python 3 very well. I have a minimal understanding of
unicode and encodings even in Python 2.
On 2011-04-18, Dave Kuhlman wrote:
> (1) Does this patch have the effect,
> under Python 3.2, of generating an .odt file containing unicode
> (2) If so, wouldn't we actually want utf-8 as the encoding? Or does
> oowriter actually understand unicode?
Python 3 uses the `unicode` object for "generic" strings internally,
allowing encoding-independent representation of all Unicode characters.
Docutils uses `unicode` internally as well - but under Python 2 it needs
to explicitely decode things it reads and encode when writing (to disk or
So no, this patch does not change the behaviour that the encoding of the
output file is governed by the config setting
The text encoding for output.