Re: FcPattern Gotcha
Akira TAGOH <[email protected]>
| Newsgroups | gmane.comp.fonts.fontconfig |
|---|---|
| Message-ID | <CACT-Cx2PyqJ_-NchCBP6yqD-b2ck40pmHpbETGu_AK1Z0p7szA@mail.gmail.com> |
Can you attach the example that can reproduce your issue? FcNameParse() should generates the same FcPattern with the strings generated by FcNameUnparse(). On Tue, Nov 29, 2016 at 2:43 PM, Lawrence D'Oliveiro < [email protected]> wrote: > On Tue, 29 Nov 2016 13:08:48 +0900, Akira TAGOH wrote: > > > On Tue, Nov 29, 2016 at 11:19 AM, Lawrence D'Oliveiro < > > [email protected]> 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 > [email protected] > https://lists.freedesktop.org/mailman/listinfo/fontconfig > -- Akira TAGOH _______________________________________________ Fontconfig mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/fontconfig