Re: [Ltru] Macrolanguage usage

"Don Osborn" <dzo@bisharat.net> Wed, 21 May 2008 03:30 UTC

Return-Path: <ltru-bounces@ietf.org>
X-Original-To: ltru-archive@megatron.ietf.org
Delivered-To: ietfarch-ltru-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6A7C3A6CA9; Tue, 20 May 2008 20:30:58 -0700 (PDT)
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FF6B28CB58 for <ltru@core3.amsl.com>; Tue, 20 May 2008 20:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level:
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cNPGqvoXZaJO for <ltru@core3.amsl.com>; Tue, 20 May 2008 20:30:55 -0700 (PDT)
Received: from kabissa.org (113166.kabissa.org [72.32.199.201]) by core3.amsl.com (Postfix) with ESMTP id 5E8D628C9A6 for <ltru@ietf.org>; Tue, 20 May 2008 07:24:33 -0700 (PDT)
Received: (qmail 25703 invoked from network); 20 May 2008 09:24:33 -0500
Received: from pool-71-255-255-167.washdc.east.verizon.net (HELO IBM92AA25595C4) (71.255.255.167) by 72.32.229.137 with SMTP; 20 May 2008 09:24:31 -0500
From: "Don Osborn" <dzo@bisharat.net>
To: "'LTRU Working Group'" <ltru@ietf.org>
References: <mailman.494.1210865385.5128.ltru@ietf.org> <00a901c8b6f5$c04529a0$e6f5e547@DGBP7M81> <30b660a20805161108w578b6cf9g11933ca34996a596@mail.gmail.com> <005901c8b787$930f98c0$6801a8c0@oemcomputer> <30b660a20805161309u67158b6arcb3b2df1c46db6a7@mail.gmail.com> <C9BF0238EED3634BA1866AEF14C7A9E561554BEB09@NA-EXMSG-C116.redmond.corp.microsoft.com> <30b660a20805161415kb1172f0xa6c4dea251344bb6@mail.gmail.com> <4832C21A.4050800@malform.no>
In-Reply-To: <4832C21A.4050800@malform.no>
Date: Tue, 20 May 2008 10:24:27 -0400
Message-ID: <001001c8ba85$35ef6fc0$a1ce4f40$@net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Aci6c/7dF0rH03nJQK+BLLFsMNQvdgACaMjg
Content-Language: en-us
Subject: Re: [Ltru] Macrolanguage usage
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

Is anyone on this list following this discussion and the evolution of the standard from the point of view of African languages? I haven't been able to stay with it for several reasons, so apologies in advance if the following is redundant to what has already been taken into account.

Much of my concern re the form and use of language tags have been voiced previously on this list and IETF-languages. I do think that as we get more people working on African language web content, software localization, etc., there will be more questions about available ISO 639 code elements and how those are (and can be) used. 

Just yesterday I learned that a small group has translated Opera in Songhai and has plans to localize some other open source software. The tag used in the .lng file is "soŋ" which fills their need and appears to approximate most closely to the ISO 639-2 code "son" - the latter representing a cluster, not even a macrolanguage. There is no locale for any variety of Songhai (which would be a topic for another list of course). I'm in communication with them for more information on the intent of their current projects but my impression is that they are expressedly not intending to limit themselves to any single currently encoded entity (khq, ses, dje, hmb, ddn, or whatever). 

It may be that for some purposes, localizers and content developers may prefer a broader tag than what is available in ISO 639-3, while in other cases find that the latter fits the need. In some cases perhaps the optimal tags do not exist yet. What this says to me is that there is a need both for flexibility and for various ways to define and refine relationships among tags

The reality of language is of course quite fluid, and we see that especially in cases where there is no single standard language form among several very closely related tongues. Even where linguists or diverse country authorities have established rules of orthography and so on, you may have situations where the optimal localization may be a series of compromises (or a reflection of either dialect leveling or an awareness of speakers of how things are expressed in different varieties of their language). That in turn may require feedback from users to know how well it works for them, but the end result in any case may be new information about tags and relationships among them.

The needs of information technology of course tend to be for clear, mutually exclusive categories (a bit cannot be somewhere between 0 and 1, nor sometimes both 0 and 1, and so on, on up). The only way to accommodate the fluidity of language in this environment seems to be with options of resort to wider or narrower definitions.

Hopefully what I'm suggesting has already been taken into account, and if so, apologies for the redundancy. But whatever the case, I do think that as more languages enter "cyberspace" mure fully in their various forms, there will be more questions by more people about how existing tags, and the systems for using them to identify content, write locales etc., respond to their needs.

Don

Don Osborn
Bisharat.net 


_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www.ietf.org/mailman/listinfo/ltru