[horde] enable UTF-8 then cause these problems
david at thbuo.gov.tw
Mon Jan 27 17:44:36 PST 2003
?Â¥?Â¼???Â§???Â¨ Jan Schneider <jan at horde.org>:
> Zitat von David Chang <david at thbuo.gov.tw>:
> > ??Â§???Â¼??Â§?Â¿?Â¹????Â§?Â¦?Â®????Â§?Â©?Â¡ Jan Schneider <jan at horde.org>:
> > > Zitat von David Chang <david at thbuo.gov.tw>:
> > >
> > > > > > Folders that created (before UTF-8 enable) with Chinese format
> > ,did
> > > > not
> > > > > > display
> > > > > > in Chinese format since UTF-8 was enabled.
> > > > >
> > > > > How did you create the folders? With IMP? With another mail client.
> > > > >
> > > > Old folder was created by IMP (which UTF is disable).
> > >
> > > Ah, then I bet the folders names were garbled if you viewed them with
> > > another client?
> > > Anyway, renaming the folders with IMP or another client should work now
> > and
> > > create folder names that are viewable by any mail client.
> > Yes renaming is working,but IMP seems doesn't transfer it automaticly
> > from
> > zh_TW charset to UTF8.
> Sorry, I lost you here completely.
> > > Great, do you still see any other problems, except those we discussed
> > before?
> > >
> > > Jan.
> > Till now here are what i found :
> > 1.When search contacts in Turba with ldap backend.All results no longer
> > in
> > Chinese format.eg, name,address .
> > Here are partial settings in turba/config/source.php
> > 'server' => 'ldap.example.com',
> > 'port' => 389,
> > 'root' => 'dc=test,dc=example.com',
> > 'bind_dn' => 'cn=root,dc=test,dc=example.com',
> > 'bind_password' => '******',
> > 'dn' => array('cn'),
> > 'objectclass' => 'person',
> > 'charset' => 'UTF8',
> > 'version' => 2
> I don't have an ldap server available, so I can't test this. But if this is
> really your setting and your ldap server really stores the data utf8
> encoded, try to set 'charset' to 'UTF-8' (with the hyphen).
Still the same result,after update via cvs few minutes ago.
> > 2.Turba/Nag/Mnemo/Kronolith export file with incorrect charset format.
> Try Turba now. If it works I'll fix the other apps too.
> What I do is to export the data in the charset that the storage backend has.
> It used to be exported in the charset of the ui. I think this solution makes
> more sense.
Great,it's work here,thanks !
> Hm, know that I think about it, it makes perhaps even more sense to export
> it in the orginal charset of the translation.
> > 3.Could not see Chinese content when import in Turba ,if file are
> > exported from
> > outlook/express.(Such import/export problems also happen in
> > Nag/Kronolith/Mnemo)
> This is really a difficult problem. How do we know what charset the data has
> that is going to be imported? The cleanest solution would be to let the user
> This might get difficult because most users probably don't know about
> Another problem is, what charsets do we offer? The ones from nls.php?
> Another list generated from an external source?
For import issue:This problem just happen when UTF-8 is enabled,thus let user
select charset ,if UTF8 is enabled.
> > 4.In gollem,file name did not look right,if it's original
> > file name is Chinese format.
> What backend do you use for Gollem?
ftp,sql(mysql) & file
More information about the horde