-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
P4
-
Affects Version/s: 7
-
Component/s: client-libs
-
x86
-
windows_7
FULL PRODUCT VERSION :
JVM Version 1.7.0
ADDITIONAL OS VERSION INFORMATION :
Windows 7 64-bit. Although this wouldn't matter.
EXTRA RELEVANT SYSTEM CONFIGURATION :
JVM Version 1.7.0
A DESCRIPTION OF THE PROBLEM :
The createFont function supports Type1 fonts but there is no way
to provide a PFM or PFA file or stream to define the font encoding.
This results in only very partial support for Type 1 fonts since I assume
Java is hardcoded for the Adobe standard encoding.
This limitation is either a bug or it needs to be documented that only
the Adobe Standard Glyph encodind is supported.
It is well understood that a Type 1 font consists of two parts, the PFB file and the PFM/AFP file. Without the PFM/AFM file you can not support font metrics correctly nor can you properly handle font encodings.
What is there now, unless I am missing something is half baked!
I sincerely hope I am missing something!
Thanks.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Try to use any type1 font that uses a font specific encoding.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
none that is reasonable. In some cases it may be possible to convert the
type 1 font to a TTF font which contains the encoding. However this is
not something that can be done on the fly. Reqiures a font utility.
JVM Version 1.7.0
ADDITIONAL OS VERSION INFORMATION :
Windows 7 64-bit. Although this wouldn't matter.
EXTRA RELEVANT SYSTEM CONFIGURATION :
JVM Version 1.7.0
A DESCRIPTION OF THE PROBLEM :
The createFont function supports Type1 fonts but there is no way
to provide a PFM or PFA file or stream to define the font encoding.
This results in only very partial support for Type 1 fonts since I assume
Java is hardcoded for the Adobe standard encoding.
This limitation is either a bug or it needs to be documented that only
the Adobe Standard Glyph encodind is supported.
It is well understood that a Type 1 font consists of two parts, the PFB file and the PFM/AFP file. Without the PFM/AFM file you can not support font metrics correctly nor can you properly handle font encodings.
What is there now, unless I am missing something is half baked!
I sincerely hope I am missing something!
Thanks.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Try to use any type1 font that uses a font specific encoding.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
none that is reasonable. In some cases it may be possible to convert the
type 1 font to a TTF font which contains the encoding. However this is
not something that can be done on the fly. Reqiures a font utility.