Skip to content
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

VF Stat table: two entries for "Regular"? #164

Open
madig opened this issue Feb 12, 2019 · 1 comment
Open

VF Stat table: two entries for "Regular"? #164

madig opened this issue Feb 12, 2019 · 1 comment
Labels

Comments

@madig
Copy link

madig commented Feb 12, 2019

Why are there two entries for regular in the STAT table (here taken from the Italic VF)?

      <AxisValue index="2" Format="2">
        <AxisIndex value="0"/>
        <Flags value="2"/>
        <ValueNameID value="267"/>  <!-- Regular -->
        <NominalValue value="400.0"/>
        <RangeMinValue value="350.0"/>
        <RangeMaxValue value="500.0"/>
      </AxisValue>
[...]
      <AxisValue index="6" Format="3">
        <AxisIndex value="0"/>
        <Flags value="2"/>
        <ValueNameID value="267"/>  <!-- Regular -->
        <Value value="400.0"/>
        <LinkedValue value="700.0"/>
      </AxisValue>

is it because LinkedValue isn't available in format 2?

Reading the spec, using ranges for the weights IMHO doesn't fit well. If the user sets the VF weight to 799 and the UI still tells him it's bold, it might clash when the document then uses the static bold font for whatever reason and it's less bold than what the designer saw.

@sairuspatel
Copy link

@madig 1. Yes. It is because the font is specifying both a range (format 2) and a style link (format 3) for weight. (Note that this is in technical violation of the current STAT spec: “No two tables should provide information for the same axis value.” We have raised this concern in the OT spec community and are looking at how to resolve it.)
2. Re. your concern “using ranges for the weights IMHO doesn't fit well,” I agree it could be potentially confusing. Note, however, that names in STAT can be combined with precise axis values to avoid this kind of situation. For example, Photoshop displays “Bold-799” for the style name in your example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants