[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Pkg-fonts-devel] Bug#785809: marked as done (fonts-dejavu-core: broken ligatures in 2.35)

Your message dated Thu, 21 May 2015 10:43:10 +0200
with message-id <20150521084310.GA30697@angband.pl>
and subject line Re: [Pkg-fonts-devel] Bug#785809: Bug#785809: fonts-dejavu-core: broken ligatures in 2.35
has caused the Debian Bug report #785809,
regarding fonts-dejavu-core: broken ligatures in 2.35
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

785809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785809
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-dejavu-core
Version: 2.35-1
Severity: normal

In the latest upload, letter combinations that would be ligatures (fi, ff,
ffi, ...) get replaced by some random characters instead.  For example, in
Dejavu Sans, fi becomes a reversed omega with a breve, while in Dejavu Sans
Bold, fi becomes o with a horizontal slash.

Downgrading to 2.34 fixes this issue, thus eliminating the possibility some
other recent upgrade was the culprit.

--- End Message ---
--- Begin Message ---
On Thu, May 21, 2015 at 09:00:26AM +0200, Fabian Greffrath wrote:
> Am Mittwoch, den 20.05.2015, 16:26 +0200 schrieb Adam Borowski: 
> > Iceweasel.
> Does the issue persists if you restart Iceweasel? If not, then I don't
> think there is much we can do about it from a font packager's position.

Hrm, indeed it does not.  Which is weird, as fonts get reloaded every page
load, so after upgrading/downgrading dejavu the change shows up.

> > In both libreoffice-writer and pango-view ligatures do render correctly.
> So, this does not seem to be an issue with the font itself, right?

Only this version of this font shows the issue.

> Please feel free to either close this bug or reassign it to iceweasel --
> or pango, cairo, harfbuzz, freetype, fontconfig or whatever in the font
> rendering stack may be responsible for this glitch. :/

Closing then, as I have no means of finding another culprit.

// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable and Non-Discriminatory prices.

--- End Message ---

Reply to: