[kronolith] DB conversion creates 'rampage_tags' with broken umlaut marks (webmail 1.2.8 to HordeGW 5.0.2)

[Jan Schneider]

Zitat von Herbert Pophal <pophal at tubit.tu-berlin.de>:

> On 02/25/2013 12:22 PM, Jan Schneider wrote:
>>
>> Zitat von Herbert Pophal <pophal at tubit.tu-berlin.de>:
>>
>>> Dear Horde folks,
>>>
>>> After having lower cased all(?) DB columns being user names before
>>> converting the database for our migration from Webmail Edition 1.2.8 to
>>> 5.0.2 I experience another DB issue.
>>>
>>> The newly created table  'rampage_tags' contains entries where tag_name
>>> equals '?bungsbl?tter' or '1. Priorit?t' instead of what I did expect:
>>> 'Übungsblätter' resp. '1. Priorität'.
>>>
>>> Is this correct? If not, what could have caused this? Which character
>>> set conversion went wrong?
>>>
>>> Which purpose does this table serve for?
>>>
>>> Environment: RHEL 6.3
>>>              PHP 5.3.3 (RedHat Packages) driven by mod_fcgid
>>>              Separate PEAR Installation of Horde Groupware 5.0.2
>>>
>>>
>>> Thanks in advance.
>>>
>>> Herbert
>>
>> Sounds like you changed database charsets during the migration, e.g.
>> used iso-8859-1 in Horde 3 but utf-8 now.
>
> Though I would like to use utf8 now in order to cover more languages, I
> did not since I fear to garble some serialized strings.
>
> Horde 3 config/conf.php: $conf['sql']['charset'] = 'iso-8859-1';
> Horde 5 config/conf.php: $conf['sql']['charset'] = 'iso-8859-1';
>
>
> Herbert

And how about the newly created tables for Horde 5? They use the  
default charset of teh database, at least on MySQL, so those might be  
utf-8.
You might also have custom SQL configurations that do not use the  
default Horde DB settings, so check those too.
-- 
Jan Schneider
The Horde Project
http://www.horde.org/