-
-
Notifications
You must be signed in to change notification settings - Fork 614
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
[Linux] letter-height of 'u' wrong in emacs #56
Comments
Can you give me your platform, emacs version, and any hinting settings that you are using? Thanks |
Linux, emacs 24.5.1, otf (ttf renders with far to large letter-spacing for me)
|
looking into it. thank you |
I have to thank |
I'm also seeing this in chrome on linux, not sure how to get info on settings |
The font configuration is still a mess in linux....
The settings of fontconfig which I posted above are all aplied expect for hintstyle, very strange, this bug seems to be there for ages ... So hintfull is used instead of hintslight. If I change the xrdb settings to hintslight the problem disappears. So it's rendered wrong only if hintfull is used. |
Are there any other (new) hinting issues when you switch from full to slight? |
Slight renders fine. |
I'm seeing this in konsole (qt5) with slight:
|
Try that in your .emacs |
The problem I reported in #64 is possibly a variation on this problem. |
Thx for (set-frame-font "Hack:size=13:hintstyle=hintmedium") chrissimpkins: This setting are a good way to test rendering on linux |
I believe that this syntax is not specific to emac. This is the font naming scheme of Fontconfig. Remark: I just noticed that hack-13 and hack:size=13 are not giving the same font size. The proper way seems to be hack-13 |
Thanks for that link @schauveau. Both My setup is a bit strange. Emacs 24.5.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.28) , compiled from source using GTK2 on Arch Linux. The X server is actually MobaX, part of MobaXterm on Windows 10. |
I have no clue why, but using So I'm using this with good results (and the OTF fonts): (set-face-attribute 'default nil :font "Hack-12:hintstyle=hintfull:autohint=true:rgba=rgb") I fiddled with most of the available fonts-conf options, but none of them fixed the spacing of the TTF fonts. I would encourage people to just fiddle with all the options as well to see where it gets them. I expected P.S. due to no reason I can think of, my issue with the height of |
... |
The reason is the font size. @chrissimpkins the ttf fonts in your developement branch don't have the letter spacing issue for me |
@duud : you are referring to the v2.011 development branch release? This was a fix for a glyph that included an empty character position with an em box (middle dot glyph) that was set to a very large width. I wonder if this led to problems with the horizontal metrics tables. |
Yes, I used the v2.011 dev-branch and it has no letter spacing
|
@lemzwerg: Werner, does ttfautohint modify the gasp table in the ttf files? These releases (both the current release 2.010 and 2.011) have a gasp table as follows on build (and prior to the autohint):
I'm wondering if this could explain why we are seeing these type size dependent issues that seem to be influenced by the level of hinting that is applied to the glyphs. It's not clear why the There is a similar issue in #32 where bold glyphs are not aligned on the baseline with the regular set glyphs in a type size dependent fashion. In that case, it appears to be a cross-platform, cross-editor issue. |
ttfautohint replaces the Note, however, that the reported issue is related to the OpenType version of Hack, which uses PS outlines. This has nothing to do with ttfautohint. I guess that the PS hints for the 'u' glyph are not fully correct, leading to the visual artifact. |
@duud what hinting settings are you using in the ttf files and what are you seeing that leads to your preference for the otf builds? |
Tentative fix at this point is to switch to the new ttf build in emacs (v2.011). Let's keep this open to discuss rendering issues in these new files. Perhaps there are some settings optimizations that will lead improvement (see @duud message above re: concern about how hinting renders vs. otf files) Download Links |
I will build another set of otf files off of the v2.011 source once I check the hints and will push that for you to try as well if it looks better on your system. |
I just tried the v2.011 TTF and both the 'u' problem and the emacs spacing bugs seem to be gone. fc-query Hack-Regular-2_011.ttf | grep spacing
|
@chrissimpkins This is all crazy - but with the ttf version fontsize 10 renders to small in xterm size 11 is to large, otf size 10 is in between and is perfect, also the ttf version has almost no visual difference between hintslight and hintfull so that ttf + hintfull almost= ttf + hintslight almost= otf + hintslight, whereas otf+hintfull renderds clearly bfrighter and somewhat bolder. |
@schauveau metrics tables were affected by this bug. hopefully addressed now. will release this bugfix this week. |
Are you still using otf files here? Would you be willing to give the new v2.014 test build of the ttf files a try and let me know how the changes affect the rendering issues that were reported (as side notes) in this thread? Available in #111 |
Experiencing a similar issue under linux (debian testing) with fonts-hack-otf 2.019-1, but with too small (height) 'u' for certain text sizes. fonts-hack-ttf fixes it, but has different line-height (smaller). My workaround is fonts-hack-otf with text size 10.1 instead of 10. |
Hey @MarkusKull you are not the first to notice the line height and prefer the OTF. I ran into this a while back and never got around to reporting it, but I just opened an issue for it at #188. Some feedback there about the line-height issue would be appreciated. |
Yes, this original report remains on the to do list. I think that this is going to be a hinting issue that we will need to look into. We are currently using the autohinter in FontLab Studio and I am not certain why it is leading to this problem. If anyone is motivated to explore this themselves, you might try the Adobe autohinter that is part of their Adobe font development kit. If you can come up with a set of specs that correct the problem, I am more than happy to include them in the workflow for our builds pronto. For now, we are working to make a solid set of ttf builds and will then turn our attention to the otf builds. There are lots of reasons for this, but the primary one is that I have a great deal more flexibility and control over the ttf hints at the moment and this has been a critical issue for screen use at small text sizes. |
otf builds were eliminated as of v3.000. Please update to ttf builds and let us know if you continue to experience problems. Thanks for the report! |
The text was updated successfully, but these errors were encountered: