| Summary: | Option to fc-match to NOT call FcConfigSubstitute / FcDefaultSubstitute? | ||
|---|---|---|---|
| Product: | fontconfig | Reporter: | Behdad Esfahbod <freedesktop> |
| Component: | fc-match | Assignee: | fontconfig-bugs |
| Status: | RESOLVED MOVED | QA Contact: | Behdad Esfahbod <freedesktop> |
| Severity: | normal | ||
| Priority: | medium | CC: | akira, freedesktop |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Behdad Esfahbod
2014-07-04 21:18:00 UTC
I'm not sure how this helps for debugging. as I mentioned in other bug, matching a font without calling FcDefaultSubstitute() may makes wrong result unless all the required values are provided in the pattern. I know that fully agree. However, I could really use the option when debugging this: https://code.google.com/p/chromium/issues/detail?id=392724 At the end it was using fc-pattern utility that enlightened me. I had forgotten that FcConfigSubstitute() adds FC_LANG. Will file another bug re that. -- 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/52. |
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.