SVG/SVG inclusion issue ?

2002-06-11 Thread Dominique Broeglin

Hello,

I'm not sure this is a bug, so this is half a bug report half a request
for help. I use fop 20.3rc
I've a fle a.svg:
svg width=100 height=50
  g id=test
...
  /g
/svg

A second file b.svg:

svg xmlns:xlink=http://www.w3.org/1999/xlink; 
 width=500 height=500
  image xlink:href=file:retro.svg x=80 y=130 width=100
height=50/
/svg

When I vizualize the file with batik (or batik rasterizer) I obtain b
including a. So far so good. Unfortunately then I try to include b.svg
in c.fo with: fo:external-graphic src=file:b.svg/. 

The resulting PDF contains the schema in b.svg, but a the place of a.svg
in b.svg I've an icon representing a broken image. Is this normal
behaviour ?

Cheers,
Dom









-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: SVG/SVG inclusion issue ?

2002-06-12 Thread Dominique Broeglin

On Tue, 2002-06-11 at 22:35, J.Pietschmann wrote:
 
 No. Batik, the SVG rasterizer, either cannot find the referenced file or
 it cannot decode its format.
 Point 1: file:b.svg is, technically, an invalid URL. FOP tries to cope
 with it, but Batik has it's of logic. Use b.svg or a full path
 file:///path/to/b.svg. In the first case, all three files a.svg, b.svg
 and c.fo should be in the current directory.

   b.svg does not work. By the way, I took the file:b.svg syntax from
the external.fo file in the FOP svg examples ;-)

 Point 2: Neither of the code snippets you show has the SVG namespace
 declared as default namespace. The usual way is that this is done in
 the SVG DTD. Check whether both files either include a proper DOCTYPE
 declaration pointing to the DTD, or declare the SVG namespace.

The SVG namespace was declared, I'm sorry for the rather poor code
examples I submited. When I add the doctype, it works. But I was not
aware the doctype was mandatory, is it ?
What confuses me is the fact that batik reads b.svg correctly but FOP
doesn't. But FOP delegates SVG handling to batik... Could you explain me
if it's normal behaviour ?

 Point 3: Your b.svg links retro.svg, not a.svg.
 

cf. pt 2

 J.Pietschmann

Thanks a lot for your help,
Dom


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]