libXft: Changes to 'no-custom-types'
GitLab Mirror
gitlab-mirror at kemper.freedesktop.org
Sat Apr 4 00:54:50 UTC 2020
New branch 'no-custom-types' available with the following commits:
commit 6e7da3c7c40deed551d14b6bab6f3d1ac256509f
Author: Keith Packard <keithp at keithp.com>
Date: Fri Apr 3 17:53:33 2020 -0700
Remove call to FcNameRegisterObjectTypes
This fontconfig function has been deprecated and no longer does
anything.
Signed-off-by: Keith Packard <keithp at keithp.com>
commit 26a3a497409279d74827f374e65ae4b8d3c1f1f7
Author: Keith Packard <keithp at keithp.com>
Date: Fri Apr 3 17:43:04 2020 -0700
Skip 'render' pattern elements with invalid type
Fontconfig no longer supports the FcNameRegisterObjectTypes API, which
means that any Xft custom fields cannot be specified in a fontconfig
name as those will always be set to FcTypeUnknown in the pattern.
The only one of those we care about is XFT_RENDER, which was used to
disable the Render extension, something most apps probably don't need
to support in names anyways. Allow the call requesting this value to
return FcResultTypeMismatch and pretend that XFT_RENDER is missing
from the pattern.
Signed-off-by: Keith Packard <keithp at keithp.com>
More information about the xorg-commit
mailing list