[rt-users] Bug in history/UTF-8-encoding?

[Benjamin Weser]

Hi List,

seems there are some more problems with UTF-8-encoding. Today it 
happened to us that a ticket's history isn't shown completely. Only the 
last two entries are shown - no create Ticket etc. are visible anymore. 
I've found the following errors in the log file:

[Tue Dec 11 08:56:38 2007] [warning]: Malformed UTF-8 character 
(unexpected continuation byte 0xb0, with no preceding start byte) in 
substitution iterator at /usr/lib/perl5/5.8.8/Text/Tabs.pm line 26. 
(/usr/lib/perl5/5.8.8/Text/Tabs.pm:26)
[Tue Dec 11 08:56:38 2007] [warning]: Malformed UTF-8 character 
(unexpected continuation byte 0xb2, with no preceding start byte) in 
substitution iterator at /usr/lib/perl5/5.8.8/Text/Tabs.pm line 26. 
(/usr/lib/perl5/5.8.8/Text/Tabs.pm:26)
[Tue Dec 11 08:56:38 2007] [warning]: Malformed UTF-8 character 
(unexpected continuation byte 0xb0, with no preceding start byte) in 
substitution iterator at /usr/lib/perl5/5.8.8/Text/Tabs.pm line 26. 
(/usr/lib/perl5/5.8.8/Text/Tabs.pm:26)
[Tue Dec 11 08:58:40 2007] [warning]: Malformed UTF-8 character 
(unexpected continuation byte 0xb0, with no preceding start byte) in 
substitution iterator at /usr/lib/perl5/5.8.8/Text/Tabs.pm line 26. 
(/usr/lib/perl5/5.8.8/Text/Tabs.pm:26)
[Tue Dec 11 08:58:40 2007] [warning]: Malformed UTF-8 character 
(unexpected continuation byte 0xb2, with no preceding start byte) in 
substitution iterator at /usr/lib/perl5/5.8.8/Text/Tabs.pm line 26. 
(/usr/lib/perl5/5.8.8/Text/Tabs.pm:26)
[Tue Dec 11 08:58:40 2007] [warning]: Malformed UTF-8 character 
(unexpected continuation byte 0xb0, with no preceding start byte) in 
substitution iterator at /usr/lib/perl5/5.8.8/Text/Tabs.pm line 26. 
(/usr/lib/perl5/5.8.8/Text/Tabs.pm:26)
...

Probably some Russian letters were used there since the error happened 
after an update of an employee of our Russian team. But I'm not sure 
about that since there are many tickets with Russian descriptions where 
no errors occured.

Are there any ideas how to fix this except manipulating the data in the 
database directly?

Best regards,
Ben