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

[Markus Unterwaditzer]

Hello Nikolay,

I have identified this commit in the OP. It appears that this is an intentional breakage. Does this really belong into a bugfix release? Or any release ever (considering the breakage that would ensue)?

Cheers,
Markus

On 8 January 2017 21:05:43 CET, Nikolay Sivov <address@hidden> wrote:

On 08.01.2017 22:56, Chris Down wrote:
 Hello,
 
 I'm also having this problem since upgrading to 2.7.1 -- "Terminus"
 magically became "xos4 Terminus" to fontconfig, even though the
 underlying files providing that font haven't changed.
 
 As a workaround I have added the following to my
 ~/.config/fontconfig/fonts.conf:
 
    <!-- Workaround for
        
 https://lists.nongnu.org/archive/html/freetype/2017-01/msg00019.html
    -->
    <alias>
      <family>Terminus</family>
      <prefer><family>xos4 Terminus</family></prefer>
    </alias>
 
 I'd expect that this breaks a lot of people's configurations, and I'm
 not sure really what the gain is here. Can we at least wait until a new
 major release (ie. 3.0.0) for such breaking changes? :-)

I haven't check, but this is likely caused by this change:

http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=3576487add2f0e9691e8c43f8b0cd8e61aebf14f

So now if foundry name is present result is "<foundryname> <facename>"
as opposed to "<facename>" before this commit.

 
 Thanks,
 
 Chris
 

 Freetype mailing list
 address@hidden
 https://lists.nongnu.org/mailman/listinfo/freetype



Freetype mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/freetype

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.