You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@twardoch had the idea of using Noto as a base for shaping "best practices" for other scripts. As a first approximation, we could scrape the Noto fonts for each script to determine which OpenType features they use, and use that to generate a list of expected features in incoming fonts.
The text was updated successfully, but these errors were encountered:
* Update checker.py
Added mark2base test that uses the serialized buffer to see if a mark has a GPOS shift if placed after a target base mark.
* Use shaper to check whether glyphs exist, see #7
* Add youseedee to requirements
* Fix some lints
* Read your own config file, pylint
* More pylint fixes
* Pin protobuf dependency
* Further poetry dependency fixes
* Cache shaping
* Fix error message
* Implement an "unknown" state
* Implement the "report" option
* Speed up the mark checker
* Don't GSUB closure on pathological fonts
* Make pylint happier
* Make result status machine readable
* A new test for unencoded glyph variants. Fixes#8
* Use the language tag from the language we're checking
* Skip tests based on certain conditions (missing features), fixes#11
* Make linter happier
* Update orthographies check to include auxiliary chars
There is probably a more elegant way to implement this but I have merged auxiliary characters into the bases for the orthographies check. For the purposes of language support testing base and auxiliary characters need to be included to ensure loan words, names and place names can all be typed for a given language.
* Improve error messages
* Add Neil's work
* Pylint stuff
* Update shaping_differs.py
Fixed Type Error caused by trying to concat YAML to str
* Make non-verbose less verbose
* Transfer IP to Google
---------
Co-authored-by: Simon Cozens <[email protected]>
Co-authored-by: Dave Crossland <[email protected]>
@twardoch had the idea of using Noto as a base for shaping "best practices" for other scripts. As a first approximation, we could scrape the Noto fonts for each script to determine which OpenType features they use, and use that to generate a list of expected features in incoming fonts.
The text was updated successfully, but these errors were encountered: