From owner-sc22wg5@open-std.org Tue Feb 15 15:23:43 2005 Return-Path: X-Original-To: sc22wg5-domo1 Delivered-To: sc22wg5-domo1@open-std.org Received: by open-std.org (Postfix, from userid 521) id C64D21499F; Tue, 15 Feb 2005 15:23:43 +0100 (CET) X-Original-To: sc22wg5@open-std.org Delivered-To: sc22wg5@open-std.org Received: from dkuug.dk (ptah.dkuug.dk [195.215.30.66]) by open-std.org (Postfix) with ESMTP id 73D3B12A78 for ; Tue, 15 Feb 2005 15:23:40 +0100 (CET) Received: from mail525.nifty.com (mail525.nifty.com [202.248.37.142]) by dkuug.dk (8.12.10/8.9.2) with ESMTP id j1FEJswE085557 for ; Tue, 15 Feb 2005 15:20:02 +0100 (CET) (envelope-from takata@edogawa-u.ac.jp) Received: from mail500.nifty.com (mail500p.nifty.com [172.22.54.104])by mail525.nifty.com with ESMTP id j1BDPMsH017578 for ; Fri, 11 Feb 2005 22:25:22 +0900 Received: from takata-n9.edogawa-u.ac.jp (nfmvno002002163.dd.ppp.infoweb.ne.jp [220.147.99.163]) (authenticated) by mail500.nifty.com with ESMTP id j1BDP58W015991 for ; Fri, 11 Feb 2005 22:25:07 +0900 Message-Id: <5.1.1.11.2.20050211214637.0512c0f0@mail.edogawa-u.ac.jp> X-Sender: gaf01617@mail.edogawa-u.ac.jp X-Mailer: QUALCOMM Windows Eudora Version 5.1J Jr5-rev2 Date: Fri, 11 Feb 2005 22:25:04 +0900 To: WG5 From: TAKATA Masayuki Subject: Re: (SC22WG5.3224) Internationalization In-Reply-To: <20050210235632.119EF12E2C@open-std.org> References: <20050210101534.B4C5612E30@open-std.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Spam-Score: 0 () Sender: owner-sc22wg5@open-std.org Precedence: bulk John, Miles, and all, At 05/02/10 10:18 +0000, John Reid wrote: > Fortran 90 included features to allow multi-byte character variables, > which continued with later revisions. At 05/02/10 23:18 +0100, Miles Ellis wrote: > "Fortran 90 included features to allow multi-byte character variables, > which were added at the request of the Japanese member body to > facilitate programming by the CJK community, and these have continued > with later revisions." I personally prefer John's version, which is simpler. That Japan first requested the feature is irrelevant here, though I'm quite happy with such acknowledgement. The benefit by the feature is clear enough for the attendees at the meeting, and the intended beneficiary was not limited to CJK community. Finally, there are people who magically create unnecessary projects, claiming that YOU wanted it. The simpler, the better. You would see what I mean, wouldn't you, Miles? ;-) Regards, Makki P.S. Just for your curiosity... > [Note: CJK is the acronym commonly used in the character coding world for > Chinese-Japanese-Korean - these being the three main multibyte character > sets.] Taiwan and Vietnum also have their own character code standards for Chinese- origin ideographic characters, and those characters are included in ISO/IEC 10646. So, CJK was not interpreted as an acronym but merely as a technical term for a range of characters in that standard, to avoid political problems between C and T. -- (Mr) Takata, Masayuki: Associate Professor Edogawa University, Nagareyama, Chiba 270-0198 Japan phone:+81-4-7152-0661ext546 fax:+81-4-7154-2490 http://www.edogawa-u.ac.jp/~takata/