Il 19 giu 2017 21:23, "Stuart Henderson" <[email protected]> ha scritto:
On 2017/06/19 17:46, David Coppa wrote: > > > Il 19 giu 2017 16:19, "Stuart Henderson" <[email protected]> ha > scritto: > > I'm looking at updating freetype, mostly to unbreak PCF font names > which are currently different on different machines (e.g. I have > "xos4 > Terminus" on a more recently installed laptop but just "Terminus" > on > other machines that have been upgraded from older versions). This > is a > problem for ports which hardcode the font name like dwm and dmenu > as > there isn't any one name which will work on all machines. > > It looks mostly straightforward to update (new functions -> minor > bump), > but it looks like there's something odd with builds/unix/ > freetype-config.in, > our file isn't the same as upstream's last release, any suggestions > on what > to do with this? > > > I've already posted an update to freetype-2.8, asking for a bulk build, > and Matthieu already tested it... Have you missed it for some reasons? > > > Ah, found it now. I'll do an i386 bulk after my current one is done. There's a difference in include/freetype/config/ftoption.h compared to upstream's; they has PCF_CONFIG_OPTION_LONG_FAMILY_NAMES commented-out, your diff has it enabled. I'd really like to get this disabled and back to the normal names for PCF fonts, unless someone can fix it so that it's consistent between newly installed and upgraded machines. Here' a bit of rationale: The PCF change to show more "colourful" family names (introduced in version 2.7.1) was too radical; it can now be configured with PCF_CONFIG_OPTION_LONG_FAMILY_NAMES at compile time. If activated, it can be switched off at run time with the new pcf property 'no-long-family-names': export FREETYPE_PROPERTIES="pcf:no-long-family-names=1" Some users think the long family names are useful, some other not. I think, by enabling the option, we can leave users the freedom of choice. Arch Linux also enabled the option. Ciao! David
