Name: vuC71690 Date: 01/13/2000

###@###.### 2000-01-13

On Solaris, starting with 1.2.2, the test case below reports identical
values regardless of the font size. The visible manifestation of this
problem is that printing via getPrintJob API prints *all* text at
10pt.

    import java.awt.*;
    
    public class FM {
// Test string used by sun.awt.motif.PSPrintStream
private static final String testString =
"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ 1234567890";
    
static Toolkit tk = Toolkit.getDefaultToolkit();
    
public static void main(String[] args) {
test(8);
test(10);
test(12);
test(20);
System.exit(0);
}
    
private static void test(int size) {
Font f = new Font("Monospaced", Font.PLAIN, size);
FontMetrics m = tk.getFontMetrics(f);
int width = m.stringWidth(testString);

     System.err.println("size = " + size
+ "; width(testString) = " + width
+ "; width('a') = " + m.charWidth('a'));
}
    }


PSPrintStream generates PostScript output as follows (comments are
mine)

    % Set font
    /SF { % javaWidthOfTestString fontSize fontNumber --
      F exch get % get font by index
      exch scalefont setfont % scale to requested size and set the font
      (abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ 1234567890)
      stringwidth pop % get PS width of test string
      div % javaWidth/PSWidth for the test string
      currentfont exch scalefont setfont % adjust fontsize
    } BD

The SF is then invoked like this (from PSPrintStream.outFont)

    int desiredWidth = curMetrics.stringWidth(testString);
    ps.println(desiredWidth+" "+font.getSize()+" "+fontIndex+" "+SetFontName);

    // uwe: e.g.
    //
    // % Font[monospaced, 0, 20]
    // 378 20 8 SF

Since regardless of font size the desiredWidth above (i.e. the width
of the test string) is always the same, SF will always scale font back
to match the (always the same) desiredWidth.

======================================================================

Name: vuC71690 Date: 01/14/2000

###@###.### 2000-01-13

This happens when the display is on a Windows machine running Exceed.
When the display is on a Solaris box everything is ok.

======================================================================