NFSL2001

Here is update flow in future: 1. Common UFOZ (non-differentiated glyphs) will remain the same. 2. Width difference will need to modify the UFO. 1. editing glyphs = replacing glif...

> Also, you'd mentioned `public.verticalOrigin` has gone missing, but it appears not to even be present in your version of the UFO files either, which makes me wonder if there's...

The author has checked and noted that the separated UFO and UFOZ are using different contour direction in the final font file. Latin are clockwise and common are counter-clockwise. ...

So just to confirm, use counter-clockwise/black on left? The sources and editing are in TrueType (quadratic) outlines, and according to TrueType specs they should be clockwise/black on right, which is...

Thanks, is the files updated? We're ready to merge soon after verifying the path direction are fixed.

I think we got a problem... did fontmake/gftools builder assumed all inputs are cubic/Bezier and CCW? Even when the source files are all CW, the output TTF is CCW. My...

> I think we got a problem... did fontmake/gftools builder assumed all inputs are cubic/Bezier and CCW? Even when the source files are all CW, the output TTF is CCW....

@aaronbell can you help to check why `bumpfontversion` in GitHub Actions isn't reflected in the build release font files? The test updates are in https://github.com/NightFurySL2001/LxgwWenkaiTC .

@aaronbell actually never mind, the problems are found: `reverseOutlineDirection: False` for TTF direction, and (quite silly) build fonts going into `fonts/ttf` by default in fontmake, but the repo uses `fonts/TTF`....

感谢您使用这个工具。 1. > 各个分项以不同颜色数值区分与标准库字数的差异。 > 如，除默认的黑色数值表示与标准库字数一致外，是否可以用红色表示不足的情况，绿色表示超出的情况？ 字符集的定义是固定的，并不会出现“超出”某个字符集的定义。若以红色标示不足的字符集，多数情况下界面将会是红色，且‘不足’的定义也因人而异。未来可能会加上绿色表示填充完整字符集而已。 2. > 可否另外增加一条“其他字数”，即除已经列出的各项字符之外，该字体文件包含的其他字符数量，这样也可以通用于各种字体文件的字符数量的检查，或更进一步，在点击该字数后，显示一个扩展页面，以显示字符的其他分类等更多信息。 正式版更改界面时将会实践，待优化代码后应该会有此功能。