Re: How to change OE so the coding is right automatically
- From: "Paul Blay" <blay.paul@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 15 Jul 2006 06:36:01 GMT
"Phil" <phil.yff@xxxxxxxxxxxx> wrote ...
I thought I'd had OE set up correctly, but I went to the site you
mentioned and followed the instructions. I have to commend you it's
very well written. I first tried posting from OE to misc.test typing
in a sample sentence using the input method editor set to Japanese IME
standard, hiragana input, and general conversion mode. It worked
perfectly. However, when I tried to reply to someone else's post, I
could not even decode the Japanese text in the posted message. The
text was garbled whether I tried to pull up the post on Outlook Express
or using a browser.
You're going to have to be more precise about what you were doing there.
However, when I tried to reply to someone else's post, I
could not even decode the Japanese text in the posted message.
Is "the Japanese text" text in the message you were replying to?
Did the message you were replying to include charset information in the headers?
The
text was garbled whether I tried to pull up the post on Outlook Express
or using a browser.
Is "the post" in this case the post you made in replying to someone or the post you were replying to?
In fact links to the posts in question would probably be a good idea.
Ah, found them.
news:pKqdnVBMivd2aSrZnZ2dnUVZ_rOdnZ2d@xxxxxxxxxxxx
That is in Unicode(UTF-7). As Jim would probably say, don't use
UTF-7 - it sucks.
"I guess they use UTF-7 because it supports the older browsers.""They" only use UTF-7 when you select UTF-7 (or sometimes when you reply to a post in UTF-7). Your posts in misc.test were in "iso-2022-jp" / Japanese(JIS) which is pretty much the default.
I'd kind of expected the technology would have advanced to the point that
everything would be handled automatically.
Newsreader software is in rather a dead-end of software development.
OE itself has 'advanced' from dangerously insecure and ludicrously buggy
to not overly secure and somewhat buggy but they have made no real effort to improve its capabilities.
The problem seems to be at its worst when I create the Japanese text
directly in OE. If I use a word processor and cut and paste into OE
the problem is less severe.
That cut and paste should be different from direct input is more than slightly odd. Given the way OE works the content should be byte-by-byte
identical whichever way you get the text in there.
I had no problems reading a response I'd created that way to somebody else's post. However, he was not able to automatically decode the text. He finally did so using ISO-2022-JP. However, I had created it in UTF-8 and when I switched to ISO-2022-JP all of the Japanese and some of the English became garbled.
By "created in UTF-8" do you mean "Selected Unicode(UTF-8) as the format before
posting" ? .
- Follow-Ups:
- References:
- How to change OE so the coding is right automatically
- From: Konrad Viltersten
- Re: How to change OE so the coding is right automatically
- From: Phil
- Re: How to change OE so the coding is right automatically
- From: Paul Blay
- Re: How to change OE so the coding is right automatically
- From: Phil
- How to change OE so the coding is right automatically
- Prev by Date: Re: "A fake form of old-fashioned Japanese speech supposed to represent the old style of the language is used."
- Next by Date: Re: Query: Use of WO where DE is expected.
- Previous by thread: Re: How to change OE so the coding is right automatically
- Next by thread: Re: How to change OE so the coding is right automatically
- Index(es):
Relevant Pages
|
