Problems compiling CVS
I've tried the following on my CVS tree
Cvs -z3 update
./build.sh clean
./build.sh all
I get the following errors:
[javac]
/usr/local/java/xml-fop/build/src/org/apache/fop/fo/FONode.java:14: Class
org.apache.fop.util.CharUtilities not found in import.
[javac] import org.apache.fop.util.CharUtilities;
[javac]^
[javac]
/usr/local/java/xml-fop/build/src/org/apache/fop/fo/flow/Block.java:18:
Class org.apache.fop.util.CharUtilities not found in import.
[javac] import org.apache.fop.util.CharUtilities;
[javac]^
[javac]
/usr/local/java/xml-fop/build/src/org/apache/fop/fo/InlineCharIterator.java:
4: Class org.apache.fop.util.CharUtilities not found in import.
[javac] import org.apache.fop.util.CharUtilities;
[javac]^
[javac]
/usr/local/java/xml-fop/build/src/org/apache/fop/layoutmgr/TextLayoutManager
.java:16: Class org.apache.fop.util.CharUtilities not found in import.
[javac] import org.apache.fop.util.CharUtilities;
[javac]^
[javac]
/usr/local/java/xml-fop/build/src/org/apache/fop/fo/flow/Block.java:507:
Class org.apache.fop.util.CharUtilities not found.
[javac] else if (CharUtilities.classOf(c) !=
[javac] ^
[javac]
/usr/local/java/xml-fop/build/src/org/apache/fop/fo/flow/Block.java:507:
Undefined variable or class name: CharUtilities
[javac] else if (CharUtilities.classOf(c) !=
[javac] ^
[javac]
/usr/local/java/xml-fop/build/src/org/apache/fop/fo/flow/Block.java:508:
Class org.apache.fop.util.CharUtilities not found.
[javac] CharUtilities.XMLWHITESPACE) {
[javac] ^
[javac]
/usr/local/java/xml-fop/build/src/org/apache/fop/fo/flow/Block.java:508:
Undefined variable or class name: CharUtilities
[javac] CharUtilities.XMLWHITESPACE) {
[javac] ^
[javac] 8 errors
BUILD FAILED
Any suggestions?
--
Carlos E. Araya
---+ WebCT Administrator/Trainer
P | California Virtual Campus
- | C/O De Anza College
G | 21250 Stevens Creek Blvd
---+ Cupertino, CA 95014
email [EMAIL PROTECTED]
web http://www.cvc1.org/ (work)
http://www.silverwolf-net.net (personal)
phone 408 257 0420 (work)
PGP Fingerprint:E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756
Hey! It compiles! Ship it!
RE: [ANNOUNCEMENT] Fop 0.20.3 released
Thanks Christian - that's fixed it. I'm happy now. You can make your release. Seriously, sometimes I feel very stupid. Every other time I've had problems with versions I've looked in the examples and this time I didn't. Cheers Tim -Original Message- From: Christian Geisert [mailto:[EMAIL PROTECTED] Sent: Tuesday, 12 March 2002 21:06 To: [EMAIL PROTECTED] Subject: Re: [ANNOUNCEMENT] Fop 0.20.3 released Keen Tim wrote: Christian, I'm having problems with this (the third) and the second release candidate for 0.20.3, but not the first. Follow my thread Trouble with ZapfDingbats in fop-user for more info. Perhaps you can advise me also. There has been a change in in the font enconding from RC1 to RC2 (I think the patch *corrected* the enconding for the symbol fonts) Have a look at docs/examples/fo/fonts.fo Cheers Tim Christian The information in this e-mail together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of review, disclosure, modification, distribution and/or publication of this e-mail message is prohibited. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network.
Re: Problems compiling CVS
try cvs up -d On 2002.03.13 01:10 Carlos Araya wrote: I've tried the following on my CVS tree Cvs -z3 update ./build.sh clean ./build.sh all
Re: Rendered SVG does not contain images from xsl:fo external-graphic/
Hi, The image part is not implemented as far as I can remember. As for the text, is it in the document, is it viewable using the batik viewer for example. It probably ignores your embedded ttf but will use the fonts available to the jvm. On 2002.03.12 20:12 Andrius Sabanas wrote: Hello, I would like to know if there is a convenient way to make preview images from xsl:fo documents. I tried rendering to SVG and feeding to Batik's JPEG transcoder, but it seems that the rendered SVG does not contain images specified with external-graphic/ in xsl:fo. Is this a bug or a not yet implemented feature? In addition, Batik transcoder does not even display text when JPG is constructed. I am using embedded ttf for displaying text. The ttf is present in my system, of course. Can this be the problem? Everything is ok when I render to PDF. Andrius
Compile Fop 0.20.3 with J2SDK1.4.0
Hello all, (B (BI try to compile Fop 0.20.3 with J2SDK1.4.0 but I have error messages. (B (BD:\fop-0.20.3\build.xml:472 javax.xml.transform.TransformerException: (Borg.xml.sax.SAXParseException: File (B"file:///D:/fop-0.20.3/D:/fop-0.20.3/build/src/codegen/encodings.xml" not found (B--- Nested Exception --- (B (BI change PDFGraphics2D.java before compiling, but I can't. (B (BHow can I compile fop 0.20.3 with JDK1.4 ? (B (B- (BMiya Chiharu
RE: FOP Performance Limitations?
Are you using the included Xalan and Xerces.jar? I replaced them with Xalan 2.2 and Xerces 1.4.2 and got big improvement in speed (on Win2000 and Sun Solaris). Peter Peter Jacobs Freelance multimedia programmeur De Budetstraat 8 B-3201 Aarschot [EMAIL PROTECTED] 016/573257
Re: SV: external-graphic src syntax
I use Fop 0.20.2 and as long as the path to the imagefile is absolute, it works. Like so: fo:external-graphic src=file:/abs/path/to/images/image.jpg/ Also, there is an entry in Fop's config.xml where you can set the basedir but the comment says 'not implemented'. If, and when this entry gets supported, that should be the place where you specify the basedir, enabling relative file paths. ///Magnus Klosa Uwe wrote: It works only with fop0_19_0. All fop0_20_x has the same error. I've tried it in two days now. Uwe -Ursprungligt meddelande- Fran: Michael Engelhart [mailto:[EMAIL PROTECTED] Skickat: den 12 mars 2002 16:28 Till: [EMAIL PROTECTED] Amne: external-graphic src syntax Can someone show me the syntax to using fo:external-graphic?? I have an image in the same directory as the stylsheet and have tried this syntax: fo:block text-align=center fo:external-graphic src=logo.jpg/ /fo:block this syntax: fo:block text-align=center fo:external-graphic src=file:./logo.jpg/ /fo:block this syntax: fo:block text-align=center fo:external-graphic src=file://./logo.jpg/ /fo:block and none of them work. I always get this error: [ERROR]: Error while creating area : Error with image URL: ./logo.jpg (No such file or directory) and no base directory is specified I have compared this to the images.fo example document as well as the W3C XSL spec and it doesn't work. I can sort of get it to work using an external url like http://somewhere.com/logo.jpg; but when I do it that way my application hangs and never comes back. any ideas??
SV: SV: external-graphic src syntax
Hello Magnus, have you tried this: fo:external-graphic src=url(image.jpg)/ I found it somewhere in the internet. Uwe -Ursprungligt meddelande- Fran: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Magnus Sjoberg Skickat: den 13 mars 2002 12:58 Till: [EMAIL PROTECTED] Amne: Re: SV: external-graphic src syntax I use Fop 0.20.2 and as long as the path to the imagefile is absolute, it works. Like so: fo:external-graphic src=file:/abs/path/to/images/image.jpg/ Also, there is an entry in Fop's config.xml where you can set the basedir but the comment says 'not implemented'. If, and when this entry gets supported, that should be the place where you specify the basedir, enabling relative file paths. ///Magnus Klosa Uwe wrote: It works only with fop0_19_0. All fop0_20_x has the same error. I've tried it in two days now. Uwe -Ursprungligt meddelande- Fran: Michael Engelhart [mailto:[EMAIL PROTECTED] Skickat: den 12 mars 2002 16:28 Till: [EMAIL PROTECTED] Amne: external-graphic src syntax Can someone show me the syntax to using fo:external-graphic?? I have an image in the same directory as the stylsheet and have tried this syntax: fo:block text-align=center fo:external-graphic src=logo.jpg/ /fo:block this syntax: fo:block text-align=center fo:external-graphic src=file:./logo.jpg/ /fo:block this syntax: fo:block text-align=center fo:external-graphic src=file://./logo.jpg/ /fo:block and none of them work. I always get this error: [ERROR]: Error while creating area : Error with image URL: ./logo.jpg (No such file or directory) and no base directory is specified I have compared this to the images.fo example document as well as the W3C XSL spec and it doesn't work. I can sort of get it to work using an external url like http://somewhere.com/logo.jpg; but when I do it that way my application hangs and never comes back. any ideas??
Re: SV: external-graphic src syntax
Hmm. Now that I know the syntax it works. Maybe I was just screwing put the long path name.. Thanks Mike On Wednesday, March 13, 2002, at 06:58 AM, Magnus Sjöberg wrote: I use Fop 0.20.2 and as long as the path to the imagefile is absolute, it works. Like so: fo:external-graphic src=file:/abs/path/to/images/image.jpg/ Also, there is an entry in Fop's config.xml where you can set the basedir but the comment says 'not implemented'. If, and when this entry gets supported, that should be the place where you specify the basedir, enabling relative file paths. ///Magnus Klosa Uwe wrote: It works only with fop0_19_0. All fop0_20_x has the same error. I've tried it in two days now. Uwe -Ursprungligt meddelande- Fran: Michael Engelhart [mailto:[EMAIL PROTECTED] Skickat: den 12 mars 2002 16:28 Till: [EMAIL PROTECTED] Amne: external-graphic src syntax Can someone show me the syntax to using fo:external-graphic?? I have an image in the same directory as the stylsheet and have tried this syntax: fo:block text-align=center fo:external-graphic src=logo.jpg/ /fo:block this syntax: fo:block text-align=center fo:external-graphic src=file:./logo.jpg/ /fo:block this syntax: fo:block text-align=center fo:external-graphic src=file://./logo.jpg/ /fo:block and none of them work. I always get this error: [ERROR]: Error while creating area : Error with image URL: ./logo.jpg (No such file or directory) and no base directory is specified I have compared this to the images.fo example document as well as the W3C XSL spec and it doesn't work. I can sort of get it to work using an external url like http://somewhere.com/logo.jpg; but when I do it that way my application hangs and never comes back. any ideas??
Re: SV: SV: external-graphic src syntax
Ok, you got me started. I looked into this and found out the following ;-) In the xsl spec., the src attribute for fo:external-graphic is specified to contain a 'uri-specification' For all I know, this is the URI definition as defined in RFC2396. Looking into this and comparing the three attribute values that failed I came up with this: 1) src=logo.jpg This should work since 'logo.jpg' is a correct relative URI according to the BNF 2) src=file:./logo.jpg This should also work since 'file:./logo.jpg' defines a correct absoluteURI. 3) src=file://./logo.jpg This defines an absolute URI, but the file:// should be followed by a 'server' or a 'reg_name' according to the RFC. I believe that the code parsing the file://./logo.jpg treats the . after 'file://' as a server name, hence the URL error. Of the three I got 1 and 2 working using Fop-0.20.2, Xalan-2.3.0 and Xerces-2.0.0 (which is good, since they s h o u l d work). Example 3 failed, complaining about Invalid Image URL - error on relative URL, which I believe is a correct error message. The relative URL really is incorrect. I also used a relative URI as in src=/root/path/to/images/image.jpg, which worked. (Note the missing file:) Hope this 'clears' up some of the fog. Rgds/// Magnus Klosa Uwe wrote: Hello Magnus, have you tried this: fo:external-graphic src=url(image.jpg)/ I found it somewhere in the internet. Uwe -Ursprungligt meddelande- Fran: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Magnus Sjoberg Skickat: den 13 mars 2002 12:58 Till: [EMAIL PROTECTED] Amne: Re: SV: external-graphic src syntax I use Fop 0.20.2 and as long as the path to the imagefile is absolute, it works. Like so: fo:external-graphic src=file:/abs/path/to/images/image.jpg/ Also, there is an entry in Fop's config.xml where you can set the basedir but the comment says 'not implemented'. If, and when this entry gets supported, that should be the place where you specify the basedir, enabling relative file paths. ///Magnus Klosa Uwe wrote: It works only with fop0_19_0. All fop0_20_x has the same error. I've tried it in two days now. Uwe -Ursprungligt meddelande- Fran: Michael Engelhart [mailto:[EMAIL PROTECTED] Skickat: den 12 mars 2002 16:28 Till: [EMAIL PROTECTED] Amne: external-graphic src syntax Can someone show me the syntax to using fo:external-graphic?? I have an image in the same directory as the stylsheet and have tried this syntax: fo:block text-align=center fo:external-graphic src=logo.jpg/ /fo:block this syntax: fo:block text-align=center fo:external-graphic src=file:./logo.jpg/ /fo:block this syntax: fo:block text-align=center fo:external-graphic src=file://./logo.jpg/ /fo:block and none of them work. I always get this error: [ERROR]: Error while creating area : Error with image URL: ./logo.jpg (No such file or directory) and no base directory is specified I have compared this to the images.fo example document as well as the W3C XSL spec and it doesn't work. I can sort of get it to work using an external url like http://somewhere.com/logo.jpg; but when I do it that way my application hangs and never comes back. any ideas??
Re: SV: SV: external-graphic src syntax
Thanks Mangus, That's great info. (Maybe we can get it stuck into the FAQ? ) I know have 2 working fine. 1 and 3 I still can't get to work My question about #1 is, how do you know what the relative path is relative too?? I my mind it should be relative to the stylesheet that's calling it but in my experience that doesn't work at all. For example if I have this setup: directory - doc.xsl (which does a dynamic transform with Xalan into an FO document) - logo.jpg The src=logo.jpg tag makes FOP complain about the Invalid URL image. thanks Mike On Wednesday, March 13, 2002, at 08:44 AM, Magnus Sjöberg wrote: Ok, you got me started. I looked into this and found out the following ;-) In the xsl spec., the src attribute for fo:external-graphic is specified to contain a 'uri-specification' For all I know, this is the URI definition as defined in RFC2396. Looking into this and comparing the three attribute values that failed I came up with this: 1) src=logo.jpg This should work since 'logo.jpg' is a correct relative URI according to the BNF 2) src=file:./logo.jpg This should also work since 'file:./logo.jpg' defines a correct absoluteURI. 3) src=file://./logo.jpg This defines an absolute URI, but the file:// should be followed by a 'server' or a 'reg_name' according to the RFC. I believe that the code parsing the file://./logo.jpg treats the . after 'file://' as a server name, hence the URL error. Of the three I got 1 and 2 working using Fop-0.20.2, Xalan-2.3.0 and Xerces-2.0.0 (which is good, since they s h o u l d work). Example 3 failed, complaining about Invalid Image URL - error on relative URL, which I believe is a correct error message. The relative URL really is incorrect. I also used a relative URI as in src=/root/path/to/images/image.jpg, which worked. (Note the missing file:) Hope this 'clears' up some of the fog. Rgds/// Magnus
Re: DocBook patch for FOP
Thanks. At least this time it ran. Here's what the output looks like now: [INFO]: building formatting object tree [INFO]: [1] [WARN]: table-layout=auto is not supported, using fixed! [INFO]: [2] [WARN]: table-layout=auto is not supported, using fixed! [INFO]: [3] [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [INFO]: [4] [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [INFO]: [5] [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [INFO]: [6] [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [INFO]: [7] [WARN]: table-layout=auto is not supported, using fixed! [WARN]: current implementation of tables requires a table-column for each column , indicating column-width [INFO]: [8] [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - last-line-end-indent is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented yet. [WARN]: property - linefeed-treatment is not implemented
another newbie question
OK, I need help on this Here is my XML page persons person name / address / country / /person person name / address / country / /person . /persons /page I am using template match=person and calling it with apply-templates in fo:page-sequence master-reference=many-pages (I know this is wrong) However, I am not getting the desired output which is the output of person details per page. I want every person to appear in a seperate page. What do I loop through to generate single page for every person element. Do you have any examples for such a case? Thanks in advance Meltem
border around text
Fop does not seem to implement borders for inline elements. Is there a way to draw a border around a text which width is unknown? ( not using absolute padding) A border applied to a block element draws a border with huge left right paddings. Thank you Franck MARTIN
Re: SV: SV: external-graphic src syntax
That's bizarre, I 'assumed' FOP used the current directory as its base dir... I ran the following command with test.xml, test.xsl and image.jpg in the current directory: current_dir java org.apache.fop.apps.Fop -xml test.xml -xsl test.xsl -pdf test.pdf All images in the xml are added to the fo using fo:external-graphic src=image.jpg/ This produces no errors. Exactly what sequence of events are you using to create the PDF? ///Magnus Michael Engelhart wrote: Thanks Mangus, That's great info. (Maybe we can get it stuck into the FAQ? ) I know have 2 working fine. 1 and 3 I still can't get to work My question about #1 is, how do you know what the relative path is relative too?? I my mind it should be relative to the stylesheet that's calling it but in my experience that doesn't work at all. For example if I have this setup: directory - doc.xsl (which does a dynamic transform with Xalan into an FO document) - logo.jpg The src=logo.jpg tag makes FOP complain about the Invalid URL image. thanks Mike On Wednesday, March 13, 2002, at 08:44 AM, Magnus Sjöberg wrote: Ok, you got me started. I looked into this and found out the following ;-) In the xsl spec., the src attribute for fo:external-graphic is specified to contain a 'uri-specification' For all I know, this is the URI definition as defined in RFC2396. Looking into this and comparing the three attribute values that failed I came up with this: 1) src=logo.jpg This should work since 'logo.jpg' is a correct relative URI according to the BNF 2) src=file:./logo.jpg This should also work since 'file:./logo.jpg' defines a correct absoluteURI. 3) src=file://./logo.jpg This defines an absolute URI, but the file:// should be followed by a 'server' or a 'reg_name' according to the RFC. I believe that the code parsing the file://./logo.jpg treats the . after 'file://' as a server name, hence the URL error. Of the three I got 1 and 2 working using Fop-0.20.2, Xalan-2.3.0 and Xerces-2.0.0 (which is good, since they s h o u l d work). Example 3 failed, complaining about Invalid Image URL - error on relative URL, which I believe is a correct error message. The relative URL really is incorrect. I also used a relative URI as in src=/root/path/to/images/image.jpg, which worked. (Note the missing file:) Hope this 'clears' up some of the fog. Rgds/// Magnus -- Secode - Total Internet Security Magnus Sjöberg Research And Development email: [EMAIL PROTECTED] cell: +46 709 150 710 POTS: +46 8 564 875 05 http://www.secode.com Internet is to be a safe area for business, transactions and information exchange
AW: SV: SV: external-graphic src syntax
Hi I think if you are running under tomcat, the current directory is tomcat/bin If you are running from command line, Java_home is the current dir Rgds Jay -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Magnus Sjöberg Gesendet: Mittwoch, 13. März 2002 15:59 An: [EMAIL PROTECTED] Betreff: Re: SV: SV: external-graphic src syntax That's bizarre, I 'assumed' FOP used the current directory as its base dir... I ran the following command with test.xml, test.xsl and image.jpg in the current directory: current_dir java org.apache.fop.apps.Fop -xml test.xml -xsl test.xsl -pdf test.pdf All images in the xml are added to the fo using fo:external-graphic src=image.jpg/ This produces no errors. Exactly what sequence of events are you using to create the PDF? ///Magnus Michael Engelhart wrote: Thanks Mangus, That's great info. (Maybe we can get it stuck into the FAQ? ) I know have 2 working fine. 1 and 3 I still can't get to work My question about #1 is, how do you know what the relative path is relative too?? I my mind it should be relative to the stylesheet that's calling it but in my experience that doesn't work at all. For example if I have this setup: directory - doc.xsl (which does a dynamic transform with Xalan into an FO document) - logo.jpg The src=logo.jpg tag makes FOP complain about the Invalid URL image. thanks Mike On Wednesday, March 13, 2002, at 08:44 AM, Magnus Sjöberg wrote: Ok, you got me started. I looked into this and found out the following ;-) In the xsl spec., the src attribute for fo:external-graphic is specified to contain a 'uri-specification' For all I know, this is the URI definition as defined in RFC2396. Looking into this and comparing the three attribute values that failed I came up with this: 1) src=logo.jpg This should work since 'logo.jpg' is a correct relative URI according to the BNF 2) src=file:./logo.jpg This should also work since 'file:./logo.jpg' defines a correct absoluteURI. 3) src=file://./logo.jpg This defines an absolute URI, but the file:// should be followed by a 'server' or a 'reg_name' according to the RFC. I believe that the code parsing the file://./logo.jpg treats the . after 'file://' as a server name, hence the URL error. Of the three I got 1 and 2 working using Fop-0.20.2, Xalan-2.3.0 and Xerces-2.0.0 (which is good, since they s h o u l d work). Example 3 failed, complaining about Invalid Image URL - error on relative URL, which I believe is a correct error message. The relative URL really is incorrect. I also used a relative URI as in src=/root/path/to/images/image.jpg, which worked. (Note the missing file:) Hope this 'clears' up some of the fog. Rgds/// Magnus -- Secode - Total Internet Security Magnus Sjöberg Research And Development email: [EMAIL PROTECTED] cell: +46 709 150 710 POTS: +46 8 564 875 05 http://www.secode.com Internet is to be a safe area for business, transactions and information exchange
AW: SV: SV: external-graphic src syntax
Hi Sorry I goofed the earlier mail. I think if you are running under tomcat, the BASE directory is tomcat/bin If you are running from command line, Java_home is the BASE dir Rgds Jay -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Magnus Sjöberg Gesendet: Mittwoch, 13. März 2002 15:59 An: [EMAIL PROTECTED] Betreff: Re: SV: SV: external-graphic src syntax That's bizarre, I 'assumed' FOP used the current directory as its base dir... I ran the following command with test.xml, test.xsl and image.jpg in the current directory: current_dir java org.apache.fop.apps.Fop -xml test.xml -xsl test.xsl -pdf test.pdf All images in the xml are added to the fo using fo:external-graphic src=image.jpg/ This produces no errors. Exactly what sequence of events are you using to create the PDF? ///Magnus Michael Engelhart wrote: Thanks Mangus, That's great info. (Maybe we can get it stuck into the FAQ? ) I know have 2 working fine. 1 and 3 I still can't get to work My question about #1 is, how do you know what the relative path is relative too?? I my mind it should be relative to the stylesheet that's calling it but in my experience that doesn't work at all. For example if I have this setup: directory - doc.xsl (which does a dynamic transform with Xalan into an FO document) - logo.jpg The src=logo.jpg tag makes FOP complain about the Invalid URL image. thanks Mike On Wednesday, March 13, 2002, at 08:44 AM, Magnus Sjöberg wrote: Ok, you got me started. I looked into this and found out the following ;-) In the xsl spec., the src attribute for fo:external-graphic is specified to contain a 'uri-specification' For all I know, this is the URI definition as defined in RFC2396. Looking into this and comparing the three attribute values that failed I came up with this: 1) src=logo.jpg This should work since 'logo.jpg' is a correct relative URI according to the BNF 2) src=file:./logo.jpg This should also work since 'file:./logo.jpg' defines a correct absoluteURI. 3) src=file://./logo.jpg This defines an absolute URI, but the file:// should be followed by a 'server' or a 'reg_name' according to the RFC. I believe that the code parsing the file://./logo.jpg treats the . after 'file://' as a server name, hence the URL error. Of the three I got 1 and 2 working using Fop-0.20.2, Xalan-2.3.0 and Xerces-2.0.0 (which is good, since they s h o u l d work). Example 3 failed, complaining about Invalid Image URL - error on relative URL, which I believe is a correct error message. The relative URL really is incorrect. I also used a relative URI as in src=/root/path/to/images/image.jpg, which worked. (Note the missing file:) Hope this 'clears' up some of the fog. Rgds/// Magnus -- Secode - Total Internet Security Magnus Sjöberg Research And Development email: [EMAIL PROTECTED] cell: +46 709 150 710 POTS: +46 8 564 875 05 http://www.secode.com Internet is to be a safe area for business, transactions and information exchange
RE: another newbie question
Sorry to bother I solved the problem thanks Meltem -Original Message- From: Meltem Kogelbauer [mailto:[EMAIL PROTECTED] Sent: 13 March 2002 14:37 To: [EMAIL PROTECTED] Subject: another newbie question OK, I need help on this Here is my XML page persons person name / address / country / /person person name / address / country / /person . /persons /page I am using template match=person and calling it with apply-templates in fo:page-sequence master-reference=many-pages (I know this is wrong) However, I am not getting the desired output which is the output of person details per page. I want every person to appear in a seperate page. What do I loop through to generate single page for every person element. Do you have any examples for such a case? Thanks in advance Meltem
Newbie question: Conditional page-brek
How can I do a page break when the TABLE_TITLE is NOT empty. xsl:value-of select=TABLE_TITLE/ Thanks Mathy
Re: SV: SV: external-graphic src syntax
I have the same setup but I'm calling FOP from an embedded application (NOT a web application - no tomcat or other server). Here's the code from my render() method: ByteArrayOutputStream out = new ByteArrayOutputStream(); DOMResult xslFODomResult = transformPDF(/some/pathto/a/stylesheet/pdf.xsl); Driver driver = new Driver(); driver.setRenderer(driver.RENDER_PDF); driver.setOutputStream(out); org.w3c.dom.Document foDoc =(org.w3c.dom.Document) xslFODomResult.getNode(); driver.render(foDoc); return (out.toByteArray()); That's why I'm trying to figure out where FOP is getting the directory path to image.jpg from. It doesn' t work in this situation. Is FOP using some kind of classpath directory??? Thanks Mike On Wednesday, March 13, 2002, at 09:59 AM, Magnus Sjöberg wrote: That's bizarre, I 'assumed' FOP used the current directory as its base dir... I ran the following command with test.xml, test.xsl and image.jpg in the current directory: current_dir java org.apache.fop.apps.Fop -xml test.xml -xsl test.xsl -pdf test.pdf All images in the xml are added to the fo using fo:external-graphic src=image.jpg/ This produces no errors. Exactly what sequence of events are you using to create the PDF? ///Magnus
Re: DOCBOOK-APPS: DocBook patch for FOP
On Wed, Mar 13, 2002 at 08:05:57AM -0500, Jeff Rancier wrote: Hello, I've generated a fo file from DocBook 1.48 XSL stylesheets, using Saxon 6.5.0. Using xalan-2.0.0.jar, I generated a intermediate fo file, using the DocBook 1.48 fo-patch-for-fop.xsl. I then attempt to generate a PDF file using FOP-20.3. Should I expect this process to work? Here is the fop output: [INFO]: FOP 0.20.3 [INFO]: building formatting object tree [ERROR]: Error in background-image property value 'http://docbook.sourceforge.ne t/release/images/draft.png': org.apache.fop.fo.expr.PropertyException: illegal c haracter [WARN]: property - background-attachment is not implemented yet. [WARN]: property - background-repeat is not implemented yet. [WARN]: property - background-position-horizontal is not implemented yet. [WARN]: property - background-position-vertical is not implemented yet. [ERROR]: Error in column-width property value '20%': org.apache.fop.fo.expr.Prop ertyException: No conversion defined [ERROR]: Error in column-width property value '20%': org.apache.fop.fo.expr.Prop ertyException: No conversion defined [ERROR]: Error in column-width property value '20%': org.apache.fop.fo.expr.Prop ertyException: No conversion defined [ERROR]: Error in column-width property value '20%': org.apache.fop.fo.expr.Prop ertyException: No conversion defined [ERROR]: Error in column-width property value '20%': org.apache.fop.fo.expr.Prop ertyException: No conversion defined [ERROR]: Error in column-width property value '20%': org.apache.fop.fo.expr.Prop ertyException: No conversion defined [ERROR]: Error in column-width property value '20%': org.apache.fop.fo.expr.Prop ertyException: No conversion defined [ERROR]: Error in column-width property value '20%': org.apache.fop.fo.expr.Prop ertyException: No conversion defined [ERROR]: Error in column-width property value '20%': org.apache.fop.fo.expr.Prop ertyException: No conversion defined [ERROR]: Error in column-width property value '20%': org.apache.fop.fo.expr.Prop ertyException: No conversion defined [ERROR]: 'master-reference' for 'fo:page-sequence'matches no 'simple-page-master ' or 'page-sequence-master' See: http://lists.oasis-open.org/archives/docbook-apps/200201/msg00532.html The patch is no longer needed as of Fop 20.3rc, which I believe was the beta for the current version 20.3. What happens when you skip the patch? You didn't mention whether you used the Docbook XSL xalan2 extensions, which help with tables. You should include extensions/xalan2.jar in your java CLASSPATH. -- Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 Caldera International, Inc. fax: (831) 429-1887 email: [EMAIL PROTECTED]
Re: FOP Performance Limitations?
Actually the FAQ (at http://www.owal.co.uk/cgi-bin/fopfaq.cgi since I have given up on the interactive Jyve program) doesn't contain much on memory consumption. I will add in the new page sequence when I (or someone else) comes up with an example. Alex At 20:22 12/03/2002, Chuck Paussa wrote: David, Most likely you're running out of memory. You should set a new page-sequence every once in a while (~60 lines of report would make it every page) Look on the FAQ about memory consumption Chuck
rotate text
Hello, I would like to rotate a piece of text by 90 degrees. Is there any possibility within FOP? The background: I create a letter together with the envelope. Unfortunately my printer only likes the envelopes turned by 90 degrees so I have to rotate the envelope page in my document . Thanks, Michael
RE: FOP Performance Limitations?
That's interesting that it made a difference for you. On our XML/XSL, it didn't make much difference - maybe it shaved 1-2 seconds of a 60 second rendering. -David On Wed, 13 Mar 2002, Peter Jacobs wrote: Are you using the included Xalan and Xerces.jar? I replaced them with Xalan 2.2 and Xerces 1.4.2 and got big improvement in speed (on Win2000 and Sun Solaris). Peter Peter Jacobs Freelance multimedia programmeur De Budetstraat 8 B-3201 Aarschot [EMAIL PROTECTED] 016/573257
