[rt-users] RT: Int. characters in ticket message - I give up :-(

[Autrijus Tang]

On Wed, Jul 02, 2003 at 04:13:20PM +0200, Gerald R?scher wrote:
> The unlauts have been somehow converted and in each line following
> a line containing an umlaut, leading characters are dropped.
> 
> What's going on here?  Commenting on a ticket doesn't involve any
> eMails so why does RT mess up it's own data?  I give up :-)

On Win32 with mysql 4.0.x (but not on Unix) we have been observing
that the SearchBuilder/mysql layer drops the utf8 flag after a while
of normal execution.

The work around here is to apply the following patch to
RT/Attachment_Overlay.pm and add this line to RT_SiteConfig.pm:

    Set( $AlwaysUseBase64, 1 );

which turns on Base64 encoding for all MIME contents.

Thanks,
/Autrijus/

--- //depot/RT/rt/lib/RT/Attachment_Overlay.pm	2003/07/01 18:18:04
+++ //depot/RT/rt/lib/RT/Attachment_Overlay.pm	2003/07/02 09:32:30
@@ -168,8 +168,8 @@
         #if the current attachment contains nulls and the 
         #database doesn't support embedded nulls
 
-        if (    ( !$RT::Handle->BinarySafeBLOBs )
-             && ( $Body =~ /\x00/ ) ) {
+        if ( $RT::AlwaysUseBase64 or
+	     ( !$RT::Handle->BinarySafeBLOBs ) && ( $Body =~ /\x00/ ) ) {
 
             # set a flag telling us to mimencode the attachment
             $ContentEncoding = 'base64';
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20030703/7dfc51f0/attachment.sig>