<?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>convert_prefs_to_sql.php and german Umlauts</title> 
  <pubDate>Fri, 10 Apr 2026 18:48:25 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/9076</link> 
  <atom:link rel="self" type="application/rss+xml" title="convert_prefs_to_sql.php and german Umlauts" href="https://bugs.horde.org/ticket/9076/rss" /> 
  <description>convert_prefs_to_sql.php and german Umlauts</description> 
 
   
   
  <item> 
   <title>Hi.

We did an upgrade from an old Ingo (v1.0) to the curr</title> 
   <description>Hi.

We did an upgrade from an old Ingo (v1.0) to the current stable version (v1.2.4).

We used the script convert_prefs_to_sql.php and no errors were detected. So everything seemed to work fine.

But now we determine an error. The old prefs-records with german Umlauts didn&#039;t convert to the new db tables. So many filters are lost. The script ignores the complete record if there is a german Umlaut in it.

We suppose that this is a bug in the script.

Can anyone confirm this?

Regards,
Mario</description> 
   <pubDate>Mon, 07 Jun 2010 08:37:19 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9076#t59037</link> 
  </item> 
   
  <item> 
   <title>Hi.

We found the cause. There was a problem with the char</title> 
   <description>Hi.

We found the cause. There was a problem with the character set in mysql. Therefore, some german umlauts were interpreted as y.

So thats not a problem with the ingo convert script.

Regards,
Mario
</description> 
   <pubDate>Tue, 15 Jun 2010 10:32:11 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9076#t59124</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
