Refinements to Build Accented Glyph - Request #460

Open
vernnobile opened this Issue Mar 20, 2013 · 5 comments

Projects

None yet

2 participants

@vernnobile
Collaborator

At present 'Build Accented Glyph' uses spacing characters as replacements for 'true' diacritic marks when a diacritic mark does not exist in a fonts character set. This tends to encourage the use of spacing marks as a default combining glyphs in place of true combining glyphs for diacritics.
Example - 'aacute' (u+00e0) is built as a default with the lowercase 'a' (u+0061) combined with the 'acute' (u+00b4), however it should be built with the lowercase 'a' combined with the 'acutecomb' (u+0301)

Proposal - that when the Build Accented Glyph tool is used and a combining ('*comb') glyph does not exist, that fontforge should prompt the user to automatically add that unicode character of the missing combining glyph to the font. The necessary combining glyph slot should then be automatically added to the font.

Good idea? Better approach? Please comment.

@ultrasquid

I think this is a good idea.

So, if I understand what you're saying correctly:

Element>Build>Accented Glyph is invoked for 'aacute' (u+00e0)

combining accent 'acutecomb' (u+0301) does not exist in the font, but spacing accent 'acute' (u+00b4) does

therefore, we Copy Reference of u+00b4 and Paste to u+0301

set width of u+0301 to 0 and center in width

Build Accented Glyph from references copied from 'a' (u+0061) and 'acutecomb' (u+0301), pasted into 'aacute' (u+00e0)

@vernnobile
Collaborator

Yes. Although not sure about the idea of the use of 'Copy Reference' from, e.g, 'acute' to 'acutecomb'. Better would be to either leave the new glyph blank or use a 'Build Duplicate Glyph'. One reason for this is that referencing referenced glyphs can cause issues.

@ultrasquid

But 'Build Duplicate Glyph' has its own issues. It works by assigning
multiple unicode values to a single glyph. While this is technically
allowed, it makes it difficult to disassociate the characters later on
during editing.

On Tue, Apr 2, 2013 at 11:17 PM, vernon adams notifications@github.comwrote:

Yes. Although not sure about the idea of the use of 'Copy Reference' from,
e.g, 'acute' to 'acutecomb'. Better would be to either leave the new glyph
blank or use a 'Build Duplicate Glyph'. One reason for this is that
referencing referenced glyphs can cause issues.


Reply to this email directly or view it on GitHubhttps://github.com/fontforge/fontforge/issues/460#issuecomment-15820252
.

Jason Pagura
zimbach at gmail dot com

@vernnobile
Collaborator

the best solution then is either; a blank glyph or, a copied reference which is then unlinked.

@ultrasquid

Since anchors are often used as a means for composing accented glyphs, can a Build subfeature be made to automate the placement of anchors? If so, this is probably worth its own issue, but I'm just floating the idea here.

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