<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.hoenzb
{mso-style-name:hoenzb;}
span.m-4185692536847094658hoenzb
{mso-style-name:m_-4185692536847094658hoenzb;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">There’s no such thing as “code-switch languages” unless you mean the individual languages that a speaker switches between when they are code switching. Definition:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“Code switching is the practice of moving back and forth between two languages, or between two dialects or registers of the same language.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As I mentioned in a post last week, the issue at hand in Michael’s scenario is that a reader of content needs to have some level of competency in both English and Spanish (or pick whatever combination of multiple languages) in order for
the content to be understandable and relevant.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Neither the t or u extensions would be appropriate for this. A new “s” extension could be devised that has explicitly additive semantics: “en-s-es” means that both English _<i>and</i>_ Spanish are required to understand the content. Potentially,
these could be chained, e.g. “en-s-s0-es-s1-fi” could mean that you need to speak English _<i>and</i>_ Spanish _and” Finnish to understand the content, with the ordering providing a prioritization (e.g., if your proficiency in Finnish more limited than Spanish,
you may get by). But a key question is what is required of matching, since general-purpose matching algorithms likely won’t pay attention to extensions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Peter<o:p></o:p></p>
<p class="MsoNormal"><a name="_MailEndCompose"><o:p> </o:p></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<p class="MsoNormal"><b>From:</b> Ietf-languages [mailto:ietf-languages-bounces@alvestrand.no]
<b>On Behalf Of </b>Mark Davis ??<br>
<b>Sent:</b> Monday, January 2, 2017 11:53 PM<br>
<b>To:</b> Phillips, Addison <addison@lab126.com><br>
<b>Cc:</b> ietflang IETF Languages Discussion <ietf-languages@iana.org>; John Cowan <cowan@ccil.org><br>
<b>Subject:</b> Re: Spanglish<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">Also, John raises a concern about being able to express transformations into code-switch languages. I added a comment with a reformulation to address that:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p style="background:#FFFFFE"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">As to John's concern in <a href="http://unicode.org/cldr/trac/ticket/9956#comment:1" title="Comment 1 for Ticket #9956"><span style="color:#880000;text-decoration:none">comment:1</span></a> about
being able to have a transformation of a code-switch language: I think that is a far less less important requirement than to have a general mechanism for code-switch languages. <o:p></o:p></span></p>
</div>
<div>
<p style="background:#FFFFFE"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">However, I think we can accommodate that — and at the same time alleviate some of people's concerns about the terms 'source' and 'target' — by changing the
syntax so that the <em><span style="font-family:"Arial",sans-serif">value</span></em> of the c0 key is the language that is mixed into the main language tag. We then get tags structured as follows:<o:p></o:p></span></p>
</div>
<div>
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" style="background:#FFFFFE;border-collapse:collapse;border:none">
<tbody>
<tr style="font-stretch:normal">
<td style="border:solid #CCCCCC 1.0pt;padding:1.2pt 3.0pt 1.2pt 3.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">es-t-<strong><span style="font-family:"Arial",sans-serif">c0-en</span></strong><o:p></o:p></span></p>
</td>
<td style="border:solid #CCCCCC 1.0pt;border-left:none;padding:1.2pt 3.0pt 1.2pt 3.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Spanglish<o:p></o:p></span></p>
</td>
<td style="border:solid #CCCCCC 1.0pt;border-left:none;padding:1.2pt 3.0pt 1.2pt 3.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Spanish with an admixture of English<o:p></o:p></span></p>
</td>
</tr>
<tr style="font-stretch:normal">
<td style="border:solid #CCCCCC 1.0pt;border-top:none;padding:1.2pt 3.0pt 1.2pt 3.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">en-t-<strong><span style="font-family:"Arial",sans-serif">c0-es</span></strong><o:p></o:p></span></p>
</td>
<td style="border-top:none;border-left:none;border-bottom:solid #CCCCCC 1.0pt;border-right:solid #CCCCCC 1.0pt;padding:1.2pt 3.0pt 1.2pt 3.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Spanglish<o:p></o:p></span></p>
</td>
<td style="border-top:none;border-left:none;border-bottom:solid #CCCCCC 1.0pt;border-right:solid #CCCCCC 1.0pt;padding:1.2pt 3.0pt 1.2pt 3.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">English with an admixture of Spanish<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p style="background:#FFFFFE"><em><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Note: the boundary between these two will be rather fuzzy, like most cases with languages. Probably best for these to recommend that es-t-c0-en be used
unless English clearly predominates.</span></em><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
</blockquote>
</div>
<div>
<p style="background:#FFFFFE"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">One could then have <o:p></o:p></span></p>
</div>
<div>
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" style="background:#FFFFFE;border-collapse:collapse;border:none">
<tbody>
<tr style="font-stretch:normal">
<td style="border:solid #CCCCCC 1.0pt;padding:1.2pt 3.0pt 1.2pt 3.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">es-t-hi-<strong><span style="font-family:"Arial",sans-serif">c0-en</span></strong><o:p></o:p></span></p>
</td>
<td style="border:solid #CCCCCC 1.0pt;border-left:none;padding:1.2pt 3.0pt 1.2pt 3.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Spanglish translated from Hindi<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<div>
<p style="background:#FFFFFE"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Although it would be again quite infrequently used, we can easily allow for the case of a code-switch language being the source, and even have the translation
of one code-switch language into another. We do this by using another keyword, much has we have done with the transliteration s0 and d0 keys. So we define c1 as a language that is mixed into the source language for -t-, allowing formulations like<o:p></o:p></span></p>
</div>
<div>
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" style="background:#FFFFFE;border-collapse:collapse;border:none">
<tbody>
<tr style="font-stretch:normal">
<td style="border:solid #CCCCCC 1.0pt;padding:1.2pt 3.0pt 1.2pt 3.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">es-t-hi-<strong><span style="font-family:"Arial",sans-serif">c0-en</span></strong>-<strong><span style="font-family:"Arial",sans-serif">c1-en</span></strong><o:p></o:p></span></p>
</td>
<td style="border:solid #CCCCCC 1.0pt;border-left:none;padding:1.2pt 3.0pt 1.2pt 3.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Spanglish translated from Hinglish<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</div>
</blockquote>
<div>
<p style="background:#FFFFFE"><span style="font-size:10.0pt;color:black"><o:p> </o:p></span></p>
<p style="background:#FFFFFE"><span style="font-size:10.0pt;font-family:"Times New Roman",serif;color:black">The more I think about it, the more I like this formulation.</span><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">Mark<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Jan 3, 2017 at 8:15 AM, Mark Davis <span style="font-family:"Segoe UI Emoji",sans-serif">
☕</span>️ <<a href="mailto:mark@macchiato.com" target="_blank">mark@macchiato.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">-u- is syntacticly unsuitable, as well as being a worse fit semantically. You can use es-t-en-c0 or es-t-en-gb-c0. You can't use es-u-en-c0, or es-u-en-gb-c0 because any two letter subtag
is a reserved keyword. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">I was not arguing in favor of using -u- extension for code-switch languages, just saying that it /is/ a broad mechanism.<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888"><br clear="all">
<span class="hoenzb"><o:p></o:p></span></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif;color:#888888">Mark</span><span style="font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Mon, Jan 2, 2017 at 7:10 PM, Phillips, Addison <<a href="mailto:addison@lab126.com" target="_blank">addison@lab126.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">><br>
> > The much<br>
> > more general mechanism is the U one, which by now has a variety of<br>
> > different settings.<br>
><br>
> Ah, yes, forgot about that. I think it would be much better then to use the U<br>
> extension.<br>
><br>
<br>
The U extension is for Locale information. I don't think that fits any better. If anything, it's a worse fit.<br>
<span style="color:#888888"><br>
<span class="m-4185692536847094658hoenzb">Addison</span></span><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>