Pierrick Brihaye wrote:
Hi,
It's neither a feature nor a bug. It's simply a gap in the implementation IMO. It really depends on your requirements. If you only have these obsolete fonts that FOP doesn't understand, it is surely worth trying to fix this. You may simply have to determine how much work it will be and if you (!) think it is worth it. We're certainly not going to turn a fix like that down.
The problem is that the fonts are licensed : there are free to use but can't be modified :-( Otherwise, it could have been quite easy to reprocess them in a font utility and, at first, merge them :-)
Remember also that Batik can handle them just because they considered several maps :
Pierrick,
from my point of view I would be interested in seeing the TTFReader and PFMReader modified to consider several maps, beside just unicode. I think such functionality would be very good for FOP.
Changes to layout that you mention in your other post will likely get a -1 from me. I think they will distract from FOP's main objective of getting a working layout that meets the requirements of the XSL-FO spec. I dont believe the layout features you describe are in the XSL-FO spec. You could always write to the XSL working group to voice your requirements, and you never know the features might be added in a future release of the spec.
Thanks,
Chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
