I added a sentence in the git archive, this will make it into the
next release.
Dear Markus,
As far as I understand, Freetype uses the native hinter (OS
hinter, I believe), but I do not know much, this is outside of
my expertise. See e.g. https://www.freetype.org/freetype2/docs/text-rendering-general.html
Any changes in the manual will have
to wait until I do a new release, and that will only happen if
there are security issues found. I have precious little time for
these hobby projects nowadays. Hopefully people can find this
discussion in the mailing list archives for the time being.
Best
Jan-Åke
On 2019-01-06 11:46, Markus Triska
wrote:
Dear Jan-Åke,
perfect, this worked, thank you very much!
Do you have a guess why FreeType handles this differently on different
platforms? This is a severe drawback in my view, because I need
pixelwise identical results. I realize this is somewhat outside the
scope of dvipng, yet also important because using FreeType is the
default, and the manual strongly encourages it.
This is clearly a use case that benefits much from --freetype0. Would
you please consider adding a note about such cases to the manual, or
(of course even better) consider a way to make dvipng obtain identical
results even when FreeType and its antialiasing is enabled?
Thank you and all the best!
Markus
_______________________________________________
Dvipng mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dvipng
--
Jan-Åke Larsson
Professor, Head of Department
|
Department
of Electrical Engineering
SE-581 83 Linköping
Phone: +46 (0)13-28 14 68
Mobile: +46 (0)13-28 14 68
Visiting address: Campus Valla, House B, Entr 27, 3A:482
Please visit us at www.liu.se |
_______________________________________________
Dvipng mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dvipng