Alexander,
I don't think that relying directly on the ImageIO API is a problem
since it's been part of the core Java class library since Java 1.4. It's
available in all JVMs that claim to be at least Java 1.4 compliant. I
don't really see the benefit in hiding the API behind an additional
layer. I
Hi Jeremias,
On Thu, 2009-09-24 at 21:06 +0200, Jeremias Maerki wrote:
> Right, and that accounts for a pretty large portion of FOP's memory
> consumption problem nowadays. With the use of OpenType fonts, this gets
> worse as they can be quite big. I'm glad you noticed that.
Yes, but currently I
On 24.09.2009 17:53:29 Alexander Kiel wrote:
> Hi,
>
> I currently thinking about the interface to use for reading OpenType
> files.
>
> There are two possibilities:
>
> - reading on top of an InputStream or
> - reading on top of a RandomAccessFile or FileChannel.
>
> Currently the implementa
Ah, I see. Essentially, you're stuck in the case where the IF is loaded
from XML in which case the user agent hasn't received the structure tree,
yet. So, to visualize this:
Direct Rendering:
- Reduced FO tree is built using XSLT and set on the user agent
- DocumentHandler.startPageSequence is cal
Hi,
I currently thinking about the interface to use for reading OpenType
files.
There are two possibilities:
- reading on top of an InputStream or
- reading on top of a RandomAccessFile or FileChannel.
Currently the implementation in FOP uses the class FontFileReader which
expects an InputStr
Jeremias Maerki wrote:
> Not just like that (if at all). The content items being produced inside
> the page-sequence have to be linked into the structure tree. There are
> links (MCIDs) back and forth between the structure tree and the content
> streams. You have to have the structure tree availabl
https://issues.apache.org/bugzilla/show_bug.cgi?id=47872
Max Berger changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
