Does that mean that PFM/AFM files are not necessary anymore? Do I just need
the PFB, when working with type 1 fonts?
Ulrich
Jeremias Maerki wrote:
Don't bother with XML font metrics files in 0.95 if you don't absolutely
need to. FOP 0.95 should handle Symbol and ZapfDingbats reasonably well
without a separate font metrics file if you configure them explicitely.
In the unlikely case, that it doesn't work without XML font metrics
files: yes, you'd have to replace it with "ZapfDingbatsEncoding".
Otherwise, FOP will work off the wrong encoding.
Off topic: I wonder how many more times we're going to mention that XML
font metrics are more and more unnecessary. When we started with those
it was a necessary evil to make custom fonts work. And now, everybody is
so used to do this tedious and annoying step that it's difficult to get
everyone back to a more intuitive approach, i.e. a simpler life. I can't
help but be amused about this. ;-) I guess we should consider adding a
big disclaimer to PFM/TTFReader stating that these tools will soon be
obsolete. Any other ideas?
On 09.01.2009 10:52:53 Ulrich Mayring wrote:
In FOP 0.94 there is documentation with respect to Dingbats fonts, that the
PFMReader writes "UnknownEncoding" to the metrics file. This has to be
replaced with SymbolEncoding or ZapfdingbatsEncoding.
The PFMReader from FOP 0.95 now writes WinAnsiEncoding for the URWDingbats
font to the metrics file. Is this ok or do I also need to replace that with
ZapfdingbatsEncoding?
Ulrich
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
