Debian Bug report logs -
#636776
libfreetype6: Line height squeezed in GNU Emacs
Reported by: Adam Sjøgren <asjo@koldfront.dk>
Date: Fri, 5 Aug 2011 20:33:01 UTC
Severity: normal
Merged with 636844
Found in version freetype/2.4.6-1
Fixed in version 2.8.1-0.1
Done: Andrew Shadura <andrew.shadura@collabora.co.uk>
Reply or subscribe to this bug.
Toggle useless messages
Report forwarded
to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#636776; Package libfreetype6.
(Fri, 05 Aug 2011 20:33:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Adam Sjøgren <asjo@koldfront.dk>:
New Bug report received and forwarded. Copy sent to Steve Langasek <vorlon@debian.org>.
(Fri, 05 Aug 2011 20:33:04 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: libfreetype6
Version: 2.4.6-1
Severity: normal
After upgrading to libfreetype6 2.4.6-1 the line height in GNU Emacs is
changed, so the lines appear squeezed together.
Here is a screenshot with libfreetype6 2.4.6-1:
* http://koldfront.dk/misc/gnu-emacs/libfreetype6_246.png
Reverting to libfreetype6 2.4.4-2 from testing returns GNU Emacs to the
usual line height:
* http://koldfront.dk/misc/gnu-emacs/libfreetype6_244.png
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libfreetype6 depends on:
ii libc6 2.13-14 Embedded GNU C Library: Shared lib
ii multiarch-support 2.13-14 Transitional package to ensure mul
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
libfreetype6 recommends no packages.
libfreetype6 suggests no packages.
-- no debconf information
Information forwarded
to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#636776; Package libfreetype6.
(Mon, 08 Aug 2011 09:30:53 GMT) (full text, mbox, link).
Acknowledgement sent
to Yves-Alexis Perez <corsac@debian.org>:
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>.
(Mon, 08 Aug 2011 09:31:03 GMT) (full text, mbox, link).
Message #10 received at 636776@bugs.debian.org (full text, mbox, reply):
merge 636844 636776
thanks
On sam., 2011-08-06 at 12:10 +0200, Yves-Alexis Perez wrote:
> Package: libfreetype6
> Version: 2.4.4-2
> Severity: normal
>
> Hey,
>
> starting with 2.4.6 upgrade, I noticed that my terminal fonts
> (Monospace, alias to DejaVu Sans Mono, 4,5) were too wide (in fact they
> are too short vertically). Attached are screenshots before and after upgrade.
>
> I'm not exactly sure what it's related too, but I prefer the previous
> rendering, which is more readable here. It seems that it only affects
> Monospace fonts, though I'm not 100% sure.
>
After doing a git bisect, here are the results:
b0962ac34e66052ccfee7996e5468f30d4bd5a72 is the first bad commit
commit b0962ac34e66052ccfee7996e5468f30d4bd5a72
Author: Steven Chu <steven.f.chu@gmail.com>
Date: Sat Jul 16 09:12:42 2011 +0200
[truetype] Fix metrics on size request for scalable fonts.
* src/truetype/ttdriver.c (tt_size_request): Fix copying metrics
from TT_Size to FT_Size if scalable font.
so it looks that this was done on purpose...
Full bisect log is:
# bad: [29a7965fd14f0a142965067e04f6b8e4ba354d3e] * Version 2.4.6 released. =========================
# good: [9ec31cea16a492bed96a96a7c30c1a466adb9792] * Version 2.4.4 released. =========================
git bisect start 'VER-2-4-6' 'VER-2-4-4'
# good: [948a8fb674c99ff41ae108b986721a4fd15c6a0e] Fix formatting of autofit debug dumps.
git bisect good 948a8fb674c99ff41ae108b986721a4fd15c6a0e
# good: [f3e2a97d5b8f437efefb0de65a4baceb526feac4] Fix URLs.
git bisect good f3e2a97d5b8f437efefb0de65a4baceb526feac4
# good: [4bf221964ca0f1db75c3fb7b08984fd50314a0a9] Improve documentation of FT_Get_Glyph_Name.
git bisect good 4bf221964ca0f1db75c3fb7b08984fd50314a0a9
# good: [f095744d2db48eddc79bc744c3286e26ebd2c694] [sfnt] Try harder to find non-zero values for ascender and descender.
git bisect good f095744d2db48eddc79bc744c3286e26ebd2c694
# good: [143799d4a95e38eab1e49c761d3c6f116fd80349] [psaux] Fix potential sign extension problems.
git bisect good 143799d4a95e38eab1e49c761d3c6f116fd80349
# bad: [3abf617b5e83a5cbe588169844fe931e7b91e50f] Add FT_CONFIG_OPTION_DISABLE_STREAM_SUPPORT.
git bisect bad 3abf617b5e83a5cbe588169844fe931e7b91e50f
# bad: [77f04cebe8035ac48f52dd1044505a1ba6185ab0] * src/base/ftpatent.c (FT_Face_SetUnpatentedHinting): Fix typo.
git bisect bad 77f04cebe8035ac48f52dd1044505a1ba6185ab0
# bad: [b0962ac34e66052ccfee7996e5468f30d4bd5a72] [truetype] Fix metrics on size request for scalable fonts.
git bisect bad b0962ac34e66052ccfee7996e5468f30d4bd5a72
Even if it was done on purpose I'm not sure what purpose it was since
the results looks less readable here.
Regards,
--
Yves-Alexis
Merged 636776 636844.
Request was from Yves-Alexis Perez <corsac@debian.org>
to control@bugs.debian.org.
(Mon, 08 Aug 2011 09:31:13 GMT) (full text, mbox, link).
Bug No longer marked as found in versions freetype/2.4.4-2.
Request was from Yves-Alexis Perez <corsac@debian.org>
to control@bugs.debian.org.
(Mon, 08 Aug 2011 10:24:04 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#636776; Package libfreetype6.
(Thu, 23 Feb 2012 12:15:09 GMT) (full text, mbox, link).
Acknowledgement sent
to rjs@cs.hut.fi (Riku Saikkonen):
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>.
(Thu, 23 Feb 2012 12:16:26 GMT) (full text, mbox, link).
Message #19 received at 636776@bugs.debian.org (full text, mbox, reply):
Hi,
Some thoughts on this bug from a typography hobbyist: from a typographic
point of view, good line spacing is not a fixed quantity but depends on
things like line length and the properties of the font, sometimes even
the text itself.
So I think ideally the line spacing should be user-configurable, perhaps
as an additional fontconfig property. I actually looked for such a
property completely unrelated to this bug: I would have liked to use
slightly larger line spacing than is the default in Emacs and xterm in
Debian squeeze. I just now found out that Emacs actually has support for
customizing line spacing (see below); but xterm nor other terminal
programs do not (as far as I know).
In typographic circles, the unit of line spacing is points (i.e., the
same as the size of the font); for instance, a 12-point font with
14-point line spacing (a less common way to state the same is to say
that there are 2 points of leading between lines). (Pixels are also okay
for a display, but not "single-spaced" or "one and a half" or
"double-spaced" as in some word processing programs - these three values
are much too coarse.)
More to the point, could this bug be related to the minspace-property
(the only thing about line spacing that appears to be configurable in
fontconfig):
http://www.xfree86.org/current/fontconfig.3.html
and
http://www.freedesktop.org/software/fontconfig/fontconfig-user.html
say that minspace is a boolean that "Eliminate[s] leading from line
spacing". The default value does not seem to be mentioned - but I assume
that a value of true _should_ create the "crammed lines" effect
mentioned in the original bug report and false should give some
additional space.
I don't have an unstable system to test this on, but perhaps you could
try altering the minspace property and seeing if it fixes things: add
":minspace=true" or ":minspace=false" to the end of the font face name.
For instance:
emacs -fn 'DejaVu Sans Mono-12:minspace=false' &
emacs -fn 'DejaVu Sans Mono-12:minspace=true' &
(actually, on my Debian squeeze system, both produce the same result,
which I guess is a bug... other properties do work, such as emacs -fn
'DejaVu Sans Mono-12:dpi=200' &)
So maybe this bug could be transformed into a feature request for an
additional fontconfig property that allows user-defined line spacing
(with a reasonable default value)? Or should it be the responsibility of
every application that uses fontconfig to display multiline text to have
an ability to control its line spacing (I don't think this viewpoint is
unreasonable, but it does make font-using programs more complex a bit
unnecessarily)?
Actually, while writing this bug report I found out that Emacs does have
internal support for changing line spacing:
(setq-default line-spacing 2)
adds two pixels of line spacing to the frame. (Or of course M-x
customize-variable RET line-spacing RET.) At least on Debian squeeze,
Emacs's default is "nil" which means that it does not add additional
space. Since Emacs does not support negative values for line-spacing,
the original bug actually makes line spacing more configurable (i.e., it
can be tightened to smaller values than the previous default).
So, as sort of a summary, changing the line-spacing variable should work
as a workaround for Emacs. But for actually fixing the bug, we should
find out
a) if the minspace property works and whether its default was and/or
should be changed,
b) what should applications expect the default behavior to be (probably
a reasonable default spacing instead of minimal spacing as seems to
be introduced by this bug), and
c) should user-configurable line spacing be the responsibility of every
application or a fontconfig property.
--
-=- Rjs -=- rjs@cs.hut.fi
Information forwarded
to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#636776; Package libfreetype6.
(Fri, 24 Feb 2012 20:45:03 GMT) (full text, mbox, link).
Acknowledgement sent
to asjo@koldfront.dk (Adam Sjøgren):
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>.
(Fri, 24 Feb 2012 20:45:03 GMT) (full text, mbox, link).
Message #24 received at 636776@bugs.debian.org (full text, mbox, reply):
On Thu, 23 Feb 2012 13:19:49 +0200, Riku wrote:
> More to the point, could this bug be related to the minspace-property
> (the only thing about line spacing that appears to be configurable in
> fontconfig):
> http://www.xfree86.org/current/fontconfig.3.html
> and
> http://www.freedesktop.org/software/fontconfig/fontconfig-user.html
> say that minspace is a boolean that "Eliminate[s] leading from line
> spacing". The default value does not seem to be mentioned - but I assume
> that a value of true _should_ create the "crammed lines" effect
> mentioned in the original bug report and false should give some
> additional space.
I just tried upgrading the the newest libfreetype6 again, and now I
notice that GNU Emacs isn't the only program where lines get crammed
together by the upgrade: Text in other programs, such as Pidgin, also
gets changed display - line spacing is decreased a lot.
I wonder if this is due to some configuration in my system, because I
doubt that people wouldn't complain about that look in a newly installed
system.
> Actually, while writing this bug report I found out that Emacs does have
> internal support for changing line spacing:
> (setq-default line-spacing 2)
Setting this works fine for me - but that doesn't solve the problem for
all the other programs where the newer libfreetype6 decreases the
default line spacing making text hard to read.
I have looked in /etc/fonts/* but I think I need someone to take a swing
at me with a clue bat...
Best regards,
Adam
--
"My internal clock is on Tokyo time." Adam Sjøgren
asjo@koldfront.dk
Information forwarded
to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#636776; Package libfreetype6.
(Sat, 17 Mar 2012 20:51:03 GMT) (full text, mbox, link).
Acknowledgement sent
to asjo@koldfront.dk (Adam Sjøgren):
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>.
(Sat, 17 Mar 2012 20:51:03 GMT) (full text, mbox, link).
Message #29 received at 636776@bugs.debian.org (full text, mbox, reply):
I could not make any of the suggestions presented by Riku Saikkonen
work.
I tried installing testing in a virtual machine and upgraded it to
unstable, to see if my troubles were caused by some left over/special
configuration on my computer. The same squished line problem was present
in the freshly installed virtual machine, so I think it isn't just my
setup.
I wonder what Ubuntu is doing in Precise Pangolin, which ought to have
the same problem.
I have resorted to building a local package with the commit, that
Yves-Alexis Perez was nice enough to find to be the cause, reverted:
* http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0962ac34e66052ccfee7996e5468f30d4bd5a72
The graphics on my screen have non-squished lines again (most noticable
in Pidgin and GNU Emacs, but other places as well - menu bar in
Iceweasel, for instance); hooray!
My private repository of unsupported packages with the patched package
is available here, in case someone is interested:
* http://koldfront.dk/debian/
Best regards,
Adam
--
"The world is short of delimiters," says Don. Adam Sjøgren
asjo@koldfront.dk
Information forwarded
to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#636776; Package libfreetype6.
(Sun, 18 Mar 2012 04:51:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Vincent Cheng <vincentc1208@gmail.com>:
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>.
(Sun, 18 Mar 2012 04:51:04 GMT) (full text, mbox, link).
Message #34 received at 636776@bugs.debian.org (full text, mbox, reply):
On Sat, Mar 17, 2012 at 1:49 PM, Adam Sjøgren <asjo@koldfront.dk> wrote:
[...]
> My private repository of unsupported packages with the patched package
> is available here, in case someone is interested:
>
> * http://koldfront.dk/debian/
I can confirm that these patched packages fix the line height issue
for me; thanks!
Is there a reason why this patch cannot be applied to the official
Debian freetype packages? If it's simply the desire not to diverge
from upstream, then I guess I'll be keeping my freetype packages
pinned for now.
Regards,
Vincent
Information forwarded
to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#636776; Package libfreetype6.
(Mon, 19 Mar 2012 01:33:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Vincent Cheng <vincentc1208@gmail.com>:
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>.
(Mon, 19 Mar 2012 01:33:03 GMT) (full text, mbox, link).
Message #39 received at 636776@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
tag 636776 patch
thanks
Dear Maintainer,
I've attached a patch (the same one that's in Adam Sjøgren's freetype
source package) for your convenience.
Regards,
Vincent
[revert_Fix_metrics_on_size_request_for_scalable_fonts.patch (text/x-patch, attachment)]
Added tag(s) patch.
Request was from Vincent Cheng <vincentc1208@gmail.com>
to control@bugs.debian.org.
(Mon, 19 Mar 2012 01:33:05 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org:
Bug#636776; Package libfreetype6.
(Sat, 24 Mar 2012 19:09:44 GMT) (full text, mbox, link).
Acknowledgement sent
to Steve Langasek <vorlon@debian.org>:
Extra info received and forwarded to list.
(Sat, 24 Mar 2012 19:09:45 GMT) (full text, mbox, link).
Message #46 received at 636776@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
tags 636776 -patch
thanks
Hi Vincent,
On Sat, Mar 17, 2012 at 09:47:36PM -0700, Vincent Cheng wrote:
> On Sat, Mar 17, 2012 at 1:49 PM, Adam Sjøgren <asjo@koldfront.dk> wrote:
> [...]
> > My private repository of unsupported packages with the patched package
> > is available here, in case someone is interested:
> > * http://koldfront.dk/debian/
> I can confirm that these patched packages fix the line height issue
> for me; thanks!
> Is there a reason why this patch cannot be applied to the official
> Debian freetype packages? If it's simply the desire not to diverge
> from upstream, then I guess I'll be keeping my freetype packages
> pinned for now.
It's not /simply/ the desire not diverge from upstream; it's that this
divergence does not appear to be regression-free regarding upstream behavior
in other areas, and I don't want to be in the position of arbitrating which
use case should take precedence or which behavior is the correct one.
(Since ultimately, I'm a library guy, not a fonts guy.)
So if you would like this changed in Debian, please discuss it with
upstream. Their mailing list is at <freetype-devel@nongnu.org>.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
[signature.asc (application/pgp-signature, inline)]
Removed tag(s) patch.
Request was from Steve Langasek <vorlon@debian.org>
to control@bugs.debian.org.
(Sat, 24 Mar 2012 19:09:46 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org:
Bug#636776; Package libfreetype6.
(Mon, 02 Apr 2012 22:27:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Steve Langasek <vorlon@debian.org>:
Extra info received and forwarded to list.
(Mon, 02 Apr 2012 22:27:03 GMT) (full text, mbox, link).
Message #53 received at 636776@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
It's also been reported that this upstream commit causes a regression for
underlining handling in gtk in Ubuntu.
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/955030
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Steve Langasek <vorlon@debian.org>:
Bug#636776; Package libfreetype6.
(Tue, 03 Apr 2012 09:12:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Sebastien Bacher <seb128@ubuntu.com>:
Extra info received and forwarded to list. Copy sent to Steve Langasek <vorlon@debian.org>.
(Tue, 03 Apr 2012 09:12:05 GMT) (full text, mbox, link).
Message #58 received at 636776@bugs.debian.org (full text, mbox, reply):
Hi,
Just for info I sent an email on the upstream list to mention the issue:
http://lists.nongnu.org/archive/html/freetype-devel/2012-04/msg00001.html
--
Sebastien Bacher
Reply sent
to Andrew Shadura <andrew.shadura@collabora.co.uk>:
You have taken responsibility.
(Wed, 03 Jan 2018 13:54:13 GMT) (full text, mbox, link).
Notification sent
to Adam Sjøgren <asjo@koldfront.dk>:
Bug acknowledged by developer.
(Wed, 03 Jan 2018 13:54:13 GMT) (full text, mbox, link).
Message #63 received at 636776-done@bugs.debian.org (full text, mbox, reply):
Control: tag -1 fixed-upstream
Version: 2.8.1-0.1
Hi,
The upstream has acknowledged the change which is no longer needed now:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/src/truetype/ttdriver.c?id=bcc74f4dafee25ea89f1d3144646cba7e30f9908
--
Cheers,
Andrew
Reply sent
to Andrew Shadura <andrew.shadura@collabora.co.uk>:
You have taken responsibility.
(Wed, 03 Jan 2018 13:54:14 GMT) (full text, mbox, link).
Notification sent
to Yves-Alexis Perez <corsac@debian.org>:
Bug acknowledged by developer.
(Wed, 03 Jan 2018 13:54:14 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Sat Jan 13 11:48:50 2018;
Machine Name:
beach
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.