freetype
[Top][All Lists]
Advanced

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

Re: [ft] Another problem with X11 PCF fonts and 2.7.1, now with bisect


From: Markus Unterwaditzer
Subject: Re: [ft] Another problem with X11 PCF fonts and 2.7.1, now with bisect
Date: Sun, 8 Jan 2017 21:23:09 +0100
User-agent: NeoMutt/20161126 (1.7.1)

On Sun, Jan 08, 2017 at 09:18:01PM +0100, Werner LEMBERG wrote:
> 
> > When upgrading from Freetype 2.7 to 2.7.1 my configuration of the
> > Terminus bitmap font broke.  Turns out it is now available under a
> > new name: "xos4 Terminus".
> 
> This is correct.
> 
> >     $ fc-match "xos4 Terminus"
> >     ter-112n.pcf.gz: "xos4 Terminus" "Regular"
> >     $ fc-match "Terminus"
> >     DejaVuSans.ttf: "DejaVu Sans" "Book"
> > 
> > This happens to me on two ArchLinux machines using the terminus-font
> > package, one of them with AMD Catalyst drivers and one of them with
> > Intel.  Downgrading to freetype 2.7 or using that new identifier
> > fixes my problem.
> 
> Well, it's not a problem but an expected change, which is mentioned in
> FreeType's `CHANGES' file:
> 
>   - PCF family names are made more `colourful'; they now include the
>     foundry and information whether they contain wide characters.  For
>     example, you no longer get `Fixed' but rather `Sony Fixed' or
>     `Misc Fixed Wide'.

Is there a reason for doing this in a bugfix release? As far as I can tell this
is a backwards-incompatible change, and every application that has had Terminus
configured will fall back to something else.

> 
> 
>    Werner



reply via email to

[Prev in Thread] Current Thread [Next in Thread]