Re: How to change OE so the coding is right automatically

Paul Blay wrote:
"Phil" <phil.yff@xxxxxxxxxxxx> wrote in evul-printable ...
Paul Blay wrote:

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 agree. That's why I didn't even think of using it until someone told
me he saw the Japanese text using UTF-7.

Hmm, well to be blunt you may not have thought of using it but
(slipped mouse button or whatever) it was almost certainly you
that selected it in the first place.

I've certainly done a lot of things inadvertantly so, under normal
circumstances, this would be a plausible explanation. However, in this
case, UTF-7 was not even an option when I created the post. It was
only later that I activated it.

Yesterday, I downloaded something called 40tude Dialog at
http://www.40tude.com/dialog/. It boasts sophisticated unicode
features.

By the look of it the two big improvements over OE are
1. encoding and decoding of inline encoded header fields
2. support for yEnc

Although the latter won't be any use to you unless you've taken to
sneaking anime files off your newsserver.

I'm interested in language - text, not binary.

By "created in UTF-8" do you mean "Selected Unicode(UTF-8) as the format before
posting" ?

I'd really meant to use the word processor's feature to save a document
as plain text with UTF-8 encoding.

What format you save your text document should be (and as far as I know is)
irrelevant to what format it ends up in your post.

I was doing it more for fault isolation. Creating the document. Saving
it as plain text with encoding. Then opening up the file with a notepad
to try to eliminate any extraneous coding. I still don't understand
why I get different results creating the text within OE and cutting and
pasting from a word processor.

I have a related question that perhaps you can answer. You saw my post
in response to Ueshiba-san. It was the first time I had posted
complete Japanese paragraphs to sci.lang.jap. Because there are no
spaces between Japanese characters, neither Google Groups nor 40tude
Dialog broke up the lines. I thought maybe it would occur during
posting so I did a couple of test runs on misc.test. Each paragraph
still remained as a single long horizontal line. I finally forced in
manual line breaks before I sent it.

I use manual line breaks as a matter of style. I don't know off hand how OE
handles mixed western and Japanese text when using automatically inserted
breaks but it should be easy to test.

I usually have mixed western and Japanese. Since the western has
spaces, OE breaks at one of those spaces.

BTW, when I did my tests, 「森の王」 came out perfectly in each of
them. I have no idea how it got garbled when I posted to s.l.j. It's
a hard enough struggle for me to compose the text to begin with, I
can't afford afford to be distracted by software gliches.

Google Group postings are pretty much a mystery to me. From what I've
observed so far the two most common problems are 1) bits of 文字化け
2) posts being encoded as if binary and being blocked by newsservers.

I had a problem with the latter. When I first tried to post to the
なんじゃこりゃ thread, I tried to answer the thread's
originator, Meredith. Google Groups said I wasn't allowed to post
because s.l.j did not allow binary posts. There was no binary either
in Meredith's post or my response. I tried quite a few variations and
none worked. Finally, I posted to one of the subordinate posts in the
thread and it went thru without incident.

The two most likely things to need checking are preferences / settings in
Google groups and the encoding your browser is using when editing the
post.

Oh, and in Google _mail_ if your Japanese text includes a kanji not in the
'standard' set Google may arbitrarily decide to encode it as Chinese Big-5.

I've never had that problem. If anything 稜 in miitsu - みいつ -
御稜威 would have caused a problem. Yet the only problem I've had
are with grade school kanji and quotation marks.

Phil Yff

.