Opened 13 years ago
Closed 12 years ago
#3924 closed defect (fixed)
AGG renderer fails to render some truetype symbols
Reported by: | dmorissette | Owned by: | dmorissette |
---|---|---|---|
Priority: | normal | Milestone: | 6.0.1 release |
Component: | AGG | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: | tbonfort |
Description
I have encountered a truetype symbol file that used to render properly with GD drivers but no longer works with the AGG renderer (both in 5.6 and 6.0).
It turns out that there was a hack in GD's gdImageStringFTEx() (gdft.c) for the FT_ENCODING_MS_SYMBOL charmap that we may need to port to the AGG renderer in order to properly support these symbols.
I will attach a patch that solves the issue for me. (Unfortunately I cannot attach my testcase, sorry)
Attachments (1)
Change History (4)
by , 13 years ago
Attachment: | agg_ttf_symbols.patch added |
---|
comment:1 by , 13 years ago
I see that GD's gdImageStringFTEx() has support for more charmap encodings. Do we need to support all of them?
comment:2 by , 13 years ago
Also note that the proposed patch intentionally checks for FT_ENCODING_MS_SYMBOL before FT_ENCODING_APPLE_ROMAN because if both encodings are present (as was the case in my testcase) then we want to use FT_ENCODING_MS_SYMBOL in priority.
Patch against SVN trunk