-
Bug
-
Resolution: Fixed
-
P3
-
1.3.0
-
None
-
beta
-
x86
-
windows_nt
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2038301 | 1.4.0 | Philip Race | P3 | Resolved | Fixed | beta |
This bug can be seen on win32 on kestrel (J2SE1.3) and internal merlin builds.
"This problem is related to using custom TrueType fonts which are
loaded through Font.createFont(Font.TRUETYPE_FONT, inputStream). When we print the JFrame using the PrinterJob class, the components in the
printout appear to be using altogether different fonts which make it
look ugly. The screen display however uses the truetype fonts correctly.
The print problem disappears when those fonts are manually put in the
C:\WindowsNT\Fonts directory. The above story happens on a PC.
The same print-out when taken from a Sun workstation, appears to
behave perfectly well (with the right fonts) irrespective of whether
those fonts are installed on the machine or not."
Test case attached.
"This problem is related to using custom TrueType fonts which are
loaded through Font.createFont(Font.TRUETYPE_FONT, inputStream). When we print the JFrame using the PrinterJob class, the components in the
printout appear to be using altogether different fonts which make it
look ugly. The screen display however uses the truetype fonts correctly.
The print problem disappears when those fonts are manually put in the
C:\WindowsNT\Fonts directory. The above story happens on a PC.
The same print-out when taken from a Sun workstation, appears to
behave perfectly well (with the right fonts) irrespective of whether
those fonts are installed on the machine or not."
Test case attached.
- backported by
-
JDK-2038301 Java2D Printing: fonts not in win32 font directory print incorrectly.
-
- Resolved
-