[Nuxeo-localizer] Non-MessageCatalog UTF-8 strings get encoded again

[Sean Treadway]

First off, Localizer promises to make a world of difference for our
site.  We have customers all over the world.  Thanks for coming this
far!

Our site dates back to Zope 2.0 where I stored all the content in UTF-8
encoded python strings.  Displaying the content worked great because I
set the Content-Type header to "text/html;charset=utf-8" for all of the
pages that submit and display the content.

I've upgraded to Zope 2.6beta.  I installed a MessageCatalog (0.9.1) in
the folder of a virtual site and have some translations in place.

When I view pages that include the utf-8 encoded content from the new
site, the non ASCII characters look like they get an extra encoding
(from utf-8 to utf-8).  When I remove the Content-Type header and
display the page in Latin-1, it looks the same as if I have the
Content-Type header and display the page in UTF-8.  If I switch a page
without the Content-Type header from Latin-1 to UTF-8 it looks fine.
However, I need to tell the browser to view the page in UTF-8 and get
the content there without an extra encoding.

My suspicion is that the MessageCatalog is doing something with the
encoding of the response before the request is finished.  The same
content, with the "Content-Type: text/html;charset=utf-8" header from
the original site (without a message catalog) looks fine.  The content
from the message catalog is fine for both pages that have and do not
have the utf-8 charset header.  The content displays fine if I delete
the message catalog and include the charset=utf-8 in the Content-Type
header.

Any insight?  What can I do?  I would really like to use the Localizer,
but updating my content is a daunting task with many objects that have
many properties.  Is there a place in the code I can look for answers or
is this a fundamental behavior of the product?  If anyone can describe
the logic that applies per request or has some sane advice for this i18n
site, I am listening.

Thanks,
-Sean