https://bugzilla.redhat.com/show_bug.cgi?id=2081539
Akira TAGOH <tagoh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagoh(a)redhat.com
--- Comment #5 from Akira TAGOH <tagoh(a)redhat.com> ---
(In reply to Hedayat Vatankhah from comment #4)
Yes, sure. And thank you for reviewing my package :)
Just a quick question (part of the above emails): should I package variable
version of the fonts separately from the normal ones? I've seen that at
least some fonts, e.g. the Noto fonts, have separate package for variable
fonts (-vf subpackages), but I don't know if I should do the same (by
definition, seems that all of them belong to a single family). If I
can/should put them in a separate subpackage, what should their fontconfig
file contain? For Noto (Arabic) fonts, I saw the variable fonts have 'have
hints' (not the exact word) set to true while non-variable version has set
it to false. I wonder if the same thing is correct for all variable fonts or
it is just specific to Noto fonts?
Thanks again, I'll upload a new version in a few hours.
You should have a variable font in a separate package because both, variable
and non-variable fonts eventually looks same at the application level as they
have same family name and both is available at a sort of the font picker which
isn't better experience. Also, the users aren't able to recognize which one is
a variable or non-variable.
This is the reason why we have a separate package for variable and non-variable
fonts.
For "fonthashint" property in fontconfig, variable fonts doesn't have
hinting.
fontconfig has a recipe to enable "autohint"ing if "fonthashint" is
set to
false. this is to provide better rendering with variable fonts.
Hope that helps.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2081539