Re: [Ltru] Proposed -t0- subtag

"Broome, Karen" <> Sun, 24 July 2011 17:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 32B6821F85C0 for <>; Sun, 24 Jul 2011 10:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.92
X-Spam-Status: No, score=-2.92 tagged_above=-999 required=5 tests=[AWL=0.679, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id i3NreMXaNQvj for <>; Sun, 24 Jul 2011 10:03:45 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EAA2D21F8A35 for <>; Sun, 24 Jul 2011 10:03:44 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server id; Sun, 24 Jul 2011 17:03:44 +0000
Received: from mail15-am1 (localhost.localdomain []) by (Postfix) with ESMTP id 109ECFE816F; Sun, 24 Jul 2011 17:03:44 +0000 (UTC)
X-SpamScore: -39
X-BigFish: VPS-39(zzc89bh9371M179dN542M98dKzz1202hzz1033IL8275bh8275dhz2fh668h839h93fh61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:; KIP:(null); UIP:(null); IPVD:NLI;;; EFVD:NLI
Received-SPF: pass (mail15-am1: domain of designates as permitted sender) client-ip=;; ; ;
Received: from mail15-am1 (localhost.localdomain []) by mail15-am1 (MessageSwitch) id 1311527023877734_4712; Sun, 24 Jul 2011 17:03:43 +0000 (UTC)
Received: from (unknown []) by (Postfix) with ESMTP id D3B03162004F; Sun, 24 Jul 2011 17:03:43 +0000 (UTC)
Received: from ( by ( with Microsoft SMTP Server id; Sun, 24 Jul 2011 17:03:43 +0000
Received: from ( []) by (Switch-3.4.2/Switch-3.3.2mp) with ESMTP id p6OH2wgM019615; Sun, 24 Jul 2011 17:03:43 GMT
Received: from ( []) by (Switch-3.4.2/Switch-3.4.2) with ESMTP id p6OH2gR1025256 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 24 Jul 2011 17:03:42 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 8.1.393.1; Sun, 24 Jul 2011 13:01:59 -0400
Received: from ([]) by ([]) with mapi; Sun, 24 Jul 2011 10:01:58 -0700
From: "Broome, Karen" <>
To: Doug Ewell <>, "" <>
Date: Sun, 24 Jul 2011 10:01:56 -0700
Thread-Topic: [Ltru] Proposed -t0- subtag
Thread-Index: AcxKIgJa16/liqfWScu+EsCQB0DdGwAADAvg
Message-ID: <>
References: <079D0DFD667C499EA3F54382C9E07BE2@DougEwell>
In-Reply-To: <079D0DFD667C499EA3F54382C9E07BE2@DougEwell>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
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 17:03:46 -0000

Hmm. Need to give this some thought and read the draft a little more closely. 

Long ago, I thought it might be appropriate for SMPTE or a similar body to register a singleton and use it to indicate subtitled/written or dubbed/spoken language, but seeing this addition I'm thinking it through again. I think the usage is likely more general than just the motion picture industry. "Zxxx" (code for unwritten documents) is not something I'll likely recommend any time soon for the motion picture industry. I've always opposed that for use to describe spoken language "tracks" though I know my use cases awhile back may have supported the creation of this tag. In most cases, it is true that the language mode can be inferred, but this is not always the case.


Karen Broome

-----Original Message-----
From: [] On Behalf Of Doug Ewell
Sent: Sunday, July 24, 2011 9:52 AM
Subject: Re: [Ltru] Proposed -t0- subtag

"Broome, Karen" <Karen dot Broome at am dot sony dot com> wrote:

> 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.

Testing my understanding of the proposed extension, I think both would 
be "ja-t-en".  The second could alternatively be "ja-Jpan-t-en", but 
since 'Jpan' is the Suppress-Script for 'ja', it could normally be 
omitted unless one felt it necessary to call attention to the writing 

Folks who insist that spoken content needs to be tagged as such, not 
inferred from the context, would probably say the first tag should be 

The point is that the same Japanese content is converted along two 
discrete paths; there is no indication that one is converted from the 
other.  The source in each case is English ("-t-en").

Doug Ewell | Thornton, Colorado, USA | RFC 5645, 4645, UTN #14 | | @DougEwell ­ 

Ltru mailing list