Thanks for that Stanislav,
I will have a look into helping out with the po (but I am really new to this
so I hope I can catch up quick enough…)
However, to solve my little problem I was thinking of a hack that I would
appreciate your opinion about.
Since iso-8895-8-i can be an alias to iso-8895-8 I was thinking about using
Text::Iconv to convert the body of the message,
(if and only if the char set is indeed iso-8895-8-i)
something like :
— /opt/rt3/lib/RT/I18N.pm in the function SetMIMEEntityToEnconding (line
284 in build 2.1.85…)
if char set contains iso-8859-8-i then convert body from iso-8859-8 to utf-8
and set the char set to utf-8…
and carry on as usual…
Do you think this can work or is this a complete flunk I’m heading into?
I am a newbie to encodings and the likes…
[mailto:firstname.lastname@example.org]On Behalf Of Stanislav Sinyagin
Sent: Tuesday, March 11, 2003 7:18 PM
To: Ron Gidron; Rt-Devel
Subject: RE: [rt-devel] Unknown encoding ‘iso-8859-8-i’ at
/opt/rt3/lib/RT/I18N.pm line 270
I am running Linux Mandrake 9.0,
My perl is v5.8.0 built for i386-linux-thread-multi
Then it’s “easier”…
The incoming email was in Hebrew encoding ‘iso-8859-8-i’,
and the current Encode-1.91 does not support Hebrew completely:
As I could read from your company homepage, Hebrew support is of
significance to your company. Then, the best way would be if your
colleagues could help Encode authors to implement this support.
Otherwise, they need to change the encoding settings in their
BTW - do you think I can benefit anything (only in this regard) from
upgrading to 2.1.85?
not really. You see, it’s the problem in external module.
rt-devel mailing list