I18N issues with 3.0.3pre1

RT Developers
1

Hi,

It seems like most of the I18N issues has been sorted out, the one
remaining issues seems to be the subject of outgoing mails.

The subject seems to be correctly converted to UTF-8, but the encoding
is tagged as ISO8859-1.

Here is an example:
=?ISO-8859-1?Q?p=C3=A5?= ADSL i Sandefjord

(The linebreak is mine)

BTW: RT flies with me, which it should considering the hardware I’ve
thrown at it :slight_smile:

IBM x335 server with 1Gb RAM with uniprocessor P4-Xeon 2.40GHz

Roy-Magne Mo

2

The subject seems to be correctly converted to UTF-8, but the encoding
is tagged as ISO8859-1.

Here is an example:
Subject: [BlueCom #246] AutoReply: Flytte telefoni over
=?ISO-8859-1?Q?p=C3=A5?= ADSL i Sandefjord

Action/SendEmail’s invocation of encode_mimewords is very very
very borked. See the patch below.

/Autrijus/

— /home/autrijus/depot/RT/import/lib/RT/Action/SendEmail.pm Thu May 29 05:55:03 2003
+++ SendEmail.pm Mon Jun 2 14:16:16 2003
@@ -589,7 +589,7 @@
# See RT::I18N, ‘NOTES: Why Encode::_utf8_off before Encode::from_to’
Encode::_utf8_off($value);
my $res = Encode::from_to( $value, “utf-8”, $enc );

  • $value = encode_mimewords( $value, ‘b’, $enc );
  • $value = encode_mimewords( $value, Encoding => ‘b’, Charset => $enc );
    $self->TemplateObj->MIMEObj->head->replace( $field, $value );
    }
3

Hello,

Action/SendEmail’s invocation of encode_mimewords is very very
very borked. See the patch below.

/Autrijus/

— /home/autrijus/depot/RT/import/lib/RT/Action/SendEmail.pm Thu May 29 05:55:03 2003
+++ SendEmail.pm Mon Jun 2 14:16:16 2003
@@ -589,7 +589,7 @@
# See RT::I18N, ‘NOTES: Why Encode::_utf8_off before Encode::from_to’
Encode::_utf8_off($value);
my $res = Encode::from_to( $value, “utf-8”, $enc );

  • $value = encode_mimewords( $value, ‘b’, $enc );
  • $value = encode_mimewords( $value, Encoding => ‘b’, Charset => $enc );
    $self->TemplateObj->MIMEObj->head->replace( $field, $value );
    }

I have applied the patch. Email encoding for sending works much better.
But I have still problems with “umlauts” in the german WebUI.
It seems that only “umlauts” displayed in the main part (downright)
of the window are broken.
The characters in the left navigation bar are correct.

Regards
Torsten

4

Action/SendEmail’s invocation of encode_mimewords is very very
very borked. See the patch below.

The patch does the trick, thanks

I’ve found another minor one:

Sending the mail below:

Message-ID: <3EDCCF0C.8090409@xxxx.xxxx> User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030530 X-Accept-Language: nn, en-us, no MIME-Version: 1.0 =?ISO-8859-1?Q?=D8=C5?= Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit

sdaf
asd
fas
df
sdf

Inserts the subject correctly as the subject of the case, but when I try
to edit it or look at the first entry in the case, the subject stops
where the newline is inserted in the subject in the mail.

And I didn’t recieve any mail back that the ticket was created, checking
the log gives this:

[Tue Jun 3 16:38:37 2003] [debug]: Converting ‘us-ascii’ to ‘utf-8’
(/usr/local/rt3/lib/RT/I18N.pm:211)
[Tue Jun 3 16:38:38 2003] [error]: error: couldn’t parse head; error
near:
<98><85>

(/usr/local/rt3/lib/RT/Template_Overlay.pm:345)
[Tue Jun 3 16:38:38 2003] [info]: RT::Scrip=HASH(0x9067e34): Couldn’t
prepare Autoreply To Requestors
(/usr/local/rt3/lib/RT/Scrip_Overlay.pm:338)

Pasting this from less, the characters above is the presentation of
unprintable characters from less.

Roy-Magne Mo