Re: Detecting a page break before it happens
Trevor, This is something you provide contingency in XSL-FO for, not something you need to do manually on every page. Search the list archives for fo:marker fo:retrieve marker look for same in the examples directory. Anyone care to update the FAQ for this? I can provide better wording. Regards, Roland Trevor Keast wrote: Hi, I have a large table that spans many pages. I need some way or detecting a page break before it happens so that I can write continued... at the bottom of the table. How can I go about doing this? Thanks in advance! Regards, Trevor. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail is solely for the use of the intended recipient and may contain information which is confidential or privileged. Any unauthorised use of its contents is prohibited. If you have received this e-mail in error, please notify the sender via return e-mail and then delete the original e-mail. This e-mail is solely for the use of the intended recipient and may contain information which is confidential or privileged. Any unauthorised use of its contents is prohibited. If you have received this e-mail in error, please notify the sender via return e-mail and then delete the original e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to put batch process into background on Mac OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
snip
I have not studied how to include the XSLT transformation. Here is
how it would go:
source XML document xslt transform via saxon (xslt 2.0) --- 50
+ .fo documents ---fop---50+ pdf documents.
The xslt automatically produces the 50 fo docs via xsl:result-
document. Would all this go into one build.xml? If so, would I
just call the xslt task first then call the generate_multiple-pdf
task?
I am not sure that I need to bundle this all together. But it might
make my life easier.
Thanks again,
Terry
Yes, I do everything inside ant, from building my initial project
structure through the PDF generation. Here is one of my targets to
produce the .fo output that is the input to Fop:
target name=-fo depends=init,convert-images
description=Produces the fo (needed for PDF production)
formatted file
xslt in=${topdoc} out=${formatdir}/${basename}.fo
style=${xsltdir}/fo/docbook.xsl
factory
name=org.apache.xalan.processor.TransformerFactoryImpl
/factory
xmlcatalog refid=catalog.docbook/
!-- BUG: Fop 0.93 crashes with svg images in my environment.
Have not been able to figure out why. Using pngs as stopgap-
they create larger PDFs and worse printed output. (emv 09042007)
--
param name=graphic.default.extension expression=png/
param name=fop1.extensions expression=1/
param name=ulink.footnotes expression=1
unless=xslt.no.ulink.footnotes/
param name=glossterm.auto.link expression=1
unless=xslt.no.glossterm.auto.link/
param name=id.warnings expression=1
unless=xslt.no.id.warnings/
/xslt
/target
It should be easy to modify to do multiple documents just like you
did for the Fop processing. I also build several other output formats
along the way, including ODF via Fop. The dependency in the targets
makes sure they are built in the right order and only if needed.
These task definitions are all in an ant-include.xml which is shared
between projects. I have a build.xml in each project which defines
some project specific parameters like ${topdoc} and $
{xsl.no.ulink.footnotes} as desired and then includes ant-
include.xml. For a few projects, the ant-include has to be
customized, but not often and I can define some special purpose tasks
in the build.xml if I need to.
Sincerely,
Eric Vought
Faith does not absolve us from trying to understand our world and
make moral distinctions with the eyes and brain given us. Religion is
as much responsibility as direction: Duty not Distinction.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFHgXFLfsH8fS6g9ecRAh4AAKDVc7xA+RsR4T/IoCarjNk5hGWcsQCg70vL
L3YF+EGqgx3tl/bEzZWYmpU=
=5D4E
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Help! URI for fo:external-graphic in web service
Hello, I am developing a web service which returns a PDF generated by FOP (fop-0.94) which must include an image. The web service is deployed as an EAR to a WebLogic server, and the image to be inserted into the PDF is contained within this EAR. How do I correctly access the image embedded in the EAR? I have been able to use a file file path when testing on my own box, but this is obviously unsuitable for other environments! The code I am using that works for my local environment looks like this: fo:block fo:external-graphic width=70mm content-height=scale-to-fit content-width=scale-to-fit src=C:\Project\src\au\com\aaa\services\certificate.gif / /fo:block Thanks for your help! Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help! URI for fo:external-graphic in web service
Jerome Munchenberg wrote: Hello, I am developing a web service which returns a PDF generated by FOP (fop-0.94) which must include an image. The web service is deployed as an EAR to a WebLogic server, and the image to be inserted into the PDF is contained within this EAR. You might try the JAR scheme, but I am not sure whether that scales well to a EAR. Another option is to use the real filepath (you can get the real unpacked EAR location through your web application server interface, I believe), or a relative path (often it is quite easy to get the WEB-INF directory and go from there). If all fails, the next easiest thing to do is to use the public URI which would also be accessible from your website to retrieve that same file. It is probably best to use localhost as server to prevent an extra server roundtrip. If you don't like any of these scenarios because of their lack of scalability, start using Catalogs (see OASIS website) and use a URIResolver (possibly with a specific scheme) to resolve the catalogs unambiguously regardless the platform / system / paths your services are running on. How do I correctly access the image embedded in the EAR? I have been able to use a file file path when testing on my own box, but this is obviously unsuitable for other environments! You were lucky that it worked, because if a file path is allowed, than that's a bug in the FOP implementation: XSL-FO prescribes that only a URI is allowed. To go from a filepath to a URI you should rewrite it something like file:///c:/project/scr/certificate.gif (note the forward slashes!). src=C:\Project\src\au\com\aaa\services\certificate.gif HTH, Cheers, -- Abel Braaksma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
