Re: basic-link
Chris, Take a look at the example here: http://marc.theaimsgroup.com/?l=fop-devm=106588921514459w=2 Perhaps it should be: external-destination=http://www.yahoo.com; instead of the url() function you used below for this attribute in the fo:basic-link. HTH, Glen --- Chris Faulkner [EMAIL PROTECTED] wrote: Hello I am having problems with fo:basic-link I use it as shown below. When you hover over the link in the resulting PDF, the link includes a load of garbage characters after the .com. Am I doing something wrong ? ARe there any alternatives for embedding a link in my PDF ? fo:table-cell display-align=center fo:block line-height=14pt font-size=9pt fo:basic-link external-destination=url('www.website.com') color=#99Visit us here www.website.com /fo:basic-link /fo:block /fo:table-cell Thanks Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: basic-link
Yes - I am using encryption :-( I have some experience of iText but I moved away from it in favour of XSL:FO and FOP. I don't fancy doing post-processing - I'll wait for the fix. Thanks Chris Are you using encryption? Afraid this is causing the garbage chars... ? ARe there any alternatives for embedding a link in my PDF ? PDF Encryption is working in 1.0 dev, but the latest I heard was basic-links aren't so... Have a look at http://xml.apache.org/fop/output.html#pdf-postprocess With iText, you can easily add a hyperlink at some absolute position on a page generated by FOP. Hope this helps! Greetz, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: basic-link
-Original Message- From: Chris Faulkner [mailto:[EMAIL PROTECTED] Yes - I am using encryption :-( I have some experience of iText but I moved away from it in favour of XSL:FO and FOP. I don't fancy doing post-processing - I'll wait for the fix. Right you are! Same here... A little experience with iText, but since FOP supports encryption and the producer / author / title props, I have seen little use for iText. Thx for the vote of confidence (in FOP that is :) ). Greetz, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: basic-link
-Original Message- From: Chris Faulkner [mailto:[EMAIL PROTECTED] I am having problems with fo:basic-link I use it as shown below. When you hover over the link in the resulting PDF, the link includes a load of garbage characters after the .com. Am I doing something wrong Are you using encryption? Afraid this is causing the garbage chars... ? ARe there any alternatives for embedding a link in my PDF ? PDF Encryption is working in 1.0 dev, but the latest I heard was basic-links aren't so... Have a look at http://xml.apache.org/fop/output.html#pdf-postprocess With iText, you can easily add a hyperlink at some absolute position on a page generated by FOP. Hope this helps! Greetz, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Basic-link problem in JSPs
First of all: Thank you very much for your help! fo:basic-link internal-destination=addressListHeading fo:page-number-citation color=blue ref-id=addressListHeading/ /fo:basic-link This is the real problem. You probably noticed that the link area is not the whole page number, in particular with multiple digit page numbers. Yes, that is right. I will follow your advise and use the headline text as link area. Your style sheet appear to be a bit more convoluted than usual. Some other hints: xsl:template match=address_list/row/* mode=address_list xsl:choose xsl:when test=local-name()='ZIP_CODE_CITY' xsl:call-template name=plzOrtRow If this comes directly from your original style sheet, you should better use matching precise templates instead of piping everything into a match-all and then use a choose in it. Is this just a matter of style or do exact templates perform better? There is not all that much value in abstracting really low-level stuff like table cell generation. Hm, I generate quite a lot of cells (the document contains only tables) and thought that a template for generating cells would reduce filesize and improve readability of the stylesheet. Thanks for your hints!!! Ralf
Re: Basic-link problem in JSPs
Ralf Steppacher wrote: If this comes directly from your original style sheet, you should better use matching precise templates instead of piping everything into a match-all and then use a choose in it. Is this just a matter of style or do exact templates perform better? A matter of robustness and maintainability. Just add templates instead of adding when-clauses, perhaps with ever more intricate conditions. In general, templates are slower but there is rarely a mesurable difference (you need hundreths of matching tamplates). Hm, I generate quite a lot of cells (the document contains only tables) and thought that a template for generating cells would reduce filesize and improve readability of the stylesheet. The verbose call-template syntax doesn't reduce the filesize either, and named template invocations can really hide what's going on. But it's your choice. Try both on a small part and see what fits you better. J.Pietschmann
Re: Basic-link problem in JSPs
Ralf Steppacher wrote: OK, I got rid of all the d-o-e. But the basic-links still are not present in the pdf generated by the embedded FOP but are if the .fo document is dumped to a file and then rendered using FOP from commandline. Can you post a trimmed down version of your source XML and the style sheet which demonstrates the problem? J.Pietschmann
Re: Basic-link problem in JSPs
Ralf Steppacher wrote: Are you, by any chance, using disable-output-escaping somewhere? Yes, but somewhere else in the stylesheet producing the fo document. It doesn't matter where. Do not use d-o-e if you expect your style sheet to work with short-circuit XSLT processor applications. XSLT doesn't del with tags, it uses a tree of nodes for input and output. What you think of as creating single tags is still plain text until serialization. A serialization never happens if the result is fed right into the XML consumer by using a DOM tree or a SAX event stream. Behaviour does not change if I comment out the two lines (that do not work with embedded fop either). If you delete the d-o-e stuff, dump the tree and check with the command line application, what happens? J.Pietschmann
Re: Basic-link problem in JSPs
Ralf Steppacher wrote: I transform a xml file and add FO vocabulary, generating a PDF with fop afterwards. Now that I got it work using xalan and fop from the command line I embedded both into a JSP and a bean following the example code from docs/examples/embedding. The problem: When I generate the PDF with the JSP my fo:basic-links don't make it into the PDF. If I dump the FO DOM tree to a file and use fop from the commandline the links are present in the PDF. Are you, by any chance, using disable-output-escaping somewhere? J.Pietschmann
Re: basic-link
You should try http://forum.planetpdf.com - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 10, 2002 11:22 AM Subject: RE: basic-link Hi, We r generating PDF files using fo. We want to provide some security features to the PDF like non-printable, non-editable etc., when opened thru Adobe acrobat. Can somebody help in achieving this? Can this be done thru FOP itself or do we need to use Adobe's API? If somebody could help me out thru Adobe API also, that would be appreciated. Regards, Vasantha Raju N -Original Message- From: MagnusSjöberg [mailto:[EMAIL PROTECTED] Sent: Wednesday, 10 April 2002 21:21 To: [EMAIL PROTECTED] Subject: fo:basic-link Hi all! When using fo:basic-link it appears that the 'hotspot' around the text in the PDF gets misaligned. The more links I have in a page, the more the hotspots stray away, making me think the error is cumulative. (My fo consists of several page sequences, if that could be a factor...) Are there any problems with the implementation of fo:basic-link? I saw earlier posts talking about this but haven't found anything conclusive. Anyone got any ideas? /// Magnus