Re: よさほい節

On 11 Jan 2007 19:50:28 -0800, dareka@xxxxxxxxx wrote:

Phil Yff wrote:
On 10 Jan 2007 19:55:57 -0800, dareka@xxxxxxxxx wrote:

Phil Yff wrote:
On Wed, 10 Jan 2007 00:00:46 +0900, dareka wrote:

My guess 2: Mac sucks, If understand correctly, UTF8 encoded
in base64 or other 7bit encoding is "recommended" on the
Internet

Nobody recommends base64 for text newsgroups, lots of people point
out that it sucks.

Then simply UTF8 is not supposed to be used. It is a 8-bit
encoding. And my first guess is available.

UTF-8 is one of the most versatile encoding schemes for people that want to
mix several languages in a document.

Then why people who want to send the mixed languages text don't use
UTF-7 instead of UTF-8 if they don't bother to dencode/encode it in
7bit encoding as base64? Or ISO-2022?
Aside from the fundamental problems Unicode has, I really don't
understand those pepole's arrogant attitude.

UTF-8 is more capable and in wider use than UTF-7. In spite of some
difficulties, it is the best existing standard to globalize e-mail and
Usenet. In other words, any number of languages in a single document that
can be read on any moderately current platform.

ISO-2022 is great for Japanese and Japanese-English documents but does not
support multi-lingual documents.

ISO-2022 ≠ IS-2022-JP
I'm not sure that it's even ISO-2022 ⊃ ISO-2022-JP or the ISO-2022-JP
what we usually see is actually is "correct" ISO-2022-JP.
By the way, if you are speaking about multi-lingual encoding.
ISO-2022-JP-2 or 3 or the like supports more "langauages" if a support
means the characters the languages have.

Agreed ISO-2022 ≠ IS-2022-JP. In the short test I conducted, I was able to
get up to three languages with different encoding schemes in my post using
ISO-2022-JP. Even with extensions, there is still a limit to what you can
do with it. It does not purport to be a global encoding scheme. In
contrast, with UTF-8, you can include dozens of languages in a single
document.

Phil Yff
.

Relevant Pages

  • Re: page encoding question
    ... >> I would like to know is what encoding would be most effective for these ... > content-type header indicating the encoding), the Western European ... > languages you are using should work all right in the standard Western ... iso-8859-1 at the moment but I am going to change it into UTF-8 to add the ...
    (alt.html)
  • Re: page encoding question
    ... They are all covered by the ISO-8859-1 encoding, ... whereas UTF-8 uses two bytes for some of the characters you'd use). ... characters in other languages. ...
    (alt.html)
  • Re: use of small kana on the increase?
    ... No way to change the preferences for encoding. ... The page where you enter the text is UTF-8 by default. ... In any case if there's Japanese text in the post it turns out as Base64. ... Unless there's some hidden trick for that I missed it looks like ...
    (sci.lang.japan)
  • Re: Foreign language characters in forms
    ... For web publishing lots of people chooses utf-8 when they must deal with content in different languages, and it's not a bad choice as almost all browsers now offers good implementations of this encoding (while utf-8 is not always a goof choice for certain languages in particular, for exemple cjk). ...
    (comp.infosystems.www.authoring.html)
  • Re: EDICT: azumashii
    ... The encoding and font is a real headache for me as I use three ... languages side by side in my PC. ... Since you're using the internet and browser to post, ... Cut and paste from the reopened file into the compose message ...
    (sci.lang.japan)