<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Encode problem in full name</title> 
  <pubDate>Fri, 10 Apr 2026 09:35:33 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7022</link> 
  <atom:link rel="self" type="application/rss+xml" title="Encode problem in full name" href="https://bugs.horde.org/ticket/7022/rss" /> 
  <description>Encode problem in full name</description> 
 
   
   
  <item> 
   <title>I use cs_CZ locale and read full name from LDAP. Every chara</title> 
   <description>I use cs_CZ locale and read full name from LDAP. Every characters in full names show correctly except one, it is a &#039;ò&#039; 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. </description> 
   <pubDate>Fri, 04 Jul 2008 09:25:04 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7022#t47197</link> 
  </item> 
   
  <item> 
   <title>So, are you saying the charset conversion works with any oth</title> 
   <description>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&#039;t do the charset conversion ourselves, of course.</description> 
   <pubDate>Fri, 04 Jul 2008 16:46:03 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7022#t47217</link> 
  </item> 
   
  <item> 
   <title>&gt; So, are you saying the charset conversion works with any o</title> 
   <description>&gt; So, are you saying the charset conversion works with any other 

&gt; non-ascii character? I have no idea how we could help you in this 

&gt; case, because we don&#039;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 &#039;n&#039; with caron(Unicode: 02C7) above. I don´t understand why this is do only with this one character :(</description> 
   <pubDate>Mon, 07 Jul 2008 11:55:15 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7022#t47346</link> 
  </item> 
   
  <item> 
   <title>I&#039;m afraid I don&#039;t know either. I suspect some brokenness in</title> 
   <description>I&#039;m afraid I don&#039;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.</description> 
   <pubDate>Mon, 07 Jul 2008 12:44:41 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7022#t47347</link> 
  </item> 
   
  <item> 
   <title>&gt; I&#039;m afraid I don&#039;t know either. I suspect some brokenness </title> 
   <description>&gt; I&#039;m afraid I don&#039;t know either. I suspect some brokenness in your 

&gt; iconv of mbstring extensions/libraries. But since Horde is generally 

&gt; 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[&#039;defaults&#039;][&#039;charset&#039;] = &#039;ISO-8859-2&#039;; in nls.php but in _prefs_hook_fullname $ldapcharset I must set Windows-1250 because with &#039;ISO-8859-2&#039; it didn&#039;t work. Maybe here is a problem. Do you have any suggestions?</description> 
   <pubDate>Wed, 09 Jul 2008 14:39:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7022#t47405</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
