Skip to content
This repository has been archived by the owner on May 29, 2020. It is now read-only.

Always pass glyph name to createChar() #335

Merged
merged 1 commit into from
May 20, 2016
Merged

Conversation

jfkthame
Copy link
Contributor

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.

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.
@sapegin
Copy link
Owner

sapegin commented May 20, 2016

What about node engine?

@jfkthame
Copy link
Contributor Author

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 sapegin merged commit d45b24c into sapegin:master May 20, 2016
@timdream
Copy link

@sapegin Could you publish a new version please?

@sapegin
Copy link
Owner

sapegin commented May 23, 2016

@timdream Done.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants