<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style data-externalstyle="true">
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst, p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle, p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
</style><style><!--
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in 0in 0pt;
font-family:"Times New Roman","serif";
font-size:12pt;
}
li.MsoNormal, div.MsoNormal {
margin:0in 0in 0pt;
font-family:"Times New Roman","serif";
font-size:12pt;
}
div.MsoNormal {
margin:0in 0in 0pt;
font-family:"Times New Roman","serif";
font-size:12pt;
}
a:link, span.MsoHyperlink {
color:blue;
text-decoration:underline;
}
span.MsoHyperlink {
color:blue;
text-decoration:underline;
}
span.MsoHyperlinkFollowed {
color:purple;
text-decoration:underline;
}
span.EmailStyle17 {
color:rgb(31, 73, 125);
font-family:"Calibri","sans-serif";
}
.MsoChpDefault {
}
div.WordSection1 {
}
--></style>
</head>
<body>
<div data-externalstyle="false" style="font-family:Calibri,'Segoe UI',Meiryo,'Microsoft YaHei UI','Microsoft JhengHei UI','Malgun Gothic','Khmer UI','Nirmala UI',Tunga,'Lao UI',Ebrima,sans-serif;font-size:16px;">
<div>First off, it is entirely appropriate to tag content for its intended audience. That's certainly what Id do for localized UI assets, and is why tagging something like es-419 is useful: nobody speaks es-419, but it’s a great way to characterize the intended
audience for a localized asset.</div>
<div> </div>
<div>But for pseudo-localized content, the tag would definitely be describing the content, not any intended audience.</div>
<div> </div>
<div>Peter</div>
<div data-signatureblock="true">
<div> </div>
<div>Sent from Windows Mail</div>
<div> </div>
</div>
<div style="border-top-color: rgb(225, 225, 225); border-top-width: 1px; border-top-style: solid;">
<strong>From:</strong> Broome, Karen<br>
<strong>Sent:</strong> December 18, 2012 2:24 PM<br>
<strong>To:</strong> Mark Davis ?, Michael Everson<br>
<strong>CC:</strong> ietflang IETF Languages Discussion<br>
<strong>Subject:</strong> RE: pseudo-localization variants<br>
</div>
<div> </div>
<div class=" WordSection1">
<div>
<div>
<p class=" MsoNormal">On Tue, Dec 18, 2012 at 10:59 AM, Michael Everson <<a tabindex="-1" href="mailto:everson@evertype.com">everson@evertype.com</a>> wrote:</p>
<p class=" MsoNormal">You're tagging the language content, not the usage scenario<span style="color: rgb(31, 73, 125);"></span></p>
<p class=" MsoNormal"><span style="color: rgb(31, 73, 125); font-family: "Calibri","sans-serif"; font-size: 11pt;"> </span></p>
<p class=" MsoNormal"><span style="color: rgb(31, 73, 125); font-family: "Calibri","sans-serif"; font-size: 11pt;">I agree. Most of the made-up tags I see in the audiovisual realm are the result of people looking to identify the audience rather than the text
or content itself and I think this is an important distinction. I do not think RFC 5646 should be used for audience identification – but its needs may be influenced by such data.</span></p>
<p class=" MsoNormal"><span style="color: rgb(31, 73, 125); font-family: "Calibri","sans-serif"; font-size: 11pt;"> </span></p>
<p class=" MsoNormal"><span style="color: rgb(31, 73, 125); font-family: "Calibri","sans-serif"; font-size: 11pt;">Regards,</span></p>
<p class=" MsoNormal"><span style="color: rgb(31, 73, 125); font-family: "Calibri","sans-serif"; font-size: 11pt;"> </span></p>
<p class=" MsoNormal"><span style="color: rgb(31, 73, 125); font-family: "Calibri","sans-serif"; font-size: 11pt;">Karen Broome</span></p>
<p class=" MsoNormal"> </p>
</div>
<p class=" MsoNormal"> </p>
</div>
</div>
</div>
</body>
</html>