-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare Fraunces for Google Fonts #1
Comments
Useful regex recipe to match & update UFO paths via find & replace:
Process to fix style names but keep proper UFO paths:
(etc) Changes made:
Lingering challengeSome names are getting a space removed between the opsz and SOFT labels. This formation isn’t anywhere in the designspaces, so it is likely due to a regex issue in
The problem: the Fraunces/mastering/scripts/fixNameTable.py Lines 42 to 61 in 9551c8d
Name table with fixNameTable.py (Click to expand)
Name table without fixNameTable.py (Click to expand)
Another Name table without fixNameTable.py (Click to expand)
The fixNameTable script doesn’t seem to have an advantage for Fraunces static name tables ... BUT it also adjusts the |
Further fixes to
|
Some of these fixes will follow the work from Viviana at https://github.com/vv-monsalve/Fraunces/issues/2
Assumptions on naming:
WONK
axis name should be “Wonky”, per Proposal: “Wonkiness” axis name should be “Wonky” due to its binary usage; "Normal" name should be "NonWonky" google/fonts#2741WONK
STAT names should beWonky
(elided) andNonWonky
Proposal: “Wonkiness” axis name should be “Wonky” due to its binary usage; "Normal" name should be "NonWonky" google/fonts#2741 (comment)SOFT
axis instance names should beSharp
,Soft
, &ExtraSoft
(Why do style names include spaces in the Axis Registry, but not in practice? google/fonts#2742)Fontbakery fixes
Whitespace naming
com.google.fonts/check/whitespace_glyphnames: Glyph 0x0020 is called "uni0020": Change to "space"
– probably by adding--no-production-names
arg to fontmakeNow that I have added
--no-production-names
, I now get the message* WARN: Glyph 0x00A0 is called "nbspace": Change to "uni00A0" [code: not-recommended-00a0]
.Not sure if this is worth worrying about...
Optical size default must be 9pt
WARN: The "opsz" (Optical Size) coordinate on the "Regular" instance is recommended to be a value in the range 9 to 13. Got 144.0 instead.
9
, butmastering/scripts/removeUnwantedVFInstances.py
removes all instances but those with opsz=144... will investigate furtherDescription length
FAIL: DESCRIPTION.en_us.html must have size smaller than 1000 bytes.
– asked at FontBakery requires the DESCRIPTION.en_us.html to be <1000 bytes (i.e. <1000 characters, including HTML) undercasetype/Fraunces#249
com.google.fonts/check/ligature_carets
add ligature caretsActually, I have added these to to UFOs, but ufo2ft doesn’t yet support this, so this is pointless. As was said at undercasetype#206:Fontbakery false fails:
com.google.fonts/check/usweightclass – * FAIL: OS/2 usWeightClass is '900' when it should be '400'. [code: bad-value]
Add VF check to ensure os/2 weightClass is same as default wght axis position fonttools/fontbakery#2364[WIP – more to come here]
The text was updated successfully, but these errors were encountered: