Closed jfkthame closed 8 years ago
What about node
engine?
AFAICS, the node
engine doesn't support creating unencoded glyphs, or at least it's not obvious how to do so (a brief attempt resulted in failure with "Fatal error: The glyph "u00a9_layer0" codepoint seems to be used already elsewhere"). This comes from svgicons2svgfont.
It's presumably possible to add support for this to the node
engine's toolchain, but I don't have the time or expertise to dig in there and figure it out, sorry.
@sapegin Could you publish a new version please?
@timdream Done.
In order to create unencoded glyphs (by specifying their codepoint as -1), it's necessary to pass a name to createChar. This is useful for glyphs that should not appear in the cmap, but will be accessed by OpenType features created later, separately from the grunt-webfont task.