New extension for transformed languages

[Mark Davis ☕]

Degrees of precision can be specified, as with BCP47 itself.

It is useful to read the document rather than just commenting on its
advantages or disadvantages based on fragments quoted on email: it's
quite short, see http://tools.ietf.org/html/rfc6497.

________________________________
Mark

— Il meglio è l’inimico del bene —



On Mon, Mar 5, 2012 at 04:05, Michael Everson <everson at evertype.com> wrote:
> On 5 Mar 2012, at 02:05, Doug Ewell wrote:
>
>> Much of RFC 6497 would seem to indicate otherwise, including this, in the Introduction:
>>
>> "This document defines an extension for specifying the source of content that has been transformed, including text that has been transliterated, transcribed, or translated, or in some other way influenced by the source.  It may be used in queries to request content that has been transformed."
>
> That extremely vague description drastically reduces the precision that might have been possible with -t-. What a pity.
>
> Michael Everson * http://www.evertype.com/
>
> _______________________________________________
> Ietf-languages mailing list
> Ietf-languages at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/ietf-languages