Tickets :: [#7022] Encode problem in full name

6.0.0-beta1

7/19/25

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 (6224 days ago)
Due
Updated	07/09/2008 (6219 days ago)
Assigned	07/04/2008 (6224 days ago)
Resolved	07/07/2008 (6221 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/09/2008 02:39:45 PM	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 12:44:41 PM	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 11:55:15 AM	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 04:46:03 PM	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 09:25:04 AM	voyager (at) centrum (dot) cz	Comment #1 Priority ⇒ 3. High Type ⇒ Bug Summary ⇒ Encode problem in full name Queue ⇒ Horde Base Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	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.