RE: [Ltru] Extended language tags (long reply)

Karen_Broome@spe.sony.com Thu, 11 October 2007 01:42 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 1Ifn47-0002k6-5G; Wed, 10 Oct 2007 21:42:19 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1Ifn46-0002ip-2i for ltru-confirm+ok@megatron.ietf.org; Wed, 10 Oct 2007 21:42:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ifn45-0002if-M9 for ltru@ietf.org; Wed, 10 Oct 2007 21:42:17 -0400
Received: from outbound-sin.frontbridge.com ([207.46.51.80] helo=outbound8-sin-R.bigfish.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ifn3z-0001X5-5J for ltru@ietf.org; Wed, 10 Oct 2007 21:42:12 -0400
Received: from outbound8-sin.bigfish.com (localhost.localdomain [127.0.0.1]) by outbound8-sin-R.bigfish.com (Postfix) with ESMTP id 9F2AA1539C54; Thu, 11 Oct 2007 01:42:03 +0000 (UTC)
Received: from mail57-sin-R.bigfish.com (unknown [10.3.40.3]) by outbound8-sin.bigfish.com (Postfix) with ESMTP id 9311815D8058; Thu, 11 Oct 2007 01:42:03 +0000 (UTC)
Received: from mail57-sin (localhost.localdomain [127.0.0.1]) by mail57-sin-R.bigfish.com (Postfix) with ESMTP id E64A9E201A9; Thu, 11 Oct 2007 01:42:01 +0000 (UTC)
X-BigFish: VP
X-FB-SS: 0,
X-MS-Exchange-Organization-Antispam-Report: OrigIP: 64.14.251.196; Service: EHS
Received: by mail57-sin (MessageSwitch) id 1192066921888417_6106; Thu, 11 Oct 2007 01:42:01 +0000 (UCT)
Received: from USCCIMTA02.spe.sony.com (unknown [64.14.251.196]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail57-sin.bigfish.com (Postfix) with ESMTP id 9020E19D805C; Thu, 11 Oct 2007 01:42:01 +0000 (UTC)
Received: from usmail02.spe.sony.com ([43.130.148.26]) by USCCIMTA02.spe.sony.com (Lotus Domino Release 6.5.5) with ESMTP id 2007101018420606-290423 ; Wed, 10 Oct 2007 18:42:06 -0700
In-Reply-To: <DDB6DE6E9D27DD478AE6D1BBBB83579561AC6067DF@NA-EXMSG-C117.redmond.corp.microsoft.com>
To: Peter Constable <petercon@microsoft.com>
Subject: RE: [Ltru] Extended language tags (long reply)
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.5 CCH7 December 15, 2006
Message-ID: <OF394D1F04.E796C7DA-ON88257371.0006E2AE-88257371.00095919@spe.sony.com>
From: Karen_Broome@spe.sony.com
Date: Wed, 10 Oct 2007 18:39:41 -0700
X-MIMETrack: Serialize by Router on USMAIL02/SVR/SPE(Release 6.5.5FP1|April 11, 2006) at 10/10/2007 18:39:40, Serialize complete at 10/10/2007 18:39:40, Itemize by SMTP Server on USCCiMTA02/SVR/SPE(Release 6.5.5|November 30, 2005) at 10/10/2007 06:42:06 PM, Serialize by Router on USCCiMTA02/SVR/SPE(Release 6.5.5|November 30, 2005) at 10/10/2007 06:42:08 PM, Serialize complete at 10/10/2007 06:42:08 PM
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b6657e60309a1317174c9db2ae5f227
Cc: "ltru@ietf.org" <ltru@ietf.org>, 'ISO 639 Joint Advisory Committee' <ISOJAC@loc.gov>
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

The comment I quoted was in reply to this comment from me. I think it was 
pretty clear that I was talking about dialects of Dutch. The context for 
this comment was not RFC 4646, it was ISO 639-6 and some of the 
interesting things I saw in its hierarchical structure and spoken/written 
distinctions:

Dialects represented here are critical to us even if we only use a small 
subset of these codes. The difference between Dutch and Flemish is 
important in our world. I understand that Dutch productions are often 
subtitled in Flanders because the accent is so different. In written form, 
there is very little to distinguish the two dialects. Even 639-3 doesn't 
recognize Flemish. 

The people tasked with classifying content and developing linguistic 
classifications are usually not people who can tell the difference between 
Flemish and Vlaams given a piece of data that merely says "Flemish." For 
this reason, I request clarification on both the Dutch and Vlaams pages on 
the Ethnologue site. This would help.

This is now probably off-topic for the IETF list, but serves as a reminder 
of the confusion that can result from the combination of such different 
language standards in BCP 47 and the need for adequate documentation and 
disambiguation at the Ethnologue site. I think ISO 639-3 may prove to be 
too complex for the average classifier of linguistic content. 

Regards,

Karen Broome
Metadata Systems Designer
Sony Pictures Entertainment
310.244.4384





Peter Constable <petercon@microsoft.com> 
10/10/2007 05:45 PM

To
"ltru@ietf.org" <ltru@ietf.org>
cc
'ISO 639 Joint Advisory Committee' <ISOJAC@loc.gov>
Subject
RE: [Ltru] Extended language tags (long reply)






[cc to JAC]

The documentation problem is something that ISO 639 RAs potentially can 
and probably should address so that it's clear to implementers that "vls" 
is indeed the identifier for the language variety typically meant by the 
appellation "Flemish".

Note, though, that there's no way to escape the issue Ethnologue is 
calling out: that "Flemish" and "Vlaams" are sometimes used to refer to 
the variety usually called (in English) Dutch. If someone wants to find 
the ID for "Flemish", they must first make sure they know what language 
variety it is they are really dealing with. That is not a problem that ISO 
639 can deal with.

Also, ISO 639 cannot really deal with the UI issue. Languages can have 
many names. Some names may go in or out of vogue; some names may be 
strongly preferred in some places and simultaneously strongly disparaged 
in other places. It is not the role of the ISO 639 JAC or the RAs to give 
out recommendations as to what names should be exposed to users in 
products.

Finally, wrt our email exchange in 2005, I think I may have expressed 
things in a way that was misunderstood. I believe this is the bit in 
question:

<quote>
E.g. Karen mentioned "nld-BE" (3066 would use require nd-BE) for Flemish, 
though 639-3 will provide "vls". I expect a successor to RFC 3066 will 
consider both valid, though we can't force people to use "vls" if they 
happen to come up with "nd-BE".
</quote>

I'm pretty sure I did not mean to imply by these comments that I 
considered "vls" appropriate for Dutch spoken in the Flemish region. I 
believe I thought we were discussing Flemish aka Vlaams.



Peter


> -----Original Message-----
> From: Karen_Broome@spe.sony.com [mailto:Karen_Broome@spe.sony.com]
> Sent: Wednesday, October 10, 2007 1:59 PM
> To: John Cowan
> Cc: ltru@ietf.org
> Subject: Re: [Ltru] Extended language tags (long reply)
>
> Without additional disambiguation, this is very confusing to just about
> anyone with a language list that includes Flemish. It is especially
> confusing to me as the editor of ISO 639-3 previously indicated to me
> and
> the MPAA that this was indeed the tag for the Flemish dialect of Dutch.
> Granted, 639-3 was in DIS status at that point. After ISO 639-3 was
> published, I recommended the "vls" tag for a non-RFC-4646 usage than
> spanned efforts of several studios.
>
> Could we make a request for just a bit more disambiguation in the
> Ethnologue entry?
>
> This is text I received in a private e-mail about the tag when I
> presented
> a list of film languages a couple years back and asked for equivalents
> in
> ISO 639-3. I specifically noted the need to distinguish the Flemish
> dialect of Dutch from the Netherlands variant:
>
> "ISO 639-3 does have an entry for "Flemish", though it happens to use
> the
> autonym "Vlaams" for the reference name. That is, on the one hand, a
> documentation problem and, on the other, a UI problem: a developer
> needs
> to be able to discover that the entry "vls, 'Vlaams'" is for Flemish,
> and
> then they need to determine the UI string they should present to users
> that will allow *them* to find the correct item in a list.
>
> Regards,
>
> Karen Broome
>
>
>
>
>
> John Cowan <cowan@ccil.org>
> 10/10/2007 12:31 PM
>
> To
> Karen_Broome@spe.sony.com
> cc
> "ltru@ietf.org" <ltru@ietf.org>
> Subject
> Re: [Ltru] Extended language tags (long reply)
>
>
>
>
>
>
> Karen_Broome@spe.sony.com scripsit:
> > I wrote:
> >
> > (I still don't know whether "vls"
> > (639-3) falls back to "nld/dut" in 639-2, though Flemish is cited as
> a
> > synonym for Vlaams in 639-3.)
>
> It does not.
>
> > Sorry, I meant to say that "Flemish" is cited as a synonym on
> > Ethnologue.com.
>
> That is to say, the name "Flemish" has been used for both vls and
> the Belgian version of nl.
>
> --
> Mark Twain on Cecil Rhodes:                    John Cowan
> I admire him, I freely admit it,
> http://www.ccil.org/~cowan
> and when his time comes I shall                cowan@ccil.org
> buy a piece of the rope for a keepsake.
>
>
> _______________________________________________
> Ltru mailing list
> Ltru@ietf.org
> https://www1.ietf.org/mailman/listinfo/ltru
>
>
>
>
>
>
> _______________________________________________
> Ltru mailing list
> Ltru@ietf.org
> https://www1.ietf.org/mailman/listinfo/ltru


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






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