Le mercredi 24 juillet 2019 à 14:37 +0200, Kevin Kofler a écrit :
Hi, Kevin
Thank you for taking the time to answer,
> Nicolas Mailhot wrote:
> > 2. fontconfig strives to hide all the legacy ways to designate
> > different
> > parts of this ideal font, and strives to expose a single "font"
> > o
Le 2019-07-24 13:49, Akira TAGOH a écrit :
Hi Akira
On Tue, Jul 23, 2019 at 10:45 PM Nicolas Mailhot
wrote:
No foo variable, foo hebrew, foo narrow, foo caption, just a single
foo
with different available features (full variability or fixed states on
the default axis, real upstream provided
Nicolas Mailhot wrote:
> 2. fontconfig strives to hide all the legacy ways to designate different
> parts of this ideal font, and strives to expose a single "font" objet no
> matter what quirks exist in individual font files. We stop exposing lots
> of weird quirky bits right and left, that need ma
On Tuesday, 23 July 2019 at 15:45, Nicolas Mailhot via devel wrote:
> Hi,
>
> Now that things are starting to move fonts-side[1], I’d like the various
> actors to agree on a common font model target.
[...]
> Therefore, I’d like to propose that the target font model on freedesktop
> systems, is the
Hi,
Now that things are starting to move fonts-side[1], I’d like the various
actors to agree on a common font model target.
Without a a common target, we’ll end up working at odds with one
another. Upstream font files can not serve as a an officious target.
They are full of quirks, you end u
