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

[bugzilla-noreply at freebsd.org]

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

--- Comment #27 from lightside <lightside at gmx.com> ---
(In reply to comment #25)
> convert -density 300 -colorspace sRGB -resize 50% -border 2 test.pdf[0]
> convert.jpg -> Font looks blurry
> <..>
> So what do you think?
If "Font looks blurry", then this may be different issue. Previous issue was
related to not readable characters for output image(s).

The print/freetype2 v2.9 changed defaults from LCD_FILTERING ("Subpixel
rendering (patented)") to LCD_RENDERING ("Harmony LCD rendering") option. See
bug #225072 for details. So, possible to check new output after LCD_FILTERING
option usage for print/freetype2 port, if this is the case. Personally, I
reported about some differences for emulators/wine-devel port in bug #228518,
comment #4, but it was also related to used fontconfig configuration.

Otherwise, since I don't have required pdf to test (to find related Git commit,
with using `git bisect`), I may just guess, that if pdftoppm output was ok and
it used the same FreeType library:
-8<--
% sh -c "pdftoppm --help 2>&1" | grep freetype
  -freetype <string>       : enable FreeType font rasterizer: yes, no
% pdftoppm -freetype yes -jpeg test.pdf image
% pdftoppm -freetype no -jpeg test.pdf image
-->8-

then this issue might be Ghostscript related (and/or how it uses FreeType
library).

The pdftoppm program doesn't use Ghostscript, as far as I know. You could check
this, if you delete installed ghostscript ports (e.g. create backup packages:
`pkg create -x ghostscript`, delete: `pkg delete -fx ghostscript`, reinstall
after check: `pkg add ghostscript*`) and run the same pdftoppm commands.

You can check ImageMagick's convert program about Ghostscript usage, if you run
it with using -verbose option:
-8<--
% convert --help | grep verbose
  -verbose             print detailed information about the image
% convert -verbose test.pdf output.jpg
'gs' -sstdout=%stderr <..>
% pkg which -o `which gs`
/usr/local/bin/gs was installed by package print/ghostscript9-agpl-base
-->8-

If you want, you can report about (new) issue to Ghostscript and/or FreeType
bug trackers. Probably, they may ask about needed information (e.g. tested pdf
(and/or used fonts), expected output image(s), etc.) and to check development
version(s) for possible fixes. If fix is available, then possible to propose it
for related FreeBSD port(s) before new available release version (but this may
depend from amount of required changes, of course).

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