- From: Yasuo Kida (木田泰夫) via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Aug 2023 04:56:08 +0000
- To: public-i18n-archive@w3.org
Hello Fuqiao, That is super. There would be a few options of doing the investigation depending on the amount of time they wan to use. a. The team at CITPC identify discrepancies, and font developers in China verify if they are also true for fonts they make. b. Setup a semi-joint investigation. Each conducts the investigation and the result will be shared through a periodic joint meeting. Producing single proposal. and anything between a and b. So far issues are found with CFF flavored OpenType fonts. - kida > 2023/08/25 10:34、Fuqiao Xue ***@***.***>のメール: > > > 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 specification says. Two examples so far are kern and VORG. Kida started a team in CITPC <https://moji.or.jp/> to review all tables in C/J fonts to find out if there are any similar issues. The goal is to propose modifications to the Open Font Format team in ISO/IEC. > > We want some more engineers from font developers to participate; it would be great if someone is familiar with TrueType flavored fonts and knowledgeable about Chinese fonts. > > If there is a detailed description of use cases and font issues/gaps, I'd be happy to ask Chinese font developers. > > — > Reply to this email directly, view it on GitHub <https://github.com/w3c/jlreq/issues/373#issuecomment-1692628555>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH5C6A4VJPTDGE4GXWD6DZDXW76LFANCNFSM6AAAAAA35XNTRE>. > You are receiving this because you authored the thread. > -- GitHub Notification of comment by kidayasuo Please view or discuss this issue at https://github.com/w3c/jlreq/issues/373#issuecomment-1692757201 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 25 August 2023 04:56:11 UTC