-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add (Letter Character Face Ratio) [PADG](?) axis #191
Comments
(I should note that the implementation presently in Chiron Hei does not explicitly follow the above master position implementation proposed but I wanted to post this proposal as a mechanism to drive consensus about how to implement it before requesting @tamcy to change anything) |
I wonder if this should be integrated into the Parametric Axes system, as its about Transparency |
Parametrically, this is a combination of XTRA, where the internal white spaces, e.g. horizontal counters, apertures and stems are being extended or reduced,,, at the same time XTSP, a spacing change is going on to maintain a given XTAB width, as it is monospaced? I think you'd need knowledge of each of those things separately in order to blend variations with different inter glyph spacing, among a range of monospaced width options. |
I think the advanceWidth doesn't change, though? |
I suggest CTRA as in 'Central Transparency', but then defining the transparent space to measure isn't obvious to me. @aaronbell mentioned the BASE table common example is |
Hello, this is the creator of Chiron Hei HK. I would like to add that the concept of the character face ratio originates from the era of movable type, where the virtual or outer bounding box represents the actual size of the movable type. The purpose of this proposed In this regard, the axis is comparable to the existing
That is actually identical to what @aaronbell propsoed, with a different scale or frames of reference. I am using the values straightly from In the current implementation of Chiron Hei HK, PADG=0 represents the default ratio, while PADG=10 equates to a 5% reduction in size. Using the above definition, PADG(?)=100 would be the default, and the current PADG=10 would translate to PADG(?)=95. Whether PADG(?)=90 can result in a 5% shrink can be discussed. I believe this should be acceptable as long as it does not cause too much surprise. |
Requirements
By ticking the cases (or putting x between the square brackets in text mode), you confirm the following:
Font project(s) using the axis
https://github.com/chiron-fonts/chiron-hei-hk
Short description of what the axis does
Enables a font to vary the letter/character face ratio (字面率) for a CJK font to provide more spacing between characters.
Image
The glyph on the left has a ratio of 92%, the one on the right has a ratio of 95%.
Why is the axis needed
When the point size becomes smaller (or larger), there is a perceived change in the space between ideographs. To address situations where (a) tracking cannot be changed, or (b) where changing tracking is not tenable (especially in mixed script scenarios), CJK foundries change the letterspace ratio in order to reduce the text density and perception of airiness.
This axis is discernibly different than
SPAC
as it does not cause reflow / affect horizontal advance of the line of text. It has some similarity withopsz
conceptually as it is related to improving rendering at smaller sizes, but I believe the intention is sufficient different to warrant its own axis, especially as it is independent of other optical corrections one might implement.My suggestion is that
PADG
should be a % reduction from 100%. So-10
would represent a 10% reduction in the character face ratio.Note The
PADG
naming convention is one that @tamcy (of Chiron Hei) came up with (referencing "Padding"), and is open to changing. Another option that could work isVBDY
, referencing the Japanese term "Virtual Body").Axis metadata fields
The text was updated successfully, but these errors were encountered: