bugThe FreeType Project - Bugs: bug #53739, Fonts aren't correctly rendered...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #53739: Fonts aren't correctly rendered with 2.9

Submitter:  None
Submitted:  Tue 24 Apr 2018 02:45:53 PM UTC
   
 
Severity:  3 - Normal Item Group:  None
Status:  Invalid Privacy:  Public
Assigned to:  wl Open/Closed:  Closed
Planned Release:  None

Jump to the original submission

Tue 14 Aug 2018 08:31:47 AM UTC, comment #11: 

I think it's best to discuss this further at

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

Werner LEMBERG <wl>
Group administrator
Mon 13 Aug 2018 08:42:45 AM UTC, comment #10: 

If I convert the pdf with "pdftops" and then use "gs" to convert it to a jpg it works. But it doesn't work if I use "gs" directly with the .pdf

Pascal Christen <pesc>
Mon 13 Aug 2018 07:50:20 AM UTC, comment #9: 

Hi

I'm having the same problem (but with a diffrent pdf) again. How can I check if it's a ghostscript, freetype or FreeBSD-port issue?

Thanks for your help

Pascal Christen <pesc>
Fri 15 Jun 2018 08:28:10 PM UTC, comment #8: 

Thanks, closing.

Werner LEMBERG <wl>
Group administrator
Thu 14 Jun 2018 11:50:56 AM UTC, comment #7: 

The print/ghostscript9-agpl-base and print/ghostscript9-agpl-x11 ports was updated to 9.23 version in ports r472239 by tijl@.

Looks like, this fixed issue for this PR. Please test.


It works now with freetype2 - 2.9.1

Pascal Christen <pesc>
Tue 05 Jun 2018 05:47:11 AM UTC, comment #6: 

Any progress here?  How shall I handle this bug report?

Werner LEMBERG <wl>
Group administrator
Sat 05 May 2018 06:54:13 AM UTC, comment #5: 


> I think we're close to a solution


I don't think so.  The proposed patch (i.e., commenting out FT_CONFIG_OPTION_POSTSCRIPT_NAMES) is almost certainly wrong, and it probably has a large impact on other programs.

The level-5 logfile in the attachment of comment #7 (of the FreeBSD bug report) is much shorter than what I get if I use your (slightly modified[*]) script to build and test FreeType with current git, see attachment.  Maybe you have the FREETYPE_PROPERTIES environment variable set, or your FontConfig setup (used by `convert' to access fonts) differs...

Please also create a level-5 logfile with current git.  In particular, in my log file you can find

  FT_Load_Glyph: index 82, flags b

(which gets emitted at tracing level 5) – this has been introduced in FreeType version 2.9, and I would like to see what flag value you get.

[*] Your script starts with `#!/bin/sh', which isn't true.  In particular, you use function names like `foo-bar', which is not portable across different `sh' versions.  It should be rather called `foo_bar', cf.

https://unix.stackexchange.com/questions/168221/are-there-problems-with-hyphens-in-functions-aliases-and-executables


(file #44098,

Werner LEMBERG <wl>
Group administrator
Fri 04 May 2018 07:36:52 AM UTC, comment #4: 

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

Posted a bug on FreeBSD and I think we're close to a solution

Pascal Christen <pesc>
Wed 25 Apr 2018 09:17:52 AM UTC, comment #3: 

I can't reproduce that with neither 2.8, 2.8.1, 2.9, nor the current git version of FreeType (on GNU/Linux).  Both fonts included in the PDF display just fine using ftview.

Using gs 9.23 the PDF gets displayed fine. The `convert' program (version 6.8.8-1 Q16) also works ok.

Can you try to self-compile FreeType, using the git version?

Werner LEMBERG <wl>
Group administrator
Wed 25 Apr 2018 05:57:01 AM UTC, comment #2: 

I need a PDF (unencrypted) or its embedded fonts that I can further analyze.

Werner LEMBERG <wl>
Group administrator
Tue 24 Apr 2018 02:53:32 PM UTC, comment #1: 

pdffonts 1769c3f6ca8a130214b129068f.pdf
name                                 type              encoding         emb sub uni object ID
------------------------------------ ----------------- ---------------- --- --- --- ---------
Type-Regular                   TrueType          WinAnsi          yes no  no      10  0
Type-Bold                      TrueType          WinAnsi          yes no  no      13  0
PLFMPD+Type-Regular            TrueType          WinAnsi          yes yes no      18  0

Anonymous
Tue 24 Apr 2018 02:45:53 PM UTC, original submission:  

Since the update to freetype2 2.9 (from 2.8.1) we're not able to render the embedded pdf fonts correctly to a jpg. We're using imagemagick for rendering but even tried ghostscript with the same result.


Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attached Files
file #44098:  5.txt.wl.xz added by wl (18KiB - application/x-xz)
file #44099:  image.jpg added by wl (9KiB - image/jpeg)
file #44022:  anonyme_visitenkarte.pdf added by pesc (113KiB - application/pdf - Here you go)
file #44006:  Screenshot from 2018-04-24 16-44-16.png added by None (15KiB - image/png - Here you see the output with 2.9 -> Before it was a readable font ;))

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by pesc (Updated the item)
  • -email is unavailable- added by wl (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-06-15 wl StatusNeed Info Invalid
        Open/ClosedOpen Closed
    2018-05-05 wl Attached File- Added 5.txt.wl.xz, #44098
        Attached File- Added image.jpg, #44099
    2018-04-25 pesc Attached File- Added anonyme_visitenkarte.pdf, #44022
    2018-04-25 wl StatusNone Need Info
        Assigned toNone wl
    2018-04-24 None Attached File- Added Screenshot from 2018-04-24 16-44-16.png, #44006

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code