Re: [Ltru] Proposed -t0- subtag

"Broome, Karen" <> Sun, 24 July 2011 15:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F099621F89BE for <>; Sun, 24 Jul 2011 08:10:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.242
X-Spam-Status: No, score=-2.242 tagged_above=-999 required=5 tests=[AWL=-1.358, BAYES_40=-0.185, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id aGg37ePYEJUw for <>; Sun, 24 Jul 2011 08:10:18 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E4A7621F85A8 for <>; Sun, 24 Jul 2011 08:10:17 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server id; Sun, 24 Jul 2011 15:10:17 +0000
Received: from mail153-va3 (localhost.localdomain []) by (Postfix) with ESMTP id 6E99313780F1; Sun, 24 Jul 2011 15:10:16 +0000 (UTC)
X-SpamScore: -31
X-BigFish: VPS-31(zzc89bh9371M15bfKc857h98dKzz1202hzz1033IL8275bh8275dhz2fh668h839h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:; KIP:(null); UIP:(null); IPVD:NLI;;; EFVD:NLI
Received-SPF: pass (mail153-va3: domain of designates as permitted sender) client-ip=;; ; ;
Received: from mail153-va3 (localhost.localdomain []) by mail153-va3 (MessageSwitch) id 1311520205522518_32022; Sun, 24 Jul 2011 15:10:05 +0000 (UTC)
Received: from (unknown []) by (Postfix) with ESMTP id 2401711A805F; Sun, 24 Jul 2011 15:09:56 +0000 (UTC)
Received: from ( by ( with Microsoft SMTP Server id; Sun, 24 Jul 2011 15:09:46 +0000
Received: from ( []) by (Switch-3.4.2/Switch-3.3.2mp) with ESMTP id p6OF8670021369; Sun, 24 Jul 2011 15:09:45 GMT
Received: from ( []) by (Switch-3.4.2/Switch-3.4.2) with ESMTP id p6OF86C5013708 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 24 Jul 2011 15:09:45 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 8.1.393.1; Sun, 24 Jul 2011 11:06:35 -0400
Received: from ([]) by ([]) with mapi; Sun, 24 Jul 2011 08:06:34 -0700
From: "Broome, Karen" <>
To: =?utf-8?B?TWFyayBEYXZpcyDimJU=?= <>, John Cowan <>
Date: Sun, 24 Jul 2011 08:06:31 -0700
Thread-Topic: [Ltru] Proposed -t0- subtag
Thread-Index: AcxCR/592Ipt1pVKSD6v1s8bQJoM9gHykJxA
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2CB55BFC7405E94F830537BD924318D5EBF16A4ABCUSSDIXMSG11am_"
MIME-Version: 1.0
Cc: "" <>
Subject: Re: [Ltru] Proposed -t0- subtag
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 24 Jul 2011 15:10:19 -0000

Forgive me if I’m only able to skim these e-mails, but I’m wondering if there might be a parallel here with a use case like: English language film gets translated into Spoken Japanese (dubbed) for one market/format and Written Japanese (subtitles/captions/AD) for another.


Karen Broome
Sony Electronics

From: [] On Behalf Of Mark Davis ?
Sent: Friday, July 15, 2011 3:03 AM
To: John Cowan
Subject: Re: [Ltru] Proposed -t0- subtag

Thanks. It would be possible to do it that way.

I'm a bit hesitant to do so, however, until we've had more experience with use cases. With regular language tags, for example, I cannot indicate that I speak Californian English with the pin-pen merger. That isn't a specious example; some people somewhere care deeply about these kinds of distinctions. We could have arbitrarily complicated chains of "influence": this content was Georgian translated into Russian (but by a native Ukrainian speaker), then transliterated into Portuguese, then translated into British English according to

Ok, that's a bit fanciful. But the point is that I think we need to get some more experience with 2 levels (source+target) before we see what makes sense beyond that. For those people with particular immediate requirements, a mechanism could be used in the meantime.

— Il meglio è l’inimico del bene —

On Thu, Jul 14, 2011 at 09:23, John Cowan <<>> wrote:
In case you missed it (it was embedded in another posting), I proposed
the -t0- subtag to indicate a transformation path: thus en-t-fr-t0-sq
would indicate text translated from Albanian to French and then to
English (as is often done with Albanian literature because of the lack
of clear copyright law in Albania, so that no one knows who has rights
to what).

Formally, this subtag is needed because stacked -t- extensions are
forbidden by RFC 5646.