Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.1.2
-
Fix Version/s: 6.3.1
-
Component/s: Core/Rendering, Font Engine
-
Labels:None
-
Environment:All
-
Support Case References:Support Case #13501 - https://icesoft.my.salesforce.com/5007000001JCv5o
-
Workaround Exists:Yes
-
Workaround Description:
Description
When rendering the provided PDF file, the fonts that are shown in bold are rendered very wide. This makes them render out of place on the page.
This issue is only seen when using the Helvetica Bold font. Initially this was substituted for the following: FINE: Font Substitution: Found type1 font: Arial-BoldMT for named font Helvetica-Bold
With the Helvetica-Bold font installed, the issue is reproducible.
This issue is only seen when using the Helvetica Bold font. Initially this was substituted for the following: FINE: Font Substitution: Found type1 font: Arial-BoldMT for named font Helvetica-Bold
With the Helvetica-Bold font installed, the issue is reproducible.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 6.3.1 [ 13113 ] |
It turns out the 6.3.0 release went out with a fairly major bug with regards to widths and encoding. This file has help narrow down what went wrong. The HEB____.TTF is a TrueType-2 font and it's becoming clear that we shouldn't do any c2g work for this sub category of font.
I've also added two public static lists the the FontManager class to make it easier to exclude fonts.
BASE_NAME_EXCLUSION_LIST contains a list of strings representing known base names that are problematic and are ignored if found on the system. These strings are all lowercase.
FONT_FILE_NAME_EXCLUSION_LIST is a list of font names with extension that should be ignored if encountered.
Show
Patrick Corless
added a comment - It turns out the 6.3.0 release went out with a fairly major bug with regards to widths and encoding. This file has help narrow down what went wrong. The HEB____.TTF is a TrueType-2 font and it's becoming clear that we shouldn't do any c2g work for this sub category of font.
I've also added two public static lists the the FontManager class to make it easier to exclude fonts.
BASE_NAME_EXCLUSION_LIST contains a list of strings representing known base names that are problematic and are ignored if found on the system. These strings are all lowercase.
FONT_FILE_NAME_EXCLUSION_LIST is a list of font names with extension that should be ignored if encountered.
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #52314 | Fri Feb 16 10:43:22 MST 2018 | patrick.corless | to the FontManager to allows user to have more control over the setting up excluded names, especially now that we are using preferneces api. Also added a few optimization for excluding. |
| Files Changed | ||||
MODIFY
/icepdf/trunk/icepdf/core/core-awt/src/main/java/org/icepdf/core/pobjects/fonts/FontManager.java
|
Marking as fixed.
Show
Patrick Corless
added a comment - Marking as fixed.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
The font in question has an encoding the renders the glyphs with incorrect widths. I believe the root of the problem is that we apply the encoding defined in the pdf which doesn't match the encoding define in the font. This incorrect matching is causing the font widths to come page incorrectly.