New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resset / change unicode char in private area /PUA to default (glyphs character) in font info #3406

Open
javapep opened this Issue Jan 11, 2019 · 3 comments

Comments

Projects
None yet
2 participants
@javapep
Copy link

javapep commented Jan 11, 2019

Resset / change unicode char in private area /PUA to default (glyphs character) in font info

Hi, folks, I have the problem with Unicode char in pua for alternate glyphs, I don't know how to fix it. How to reset to default Unicode char in glyph info. I'm placing the glyph in private area for OpenType features, coz if I generate the font this Unicode chart change to forming my own glyph and can't to back default again. Than if i open new page this Unicode chart still all ready not back to default. i attached the problem.

1.This my own glyphs...and all Unicode char forming like my own glyphs.
2.This unicode char that change like my own glyphs.
3.This default unicode char.... The problem is all unicode char can't to setting to default again

Thanks you in advance

deepinscreenshot_select-area_20190108104647
deepinscreenshot_select-area_20190108213530
deepinscreenshot_select-area_20190108213614

@skef

This comment has been minimized.

Copy link

skef commented Jan 11, 2019

Having read through your description, I am not quite sure what problem you face, and whether it is more of a bug in the software or a question about normal practice. So I'll make a few suggestions from both perspectives.

The most common practice for alternate glyphs, at least in FontForge, is to give them unique names but assign all of them "-1" as a unicode value. This is equivalent to each not having any associated unicode slot. Only the standard or "default" glyphs should have their associated unicode values in the font. Alternates are then substituted by name, not unicode value, in GSUB lookup tables, which can be accessed in FontForge from the Lookups section of the Element->Font Info dialog, or the "Substitutions, Mult Subs, and Ligatures` section of the dialog in your screenshots. You can read more about OpenType and FontForge substitutions here: http://fontforge.github.io/en-US/documentation/interface/lookups/

If this does not solve your problem, it would be helpful if you could update this issue with a description of a specific sequence of steps that reproduce your problem in FontForge. Whether your issue is related to a software bug or a misunderstanding of how FontForge is intended to work, that more detailed description would likely clarify your problem.

@javapep

This comment has been minimized.

Copy link

javapep commented Jan 11, 2019

Thanks @skef for ur suggestion. I'm too, I always wrote all alternate and ligature like your feedback. The question is when we chage unicode value with -1... Is still already in Private use slot or not?.

@skef

This comment has been minimized.

Copy link

skef commented Jan 11, 2019

The question is when we chage unicode value with -1... Is still already in Private use slot or not?.

No, glyphs with a -1 unicode value will be treated as unmapped on the Unicode level.

If you need glyphs included in the private use area I believe you should be able to set their unicode values explicitly by typing in the "Unicode Value" box and hitting "OK" at the bottom of the dialog. But then you need to be careful not to "remap" those values based on glyph name, either in that dialog or font-wide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment