[Koha-bugs] [Bug 22983] The Koha copy of NotoSans font (in the new OPAC) lacks glyphs for (some) Roman letters with diacritics

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22983

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #11 from David Cook <dcook at prosentient.com.au> ---
Is this still an issue? It looks like the font family CSS has moved on a bit
over the past few years...

--

I haven't seen this issue personally, but I mostly work in English, French,
Arabic, and Chinese. English and French are included in the Noto Sans font,
while Arabic is in Noto Sans Arabic font and Chinese has a few Noto Sans
Chinese fonts. 

I'm not a font expert by any means, but recently I created a custom
NotoSansTC-Regular TFF file for label printing in Chinese and English. That's a
very different use case but I learned a lot about fonts in the process.

Little tip for troubleshooting fonts in Chrome: 
- Inspect the element
- Go to "Computed"
- Scrolldown to the very bottom to see a "Rendered Fonts" section. 

I'm looking at an OPAC with English and Arabic right now, and it's telling me
that it's rendered 11 glyphs using a local file for Segoe UI and 2 glyphs using
a local file for Noto Sans. A bit of trial and error proved the 2 Noto Sans
glyphs were the space character and a punctuation mark. 

When using the Google Fonts tester, I type in some Polish and I can see that it
is using "Noto Sans - Network resource" for the 16 glyphs. 

--

Now back to Koha... if "fonts/NotoSans-Regular-webfont.woff2" is being used,
that would mean that "Noto Sans Regular" isn't available locally. 

But if the glyph isn't available in "fonts/NotoSans-Regular-webfont.woff2", it
should move on to "sans-serif" (when this issue was raised, I don't think the
CSS was "NotoSans, sans-serif" so maybe that was contributing to the problem).

But even without "sans-serif", it should still resort to a default system font
(like "Times New Roman" on English Windows systems).

--

So ultimately this one sounds like a misconfigured local system to me.

-- 
You are receiving this mail because:
You are watching all bug changes.