On 04/04/12 18:02, Vincent Hennebert wrote:
> Hi Craig,
>
> Thanks for your extensive study!
>
> On 03/04/12 10:31, Craig Ringer wrote:
>> On 03/04/12 01:16, Vincent Hennebert wrote:
>>
From a quick look that sounds about right. Are you developing with a 1.7
JDK?
You would have to m
Hi Craig,
Thanks for your extensive study!
On 03/04/12 10:31, Craig Ringer wrote:
> On 03/04/12 01:16, Vincent Hennebert wrote:
>
>>> From a quick look that sounds about right. Are you developing with a 1.7
>>> JDK?
>>> You would have to make your code 1.5-compatible. Also, it would be good if
On 03/04/12 01:16, Vincent Hennebert wrote:
>> From a quick look that sounds about right. Are you developing with a 1.7 JDK?
>> You would have to make your code 1.5-compatible. Also, it would be good if
>> you could back your optimizations with profiling data. If code
>> safety/readability have to
Hi Craig,
On 30/03/12 01:23, Craig Ringer wrote:
> On 03/30/2012 05:09 AM, J.Pietschmann wrote:
>> Am 29.03.2012 01:24, schrieb Craig Ringer:
>>> I'd also like to have getEncodedName() return a byte[] not a
>>> String, since an encoded PDF name isn't actually text data.
>> Sounds like a reasonable
Am 30.03.2012 02:23, schrieb Craig Ringer:
> Given the number of these kinds of issues in fop's pdf library I'm more
> and more inclined to wonder if it should just be replaced with PDFBox.
This has already been proposed, and there is a general agreement this
would be one of the better ways to pro
On 03/30/2012 05:09 AM, J.Pietschmann wrote:
Am 29.03.2012 01:24, schrieb Craig Ringer:
I'd also like to have getEncodedName() return a byte[] not a
String, since an encoded PDF name isn't actually text data.
Sounds like a reasonable idea.
BTW, is there any reason Fop's PDF library uses java.
Am 29.03.2012 01:24, schrieb Craig Ringer:
> I'd also like to have getEncodedName() return a byte[] not a
> String, since an encoded PDF name isn't actually text data.
Sounds like a reasonable idea.
> BTW, is there any reason Fop's PDF library uses java.lang.String when
> working with sequences o
Hi all
I've been working with PDFName in my code and have run into a bit of an
oddity I was hoping for comments on.
For any given string `fred', the operation:
( new PDFName(fred) ).getName().equals(fred)
isn't guaranteed to be true, because PDFName.getName() returns the
*escaped* name.
