AW: AW: Non existent tag error...
Hi Darren! That's not completely righ. Your tests check if the attribute named tagname exists, not the tag named tagname. Christian -Ursprüngliche Nachricht- Von: Darren Munt [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 29. November 2001 23:18 An: '[EMAIL PROTECTED]' Betreff: RE: AW: Non existent tag error... I've found that the test needs to encompass three possibilities: 1. That the tag is not present; 2. That the tag is empty (ie. tagname=''), or; 3. That the tag is present and contains a value. If you use test=@tagname, the test will be true in cases 2 and 3. However, if you use test=not(@tagname='') (or test=@tagname!='') then it will only be true for case 3, at least this is the case with the parser I use. So it depends on whether or not you want different behaviour when the tag is missing than you want when the tag is present but empty. -Original Message- From: bryan hansen [mailto:[EMAIL PROTECTED]] Sent: Friday, 30 November 2001 2:09 To: [EMAIL PROTECTED] Subject: Re: AW: Non existent tag error... I did not solve the problem, I was going to add the line that I said oops on in the original message, sorry for the confusion. I will try this and see if it works. Thanks, Bryan --- Beer, Christian [EMAIL PROTECTED] wrote: Hi Bryan, did you solve the problem, or what does the oops mean?? Anyway: xsl:when test=Transaction/Filing/OldFilingNumber != '' is not right, I think! Try: xsl:when test=Transaction/Filing/OldFilingNumber That is the right term, the book says so. Christian -Ursprüngliche Nachricht- Von: bryan hansen [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 28. November 2001 18:16 An: [EMAIL PROTECTED] Betreff: Re: Non existent tag error... Oops, line 87 is the line that does the xsl:when test! Bryan --- bryan hansen [EMAIL PROTECTED] wrote: I have some xsl that checks to see if a tag does not exist: fo:table-cell fo:block text-align=start xsl:choose xsl:when test=Transaction/Filing/OldFilingNumber != '' xsl:value-of select=Transaction/Filing/OldFilingNumber/ /xsl:when xsl:otherwise N/A /xsl:otherwise /xsl:choose /fo:block /fo:table-cell This was working correctly, but now I am getting an error: ; SystemID: http://utstbrucc2/ucc-ack.fo.xsl; Line#: 87; Column#: -1 javax.xml.transform.TransformerException: Unknown error in XPath The only thing that has changed was that I reinstalled fop? Am I missing a required jar or have a different version that would make this stop working? __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: CVS snapshot does not render
I'm reiterating my request. Does anybody have an idea as to what the solution might be? I downloaded the latest (http://cvs.apache.org/snapshots/xml-fop/xml-fop_20011130051622.tar.gz) and it still won't work. Philippe Van Der Gucht wrote: Hello, I'm trying to make the latest cvs snapshot working but when it tries to render PDF's I get this: ---8--- Fop Test Starting Tests ... Buildfile: build.xml init: newPDF: [fop] D:\xml-fop\docs\examples\fo\border.fo - D:\xml-fop\docs\examples\te sts\border.pdf [fop] building formatting object tree [fop] Parsing of document complete, stopping renderer [fop] D:\xml-fop\docs\examples\fo\bordershorthand.fo - D:\xml-fop\docs\ex amples\tests\bordershorthand.pdf [fop] building formatting object tree [fop] Couldn't render file: null BUILD FAILED ---8--- I'm using the 1.3.1_01 jdk on an NT4 sp6a machine. Nobody else seems to have this kind of problem so I'm baffled! Philippe. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3302] - NoClassDefFoundError - org/apache/fop/apps/fop
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3302. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3302 NoClassDefFoundError - org/apache/fop/apps/fop [EMAIL PROTECTED] changed: What|Removed |Added Severity|Blocker |Minor Status|NEW |ASSIGNED OS/Version|Windows NT/2K |Linux Priority|Other |High - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3302] - NoClassDefFoundError - org/apache/fop/apps/fop
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3302. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3302 NoClassDefFoundError - org/apache/fop/apps/fop [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: CVS snapshot does not render
As previously stated current cvs does NOT work. It will not work until the code is written to make it work. If you want something that works then stick with the releases (ie. 0.20.2). On 2001.11.30 13:01 Philippe Van Der Gucht wrote: I'm reiterating my request. Does anybody have an idea as to what the solution might be? I downloaded the latest (http://cvs.apache.org/snapshots/xml-fop/xml-fop_20011130051622.tar.gz) and it still won't work. Philippe Van Der Gucht wrote: Hello, I'm trying to make the latest cvs snapshot working but when it tries to render PDF's I get this: ---8--- Fop Test Starting Tests ... Buildfile: build.xml init: newPDF: [fop] D:\xml-fop\docs\examples\fo\border.fo - D:\xml-fop\docs\examples\te sts\border.pdf [fop] building formatting object tree [fop] Parsing of document complete, stopping renderer [fop] D:\xml-fop\docs\examples\fo\bordershorthand.fo - D:\xml-fop\docs\ex amples\tests\bordershorthand.pdf [fop] building formatting object tree [fop] Couldn't render file: null BUILD FAILED ---8--- I'm using the 1.3.1_01 jdk on an NT4 sp6a machine. Nobody else seems to have this kind of problem so I'm baffled! Philippe. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Embedding Other Documents into a PDF File
Hi, Is there any way to embed other documents into a PDF file eg. another pdf file, using fop? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Pre Formatted Text
I am using FOP to generate PDFs on the fly from XML. One of my XML elements contains a large (1K - 1M) preformatted (contains LFs) block of text. When I display this field in HTML I use a PRE tag. Is there a FO tag that FOP supports that functions similarly? Thanks, Jim Urban Product Manager Netsteps Inc. Suite 505E 1 Pierce Pl. Itasca, IL 60143 Voice: (630) 250-3045 x2164 Fax: (630) 250-3046 attachment: winmail.dat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Optional + on integer and number
Dear Dandies, Before I send this question to the editors, I'll ask it here in case I'm missing something obvious. How is the optional '+', on integer and number types, expressed in grammar of Section 5.9? Quote from 5.11 Property Datatypes--- integer A signed integer value which consists of an optional '+' or '-' character followed by a sequence of digits. A property may define additional constraints on the value. NOTE: A '+' sign is allowed for CSS2 compatibility. number A signed real number which consists of an optional '+' or '-' character followed by a sequence of digits followed by an optional '.' character and sequence of digits. A property may define additional constraints on the value. Endquote Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Invalid Image URL, No Protocol.
Happens when I do this:
xsl:variable name=filenamefile:///./server/html/xsl:value-of
select=$current-dsn//xsl:value-of select=picture//xsl:variable
fo:external-graphic height=3.375cm width=4.50cm src={$filename}/
I've tried different versions of this but it still gives Invalid Image URL and tells
me I have no protocol.
Any Ideas?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Fill pattern problem
Hi, The following svg file crashes out the PDF renderer I hand wrote the file, so I dont know if is a bug in the XML. Adobe's plugin seems to render it OK. ?xml version=1.0 encoding=iso-8859-1? !DOCTYPE svg PUBLIC -//W3C//DTD SVG 2303 Stylable//EN http://www.w3.org/TR/2000/03/WD-SVG-2303/DTD/svg-2303-stylable.dtd; svg xml-space=preserve preserveAspectRatio=xMaxYMaxmeet xmlns:svg=http://www.w3.org/2000/svg; defs pattern id=pattern x=0 y=0 patternUnits=userSpaceOnUse width=185 height=200 g transform=rotate(45 100 15) translate(50 50) g fill=#66 stroke=#66 text x=0 y=33.75 font-family=Helvetica font-size=20Pattern Fill/text /g /g /pattern /defs g id=overlay opacity=0.50 rect x=0 y=0 width=900 height=470 fill=url(#pattern) stroke=black stroke-width=0 /g /svg Heres the FO ?xml version=1.0 encoding=UTF-8? fo:root font-family=Univers font-size=9pt text-align=center xmlns:fo =http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin-bottom=25pt margin-left=100pt margin-right=50pt margin-top=75pt master-name=simple page-height =210mm page-width=297mm fo:region-body margin-bottom=50pt/ fo:region-after extent=25pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-name=simple fo:static-content flow-name=xsl-region-after fo:block font-size=7pt text-align-last=center fo:page-number/ /fo:block /fo:static-content fo:flow flow-name=xsl-region-body fo:block fo:instream-foreign-object svg:svg height=150mm width=250mm xmlns:svg =http://www.w3.org/2000/svg; svg:image height=478 transform =scale(0.6) width=1145 xlink:href=file:///m:/overlay.txt/ /svg:svg /fo:instream-foreign-object /fo:block /fo:flow /fo:page-sequence /fo:root org.apache.fop.apps.Fop svgtest.fo svgtest.pdf [INFO]: FOP 0.20.2 [INFO]: building formatting object tree [INFO]: [1] [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: svg graphic could not be built: java.lang.Object java.lang.ClassCastException: java.lang.Object at org.apache.batik.bridge.SVGImageElementBridge.createRasterImageNode(SVGImageElementBridge.java:167) at org.apache.batik.bridge.SVGImageElementBridge.createGraphicsNode(SVGImageElementBridge.java:109) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:167) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:133) at org.apache.batik.bridge.GVTBuilder.build(GVTBuilder.java:66) at org.apache.fop.render.pdf.PDFRenderer.renderSVGDocument(PDFRenderer.java:413) at org.apache.fop.render.pdf.PDFRenderer.renderSVGArea(PDFRenderer.java:382) at org.apache.fop.svg.SVGArea.render(SVGArea.java:58) at org.apache.fop.render.pdf.PDFRenderer.renderForeignObjectArea(PDFRenderer.java:366) at org.apache.fop.layout.inline.ForeignObjectArea.render(ForeignObjectArea.java:50) at org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRenderer.java:223) at org.apache.fop.layout.LineArea.render(LineArea.java:162) at org.apache.fop.render.AbstractRenderer.renderBlockArea(AbstractRenderer.java:192) at org.apache.fop.layout.BlockArea.render(BlockArea.java:82) at org.apache.fop.render.AbstractRenderer.renderAreaContainer(AbstractRenderer.java:158) at org.apache.fop.layout.ColumnArea.render(ColumnArea.java:33) at org.apache.fop.render.AbstractRenderer.renderSpanArea(AbstractRenderer.java:58) at org.apache.fop.layout.SpanArea.render(SpanArea.java:53) at org.apache.fop.render.AbstractRenderer.renderBodyAreaContainer(AbstractRenderer.java:114) at org.apache.fop.render.pdf.PDFRenderer.renderPage(PDFRenderer.java:728) at org.apache.fop.render.pdf.PDFRenderer.render(PDFRenderer.java:696) at org.apache.fop.apps.StreamRenderer.queuePage(StreamRenderer.java:206) at org.apache.fop.layout.AreaTree.addPage(AreaTree.java:81) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:305) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:191) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:178) at org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1398) at org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator.java:1019) at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1256) at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381) at
Simple extension problem
Greetings all,
I'm learning to write extensions and I'm trying to start simple.
I think I've followed the directions on the Extensions page
(http://xml.apache.org/fop/extensions.html), but something
is still missing or incorrect.
I'm using JDK build 1.4.0-beta3-b84 with Fop0.20.2 on
Windows 2000, Service Pack 3.
I have a Java class to simply output the Date in the default
locale. Eventually I'll need to get content from log files and
database tables, etc., but I just want to see output from my
extension class show up in the rendered result right now.
I have an ElementMapping subclass that parallels
the functionality used to support the fox:label tag.
I have a single line of text in the text file
META-INF/services/org.apache.fop.fo.ElementMapping
with the fully qualified class name for that ElementMapping
subclass:
gov.census.geo.pob.fop.extensions.TimeDisplayMapping
I stored the jar in my Fop-0.20.2\lib\ directory.
My stylesheet element includes the attributes
xmlns:pob=http://jgilvary.geo.census.gov/;
extension-element-prefixes=pob
When I try to use pob:time / in the fo file, there is no output
in pdf or awt. There are no more error messages about
Transformer errors or ClassNotFoundExceptions, so I
think I'm getting closer. Everything else I do in that file
works (png images, pdf bookmarks and internal links),
so I believe the set up is correct.
I'm doing something wrong or not doing something right G
Any help greatly appreciated.
Thanks,
Joe
Functionality class source code:
package gov.census.geo.pob.fop.extensions;
import org.apache.fop.fo.*;
import org.apache.fop.extensions.*;
import java.util.Date;
import java.text.SimpleDateFormat;
public class TimeDisplay extends ExtensionObj {
private String today = (new SimpleDateFormat()).format(new Date());
public static class Maker extends FObj.Maker {
public FObj make(FObj parent, PropertyList propertyList) {
return new TimeDisplay(parent, propertyList);
}
}
public static FObj.Maker maker() {
return new TimeDisplay.Maker();
}
public TimeDisplay(FObj parent, PropertyList propertyList) {
super(parent, propertyList);
}
public String toString(){
return (today);
}
}
ElementMapping subclass source code:
package gov.census.geo.pob.fop.extensions;
import org.apache.fop.fo.*;
import org.apache.fop.fo.properties.ExtensionPropertyMapping;
import org.apache.fop.fo.TreeBuilder;
import java.util.Enumeration;
import java.util.HashMap;
import java.util.Iterator;
public class TimeDisplayMapping implements ElementMapping {
public final static String URI = http://jgilvary.geo.census.gov/;;
private static HashMap foObjs = null;
public synchronized void addToBuilder(TreeBuilder builder) {
if(foObjs == null) {
foObjs = new HashMap();
foObjs.put(time, TimeDisplay.maker());
}
builder.addMapping(URI, foObjs);
builder.addPropertyList(URI,
ExtensionPropertyMapping.getGenericMappings
());
/* Add any element mappings */
for (Iterator iter = ExtensionPropertyMapping.getElementMappings
().iterator();
iter.hasNext(); ) {
String elem = (String)iter.next();
builder.addElementPropertyList(URI, elem,
ExtensionPropertyMapping.getElementMapping(elem));
}
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: Fill pattern problem
Hi, Have you tried the svg standalone though batik. The exception is being thrown by batik. It looks like a problem where batik causes a class cast exception when an image cannot be found (ie. file:///m:/overlay.txt is wrong). The problem is that batik tries to load a broken image svg from within batik. When it tries to load this image it uses the default xml parser (which is wrong) and then cannot load it, so it uses a simple svg instead. In another part it gets a graphics hint from the image's object but java incorrectly returns an Object instead of null then the class cast exception occurs as it expects another type of object that is only with the brocken link image. So the result is that batik was fixed to handle this better and FOP sets the default xml parser on batik. If I remember correctly this was in the last release. On 2001.11.30 16:15 James Richardson wrote: Hi, The following svg file crashes out the PDF renderer I hand wrote the file, so I dont know if is a bug in the XML. Adobe's plugin seems to render it OK. ?xml version=1.0 encoding=iso-8859-1? !DOCTYPE svg PUBLIC -//W3C//DTD SVG 2303 Stylable//EN http://www.w3.org/TR/2000/03/WD-SVG-2303/DTD/svg-2303-stylable.dtd; svg xml-space=preserve preserveAspectRatio=xMaxYMaxmeet xmlns:svg=http://www.w3.org/2000/svg; defs pattern id=pattern x=0 y=0 patternUnits=userSpaceOnUse width=185 height=200 g transform=rotate(45 100 15) translate(50 50) g fill=#66 stroke=#66 text x=0 y=33.75 font-family=Helvetica font-size=20Pattern Fill/text /g /g /pattern /defs g id=overlay opacity=0.50 rect x=0 y=0 width=900 height=470 fill=url(#pattern) stroke=black stroke-width=0 /g /svg Heres the FO ?xml version=1.0 encoding=UTF-8? fo:root font-family=Univers font-size=9pt text-align=center xmlns:fo =http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin-bottom=25pt margin-left=100pt margin-right=50pt margin-top=75pt master-name=simple page-height =210mm page-width=297mm fo:region-body margin-bottom=50pt/ fo:region-after extent=25pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-name=simple fo:static-content flow-name=xsl-region-after fo:block font-size=7pt text-align-last=center fo:page-number/ /fo:block /fo:static-content fo:flow flow-name=xsl-region-body fo:block fo:instream-foreign-object svg:svg height=150mm width=250mm xmlns:svg =http://www.w3.org/2000/svg; svg:image height=478 transform =scale(0.6) width=1145 xlink:href=file:///m:/overlay.txt/ /svg:svg /fo:instream-foreign-object /fo:block /fo:flow /fo:page-sequence /fo:root org.apache.fop.apps.Fop svgtest.fo svgtest.pdf [INFO]: FOP 0.20.2 [INFO]: building formatting object tree [INFO]: [1] [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: unknown font Univers,normal,normal so defaulted font to any [ERROR]: svg graphic could not be built: java.lang.Object java.lang.ClassCastException: java.lang.Object at org.apache.batik.bridge.SVGImageElementBridge.createRasterImageNode(SVGImageElementBridge.java:167) at org.apache.batik.bridge.SVGImageElementBridge.createGraphicsNode(SVGImageElementBridge.java:109) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:167) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:133) at org.apache.batik.bridge.GVTBuilder.build(GVTBuilder.java:66) at org.apache.fop.render.pdf.PDFRenderer.renderSVGDocument(PDFRenderer.java:413) at org.apache.fop.render.pdf.PDFRenderer.renderSVGArea(PDFRenderer.java:382) at org.apache.fop.svg.SVGArea.render(SVGArea.java:58) at org.apache.fop.render.pdf.PDFRenderer.renderForeignObjectArea(PDFRenderer.java:366) at org.apache.fop.layout.inline.ForeignObjectArea.render(ForeignObjectArea.java:50) at org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRenderer.java:223) at org.apache.fop.layout.LineArea.render(LineArea.java:162) at org.apache.fop.render.AbstractRenderer.renderBlockArea(AbstractRenderer.java:192) at org.apache.fop.layout.BlockArea.render(BlockArea.java:82) at org.apache.fop.render.AbstractRenderer.renderAreaContainer(AbstractRenderer.java:158) at org.apache.fop.layout.ColumnArea.render(ColumnArea.java:33) at org.apache.fop.render.AbstractRenderer.renderSpanArea(AbstractRenderer.java:58) at org.apache.fop.layout.SpanArea.render(SpanArea.java:53) at
Re: Added letter-spacing support to Fop
Hi Raymond, I appreciate your patch. I have had a quick look at it appears that it would do the right thing. One thing is that for the pdf renderer I think there might be a better way to specify the character spacing (Tc operator I think). As far as getting it into the current cvs, the problem is that the current cvs has changed a great deal since 0.20.2 and we are working the basic way that FOP handles fo and ultimately creates the output. Your changes would be useable but only some of it can be put into the current cvs. The main problem is that a fair amount of work needs to be done before FOP will do anything useful and most of the people who have been doing this don't have the time at the moment. It is a priority to get FOP to a stage where everyone can understand what is happening and to be able to contribute individual pieces of work (such as your patch) that will improve FOP. The options area: - put your patch on the maintenence brach and sometime soon do a maintanence release - you could make the patch for the current cvs, only about half will be possible and it will not work for a while - you could help out with getting current cvs to work I release there are no quick solutions but this is something that has to be done to make FOP better in the long term. Thanks, Keiron. On 2001.11.30 15:37 Raymond Penners wrote: Hi, I've added support for the 'letter-spacing' property. A patch to fop 0.20.2, and a test case are added to this mail. I would really appreciate some feedback on this. For example, what changes are necessary to get letter-spacing support integrated into CVS. Thanks, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fill pattern problem
Keiron Liddle wrote: Hi, Have you tried the svg standalone though batik. The exception is being thrown by batik. It looks like a problem where batik causes a class cast exception when an image cannot be found (ie. file:///m:/overlay.txt is wrong). My apologies, I didn't explain. The given SVG file was saved as m:/overlay.txt. I will try Batik by itself.then maybe hop to the Batik mailinglist. Cheers! James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP conformance
On 2001.11.30 15:39 Elliotte Rusty Harold wrote: At 4:48 PM -0400 11/29/01, Arved Sandstrom wrote: This was already a known thing, and Norman Walsh pointed it out also. There is simply no point in fixing this until the FOP rewrite emerges. That's your choice. However, you should realize that this is going to cause a lot of confusion for many users. It basically condemns FOP to irrelevance until the rewrite is finished. I'm personally going to have pull references to FOP out of the online XML Bible chapters and the next edition of XML in a Nutshell, and switch my own toolchains over to PassiveTeX. Although this is a small change conceptually, it is one that affects pretty much *every* XSL-FO document anyone is ever going to write. FOP has a large mindshare because it was first and because it is open source. Leaving this minor change until the rewrite is done is pretty much going to abandon the competitive advantages FOP has gained by being first. People will move to PassiveTeX, XEP, Antenna House, and other products instead. If that's OK with you, then that's your choice. Just make sure this is in fact what you want to happen. To put it another way. I could keep doing all the small things for everyone while telling them that a whole set of problems will be solved at some indefinite time in the future which keeps getting further away. This will also eventually condemn FOP to irrelevance. Doing that will also mean that other people are not able to get involved with FOP as there is a major change that needs to happen to get many things working properly. If people really insist then I can make a release soon. This will delay any other important improvements. If someone else really thinks there are things that need doing then I strongly suggest that you get busy and do them. Does anyone else have any better suggestions? I would be glad to hear them. Regards, Keiron. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fill pattern problem
Please excuse my stupidity I had the following in the SVG: g id=overlay opacity=0.07 rect x=0 y=0 width=900 height=470 fill=url(#pattern) stroke=black stroke-width=0 /g Note lack of end tag for the rect Still, the error msg threw me a little. Cheers! James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP conformance
Keiron Liddle wrote: On 2001.11.30 15:39 Elliotte Rusty Harold wrote: At 4:48 PM -0400 11/29/01, Arved Sandstrom wrote: This was already a known thing, and Norman Walsh pointed it out also. There is simply no point in fixing this until the FOP rewrite emerges. That's your choice. However, you should realize that this is going to cause a lot of confusion for many users. It basically condemns FOP to irrelevance until the rewrite is finished. I'm personally going to have pull references to FOP out of the online XML Bible chapters and the next edition of XML in a Nutshell, and switch my own toolchains over to PassiveTeX. Although this is a small change conceptually, it is one that affects pretty much *every* XSL-FO document anyone is ever going to write. [..] If someone else really thinks there are things that need doing then I strongly suggest that you get busy and do them. Does anyone else have any better suggestions? I would be glad to hear them. I think too we should do a maintenance release (from 'fop-0_20_2-maintain' branch). I volunteer to do the necessary patches, do some testing etc. Regards, Keiron. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP conformance
Hi All: Actually I was not implying or suggesting that you correct FOP and make it work for just the page-reference property, that will be a minor change on the great scheme of things, however if you have a number of minor things, it eventually adds up to a lot of things. On my particular case, I will be unable to take advantage of all the wonderful things FOP has to offer. It will be nice to check the tests (I think we will have thousands of tests) against various implementations. I guess my point is that even if FOP does not have those minor things at this point, maybe it can have them at some not too distant future. Greetings Carmelo Montanez - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Merging jfor into FOP - what's the plan?
On Thursday 29 November 2001 12:44, Keiron Liddle wrote: So are things like static areas, markers, page numbers etc. possible with rtf or are these type of things simply not possible. Keiron, as far as I know, RTF does support the following (but jfor currently not for most of these things) - In parentheses, my understanding of these concepts, to make sure we're on the same wavelength: static areas - yes (headers and footers) markers - yes (references like see page N) page numbers - yes (dynamic auto-numbering) But things like page numbers must be left to RTF to compute, FOP will need to include an *RTF code* to let the RTF reader compute page numbers, not compute them by itself. - Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Jaggies
When rendering my previous post, Batik seems to be able to render fine in the GUI, but when included in FOP ( either as external graphic, or instream foreign object ), the rendered text has the most ugly jaggies. I think I read in the archive that FOP rasterises the SVG before inserting into the PDF. Is this right? Why? Can this be turned off? Cheers! James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
unsubcribe
plz can any body tell me , how to unsbsribe from this list I have tried to send a mail to this link [EMAIL PROTECTED] i got the confirmation also but still i am getting mails thanks Maneshi Tuli 212-454-1646 (O) 732 -882-0353(H) -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP conformance
Hi, Christian That would be much appreciated. As before, I can do the actual release itself once someone has notified me (read the list) that they think the time is right. As regards the topic in general, I support Keiron 100%. The entire point of the rewrite is that during the process things are in limbo...this was well understood before, or so I thought. Making improvements to a pre-rewrite release such as FOP-0.20.2 should not use any cycles from the most productive coders we currently have on this project. IMHO. Which is why having others chip in is much appreciated. I can spare enough time to support commits to FOP-0.20.2, and minor work, since I am currently most definitely _not_ a productive coder. :-) I'd plead time pressure, which has been a major factor, but to be honest what I have really been much of this year is simply burnt out on Java. I am much less enthused about it than I was before, and for the past 2 years, after using it at work every single day (J2EE, J2ME) I hardly wanted to use it again in my own time. I say that simply so the other committers become aware of what the situation is. I have most definitely not lost interest in FOP or XSL-FO - I just need a rest from Java, rather badly. But in any case I can support minor work such as this maintenance release. I am currently working on a contract which has absolutely zero to do with Java and XML (it's SQL, C++, ASP), which is so refreshing that I cannot even begin to describe it. :-) Hopefully that'll clear my head and allow me to get back into Java coding again. Regards, Arved Sandstrom - Original Message - From: Christian Geisert [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 30, 2001 12:27 PM Subject: Re: FOP conformance Keiron Liddle wrote: On 2001.11.30 15:39 Elliotte Rusty Harold wrote: At 4:48 PM -0400 11/29/01, Arved Sandstrom wrote: This was already a known thing, and Norman Walsh pointed it out also. There is simply no point in fixing this until the FOP rewrite emerges. That's your choice. However, you should realize that this is going to cause a lot of confusion for many users. It basically condemns FOP to irrelevance until the rewrite is finished. I'm personally going to have pull references to FOP out of the online XML Bible chapters and the next edition of XML in a Nutshell, and switch my own toolchains over to PassiveTeX. Although this is a small change conceptually, it is one that affects pretty much *every* XSL-FO document anyone is ever going to write. [..] If someone else really thinks there are things that need doing then I strongly suggest that you get busy and do them. Does anyone else have any better suggestions? I would be glad to hear them. I think too we should do a maintenance release (from 'fop-0_20_2-maintain' branch). I volunteer to do the necessary patches, do some testing etc. Regards, Keiron. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP conformance
At 1:19 PM -0400 11/30/01, Arved Sandstrom wrote: As regards the topic in general, I support Keiron 100%. The entire point of the rewrite is that during the process things are in limbo...this was well understood before, or so I thought. It was understood. However, there was an implicit assumption that XSL-FO was stable enough that FOP 0.20-2 would continue to work as well as it ever had. When XSL 1.0 was released, that assumption proved to be false. That's not the fault of anybody here, just life on the bleeding edge. As other projects like DocBook start upgrading their stylesheets to support the final XSL 1.0 recommendation, then FOP stops working where it worked before. This means users need to make a decision between supporting the tools that work with XSL 1.0 and FOP. Nobody here anticipated this. Note that I am specifically talking about the change from the master-name to master-reference attribute, not the various other patches that have been submitted to 0.20-2. While useful, those patches aren't as important. The master-name/master-reference affects all XSL-FO documents, and means that FOP is totally non-functional. This is not a case of not supporting this feature in these stylesheets or that feature in those stylesheets. FOP will not produce any output when presented with an XSL 1.0 stylesheet. It cannot be used. -- +---++---+ | Elliotte Rusty Harold | [EMAIL PROTECTED] | Writer/Programmer | +---++---+ | The XML Bible, 2nd Edition (Hungry Minds, 2001) | | http://www.ibiblio.org/xml/books/bible2/ | | http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/ | +--+-+ | Read Cafe au Lait for Java News: http://www.cafeaulait.org/ | | Read Cafe con Leche for XML News: http://www.ibiblio.org/xml/ | +--+-+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP conformance
And between me and Christian I think we will see to it that this change, at least, gets done and is reflected in a maintenance release, which I suggest should appear NLT Dec 15. In other words, I accept your argument (that was never in question). It's a resource thing...Keiron and Karen (and some others, such as Peter West) are looking at the rewrite, so it's up to the rest of us to do stuff like this. AHS - Original Message - From: Elliotte Rusty Harold [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 30, 2001 12:47 PM Subject: Re: FOP conformance At 1:19 PM -0400 11/30/01, Arved Sandstrom wrote: As regards the topic in general, I support Keiron 100%. The entire point of the rewrite is that during the process things are in limbo...this was well understood before, or so I thought. It was understood. However, there was an implicit assumption that XSL-FO was stable enough that FOP 0.20-2 would continue to work as well as it ever had. When XSL 1.0 was released, that assumption proved to be false. That's not the fault of anybody here, just life on the bleeding edge. As other projects like DocBook start upgrading their stylesheets to support the final XSL 1.0 recommendation, then FOP stops working where it worked before. This means users need to make a decision between supporting the tools that work with XSL 1.0 and FOP. Nobody here anticipated this. Note that I am specifically talking about the change from the master-name to master-reference attribute, not the various other patches that have been submitted to 0.20-2. While useful, those patches aren't as important. The master-name/master-reference affects all XSL-FO documents, and means that FOP is totally non-functional. This is not a case of not supporting this feature in these stylesheets or that feature in those stylesheets. FOP will not produce any output when presented with an XSL 1.0 stylesheet. It cannot be used. -- +---++---+ | Elliotte Rusty Harold | [EMAIL PROTECTED] | Writer/Programmer | +---++---+ | The XML Bible, 2nd Edition (Hungry Minds, 2001) | | http://www.ibiblio.org/xml/books/bible2/ | | http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/ | +--+-+ | Read Cafe au Lait for Java News: http://www.cafeaulait.org/ | | Read Cafe con Leche for XML News: http://www.ibiblio.org/xml/ | +--+-+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
fo:external-graphic question
Has anyone figured out a way to use a relative path with the file:... protocol in fo:external-graphic? The path below works on my Unix boxes. The probem is I develop in an NT box and I'm getting tired of changing my stylesheets every time I upload to the staging or porduction servers. This is the full path which works: fo:external-graphic src=file:///usr/local/weblogic/config/isappdev/applications/RVWebApp1/WEB-I NF/lib/ClinTrialLogoGreenBig.gif / But every time I try to use something like this: fo:external-graphic src=file://./config/isappdev/applications/RVWebApp1/WEB-INF/lib/ClinTrialLo goGreenBig.gif / I get this error: Error while creating area : Invalid Image URL - error on relative URL : no protocol: null/config/isap pdev/applications/RVWebApp1/WEB-INF/lib/ClinTrialLogoGreenBig.gif By the way I still haven't found a way to get the file protocol to work on NT. I have to use HTTP. I could use HTTP on the Unix boxes, but I'd still have to change the port every time. Any ideas, even a pointer would be greatly appreciated. Matt Savino - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP conformance
Tell me where to look, and I'll take a crack at it. I ran into this while trying to use FOP, and switched to the simple-page-master to make it work. Thanks Scott Sanders -Original Message- From: Arved Sandstrom [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 10:03 AM To: [EMAIL PROTECTED] Subject: Re: FOP conformance And between me and Christian I think we will see to it that this change, at least, gets done and is reflected in a maintenance release, which I suggest should appear NLT Dec 15. In other words, I accept your argument (that was never in question). It's a resource thing...Keiron and Karen (and some others, such as Peter West) are looking at the rewrite, so it's up to the rest of us to do stuff like this. AHS - Original Message - From: Elliotte Rusty Harold [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 30, 2001 12:47 PM Subject: Re: FOP conformance At 1:19 PM -0400 11/30/01, Arved Sandstrom wrote: As regards the topic in general, I support Keiron 100%. The entire point of the rewrite is that during the process things are in limbo...this was well understood before, or so I thought. It was understood. However, there was an implicit assumption that XSL-FO was stable enough that FOP 0.20-2 would continue to work as well as it ever had. When XSL 1.0 was released, that assumption proved to be false. That's not the fault of anybody here, just life on the bleeding edge. As other projects like DocBook start upgrading their stylesheets to support the final XSL 1.0 recommendation, then FOP stops working where it worked before. This means users need to make a decision between supporting the tools that work with XSL 1.0 and FOP. Nobody here anticipated this. Note that I am specifically talking about the change from the master-name to master-reference attribute, not the various other patches that have been submitted to 0.20-2. While useful, those patches aren't as important. The master-name/master-reference affects all XSL-FO documents, and means that FOP is totally non-functional. This is not a case of not supporting this feature in these stylesheets or that feature in those stylesheets. FOP will not produce any output when presented with an XSL 1.0 stylesheet. It cannot be used. -- +---++---+ | Elliotte Rusty Harold | [EMAIL PROTECTED] | Writer/Programmer | +---++---+ | The XML Bible, 2nd Edition (Hungry Minds, 2001) | | http://www.ibiblio.org/xml/books/bible2/ | | http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/ | +--+-+ | Read Cafe au Lait for Java News: http://www.cafeaulait.org/ | | Read Cafe con Leche for XML News: http://www.ibiblio.org/xml/ | +--+-+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AW: AW: Non existent tag error...
So I am not totally clear then, does Darrens method check to see if the tag exists then? Anyways, I am still getting the XPath error with his method. Any other suggestions? Thanks, Bryan --- Beer, Christian [EMAIL PROTECTED] wrote: Hi Darren! That's not completely righ. Your tests check if the attribute named tagname exists, not the tag named tagname. Christian -Ursprüngliche Nachricht- Von: Darren Munt [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 29. November 2001 23:18 An: '[EMAIL PROTECTED]' Betreff: RE: AW: Non existent tag error... I've found that the test needs to encompass three possibilities: 1. That the tag is not present; 2. That the tag is empty (ie. tagname=''), or; 3. That the tag is present and contains a value. If you use test=@tagname, the test will be true in cases 2 and 3. However, if you use test=not(@tagname='') (or test=@tagname!='') then it will only be true for case 3, at least this is the case with the parser I use. So it depends on whether or not you want different behaviour when the tag is missing than you want when the tag is present but empty. -Original Message- From: bryan hansen [mailto:[EMAIL PROTECTED]] Sent: Friday, 30 November 2001 2:09 To: [EMAIL PROTECTED] Subject: Re: AW: Non existent tag error... I did not solve the problem, I was going to add the line that I said oops on in the original message, sorry for the confusion. I will try this and see if it works. Thanks, Bryan --- Beer, Christian [EMAIL PROTECTED] wrote: Hi Bryan, did you solve the problem, or what does the oops mean?? Anyway: xsl:when test=Transaction/Filing/OldFilingNumber != '' is not right, I think! Try: xsl:when test=Transaction/Filing/OldFilingNumber That is the right term, the book says so. Christian -Ursprüngliche Nachricht- Von: bryan hansen [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 28. November 2001 18:16 An: [EMAIL PROTECTED] Betreff: Re: Non existent tag error... Oops, line 87 is the line that does the xsl:when test! Bryan --- bryan hansen [EMAIL PROTECTED] wrote: I have some xsl that checks to see if a tag does not exist: fo:table-cell fo:block text-align=start xsl:choose xsl:when test=Transaction/Filing/OldFilingNumber != '' xsl:value-of select=Transaction/Filing/OldFilingNumber/ /xsl:when xsl:otherwise N/A /xsl:otherwise /xsl:choose /fo:block /fo:table-cell This was working correctly, but now I am getting an error: ; SystemID: http://utstbrucc2/ucc-ack.fo.xsl; Line#: 87; Column#: -1 javax.xml.transform.TransformerException: Unknown error in XPath The only thing that has changed was that I reinstalled fop? Am I missing a required jar or have a different version that would make this stop working? __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: no visual tool for FOP?
Like FOP html2fo is still under development. It is stable but not complete. You are welcome to send me a list of html tags you want to be supported - or even better a sample file where they are used. Enrico Am Donnerstag, 22. November 2001 19:43 schrieben Sie: I am interested in most html2pdf, html2fo, but after I tried any of them, i am frustrated. some very lame ones support only 3 tags even. so i am wondering this tool support all html tags specified in HTML 4.0 DTD? On Sat, 17 Nov 2001, Enrico Schnepel wrote: Hello I've developed a tool html2fo for conversion of .html files to .fo. http://html2fo.sourceforge.net A similar tool is WH2FO at http://www-uk.hpl.hp.com/people/fabgia/wh2fo/wh2fo.html WH2FO is optimized for Word 2000 html files - html2fo is more general. Enrico Am Freitag, 16. November 2001 21:45 schrieben Sie: XMLSpy 4.1 has FO transformation built in as an option under the XSL menu. All you have to do is point it to FOP.bat. I guess you could call this a visual tool. But I'm going to guess that what the original poster is looking for is some kind of a WYSIWIG PDF editor that manipulates the underlying FO? That would be a pretty intense project. Do you think Adobe will ever implement a built-in fop processor? The Acrobat plug-in could come to life any time the browser comes across a .fo file, just like it does now when it sees a .pdf. Any pages that require precise coloring, layout, pagination, etc. would be candidates for conversion from html to fo. Definitely some interesting possibilities here. I suppose people could be doing the same thing now if they have Exchange, but when you can make little changes through a text editor it's a lot more convenient. You'd think they'd be all for it since it could drastically increase PDF viewing on the web. Although I guess it could cut into sales of their full-version Acrobat (what used to be called Exchange). So what part of it would they sell? Hmmm. Can even they do this within the licensing rules of this project? -Matt -Original Message- From: Charles Palmer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 13, 2001 1:56 AM To: [EMAIL PROTECTED] Subject: RE: no visual tool for FOP? Hi team This is also something I am curious about. Here are two embryonic ideas - can anyone see any merit in them? 1 XMLSpy seems to have the ability to convert a Word document to XML. Could XSLT be used to transform this XML to FO, and thence to PDF? Then Word could be used as the visual tool. 2 Sun's new Star Office apparently saves files as XML (see http://xml.coverpages.org/starOfficeXML.html ). Could the word processor from StarOffice be used as the visual tool? By the way, XMLSpy mentions support or fop - does anyone have experience with this? Regards - Charles Palmer Technical Director, DSP Design Ltd email: [EMAIL PROTECTED] 7 Tapton Park Innovation Centre, Brimington Rd, Chesterfield S41 0TZ, UK ph: +44 (0) 1246 545 918 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Pre Formatted Text
Hello Jim, try: fo:block white-space-collapse=false YOUR TEXT INCLUDING LF's AND SPACES /fo:block Regards Enrico Am Freitag, 30. November 2001 14:55 schrieben Sie: I am using FOP to generate PDFs on the fly from XML. One of my XML elements contains a large (1K - 1M) preformatted (contains LFs) block of text. When I display this field in HTML I use a PRE tag. Is there a FO tag that FOP supports that functions similarly? Thanks, Jim Urban Product Manager Netsteps Inc. Suite 505E 1 Pierce Pl. Itasca, IL 60143 Voice: (630) 250-3045 x2164 Fax: (630) 250-3046 Content-Type: application/ms-tnef; charset=iso-8859-1; name=winmail.dat Content-Transfer-Encoding: base64 Content-Description: Content-Type: text/plain; charset=us-ascii; name=Anhang: 2 Content-Transfer-Encoding: 7bit Content-Description: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: fo:external-graphic question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 10:28 30-11-2001, Savino, Matt C wrote: But every time I try to use something like this: fo:external-graphic src=file://./config/isappdev/applications/RVWebApp1/WEB-INF/lib/ClinTrialLo goGreenBig.gif / I wouldn't expect that to work; that says make a file connection to the host '.', which is the root of the entire Internet. If you want a relative URI, why not just use a relative URI? I.e., src=config/isappdev/applications/RVWebApp1/WEB-INF/lib/ClinTrialLogoGreenBig.gif? Then the current protocol, host, and directory will be used as the base URI and the relative URI interpreted relative to that. ~Chris - -- Christopher R. Maden, Principal Consultant, HMM Consulting Int'l, Inc. DTDs/schemas - conversion - ebooks - publishing - Web - B2B - training URL: http://www.hmmci.com/ URL: http://crism.maden.org/consulting/ PGP Fingerprint: BBA6 4085 DED0 E176 D6D4 5DFC AC52 F825 AFEC 58DA -BEGIN PGP SIGNATURE- Version: PGP Personal Privacy 6.5.8 iQA/AwUBPAiLHKxS+CWv7FjaEQJr5wCdEwscbmOp7ol0fOokVKmMTAcJhwQAn0o6 ubOxz9sc2W5+AWugaMWMAbkm =BJwq -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
