https://issues.apache.org/bugzilla/show_bug.cgi?id=52290
--- Comment #4 from Craig Ringer ring...@ringerc.id.au 2011-12-15 07:20:48
UTC ---
It turns out that the manual font definitions are not required. A regular
directory scan for fonts will add the fully qualified face name as a fake
family
https://issues.apache.org/bugzilla/show_bug.cgi?id=52289
--- Comment #3 from Craig Ringer ring...@ringerc.id.au 2011-12-15 07:25:17
UTC ---
This looks like it might be partly by design.
It seems fop registers a font more than once. It'll register the most
preferred face for a family under the
https://issues.apache.org/bugzilla/show_bug.cgi?id=52290
--- Comment #5 from Craig Ringer ring...@ringerc.id.au 2011-12-15 07:25:44
UTC ---
Please flag as importance: Enhancement
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this
https://issues.apache.org/bugzilla/show_bug.cgi?id=52289
--- Comment #4 from Craig Ringer ring...@ringerc.id.au 2011-12-15 07:26:33
UTC ---
Please flag as importance: enhancement
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this
https://issues.apache.org/bugzilla/show_bug.cgi?id=52338
Bug #: 52338
Summary: Fop doesn't handle CID TrueType fonts in PostScript
output
Product: Fop
Version: 1.0
Platform: PC
OS/Version: Linux
