Hi Alexander,
Alexander Kiel wrote:
> Hi Vincent,
>
>> I see. I had in mind to use OpenTypeDataInputStream as the common
>> interface. It actually makes sense to use ImageInputStream instead.
>> Simpler and just as flexible. That will add a direct dependency on
>> a class in the javax.imageio pac
Hi Vincent,
> I see. I had in mind to use OpenTypeDataInputStream as the common
> interface. It actually makes sense to use ImageInputStream instead.
> Simpler and just as flexible. That will add a direct dependency on
> a class in the javax.imageio package, but this is not a problem as it is
> pa
Hi Alexander,
Alexander Kiel wrote:
> Hi Vincent,
>
Here are my two cents: if you make use of classes in javax.imagio at
only one place in your font library, then there’s no need to worry about
creating a more neutral layer. If OTOH you need to use those classes
everywhere, th
Hi Vincent,
> >> Here are my two cents: if you make use of classes in javax.imagio at
> >> only one place in your font library, then there’s no need to worry about
> >> creating a more neutral layer. If OTOH you need to use those classes
> >> everywhere, then it makes sense to use a simplified abs
Hi Alexander,
Alexander Kiel wrote:
> Hi Vincent,
>
>>> I had a look at SeekableStream and I can imagine how the needs resulted
>>> in the ImageInputStream interface. I haven't decided yet if I should use
>>> ImageInputStream directly. Maybe someone else can throw it's two cents
>>> in here.
>> H
Hi Vincent,
> > I had a look at SeekableStream and I can imagine how the needs resulted
> > in the ImageInputStream interface. I haven't decided yet if I should use
> > ImageInputStream directly. Maybe someone else can throw it's two cents
> > in here.
>
> Here are my two cents: if you make use o
Hi Alexander,
Knowing just about nothing of font file formats and libraries, I’ll play
the ignorant guy asking naive questions, hoping that it might give you
good ideas.
Alexander Kiel wrote:
> Hi Jeremias,
>
> On Fri, 2009-09-25 at 08:37 +0200, Jeremias Maerki wrote:
>> I don't think that rely
Hi Jeremias,
On Fri, 2009-09-25 at 08:37 +0200, Jeremias Maerki wrote:
> 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 re
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
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
12 matches
Mail list logo
