[otrs] UTF-8 and StdAttachment

Daniel Wedewardt daniel.wedewardt at native-instruments.de
Fri Jan 4 15:03:10 GMT 2008


Hi,

since we changed the DefaultCharset in Kernel/Config.pm from 

  $Self->{'DefaultCharset'} = 'iso-8859-1';
to
  $Self->{'DefaultCharset'} = 'utf-8';

we got trouble with StdAttachments. The DefaultCharset of our MySQL
database is from first day utf-8 (also while iso-8859-1 is the
DefaultCharset in OTRS). A sended answer with a StdAttachment have the
double size than it really is. For sure, after receiving the
Agent-Response-Mail with the standard attachment, it can't be opened. 
When we load a new standard attachment to otrs after switching to utf-8
DefaultCharset and use this new standard attachment, the same thing
happen. It makes no difference.
The table standard_attachment is set to collation utf8_general_ci for
fields name, content_type, filename, comments. All other fields aren't
affected by collations. The content field also has the binary attribute
flag.
When we shortly switch bag to iso, the standard attachment have the
right size and could be read very well on client side.
It looks like, that only database stored attachments are affected by
this issue because uploading an attachment while composing an agent
response article, the attachment could be read very well on client side.

Before I forgot: we're using OTRS 2.2.2. I know, there is OTRS 2.2.4,
but I couldn't find any related documented change in logs.

Bye


Daniel



More information about the otrs mailing list