Date: Tue, 06 Jun 2017 02:50:10 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 219608] print/freetype2 produces incorrect line spacing for some fonts Message-ID: <bug-219608-6497-CfuILXxOVg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219608-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-219608-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219608 --- Comment #19 from lightside <lightside@gmx.com> --- (In reply to comment #13) > Thanks for working on this. If you have no objections I'll wait a few day= s to > confirm that thee are no other unexpected issues a then ask for maintainer > approval and commit. No problem, but I don't know about possible regressions between 2.7.1 and 2= .8 versions, which possibly caused some differences in your case. I just propo= sed what worked in my case (and settings). (In reply to comment #14) > Thanks both of you for working on this issue. I will give it a go soon as= well. Thanks for your attention. (In reply to comment #14) > can you report this problem upstream? We are probably not the only onces > having this issue and you clearly know how to explain the issue the best. I shared some links in comment #2, which shows that this issue is known to upstream developers: https://savannah.nongnu.org/bugs/?50470 https://savannah.nongnu.org/bugs/?50470#comment17 -8<-- We are back to square one. The rationale (http://lists.nongnu.org/archive/html/freetype-devel/2011-07/msg00022.html)= for the original fix in 2011 was to fix ascend, descend, and line spacing values and it worked for any font. -->8- https://savannah.nongnu.org/bugs/?50470#comment26 -8<-- Here you can find an extensive explanation of the problem. http://lists.nongnu.org/archive/html/freetype-devel/2017-04/msg00042.html -->8- But that PR was closed. I don't object if someone shares a link to this PR and/or patch in attachme= nt #183237. But I guess, that this method is already known (converted for 2.8 version), but not used for some reason. Otherwise, it was possible to create some define to enable this in the same place (src/truetype/ttdriver.c). Possible, that AF_CONFIG_OPTION_TT_SIZE_METRICS method wasn't complete for = 2.8 version (related to line spacing). In turn, this possibly caused other actions: Gnome's vte developers may consider to fix this (probably gnome-terminal related; not sure about mate-terminal): https://bugzilla.gnome.org/show_bug.cgi?id=3D781479#c15 -8<-- Egmont Koblinger 2017-04-19 18:01:08 UTC In the mean time, we could consider adding an API and a hidden g-t setting = to add/subtract a constant pixel value from the cell size computed by pango. That'd address bug 738781 as well. -->8-=20 Chromium related: https://bugzilla.redhat.com/show_bug.cgi?id=3D1437999#c66 -8<-- Marek Kas=C3=ADk 2017-05-22 05:48:44 EDT <..> Regarding the Chromium case, it seems that people around Chromium are discussing about bundling of their own freetype which could solve the issue even in F24, F25 and F26 depending on whether and when they will do that (https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromium= -packagers/xhmgu-1Vcok). -->8-=20 So, what already proposed in this PR could be just a intermediate solution. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219608-6497-CfuILXxOVg>