<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="generator" content="Windows Mail 17.5.9600.16404">
<style type="text/css"><!--html { font-family: "Color Emoji", "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; }--></style><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.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
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>
</head>
<body dir="ltr">
<div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;">
<div>This brings up an issue that seems at least as interesting as the language prefix issue: this variant implies (or should imply) Latn script, but we don't have a good mechanism to capture that. This isn't a new scenario, though ― the same would apply to
the fonipa variant subtag, for instance. A prefix field, per the current rules, must contain a valid tag; it can't have a language range like “*-Latn”.</div>
<div><br>
</div>
<div>Related, I don't recall if we ever discussed a potential interaction with suppress script: if the variant implies a particular script, then a script subtag adds no additional information ― e.g. “en-Latin-unifon” would be no more informative than “en-unifon”.
That's the kind of situation for which suppress-script was added. But adding a suppress-script field to a variant entry is not currently allowed.</div>
<div><br>
</div>
<div><br>
</div>
<div>Peter<br>
</div>
<div data-signatureblock="true">
<div><br>
</div>
<div>Sent from Windows Mail</div>
<div><br>
</div>
</div>
<div style="padding-top: 5px; border-top-color: rgb(229, 229, 229); border-top-width: 1px; border-top-style: solid;">
<div><font face="'Color Emoji', 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif'" style="line-height: 15pt; letter-spacing: 0.02em; font-family: "Color Emoji", "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 12pt;"><b>From:</b> <a href="mailto:everson@evertype.com" target="_parent">Michael
Everson</a><br>
<b>Sent:</b> Sunday, September 15, 2013 11:20 AM<br>
<b>To:</b> <a href="mailto:ietf-languages@iana.org" target="_parent">ietf-languages@iana.org</a></font></div>
</div>
<div><br>
</div>
<div dir="">
<div id="readingPaneBodyContent">On 15 Sep 2013, at 18:31, Doug Ewell <doug@ewellic.org> wrote:<br>
<br>
> It's also worth mentioning that script subtags cannot be added to the Language Subtag Registry unless the corresponding ISO 15924 code element already exists (RFC 5646, Section 2.2.3). Since there is currently no ISO 15924 code element for Unifon, it's not
a question of whether a variant subtag is the best way to go; it's the only way to go.<br>
<br>
The code element is Latn.<br>
<br>
Michael Everson * http://www.evertype.com/<br>
<br>
_______________________________________________<br>
Ietf-languages mailing list<br>
Ietf-languages@alvestrand.no<br>
http://www.alvestrand.no/mailman/listinfo/ietf-languages<br>
</div>
</div>
</div>
</body>
</html>