Re: [Ltru] draft-falk-transliteration-tags

Mark Davis ☕ <> Mon, 04 July 2011 22:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 94C1821F8740 for <>; Mon, 4 Jul 2011 15:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_FONT_FACE_BAD=0.884, 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 UCSlShN-rsNc for <>; Mon, 4 Jul 2011 15:46:40 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5B0A821F861A for <>; Mon, 4 Jul 2011 15:46:13 -0700 (PDT)
Received: by ywp31 with SMTP id 31so2651080ywp.31 for <>; Mon, 04 Jul 2011 15:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=vlxt281Bp59ePkMb7CvHn6CXx0kB44JYdemPgj+b0tk=; b=saXYqts25zT6XQr1arF9ZtTa5l6N8ioGE1UjrYxbdwuUPHQFSc8nYMAacJusTeayXh lc3A5ZBTRtdfrGTSVbIUfVODSTdW4eOQuS3kz86MDc2Gqjjn+hDM2hTcLwivImYVCagU zqz6Fu/e++qZ60R3pJTQkKTQam3kJOb41DpM4=
MIME-Version: 1.0
Received: by with SMTP id 20mr2470660ybb.444.1309819571092; Mon, 04 Jul 2011 15:46:11 -0700 (PDT)
Received: by with HTTP; Mon, 4 Jul 2011 15:46:11 -0700 (PDT)
In-Reply-To: <>
References: <> <>
Date: Mon, 4 Jul 2011 15:46:11 -0700
X-Google-Sender-Auth: VH7lOuFYOzsq6NfQOG40pFxqhy8
Message-ID: <>
From: =?UTF-8?B?TWFyayBEYXZpcyDimJU=?= <>
To: Nevil Brownlee <>
Content-Type: multipart/alternative; boundary=000e0cd48714413cfd04a74622fe
Cc:,, LTRU Working Group <>, Courtney Falk <>
Subject: Re: [Ltru] draft-falk-transliteration-tags
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: Mon, 04 Jul 2011 22:46:41 -0000

Courtney had agreed to combine efforts, resulting in

Thanks for your feedback on the 00 version. There have been a number of
changes due to Martin Dürst's comments, and I have some feedback on your
issues below.

*— Il meglio è l’inimico del bene —*

>        - Either identify transliteration, transcription, and
>        translation separately or explain what that is not
>        necessary.

That should be described, perhaps something like:

The transform involved (transliteration, transcription, translation, or
other) is specified by the mechanism. It may involve a combination of
techniques, such as translation for terms with specific or well-known
meanings (such as lake or park) and transcriptions for other names (such as
Lago di Bracciano). (Note that the difference between "transliteration" and
"transcription" is not always clear. Some people restrict the use
to be "lossless", although it is rarely the case that any transform is
purely lossless.)

>        - Make sure that transliteration and transcription
>        systems are properly and unambiguously identified or
>        explain why that is not necessary.

The whole structure of BCP47 allows for a degree of specificity which is
flexible enough to meet user's needs. There are times, for example, that all
one knows about certain data content is that it is, say, Cyrillic
transliterated into Latin. In other circumstances, one might know much more
specifically that it is Bulgarian (Cyrillic) transliterated into Spanish
(Latin, Latin American) according to Ivanov's 2009 rules.

>        - Rigorously define all subfields and alternate
>        extensions with either a well-defined model for
>        producing identifiers, a registry and registration
>        rules, or both.

In specifying the source for the transform, we have simply followed the
structure of itself, and require no
additional registry, because the and BCP47 supply
everything that is required.

In specifying the mechanism, we have followed the precedent of, in having the Unicode Consortium
maintain the registry.