On Tue, 29 Nov 2016 13:08:48 +0900, Akira TAGOH wrote: > On Tue, Nov 29, 2016 at 11:19 AM, Lawrence D'Oliveiro < > ldo@xxxxxxxxxxxxxxxxxxx> wrote: > >> I figured out that the problem seems to come from the inclusion >> of the “lang” and “charset” criteria in the returned pattern: the >> values for these tend to consist of long lists of items separated >> by “|” characters. But remove them, and the resulting pattern will >> correctly find the font again. >> > How did you do that? the separator is only shown by the debugging > output like FcPatternPrint() though, it isn't expected to reuse it > for any other purposes. This was in the return value from FcNameUnparse. _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/fontconfig
