On Thursday, June 10, 2004 4:43 AM
Boris Ratner
The problem was occuring when i tried to send 'iso-8859-8' encoded mail to otrs 1.2.3 *with* DefaultCharset->utf-8 set. I used Mozilla-mail to do this. Mozilla mail sends 'iso-8859-8' encoded mail with encoding set to 'iso-8859-8-i'.
One could think of Mozilla handling 8859-8-I, which is a LTR language, the same way as 8859-8, which is to be written RTL. So Mozilla changed the language direction to its wish? Um...
example:" From: =?ISO-8859-8-I?Q?=E1=E5=F8=E9=F1_=F8=E0=E8=F0=F8?= " Perl Encode module doesn't have this encoding or alias - so i have
From http://search.cpan.org/~dankogai/Encode-2.01/lib/Encode/Supported.pod: "ISO-8859-8-1 [Hebrew] None of the Encode team knows Hebrew enough (ISO-8859-8, cp1255 and MacHebrew are supported because and just because there were mappings available at http://www.unicode.org/). Contributions welcome."
added it as an alias to the "normal" form in /usr/lib/perl/5.8.4/Encode/Alias.pm. Now mail arrives successfully and it looks great on QueueView and ArticleZoom.
This is because you yourself composed a iso-8859-8 message, which was flagged incorrectly by your mailer as iso-8859-8-i, which in the end you mapped to iso-8859-8 again.
In article_plain table (or "plain" view)this mail look wrong. The message text (pain_text message , no attachments) was encoded wrongly to UTF-8 and displays totaly wrong charachters. I've verified that browser encoding is UTF-8 and used unicode terminal to view the content of article_plain to double check that .
I have no idea about that. What does happen to a mail originally sent as iso-8859-8 instead of its counterpart, -i? Regards, Robert Kehl -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Tel. +49 (0)6172 4832388