GithubHelp home page GithubHelp logo

alumni-sans-pinstripe's People

Contributors

crystaltype avatar davelab6 avatar fonthausen avatar vv-monsalve avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

isabella232

alumni-sans-pinstripe's Issues

L1 Mastering Font checklist

L1 Mastering Font checklist

Diacritics

  • Inspect the font and choose the best version of the diacritics (in terms of balance, weight, size, contrast) and move them to comb mark.
  • Adjust left and right sidebearings of all the comb marks to 0.
  • Work on the selected diacritics to ensure the balance among all marks (contrast, weight, size, stroke or others)
  • Ensure the consistence among related marks, see issue of reference.
  • Adjust position, weight, or outlines of the diacritics if needed to, without changing the design of them, and using glyphs app locked guidelines.
  • Decomposed transformed components, review proportions ensuring round coordinates.
  • Test the comb marks by inspecting all of them in context (right-click and choose all glyphs using this component).
  • Inspect and balance the below marks (size, weight, balance) e.g. ogonek cedilla to avoid huge marks
  • Create Catalan Punt Volat
  • Delete the legacy marks and add them back so they are made from comb marks.
  • Create comb.case marks by making them less tall and less narrow while keeping them at the same weight (preferable at the height they are intended to use, to be able to inspect them in their context)
  • Create the Vietnamese mark.
  • Make compound glyphs for the entire font.
  • Adjust the anchor position.
  • Run the automatic Glyphsapp command: update glyph info.

Glyphs & Outlines

  • Create the missing glyphs needed.
  • Run the automatic Glyphsapp commands: Add extremes; cubic curves; correct outlines direction; tidy up paths; round coordinates; remove PS Hint
  • Check kerning and spacing by using the txt files. Fix any kerning and spacing errors if needed for the most common kerning pairs.
  • Check spacing and kerning for numerlas (main + .lf) and use arithmetic spacing for the .lf ones
  • Check terminal forms spacing to avoid crashes or collisions. Issue of reference
  • Run the automatic Glyphsapp command: Resolve all metrics to update the metrics in the entire font.
  • Check everything once again by going glyph by glyph.
  • Run the automatic Glyphsapp Update Glyph Info command to avoid bad names issues
  • Run the automatic Glyphsapp Convert to cubic command to avoid qcurves
  • @ ¿? ¡! ”” «» position, spacing is good
  • Lining figures based of main ones + spacing + kerning

OT Features

  • All the features that should be done automatically to be done in that way, e.g. All Letters
  • Check OpenType features and see if all listed are valid, e.g. if .fina glyphs are actually ending shapes or ss are not repeated under different names.
  • Create Lookup for positional alternates for fina and init cases
  • Inspect if Stylistic Sets have the right name or rename .001 etc... glyphs and generate the automatic OpenType code.
  • Check if there is a stylistic set that would correspond to SmallCaps feature instead and change it.
  • Check if the OpenType code has any error.
  • Hit the update & compile buttons to check everything is working well.

Testing changes

  • Inspect the font created by the CI GHA to check production errors. If the action isn't included yet in the repo, export and test the font using Glyphs.
  • Check the before and after font using gen-html diff if needed (for update font cases)
  • Check the font on gen-html proof to see if it's working well on web. Use the --imgs flag to produce images.
  • Commit and make PR using images.

Font Production L1

  • QA assessment
  • Review/Adjust metrics and alignment zones
  • Review/adjust coord axes + custom param
  • Add extremes; cubic curves; correct outlines direction; sound coordinates; remove PS Hint
  • Adjust Vertical metrics
  • Include License strings
  • fsSelection bit 7
  • fsType bit 0
  • Copyright strings
  • Information files (Authors, Contributors)
  • OFL (good copyright license + working git link)
  • Description (good working link)
  • Update Glyph info
  • Readme + sample image
  • First spacing & kerning review
  • Bump version number
  • Build
  • CI build & test
  • OT L1 features check
  • FB QA
  • Regression QA (if apply)
  • Visual QA
  • html + apps (testing + proofing)
  • PR

Design Issue

Google Fonts Latin Core & Plus coverage

  • Design all the glyphs required both in the Latin Core + GF Latin Plus encoding
  • Create all the comb marks as mentioned below
  • Leave only the compound glyphs (e.g. adblgrave) marked in dark grey as pending to be created using the components

Diacritics

  • Please ensure the definitive design is adjusted in the combining marks, so they will be ready to create the compound glyphs.
  • Once the definitive design is ensured in the comb marks Legacy marks, delete the legacy marks and add them back so they are made using the comb marks as components.
  • Diacritics need to be balanced (in weight, size, contrast) and match the style of the typeface design.
  • Adjust the vertical position using glyphs app locked guidelines.
  • Ensure related marks are consistent between them, e.g. caron and circumflex
  • Caron.alt need to have the alternate shape used in Ľ Slovak On page 30 of this document you can find detailed info around the vertical Caron.
  • Leave a 0 sidebearings value for the marks

Glyphs

  • The ampersand and Eng need to be consistent (in size and style) with the font. See RUSerius as reference
  • The German Double SS need to be fixed. This article is a good reference
  • Currency symbols are related to the overall design and have balanced proportions
  • ordfeminine and ordmasculine as well as superior numbers are well proportioned and with a balanced stem thickness. Issue of reference
  • fractions and superior numerals have a good proportion + weight. Issue of reference

Spacing

  • Inspect the spacing and kerning of the font to ensure it is working properly and most common cases are covered. Issue of reference
  • Terminal forms spacing should avoid crashes or collisions. Issue of reference

Browsers Preview

OS X High Sierra Safari_11
Desktop_OS_X_High_Sierra_safari_11 1_
Windows 10 Chrome_71
Desktop_Windows_10_chrome_71 0_
Windows 10 Edge_18
Desktop_Windows_10_edge_18 0_

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.