|Evolution Programming Resources
Listing 1 shows a small fraction of the rendering code of a component.
If you execute the code on MacOS X and compare the rendered text with the result of a native program rendering the same text using the same font you'll get a totally identical result.
If you try the same on Windows (Sun JRE 1.3.1) you will get totally different results. Java renders the font far smaller than the native code.
The is a result of the different screen resolution assumed by Java 2D and Windows. While Java assumes 72 dpi screen resolution Windows uses 96 dpi or 120 dpi depending on your font size setting in the display properties.
To provide resolution independent rendering Java 2D API supplies the
method in the
GraphicsConfiguration class. Applying the returned transformation to the
Graphics context should produce the same results a the native windows rendering code.
But unfortunately this method returns always a identity transformation if it is called for the screen device.
So instead of using
getNormalizingTransform() you have to use
Toolkit class and the calculate the correct font size as shown in listing 2.
The code in listing 2 creates almost the same results as the native Windows font rendering. But if you take a closer look you will notice slight differences in kerning and antialiasing. It seems that Java 2D is using its own font renderer instead of the native implementation on Windows.
An alternative solution would be to create a
AffineTransform scaling by the factor
screenRes / 72.0.
The advantage of that solution would be that the transformation allows scaling by fractional numbers while the
class doesn't support fractional font sizes. In reality the results of both solutions are identical. Also the same font size
correction as shown in listing 2 can be used in Java 1.1 code since it doesn't rely on any Java 2D features.