dynamically, but identical fop xml
works fine when sent straight to serializer
Thanks Antonio,
I think that may be the problem (I then installed netscape
and it worked fine) - I'll check my browser when I'm on my
work machine tomorrow.
cheers again,
James
--- Antonio Gallardo Rive
Try to send a response with a clear PDF extension. Example:
foo.pdf.
I had this problem before with MSIE 6.0 SP1 and it corrects the error. Have a
nice xsl-fo coding :-D
Antonio Gallardo.
El Jueves, 24 de Octubre de 2002 08:47, Ryan Agler escribió:
> I played around with fo for the first time y
Thanks Antonio,
I think that may be the problem (I then installed netscape
and it worked fine) - I'll check my browser when I'm on my
work machine tomorrow.
cheers again,
James
--- Antonio Gallardo Rivera
<[EMAIL PROTECTED]> wrote: > Try to send a
response with a clear PDF extension.
> Example:
>
Cheers Robert (I'll test that out tomorrow - am away from
my dev machine now - although another test described below
seems to suggest that my Cocoon installation is fine.)
Earlier I decided to load the page in netscape 6 instead -
it worked, switch back to IE 6 - doesn't work.
Has anybody else ex
I played around with fo for the first time yesterday and ran into the
same thing. Turns out if I enclosed everything after with an , and then also enclosed
anything within an fo:cell with things worked out fine.
-Original Message-
From: James Ashton [mailto:jamesashton@;yahoo.com]
James,
Ran into something similar...this may help: Make sure that the fop JAR
file version inside Cocoon is the same as the one you use when you
serialize. I had fop-0.20.4.jar running from the command line and
fop-0.20.3.jar running inside Cocoon and noticed some anomalies.
Hope this helps!
