<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)">
<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:"Cordia New";
panose-1:2 11 3 4 2 2 2 2 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:Aptos;}
@font-face
{font-family:"Microsoft JhengHei";
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Helvetica Neue";}
@font-face
{font-family:"\@Microsoft JhengHei";}
@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;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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 lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">For both of these proposed features, I’m also wondering why using existing stylistic set features wouldn’t be sufficient.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Hin-Tak Leung <htl10@users.sourceforge.net>
<br>
<b>Sent:</b> Friday, March 1, 2024 3:01 PM<br>
<b>To:</b> Peter Constable <pconstable@microsoft.com>; Ken Lunde <lunde@unicode.org><br>
<b>Cc:</b> mpeg-otspec@lists.aau.at<br>
<b>Subject:</b> Re: [MPEG-OTSPEC] [EXTERNAL] Re: Two GSUB Proposals for OFF: 'cabp' and 'hypy'<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica Neue"">Yes, sorry for derailing that discussion. This feature seems to be raised by one vendor for one intended usage, a relation with a national standard. There are a few existing feature tags of a similar
nature (in Japanese for historical forms). I was just saying that it is somewhat strange to have features tags concerning the Latin glyphs and Latin diacritics in a Chinese font. (and also questioning the relation with the said national standard). IMO it is
a specialised and perhaps even a vendor-specific feature... so I shall point the discussion back: is another vendor likely to want to ship a font with these feature tags?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica Neue""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica Neue""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica Neue""><o:p> </o:p></span></p>
</div>
<div id="ydpfa331328yahoo_quoted_9831869892">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">On Friday, 1 March 2024 at 18:34:37 GMT, Ken Lunde via mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a>> wrote:
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">Peter,<br>
<br>
That is precisely why I explicitly stated that I had no strong objection to registering said feature, though that seemed to have become lost to the noise. In my mind, the question we should be asking is whether the number of fonts that would likely include
this feature would rise to the level that it would make sense to register it, as opposed to simply using named character variant or stylistic set features for this purpose.<br>
<br>
Regards...<br>
<br>
-- Ken<br>
<br>
> On Feb 29, 2024, at 15:00, Peter Constable via mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>> wrote:<br>
> <br>
> I’m not sure why standardization of transliteration conventions is being mentioned. An OT feature would simply be providing a way for content authors to access particular glyph variants from a font to suit their typographic preference.<br>
> Peter<br>
> From: mpeg-otspec <<a href="mailto:mpeg-otspec-bounces@lists.aau.at" target="_blank">mpeg-otspec-bounces@lists.aau.at</a>> on behalf of Hin-Tak Leung via mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>><br>
> Date: Thursday, February 29, 2024 at 3:56 PM<br>
> To: <a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a> <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>>, suzuki toshiya <<a href="mailto:mpsuzuki@hiroshima-u.ac.jp" target="_blank">mpsuzuki@hiroshima-u.ac.jp</a>><br>
> Cc: Eiso CHAN <<a href="mailto:eisoch@126.com" target="_blank">eisoch@126.com</a>><br>
> Subject: [EXTERNAL] Re: [MPEG-OTSPEC] Two GSUB Proposals for OFF: 'cabp' and 'hypy'<br>
> That's especially true in mainland China where the teaching of spoken English is generally poor (and even deprecated) and subjected to local /personal variations. Not sure what is the intended audience of this kind of standardisation - is it for non-Chinese
learning Chinese as a non-native language?<br>
> There is also rumours that English is to be banned / deprecated / not taught in junior schools.<br>
> On Thursday, 29 February 2024 at 22:44:16 GMT, Hin-Tak Leung via mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>> wrote:<br>
> For those who want to read the source material, it seems that the canonical sources for GBZ 40637 might be<br>
> <a href="https://www.chinesestandard.net/AMP/English.amp.aspx/GBZ40637-2021" target="_blank">
https://www.chinesestandard.net/AMP/English.amp.aspx/GBZ40637-2021</a><br>
> <a href="https://openstd.samr.gov.cn/bzgk/gb/newGbInfo?hcno=52E2DE28D439C1937EE09AE4B5AA615B" target="_blank">
https://openstd.samr.gov.cn/bzgk/gb/newGbInfo?hcno=52E2DE28D439C1937EE09AE4B5AA615B</a><br>
> For the English and Chinese version of it respectively (behind pay walls), and a somewhat reliable Chinese version available for download at:<br>
> <a href="https://archive.org/details/GB-Z40637-2021/page/n5/mode/1up" target="_blank">
https://archive.org/details/GB-Z40637-2021/page/n5/mode/1up</a><br>
> I am mostly with Ken Lunde on this: transliteration itself is a work-around (trying to approximate one language's sound with another), and diacritics on transliteration is a refinement of a workaround... for actual scholarly work, the traditional way of
indicating the pronunciation of a rare word in Chinese is to say "XY </span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">切</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">" where you indicates the starting
consonant and the ending vowel with two common native words.e.g. my surname "</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">梁</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">"'s Cantonese pronunciation
might be written down as "</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">連揚切</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">", where you take the consonant of the first (</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">連</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">"leen")
and join with the ending vowel of another ("</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">揚</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">""yeung") to form "leung". Most people can't quite pronounce
English "leung" correctly anyway, so the traditional way of annotating it as e.g. "</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">連揚切</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">" would be preferable...
it is somewhat a lost cause to try to standardise on hyphenation and diacritics of transliterations...<br>
> On Thursday, 29 February 2024 at 14:16:26 GMT, suzuki toshiya via mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>> wrote:<br>
> Dear Eiso, Fuji-san,<br>
> I checked </span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">現代漢語拼音方案</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">2012 available at<br>
> <a href="http://edu.shandong.gov.cn/attach/0/b72295c44ff442c8b333a481f524dbe9.pdf" target="_blank">
http://edu.shandong.gov.cn/attach/0/b72295c44ff442c8b333a481f524dbe9.pdf</a><br>
> I guess, the glyphs you want to care might be:<br>
> "a" in "ai" (</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">哀</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">), "uan" (</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">弯</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">),
"Van" (</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">冤</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">) in
</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">韻母表</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A"><br>
> "g" in "ang" (</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">昂</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">), "eng" (</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">亨的韵母</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">),
"ieng" (</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">英</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">), "ueng" (</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">翁</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">),
"veng" (</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">雍</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">) in
</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">韻母表</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A"><br>
> Am I understanding correctly?<br>
> </span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">漢語拼音方案</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">1958 (I'm unsure the source of this scanned image):<br>
> <a href="http://www.moe.gov.cn/ewebeditor/uploadfile/2015/03/02/20150302165814246.pdf" target="_blank">
http://www.moe.gov.cn/ewebeditor/uploadfile/2015/03/02/20150302165814246.pdf</a><br>
> there is no clear distinction of the typeface for "a" & "g".<br>
> A distinction of "a" is mentioned in the </span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">四、声調符号</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">, special "a" is used for
</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">軽声</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">,<br>
> maybe it would be the update introduced in 2012.<br>
> But yet I'm unsure about the background to distinguish "g".<br>
> Regards,<br>
> mpsuzuki<br>
> On 2024/02/29 22:28, </span><span style="font-size:10.0pt;font-family:"Microsoft JhengHei",sans-serif;color:#26282A">陈永聪</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A"> via mpeg-otspec wrote:<br>
> > Fuji-San,<br>
> > > Thank you for your comments. The most official materials for Hanyu Pinyin forms are
</span><span style="font-size:10.0pt;font-family:"Microsoft JhengHei",sans-serif;color:#26282A">汉语拼音方案</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">and
</span><span style="font-size:10.0pt;font-family:"Microsoft JhengHei",sans-serif;color:#26282A">现代汉语词典</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">.<br>
> > > Eiso<br>
> > ---- Replied Message ----<br>
> > From Takaaki Fuji </span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">藤</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">
</span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">貴亮</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A"><<a href="mailto:tfuji@morisawa.co.jp" target="_blank">tfuji@morisawa.co.jp</a>><<a href="mailto:tfuji@morisawa.co.jp">mailto:tfuji@morisawa.co.jp</a>><br>
> > Date 02/29/2024 </span><span style="font-size:10.0pt;font-family:"MS Gothic";color:#26282A">下午</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A">6:45<br>
> > To </span><span style="font-size:10.0pt;font-family:"Microsoft JhengHei",sans-serif;color:#26282A">陈永聪</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A"> <<a href="mailto:eisoch@126.com" target="_blank">eisoch@126.com</a>><<a href="mailto:eisoch@126.com">mailto:eisoch@126.com</a>><br>
> > Cc mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>><<a href="mailto:mpeg-otspec@lists.aau.at">mailto:mpeg-otspec@lists.aau.at</a>><br>
> > Subject Re: [MPEG-OTSPEC] Two GSUB Proposals for OFF: 'cabp' and 'hypy'<br>
> > Dear Eiso,<br>
> > > I'm just curious, but for ‘hypy’, is there any good source I can look at for the ‘official' glyph forms of Hanyu Pinyin?<br>
> > > If I understand the issue correctly, ‘hypy’ is not only about the Futura-like one-story a/g shown in Example, but also the tone marks are preferred to have a 'reverse-modulation’; while an acute is always stroked from top to bottom as a Latin accent,
as a Pinyin mark it goes upwards from left to right to illustrate the second/rising tone. I imagine this conflict/divergence has long been such an issue in a dual-script situation, so switching between the two via GSUB sounds like a great improvement to me!<br>
> > > Thank you,<br>
> > > Takaaki Fuji<br>
> > >> On Feb 26, 2024, at 9:38, </span><span style="font-size:10.0pt;font-family:"Microsoft JhengHei",sans-serif;color:#26282A">陈永聪</span><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A"> via mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>>
wrote:<br>
> >> >> This is my first proposal for OFF. Please see <a href="http://cloud.caaph.com:10121/f/fed7bd2e3d/" target="_blank">
http://cloud.caaph.com:10121/f/fed7bd2e3d/</a><br>
> >> I suggest adding two GSUB features. 'cabp' is used to support GB/Z 40637—2021, 'hypy' is used to support the special glyphs forms used for Hanyu Pinyin.<br>
> >> >> If you have any suggestions or feedbacks, please let me know.<br>
> >> >> Regards,<br>
> >> Eiso_______________________________________________<br>
> >> mpeg-otspec mailing list<br>
> >> <a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a><br>
> >> <a href="https://lists.aau.at/mailman/listinfo/mpeg-otspec" target="_blank">
https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><br>
> > _______________________________________________<br>
> mpeg-otspec mailing list<br>
> <a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a><br>
> <a href="https://lists.aau.at/mailman/listinfo/mpeg-otspec" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><o:p></o:p></span></p>
<div id="ydpfa331328yqtfd11129">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica Neue";color:#26282A"><br>
> _______________________________________________<br>
> mpeg-otspec mailing list<br>
> <a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a><br>
> <a href="https://lists.aau.at/mailman/listinfo/mpeg-otspec" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><br>
> _______________________________________________<br>
> mpeg-otspec mailing list<br>
> <a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a><br>
> <a href="https://lists.aau.at/mailman/listinfo/mpeg-otspec" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><br>
<br>
<br>
_______________________________________________<br>
mpeg-otspec mailing list<br>
<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a><br>
<a href="https://lists.aau.at/mailman/listinfo/mpeg-otspec" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>