Bug 65638

Summary:	changing the matcher function for family to forward matching
Product:	fontconfig	Reporter:	Akira TAGOH <akira>
Component:	library	Assignee:	fontconfig-bugs
Status:	RESOLVED MOVED	QA Contact:	Behdad Esfahbod <freedesktop>
Severity:	enhancement
Priority:	medium	CC:	freedesktop
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Akira TAGOH 2013-06-11 08:23:11 UTC

The issue was raised at Red Hat Bugzilla:
  https://bugzilla.redhat.com/show_bug.cgi?id=956453

Adding all of variants of fonts as aliases are not realistic. I'd suggest to change the matcher function for family name from the exact matching to the forward matching and give the certain score against how many strings is being remained in the buffer.

Comment 1 Behdad Esfahbod 2013-06-12 17:33:15 UTC

I don't think we should do that.  The usecase is clearly Postscript-name specific.  We should have a smart PS_FAMILY matcher, but leave the FAMILY matcher untouched.

Comment 2 Akira TAGOH 2013-06-13 09:02:35 UTC

Indeed that may be the problem that they are requesting it with FC_FAMILY but AFAIUC it's not the point here. if there are no such fonts installed on the system, even if they are expecting to see some serif font, fontconfig returns sans-serif font according to 49-sanserif.conf. and this endeavor is to guess their requirement as much as possible. of course they should use FC_POSTSCRIPT_NAME in this case and we should try to build the better font list for them, which is missing so far and is the rest of the work around the postscript name support.

that said it is the fact that this issue may be likely to happen with the usual query against FC_FAMILY too like we sometimes got a bug, "please add blahblahblah fonts to xxx-yyy.conf".

Comment 3 GitLab Migration User 2018-08-20 21:48:01 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/57.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.