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
Problem on advance heights of some vertical glyphs. #2
Comments
Fmm... it seems that topSideBearing of some glyphs generated by fontforge is accidentally overspaced. Some notable metrics information about (e.g.) aj674.pw.vert is:
Whilst my generatior script has nothing on this glyph, this may be a fontforge bug. You say, @cc4966, that pixiv-novel-font must have |
May this help...? http://www.akenotsuki.com/eyeben/fonts/kanren.html |
This problem may be caused by |
The following procedure can be help for this problem.
|
Uh, I see. I didn't notice the mapping inconsistency. Though topSideBearing of
Yes TTX is a great tool for font inspection but a tough way to modify and pack fonts by scripting. Merging two fonts is one of the hardest operation on XML, and out of proportion (in contrast to that FontForge has one simple function MergeFonts()). |
Fixed in c38d98f |
The
vmtx
table of this font has unexpected values for some glyphs in advance heights or top side bearings: for example,(
,[
,{
and⦅
have too big top side bearing or less advance height.I think that they should have
AdnvanceHeight = 2048
.In that case, the corresponding brackets, namely,
)
,]
,}
and⦆
, also should haveAdnvanceHeight = 2048
.The text was updated successfully, but these errors were encountered: