nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Publish PDFs on generation

Amanda_J_0204

We are attemting to set our DCTs to publish content in PDF format, as an alternative to Visual Annotate since some of our users have Macintoshes and Visual Annotate is not supported on anything other than Internet Explorer.

Does anyone generate PDFs? If so, what technologies do you use? I've looked at this thread (http://devnet.interwoven.com/forums_vb/showthread.php?t=27800&forumid=11&highlight=Adobe), but was wondering if anyone is using xsl-fo with FOP (or similar product), and this is working successfully for you?

Since I don't have direct access to our servers (Windows 2003), I'd prefer to approach our sysadmins with a solution that has worked elsewhere.

We are running Interwoven TeamSite 6.7.2.0, Build Number: 69626

Find more posts tagged with

Comments

nipper

I have, in the 5.5 time frame used FOP within a TPL.

Now how that would work with XSLT, I have no idea.

I doubt there are too many people doing this, so you may be on your own.

Now why you need PDF is also a question. PDF will not give you the visual annotate functionality, so I am unclear why you are trying this. There certainly are valid use cases, again I just do not understand yours.

vpatel

I have, in the 5.5 time frame used FOP within a TPL.

Now how that would work with XSLT, I have no idea.

This is doable in XSL as well. Please search for XSL-FO (Formatting Objects). Here is sample reference link: http://www.xml.com/pub/a/2001/01/17/xsl-fo/index.html

Adam Stoller

PDF will not give you the visual annotate functionality

There are a number of PDF tools (Adobe or Apple's Preview among them) that allow for annotation of PDF documents (notes, highlighting, etc.) that would provide the kind of functionality that VisualAnnotate does in a multi-platform manner.

Of course, if you're on a Mac, you could generate a PDF of any page you wanted, mark it up and then import it into TeamSite or send it via email or something to show someone what you want modified... or take screen shots (JPG, TIFF, etc.) and mark them up and send those along and do the same thing...

nipper

Of course, if you're on a Mac, you could generate a PDF of any page you wanted, mark it up and then import it into TeamSite or send it via email or something to show someone what you want modified... or take screen shots (JPG, TIFF, etc.) and mark them up and send those along and do the same thing...

Of course if you are on a Mac then you do not have any money left over to buy software since you spent 3 K on a 2GB system and now you carry your lunch to work every day.

Smiley Very Happy

Not that I want to start a Mac/PC war.

Jamik

Of course if you are on a Mac then you do not have any money left over to buy software since you spent 3 K on a 2GB system and now you carry your lunch to work every day.

Not that I want to start a Mac/PC war.

well if you bought a mac then you already own all the software needed to do this Smiley Wink

not that you wanted to start a mac/pc war

Amanda_J_0204

I have, in the 5.5 time frame used FOP within a TPL.

Now how that would work with XSLT, I have no idea.

I doubt there are too many people doing this, so you may be on your own.

Now why you need PDF is also a question. PDF will not give you the visual annotate functionality, so I am unclear why you are trying this. There certainly are valid use cases, again I just do not understand yours.

Thanks, Nipper. Did you have the TPL produce the output in the appropriate xsl-fo format? And, I applologize for being a noob but, how was the xsl-fo formated file accessed by FOP?

To answer your question: There are a few individuals who need a standardized way of marking up changes for LOTS of users who use different browsers and platforms. The annotating tools built into Adobe Reader/Acrobat would serve this purpose. As much as I'd like to ask everybody to use IE on a PC, it's not really an option.

nipper

No I do not have a copy, this was 5 years ago and if I did it would not help much if you are using XSLTs instead of TPLs.

Amanda_J_0204

No I do not have a copy, this was 5 years ago and if I did it would not help much if you are using XSLTs instead of TPLs.

At the moment, we're using TPLs. Was just wondering if the TPL was producing the xsl-fo formated file? And if this was a problem, since I thought there wasn't a lot of support for XSLT in Interwoven yet.

osgi-error.png

nipper

At the moment, we're using TPLs. Was just wondering if the TPL was producing the xsl-fo formated file? And if this was a problem, since I thought there wasn't a lot of support for XSLT in Interwoven yet.

You certainly can use an XSLT. That is supported and has been for a couple years.

My TPL basically generated a temp HTML file, then ran a system call starting FOP to create the PDF.

Amanda_J_0204

I'm now at a point where I'm using a .NET version of FOP (NFOP) to take an XML DCT file generated by Teamsite, parse it using an XSL file, and save a PDF. However, because the XML is well formed, the html within it looks like this:

Some text here bolded text</strong&ampgt;

So in the PDF, this gets converted to:

Some text here bolded text

The people who need to do reviews don't know html and won't want to see this extra code.

I've tried using Saxon to parse through this particular bit of code, but errors display. I've learned via Google that Saxon and NFOP require the inclusion of their respective libraries (ApacheFop.Net.dll and IKVM.GNU.Classpath) but these libraries have an overlap in the form of org.xml.sax.

Does anyone use any particular parser to convert encoded xml as specified above into the appropriate characters?

example.zip

Adam Stoller

In your XSL file - when you use

<xsl:value-of ...>

do you use the attribute

disable-output-escaping="yes"

?
If not, try doing so and see if that solves your problem.

Amanda_J_0204

In your XSL file - when you use
<xsl:value-of ...>
do you use the attribute
disable-output-escaping="yes"
?
If not, try doing so and see if that solves your problem.

I've tried this; it completely removes all content from the area with

<xsl:value-of ...>

where

disable-output-escaping="yes"

is used.

vpatel

Have you tried <xsl:copy-of select="..."/>? Try it with/without the disable-output-escaping="yes" option. That may help.

Amanda_J_0204

Have you tried <xsl:copy-of select="..."/>? Try it with/without the disable-output-escaping="yes" option. That may help.

I just tried this, it prevented any of the content from displaying.

When I tried:

<xsl:copy-of select=".//Content" disable-output-escaping="yes" />

XMLSpy told me:
File

\My Documents\Visual Studio 2005\WebSites\FOP\testfo.xsl is not valid.
Unexpected attribute
disable-output-escaping="yes"

Amanda_J_0204

Almost every resource I've looked at says I need to parse the xml twice in order to get the affect I need, and I can't use Saxon for reasons stated previously...

Would anyone know of a way to sent JUST ONE or maybe TWO nodes from an XML file to be parsed by iwpt_compile.ipl or any other parser used by Teamsite?