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

[Benjamin Weser]

Sorry, I always forget to add my system configuration:
RT 3.6.4
Apache 2.2.3
MySQL 5.0.26
Perl: v5.8.8


Benjamin Weser schrieb:
> 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
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
>
> If you sign up for a new RT support contract before December 31, we'll 
> take
> up to 20 percent off the price. This sale won't last long, so get in 
> touch today.    Email us at sales at bestpractical.com or call us at +1 
> 617 812 0745.
>
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com