Hi Justin-san,
Thank you for your reply.
I received a private message from Okada-san with the post from
Murai-san which leads to a character corruption.
Here is the source:
---BEGIN
44GK5LmF44GX44G244KK44Gn44GZ44CC5p2R5LqV44Gn44GZ44CCDQoNCuS5heOAheOBrlBvb3Rl
bOabtOaWsOOBp+OBmSAoNeODtuaciOOBtuOCij8p44CC5YaF5a6556K66KqN44GK6aGY44GE44GE
44Gf44GX44G+44GZ44CCDQpodHRwOi8vd3d3LmphZGUuZHRpLm5lLmpwL35tdXJhaS9oYWlrdS9q
YV9jYXRrZXlzXzIwMTYxMC50eHQuemlwDQoNCiJJIGtub3cgd2hhdCBJJ20gZG9pbmciIOOBruOB
hOOBhOios+OBquOBhOOBp+OBmeOBiz8NCg0K44Gn44GvDQoNCuS7iuWbnuOBruWkieabtOeCuQ0K
MTAvMjkNCmh0dHA6Ly9jZ2l0LmhhaWt1LW9zLm9yZy9oYWlrdS9jb21taXQvP2lkPTczOTNkYWU2
MzEyODQ0MTk5OTgzYzhhODU2M2ZjZGQwMjE1ZDgwMjUNCg==
-----------------------------------------------------------------------
Haiku Project: http://haiku-os.org
Japanese translation/localization: haiku-i18n-jp@xxxxxxxxxxxxx
Message archive: //www.freelists.org/archive/haiku-i18n-jp
---END
Without the footers, these base64 strings can be decoded to valid
UTF-8 Japanese strings,
but with the footers, these cannot be recovered.
Try this:
<https://www.base64decode.org/>
Yours,
log-1
2016-12-10 21:07 GMT+09:00 Justin Stressman <jstressman@xxxxxxxxx>:
Eguchi-san,-----------------------------------------------------------------------
I don't think base64 encoding is the problem.
The text is being encoded as "Content-Type: text/plain; charset=UTF-8"
Then the entire message is being encoded as base64.
An explanation of how this works can be found here:
http://www.sljfaq.org/afaq/encodings.html#encodings-In-e-mail
Basically the text itself is encoded as UTF-8, then the entire message is
turned into a base64 7bit string in order to ensure that it isn't corrupted
by outdated mail server or client software along the way.
The client at the other end should receive the 7bit base64 encoded string
and then decode that back into a utf-8 message.
It looks like what is happening is that the mail client is assuming SJIS
rather than displaying it properly as UTF-8.
So you end up with 文字化け.
That's a problem with the client handling of the "content-type" text
encoding itself of UTF-8, not the "content-transfer-encoding" of base64.
It is clearly able to decode the base64 back into the normal text message.
It just uses the wrong text encoding, Shift_JIS rather than UTF-8, to render
the message itself.
On Mon, Dec 5, 2016 at 9:30 AM Satoshi Eguchi <satoshieguchi82@xxxxxxxxx>
wrote:
Hi all,
I write this message in English to prevent it being encoded in base64.
# but this mail may be encoded base64 anyway...
I found that the message sent by Okada-san with Apple Mail client
was also encoded in base64;
to my understanding, modern e-mail clients tend to use base64 encoding.
Murai-san's using Thunderbird and plain text encoding can solve this
problem temporally, but others cannot post any messages from their
e-mail clients correctly, so this is not a fundamental solution.
I think that we should take away the footers inserted by the freelists
server.
How do you think about this?
Yours,
log-1
-----------------------------------------------------------------------
Haiku Project: http://haiku-os.org
Japanese translation/localization: haiku-i18n-jp@xxxxxxxxxxxxx
Message archive: //www.freelists.org/archive/haiku-i18n-jp
