Re: [Ltru] Proposed -t0- subtag

"Doug Ewell" <doug@ewellic.org> Sun, 24 July 2011 16:51 UTC

Return-Path: <doug@ewellic.org>
X-Original-To: ltru@ietfa.amsl.com
Delivered-To: ltru@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8871B21F8507 for <ltru@ietfa.amsl.com>; Sun, 24 Jul 2011 09:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.926
X-Spam-Level:
X-Spam-Status: No, score=-0.926 tagged_above=-999 required=5 tests=[AWL=-0.742, BAYES_40=-0.185, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2x4LT7mDcsl4 for <ltru@ietfa.amsl.com>; Sun, 24 Jul 2011 09:51:30 -0700 (PDT)
Received: from p3plsmtpa06-03.prod.phx3.secureserver.net (p3plsmtpa06-03.prod.phx3.secureserver.net [173.201.192.104]) by ietfa.amsl.com (Postfix) with SMTP id A562D21F84F1 for <ltru@ietf.org>; Sun, 24 Jul 2011 09:51:30 -0700 (PDT)
Received: (qmail 31402 invoked from network); 24 Jul 2011 16:51:30 -0000
Received: from unknown (24.8.55.39) by p3plsmtpa06-03.prod.phx3.secureserver.net (173.201.192.104) with ESMTP; 24 Jul 2011 16:51:30 -0000
Message-ID: <079D0DFD667C499EA3F54382C9E07BE2@DougEwell>
From: "Doug Ewell" <doug@ewellic.org>
To: <ltru@ietf.org>
Date: Sun, 24 Jul 2011 10:51:44 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3508.1109
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3508.1109
Subject: Re: [Ltru] Proposed -t0- subtag
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Sun, 24 Jul 2011 16:51:33 -0000

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

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 
"jp-Zxxx-t-en".

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
www.ewellic.org | www.facebook.com/doug.ewell | @DougEwell ­