<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Simplify FC_FOUNDRY processing?" href="https://bugs.freedesktop.org/show_bug.cgi?id=88679#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Simplify FC_FOUNDRY processing?" href="https://bugs.freedesktop.org/show_bug.cgi?id=88679">bug 88679</a> from <a class="email" href="mailto:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> Akira TAGOH</a> <pre>(In reply to Behdad Esfahbod from <a href="show_bug.cgi?id=88679#c10">comment #10</a>) > (In reply to Akira TAGOH from <a href="show_bug.cgi?id=88679#c9">comment #9</a>) > > Getting rid of FcNoticeFoundry seems not a good idea. in case it is used in > > the code path, the foundry looks like: > > foundry: "Copyright (c) 1989, 1991 Adobe Systems Incorporated. All Rights > > Reserved.Utopia is a registered trademark of Adobe Systems Incorporated."(s) > > > > it isn't what we expect. > > Humm. I thought it looks for strings like Adobe and assigns "Adobe"... right. so FcNoticeFoundry assigns "Adobe" instead of the above copyright notice in that case. let me show you some examples we fail on picking up foundries without FcNoticeFoundry. there are two code paths acquire the information through FcNoticeFoundry. one is from TT_NAME_ID_{TRADEMARK,MANUFACTURE} and one is FT_Get_PS_Font_Info. the former one fails on google-crosextra-caladea and lyx say. later one is Type1 fonts and some PCF fonts. apparently we need to keep maintaining FcNoticeFoundry at least for them.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>