https://bugzilla.redhat.com/show_bug.cgi?id=1813187
Akira TAGOH <tagoh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(tagoh(a)redhat.com) |
--- Comment #6 from Akira TAGOH <tagoh(a)redhat.com> ---
If ghostscript has no plans to support variable fonts or a plan to support only
named-instances, you can set false to FC_VARIABLE
as a query pattern; that should be more simple and easier than your patch
applied in ghostscript; you can take care of the named-instances in VF font
files as same as usual face then. otherwise set FcDontCare to FC_VARIABLE and
need more changes in the code to deal with non-named-instances perhaps.
The meta face which you faced the issue this time provides such information
instead of providing it as one of faces because there are so many patterns to
enummerate everything and quite hard to do. the targetted properties such as
FC_WEIGHT, FC_WIDTH and FC_SIZE has a value in FcRange which means they can use
an unique value between them.
Unfortunately there are no more detailed document though, pango source code may
helps how to deal with them.
--
You are receiving this mail because:
You are on the CC list for the bug.