ERROR: check/canonical_filename with MutatorSans-VF
See original GitHub issue@justvanrossum reported at https://github.com/googlefonts/fontbakery/issues/3273#issuecomment-839572283 that the VF in MutatorSans-VF.ttf.zip errors on com.google.fonts/check/canonical_filename
because “the name table doesn’t contain a required entry.”
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (10 by maintainers)
Top Results From Across the Web
How do I resolve a canonical filename in Windows?
Short answer: not really. There is no simple way to get the canonical name of a file on Windows. Local files can be...
Read more >FIO16-J. Canonicalize path names before validating them
Canonicalizing file names makes it easier to validate a path name. ... Invalid file; handle error } FileInputStream fis = new FileInputStream(f); ...
Read more >Blueprint Build System - Go Packages
Unpacks the properties into the Module. * Does not invoke load hooks or any mutators. The filename is only used for reporting errors....
Read more >Add protobuf fuzzer support to OSS-Fuzz · Issue #864 - GitHub
/src/LPM/external.protobuf/include/google/protobuf/arenastring.h:177:57: error: unused parameter 'default_value' [-Werror ...
Read more >apex/apex.go - platform/build/soong - android Git repositories
AndroidManifest *string `android:"path"`. // Canonical name of this APEX bundle. Used to determine the path to the activated APEX on.
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
OK, I think this is better now, right, @justvanrossum? Now we actually FAIL in that specific case:
You could have left the condition in the check, catch the Error and report it as a fail.
Well, if it’s reasonable to do it this way, and the font fails to adhere to that scheme, it qualifies for another check, not?
I’m just looking at the check, it parses the font itself:
ttFont = TTFont(font)
, so, there’s probably more refactoring that should be done.