Re: [Ltru] Proposed -t0- subtag

[Mark Davis ☕ <[e-mail]>]

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 http://en.wikipedia.org/wiki/English_As_She_Is_Spoke.

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.

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


On Thu, Jul 14, 2011 at 09:23, John Cowan <[e-mail]> 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.
>