<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><p style="color: rgb(14, 16, 26); background: none; margin-top: 0pt; margin-bottom: 0pt;"><span data-preserver-spaces="true" 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></p><p style="color: rgb(14, 16, 26); background: none; margin-top: 0pt; margin-bottom: 0pt;"><span data-preserver-spaces="true" 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></p><p style="color: rgb(14, 16, 26); background: none; margin-top: 0pt; margin-bottom: 0pt;"><span data-preserver-spaces="true" 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></p><p style="color: rgb(14, 16, 26); background: none; margin-top: 0pt; margin-bottom: 0pt;"><span data-preserver-spaces="true" style="background: none; margin-top: 0pt; margin-bottom: 0pt;">We started a team in </span><a target="_blank" href="https://moji.or.jp/" class="editor-rtfLink" style="background: none; margin-top: 0pt; margin-bottom: 0pt; color: rgb(74, 110, 224);"><span data-preserver-spaces="true" style="background: none; margin-top: 0pt; margin-bottom: 0pt;">CITPC</span></a><span data-preserver-spaces="true" 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></p><p style="color: rgb(14, 16, 26); background: none; margin-top: 0pt; margin-bottom: 0pt;"><span data-preserver-spaces="true" 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></p><p style="color: rgb(14, 16, 26); background: none; margin-top: 0pt; margin-bottom: 0pt;"><span data-preserver-spaces="true" 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></p><p style="color: rgb(14, 16, 26); background: none; margin-top: 0pt; margin-bottom: 0pt;"><span data-preserver-spaces="true" 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></p><br class="Apple-interchange-newline"></div></body></html>