Had enough of the complaints and fixed it: http://svn.apache.org/viewcvs?rev=366718&view=rev
The change itself is not difficult but it required quite a few changes to many classes because it is a bit invasive. In the end it boiled down to that the FOUserAgent object needed to be carried into the font objects so that when the lazy evaluation tries to read the font metrics or later the PDF or PS renderers want to embed it the URI Resolver set in the FOUserAgent object can be invoked. The FOP font setup is also invoked through various ...Graphics2D classes. To be honest I don't understand that part of the code and just added a null pointer for the new FOUserAgent argument to the font setup. Doesn't seem to have broken anything in our test system. Someone with a better understanding of this area may want to take a look please. I also submitted as part of this patch (made the commit simpler) and new image class (for Java 1.4 only) which encapsulates the existing JpegImage but allows access to the decoded image (need for the AFP Renderer). As far as I can tell this change is completely transparent to the existing Jpeg handling and hopefully will not cause any problems. Manuel
