Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Admin: TLUG Bank Account Number
- To: tlug@example.com
- Subject: Re: tlug: Admin: TLUG Bank Account Number
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Thu, 30 Oct 1997 19:18:33 +0900 (JST)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=iso-2022-jp
- In-Reply-To: <199710300828.RAA17189@example.com>
- References: <Pine.LNX.3.96.971030135604.372A-100000@example.com><199710300828.RAA17189@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "Alberto" == A Tomita,Jr <Alberto@example.com> writes: Alberto> In message Alberto> <Pine.LNX.3.96.971030135604.372A-100000@example.com> Alberto> Craig wrote: >>> The name on the front of the 通帳 is Tokyo Linux Users Group. >>> The name printed in the book isトウキヨウリナツクスウーザーグルー >>> プ Alberto> I'm using MHE on top of Emacs 18.59.1, both from Alberto> JE-0.9.8a, and I can read it. And so can I; now that NEmacs (I guess; although there were Mules based on Emacs 18) has translated it to ISO-2022-JP. However, neither NEmacs nor JE give a whack about complying with standards, they only want to display Japanese correctly in as many cases as possible without user intervention. This is a laudable goal, and I approve of it in the abstract. However, I hang out on mailing lists where I need to be able to read "Hrvoje Nik,B9i,Bf" as well as 「小田クレーグ」. And that informs my perspective.... Did you get the Latin-2 caron and accent diacriticals? (Possibly, if you're using Mule and not NEmacs, and have the fonts installed.) How about you Pine users? Not a snowball's chance.... >> Either tell Pine you're defaulting to 8-bit EUC (maybe >> "charset=ISO-2022-8" or "charset=x-euc-jp" will do, although Alberto> The header of Craig's message says the message was using Alberto> ISO-2022-JP: Well, it definitely was not using ISO-2022-JP. That is a seven-bit encoding AFAIK.[1] I'm not _sure_ that ISO-2022-8 will work; I've never tried it. But ISO-2022-JP _should_ fail to produce correct display of Craig's message, if not for 8-bit-ness, then because Craig's message had no `kanji-in' sequences. (In fact, this last makes me pretty sure that `ISO-2022-8' won't work; that's why the non-standard `x-euc-jp' content type got invented, I bet.) But most Japanese software is intentionally broken (more politely, non-compliant), so that it can read the messages produced by all the legacy broken software and other intentionally broken software here in the .jp domain :-( Footnotes: [1] My books on m17n are at home, or I'd look it up and be positive. Next TLUG meeting is Saturday Dec. 13, 1997 (possibly Nov. 13?) --------------------------------------------------------------- a word from the sponsor: TWICS - Japan's First Public-Access Internet System www.twics.com info@example.com Tel:03-3351-5977 Fax:03-3353-6096
- References:
- Re: tlug: Admin: TLUG Bank Account Number
- From: Craig Oda <craig@example.com>
- Re: tlug: Admin: TLUG Bank Account Number
- From: "A.Tomita,Jr." <Alberto@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: Admin: TLUG Bank Account Number
- Next by Date: 8.8.8 (Was Re: tlug: mail newbie question)
- Prev by thread: Re: tlug: Admin: TLUG Bank Account Number
- Next by thread: Re: tlug: Admin: TLUG Bank Account Number
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links