On Mon, Sep 30, 2019 at 10:32 PM Vladimir Panteleev <git@xxxxxxxxxxxxxxxxxxxxx> wrote: > > On Mon, 30 Sep 2019 at 11:55, Akira TAGOH <akira@xxxxxxxxx> wrote: > > How about fc-list and/or fc-match? does it contain the expected font? > > I can get it to list the font with these. Probably I should clarify > that the problem is restricted to Qt applications, I can select and > use the font fine with other programs. > > I don't know how the Qt application queried the font, so I found > FC_DEBUG. If I'm reading it correctly, it looks like the "file" > property is already part of the *match* pattern, meaning that Qt > already knows which file the font is in. After > > a57f22bf, it is specifying a different file (8x13 instead of 7x13), so > it seems that the change causes it to refuse 7x13 or prefer 8x13 over > it. Hm. apparently that would be better reporting this to Qt. Looking at the above results, I'm afraid there is nothing we can do in fontconfig. > > > > You could even see with fc-query /path/to/font how fontconfig parses > > it. you may see more clue on it. > > As expected from reading the patch, before a57f22bf, fc-query does not > show a "familylang" property for /usr/share/fonts/misc/7x13.pcf.gz, > but it does show one (with value "en") after a57f22bf. > > Thanks! Thanks, -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/fontconfig
