nuxeo-localizer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nuxeo-localizer] Problems with UTF-8 vs Latin-1


From: Juan David Ibáñez Palomar
Subject: Re: [Nuxeo-localizer] Problems with UTF-8 vs Latin-1
Date: Tue, 04 Mar 2003 11:19:06 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021204 Debian/1.2.1-1


First, apologies to reply so late..

And now to the problem, the character encoding of the Localizer
management screens is hardocoded to UTF8, it is a Localizer's
policy, different that the Zope's one. The "management_page_charset"
variable does not change anything to Localizer.

If you use a modern browser your management screen should be in UTF8,
unless you change it manually, what would be a very bad idea, because
with the line "name="es:utf8:ustring" Localizer says ZPublisher that
the information the browser sends is encoded in UTF8, so it is better
if it really is.

When a normal string is mixed with an unicode string it is
automatically changed to unicode and it is interpreted as ASCII (by
default) used. If there is a non ASCII character, for example an
accentuated vowel the "ASCII encoding error: ordinal not in range(128)"
is raised.

Why this happens to you in this context? I don't know. I would need
the whole traceback for instance.




Garikoitz Araolaza wrote:

Thanks Milos!

But no... it doesn't work.

I even don't have any doc/CHANGES.txt

I did a grep inside my Localizer install and only found a vague reference to the management_page_charset

Any other hint from someone else?

Am I the only one with this problem?

Gari

At 16:44 26/02/03, you wrote:

Garikoitz Araolaza wrote:

All my sites using Localizer were created before the Zope 2.6.1 and Localizer 1.0
I do most of my edit within Zope's and Localizer's manage pages.
Lastly I'm getting this error while editing LocalContent objects with Latin-1 chars:


Try to add certain property to your root folder.

The property name must be "management_page_charset"

Property value may be "iso-9959-1"... I'm not sure.

Is it better now?

This is unsatisfactorily documented in doc/CHANGES.txt

--
Milos Prudek






_______________________________________
Garikoitz Araolaza
Code&Syntax
address@hidden

BIC-Berrilan
Azitaingo Industrialdea
E-20600-EIBAR
Tel: +34 943 82 06 06




_______________________________________________
Nuxeo-localizer mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/nuxeo-localizer



--
J. David Ibáñez, http://www.j-david.net
Software Engineer / Ingénieur Logiciel / Ingeniero de Software






reply via email to

[Prev in Thread] Current Thread [Next in Thread]