justvanrossum / nabla Goto Github PK

Or the specimen should be tweaked. The M in the first line gets clipped at the top:

Is there a .woff2 version you could include in the download? I know there are tools I could use to convert it but some of those are not compatible with variable color fonts afaik.

specimen.html and docs/index.html are now diverging.

Maybe specimen.html should be deleted, although it's still useful to proof a locally built font.

I can't seem to get this font to work for me on mobile devices and I'm not sure what I'm doing wrong. Both google fonts + your website is able to display it fine on mobile, but I simply get black text.

Here is my css:

@import url('https://fonts.googleapis.com/css2?family=Nabla:EDPT,EHLT@150,12');

#name {
  font-family: 'Nabla', Helvetica, sans-serif;
  font-variation-settings: "EDPT" 150, "EHLT" 12;
  font-palette: --Nabla;
}

@font-palette-values --Nabla {
	font-family: 'Nabla';
	base-palette: 1;
}

All I get is this:

<h1 id="name">Text Text</h1>

Any idea what I am doing wrong?

• Add named instances (see also #22) com.google.fonts/check/varfont_has_instances
• avar #25 com.google.fonts/check/mandatory_avar_table
• gasp #24 com.google.fonts/check/gasp
• prep #24 com.google.fonts/check/smart_dropout
• fvar com.google.fonts/check/varfont/regular_wght_coord et al.
• file name (depends on axis tags) com.google.fonts/check/canonical_filename
• STAT axis values com.google.fonts/check/STAT/gf-axisregistry et al.

• googlefonts/axisregistry#58
• googlefonts/axisregistry#60

This doesn't make sense, and can cause confusion elsewhere. Reported by @yarmola in justvanrossum/fontgoggles#276 (comment)

I understand that the GF-served version of this font contains an SVG table as a fallback for COLR.

In Safari (macOS 10.15.7, Safari 15.6.1), going to this GF URL shows this:

Whereas Bungee Spice shows this:

At the same time I get the report from @GaetanBaehr that the SVG fallback also doesn't show color in (up-to-date) Adobe Illustrator and InDesign, whereas other SVG-in-OT fonts do.

Posted here by request of @chrissimpkins, Cc @anthrotype

Especially now that #2 is more or less resolved.

Where shapes meet, the background color bleeds through:

We'll probably have to make all shapes one or more units thicker, so there will be a small overlap.

• Come up with a name for the typeface (not containing the word "color")
• Change the name of the repo and source file accordingly, adapt build.sh
• Define initial gradient palette: how many colors? Which colors play which role?
• Add gradients to the "sides"; this needs a "side-gradient" glyph layer containing open paths with named nodes. Node names will be mapped to colors.
• Add a gradient to the "front": will this be a fixed colorline for all glyphs, or will individual glyphs need customization? If a per-glyph thing is needed, we can use a verical line representing the color line, and put it in a "front-gradient" glyph layer.
• Add highlights; this needs a "highlight" glyph layer containing open paths that represent the highlights.
• [ ] Write code for shape exceptions, such as the dot on the i.
• Add fontbakery step to workflow

Do we need platformID="1"? I think this is automatically generated by Glyphs.

And when I scan with fontbakery check-universal Nabla\[EDPT,EHLT\].ttf, there is an error that says:

 According to the 'fvar' documentation in OpenType spec v1.9
      https://docs.microsoft.com/en-us/typography/opentype/spec/fvar

      The default instance of a font is that instance for which the coordinate
      value of each axis is the defaultValue specified in the corresponding
      variation axis record. An instance record is not required for the default
      instance, though an instance record can be provided. When enumerating
      named instances, the default instance should be enumerated even if there
      is no corresponding instance record. If an instance record is included
      for the default instance (that is, an instance record has coordinates set
      to default values), then the nameID value should be set to either 2 or
      17, and the postScriptNameID value should be set to 6.


     FAIL 'Regular' instance has the same coordinates as the
          default instance; its subfamilyNameID should be either 2 or 17,
          instead of 258. [code: invalid-default-instance-subfamily-nameid:258]

     FAIL 'Regular' instance has the same coordinates as the
          default instance; its postScriptNameID should be 6, instead of 259.
          [code: invalid-default-instance-postscript-nameid:259]

  <name>
    <namerecord nameID="256" platformID="1" platEncID="0" langID="0x0" unicode="True">
      Extrusion Depth
    </namerecord>
    <namerecord nameID="257" platformID="1" platEncID="0" langID="0x0" unicode="True">
      Edge Highlight
    </namerecord>
    <namerecord nameID="258" platformID="1" platEncID="0" langID="0x0" unicode="True">
      Regular
    </namerecord>
    <namerecord nameID="259" platformID="1" platEncID="0" langID="0x0" unicode="True">
      Nabla-Regular
    </namerecord>
    <namerecord nameID="260" platformID="1" platEncID="0" langID="0x0" unicode="True">
      Shallow
    </namerecord>
    <namerecord nameID="261" platformID="1" platEncID="0" langID="0x0" unicode="True">
      Deep
    </namerecord>
    <namerecord nameID="262" platformID="1" platEncID="0" langID="0x0" unicode="True">
      No Highlight
    </namerecord>
    <namerecord nameID="263" platformID="1" platEncID="0" langID="0x0" unicode="True">
      Highlight
    </namerecord>
    <namerecord nameID="264" platformID="1" platEncID="0" langID="0x0" unicode="True">
      Max Highlight
    </namerecord>
    <namerecord nameID="0" platformID="3" platEncID="1" langID="0x409">
      Copyright 2022 The Nabla Project Authors (https://github.com/justvanrossum/nabla)
    </namerecord>
    <namerecord nameID="1" platformID="3" platEncID="1" langID="0x409">
      Nabla
    </namerecord>
    <namerecord nameID="2" platformID="3" platEncID="1" langID="0x409">
      Regular
    </namerecord>
    <namerecord nameID="3" platformID="3" platEncID="1" langID="0x409">
      1.000;TYPT;Nabla-Regular
    </namerecord>
    <namerecord nameID="4" platformID="3" platEncID="1" langID="0x409">
      Nabla Regular
    </namerecord>
    <namerecord nameID="5" platformID="3" platEncID="1" langID="0x409">
      Version 1.000
    </namerecord>
    <namerecord nameID="6" platformID="3" platEncID="1" langID="0x409">
      Nabla-Regular
    </namerecord>
    <namerecord nameID="9" platformID="3" platEncID="1" langID="0x409">
      Arthur Reinders Folmer
    </namerecord>
    <namerecord nameID="12" platformID="3" platEncID="1" langID="0x409">
      http://www.typearture.com
    </namerecord>
    <namerecord nameID="13" platformID="3" platEncID="1" langID="0x409">
      This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://scripts.sil.org/OFL
    </namerecord>
    <namerecord nameID="14" platformID="3" platEncID="1" langID="0x409">
      https://scripts.sil.org/OFL
    </namerecord>
    <namerecord nameID="256" platformID="3" platEncID="1" langID="0x409">
      Extrusion Depth
    </namerecord>
    <namerecord nameID="257" platformID="3" platEncID="1" langID="0x409">
      Edge Highlight
    </namerecord>
    <namerecord nameID="258" platformID="3" platEncID="1" langID="0x409">
      Regular
    </namerecord>
    <namerecord nameID="259" platformID="3" platEncID="1" langID="0x409">
      Nabla-Regular
    </namerecord>
    <namerecord nameID="260" platformID="3" platEncID="1" langID="0x409">
      Shallow
    </namerecord>
    <namerecord nameID="261" platformID="3" platEncID="1" langID="0x409">
      Deep
    </namerecord>
    <namerecord nameID="262" platformID="3" platEncID="1" langID="0x409">
      No Highlight
    </namerecord>
    <namerecord nameID="263" platformID="3" platEncID="1" langID="0x409">
      Highlight
    </namerecord>
    <namerecord nameID="264" platformID="3" platEncID="1" langID="0x409">
      Max Highlight
    </namerecord>
  </name>

According to https://caniuse.com/?search=font-palette, font-palettes should be supported by all current browser versions. Still, Firefox doesn’t display Nabla’s palettes reliably (?). Further tests with other color fonts worked fine, so I wonder whether this is a browser problem or a font issue.

Hi there, @justvanrossum! What an amazing typeface you've created, and extra cool that it is open source. ✨ 🙌 ✨

Would you consider adding a license to your repo that signals how you'd like it to allow it to be used? That would be helpful for lots of folks (whether individuals or teams) who need to take licensing restrictions into consideration when they use your font in their projects.

Warm regards,
Joel

This to make it more easy to integrate into the GF system.

Hello!

This is an automatically-generated report about possible interpolation problems in Nabla[EDPT,EHLT].ttf, as found in the Google Fonts catalog.

The particular version of the font that was tested was v1.002/nabla-fonts.zip.

To download a PDF version of this report with helpful visuals of the problems, click here; Or to view it on the GitHub website, click here.

The report follows:

Glyph acute was not compatible:
  Masters: '', 'EDPT=0.0':
    Contour order differs: [0, 1, 2] in '', [1, 0, 2] in 'EDPT=0.0'
Glyph acutecomb was not compatible:
  Masters: '', 'EDPT=0.0':
    Contour order differs: [0, 1, 2] in '', [1, 0, 2] in 'EDPT=0.0'
Glyph slash was not compatible:
  Masters: '', 'EDPT=0.0':
    Contour order differs: [0, 1, 2] in '', [2, 1, 0] in 'EDPT=0.0'

This report was generated using the fonttools varLib.interpolatable tool. We understand that sometimes the tool generates false-positives. Particularly for more complicated font designs. If you did not find this report useful, please apologize and ignore & close it.

To give feedback about this report, please file an issue or open a discussion at fonttools.

just curious why you decided to turn off the gvar IUP optimization? Is it for speed or does it create issues somewhere else?

Fontbakery:

Ensure variable fonts include an avar table.
Check ID: <FontBakeryCheck:com.google.fonts/check/mandatory_avar_table>
Most variable fonts should include an avar table to correctly define axes progression rates.

For example, a weight axis from 0% to 100% doesn't map directly to 100 to 1000, because a 10% progression from 0% may be too much to define the 200, while 90% may be too little to define the 900.

If the progression rates of axes is linear, this check can be ignored. Fontmake will also skip adding an avar table if the progression rates are linear. However, we still recommend designers visually proof each instance is at the desired weight, width etc.

🔥 fonts/Nabla.ttf
	• 🔥 FAIL
This variable font does not have an avar table. [code: missing-avar]

Can we just skip this check, or should I add a no-op avar table just to keep this check quiet? TBH it feels this FAIL should be a WARNING.

It's not really an opsz axis, and I wouldn't really want it to be tuned automatically based on the point size. But what other google-fonts-supported axis would fit the bill for this effect?

@davelab6 ?