<div dir="ltr"><div class="gmail_default" style="font-family:"times new roman",serif">That doesn't work for a very common use case: selection.</div><div class="gmail_default" style="font-family:"times new roman",serif"><br></div><div class="gmail_default" style="font-family:"times new roman",serif">To communicate requests for localized content and internationalization services, locales are used, which are an extension of language tags. When people pick a language from a menu, internally they are picking a locale (en-GB, es-419, etc). If you want an application to support Spanglish or Hinglish (and one definitely sees requests for the latter), then you have to have a locale to represent that.</div><div class="gmail_default" style="font-family:"times new roman",serif"><br></div><div class="gmail_default" style="font-family:"times new roman",serif">This is not a small use case: it is on every mobile device, every laptop, most server requests for contents, and so on. Having the ability to tag parts of a text at a fine grained level is an orthogonal use case, and useless for communicating such locale selections. (And such fine-grained tagging falls apart for cases like Denglisch "gedownloadet" or the Franglais "downloadé", anyway, but I don't want to deep-end on that.)</div><div class="gmail_default" style="font-family:"times new roman",serif"><br></div><div class="gmail_default" style="font-family:"times new roman",serif"><br></div><div class="gmail_default" style="font-family:"times new roman",serif">I'm not as sanguine about a new RFC for another extension: those are an complete pain to do, and take an inordinate amount of time and effort. That also isn't at all necessary. It is clearly well within the scope of -t-, which is fairly broad as per the bolding below.</div><div class="gmail_default" style="font-family:"times new roman",serif"><br></div><div class="gmail_default" style="font-family:"times new roman",serif"><div class="gmail_default"> This document specifies an Extension to BCP 47 that provides subtags</div><div class="gmail_default"> for specifying the source language or script of transformed content,</div><div class="gmail_default"> including content that has been transliterated, transcribed, or</div><div class="gmail_default"> translated, <b>or in some other way influenced by the source</b>. It also</div><div class="gmail_default"> provides for additional information used for identification.</div><div class="gmail_default"><br></div><div class="gmail_default">— <a href="https://tools.ietf.org/html/rfc6497">https://tools.ietf.org/html/rfc6497</a></div><div class="gmail_default"><br></div><div class="gmail_default">My only question to this list would be for recommendations as to what the best subtag in the T extension for such code-switching would be. </div><div class="gmail_default"><ol><li>It could be a value under the m0 key (like es-t-en-m0-codeswit or hi-t-en-m0-codeswit), or </li><li>It could be a new key (like es-t-en-c0 or hi-t-en-c0), which would be shorter for the general case and allow for finer-grained distinctions in the future if necessary. (I lean towards this.)<br></li></ol></div></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><font face="'times new roman', serif"><div style="background-color:transparent;margin-top:0px;margin-left:0px;margin-bottom:0px;margin-right:0px"><div></div></div><div style="background-color:transparent;margin-top:0px;margin-left:0px;margin-bottom:0px;margin-right:0px">Mark</div></font><div><div><font face="'times new roman', serif"><i><span style="font-style:normal"><i></i></span><i></i></i></font></div></div></div></div></div></div></div>
<br><div class="gmail_quote">2016-12-19 5:47 GMT+01:00 Martin J. Dürst <span dir="ltr"><<a href="mailto:duerst@it.aoyama.ac.jp" target="_blank">duerst@it.aoyama.ac.jp</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2016/12/19 03:12, Michael Everson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
An example of Spanglish (from a published translation of The Little Prince):<br>
</blockquote>
<br></span>
So one way to express what's happening would be the following:<br>
<br>
<p lang='es'>Cuando yo tenía seis años, encontré un <span lang='en'>beautiful</span> dibujo en un <span lang='en'>book</span> llamado <span lang='en'>True</span> cuentos sobre una <span lang='en'>jungle</span>. El <span lang='en'>book</span> mostraba<br>
una boa constrictora tragándose un <span lang='en'>wild animal</span>. Esta es la copia del dibujo.<br>
<br>
El book decía: ‘La boa constrictora se traga sus presas <span lang='en'>whole</span>, sin masticarlas. Después ellas son incapaces de movimiento.<br>
Después ellas <span lang='en'>sleep</span> por seis meses <span lang='en'>while</span> hacen la digestión.’<br>
<br>
<span lang='en'>That</span> me puso a pensar sobre todas las cosas que están en la <span lang='en'>jungle</span>, y, con una crayola, yo hice mi primer dibujo. Lo llamé<span class=""><br>
drawin número uno. Él looked así...<br></span>
</p><br>
<br>
Sorry if I made some mistakes, in particular if I overlooked an English word.<br>
<br>
Regards, Martin.<div class="HOEnZb"><div class="h5"><br>
______________________________<wbr>_________________<br>
Ietf-languages mailing list<br>
<a href="mailto:Ietf-languages@alvestrand.no" target="_blank">Ietf-languages@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages" rel="noreferrer" target="_blank">http://www.alvestrand.no/mailm<wbr>an/listinfo/ietf-languages</a><br>
</div></div></blockquote></div><br></div>