<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Wishlist: support FC_POSTSCRIPT_NAME" href="https://bugs.freedesktop.org/show_bug.cgi?id=38737#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Wishlist: support FC_POSTSCRIPT_NAME" href="https://bugs.freedesktop.org/show_bug.cgi?id=38737">bug 38737</a> from <a class="email" href="mailto:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> Akira TAGOH</a> <pre>Well, still thinking how to address <a href="show_bug.cgi?id=38737#c4">comment#4</a> though, the ideas I have so far is: For cache: * the change in FcFreeTypeQueryFace(): in case any fonts doesn't have TT_NAME_ID_PS_NAME, generate PS-compliant name from the family name as the printing libraries do. For match: * the change in FcNameParse(): we could add some code to guess if the string is more likely to be the family name or PostScript name from the existence of '-', ' ', and '-H', or '-V' as the suffix etc. set it to FC_FAMILY and/or FC_POSTSCRIPT_NAME. in some case, pre-lookup for that name may be a good idea? because it would be easy to write the mathing rules if we are sure either of the values points to the correct value. otherwise one who is responsible to maintain the rule needs to write the complicated (or duplicated) rules to match either of FC_FAMILY or FC_POSTSCRIPT_NAME then. or think about the syntax to achieve the rule like: If pat['family'] == 'Courier' or pat['postscript'] == 'Courier' then something * in FcNameParse() or in fcstr.c and fclang.c: * any function to guess the language from CMap if any. * a special comparison mode or attribute to ignore the suffix string like CMap. or should it be done with the above idea at pre-stage? There should be more we need to think about, but just to share current idea.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>