Skip to content

Spacing axis - #9

Merged
Peter Constable (PeterCon) merged 4 commits into
microsoft:masterfrom
LetterModeller:master
Nov 27, 2017
Merged

Spacing axis#9
Peter Constable (PeterCon) merged 4 commits into
microsoft:masterfrom
LetterModeller:master

Conversation

@LetterModeller

Copy link
Copy Markdown
Contributor

No description provided.

@msftclas

Microsoft Contribution License Agreements (msftclas) commented Nov 23, 2017

Copy link
Copy Markdown

CLA assistant check
All CLA requirements met.

@justvanrossum

Copy link
Copy Markdown

Additional application idea:

  • make ligatures properly respond to spacing

Perhaps also mention latin-based connected script typefaces.

@tiroj

Copy link
Copy Markdown
Collaborator

I am interpreting this proposal as for 'optical spacing', i.e. it isn't simply an x-direction 'white space' adjustment feature (although could be implemented as such), but may also involve adjustments to glyph shape (indeed, may require such adjustments in the case of joining scripts), and may involve variable GPOS interaction, e.g. to scale kerning proportionally to variable spacing. Frank E. Blokland (@LetterModeller) does that interpretation fit with what you have in mind.

[I think that for all new axis proposals we need to understand whether the proposed axis is optical or parametric (perhaps this is a category to add to the standard proposal template?). I define an optical axis as one that may affect more than one aspect of a design at a time, e.g. stem weight changing on a width axis; whereas a parametric axis affects only one aspect at a time, independently of others (cf. Amstelvar). These represent two different models of designing a variable font, and it seems fairly important to distinguish whether a given axis proposal is optical or parametric. All five of the initially registered OT variations axes are optical axes, although only one — Optical Size — explicitly acknowledges this.]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The proposal summary is incomplete: it is missing the Administrative and General Technical Information sections, which should precede the Proposed Axis Details section.

Also, the heading for the Justification section is missing. Please keep all of the sections, with headings, in the order given in the template ProposalSummary.md file

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Format needs fixing but details are all there. I'll approve and fix the formatting afterward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants