Re: Subtag registration: Russian transliteration of Chinese

Here is the reasoning.

English:
<span lang='en'>I saw <span lang='en-t-ru'>Mikhail Gorbachev</span>.</span>

// It is all in English. The "Mikhail Gorbachev" comes from ru, but is
transformed to English spelling, and so is now English (the -t-ru tells us
what it was from). The Russian original was Михаи́л Горбачёв.

German:
Ich sah Michail Gorbatschow.
<span lang='de'>Ich sah <span lang='de-t-ru'>Michail
Gorbatschow</span>.</span>
// same principles, but for German.

Mark

On Tue, Oct 13, 2015 at 6:47 PM, Doug Ewell <doug@ewellic.org> wrote:

> Yegor Grebnev wrote:
>
> > Sorry, it seems that I have misunderstood Doug's original
> > recommendation. Yes, "Chinese transcribed as Russian" seems to be an
> > appropriate option. Thank you!
>
> So it sounds like Yegor does expect the transformed content to continue
> to be identified primarily as Chinese, not as Russian, where "ru-t-zh"
> or "ru-anything" might imply the latter.
>
> So, I know RFC 6497 has been around for three and a half years, but I
> guess I'm still a little puzzled by the idea that content in language A,
> transliterated according to the orthographic conventions of language B,
> should result in that content being labeled "language B" according to
> the primary language subtag.
>
> Consider:
>
> (English)
> This is a sample sentence.
>
> (Russian)
> Это образец приговор.
>
> (Russian, transliterated according to some English-specific convention)
> Eto obrazets prigovor.
>
> These snippets would be tagged, respectively, as "en", "ru", and
> (according to 6497) "en-t-ru". Is this right?
>
> --
> Doug Ewell | http://ewellic.org | Thornton, CO 🇺🇸
>
> _______________________________________________
> Ietf-languages mailing list
> Ietf-languages@alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/ietf-languages
>