6 Sep
2007
6 Sep
'07
4:43 p.m.
An interesting result... pdf's generated in this method cannot be
printed (print flag set to false I guess). How do I tell it to allow
printing?
________________________________
From: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org] On Behalf
Of Vincent Massol
Sent: 06 September 2007 13:44
To: XWiki Users
Subject: Re: [xwiki-users] PDF on 1.1RC1
On Sep 6, 2007, at 2:21 PM, Esbach, Brandon wrote:
Browser: Firefox
OS: WindowsXP
The save/view dialog was there for 1.0B4; only since RC1 is it
no longer a dialog. I saw a note somewhere about this a while back (I
think), just can't recall if it was for PDF or RTF.
I don't know or recall anything about that. However it's working fine
for me (I'm on Mac/Firefox).
-Vincent
________________________________
From: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org]
On Behalf Of Vincent Massol
Sent: 06 September 2007 13:19
To: XWiki Users
Subject: Re: [xwiki-users] PDF on 1.1RC1
On Sep 6, 2007, at 1:56 PM, Esbach, Brandon wrote:
Hi Vincent;
That worked perfectly. Minor thing, the PDF opens into
the browser instead of the origional save/view option (most of my users
prefer saving the pdf instead of viewing it) - is this optional, or the
new way that it works?
I still don't know what we have changed as I don't recall any
change since 1.0 that would have affected this behavior (but everything
is possible).
On my machine I have the dialog box asking for saving or viewing
the PDF...
What browser/OS are you using?
Thanks
-Vincent
Current environment:
Using the following:
Tomcat 5.5.17
JDK: 1.5.0 build4
xerces jar on the lib folder: xercesImpl-2.0.2.jar
Not aware of any other xerces jar's in use; but it's
possible.
________________________________
From: Vincent Massol [mailto:vincent@massol.net]
Sent: 06 September 2007 12:37
To: Esbach, Brandon
Subject: Re: [xwiki-users] PDF on 1.1RC1
Brandon,
Could you try this new jar? It should work fine although
I'm not sure why... ;)
What JDK are you using on that machine? What container
too? Maybe there's another xerces jar that gets picked up that has a
slightly different behavior...
Thanks
-Vincent