[Fwd: Re: [Nuxeo-localizer] Re: [Zope] NuxDocument Nonfunctional]

[Fermigier Stefane]

> -----Forwarded Message-----
> 
> From: Myroslav Opyr <myroslav@zope.net.ua>
> To: fg@nuxeo.com
> Cc: nuxeo-localizer@nongnu.org, damon@hddesign.com, zope@zope.org
> Subject: Re: [Nuxeo-localizer] Re: [Zope] NuxDocument Nonfunctional
> Date: 28 Jan 2003 18:58:49 +0200
> 
> Florent Guillaume wrote:
> 
> >Apparently Localizer (in fact, python gettext module) didn't correctly
> >parse the charset of the .po files... Are they standard .po files? There
> >should be a Content-Type: xxx; charset=foo header in them.
> >
> >If you could add debug statements to /local/lib/python2.1/gettext.py to
> >track this down it would be helpful.
> >
> Florent, why Zope Product would require Localizer to be installed to 
> function correctly? We've just removed all gettext form .dtml files to 
> make it work. ZMI is mainly in English and that is pretty good solution 
> until Zope provide Basement for Product l10n. Until that time I see no 
> reason to force users to install Localizer just to see ZMI of that one 
> product (NuxDocument in our case) in other language. Note, there is no 
> fallback mechanism to make it work without Localizer installed.

Feel free to write one, it will be included in the next release. If you
don't, it's in my TODO list for the project.

> And here is the case to mention our NuxDocument patch. We had to remocve 
> all convesions because NuxDocument just corrupted generated HTML from 
> wvWare which was perfect for use in our case (UTF-8 encoding). 

The default interface is in latin-1. The probleme is when wvWare
produces output in UTF-8 that gets included in a Latin-1 interface, and
in that case, the sensible thing to do is to convert everything to a
common encoding. As you are aware, some work is needed to support
non-latin-1 interface. Feel free to write a patch that would permit the
component user to choose between UTF-8 or Latin-1 (or even other
encodings) using the web interface.

> What maillist is correct place for discussion of NuxDocument?

It's in the README: "Send bug reports or comments to -> sf@nuxeo.com".
You can also use the cps-users list
(http://www.nuxeo.com/cps/mailman/listinfo/cps-users) since NuxDocument
is now a part of the CPS framework.

	S.