Summary: | FcFontList "contain" semantics unproductive | ||
---|---|---|---|
Product: | fontconfig | Reporter: | Behdad Esfahbod <freedesktop> |
Component: | library | Assignee: | fontconfig-bugs |
Status: | RESOLVED MOVED | QA Contact: | Behdad Esfahbod <freedesktop> |
Severity: | normal | ||
Priority: | medium | CC: | akira, drott, freedesktop |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Behdad Esfahbod
2018-07-16 12:04:38 UTC
What ops is preferred may depends on the context and property. I suppose OR op may be preferred for the unique value in a property like family. but both AND and OR might be for bitwise property like charset/lang. most properties has unique value. in this sense we could change the behavior but obvious syntax would needs to be added for AND. (In reply to Akira TAGOH from comment #1) > What ops is preferred may depends on the context and property. I suppose OR > op may be preferred for the unique value in a property like family. but both > AND and OR might be for bitwise property like charset/lang. most properties > has unique value. in this sense we could change the behavior but obvious > syntax would needs to be added for AND. Both charset and lang keep multiple values in same element. The caller can create a charset/lang and add everything they want into it if AND is needed... I think just changing the behavior is fine to be honest. -- 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/5. |
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.