Control: close -1 2.5.2-2
On Sat, Nov 01, 2014 at 10:48:09PM -0400, Michael Gilbert wrote:
On Tue, Sep 23, 2014 at 12:45 PM, Steve Langasek wrote:
So why not changing only the default UI font in GNOME until Cantarell gets
fixed, instead of disabling a nice improvement like that?
Droid or
On Tue, Sep 23, 2014 at 12:45 PM, Steve Langasek wrote:
So why not changing only the default UI font in GNOME until Cantarell gets
fixed, instead of disabling a nice improvement like that?
Droid or DejaVu could be a valid substitute in the meanwhile.
I don't control what fonts the GNOME
On Wed, Sep 24, 2014 at 2:49 PM, Theppitak Karoonboonyanan
t...@debian.org wrote:
So, the issue seems not to be on the font itself, but rather on the
rasterizer and people's preferences.
I still agree with Jason Pleau that Adobe rasterizer should be preferred.
The reason I didn't ship OTF in
On Tue, Sep 23, 2014 at 1:47 PM, Steve Langasek vor...@debian.org wrote:
So if this is only a problem with the GNOME3 default font, please get that
font fixed in Debian, after which I am willing to reinstate the Adobe
engine. But I'm not willing to enable it while it represents a regression
On Tue, Sep 23, 2014 at 09:25:33AM +0700, Theppitak Karoonboonyanan wrote:
Package: libfreetype6
Version: 2.5.2-2
Followup-For: Bug #730742
Control: reopen -1
Dear Maintainer,
I also prefer Adobe rasterizer, to the point that my font packages,
namely fonts-tlwg-*, have switched from TTF
Il 23/set/2014 08:51 Steve Langasek vor...@debian.org ha scritto:
So if this is only a problem with the GNOME3 default font, please get that
font fixed in Debian, after which I am willing to reinstate the Adobe
engine. But I'm not willing to enable it while it represents a regression
vs.
On Tue, Sep 23, 2014 at 10:47:11AM +0200, BubuXP wrote:
Il 23/set/2014 08:51 Steve Langasek vor...@debian.org ha scritto:
So if this is only a problem with the GNOME3 default font, please get that
font fixed in Debian, after which I am willing to reinstate the Adobe
engine. But I'm not
Package: libfreetype6
Version: 2.5.2-2
Followup-For: Bug #730742
Control: reopen -1
Dear Maintainer,
I also prefer Adobe rasterizer, to the point that my font packages,
namely fonts-tlwg-*, have switched from TTF to OTF due to the improved
quality it provides. The result was better control on
I can see that this patch fixed the issue for some people, I (and maybe
others too?) preferred the way the fonts were rendered with the Adobe
hinter.
From what I can see we can't have both in the same package as the
engine used (freetype or adobe) is decided at compile time.
Is there
Package: libfreetype6
Followup-For: Bug #730742
Following up again: any chance of addressing this regression in the next
version of the Debian package, such as by applying the patch to disable
the Adobe hinter?
I'd like to make sure this issue gets fixed before the next stable
release.
- Josh
Package: libfreetype6
Followup-For: Bug #730742
Any status update on this issue? I still have libfreetype6 on hold on
all my systems, and it sounds like many others observe this issue as
well.
- Josh Triplett
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
This same bug has been reported in FreeType mailing list:
http://lists.nongnu.org/archive/html/freetype/2014-01/msg6.html
Here are the results:
http://lists.nongnu.org/archive/html/freetype/2014-01/msg00011.html
Adobe engine is ok, the bug is located in:
- the rendering engine expect gamma
It looks like I spoke too soon. With the new version of libfreetype6
(2.5.1-1) and the fontconfig configuration above, most font rendering
matches the behavior of 2.4.9-1.1, but some things still render
differently. For instance, see the attached screenshots of
gnome-terminal. The terminal
On Sat, Dec 21, 2013 at 11:23:57AM -0800, Josh Triplett wrote:
On Mon, Dec 16, 2013 at 11:53:01AM +0100, BubuXP wrote:
I found the cause (maybe).
Probably the fuzzy fonts are all OpenType fonts. Starting from
freetype 2.5.0.1, the Adobe CFF engine is the default rasterizer for
those class
On Mon, Dec 16, 2013 at 11:53:01AM +0100, BubuXP wrote:
I found the cause (maybe).
Probably the fuzzy fonts are all OpenType fonts. Starting from
freetype 2.5.0.1, the Adobe CFF engine is the default rasterizer for
those class of fonts.
I found the cause (maybe).
Probably the fuzzy fonts are all OpenType fonts. Starting from
freetype 2.5.0.1, the Adobe CFF engine is the default rasterizer for
those class of fonts.
https://blogs.adobe.com/typblography/2013/05/adobe-contributes-cff-rasterizer-to-freetype.html
From:
On Mon, Dec 16, 2013 at 11:53:01AM +0100, BubuXP wrote:
I found the cause (maybe).
Probably the fuzzy fonts are all OpenType fonts. Starting from
freetype 2.5.0.1, the Adobe CFF engine is the default rasterizer for
those class of fonts.
On Thu, 12 Dec 2013 13:10:01 -0800, Steve Langasek wrote:
This is not garbage display.
I was sure this was the problem but seems I was wrong, sorry.
Probably I will be wrong this time too, but if possible I'd like to
know by those affected by the bug:
- the desktop environment they are using and
Version 2.5.2 has been released meantime, where probably the problem
has been fixed:
CHANGES BETWEEN 2.5.1 and 2.5.2
I. IMPORTANT BUG FIXES
- Improving the display of some broken TrueType fonts introduced a
bug that made FreeType crash on some popular (but not fully
On Thu, Dec 12, 2013 at 09:55:22PM +0100, BubuXP wrote:
Version 2.5.2 has been released meantime, where probably the problem
has been fixed:
Which of these changes are you claiming fixes the issue?
CHANGES BETWEEN 2.5.1 and 2.5.2
I. IMPORTANT BUG FIXES
- Improving the display of some
FYI, I tried dpkg-reconfigure fontconfig-config and switching to
Autohinter, which made the letters look a bit thinner, but the look
improved overall (YMMV).
--
Jindřich Makovička
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Am Donnerstag, den 05.12.2013, 08:37 -0800 schrieb Steve Langasek:
If you want to disable the *use* of subpixel rendering, I believe there's a
fontconfig option for this. But we should not disable the *capability* for
subpixel rendering in freetype.
I wonder why the capability is not enabled
On Thu, Dec 05, 2013 at 01:13:08PM -0800, Josh Triplett wrote:
On Thu, Dec 05, 2013 at 08:37:59AM -0800, Steve Langasek wrote:
On Thu, Dec 05, 2013 at 09:23:56AM +0100, Fabian Greffrath wrote:
Confirmed with the upstream version, but only when
FT_CONFIG_OPTION_SUBPIXEL_RENDERING is
Dear Steve,
Confirmed with the upstream version, but only when
FT_CONFIG_OPTION_SUBPIXEL_RENDERING is enabled, which is the case in
the Debian build but not in the default upstream build.
please disable enable-subpixel-rendering.patch in the next upload of the
freetype package.
- Fabian
On Thu, Dec 05, 2013 at 09:23:56AM +0100, Fabian Greffrath wrote:
Dear Steve,
Confirmed with the upstream version, but only when
FT_CONFIG_OPTION_SUBPIXEL_RENDERING is enabled, which is the case in
the Debian build but not in the default upstream build.
please disable
On Thu, Dec 05, 2013 at 08:37:59AM -0800, Steve Langasek wrote:
On Thu, Dec 05, 2013 at 09:23:56AM +0100, Fabian Greffrath wrote:
Confirmed with the upstream version, but only when
FT_CONFIG_OPTION_SUBPIXEL_RENDERING is enabled, which is the case in
the Debian build but not in the
Confirmed with the upstream version, but only when
FT_CONFIG_OPTION_SUBPIXEL_RENDERING is enabled, which is the case in
the Debian build but not in the default upstream build.
-- Juliusz
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Package: libfreetype6
Version: 2.5.1-1
Followup-For: Bug #730742
I can confirm this too, though some fonts still render fine.
For example, Cantarell (default GNOME3 font) renders fuzzy, but
BitStream Vera Sans renders fine.
Regards,
Colomban
--
To UNSUBSCRIBE, email to
28 matches
Mail list logo
