** Observed with 5/3/99 Win32 M6 candidate build ** I sent the following body text including the Hankaku sequence for "mail". これも二本からのﾒｰﾙなり。 Apparently we don't have Hankaku-to-Zenkaku hooked up yet, because what I received was 8-bit Hankaku characters mixed in with the 7-bit JIS. ---------------- Source of the above with relevant headers ********* Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by netscape.com id WAA08208 =1B$@$3$l$bFsK\$+$i$N=1B(J=D2=B0=D9=1B$@$J$j!#=1B(B ---------------- Source of the above with relevant headers ********* Maybe there is some prefs50.js option? In any case, the default should be no Hankaku.
M7. Filed a separte bug (#5909) for the mapping function. Messenger will use it when it's available. We can use mailnews.send_hankaku_kana (same as 4.5).
I tried the pref option (set to false) but it did not work. Are you saying that the pref option will work when the interface utility is checked in? (Bug 5904)
You're right, it won't work until M7, sorry for the confusion.
5909 is fixed, the mapping interface is available. But there is an another issue because of the change 6672. The plan for M7 is that messenger to receive a stream instead of nsString from Ender. Since messenger now gets converted stream (not unicode unless explicitly request), it is not easy to use the new mapping interface which is unicode base. It may be solved by let Ender to do this mapping. This works for mail body but widgets (e.g. subject) may be difficult. This mapping is only needed for mail and it should not be applied for HTML forms for example. Adding email@example.com,firstname.lastname@example.org,email@example.com to cc.
I should wait until the new interface of the Ender to compelete (6672). For headers, need to wait for the Ender widget. Moving to M8.
Adding dependency 6262,6672.
Adding 8865 to dependency. Also moving to M9, it is not likely that I have chance to make this for M8.
Moving to M10.
Post beta feature, M15.
Removing dependency to 8865, hankaku->zenkaku conversion is not included in 8865.
Checked in. Now it maps hankaku to zenkaku for mail send if the charset is "ISO-2022-JP" and the pref "mailnews.send_hankaku_kana" is false or not specified.
** Checked with 2/18/2000 Win32 build ** With both Plain text and HTML mail, Hankaku characters are now converted into Zenkaku characters under ISO-2022-JP setting for send. Marking it fixed verified.
CC'ing marina and ji.