Re: Merging jfor into FOP - what's the plan?
On 2001.11.27 12:40 Bertrand Delacretaz wrote: Without knowing too much about FOP internals, I think a processing chain along these lines might help: parsing if needed - SAX events - FO attributes processing (validation, inheritance) - StructureRenderer StructureRenderer is EITHER Layout + PrintRenderer OR StructureProcessor (RTF, MIF, etc.) What we need to find out is how much the existing FOP and these structure renderers have in common. This sounds like the sort of approach that we need. If possible we might be able to have a layout processor which normally reads the fo objects and creates an area tree. An alternate implementation will instead directly create the output document. The fo object tree does all the handling of attributes. So are things like static areas, markers, page numbers etc. possible with rtf or are these type of things simply not possible. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Driver API Suggestion
Hi,
as a former (0.19 was running fine) and future user (hope I
get 0.20.2 up again, 0.20.1 was kind of a mess in my environment)
of fop I'd first like to thank for it. Great work!
Second I have a question on the API of the Driver Object, which
is a bit about aesthetic
Deep within a XSLT Framework we use, I have code like
// -1-
Result outResult = obtainResult(mime, status, out);
transformer.setErrorListener(this);
transformer.transform(source, outResult);
// -2-
if ( status.getDriver() != null ) {
status.getDriver().format();
status.getDriver().render();
}
with obtainResult() containing different branches e.g. like this
Driver driver = new Driver();
driver.setRenderer(Driver.RENDER_PDF);
driver.setOutputStream(out);
status.setDriver(driver); // - -2-
return new SAXResult(driver.getContentHandler());
-1- is fairly generic in the sense that different kinds of
sources and different kinds of results can be processed.
-2- is what I don't like. Actually the status object is the problem
since its main purpose in this sequence is to store additional
information about the Driver object, s.th. which is not needed for
most of the other Result objects used at this point within out
Framework.
If the the driver.getContentHandler() would return an object which
would automatically start the format() and render() after the
endDocument() has been fired, this would be very convenient in above
use case.
So I wonder if it would be useful for more people to have s.th. like a
Driver.getContentHandler(boolean autoRender)
method, which eigher returns a normal ContentHandler or one which
automatically formats and renders. Actually I haven't get a usecase
for autoRender = false arround here yet.
Thanks for your patience and reading till here.
Frank
--
Dr. Frank Sven Nestel
Principal Software Engineer
COI GmbHErlanger Straße 62, D-91074 Herzogenaurach
Phone +49 (0) 9132 82 4611
http://www.coi.de, mailto:[EMAIL PROTECTED]
COI - Solutions for Documents
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: CVS snapshot does not render
Can you send me your JAVA_HOME, build.bat and fo.bat? another question: has you a class as follow? org.apache.fop.fo.properties.Precedence my jdk raise this Class not found, so I don't know where I can retreive it. Seems it's missing together with other hundred classes! Thanks. Antonio. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Please help me to solve strange space problem in fo:block
Hi I am generating a simple document with fixed font family. If the fo:block contains the new line( with the space collapsed), then the next line in PDF is shifted by one character length to the right. FO: fo:page-sequence master-name=simplePM fo:flow flow-name=xsl-region-body fo:block font-family=Courier white-space-collapse=falseThis is a simple fo block. Hello World/fo:block fo:block font-family=Courier wrap-option=no-wrap white-space-collapse=falseThis is a simple fo block. Hello World/fo:block /fo:flow Please look at the attachments for details of FO and PDF. Is it a bug? Or am I writing the invalid XSL FO? Please somebody can look at it. block.pdf block.fo Thanks Mahendar This message is confidential and may also be legally privileged. If you are not the intended recipient, please notify us immediately. You should not copy it or use it for any purpose, nor disclose it's contents to any other person. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of Wilco International. block.pdf Description: Binary data block.fo Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
patch: added support for letter-spacing
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, especially from one of the core developers. Thanks, -- Raymond Penners ?xml version=1.0 encoding=utf-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set !-- layout information -- fo:simple-page-master master-name=simple page-height=29.7cm page-width=21cm margin-top=1cm margin-bottom=2cm margin-left=2.5cm margin-right=2.5cm fo:region-body margin-top=3cm/ fo:region-before extent=3cm/ fo:region-after extent=1.5cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-name=simple fo:flow flow-name=xsl-region-body fo:table fo:table-column column-width=1cm/ fo:table-column column-width=1cm/ fo:table-column column-width=1cm/ fo:table-column column-width=1cm/ fo:table-column column-width=1cm/ fo:table-column column-width=1cm/ fo:table-column column-width=1cm/ fo:table-column column-width=1cm/ fo:table-body fo:table-row line-height=2cm fo:table-cell border-width=.1pt border-left-style=solid fo:block0/fo:block /fo:table-cell fo:table-cell border-width=.1pt border-left-style=solid fo:block1/fo:block /fo:table-cell fo:table-cell border-width=.1pt border-left-style=solid fo:block2/fo:block /fo:table-cell fo:table-cell border-width=.1pt border-left-style=solid fo:block3/fo:block /fo:table-cell fo:table-cell border-width=.1pt border-left-style=solid fo:block4/fo:block /fo:table-cell fo:table-cell border-width=.1pt border-left-style=solid fo:block5/fo:block /fo:table-cell fo:table-cell border-width=.1pt border-left-style=solid fo:block6/fo:block /fo:table-cell fo:table-cell border-width=.1pt border-left-style=solid fo:block7/fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table fo:block font-size=12pt font-family=sans-serif line-height=15pt space-after.optimum=3pt text-align=justify ABCABCABCABCABCABCABCABCDEF /fo:block fo:block font-size=12pt font-family=sans-serif line-height=15pt space-after.optimum=3pt text-align=justify letter-spacing=.5cm ABCABCABCABCABCABCABCABCDEF /fo:block fo:block font-size=12pt font-family=sans-serif line-height=15pt space-after.optimum=3pt text-align=justify letter-spacing=1cm ABCABCABCABCABCABCABCABCDEF /fo:block fo:block font-size=12pt font-family=sans-serif line-height=15pt space-after.optimum=3pt text-align=justify letter-spacing=2cm ABCABCABCABCABCABCABCABCD /fo:block !-- this defines normal text -- fo:block font-size=12pt font-family=sans-serif line-height=15pt space-after.optimum=3pt text-align=justify letter-spacing=3cm ABCABCABCABCABCABCABCABCD /fo:block !-- this defines normal text -- fo:block font-size=12pt font-family=sans-serif line-height=15pt space-after.optimum=3pt text-align=justify letter-spacing=4cm ABCABCABCABCABCABCABCABC /fo:block !-- this defines normal text -- fo:block font-size=12pt font-family=sans-serif line-height=15pt space-after.optimum=3pt text-align=justify letter-spacing=5cm ABCABCABCABCABCABCABCABC /fo:block fo:block-container background-color=blue width=3cm height=3cm fo:blockX /fo:block /fo:block-container /fo:flow /fo:page-sequence /fo:root diff -u -r Fop-0.20.2/src/codegen/foproperties.xml Fop-0.20.2.dlx/src/codegen/foproperties.xml --- Fop-0.20.2/src/codegen/foproperties.xml Sat Sep 29 21:28:48 2001 +++ Fop-0.20.2.dlx/src/codegen/foproperties.xml Thu Nov 29 13:33:14 2001 @@ -1190,8 +1190,8 @@ property nameletter-spacing/name inheritedtrue/inherited -datatypeToBeImplemented/datatype -defaultnormal/default +datatypeLength/datatype +default0pt/default /property property namesuppress-at-line-break/name Only in
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]
Fw: xslt and number formats
Sorry this is probably not the most appropriate forum, but I have looked everywhere I can think of. If anyone on this list can point me in the right direction I would be grateful. Thanks, Brian - Original Message - From: Brian T. Wolf [EMAIL PROTECTED] Newsgroups: comp.text.xml Sent: Tuesday, November 27, 2001 2:04 PM Subject: xslt and number formats OK, I am at my wits' end. I have looked at various sites, specs, and FAQ's, and I just am not getting an understanding of number formatting. I am using templates to transform my XML data into a table after which I will have column totals. I am using the sum() function and the math seems to be working as expected - with one minor hitch: the decimals are being truncated. Since I am printing invoices dealing with currency it is essential that the decimals remain down to the penny. Can someone explain this in clear English for me, or else point me somewhere I may not have yet seen? sample XML: taxes tax_item descriptionFederal Excise Tax/description amount2.25/amount /tax_item tax_item descriptionState 911 Emergency Tax/description amount0.54/amount /tax_item /taxes sample XSL: xsl:template match=taxes !-- cut irrelevant table info -- fo:table-row fo:table-cell fo:block xsl:value-of select=sum(tax_item/amount)/ /fo:block /fo:table-cell /fo:table-row !-- other irrelevant table info -- /xsl:template I am using xalan-2.0.0 for the transformation, if that makes a difference. Thanks much, Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: xslt and number formats
Silly me, the sample I included in the message is not what I was really using. Instead of xsl:value-of select=sum(tax_item/amount)/ I was really using xsl:number value=sum(tax_item/amount)/. The value-of does seem to work better - thanks! I still need to include your suggestion for the format-number, however if I use after the decimal as you suggest then trailing zeroes are omitted. So instead I have put in 0.00 and that seems to do the trick. -Brian - Original Message - From: Ramin Firoozye [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 29, 2001 9:24 AM Subject: RE: xslt and number formats Hi Brian, I tried your code in Xalan (C and J) and MSXML and got '2.79' (with the digits after decimal point intact). The XSLT spec says that numbers are kept in double format internally so you shouldn't be getting any truncation loss as a result of doing math. The 'sum' function is also supposed to keep numbers in their original format. The only culprit may be the xsl:value-of instruction (although on my system, it's working fine). You might want to try to force a format using something like: xsl:value-of select=format-number(sum(tax_item/amount), '.#') / The '#' characters default to the formatting scheme defined in the JDK 1.1 java.text.DecimalFormat class http://java.sun.com/products/jdk/1.1/docs/api/java.text.DecimalFormat.html . Hope this helps, Ramin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP conformance
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. Arved Sandstrom - Original Message - From: Carmelo Montanez To: [EMAIL PROTECTED] Sent: Thursday, November 29, 2001 4:14 PM Subject: FOP conformance Hi all: Anyone aware of how FOP 0.20.2 conforms to the latest XSL recommendations of October of this year?, I am writing some conformance tests for the latest specifications and FOP complains about fo:page-sequence master-reference = "some-master-reference" /fo:page-sequence it complains about "master-reference", which used to be "master-name" on the previous version. Thanks, Carmelo Montanez
