<html xmlns:v="urn:schemas-microsoft-com:vml" 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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
/* 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;}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
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;}
p.attach, li.attach, div.attach
{mso-style-name:attach;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:9.0pt;
font-family:"Arial",sans-serif;}
p.bold, li.bold, div.bold
{mso-style-name:bold;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Arial",sans-serif;
font-weight:bold;}
p.green, li.green, div.green
{mso-style-name:green;
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;
color:#628C2A;}
p.replbq, li.replbq, div.replbq
{mso-style-name:replbq;
margin:3.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.ad, li.ad, div.ad
{mso-style-name:ad;
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;}
p.underline, li.underline, div.underline
{mso-style-name:underline;
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;}
p.ad1, li.ad1, div.ad1
{mso-style-name:ad1;
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;}
p.ad2, li.ad2, div.ad2
{mso-style-name:ad2;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:7.5pt;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.underline1, li.underline1, div.underline1
{mso-style-name:underline1;
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;
text-decoration:underline;}
span.yshortcuts
{mso-style-name:yshortcuts;}
span.yshortcuts1
{mso-style-name:yshortcuts1;
font-family:"Verdana",sans-serif;
font-weight:bold;}
span.yshortcuts2
{mso-style-name:yshortcuts2;
font-family:"Verdana",sans-serif;
font-weight:normal;}
span.EmailStyle34
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">If a tag is to be registered for this, I recommend that it use four letters, not three — e.g., “ZHTM”.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Requests may come for a tag to differentiate typography for a particular _<i>language</i>_ from that of other languages. Where there isn’t a conflict, the most sensible choice of tag in that case would be to use the ISO 639-3 ID appended
with a space. “zhm” isn’t currently assigned in ISO 639, but it could get assigned at some point. If that were to happen, it would not be for “Traditional Chinese as used in Macao” since that isn’t a language; it’s a typographic variant of an orthography for
one or possibly more languages as used in a particular region. So, “ZHM ” would create risk of future conflict; a four-letter tag such as “ZHTM” would avoid any such risk.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I recognize that this would differ from the precedents of “ZHH”, “ZHS” and “ZHT”, but those were less-than-optimal choices for tags for the same reasons given here. There’s no benefit from adding to risk just for the sake of following earlier
decisions.<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"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> mpeg-OTspec@yahoogroups.com <mpeg-OTspec@yahoogroups.com>
<b>On Behalf Of </b>Ken Lunde lunde@adobe.com [mpeg-OTspec]<br>
<b>Sent:</b> Monday, December 3, 2018 10:31 AM<br>
<b>To:</b> opentype-list@indx.co.uk; mpeg-OTspec@yahoogroups.com<br>
<b>Subject:</b> [mpeg-OTspec] Re: [OpenType] Proposed new language tag: ZHM (Chinese, Macao SAR)<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div id="ygrp-mlmsg">
<div id="ygrp-msg">
<div id="ygrp-text">
<p>Eric, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Macao SAR is currently preparing such documentation, in the form of their forthcoming MSCS (Macao Supplementary Character Set) character set standard. IRG N2281, which is their Activity Report for IRG #50, provides a bit of background:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fappsrv.cse.cuhk.edu.hk%2F~irg%2Firg%2Firg50%2FIRGN2281_MacaoActivityReport.pdf&data=02%7C01%7Cpetercon%40microsoft.com%7C8f66c0d878c64a61229e08d659506370%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636794599143340029&sdata=lkNG24jv0TOxiEvayfENcBnRqFNUHsRhe47QJQvI4%2Fg%3D&reserved=0">http://appsrv.cse.cuhk.edu.hk/~irg/irg/irg50/IRGN2281_MacaoActivityReport.pdf</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In the case of ZHT and ZHH (introduced in Version 1.5), while both are considered to be Traditional Chinese, the official conventions are different, which leads to different glyphs for a non-trivial number of ideographs. ZHH uses a very
large number of forms that are the same as ZHT, some that are the same as ZHS, and even a few that are the same as JAN. And, some forms are unique to ZHH. The same would be true for ZHM.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Speaking from a regional standards point-of-view, MSCS (ZHM) is expected to share a lot of forms with HKSCS (ZHH), but some will be different, and possibly shared with CNS 11643 (ZHT). A known example is the
<span style="font-family:"MS Gothic"">女</span> component when used on the left side of an ideograph. Instead of following HKSCS, MSCS will follow CNS 11643. See the attached code chart excerpt for U+597B
<span style="font-family:"MS Gothic"">奻</span>. When Macao SAR submits their horizontal extension that is based on MSCS, the M-Source representative glyph will be the same as the T-Source one. Other components are likely to be affected in the same way.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards...<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">-- Ken<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">On Dec 2, 2018, at 10:25 AM, Eric Muller via OpenType <opentype-<a href="mailto:listmaster@indx.co.uk">listmaster@indx.co.uk</a>> wrote:<br>
<br>
Message from OpenType list:<br>
<br>
<br>
On 12/2/2018 6:57 AM, Ken Lunde via OpenType wrote:<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">there are enough differences to warrant a new language tag.<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
Just curious: Is there some documentation of those differences? I <br>
suppose the bulk of the differences are glyph shapes, but is there <br>
anything else?<br>
<br>
Thanks,<br>
Eric.<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><img border="0" width="518" height="92" style="width:5.3906in;height:.9583in" id="_x0035_C721281-4328-461C-9154-9D0B8F03392F" src="cid:image001.png@01D498BC.584D6DD0" alt="cid:4CA7C5F9-7D7F-490F-83AC-26C3FF4B8725@corp.adobe.com"><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:white"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>