Hi, On 13/05/21 09:16, Hans Hagen wrote:
A next upload will scan the names (read: i commented the possible catch for issues, let's see when the font that needed that pops up again). Good news! Looking forward to seeing luaotfload catch up on this.
The renaming of bad glyphs can technically be fixed but a runtime hack but i try to avoid that .. the more heuristics, the harder to fight.
If I understand correctly the matter, I'd like to still advocate for an attempt. If there is something bad that must be discarded to avoid renaming heuristics, that is OK, but at least it would be nice to "leave the gap" in the codepoints, to avoid breaking the codepoint->glyph published correspondence. It is PUA, but "private" is not really "personal" and agreements about how some fonts put stuff here are probably expected to work across more than one individual, e.g. across organization or even at a wider level (think CSUR). I think that it is really important to assure that those work. The breakage of cut and paste seems particularly bad.
You can try to patch luaotfload. Locate the 'report' line and comment those two as below.
local length = readbyte(f) if length > 0 then glyphs[mapping].name = readstring(f,length) else -- report("quit post name fetching at %a of %a: %s",i,maxnames,"overflow") -- break end
I'll try that... With the names, there is the problem that as of today lualatex does not provide a LaTeX command to access the glyphs by name out of the box (as I understand it is the case in ConTeXt) so you need to write some Lua code. I'll make some experiment and if that works, I'll make a small package for that.
Did you try to use the regular variant:
\starttext \definefontfeature[materialicons][default][rlig=yes] \definedfont[file:materialiconsregular.ttf*materialicons] baby_changing_station % selects symbol as ligature \stoptext
(in latex equivalent) .. keep in mind that 'web' fonts are often more minimalistic, so i never use them (when there's a real one).
The problem here is that the "regular variant" is the official one (I understand from google), while the "webfont" is a community project that incorporates the /official/ material design icons with many contributions drawn to be fully consistent with the official icons. And my problem is that I need to make use of some of these contributions. So I really have no choice. In any case, I have opened a bug at the webfont developer to see if they can get more ConTeXt friendly by at least fixing the font->cheatsheet correspondence and the duplicate names. See https://github.com/Templarian/MaterialDesign-Webfont/issues/78 Thanks, Sergio