Analysis of source code of current product shows
some some calls to setFont that hardcode a certain
font
size that isn't relative to global font size.

Usually, fonts are obtained from the global font
size
value of the product. But if specific font sizes
are needed, they should be assigned based on a
relative
offset from the default font size instead of as a
specific
size.

This is because the localized products will soon
be able to
set the default font size needed for proper
appearance
of their character sets, and hardcoded fonts may
be too
small for meeting those requirements.

If there are other parts of code where hardcoded
font size
might be set other than setFont, can you also
review
that ?
Issue will be marked with FONTSIZE keyword which
means it 
will not be placed on dashboards for 3.5 or nevada
as
needing waiving but fixes still need to be for the
ML
release of 3.5 and Nevada.


Specific calls to setFont seen in source code:

titleLabel.setFont(new java.awt.Font ("Dialog", 1,
11));  /
/ NOI1
8N
textArea.setFont(new java.awt.Font ("Dialog", 0,
11));// NO
I18N
aboutTextArea.setFont(new java.awt.Font("Dialog",
0, 11));
iconLabel.setFont(new java.awt.Font("Dialog", 1,
11));
jTextArea1.setFont(new java.awt.Font("Dialog", 0,
11));
iconLabel.setFont(new java.awt.Font("Dialog", 1,
11));
descTextArea.setFont(new
java.awt.Font("Monospaced", 0, 12)
);
titleLabel.setFont(new java.awt.Font ("Dialog", 1,
11));
textArea.setFont(new java.awt.Font ("Dialog", 0,
11));
licenceTextArea.setFont(new
java.awt.Font("Monospaced", 0,
12));
jTextArea1.setFont(new java.awt.Font("Dialog", 0,
11));
jTextArea.setFont(new java.awt.Font("Dialog", 0,
11));
textLabel.setFont(new java.awt.Font("Dialog", 1,
11));