Re: Writing to the newsgroup?

On Mon, 05 Nov 2007 18:13:40 -0700, Arri London wrote:

Phil wrote:

On Mon, 05 Nov 2007 09:13:18 -0700, Arri London wrote:

In Japanese that is. How do people write into the group? Sometimes I see
odd characters that aren't Japanese so assuming I don't have quite the
proper fonts.

However I did find my wp software (Unitype Global writer) that
supposedly lets me write in hiragana and kanji (get to pick and choose
after entering the words in romaji). However cut-and-paste didn't work.
Do I need something different?

Your post was encoded in iso-2022-jp. It should show Japanese fine. I'm
replying with iso-2022-jp. You should be able to read the Japanese I'll
included below as a test.

Another common encoding scheme is UTF-8. UTF-8 and iso-2022-jp should be
able to read each other's Japanese characters. However, if a UTF-8 post
has a number of different languages with different character sets,
iso-2022-jp decoding may not be able to show all of them. Here's a test
passage. It's the opening preamble to an anime show that aired last
season, "Jigoku Shoujo - Hutakomori". I will send it first in iso-2022-jp
and then in UTF-8.

ゆらりゆらりと業の影
哀れな定め　迷い道
憎み憎まれ　ひび割れた
合せ鏡の二籠
時の交わる闇より来たりて
あなたの怨み晴らします

Yurari yurari to gou no kage
Aware na sadame mayoi michi
Nikumi nikumare hibiwareta
Awasekagami no hutakomori
Toki no majiwaru yami yori kitarite
Anata no urami harashimasu

The shadow of karma swings to and fro.
Wretched fate leads one astray.
Hating, being hated - a captive duo - receding
Reflections in a pair of cracked facing mirrors.
Coming forth from the intersection of time intertwined with darkness,
You shall find relief from your torment.

--
Phil

TY it did show up perfectly in the original post, but doesn't show up as
I type the reply.

Nevertheless, I see it perfectly in your reply unlike your reply to the
UTF-8 encoding where the quoted Japanese from my post became garbled. The
header info in your original post, my reply, and your reply to this post
all show the same character encoding info:

Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
--
Phil
.

Relevant Pages

  • Re: Input Character Set Handling
    ... two 8-bit encoded characters matching 208 and 144. ... You wrote that you deal with say Japanese and Korean 'legacy' encodings ... neither for Russian in UTF-8 nor for Japanese ... I don't know why you did not know before about say .HTML files ...
    (comp.lang.javascript)
  • Re: Fast UTF-8 strlen function
    ... > How do I print a UTF-8 string to the console in Linux? ... technically able to render all those characters... ... Did you see my "Japanese Hello World" example? ...
    (alt.lang.asm)
  • Re: FTPFindFirstFile unicode
    ... be encoded using 520 characters in UTF-8, and this might be where the problem is. ... Explorer, choosing the MultiByte tab, pasting the Japanese filename in the top window, and ... It works fine for filenames that have english ...
    (microsoft.public.vc.mfc)
  • Re: Need help with CABWIZ
    ... I thought your previous posting said that CAB files couldn't contain multibyte glyphs. ... CABWIZ isn't the only defective component of the Japanese version of Visual Studio 2005, it's just the part that I needed help with in this thread. ... If we're going to argue about belittling, then revisit your own statement "having Unicode doesn't simply give you Japanese glyph support". ... a limitation on the way that CABWIZ stores it's data - it's single byte characters, so there's no way it can store a multi-byte glyph. ...
    (microsoft.public.pocketpc.developer)
  • Re: FTPFindFirstFile unicode
    ... a 260-character Japanese name would need to ... be encoded using 520 characters in UTF-8, and this might be where the problem is. ... It works fine for filenames that have english ...
    (microsoft.public.vc.mfc)