Re: [Ltru] Macrolanguage, Extlang. The Sami language situation as example

"Mark Davis" <mark.davis@icu-project.org> Fri, 30 May 2008 16:31 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 5AFCF3A6994; Fri, 30 May 2008 09:31:00 -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 21C3C3A67E5 for <ltru@core3.amsl.com>; Fri, 30 May 2008 09:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.676
X-Spam-Level:
X-Spam-Status: No, score=-1.676 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 vaHeW17Oii7m for <ltru@core3.amsl.com>; Fri, 30 May 2008 09:30:58 -0700 (PDT)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.186]) by core3.amsl.com (Postfix) with ESMTP id 033783A68B1 for <ltru@ietf.org>; Fri, 30 May 2008 09:30:56 -0700 (PDT)
Received: by ti-out-0910.google.com with SMTP id a6so3426585tib.25 for <ltru@ietf.org>; Fri, 30 May 2008 09:30:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=+1fR6+/G4nEihH5bGAUd1nTWr11AxHFn+ZwqO+L71hE=; b=lAh+7g2wptl7eMsBeDuKFTukMrBsnB0IY0oznLtev1EtMdtKxn0UNXWRyAP2cbtx103EfJT7giJzUsq6VY4tBWR1ZqHz3PDjcatFw40avVKZlrKdLAptpIYJvq1mK0t+3Jq38UQSMwzecgllw2rOnT2rjrL0EPL+8IVo0Yf731g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=rdRwvXzjgq6lHRgaQsnzSFE+DLwINmVFoTR0Qx7inF4LdxPAXowtBiRn9F9dE4cImFgBuDrNdeGf9+UYN2DkYwhvyqYFc5NidlTbC5NVR4eUEdFUYQMhDb6guG92CcfRt7UjHE2yOcDIaX4bNHFv1qegntGf9XySvR0MmBkmHwQ=
Received: by 10.151.156.11 with SMTP id i11mr1727839ybo.106.1212165053999; Fri, 30 May 2008 09:30:53 -0700 (PDT)
Received: by 10.150.206.3 with HTTP; Fri, 30 May 2008 09:30:53 -0700 (PDT)
Message-ID: <30b660a20805300930m56418561v35245655496c5d02@mail.gmail.com>
Date: Fri, 30 May 2008 09:30:53 -0700
From: Mark Davis <mark.davis@icu-project.org>
To: Doug Ewell <doug@ewellic.org>
In-Reply-To: <004501c8c1ed$ac02e560$e6f5e547@DGBP7M81>
MIME-Version: 1.0
References: <mailman.636.1211925384.15310.ltru@ietf.org> <004d01c8c065$838b8d50$e6f5e547@DGBP7M81> <008001c8c105$cc421820$64c64860$@net> <001501c8c121$646ebe80$e6f5e547@DGBP7M81> <483E14ED.6030100@malform.no> <002601c8c13e$60217e40$e6f5e547@DGBP7M81> <483E3D68.1080202@malform.no> <004901c8c155$419bf560$e6f5e547@DGBP7M81> <4D25F22093241741BC1D0EEBC2DBB1DA013A84C39D@EX-SEA5-D.ant.amazon.com> <004501c8c1ed$ac02e560$e6f5e547@DGBP7M81>
X-Google-Sender-Auth: a014ce1c529dc28d
Cc: LTRU Working Group <ltru@ietf.org>
Subject: Re: [Ltru] Macrolanguage, Extlang. The Sami language situation as example
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: multipart/mixed; boundary="===============1938703804=="
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

I may have been the quotee; let me elaborate slightly.
If 'zh' hadn't existed, or had been clearly specified to be only Mandarin,
then I doubt that 639-3 would have introduced a new code as a macrolanguage
for that and other codes. I was not trying to say that macrolanguage made no
sense, or that it wasn't well defined, but that I think it was defined so as
to deal with a particular issue in coding.

After all, many people consider "gsw" to be a "kind" of German, but there is
no macrolanguage that encompasses both "de" and "gsw", and the same can be
said for many, many languages. So I don't think there was an attempt to
search out *all* the cases where sets of language codes were related and
considered a single entity for some purposes, and make macrolanguage codes
for all of them; more to deal with those cases where a code had existed in
639 or some other standard.

Peter can correct me if I have this wrong.

Mark

On Thu, May 29, 2008 at 5:39 PM, Doug Ewell <doug@ewellic.org> wrote:

> "Phillips, Addison" <addison at amazon dot com> wrote:
>
> >> I'm one of apparently few people who truly believe the ISO 639-3/RA
> >> definition of "macrolanguage," and don't think of it as some kind of
> >> cover story.
> >
> > Since we have the direct testimony of the folks who conceived of
> > macrolanguage, I don't see any reason why anyone would believe
> > otherwise.
>
> It's been claimed often on this list that macrolanguages are nothing but
> a standardization kludge or "shim" between ISO 639-2 and 639-3.  Here is
> a direct quote from this list, from less than two weeks ago:
>
> "According to everything I've heard, the macrolanguage was devised as a
> construction which is an attempt to rationalize inconsistent approach to
> languages used by previous versions of ISO 639. It does not represent
> any particularly reality beyond that."
>
> That is completely different from the ISO 639-3/RA definition, the one
> Peter has quoted and paraphrased numerous times, the one I believe:
>
> "In various parts of the world, there are clusters of closely-related
> language varieties that... can be considered distinct individual
> languages, yet in certain usage contexts a single language identity for
> all is needed....  Where such situations exist, an identifier for the
> single, common language identity is considered in this part of ISO 639
> to be a macrolanguage identifier."
>
> The first quote says macrolanguages do not represent reality; the second
> (ISO) quote defines them in terms of reality.
>
> The ISO definition is a "cover story" if it is simply an attempt at a
> legitimate-sounding explanation for what is really, under the surface, a
> kludge.  I think if the RA really felt they were a kludge, they would
> have come out and said so (perhaps using a more dignified term than
> "kludge").  But the reality is there are plenty of situations, in all
> walks of life, where people think in terms of "the Chinese language" or
> "the Arabic language" and do not (need to) distinguish between the
> individual languages.
>
> Note, once again, that this is not an argument for or against extlang.
>
> --
> Doug Ewell  *  Arvada, Colorado, USA  *  RFC 4645  *  UTN #14
> http://www.ewellic.org
> http://www1.ietf.org/html.charters/ltru-charter.html
> http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ
>
> _______________________________________________
> Ltru mailing list
> Ltru@ietf.org
> https://www.ietf.org/mailman/listinfo/ltru
>



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