Test fails imho because of wrong out.expected. fontconfig-2.9.0/test[1]> for i in 4x6.pcf 8x16.pcf ; do fc-query $i; done | grep "family\|size" Pattern has 18 elts (size 32) family: "Misc Fixed"(s) pixelsize: 6(f)(s) Pattern has 18 elts (size 32) family: "Sony Fixed"(s) pixelsize: 16(f)(s) fontconfig-2.9.0/test[0]> cat out.expected Fixed:pixelsize=16 Fixed:pixelsize=6 = Fixed:pixelsize=16 Fixed:pixelsize=6 = Fixed:pixelsize=16 Fixed:pixelsize=6 fontconfig-2.9.0/test> cat out Misc Fixed:pixelsize=6 Sony Fixed:pixelsize=16 = Misc Fixed:pixelsize=6 Sony Fixed:pixelsize=16 = Misc Fixed:pixelsize=6 Sony Fixed:pixelsize=16
I don't see any fails on those testing. is it a result of run-test.sh in test dir?
(In reply to comment #1) > I don't see any fails on those testing. is it a result of run-test.sh in test > dir? Hmmmm ... Yes. with make check I get: [...] make[2]: Entering directory `/home/abuild/rpmbuild/BUILD/fontconfig-2.9.0/test' *** Test failed: Basic check *** output is in 'out', expected output in 'out.expected' FAIL: run-test.sh ================== 1 of 1 test failed ================== [..] I thought it is because fontconfig-2.9.0/test> FONTCONFIG_FILE=`pwd`/fonts.conf ../fc-list/fc-list - family pixelsize gives Misc Fixed:pixelsize=6 Sony Fixed:pixelsize=16 for me instead of Fixed:pixelsize=16 Fixed:pixelsize=6 in the out.expected. (note strings before whitespace seems to be removed.)
actually "Misc" and "Sony" is the foundry but not the family name though. you can try FC_DEBUG=384 fc-query.
(In reply to comment #3) > actually "Misc" and "Sony" is the foundry but not the family name though. you > can try FC_DEBUG=384 fc-query. Tried: fontconfig-2.9.0/test> FC_DEBUG=384 ../fc-query/fc-query 4x6.pcf | grep "family\|foundry" Fontconfig error: Cannot load default config file using FreeType family "Misc Fixed" family: "Misc Fixed"(s) foundry: "Misc"(s) So what's wrong?
Do you have any patches in freetype for that perhaps?
(In reply to comment #5) > Do you have any patches in freetype for that perhaps? You are right, that's it. Marking the patch fixing the test as suse-specific, will try to figure out why we have this later. Thanks a lot & sorry for noise.
(In reply to comment #6) > (In reply to comment #5) > > Do you have any patches in freetype for that perhaps? > > You are right, that's it. Marking the patch fixing the test as suse-specific, > will try to figure out why we have this later. Yes, suse has been carrying that patch for quite a while.
One of our users at Exherbo is hitting this bug again with freetype >=2.7.1
Test output diff as reference: --- out 2017-03-19 12:11:15.790611338 +0100 +++ out.expected 2012-02-20 04:49:18.000000000 +0100 @@ -1,8 +1,8 @@ -Misc Fixed:pixelsize=6 -Sony Fixed:pixelsize=16 +Fixed:pixelsize=16 +Fixed:pixelsize=6 = -Misc Fixed:pixelsize=6 -Sony Fixed:pixelsize=16 +Fixed:pixelsize=16 +Fixed:pixelsize=6 = -Misc Fixed:pixelsize=6 -Sony Fixed:pixelsize=16 +Fixed:pixelsize=16 +Fixed:pixelsize=6
I see this issue and introduced by freetype 2.7.1: - 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'.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/84.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.