On Tue, 25 Sep 2001 22:40:32 Thomas E Deweese wrote:
Thanks for working with me on this...
I think I have tracked it down to a bug in the way BufferedImage
handles properties (see attached Java file for demonstration).
So I guess I'll bend an put in the 'instanceof' check
George,
george moudry wrote:
Hello Batikers, I am playing with w3.org's sample file
http://www.w3.org/Graphics/SVG/Test/20010127/interact-bubble-BE-04.html
and have a question regarding the batik code.
Every time I move my mouse over an object with an
g onmouseover=bubbleYes(evt,
deweese 01/09/26 05:40:51
Modified:sources/org/apache/batik/util ParsedURL.java
ParsedURLDefaultProtocolHandler.java
test-resources/org/apache/batik/util regBase64.xml
regParsedURL.xml
Log:
1) Removed tests with
KL == Keiron Liddle [EMAIL PROTECTED] writes:
KL Hi again, As you might guess this problem is related to the
KL previous broken link problems.
KL It appears in line 469 in ParsedURL that if the specified url on
KL the element eg: use xlink:href=file:ref.svg#FOP
KL transform=scale(1.5) x=18
On Wed, 26 Sep 2001 14:47:33 Thomas E Deweese wrote:
I implemented this, but I was unable to track down the definitive
reference on relative URI's, does anyone know where that is?
I am particularly interested in what should be done if protocols
differ between parent and child URIs
deweese 01/09/26 07:49:58
Modified:sources/org/apache/batik/util
ParsedURLDefaultProtocolHandler.java
test-resources/org/apache/batik/util regParsedURL.xml
Log:
1) Cleaned up last remaining corner cases in relative URL parsing.
2) Added
KL == Keiron Liddle [EMAIL PROTECTED] writes:
KL On Tue, 25 Sep 2001 22:40:32 Thomas E Deweese wrote:
[...] for some reason you are hitting the default broken-link
handler instead of the SVG broken link handler. [...]
KL I've found out where the problem is. The BrokenLink.svg is
KL
