On Fri, 2005-10-28 at 03:54, Ulrich wrote:
This is correct but I still think that this fact doesn't imply that it isn't
possible to set up a test suite. As far as I understand FreeType will
generate a certain rasterisation result depending on the parameter settings
and the environment it
On Fri, 2005-10-28 at 14:38, Ulrich wrote:
It's more than just shape. It's the difference between a pixel having
0xfe and 0xfd.
Sorry for using the wrong term shape. It should have been result. I
assume that every single change in the result has to be checked as one pixel
being on or
1. What modules should we include in LSB to begin with?
I don't see a reason to exclude a module.
I can see several reasons:
some modules are still experimental and not well tested. I'm thinking
primarily about the otvalid and gxvalid ones used to perform
validation of OpenType tables.
we
On Mon, 2005-10-10 at 16:37, Fujinaka, Todd wrote:
I may have done something wrong, but those tests take an incredibly long
time.
Oh, they never end. It keeps churning out random tests and saving the
few that cause problems.
I think the tests we need are just something to test to see that all
On Sat, 2005-10-08 at 01:49, Ulrich wrote:
Sure, but as long as FreeType deterministically produces its results
depending on certain parameter settings (including the automatically
detected environment) testing is still a matter of deciding whether these
results are still the same compared
