How useful is the contour_count check? Some examples
See original GitHub issueAfter improving the check routine a bit by addressing issue #2612, I am not considering how useful the check is (in comparison to how it extremely often emits false-WARN
s)
Here are my current concerns:
- Most families in the Google Fonts collection do not
PASS
this check due to false-WARN
s. - Should this remain as a
WARN
-level check? - Should it be completely deprecated?
- Or should it be downgraded to merely
INFO
-level?
Example 1
Here’s a good example of the check detecting an actual problem:
zooming in:
Example 2
Another reasonable warning with the same font (the “divide” glyph only has dots but lacks a bar):
Example 3
Here’s a group of false-WARN
s on OleoScript-Bold. The glyphs are actually good, but the loops in them result in a different count then what would be expected in most designs:
Example 4
Another good catch: weird contours self-overlapping in SingleDay-Regular glyph “f”:
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
New in iOS 14: Vision Contour Detection - by Anupam Chugh
This computer vision task is useful for shape analysis, edge detection, and is helpful in scenarios where you need to find similar types...
Read more >Vision Framework Tutorial for iOS: Contour Detection - Kodeco
Learn how to detect and modify image contours in your SwiftUI iOS apps in a fun and artistic way using the Vision framework....
Read more >Detect text area in an image using python and opencv
Still, useful to know it exists if you don't want to code the algorithm ... kern_size ) # dilate img and check current...
Read more >Explore Computer Vision APIs - WWDC20 - Videos
Learn how to bring Computer Vision intelligence to your app when you combine the power of Core Image, Vision, and Core ML. Go...
Read more >googlefonts — Font Bakery 0.7.34 documentation
The expected contour count data for this check is currently optimized for the ... This check is merely informative, displaying and useful comparison...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sure, but this is often to find a
%
without a bar in the middle, and aé
where the acute overlaps the e because the marks as mispositioned will not be found today, as there are 2 contours, but will be found in this case. So the overlap-removed version is a separate check that also needs human inspection.The check should have instructions to the human so they can do their job well 😃
I believe the solution to this is to have more fine grained leveling of check results; some FAILs are extremely critical and some are important enough to be FAILs but are okay to wait to fix until later… and some WARNs are important to pay attention to, and some WARNs are not so important.
Viviana mentioned on a call that having the check output an alphabetically sorted, comma separated, single line, and, an alphabetically sorted, line break separated, list, of glyph names to check, would help users so they can copy and paste that list into their font editor to check these things.