[Rendering issue, not displaying full charset]

[sannorozco]

Hello Lasse @graphicore,

While displaying RobotoAvar2-Regular, there’s a section that does not display correctly, this is the accents section. In this font we have a lot of sets, but for some reason it only displays two sets, causing confusion.

These are all the accents we have:

HH /grave HH HH /acute HH HH /dieresis HH HH /macron HH HH /cedilla HH HH /circumflex HH HH /caron HH HH /firsttonechinese HH HH /breve HH HH /dotaccent HH HH /ring HH HH /ogonek HH HH /tilde HH HH /hungarumlaut HH HH /hookabove HH HH /breveinverted HH HH /dblgrave HH HH /horn HH HH /dotbelow HH HH /dieresisbelow HH HH /commaaccent HH HH /brevebelow HH HH /macronbelow HH HH /commaaccentturned HH HH /gravecomb HH HH /acutecomb HH HH /circumflexcomb HH HH /tildecomb HH HH /macroncomb HH HH /brevecomb HH HH /dotaccentcomb HH HH /dieresiscomb HH HH /hookabovecomb HH HH /ringcomb HH HH /hungarumlautcomb HH HH /caroncomb HH HH /breveinvertedcomb HH HH /dblgravecomb HH HH /horncomb HH HH /dotbelowcomb HH HH /dieresisbelowcomb HH HH /commaaccentcomb HH HH /cedillacomb HH HH /ogonekcomb HH HH /brevebelowcomb HH HH /macronbelowcomb HH HH /commaaccentturnedcomb HH HH /gravecomb-stack HH HH /acutecomb-stack HH HH /dieresiscomb-stack HH HH /macroncomb-stack HH HH /circumflexcomb-stack HH HH /caroncomb-stack HH HH /brevecomb-stack HH HH /dotaccentcomb-stack HH HH /ringcomb-stack HH HH /tildecomb-stack HH HH /hungarumlautcomb-stack HH HH /hookabovecomb-stack HH HH /breveinvertedcomb.stack HH HH /dblgravecomb-stack HH HH /grave-stack HH HH /acute-stack HH HH /circumflex-stack HH HH /tilde-stack HH HH /macron-stack HH HH /breve-stack HH HH /dotaccent-stack HH HH /dieresis-stack HH HH /hookabove-stack HH HH /ring-stack HH HH /hungarumlaut-stack HH HH /caron-stack HH HH /breveinverted-stack HH HH /dblgrave-stack HH HH /grave.case HH HH /acute.case HH HH /dieresis.case HH HH /macron.case HH HH /cedilla.case HH HH /circumflex.case HH HH /caron.case HH HH /breve.case HH HH /dotaccent.case HH HH /ring.case HH HH /ogonek.case HH HH /tilde.case HH HH /hungarumlaut.case HH HH /hookabove.case HH HH /breveinverted.case HH HH /dblgrave.case HH HH /horn.case HH HH /dotbelow.case HH HH /dieresisbelow.case HH HH /commaaccent.case HH HH /brevebelow.case HH HH /macronbelow.case HH HH /gravecomb.case HH HH /acutecomb.case HH HH /dieresiscomb.case HH HH /macroncomb.case HH HH /cedillacomb.case HH HH /circumflexcomb.case HH HH /caroncomb.case HH HH /brevecomb.case HH HH /dotaccentcomb.case HH HH /ringcomb.case HH HH /ogonekcomb.case HH HH /tildecomb.case HH HH /hungarumlautcomb.case HH HH /hookabovecomb.case HH HH /breveinvertedcomb.case HH HH /dblgravecomb.case HH HH /horncomb.case HH HH /dotbelowcomb.case HH HH /dieresisbelowcomb.case HH HH /commaaccentcomb.case HH HH /brevebelowcomb.case HH HH /macronbelowcomb.case HH HH /gravecombstack.case HH HH /acutecombstack.case HH HH /dieresiscombstack.case HH HH /macroncombstack.case HH HH /circumflexcombstack.case HH HH /brevecombstack.case HH HH /dotaccentcombstack.case HH HH /tildecombstack.case HH HH /hookabovecombstack.case HH HH /grave-stack.case HH HH /acute-stack.case HH HH /dieresis-stack.case HH HH /macron-stack.case HH HH /circumflex-stack.case HH HH /caron-stack.case HH HH /breve-stack.case HH HH /dotaccent-stack.case HH HH /ring-stack.case HH HH /tilde-stack.case HH HH /hungarumlaut-stack.case HH HH /hook-stack.case HH HH /breveinverted-stack.case HH HH /dblgrave-stack.case HH HH /gravecomb-stack.case HH HH /acutecomb-stack.case HH HH /dieresiscomb-stack.case HH HH /macroncomb-stack.case HH HH /circumflexcomb-stack.case HH HH /caroncomb-stack.case HH HH /brevecomb-stack.case HH HH /dotaccentcomb-stack.case HH HH /ringcomb-stack.case HH HH /tildecomb-stack.case HH HH /hungarumlautcomb-stack.case HH HH /hookcomb-stack.case HH HH /breveinvertedcomb-stack.case HH HH /dblgravecomb-stack.case HH

But for some reason TypeRoof displays only a few, This has caused confusion while we review the font. See below:

HHHHHH¨HHHH¯HHHH¸HHHHˆHHHHˇHHHHˉHHHH˘HHHH˙HHHH˚HHHH˛HHHH˜HHHH˝HHHH̀HHHH́HHHĤHHHH̃HHHH̄HHHH̆HHHḢHHHḦHHHH̉HHHH̊HHHH̋HHHȞHHHH̏HHHH̛HHHḤHHHH̤HHHH̦HHHḨHHHH̨HHHḪHHHH̱HHHH̒HH`

Is this the case for updating the groups? How can we access these glyphs with no unicode?

TypeRoof/lib/assets/glyph-groups.yaml

Lines 42 to 44 in c3a0169

	Accents:
	_default: '`¨¯°´ˆˇ˘˙˚˛˜˝‘’¸ʼ'
	_extended: 'ˉ̧̨̛̣̤̦̮̱̀́̂̃̄̆̇̈̉̊̋̌̏̑'

Hope this is easy to fix so we can see all the charset.

Thanks!

[graphicore]

Is this the case for updating the groups? How can we access these glyphs with no unicode?

glyph-groups.yaml will only help if the glyphs have a charcode and can be reached directly

We don't have the means yet to access unencoded glyphs, as we use HTML for rendering and there just is no way to do so. However, with harfbuzz.js we can access and render all the glyphs in the font, I think that would be the way.

Another path, that we don't explore yet, is to access glyphs that require features to be accessed, that could be useful as well though.

[sannorozco]

Yeah, it seems the way to go is harfbuzz.js as you mention.

Inside our fonts we have many variable parts that we use to make the glyphs, and it will be helpful to proof them all.

Thanks!

[eomine]

Implementing a Harfbuzz renderer sounds like a relatively complex/big project.
Is this more like a "nice to have" feature?

[graphicore]

It's not incredibly big. We already load harfbuzz.js and it has the facilities to render glyphs, so we would draw to svg or canvas. Given that a lot of changes need to be made to get to the point of rendering actual glyphs, it's not a small project either. Definitely in the TODO list.

A possible workaround could be to add add-hoc PUA code points to the unencoded glyphs and replace the font, but we would inherit some problems the PUA has, e.g. copy and paste of text or saved documents could break.