Giters

arrowtype / shantell-sans

Shantell Sans, from Shantell Martin, is a marker-style font built for creative expression, typographic play, and animation.

Home Page:https://shantellsans.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Update axis naming once new axes are accepted into Google Fonts Axis Registry

arrowtype opened this issue · comments

commented

Aside from visual improvements (drawing, spacing, kerning), the following steps are needed to make these fonts ready to launch.

Next

  • check if vertical metrics should really be included in the font (answer: almost certainly not; they are for vertical typesetting)
  • fix winAscent & winDescent (set to avoid clipping; useTypeMetrics added)
    • test the result in mac apps
  • Run FontBakery on VF and sampling of statics, then add to this list as needed
  • narrow down features to single source of truth, then update how calt is added in build-prep
  • the static build interpolates UFOs twice – once for TTFs, and again for OTFs. Simplify this.
  • set underline and strikethrough values
  • update GDEF in features during build-prep
  • maybe change pseudo-random code from calt to rlig? (discussion). This would more strictly ensure that randomness is "on" for users, and would leave the yukrcyr_yukrcyr ligature alone in calt.
    • update static subsetter to remove rlig, not calt, in normal instances
    • test rlig with tracking… it should work but would be good to know (result: yes, it works even when tracking is turned up, as tested in Safari, Chrome, and InDesign)
  • test 1.005 build with fewer instances (googlefonts/axisregistry#38 (comment))
  • make "prepped for google fonts" release folder, similar to Recursive
  • add zero feature for slashed zero, because it’s nice

Based on fontbakery run with latest version of fontbakery

  • prevent build from generating .alt3 glyphs if they are not in the uppercase or lowercase variables (making them unreachable in the simpler part of the rlig feature)
  • add the "dotted circle character (U+25CC)"
  • remove overlaystrokeshortcmb from GDEF marks category Not important.
  • add meta table (requires research) FontMake doesn't seem to do this yet, as far as I can tell. googlefonts/fontmake#934. I probably won’t add it unless it becomes important.
  • add ligature carets (anchors starting with caret_ for fontmake) Not important.
  • debug STAT table adding

Also

  • decide whether/how to define axes on web specimen
  • Feedback from Yanone (#114)

Finally...

  • add OFL license to main
  • make repo public
  • get axis definition PRs merged
  • change axis naming, if required
  • (once axes are merged) PR font to google/fonts; get Yanone’s help
commented
  • Adjust contours to avoid this overlap-removal issue:

image

commented

Questions asked and answered on a Google Fonts weekly meeting:

  • Is it important to add a meta table?
  • Is it important to add ligature carets?
  • Is it important to remove overlaystrokeshortcmb from GDEF marks category?

Answers: if they are only warn level messages in FontBakery, these are safe to ignore for now.