Return to Jive Software

Skip navigation
Up to Discussions in Support
1,567 Views 4 Replies Last post: Apr 3, 2009 11:45 AM by mjacobsen RSS
wolfpack Beginner
wolfpack
361 posts since
Apr 6, 2007
Currently Being Moderated

Jan 21, 2009 12:39 PM

Better control of PDF output?

Is it possible to have more control over the way wiki content is rendered as a PDF?  We'd like to put custom headers, footers, and other personalized touches to our environment.  Is there any way to do this?  I found the FOP XSL file in clearspace.jar, but am wondering if there's a friendlier way to customize things?  Also, would it be possible to have different PDF conversion templates for different documents/spaces/projects/etc?

 

Thanks,

Andy

Tags: clearspace, custom, customization, export, configuration, pdf, conversion
vinh.jones Jive Employee
vinh.jones
15,389 posts since
Apr 1, 2008
Currently Being Moderated
Jan 22, 2009 11:56 AM in response to: Andy Goldstein
Re: Better control of PDF output?

Hey Andy,

 

Unfortunately, the FOP XSL is the only way to be customizing your PDF output. There is currently no way of creating PDF conversion templates for different content types, though this might be possible through heavy customization.

 

Thanks,

Vinh

Steve.Vereecke Novice
Steve.Vereecke
18 posts since
Mar 10, 2009
Currently Being Moderated
Mar 31, 2009 3:12 AM in response to: Vinh
Re: Better control of PDF output?

Hi,

 

Have the pdf options in SBS 3.0 been changed? or is it still limited?

vinh.jones Jive Employee
vinh.jones
15,389 posts since
Apr 1, 2008
Currently Being Moderated
Mar 31, 2009 8:45 AM in response to: Steve.Vereecke
Re: Better control of PDF output?

There have been no major changes to PDF output for SBS.

mjacobsen Novice
mjacobsen
56 posts since
Feb 24, 2009
Currently Being Moderated
Apr 3, 2009 11:45 AM in response to: Vinh
Re: Better control of PDF output?

Seems like a useful start would be to pull the file out of the JAR like the other page templates so customizing the PDF output does not require ripping apart the JAR. I haven't done this yet, I suspect if we go down this route, it will need to be redone after every upgrade.

 

Mike

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.