[Bug 227761] print/freetype2: Fonts aren't correctly rendered with 2.9

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri May 4 02:06:03 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227761

lightside <lightside at gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #193013|0                           |1
        is obsolete|                            |

--- Comment #6 from lightside <lightside at gmx.com> ---
Created attachment 193036
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193036&action=edit
Testing environment for freetype2, based on git bisect

(In reply to Baptiste Daroussin from comment #2)
> I can reproduce for sure, but I am not sure how to debug that :(
I think, also possible to enable some debugging features in a FreeType 2 builds
(e.g. selected DEBUG option for print/freetype2 port):
https://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/docs/DEBUG?h=VER-2-9-1#n1
https://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/include/freetype/config/ftoption.h?h=VER-2-9-1#n398

After build possible to use FT2_DEBUG (and/or other) environment variable(s) in
conjunction with test program. For example:
% env FT2_DEBUG="any:5" LD_PRELOAD=./objs/.libs/libfreetype.so sh -c "convert
-append path/to/file.pdf image.jpg 2>&1"

Attached new archive with testing environment:
- Added -d option for "git clean" command to also remove created directories
during build, e.g. ./objs/.libs
- Added help, clean, build, test options for test.sh script
- Added some debugging settings
- Removed anonyme_visitenkarte.pdf file, which possible to download/extract
from previous attachment #193013:
% fetch -o - "https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193013" | tar
-xf - --include anonyme_visitenkarte.pdf
% sha256 anonyme_visitenkarte.pdf 
SHA256 (anonyme_visitenkarte.pdf) =
949b114d3e2cf21fc7f97ade1491c73c292fee04525c2cf551ab05543901d6ae

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.


More information about the freebsd-gnome mailing list