You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove double call to pyftsubset with error handlign and recovery
Change the per-page text aggregation to not be overridden in the case where we're configured to use a site-wide subset. Keep test per page, also create site-wide subset in a different property. Switch between them based on config, or create a new property for the current set in use per page. This should enable the ability to bak track a missing glyph to a specific page
Improve error message of missing glyphs per page. Possible narrowing it down to exact line and char offset on the page (if the glyph is from html)
Maybe also look into the possibility of wrapping a <span> around missing glyphs that appear in html, in order to style them with the fallback system font. There will be obvious problems, liek styling from the outside hitting the span in an unintentional way, but it might be worth spending some time to map them out to lean if we can solve it
The text was updated successfully, but these errors were encountered:
The current implementation warn about missing glyphs, but only for local subsetting, which might not be the most likely entry first-use case.
pyftsubset
with error handlign and recoveryMaybe also look into the possibility of wrapping a
<span>
around missing glyphs that appear in html, in order to style them with the fallback system font. There will be obvious problems, liek styling from the outside hitting the span in an unintentional way, but it might be worth spending some time to map them out to lean if we can solve itThe text was updated successfully, but these errors were encountered: