Re: use of small kana on the increase?

It seems to me I heard somewhere that Paul Blay wrote in article
<4e%eh.1617$1W1.776@xxxxxxxxxxxxxxxxxxxx>:

"Phil Yff" <phil.yff@xxxxxxxxxxxx> wrote ...
On Sun, 10 Dec 2006 18:49:01 GMT, Paul Blay wrote:
First I don't think Google Groups minds base 64, it's the other servers
that don't pick it up (because it looks like binary).

I don't see her posts on a news server that accepts base 64. In fact, I
get Meredith's posts on it when some people don't. I'm not saying you're
wrong. Without tracking the post, all I can do is make an informed guess
based on the info in the header. I see it was posted on Google Groups and
I don't see it on any of the other news servers I have access to. So, my
assumption is it was left out of the Google Groups news feed.

If the _origin_ was Google Groups (and it was for Cindy's post) then if it isn't in
the Google Groups news feed then it gets nowhere at all and thus nobody outside
of Google Groups would ever have seen it.

The headers of Cindy's last previous post that I've received in this
thread, Message-ID:
<1165715409.814993.191350@xxxxxxxxxxxxxxxxxxxxxxxxxxxx, looks like it
was injected into Google via Road Runner; I wonder if that's got
anything to do with the price of fish. That post is set for UTF-8 and
Base 64.

Second I doubt it's the method of inputting Japanese, it's much more
likely to be an inappropriate encoding chosen to view the Google
Groups page when entering the text or some encoding/language
setting in Google Groups preferences.

I think it's a question of semantics. Something is triggering the encoding to
base64 and it is likely it is language related.

The point is that posts via Google Groups posts start as text in a plain-text textbox
on a browser. A textbox that is completely indifferent to _how_ text is generated.
If it's in the textbox and it looks like Japanese on your screen then it makes no
difference how it was typed or where it was pasted from in what format. Thus there
is no plausible benefit to be gained from pasting in text from a wordprocessor (say)
instead of using an IME (as far as 64-bit encoding being used or not).

Incidentally the textbox used to enter text in Outlook Express is _not_ a plain text
textbox which can lead to some interesting (and annoying) 'features'
--
Don Kirkman
.

Relevant Pages

  • Re: How do search engines index multilingual content?
    ... > Andreas Prilop wrote: ... >> Google Groups still ignore the charset parameter of Usenet ... encoding, and only returned pages which used that same encoding. ...
    (comp.infosystems.www.authoring.html)
  • Re: 3Dginput
    ... The reason you have seen 3Dginput is that Google Groups does MIME quoted-printable ... encoding of characters outside the range of printable US-ASCII. ... capital A with the grave accent is character number 192, which is hex C0, ... the encoding for which is equal-sign Cee zero. ...
    (comp.soft-sys.matlab)
  • Re: Enumerate registered codecs
    ... Is there a method to enumerate the registered codecs at runtime? ... Google to search for codecin this newsgroup in Google groups. ... a required encoding or enters an invalid encoding, we need to tell them which encodings are valid and how they are specified. ...
    (comp.lang.python)
  • Re: use of small kana on the increase?
    ... is that you are posting thru Google Groups and Google ... Groups is not sending out your post with its news feed. ... because your posts use base64 content transfer encoding. ...
    (sci.lang.japan)
  • Re: wanadoo news server please
    ... Via Google Groups news is free, ... But PLEASE don't use google groups, ... I use it when away from home, to keep track of things on Usenet simply because my regular internet connections I have access to have Port 119 closed. ... Please replace invalid and invalid with gmx and net to reply. ...
    (uk.telecom.broadband)