Re: [Ltru] Status of RFC 4645bis
"Doug Ewell" <dewell@adelphia.net> Wed, 21 March 2007 14:41 UTC
Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HU1zu-0004sI-MH; Wed, 21 Mar 2007 10:41:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HU1zu-0004sC-8o for ltru@ietf.org; Wed, 21 Mar 2007 10:41:06 -0400
Received: from mta1.adelphia.net ([68.168.78.175]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HU1zS-0003vQ-AY for ltru@ietf.org; Wed, 21 Mar 2007 10:41:06 -0400
Received: from DGBP7M81 ([76.167.184.182]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with SMTP id <20070321142444.ZDPF2272.mta10.adelphia.net@DGBP7M81>; Wed, 21 Mar 2007 14:24:44 +0000
Message-ID: <017901c76bc4$ac333e70$6401a8c0@DGBP7M81>
From: Doug Ewell <dewell@adelphia.net>
To: LTRU Working Group <ltru@ietf.org>
References: <007501c747f3$c30db930$6801a8c0@DGBP7M81> <4600D0E9.8060600@sil.org>
Subject: Re: [Ltru] Status of RFC 4645bis
Date: Wed, 21 Mar 2007 07:24:43 -0700
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc:
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org
Martin Hosken <martin underscore hosken at sil dot org> wrote: > OK I'll take a go (I couldn't find bis-02 only bis-01 so I'll talk > about that). You're right, -01 is the version most recently submitted. > My main point is that there are lots of suppress scripts missing. There is a problem in general with Suppress-Script, but I contend it is a problem best discussed in the main process document (RFC 4646bis) and not in the document that delivers the Registry and outlines the rules for creating it (RFC 4645bis). The problem, as you state and as Frank Ellermann has stated roughly 4,646 times, is that by providing such a field, users will expect it to be correctly and authoritatively populated all of the time. This is something ietf-languages has (IMHO) neither the time nor the expertise to do. Instead, the field is present only for a sampling of languages for which an "overwhelmingly used" script could be determined with little or no controversy. Proposals to add others are welcome at ietf-languages. The gap between expectation and reality here is one of the reasons I opposed Suppress-Script in the first place. > Here are a few that spring out at me: > > ko -> Hang > > This is a biggy I would suspect. I thought so too, for a long time, and studied this a year ago to try to prove it. I read books, scanned newspapers, and talked to native Korean speakers. What I found was that, although Hangul is by far the most common script for writing Korean (maybe even "overwhelmingly"), there is noticeable use of hanja is certain contexts: scientific works, personal names, newpaper headlines (to resolve ambiguities), and a few others. There is also an important tradition that hanja is part of the Korean cultural experience, so that even if Hangul is overwhelmingly used, the "controversy" factor applies here. I went in firmly believing that this Suppress-Script should be added, and came away believing it should not, which I think is significant. > The following I'm not so sure about. > > bm -> Latn > ... See above. The correct place to propose these is ietf-languages. > Hmm I'll stop there. I wonder if it might be helpful to put some kind > of comment into the registry to say either that the decision has been > made that this language has no suppress script (because more than one > is used) or that no decision has been made as to whether this language > has a suppress script or not until they've all been decided on. Again, I believe the place for such a comment is in RFC 4646bis. There is no provision in the syntax of the Registry to add file-level comments, though it was suggested during LTRU 1.0. -- Doug Ewell * Fullerton, California, USA * RFC 4645 * UTN #14 http://users.adelphia.net/~dewell/ http://www1.ietf.org/html.charters/ltru-charter.html http://www.alvestrand.no/mailman/listinfo/ietf-languages _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru
- [Ltru] Status of RFC 4645bis Doug Ewell
- Re: [Ltru] Status of RFC 4645bis Martin Hosken
- Re: [Ltru] Status of RFC 4645bis Doug Ewell
- [Ltru] Suppress-Script (was: Re: Status of RFC 46… Frank Ellermann
- RE: [Ltru] Suppress-Script (was: Re: Status of RF… McDonald, Ira
- Re: [Ltru] Status of RFC 4645bis John Cowan
- Re: [Ltru] Status of RFC 4645bis Addison Phillips
- [Ltru] Re: Suppress-Script Frank Ellermann
- Re: [Ltru] Suppress-Script (was: Re: Status of RF… Randy Presuhn
- Re: [Ltru] Suppress-Script (was: Re: Status of RF… John Cowan
- Re: [Ltru] Suppress-Script Martin Hosken
- RE: [Ltru] Suppress-Script (was: Re: Status of RF… McDonald, Ira
- [Ltru] List archives (was: Suppress-Script) Frank Ellermann