freetype-2.7.1 has changed naming policy for pcf fonts: - 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'. The font's name in /etc/fonts/conf.avail/75-yes-terminus.conf must be changed accordingly: --- 75-yes-terminus.conf 2017-01-09 19:39:05.704273108 +0900 +++ 75-yes-terminus.conf.new 2017-01-09 19:37:51.441342092 +0900 @@ -5,7 +5,7 @@ <selectfont> <acceptfont> <pattern> - <patelt name="family"><string>Terminus</string></patelt> + <patelt name="family"><string>xos4 Terminus</string></patelt> </pattern> </acceptfont> </selectfont>
Now the command "fc-match 'xos4 Terminus'" returns the actual terminus font file. But this is just one stem of ramification from freetype-2.7.1 update. Packages that hinges on a pcf font's name through freetype should mirror this. For example, the default configuration of x11-wm/dwm calls for "Terminus" and this will cause unexpected behavior. Other pcf fonts should be taken care of and also for packages that depends on them.
hmm this patch does not work.. # patch 75-yes-terminus.conf a.patch patching file 75-yes-terminus.conf patch: **** malformed patch at line 10: </acceptfont>
Created attachment 459632 [details, diff] patch against the source tree Sorry, that diff was just to show the conf difference. Attaching a new patch against the terminus source tree.
well patch run through, but i am not on OSX Portage 2.3.3 (python 3.5.2-final-0, default/linux/amd64/13.0/desktop/plasma/systemd, gcc-5.4.0, glibc-2.23-r3, 4.9.2-gentoo x86_64) ================================================================= System uname: Linux-4.9.2-gentoo-x86_64-Intel-R-_Core-TM-_i7-3740QM_CPU_@_2.70GHz-with-gentoo-2.3 KiB Mem: 24626196 total, 15680216 free KiB Swap: 26488828 total, 26488828 free Timestamp of repository gentoo: Wed, 11 Jan 2017 20:30:01 +0000 Timestamp of repository poly-c: Wed, 11 Jan 2017 13:32:55 +0000 sh bash 4.4_p5-r1 ld GNU ld (Gentoo 2.27 p1.0) 2.27 app-shells/bash: 4.4_p5-r1::gentoo dev-java/java-config: 2.2.0-r3::gentoo dev-lang/perl: 5.24.1_rc4::gentoo dev-lang/python: 2.7.12::gentoo, 3.4.5::gentoo, 3.5.2::gentoo dev-util/cmake: 3.7.1::gentoo dev-util/pkgconfig: 0.29.1::gentoo sys-apps/baselayout: 2.3::gentoo sys-apps/openrc: 0.23.1::gentoo sys-apps/sandbox: 2.10-r3::gentoo sys-devel/autoconf: 2.13::gentoo, 2.69-r2::gentoo sys-devel/automake: 1.13.4-r1::gentoo, 1.14.1-r1::gentoo, 1.15-r2::gentoo sys-devel/binutils: 2.27::gentoo sys-devel/gcc: 5.4.0-r2::gentoo sys-devel/gcc-config: 1.8-r1::gentoo sys-devel/libtool: 2.4.6-r2::gentoo sys-devel/make: 4.2.1::gentoo sys-kernel/linux-headers: 4.9::gentoo (virtual/os-headers) sys-libs/glibc: 2.23-r3::gentoo Repositories: ################# i also confirm this problem that terminus does not work under dwm wm, and fall back to this ugly default font... maybe someone has a solution. my .Xdefault is in the meanwhile out commented: !URxvt.font: xft:terminus:pixelsize=14:antialias=false !URxvt.boldFont: xft:terminus:bold:pixelsize=14:antialias=false !URxvt.italicFont: xft:terminus:italic:pixelsize=14:antialias=false !URxvt.boldItalicFont: xft:terminus:bolditalic:pixelsize=14:antialias=false :((
I checked dwm's default font and it's not "Terminus" but "monospace", so dwm is off the hook. Sorry for my presumption. Since no package should set default font to a specific one without RDEPEND or something, the patch to 75-yes-terminus.conf would suffice to address the problem. And I also expect the conf be updated soon by the upstream to work along with freetype-2.7.1. As most users choose to use whatever font they want, losing their favorite font settings and spending time to find out the culprit and an apropriate fix would be inconvenient or pesky for them. It would be nice to give notice to those who update to freetype-2.7.1. The impact to UX is very abrupt and present, although the naming policy change might be a minor thing for freetype.
freetype-2.7.1-r1 reverts to old naming policy for pcf fonts. (bug 606688) So scratch this too.
