Hin-Tak Leung
2018-08-02 15:14:45 UTC
Hi,
This is a follow-up to my earlier message below.
For easier reading by individual font owners/maintainers, the test result are now unpacked under :
https://github.com/HinTak/FontVal-Tests-at-10pt
with the exact file system hierarchy as the font files themselves as on the corresponding Linux distribution, with a leading "/usr/share" removed.
There are currently two branches, "fedora" and "ubuntu". The fedora branch contains also the past annual-ish testing results. This allow easier checking of both changes/improvements of libre fonts, as well as regression in FontVal itself.
At the bottom of the fedora branch is the FontVal 1.0 test result around 2016 October on Fedora (24). At some point differences between that and the current 2.x (I.e. FreeType) backend needs to be looked at and documented as bugs of old legacy backend, regression of new, or simply differences between Microsoft rendering and jFreeType. That will be a large undertaking.
The commit dates are meaningless at the moment, though luckily the reports themselves say when they were generated.
I'll add a readme wiki at some point.
Please spread the news to font owners/maintainers.
--------------------------------------------
On Thu, 12/7/18, Hin-Tak Leung <***@users.sourceforge.net> wrote:
Subject: FontVal changes and the next set of test results of libre fonts
To: ***@lists.freedesktop.org, freetype-***@nongnu.org
Cc: ***@lab6.com
Date: Thursday, 12 July, 2018, 19:05
Hi all,
Since mid-May actually, for about two
months now, I have been running my fedora linux box with the
system freetype fully patched /enabled with the FontVal
changes without noticeable problems.
To recap, when Microsoft opened the
Font Validator code base, they left out a few pieces, one of
which was the part which does truetype hinting instruction
analysis (a.k.a. "rasterization tests"). A replacement based
on FreeType was gradually developed over the last 3 years,
and was "feature complete" (as in, implementing all of the
previous, more or less) last summer. There were some
discussion about up-streaming those changes; and before that
can happen, if at all, they must not interfere with normal
freetype usage as the system font renderer.
So anyway,
The test results of all of fedora
shipped fonts - about 3600 of those - around mid-May, using
the system's enhanced freetype library, at 10pt, is here
http://htl10.users.sourceforge.net/tmp/fc28-ras-results.tgz
and at the beginning of June I also
collected all the test results, again at 10pt, for all
Ubuntu WSL (supposedly 16.04) shipped fonts, again about
3500 of them - is here
http://htl10.users.sourceforge.net/tmp/ubuntu-wsl-reports.tgz
Font owners etc can have a look.
There were some interface adjustments
to both the C# binding and the python binding to the
enhanced backend for adapting to system-freetype usage, at
https://github.com/HinTak/freetype-py , font-diag
branch.
https://github.com/HinTak/SharpFont , v4??+fixes
branch.
The next important change to Font Val
has to be re-enabling building with MS visual studio.
Apparently at least two people have had a go (without trying
to tell me to co-ordinate the effort)... according to the
network of forks...
https://github.com/Microsoft/Font-Validator/network
https://github.com/HinTak/Font-Validator/network
This is a follow-up to my earlier message below.
For easier reading by individual font owners/maintainers, the test result are now unpacked under :
https://github.com/HinTak/FontVal-Tests-at-10pt
with the exact file system hierarchy as the font files themselves as on the corresponding Linux distribution, with a leading "/usr/share" removed.
There are currently two branches, "fedora" and "ubuntu". The fedora branch contains also the past annual-ish testing results. This allow easier checking of both changes/improvements of libre fonts, as well as regression in FontVal itself.
At the bottom of the fedora branch is the FontVal 1.0 test result around 2016 October on Fedora (24). At some point differences between that and the current 2.x (I.e. FreeType) backend needs to be looked at and documented as bugs of old legacy backend, regression of new, or simply differences between Microsoft rendering and jFreeType. That will be a large undertaking.
The commit dates are meaningless at the moment, though luckily the reports themselves say when they were generated.
I'll add a readme wiki at some point.
Please spread the news to font owners/maintainers.
--------------------------------------------
On Thu, 12/7/18, Hin-Tak Leung <***@users.sourceforge.net> wrote:
Subject: FontVal changes and the next set of test results of libre fonts
To: ***@lists.freedesktop.org, freetype-***@nongnu.org
Cc: ***@lab6.com
Date: Thursday, 12 July, 2018, 19:05
Hi all,
Since mid-May actually, for about two
months now, I have been running my fedora linux box with the
system freetype fully patched /enabled with the FontVal
changes without noticeable problems.
To recap, when Microsoft opened the
Font Validator code base, they left out a few pieces, one of
which was the part which does truetype hinting instruction
analysis (a.k.a. "rasterization tests"). A replacement based
on FreeType was gradually developed over the last 3 years,
and was "feature complete" (as in, implementing all of the
previous, more or less) last summer. There were some
discussion about up-streaming those changes; and before that
can happen, if at all, they must not interfere with normal
freetype usage as the system font renderer.
So anyway,
The test results of all of fedora
shipped fonts - about 3600 of those - around mid-May, using
the system's enhanced freetype library, at 10pt, is here
http://htl10.users.sourceforge.net/tmp/fc28-ras-results.tgz
and at the beginning of June I also
collected all the test results, again at 10pt, for all
Ubuntu WSL (supposedly 16.04) shipped fonts, again about
3500 of them - is here
http://htl10.users.sourceforge.net/tmp/ubuntu-wsl-reports.tgz
Font owners etc can have a look.
There were some interface adjustments
to both the C# binding and the python binding to the
enhanced backend for adapting to system-freetype usage, at
https://github.com/HinTak/freetype-py , font-diag
branch.
https://github.com/HinTak/SharpFont , v4??+fixes
branch.
The next important change to Font Val
has to be re-enabling building with MS visual studio.
Apparently at least two people have had a go (without trying
to tell me to co-ordinate the effort)... according to the
network of forks...
https://github.com/Microsoft/Font-Validator/network
https://github.com/HinTak/Font-Validator/network