[#7022] Encode problem in full name
Summary Encode problem in full name
Queue Horde Base
Queue Version 3.2.1
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester voyager (at) centrum (dot) cz
Created 07/04/2008 (364 days ago)
Due
Updated 07/09/2008 (359 days ago)
Assigned 07/04/2008 (364 days ago)
Resolved 07/07/2008 (361 days ago)
Attachments
Milestone
Patch No

History
07/09/2008 voyager (at) centrum (dot) cz Comment #5 Reply to this comment
I'm afraid I don't know either. I suspect some brokenness in your 
iconv of mbstring extensions/libraries. But since Horde is generally 
converting the characters correctly, this is not a bug in Horde.
Ok, maybe this help to solve my problem. I try to comment lines for 
iconv and mbstring in function _convertCharset($input, $from, $to) in 
String.php file and it works! full name shows perfectly all character. 
Of course any other conversions in sidebar or Inbox mails shows all 
national characters wrong. Is it conversion for Main Horde page 
different from conversion for sidebar and inbox mails? I have 
$nls['defaults']['charset'] = 'ISO-8859-2'; in nls.php but in 
_prefs_hook_fullname $ldapcharset I must set Windows-1250 because with 
'ISO-8859-2' it didn't work. Maybe here is a problem. Do you have any 
suggestions?
07/07/2008 Jan Schneider Comment #4
State ⇒ Not A Bug		 Reply to this comment
I'm afraid I don't know either. I suspect some brokenness in your 
iconv of mbstring extensions/libraries. But since Horde is generally 
converting the characters correctly, this is not a bug in Horde.
07/07/2008 voyager (at) centrum (dot) cz Comment #3 Reply to this comment
So, are you saying the charset conversion works with any other 
non-ascii character? I have no idea how we could help you in this 
case, because we don't do the charset conversion ourselves, of course.
Yes, any other characters show fine. I see below in my first post that this character display wrong. So, again by words it is 'n' with caron(Unicode: 02C7) above. I donīt understand why this is do only with this one character :(
07/04/2008 Jan Schneider Comment #2
Priority ⇒ 1. Low
State ⇒ Feedback		 Reply to this comment
So, are you saying the charset conversion works with any other 
non-ascii character? I have no idea how we could help you in this 
case, because we don't do the charset conversion ourselves, of course.
07/04/2008 voyager (at) centrum (dot) cz Comment #1
Patch ⇒
Milestone ⇒
Summary ⇒ Encode problem in full name
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 3. High
Queue ⇒ Horde Base		 Reply to this comment
I use cs_CZ locale and read full name from LDAP. Every characters in full names show correctly except one, it is a 'ō' character, it show two question mark ?? instead. I try to change convertCharset in prefs_hook_fullname but nothing do all right. I also try to unlock prefs fullname and write name correctly but with same result.