Mailinglist Archive: opensuse-bugs (4258 mails)

< Previous Next >
[Bug 904015] outlined fonts didn't get their antialias enabled by fontconfig in openSUSE 13.2 and above
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 31 Jan 2017 10:28:23 +0000
  • Message-id: <bug-904015-21960-oIFMVWlTxe@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=904015
http://bugzilla.suse.com/show_bug.cgi?id=904015#c35

Petr Gajdos <pgajdos@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |pgajdos@xxxxxxxx,
| |tiwai@xxxxxxxx

--- Comment #35 from Petr Gajdos <pgajdos@xxxxxxxx> ---
(In reply to Marguerite Su from comment #31)
<match target="pattern">

This element holds first a (possibly empty) list of <test> elements and then
a (possibly empty) list of <edit> elements. Patterns which match all of the
tests are subjected to all the edits. If 'target' is set to "font" instead
of the default "pattern", then this element applies to the font name
resulting from a match rather than a font pattern to be matched.

Let me explain it in another simple way:

If you use <match target="font">, you have to write a "test" condition that
actually matches "one" font. (you see there's no "the font names" but "the
font name").

I do not understand it that way. 'pattern' changes entries in the pattern
before matching the pattern to a real font. Then the matching of pattern to a
one real font in the system happens which results in a pattern that correspons
to only that font (incl. 'file' entry for example). Later, 'font' type changes
are performed on entries in the pattern that corresponds to one font in the
system, just before it is returned from the library.

That means, for example, that:

<match target="font">
<!-- hinting is on unconditionally, but that -->
<!-- can be controlled via hintstyle (hintnone) -->
<edit name="hinting" mode="assign">
<bool>true</bool>
</edit>
</match>

says: 'for every real font pattern set hinting to true'. Or:

<match target="font">
<test name="fontformat">
<string>CFF</string>
</test>
<edit name="autohint" mode="assign">
<bool>false</bool>
</edit>
</match>

says: for every real font pattern, where fontformat=CFF, set autohint to false.
That is because CFF are not supposed to be rendered by autohinter.

That all sounds correct, because most likely 'fontformat' entry of the pattern
is likely not filled in at all before matching to real font.

And now:

<match target="font">
<!-- this test should not be needed,
as antialiasing is done only for outlines,
but workarounds Qt5 issue, see bug 866705 -->
<test name="outline">
<bool>true</bool>
</test>
<edit name="antialias" mode="assign">
<bool>true</bool>
</edit>
</match>


This sounds correct to me to change font, again, because I think 'outline' will
probably not part of the pattern before matching at all. Writing from top of my
head, sorry If I overlooked something.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >