Message-ID: <001101ca9762$293d68c0$0600a8c0@osiris> From: "jsmith" To: Subject: Japanese Character pattern matching Date: Sun, 17 Jan 2010 11:45:18 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CA976A.8AF5E9E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 This is a multi-part message in MIME format. ------=_NextPart_000_000E_01CA976A.8AF5E9E0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable It should be noted that I am receiving emails using pop and the patch in = Issue #2420 but I don't think the problem lies with this. When I try and send emails to the redmine server with Japanese = characters in them it appears to work apart from the pattern matching. For example if I send an email with the following keywords. Tracker: =1B$B3+H/=1B(B ------=_NextPart_000_000E_01CA976A.8AF5E9E0 Content-Type: text/html; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable

It should be noted that I am receiving emails using pop and the patch = in=20 Issue #2420 but I don't think = the=20 problem lies with this.

When I try and send emails to the redmine server with Japanese = characters in=20 them it appears to work apart from the pattern matching.

For example if I send an email with the following keywords.

Tracker: = =1B$B3+H/=1B(B

------=_NextPart_000_000E_01CA976A.8AF5E9E0--