<html><head></head><body><div class="ydpa73751e7yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>Meant to reply-all.</div><div><br></div>
<div id="ydpa73751e7yahoo_quoted_2708580616" class="ydpa73751e7yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>----- Forwarded message -----</div>
<div><b>From:</b> Hin-Tak Leung <htl10@users.sourceforge.net></div><div><b>To:</b> 木田泰夫 <kida@mac.com></div><div><b>Sent:</b> Monday, 21 August 2023 at 14:50:48 BST</div><div><b>Subject:</b> Re: [MPEG-OTSPEC] Discrepancies between OpenType Japanese fonts and OT spec</div><div><br></div>
<div><div id="ydpa73751e7yiv4506109673"><div><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;" class="ydpa73751e7yiv4506109673ydpa1e55d58yahoo-style-wrap"><div></div>
<div>Hi Kida kun,</div><div><br clear="none"></div><div>Are you talking about some part of the spec not being appropriate / practical for Japanese/CJK, or that implementers (Microsoft's font scaler, Apple's coretext, freetype/harfbuzz) not following what the specs said?</div><div><br clear="none"></div><div>Implementers have their own schedules and priorities (and sometimes, for strategic reasons, simply don't follow the spec or community consesus, when it is a business advantage to not follow.), and have different release schedules, compared to the opentype/open font format releases.</div><div><br clear="none"></div><div>It is a bit confusing what you wrote.</div><div><br clear="none"></div><div>Regards,</div><div>Hin-Tak</div><div><br clear="none"></div><div><br clear="none"></div><div><br clear="none"></div>
<div id="ydpa73751e7yiv4506109673ydpa1e55d58yahoo_quoted_3571329559" class="ydpa73751e7yiv4506109673ydpa1e55d58yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div id="ydpa73751e7yiv4506109673yqt75093" class="ydpa73751e7yiv4506109673yqt5180721993"><div>
On Monday, 21 August 2023 at 08:14:41 BST, 木田泰夫 <kida@mac.com> wrote:
</div>
<div><br clear="none"></div>
<div><br clear="none"></div>
<div><div id="ydpa73751e7yiv4506109673ydpa1e55d58yiv2906859256"><div><div><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><span style="background:none;margin-top:0pt;margin-bottom:0pt;">Hello Vladimir and all,</span></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><br clear="none"></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><span style="background:none;margin-top:0pt;margin-bottom:0pt;">In the last few months, we noticed discrepancies between how CFF-based OpenType Japanese fonts have been implemented for these 20+ years and what OpenType/Open Font Format specification says. Two examples so far are kern (should be default off for fullwidth characters) and VORG (mandatory for CFF-based OT fonts), but there might be more. Most likely, the issue is common to Chinese CFF-based OT fonts and possibly Korean.</span></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><br clear="none"></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><span style="background:none;margin-top:0pt;margin-bottom:0pt;">I hope they will be fixed in the upcoming release.</span></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><br clear="none"></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><span style="background:none;margin-top:0pt;margin-bottom:0pt;">We started a team in </span><a shape="rect" href="https://moji.or.jp/" style="background:none;margin-top:0pt;margin-bottom:0pt;color:rgb(74, 110, 224);" class="ydpa73751e7yiv4506109673ydpa1e55d58yiv2906859256editor-rtfLink" rel="nofollow" target="_blank"><span style="background:none;margin-top:0pt;margin-bottom:0pt;">CITPC</span></a><span style="background:none;margin-top:0pt;margin-bottom:0pt;">, with help from Nat/Taro at Adobe, to go through all tables in C/J fonts to find out if there are any other similar issues. We could either propose changes individually as we find them or wait until the investigation is complete and submit a proposal covering all known issues.</span></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><br clear="none"></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><span style="background:none;margin-top:0pt;margin-bottom:0pt;">I am leaning toward the piecemeal approach, but I would appreciate it if you could advise me on how we should move forward.</span></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><br clear="none"></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><span style="background:none;margin-top:0pt;margin-bottom:0pt;">Thank you and best,</span></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><br clear="none"></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><span style="background:none;margin-top:0pt;margin-bottom:0pt;">- kida</span></p><p style="color:rgb(14, 16, 26);background:none;margin-top:0pt;margin-bottom:0pt;"><br clear="none"></p><br clear="none" class="ydpa73751e7yiv4506109673ydpa1e55d58yiv2906859256Apple-interchange-newline"></div></div></div>_______________________________________________<br clear="none">mpeg-otspec mailing list<br clear="none"><a shape="rect" href="mailto:mpeg-otspec@lists.aau.at" rel="nofollow" target="_blank">mpeg-otspec@lists.aau.at</a><br clear="none"><a shape="rect" href="https://lists.aau.at/mailman/listinfo/mpeg-otspec" rel="nofollow" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><br clear="none"></div></div>
</div>
</div></div></div></div></div>
</div>
</div></div></body></html>