Noto Sans Symbols 2 type tester and glyphs overview are outdated on fonts.google.com

[LaPingvino]

This issue also works for requesting features.

Describe the issue On the fonts.google.com website, Noto Sans Symbols 2 seems up to date for the download part, e.g. 🟙 is properly included, but it and e.g. Kaktovik numerals don't show in the glyph list or appear properly when using the type tester.

To Reproduce Try looking for the nine pointed star in the glyph list (should appear after the go symbols) or try typing/copy-pasting 🟙 (U+1f7d9).

Expected behavior The new characters should appear in the glyph list and work properly in the type tester.

Additional context New characters since Unicode 15 and possibly 15.1

[emmamarichal]

@simoncozens, is it a subset issue?

[simoncozens]

In general: If a glyph is in the font we serve but it's not coming out of the web API, then yes, it's likely a subset issue.

In this case: Yes, NINE POINTED STAR is not in the latest symbols nam file, and it should be added, and the same goes for the Kaktovik Numerals block. There are probably other codepoints in Noto Sans Symbols 2 that are not being served. I'll do a test and make a PR.

[simoncozens]

Actually we probably need to re-push the font once this is done; I did add NINE POINTED STAR two weeks ago and apparently Garret merged it.

[LaPingvino]

@simoncozens so now re-push?

[simoncozens]

That's something the eng team do internally. They're working on it!

[LaPingvino]

How long do these things take normally? when should I check in again? @simoncozens

[simoncozens]

Probably a couple of weeks?

[LaPingvino]

https://issuetracker.google.com/issues/289759016 also references an internal bug... any updates on either?

[simoncozens]

Looks OK to me:

[LaPingvino]

Quick check for what works:

• [x] Filter
• [ ] Type tester (shows replacement glyph instead, might be JS issue?)
• [ ] Glyph view (? unless I got the wrong group)

[simoncozens]

Yeah, looks like some stuff on the front end has not been updated to Unicode 15.0. We've hit the limits of my knowledge here, and this becomes a question for the frontend team.

[LaPingvino]

no changes yet... do you know anyone of the right team to ping?

[simoncozens]

@garretrieger?

[garretrieger]

@nathan-williams for the FE team

[LaPingvino]

One month later... is this properly checked, scheduled etc? Just checked with the same checklist and the result is the same, it shows in search but not in the type tester and glyph overview.

[LaPingvino]

@simoncozens @garretrieger @nathan-williams sorry for being annoying... 🙃

[LaPingvino]

Just did a little testing and found the following:

• When using the search page, it fully works
• When using the specimen page, it works at first and then fails when using a link to get to the page, maybe because of a cache overwrite, see next item why
• When using the font tester, it always fails and when testing the woff2 file used on that page (added here) I see that the new characters are still missing here Possibly rebuilding the fonts from the last version might be enough? Looks like some kind of cache invalidation issue for the proper font page... Archive.zip

@simoncozens @garretrieger @nathan-williams

[simoncozens]

No point tagging me, I just provide the fonts and they're working. :-) It's a subsetting issue on the back end. It's not to do with caching but the way that subsets are delivered using CSS.

[vv-monsalve]

I can reproduce the following:

Copy-pasting 🟙 in the field for "Type something" + querying for Noto Sans Symbols works to display the NINE POINTED STAR symbol (for Noto Sans Symbols 2, Noto Symbols displays tofu in that view)

However, when copy-pasting that same glyph into the TypeTester, it shows a tofu.

@nathan-williams could you please take a look at this?

[LaPingvino]

@vv-monsalve @nathan-williams ping 🙈

[vv-monsalve]

@nathan-williams I reran the test (as in my previous comment), but the issue persists. Could you help us understand the root cause and what could be the solution?

[nathan-williams]

@LaPingvino apologies for not noticing the earlier messages that I was tagged in. I realize it's been several months and this turned out to be a pretty simple issue.

The fix should roll out in the next week or two.

[LaPingvino]

thanks a million @nathan-williams ! I already was considering to apply just to get this done 🤭

[LaPingvino]

I suspect it's not your field, but any idea if that has an effect on this? https://issuetracker.google.com/issues/289759016 (updating fallback fonts on Android, ChromeOS and Google Docs)

For ChromeOS it seems to rely on a Gentoo ebuild I'm not certain about if it's still working correctly. For Android and Google Docs I know even less relevant pointers... I hope it's just normal update delay, but my gut feeling says there might be something broken.

[LaPingvino]

Verified fixed, can close @nathan-williams (but will be very pleased if you can give the issuetracker bug a look)