17 Nov 2000,  xxxxx@xxxxx  -- see also # 4219697 (only TrueType was added)
----------------------------
The 1.3 version of the Font class has a static method called createFont() that
accepts a fontFormat parameter and an InputStream.  Currently only TrueType
fonts are supported by this API (fontFormat == TRUETYPE_FONT).

Support for Adobe Type 1 font rendering should be included in the 1.4 version.
This should be able to support partial fonts as well as complete fonts so that
documents with embedded fonts and partially embedded fonts can be rendered in
Java.
(Review ID: 112468) 
======================================================================

Copy your Type1 fonts into $JREHOME/lib/fonts.
They'll automatically get picked up along with the TrueType fonts in there that
ship with the JRE. They'll then be "installed fonts" - no need to use 
Font.createFont(..) - just use new Font(..).
This may not work for everyone but it should work for many cases.

 xxxxx@xxxxx  2001-08-14
============================

This definitely won't be in merlin. 

 xxxxx@xxxxx  2001-07-31
=========================

For tiger (1.5) the implementation and spec has been updated to accept
 Font.TYPE1_FONT.

It should also support Adobe Type 1C fonts (the "C" is for 
Compact).  This will allow rendering of fonts that are 
embedded in, for example, PDF files.

Java not supporting Type 1 font is some lame man.

Some document formats, such as PDF, have embedded Type 1
fonts, for which this capability is essential.  Also, it's
nice to be able to package fonts with an application and not
have to install them in the OS.  Note that tolls for
converting Type 1 to TrueType are generally lousy, dropping
hinting for example.

If unicode mappings are a reason for not adding them, then 
let us pass a mapping of unicode to postscript names... 
Give us something to work with!!

If load-time support is already there then it cannot be 
much more work to add run-time support.  Come on Sun; this 
is important if you want any serious platform independent 
Java programs that deal with documents.

When additional type1 functionality is added, how about 
also adding the option of using post table character 
referencing in addition to unicode for all font types.  
Since reference by post name is necessary for accessing 
glyphs in type1 anyway, why not give us the ability draw 
characters by passing post names?  That would give 
developers the ability to handle custom encodings and would 
also give us the ability to easily get around the current 
problems with symbol ttf fonts.

i've tried the workaround... doesn't work. really need java to 
implement this soon.