[Zope-Coders] Re: [ZC] 486/ 2 Comment "Unicode works but fail all non-8859 users."

[kent sin]

but.

How can I change the title's property to utext?

And moreover, it is possible to introduce an
'encoding' variable, which, is by default is set to
anything you like, but it allow the site manager to
change to anything apropriate. The best place for such
an variable  is a proprity of the root of the site.

Rgs,

Kent Sin
--- "Collector: Zope Bugs, Features, and Patches ..."
<zope-coders@zope.org> wrote:
> Issue #486 Update (Comment) "Unicode works but fail
> all non-8859 users."
>  Status Pending, Zope/bug critical
> To followup, visit:
>   http://collector.zope.org/Zope/486
> 
>
==============================================================
> = Comment - Entry #2 by htrd on Jul 24, 2002 9:40 am
> 
> First, thanks for testing this.
> 
> > fail to accept Chinese text for title, which, is
> possible before this changes.
> 
> Yes, if your title property has 'string' type. This
> was always dangerous. It should work if the title
> has 'ustring' type.
> 
> > all manage interface and default zope
> standard_html to force an utf-8 encoding
> 
> Yes, all management pages use latin-1 by default.
> Your unicode 'title' properties wont render
> correctly on a Folder 'contents' page; but you will
> get the true value when it is rendered in your own
> utf8 pages.
> 
> Changing the ZMI to use utf8 is a much riskier step
> - to be tackled experimentally in Zope 2.7
> 
> 
> 
> 
> 
> ________________________________________
> = Request - Entry #1 by Anonymous User on Jul 24,
> 2002 9:14 am
> 
> The current cvs version after unicodedified, which
> accept utext and utoken, fail to accept Chinese text
> for title, which, is possible before this changes.
> 
> The problem can be fixed by changing all manage
> interface and default zope standard_html to force an
> utf-8 encoding. And read the text as utf-8 instead
> of 8859. This is very critical and will stop many
> non-8859 sites working after the cvs go to public. 
> 
> I don't known how many people will be hurted after
> turning to utf-8 as default, but that seems a
> universal acceptable solution because it works
> unnoticeable in windows environment. The user will
> not notice the different, and the browser will send
> out the text in utf-8 automatically. Even, the
> original text is copy from another encoding, windows
> will convert it automatically. 
> 
> This will stop my site, and many in Japaneses,
> Korean, etc. So, please take it carefully.
>
==============================================================
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com