Thanks for your input! :)
I have something like that in mind but I don't think that a complicated
algorithm is needed here; we're basically working with two alpha bitmaps of
(roughly) the same size. I would simply compare the bitmaps on a pixel-by-pixel
basis, weigh the results by the max.
I'm not familiar with graphics testing, but maybe algorithms exist that
look for a magnitude of a difference between two images (maybe something
like this exists in video encoding land?). Then you could ignore changes
less than 1% or something.
___
Thanks a lot for clarifying that, I will look into that demo program! :)
Armin
On 19/03/2018 18:25:21, Werner LEMBERG wrote:
> Further, if I understand correctly (I have to and will read up on
> this though), outlines do not take stem hints into account.
This is not correct. It's
> Further, if I understand correctly (I have to and will read up on
> this though), outlines do not take stem hints into account.
This is not correct. It's exactly the hinting that distorts glyph
outlines so that they are rendered better at lower resolutions. You
might play with the `ftgrid'
Thanks for your insight! :)
I was just wondering in terms of a test framework that would detect and present
rendering regressions: what should said framework compare, and what would it
present? Have you had a chance to look at my GSoC draft proposal?
Judging from your text, comparing glyphs
> > Concretely: is the outline-to-bitmap algorithm definitive and
> > final or is it subject to (probably subtle) changes every now and
> > then?
>
> Most changes happen to the outlines. However, from time to time, both
> the B/W and graymap rasterizers get modified; for such cases it is
>
Hi,
Due to my college exams I will have to delay my draft proposal submission.
I will do that as soon as the exam gets over. I will send it by 22nd so
that we can discuss further.
Thank You
Regards
Parth
On Sun, Mar 18, 2018 at 12:04 PM, Parth Wazurkar
wrote:
>
>