Re: BUG: Mapping of ascii minus character in PS renderer
On 22.01.2003 23:55:14 Arnd Beißner wrote: Hello there, after some research I found and fixed a bug in the PS renderer that can be a real nuisance. Yeah, one that I never got round to fix. The problem is as follows: The ascii (and Unicode) minus character is mapped to the hyphen character by the PDF renderer. The PostScript renderer instead maps it tho the minus character. This happens because the generated PS code reencodes the fonts to ISO Latin 1 encoding, which handles ascii code 45 differently from the standard PS font encoding. Typograpically, the character at 45 in ISOLatin1 is a real minus, and the character at 45 in Standard Encoding is a hyphen, which is about half as wide as the minus in your average font. The difference in your PS output can be quite destructive, as FOP always formats assuming the width of the hyphen character... A patch follows. The reason I'm not yet submitting a real diff to Bugzilla is that I am a) extremely overloaded right now and b) this really needs to be discussed: Some thoughts on this (by 'FOP' I mean formatter+PDF renderer code): 1. Who's right and who's wrong? Either FOP - or - the PS renderer is right, but who? I'm sure that the PS renderer is wrong. When I wrote it I've used ISOLatin1 encoding because it got more characters right than with StandardEncoding. :-) I didn't want to spend too much time on this because at that time the PS renderer was merely a proof-of-concept. 2. If FOP is right, then the PS renderer must be fixed. This can be done either by fixing the method renderWordArea or by changing the PS procedures. However, the latter would increase PS file size (can't copy the ISO latin 1 enconding as opposed to the standard encoding), so I opted for changing renderWordArea. Not happy with that on the long run. For immediately fixing this it's ok. When I rewrite the PS renderer for the redesign I intend to get that right from the beginning. The problem is not just the hyphen character. There are others. The problem is that the base14 fonts are set to WinAnsiEncoding (see org.apache.fop.render.pdf.fonts.Helvetica) and the PS renderer uses ISOLatin1. So, depending on the characters used you get multiple mismatches not just the hyphen character. What we probably need is a custom encoding scheme like Acrobat Reader uses when converting PDF to PostScript (PDFEncoding). That'll be some work... 3. If FOP is wrong, then probably someone else must fix it - I suppose I won't find the right place for the fix easily. FOP is right. Personally I think the PS renderer is wrong, since the original Adobe PS character encoding maps ascii 45 to the hyphen character and Adobe usually knows what they're doing. Still, at that point in time, Unicode wasn't there yet, so... This is an issue that we may possible want to solve before 0.20.5 goes final. Personally, I won't have time before the weekend to check with the Unicode and/or XSL spec. Any comments/ideas? --- temp fix that I use --- snip/ I'll put your fix in but I can't guarantee that it'll be before Christian does the release. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/render/ps PSRenderer.java
jeremias2003/01/23 00:37:37
Modified:src/org/apache/fop/render/ps Tag: fop-0_20_2-maintain
PSRenderer.java
Log:
Temporary fix for an encoding mismatch (WinAnsiEncoding vs. ISOLatin1). The hyphen
character is the only character corrected.
Submitted by: Arnd Beissner [EMAIL PROTECTED]
Revision ChangesPath
No revision
No revision
1.15.2.13 +11 -5 xml-fop/src/org/apache/fop/render/ps/PSRenderer.java
Index: PSRenderer.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/ps/PSRenderer.java,v
retrieving revision 1.15.2.12
retrieving revision 1.15.2.13
diff -u -r1.15.2.12 -r1.15.2.13
--- PSRenderer.java 18 Jan 2003 18:19:14 - 1.15.2.12
+++ PSRenderer.java 23 Jan 2003 08:37:37 - 1.15.2.13
@@ -1,6 +1,6 @@
/*
* $Id$
- * Copyright (C) 2001-2002 The Apache Software Foundation. All rights reserved.
+ * Copyright (C) 2001-2003 The Apache Software Foundation. All rights reserved.
* For details on use and redistribution please refer to the
* LICENSE file included with these sources.
*/
@@ -74,7 +74,8 @@
add a color to grayscale conversion for bitmaps to make output smaller (See
PCLRenderer)
- enhanced font support and font embedding
-- support different character encodings
+- fix character encodings (Helvetica uses WinAnsiEncoding internally but is
+ encoded as ISOLatin1 in PS)
- try to implement image transparency
- Add PPD support
- fix border painting (see table.fo)
@@ -706,10 +707,15 @@
for (int i = 0; i l; i++) {
char ch = s.charAt(i);
char mch = fs.mapChar(ch);
-if (mch 127) {
+
+/**@todo Do this in a clean way */
+// temp fix abe: map ascii '-' to ISO latin 1 hyphen char
+if (mch == '-') {
+ sb = sb.append(\\ + Integer.toOctalString(173));
+} else /* fix ends */ if (mch 127) {
sb = sb.append(\\ + Integer.toOctalString(mch));
} else {
-String escape = \\()[]{};
+final String escape = \\()[]{};
if (escape.indexOf(mch) = 0) {
sb.append(\\);
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop CHANGES
jeremias2003/01/23 00:39:38 Modified:.Tag: fop-0_20_2-maintain CHANGES Log: Update changes Revision ChangesPath No revision No revision 1.10.2.44 +3 -0 xml-fop/CHANGES Index: CHANGES === RCS file: /home/cvs/xml-fop/CHANGES,v retrieving revision 1.10.2.43 retrieving revision 1.10.2.44 diff -u -r1.10.2.43 -r1.10.2.44 --- CHANGES 21 Jan 2003 10:52:39 - 1.10.2.43 +++ CHANGES 23 Jan 2003 08:39:38 - 1.10.2.44 @@ -1,5 +1,8 @@ == Done since 0.20.4 release +- Temporary fix for wrong mapping of the hyphen character in the PostScript + renderer. Needs to be done in a clean way later. + Submitted by: Arnd Beissner [EMAIL PROTECTED] - Fix for bug 16257: Get ascender/descender from OS/2 table if the ones in hhea are zero (Jeremias Maerki) - Reduced the size of the PSRenderer output (removed redundant movetos) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Possible bug in initial-page-number in fop 0.20.5.rc
BUG in initial-page-number handling? This xsl:fo document renders 3 pages ?xml version=1.0 encoding=iso-8859-1? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set !-- layout for the first page -- fo:simple-page-master master-name=testMaster page-height=29.6cm page-width=21cm margin-top=0.5cm margin-bottom=0.5cm margin-left=2cm margin-right=2cm fo:region-body margin-top=0.5cm/ fo:region-before extent=2cm/ fo:region-after extent=0cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=testMaster fo:flow flow-name=xsl-region-body fo:blocktest/fo:block /fo:flow /fo:page-sequence !-- without initial-page-number -- fo:page-sequence master-reference=testMaster initial-page-number=1 fo:flow flow-name=xsl-region-body fo:blocktest/fo:block /fo:flow /fo:page-sequence /fo:root This document is correct, only two pages ?xml version=1.0 encoding=iso-8859-1? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set !-- layout for the first page -- fo:simple-page-master master-name=testMaster page-height=29.6cm page-width=21cm margin-top=0.5cm margin-bottom=0.5cm margin-left=2cm margin-right=2cm fo:region-body margin-top=0.5cm/ fo:region-before extent=2cm/ fo:region-after extent=0cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=testMaster fo:flow flow-name=xsl-region-body fo:blocktest/fo:block /fo:flow /fo:page-sequence !-- without initial-page-number -- fo:page-sequence master-reference=testMaster fo:flow flow-name=xsl-region-body fo:blocktest/fo:block /fo:flow /fo:page-sequence /fo:root Any ideas? henrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Fwd: xml.apache.org refactoring #1]
Keiron Liddle wrote: Personally I would like to see some sort of rotation (assuming that there will always be 1 or 2). For example every 6 months. Why? So the PMC becomes something that is better known and diverse than the mystery that it currently seems to be. This is an excellent idea. Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Possible bug in initial-page-number in fop 0.20.5.rc
This isnt a bug. Try setting the attribute force-page-count=no-force on the first page-sequence. 3 pages are rendered because default value for force-page-count is auto, which basically means that because you set the initial page count of the 2nd page sequence to an odd number (1 in your example), FOP needs to insert an EVEN page at the end of the 2nd page sequence. From: Henrik Holle [EMAIL PROTECTED] BUG in initial-page-number handling? This xsl:fo document renders 3 pages ?xml version=1.0 encoding=iso-8859-1? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set !-- layout for the first page -- fo:simple-page-master master-name=testMaster page-height=29.6cm page-width=21cm margin-top=0.5cm margin-bottom=0.5cm margin-left=2cm margin-right=2cm fo:region-body margin-top=0.5cm/ fo:region-before extent=2cm/ fo:region-after extent=0cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=testMaster fo:flow flow-name=xsl-region-body fo:blocktest/fo:block /fo:flow /fo:page-sequence !-- without initial-page-number -- fo:page-sequence master-reference=testMaster initial-page-number=1 fo:flow flow-name=xsl-region-body fo:blocktest/fo:block /fo:flow /fo:page-sequence /fo:root This document is correct, only two pages ?xml version=1.0 encoding=iso-8859-1? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set !-- layout for the first page -- fo:simple-page-master master-name=testMaster page-height=29.6cm page-width=21cm margin-top=0.5cm margin-bottom=0.5cm margin-left=2cm margin-right=2cm fo:region-body margin-top=0.5cm/ fo:region-before extent=2cm/ fo:region-after extent=0cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=testMaster fo:flow flow-name=xsl-region-body fo:blocktest/fo:block /fo:flow /fo:page-sequence !-- without initial-page-number -- fo:page-sequence master-reference=testMaster fo:flow flow-name=xsl-region-body fo:blocktest/fo:block /fo:flow /fo:page-sequence /fo:root Any ideas? henrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] _ MSN Messenger - fast, easy and FREE! http://messenger.msn.co.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Integration of Peter's work
Hi all (and especially Peter) I'd like to ask if and when we can integrate Peter's work into the main redesign. If nobody is against this move in general, I'd volunteer to help Peter integrate it. I've got some time for this and I think this could help focus our limited resources. Peter, would you add a Wiki page describing what needs to be done for the integration and what others could help you with? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Integration of Peter's work
Jeremias, I shall do that, although, never having had anything to do with Wikis before, I will be fumbling. As you may have noticed, I have been somewhat distracted since the New Year. Among the things that require attention are my attempts at a pseudo-code-walkthrough style of documentation for the properties code. I hope to post my initial efforts tomorrow. I have struggled to make the documentation acceptable to Forrest, but the end result is not satisfactory, and I am hoping for some detailed suggestions once I get the pages up. There are a couple of issues in the design of the properties code that will require decisions from the editors. I will detail these on the Wiki, and formulate questions for the editors in hopes of a quick reply. Those things aside, the integration can probably proceed along the same vector as the current FO Tree integration - via the completion of page-sequence events. What will be interesting here is the possibility of defining a set of structure events for integration with the structure renderers like RTF, and I hope we can have some fruitful discussions with Bertrand on this. Warning: extensive style policing will be required. A bit to do over the next few days. Peter Jeremias Maerki wrote: Hi all (and especially Peter) I'd like to ask if and when we can integrate Peter's work into the main redesign. If nobody is against this move in general, I'd volunteer to help Peter integrate it. I've got some time for this and I think this could help focus our limited resources. Peter, would you add a Wiki page describing what needs to be done for the integration and what others could help you with? -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Integration of Peter's work
On 23.01.2003 12:34:33 Peter B. West wrote: Jeremias, I shall do that, although, never having had anything to do with Wikis before, I will be fumbling. It's easy. You'll see. :-) As you may have noticed, I have been somewhat distracted since the New Year. Among the things that require attention are my attempts at a pseudo-code-walkthrough style of documentation for the properties code. I hope to post my initial efforts tomorrow. I have struggled to make the documentation acceptable to Forrest, but the end result is not satisfactory, and I am hoping for some detailed suggestions once I get the pages up. There are a couple of issues in the design of the properties code that will require decisions from the editors. I will detail these on the Wiki, and formulate questions for the editors in hopes of a quick reply. I don't think that each and every issue has to be resolved prior to move your things in. We can sort that out later, right? Or are there any showstoppers? Those things aside, the integration can probably proceed along the same vector as the current FO Tree integration - via the completion of page-sequence events. What will be interesting here is the possibility of defining a set of structure events for integration with the structure renderers like RTF, and I hope we can have some fruitful discussions with Bertrand on this. Warning: extensive style policing will be required. :-) A bit to do over the next few days. I don't want to put pressure on you. Just know that I'm available if you're ready. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Integration of Peter's work
Jeremias Maerki wrote: On 23.01.2003 12:34:33 Peter B. West wrote: ... There are a couple of issues in the design of the properties code that will require decisions from the editors. I will detail these on the Wiki, and formulate questions for the editors in hopes of a quick reply. I don't think that each and every issue has to be resolved prior to move your things in. We can sort that out later, right? Or are there any showstoppers? Mess-makers. We will need to think about the sorts of changes that will be required if the decision goes against me. ... I don't want to put pressure on you. Just know that I'm available if you're ready. Much appreciated. Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Integration of Peter's work
Peter B. West wrote: . . . What will be interesting here is the possibility of defining a set of structure events for integration with the structure renderers like RTF, and I hope we can have some fruitful discussions with Bertrand on this. Looks promising, let me know where to look when the time is right. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Integration of Peter's work
Title: Integration of Peter's work If clear documentation of what needs to be done can be produced, I'm willing to offer my time to it, too, though I don't know if my not having R/W access to the CVS would make me an unsuitable candidate. -Original Message-From: Jeremias Maerki [mailto:[EMAIL PROTECTED]]Sent: Thursday, January 23, 2003 5:57 AMTo: [EMAIL PROTECTED]Subject: Integration of Peter's work Hi all (and especially Peter)I'd like to ask if and when we can integrate Peter's work into the mainredesign. If nobody is against this move in general, I'd volunteer tohelp Peter integrate it. I've got some time for this and I think thiscould help focus our limited resources.Peter, would you add a Wiki page describing what needs to be done forthe integration and what others could help you with?Jeremias Maerki-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, email: [EMAIL PROTECTED]
Re: Integration of Peter's work
Processing properly generated unified diffs is not much of a problem. It would be cool if you could help, too. We can use all the help we can get. Just curious: Is the missing R/W access to CVS a reason for you not to contribute? (another little thing: Are you forced to use that particular mail client you currently use?) On 23.01.2003 14:39:25 Rhett Aultman wrote: If clear documentation of what needs to be done can be produced, I'm willing to offer my time to it, too, though I don't know if my not having R/W access to the CVS would make me an unsuitable candidate. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Integration of Peter's work
Rhett Aultman wrote: As for my mail client...pretty much, yes, I am. It's a standard at my company. The only other option is for me to switch to my private email account and start using a web-based client. If it's annoying people, I can. If you're using Outlook, there is a checkbox on the Name tab of the Address Book Properties screen that says Send E-Mail using plain text only which may help with the text/html issue. The Mail Options tab of the Tools / Options menu has a more global setting that does the same thing. If there are other things about Outlook that are problems, I don't know what they are. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: mail clients (was: Integration of Peter's work)
For my part, I've never understood why people seem to prefer mailing lists to NTTP newsgroups. Has there ever been a discussion about moving to a newsgroup? -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 9:59 AM To: [EMAIL PROTECTED] Subject: Re: mail clients (was: Integration of Peter's work) It's not only about the HTML. It's also about the In-Reply-To and/or References header entry. Some mail clients have a thread view (as a tree) and not having these header entries involves attaching mails manually to the thread. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: mail clients (was: Integration of Peter's work)
I can't remember any. Do you know about gmane (http://www.gmane.org)? You could try to have the FOP lists registrated there. Other Apache projects have done the same. On 23.01.2003 16:42:09 Patrick Dean Rusk wrote: For my part, I've never understood why people seem to prefer mailing lists to NTTP newsgroups. Has there ever been a discussion about moving to a newsgroup? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Integration of Peter's work
On 23.01.2003 16:07:24 Rhett Aultman wrote: Doing anything is why I have volunteered to help integrate Peter's work. It seems like the sort of thing I could do without excessive domain knowledge and like something I can do while I keep an eye on the layout system and while thinking about my other projects. ;) That's fine. The leaves room for me to concentrate on Avalonization. BTW, does anyone here use Eclipse as their IDE? I use it, and getting it to play nice with FOP's source hasn't been easy for me, so I thought I might ask around. I use it. That's why I refactored the build in the redesign. There you can have two source directories (src and build/gensrc) and you'll have everything you need. For the branch this is not so simple as there is still PDFGraphics2D.java that doesn't compile so easily. I've changed this in the redesign to PDFGraphics2D.javat (t=template). To build the build/gensrc directory, just call build codegen. Does that help? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Integration of Peter's work
...and I don't use the built-in Ant support. Doesn't work on my machine. Lots of error with out build.xml. On 23.01.2003 18:32:01 Jeremias Maerki wrote: BTW, does anyone here use Eclipse as their IDE? I use it, and getting it to play nice with FOP's source hasn't been easy for me, so I thought I might ask around. I use it. That's why I refactored the build in the redesign. There you can have two source directories (src and build/gensrc) and you'll have everything you need. For the branch this is not so simple as there is still PDFGraphics2D.java that doesn't compile so easily. I've changed this in the redesign to PDFGraphics2D.javat (t=template). To build the build/gensrc directory, just call build codegen. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Integration of Peter's work
Just realize that I am, with the exception of my layout experience, a grunt. I'm volunteering for this because I'm assuming that Peter has gotten the majority of the actual engineering out of the way and that helping incorporate his work isn't going to require massive amounts of domain knowledge. If it does, it's going to take me longer than it'll take others. I guess I'll know when the TODO list becomes available. -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 12:32 PM To: [EMAIL PROTECTED] Subject: Re: Integration of Peter's work On 23.01.2003 16:07:24 Rhett Aultman wrote: Doing anything is why I have volunteered to help integrate Peter's work. It seems like the sort of thing I could do without excessive domain knowledge and like something I can do while I keep an eye on the layout system and while thinking about my other projects. ;) That's fine. The leaves room for me to concentrate on Avalonization. BTW, does anyone here use Eclipse as their IDE? I use it, and getting it to play nice with FOP's source hasn't been easy for me, so I thought I might ask around. I use it. That's why I refactored the build in the redesign. There you can have two source directories (src and build/gensrc) and you'll have everything you need. For the branch this is not so simple as there is still PDFGraphics2D.java that doesn't compile so easily. I've changed this in the redesign to PDFGraphics2D.javat (t=template). To build the build/gensrc directory, just call build codegen. Does that help? Jeremias Maerki - 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-design
Confronted to volumetric problems I am very interested in the re-design branch of the FOP project, in particular the FO SAX input and ASAP rendering tasks. I wonder if I could try helping in order to make possible getting a release available this year. But I have not been able to catch the real design/development state of the 1.0 branch. Does anyone already work on the preceding items ? Cédrick Le Névanen Airbus France This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: mail clients (was: Integration of Peter's work)
Patrick Dean Rusk wrote: For my part, I've never understood why people seem to prefer mailing lists to NTTP newsgroups. Has there ever been a discussion about moving to a newsgroup? Probably security stuff, old practice and archiving. But anyway, what's wrong with mail list? Please, no more revolutions :) -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
FOP 0.20.4 5rc timing w large COMMENT sections
Howdy folks, I have a file where I've commented a fairly large section of my source XML file (commented areas affect FLOW content--so it won't print out so many darn pages! :-). I've found significant discrepancies involving the timing of outputting the commented version vs. the uncommented version. The intention of this message is to give a heads up (and hopefully initiate discussion) that there may be discrepancies in rendering time vs. actual output time when dealing with large comment sections. Respectfully, Web Maestro Clay === XML file info: COMMENTED version (1 page of output): FILENAME - test_NCWC_sm_1.1.XML FILESIZE - 240 KB (246,218 bytes) TIME: 01:05 (actual) TIME: 2000ms (reported rendering time) UN-COMMENTED version (5 pages of output): FILENAME - test_NCWC_1.1.XML FILESIZE - 240 KB (246,213 bytes) When I processed the COMMENTED version of the file--which printed out a 1 page document--it took 01:05 (1 minute 5 seconds) watching the system clock, but the DOS output showed ~2000ms: C:\Program Files\Java\fop-0.20.4fop -d -xml C:\xml_med7\biglinux\test_NCWC_sm_1.1.XML -xsl C:\xml_med7\fo\xml_med7_default.fo -pdf 030123_NCWC_sm_1.1.pdf [DEBUG] Input mode: [DEBUG] xslt transformation [DEBUG] xml input file: C:\xml_med7\biglinux\test_NCWC_sm_1.1.XML [DEBUG] xslt stylesheet: C:\xml_med7\fo\xml_med7_default.fo [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: 030123_NCWC_sm_1.1.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [DEBUG] base directory: file:/C:/xml_med7/biglinux/ [INFO] FOP 0.20.4 [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [DEBUG] setting up fonts [INFO] [1] [DEBUG] Last page-sequence produced 1 pages. [INFO] Parsing of document complete, stopping renderer [DEBUG] Initial heap size: 2525Kb [DEBUG] Current heap size: 3641Kb [DEBUG] Total memory used: 1115Kb [DEBUG] Memory use is indicative; no GC was performed [DEBUG] These figures should not be used comparatively [DEBUG] Total time used: 2000ms [DEBUG] Pages rendered: 1 [DEBUG] Avg render time: 2000ms/page C:\Program Files\Java\fop-0.20.4 It took 2 seconds of rendering time compared to 65 seconds of time taken from command line [Enter] to FOP output completion. But when I run the normal un-COMMENTED version, it now took 15 seconds. However, the DOS window showed: C:\Program Files\Java\fop-0.20.4fop -d -xml C:\xml_med7\biglinux\test_NCWC_1.1.XML -xsl C:\xml_med7\fo\xml_med7_default.fo -pdf 030123_NCWC_1.1.pdf [DEBUG] Input mode: [DEBUG] xslt transformation [DEBUG] xml input file: C:\xml_med7\biglinux\test_NCWC_1.1.XML [DEBUG] xslt stylesheet: C:\xml_med7\fo\xml_med7_default.fo [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: 030123_NCWC_1.1.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [DEBUG] base directory: file:/C:/xml_med7/biglinux/ [INFO] FOP 0.20.4 [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [DEBUG] setting up fonts [INFO] [1] [INFO] [2] [INFO] [3] [INFO] [4] [INFO] [5] [DEBUG] Last page-sequence produced 5 pages. [INFO] Parsing of document complete, stopping renderer [DEBUG] Initial heap size: 2666Kb [DEBUG] Current heap size: 15561Kb [DEBUG] Total memory used: 12894Kb [DEBUG] Memory use is indicative; no GC was performed [DEBUG] These figures should not be used comparatively [DEBUG] Total time used: 9609ms [DEBUG] Pages rendered: 5 [DEBUG] Avg render time: 1921ms/page C:\Program Files\Java\fop-0.20.4 Both times it appeared to hang on [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser. In FOP's defense, I noticed the last line refers to Avg render time: BTW, I also tried this with 0.20.5rc and here're my results. COMMENTED version (00:58 seconds): C:\Program Files\Java\fop-0.20.5rcfop -d -xml C:\xml_med7\biglinux\test_NCWC_sm_1.1.XML -xsl C:\xml_med7\fo\xml_med7_default.fo -pdf 030123_NCWC_sm_1.1.pdf [DEBUG] Input mode: [DEBUG] xslt transformation [DEBUG] xml input file: C:\xml_med7\biglinux\test_NCWC_sm_1.1.XML [DEBUG] xslt stylesheet: C:\xml_med7\fo\xml_med7_default.fo [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: 030123_NCWC_sm_1.1.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] base directory: file:/C:/xml_med7/biglinux/ [INFO] FOP 0.20.5rc [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [INFO] setting up fonts [INFO] [1] [DEBUG] Last page-sequence produced 1 pages. [INFO] Parsing of
FOP 0.20.4 5rc timing w large COMMENT sections
Sorry for the re-post. I'd neglected to include some information on the XML file info summary for the un-commented version. I've included it, as well as a summary of the FOP .4 .5rc rendering times. You can delete the previous post. :-) Howdy folks, I have a file where I've commented a fairly large section of my source XML file (commented areas affect FLOW content--so it won't print out so many darn pages! :-). I've found significant discrepancies involving the timing of outputting the commented version vs. the uncommented version. The intention of this message is to give a heads up (and hopefully initiate discussion) that there may be discrepancies in rendering time vs. actual output time when dealing with large comment sections. Respectfully, Web Maestro Clay === XML file timing summary: COMMENTED version (1 page of output): FILENAME - test_NCWC_sm_1.1.XML FILESIZE - 240 KB (246,218 bytes) 0.20.4 TIME: ~01:05 (actual) 0.20.4 TIME: 2000ms (reported rendering time) 0.20.5rc TIME: ~00:58 (actual) 0.20.5rc TIME: 1687ms (reported rendering time) === UN-COMMENTED version (5 pages of output): FILENAME - test_NCWC_1.1.XML FILESIZE - 240 KB (246,213 bytes) 0.20.4 TIME: ~00:15 (actual) 0.20.4 TIME: 2000ms (reported rendering time) 0.20.5rc TIME: ~00:09 (actual) 0.20.5rc TIME: 8344ms (reported rendering time) When I processed the COMMENTED version of the file--which printed out a 1 page document--it took 01:05 (1 minute 5 seconds) watching the system clock, but the DOS output showed ~2000ms: C:\Program Files\Java\fop-0.20.4fop -d -xml C:\xml_med7\biglinux\test_NCWC_sm_1.1.XML -xsl C:\xml_med7\fo\xml_med7_default.fo -pdf 030123_NCWC_sm_1.1.pdf [DEBUG] Input mode: [DEBUG] xslt transformation [DEBUG] xml input file: C:\xml_med7\biglinux\test_NCWC_sm_1.1.XML [DEBUG] xslt stylesheet: C:\xml_med7\fo\xml_med7_default.fo [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: 030123_NCWC_sm_1.1.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [DEBUG] base directory: file:/C:/xml_med7/biglinux/ [INFO] FOP 0.20.4 [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [DEBUG] setting up fonts [INFO] [1] [DEBUG] Last page-sequence produced 1 pages. [INFO] Parsing of document complete, stopping renderer [DEBUG] Initial heap size: 2525Kb [DEBUG] Current heap size: 3641Kb [DEBUG] Total memory used: 1115Kb [DEBUG] Memory use is indicative; no GC was performed [DEBUG] These figures should not be used comparatively [DEBUG] Total time used: 2000ms [DEBUG] Pages rendered: 1 [DEBUG] Avg render time: 2000ms/page C:\Program Files\Java\fop-0.20.4 It took 2 seconds of rendering time compared to 65 seconds of time taken from command line [Enter] to FOP output completion. But when I run the normal un-COMMENTED version, it now took 15 seconds. However, the DOS window showed: C:\Program Files\Java\fop-0.20.4fop -d -xml C:\xml_med7\biglinux\test_NCWC_1.1.XML -xsl C:\xml_med7\fo\xml_med7_default.fo -pdf 030123_NCWC_1.1.pdf [DEBUG] Input mode: [DEBUG] xslt transformation [DEBUG] xml input file: C:\xml_med7\biglinux\test_NCWC_1.1.XML [DEBUG] xslt stylesheet: C:\xml_med7\fo\xml_med7_default.fo [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: 030123_NCWC_1.1.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [DEBUG] base directory: file:/C:/xml_med7/biglinux/ [INFO] FOP 0.20.4 [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [DEBUG] setting up fonts [INFO] [1] [INFO] [2] [INFO] [3] [INFO] [4] [INFO] [5] [DEBUG] Last page-sequence produced 5 pages. [INFO] Parsing of document complete, stopping renderer [DEBUG] Initial heap size: 2666Kb [DEBUG] Current heap size: 15561Kb [DEBUG] Total memory used: 12894Kb [DEBUG] Memory use is indicative; no GC was performed [DEBUG] These figures should not be used comparatively [DEBUG] Total time used: 9609ms [DEBUG] Pages rendered: 5 [DEBUG] Avg render time: 1921ms/page C:\Program Files\Java\fop-0.20.4 Both times it appeared to hang on [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser. In FOP's defense, I noticed the last line refers to Avg render time: BTW, I also tried this with 0.20.5rc and here're my results. COMMENTED version (00:58 seconds): C:\Program Files\Java\fop-0.20.5rcfop -d -xml C:\xml_med7\biglinux\test_NCWC_sm_1.1.XML -xsl C:\xml_med7\fo\xml_med7_default.fo -pdf 030123_NCWC_sm_1.1.pdf [DEBUG] Input mode: [DEBUG] xslt transformation [DEBUG] xml input file: C:\xml_med7\biglinux\test_NCWC_sm_1.1.XML [DEBUG] xslt stylesheet: C:\xml_med7\fo\xml_med7_default.fo [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file:
RE: mail clients (was: Integration of Peter's work)
Jeremias Maerki wrote: It's not only about the HTML. It's also about the In-Reply-To and/or References header entry. Some mail clients have a thread view (as a tree) and not having these header entries involves attaching mails manually to the thread. Hmmm. I use Outlook it does this for me. Are my emails coming through messed up? Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
strokeSVGText in Postscript format
Has anyone made or is making an effort to implement strokeSVGText==false feature in PS renderning? I don't want to reinvent wheel here, if no effort is there, I would like to dive into this. Whenever I talk to my collegures or boss about how wonderful FOP is for PDF publishing, the feedback alway is PS SVG sucks. My goal is to make PS SVG rendering a decent one. Three things I wanted to achieve, display right color stroke, Quadratic Bezier Curve and text embedding. the first two are relatively easier, I have submitted two patch #16182 and #16306. So far, colors, curves and text are displayed correctly but the file size is huge when you have text in your SVG. This is because the PS renderer actually draws text in SVG. I would like to implement a strokeSVGText like feature in PDF here. If any committer has this on his radar, that's a great news to me:-) ( Or give me a boot ) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: mail clients (was: Integration of Peter's work)
I use Mozilla 1.2.1 and your msgs come through fine for me. :-) Victor Mote wrote: Jeremias Maerki wrote: It's not only about the HTML. It's also about the In-Reply-To and/or References header entry. Some mail clients have a thread view (as a tree) and not having these header entries involves attaching mails manually to the thread. Hmmm. I use Outlook it does this for me. Are my emails coming through messed up? Victor Mote -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: mail clients (was: Integration of Peter's work)
Yours are ok. You can check yourself for the In-Reply-To header. On 23.01.2003 19:17:48 Victor Mote wrote: Jeremias Maerki wrote: It's not only about the HTML. It's also about the In-Reply-To and/or References header entry. Some mail clients have a thread view (as a tree) and not having these header entries involves attaching mails manually to the thread. Hmmm. I use Outlook it does this for me. Are my emails coming through messed up? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/area/inline Container.java InlineArea.java Word.java
keiron 2003/01/23 10:59:08
Modified:src/org/apache/fop/area AreaTreeModel.java BodyRegion.java
CTM.java CachedRenderPagesModel.java MinOptMax.java
RegionViewport.java RenderPagesModel.java Span.java
StorePagesModel.java Trait.java
src/org/apache/fop/area/inline Container.java
InlineArea.java Word.java
Log:
cleaned up some style errors
Revision ChangesPath
1.2 +5 -5 xml-fop/src/org/apache/fop/area/AreaTreeModel.java
Index: AreaTreeModel.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/area/AreaTreeModel.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- AreaTreeModel.java22 Dec 2002 22:40:31 - 1.1
+++ AreaTreeModel.java23 Jan 2003 18:59:07 - 1.2
@@ -1,9 +1,9 @@
/*
-* $Id$
-* Copyright (C) 2002 The Apache Software Foundation. All rights reserved.
-* For details on use and redistribution please refer to the
-* LICENSE file included with these sources.
-*/
+ * $Id$
+ * Copyright (C) 2002 The Apache Software Foundation. All rights reserved.
+ * For details on use and redistribution please refer to the
+ * LICENSE file included with these sources.
+ */
package org.apache.fop.area;
1.8 +55 -6 xml-fop/src/org/apache/fop/area/BodyRegion.java
Index: BodyRegion.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/area/BodyRegion.java,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- BodyRegion.java 18 Sep 2002 13:50:13 - 1.7
+++ BodyRegion.java 23 Jan 2003 18:59:07 - 1.8
@@ -19,7 +19,7 @@
private int columnGap;
private int columnCount;
-/** Referenc inline progression dimension for the body. */
+/** Reference inline progression dimension for the body. */
private int refIPD;
/**
@@ -30,46 +30,95 @@
super(BODY);
}
-// Number of columns when not spanning
+/**
+ * Set the number of columns for blocks when not spanning
+ *
+ * @param colCount the number of columns
+ */
public void setColumnCount(int colCount) {
this.columnCount = colCount;
}
-// Number of columns when not spanning
+/**
+ * Get the number of columns when not spanning
+ *
+ * @return the number of columns
+ */
public int getColumnCount() {
return this.columnCount;
}
-// A length (mpoints)
+/**
+ * Set the column gap between columns
+ * The length is in millipoints.
+ *
+ * @param colGap the column gap in millipoints
+ */
public void setColumnGap(int colGap) {
this.columnGap = colGap;
}
+/**
+ * Set the before float area.
+ *
+ * @param bf the before float area
+ */
public void setBeforeFloat(BeforeFloat bf) {
beforeFloat = bf;
}
+/**
+ * Set the main reference area.
+ *
+ * @param mr the main reference area
+ */
public void setMainReference(MainReference mr) {
mainReference = mr;
}
+/**
+ * Set the footnote area.
+ *
+ * @param foot the footnote area
+ */
public void setFootnote(Footnote foot) {
footnote = foot;
}
-
+/**
+ * Get the before float area.
+ *
+ * @return the before float area
+ */
public BeforeFloat getBeforeFloat() {
return beforeFloat;
}
+/**
+ * Get the main reference area.
+ *
+ * @return the main reference area
+ */
public MainReference getMainReference() {
return mainReference;
}
+/**
+ * Get the footnote area.
+ *
+ * @return the footnote area
+ */
public Footnote getFootnote() {
return footnote;
}
+/**
+ * Clone this object.
+ * This is only used to clone the current object, the child areas
+ * are assumed to be null and are not cloned.
+ *
+ * @return a shallow copy of this object
+ */
public Object clone() {
BodyRegion br = new BodyRegion();
br.setCTM(getCTM());
1.7 +36 -8 xml-fop/src/org/apache/fop/area/CTM.java
Index: CTM.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/area/CTM.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- CTM.java 25 Oct 2002 09:29:39 - 1.6
+++ CTM.java 23 Jan 2003 18:59:07 - 1.7
Re: strokeSVGText in Postscript format
On 23.01.2003 19:32:47 George Yi wrote: Has anyone made or is making an effort to implement strokeSVGText==false feature in PS renderning? No. I don't want to reinvent wheel here, if no effort is there, I would like to dive into this. Whenever I talk to my collegures or boss about how wonderful FOP is for PDF publishing, the feedback alway is PS SVG sucks. My goal is to make PS SVG rendering a decent one. Three things I wanted to achieve, display right color stroke, Quadratic Bezier Curve and text embedding. the first two are relatively easier, I have submitted two patch #16182 and #16306. So far, colors, curves and text are displayed correctly but the file size is huge when you have text in your SVG. This is because the PS renderer actually draws text in SVG. I would like to implement a strokeSVGText like feature in PDF here. If any committer has this on his radar, that's a great news to me:-) ( Or give me a boot ) The problem is the following: FOP is being redesigned. Version 0.20.5 that will be released within the next days will most probably be the last version based on the maintenance branch. The next version to be released is planned to be 1.0dev based on the redesign code. So code you develop for the maintenance branch will likely be discarded after the 1.0dev of out. Developing for the maintenance branch is a dead end. What I propose you is the following: Keiron developed a PDFTranscoder for Batik that renders SVG as PDF. The same code is also used in the PDF renderer. I urge you to develop a similar thing, a PSTranscoder for Batik, in the redesign (trunk in CVS). We can then try to make sure that you can reuse that Transcoder in the PS renderer in the maintenance branch if you absolutely need that. That way we will avoid having to develop the whole thing twice. If you want I can help you set up the whole thing. I wanted to restart on the PS renderer anyway, just not that soon. But I can switch priorities. How does that sound? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Re-design
Where did you find these tasks? I'm not sure what you mean with these. That's great that you want to help! Welcome! On 23.01.2003 18:37:55 LENEVANEN Cedrick wrote: Confronted to volumetric problems I am very interested in the re-design branch of the FOP project, in particular the FO SAX input and ASAP rendering tasks. I wonder if I could try helping in order to make possible getting a release available this year. But I have not been able to catch the real design/development state of the 1.0 branch. Does anyone already work on the preceding items ? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: strokeSVGText in Postscript format
Sounds attractive to me. I don't know how much dedication I can put into this. My paid job has absolute No.1 priority. But if some committer take a lead, I am certainly willing to help to implement some features. Anyway, help me setup first. I can always learn something:-) -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 1:08 PM To: [EMAIL PROTECTED] Subject: Re: strokeSVGText in Postscript format On 23.01.2003 19:32:47 George Yi wrote: Has anyone made or is making an effort to implement strokeSVGText==false feature in PS renderning? No. I don't want to reinvent wheel here, if no effort is there, I would like to dive into this. Whenever I talk to my collegures or boss about how wonderful FOP is for PDF publishing, the feedback alway is PS SVG sucks. My goal is to make PS SVG rendering a decent one. Three things I wanted to achieve, display right color stroke, Quadratic Bezier Curve and text embedding. the first two are relatively easier, I have submitted two patch #16182 and #16306. So far, colors, curves and text are displayed correctly but the file size is huge when you have text in your SVG. This is because the PS renderer actually draws text in SVG. I would like to implement a strokeSVGText like feature in PDF here. If any committer has this on his radar, that's a great news to me:-) ( Or give me a boot ) The problem is the following: FOP is being redesigned. Version 0.20.5 that will be released within the next days will most probably be the last version based on the maintenance branch. The next version to be released is planned to be 1.0dev based on the redesign code. So code you develop for the maintenance branch will likely be discarded after the 1.0dev of out. Developing for the maintenance branch is a dead end. What I propose you is the following: Keiron developed a PDFTranscoder for Batik that renders SVG as PDF. The same code is also used in the PDF renderer. I urge you to develop a similar thing, a PSTranscoder for Batik, in the redesign (trunk in CVS). We can then try to make sure that you can reuse that Transcoder in the PS renderer in the maintenance branch if you absolutely need that. That way we will avoid having to develop the whole thing twice. If you want I can help you set up the whole thing. I wanted to restart on the PS renderer anyway, just not that soon. But I can switch priorities. How does that sound? Jeremias Maerki - 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: strokeSVGText in Postscript format
Deal. I'll start setting up the basic infrastructure for it tomorrow. I hope we can get you started on this real fast. :-) On 23.01.2003 20:29:22 George Yi wrote: Sounds attractive to me. I don't know how much dedication I can put into this. My paid job has absolute No.1 priority. But if some committer take a lead, I am certainly willing to help to implement some features. Anyway, help me setup first. I can always learn something:-) Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
Hey Maestro! Have you tried to run only the XSLT part of it? Do that and compare execution times there. That should be interesting. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
Jeremias, Jeremias Maerki wrote: Hey Maestro! Have you tried to run only the XSLT part of it? Do that and compare execution times there. That should be interesting. Jeremias Maerki I don't know how to run only the XSLT part of it... Can you give any more information as to what you're referring?__ -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
Run the XSL transformation alone. Using fop.bat you've done: XML XSL-FO --- PDF (XSLT) (FOP) The XSLT part of it is this: XML XSL-FO (XSLT) (I hope the ASCII art comes out ok) Since the comments should in theory not reach FOP it is my guess that something's happening during the XSL transformation from XML to FO. Xalan does that, for example. I don't know what XSLT processor you use. If you use Xalan you can use its command line: http://xml.apache.org/xalan-j/commandline.html I think you can use the -DIAG option to get timings for the transformation. Does that clear it up? On 23.01.2003 21:47:09 Clay Leeds wrote: Jeremias, Jeremias Maerki wrote: Hey Maestro! Have you tried to run only the XSLT part of it? Do that and compare execution times there. That should be interesting. Jeremias Maerki I don't know how to run only the XSLT part of it... Can you give any more information as to what you're referring?__ Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
Jeremias Maerki wrote: Run the XSL transformation alone. Using fop.bat you've done: XML XSL-FO --- PDF (XSLT) (FOP) The XSLT part of it is this: XML XSL-FO (XSLT) (I hope the ASCII art comes out ok) Since the comments should in theory not reach FOP it is my guess that something's happening during the XSL transformation from XML to FO. Xalan does that, for example. I don't know what XSLT processor you use. If you use Xalan you can use its command line: http://xml.apache.org/xalan-j/commandline.html I think you can use the -DIAG option to get timings for the transformation. Does that clear it up? It helps. However, I only have fop-0.20.4 (.5rc) installed. I also notice that in the lib/ folder I've got xalan-2.3.1.jar. Will this suffice, or do I need to install the full version of xalan. Also, the current version of xalan is 2.4.1... should I try it with that? Lastly, I want my system to match--as closely as possible--that of my clients. What steps can I take to ensure that I can regain that parity for testing? BTW, thanks for the quick replies! :-) -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
On 23.01.2003 22:15:17 Clay Leeds wrote: It helps. However, I only have fop-0.20.4 (.5rc) installed. I also notice that in the lib/ folder I've got xalan-2.3.1.jar. Will this suffice, or do I need to install the full version of xalan. Also, the current version of xalan is 2.4.1... should I try it with that? Yep. In this case do: java -cp lib/xml-apis.jar;lib/xercesImpl-2.2.1.jar;lib/xalan-2.4.1.jar org.apache.xalan.xslt.Process -IN test2.xml -XSL test2.xsl -OUT test2.out.xml -DIAG That will run the XSL transformation. It assumes you're in the root directory of your FOP distribution (location of fop.bat) and you're using Windows. You may have to adjust the names of the jar files depending on the FOP version. Lastly, I want my system to match--as closely as possible--that of my clients. What steps can I take to ensure that I can regain that parity for testing? Well, if you use fop.bat to do the testing, you're using the same jars I used above for the XSL transformation. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: mail clients (was: Integration of Peter's work)
Victor Mote wrote: It's not only about the HTML. It's also about the In-Reply-To and/or References header entry. Some mail clients have a thread view (as a tree) and not having these header entries involves attaching mails manually to the thread. Hmmm. I use Outlook it does this for me. Are my emails coming through messed up? Some view source in Moz reveals a few things. There is no In-Reply-To nor a References header in Rhett's mail, but there is X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Integration of Peter's work Thread-Index: AcLC5w8EfopAYM1NRWmF6Xg3Xcc/PQAAvEbg From Jeremias Mail In-Reply-To: [EMAIL PROTECTED] References: [EMAIL PROTECTED] \ [EMAIL PROTECTED] X-Mailer: Becky! ver. 2.05.06 Peter's mail headers User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030115 X-Accept-Language: en-us, en References: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] From Victor: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: [EMAIL PROTECTED] Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 I guess MS Exchange wants to impose it's own method for threading on the unsuspecting rest of the world. Another MUA (or MTA?) which provides only the most basic mail headers identifies itself as X-Mailer: Internet Mail Service (5.5.2653.19) and is rather often seen, unfortunately some prolific posters on XML-DEV use it. Somehow, however, Mozilla often threads these messages to the start message of the thread rather than starting a wholly new one. Additional mailers which seems to be ok Both In-Reply-To and References: X-Mailer: Balsa 1.1.6 X-Mailer: Calypso Version 3.30.00.00 (4) X-Mailer: Forte Agent 1.92/32.572 X-Mailer: mh-e 6.1; nmh 1.0.4+dev; Emacs 21.2 X-Mailer: SquirrelMail (version 1.2.8) X-Mailer: Sylpheed version 0.7.0 (GTK+ 1.2.6; i586-pc-linux-gnu) X-Mailer: The Bat! (v1.54/10) Personal X-Mailer: VM 7.01 under Emacs 21.1.1 X-Mailer: Ximian Evolution 1.0.5 User-Agent: KMail/1.4.1 User-Agent: Opera7.0/Win32 M2 BETA2 build 2577 In-Reply-To but but no References X-Mailer: IMail v7.13 X-Mailer: Apple Mail (2.551) X-Mailer: CommuniGate Pro Web Mailer v.4.0 X-Mailer: EdMax Ver2.32.8F X-Mailer: ELM [version 2.5 PL6] X-Mailer: EMUmail 4.5 X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 X-Mailer: Lotus Notes Build V60_M14_08012002NP Release Candidate ... X-Mailer: Lotus Notes Release 6.0 September 26, 2002 X-Mailer: MailCity Service X-Mailer: Mailsmith 1.5.4 (Blindsider) X-Mailer: Microsoft CDO for Windows 2000 X-Mailer: Microsoft Outlook, Build 10.0.2627 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-Mailer: MIME-tools 5.41 (Entity 5.404) X-Mailer: Opera 6.05 build 1140 X-mailer: Pegasus Mail for Windows (v4.02) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 User-Agent: Internet Messaging Program (IMP) 4.0-cvs User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2106 User-Agent: Microsoft-Entourage/10.0.0.1309 User-Agent: Opera7.0/Win32 M2 BETA2 build 2577 References but no In-Reply-To X-Mailer: Gnus v5.7/Emacs 20.7 X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-Mailer: Mozilla 4.78 [en]C-CCK-MCD (Windows NT 5.0; U) X-Mailer: SKYRiXgreen_3.1 NGMime_4.2.18 X-Mailer: WWW-Mail 1.6 (Global Message Exchange) User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 User-Agent: KNode/0.7.1 User-Agent: Mutt/1.4i User-Agent: Pan/0.9.7 (Unix) User-Agent: Xnews/05.08.12 Not ok: X-Mailer: AOL 5.0 for Mac sub 28 X-Mailer: AOL 7.0 for Windows UK sub 10500 X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc X-Mailer: freemail 0.9.8 X-Mailer: Lotus Notes Release 5.0.x (up to 5.0.11) X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-Mailer: NetMail ModWeb Module X-Mailer: Netscape Webmail X-Mailer: Novell GroupWise 5.5.3 X-Mailer: Novell GroupWise Internet Agent 6.5.0 X-Mailer: Open WebMail 1.41 X-Mailer: Postman 1.12 X-Mailer: Web Mail 5.2.0-3_sol28 Unknown status X-Mailer: Atlas Mailer 2.0 X-Mailer: Mulberry/2.2.0 (Win32) X-Mailer: PHP X-Mailer: Yahoo Groups Message Poster User-Agent: Instant Web Mail 0.61 User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs User-Agent: eGroups-EW/0.82 (actually, that's the same as the Yahoo mailer above Not a real MUA X-Mailer: org.apache.tools.mail.MailMessage (jakarta.apache.org) (that's Nicola Ken's patch queue script) I left out newer versions of working programs. The cluster of big names in the not ok section is a bit
Re: FOP 0.20.4 5rc timing w large COMMENT sections
Jeremias Maerki wrote: On 23.01.2003 22:15:17 Clay Leeds wrote: It helps. However, I only have fop-0.20.4 (.5rc) installed. I also notice that in the lib/ folder I've got xalan-2.3.1.jar. Will this suffice, or do I need to install the full version of xalan. Also, the current version of xalan is 2.4.1... should I try it with that? Yep. In this case do: java -cp lib/xml-apis.jar;lib/xercesImpl-2.2.1.jar;lib/xalan-2.4.1.jar org.apache.xalan.xslt.Process -IN test2.xml -XSL test2.xsl -OUT test2.out.xml -DIAG That worked great (except I had to change the version numbers for xerces (xercesImpl-2.0.1.jar) xalan(xalan-2.3.1.jar) (which was probably expcected :-): C:\Program Files\Java\fop-0.20.4java -cp lib/xml-apis.jar;lib/xercesImpl-2.0.1.jar;lib/xalan-2.3.1.jar org.apache.xalan.xslt.Process -IN C:\xml_med7\biglinux\test_MIWC_1.1.xml -XSL C:\xml_med7\fo\xml_med7_MIWC.fo -OUT 030123_test_xml_med7_MIWC_1.1.out.xml -DIAG Transform of C:\xml_med7\biglinux\test_MIWC_1.1.xml via C:\xml_med7\fo\xml_med7_MIWC.fo took 2813 ms C:\Program Files\Java\fop-0.20.4 That will run the XSL transformation. It assumes you're in the root directory of your FOP distribution (location of fop.bat) and you're using Windows. You may have to adjust the names of the jar files depending on the FOP version. Lastly, I want my system to match--as closely as possible--that of my clients. What steps can I take to ensure that I can regain that parity for testing? Well, if you use fop.bat to do the testing, you're using the same jars I used above for the XSL transformation. Jeremias Maerki In the end, the following took just over 4 seconds, which means I don't think it was xalan which took so long. C:\Program Files\Java\fop-0.20.4java -cp build\fop.jar;lib\batik.jar;lib\xalan-2.3.1.jar;lib\xercesImpl-2.0.1.jar;lib\xml-apis.jar;lib\avalon-framework-cvs-20020315.jar;lib\logkit-1.0.jar;lib\jimi-1.0.jar org.apache.fop.apps.Fop -d -fo 030123_test_xml_med7_MIWC_1.1.out.xml -pdf 030123_test_XSLT_001.pdf [DEBUG] Input mode: [DEBUG] FO [DEBUG] fo input file: 030123_test_xml_med7_MIWC_1.1.out.xml [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: 030123_test_XSLT_001.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [DEBUG] base directory: file:/C:/Program Files/Java/fop-0.20.4/ [INFO] FOP 0.20.4 [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [DEBUG] setting up fonts [INFO] [1] [INFO] [2] [DEBUG] Last page-sequence produced 2 pages. [INFO] Parsing of document complete, stopping renderer [DEBUG] Initial heap size: 726Kb [DEBUG] Current heap size: 5396Kb [DEBUG] Total memory used: 4669Kb [DEBUG] Memory use is indicative; no GC was performed [DEBUG] These figures should not be used comparatively [DEBUG] Total time used: 4422ms [DEBUG] Pages rendered: 2 [DEBUG] Avg render time: 2211ms/page C:\Program Files\Java\fop-0.20.4 -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
On 23.01.2003 22:47:20 Clay Leeds wrote: snip/ That worked great (except I had to change the version numbers for xerces (xercesImpl-2.0.1.jar) xalan(xalan-2.3.1.jar) (which was probably expcected :-): C:\Program Files\Java\fop-0.20.4java -cp lib/xml-apis.jar;lib/xercesImpl-2.0.1.jar;lib/xalan-2.3.1.jar org.apache.xalan.xslt.Process -IN C:\xml_med7\biglinux\test_MIWC_1.1.xml -XSL C:\xml_med7\fo\xml_med7_MIWC.fo -OUT 030123_test_xml_med7_MIWC_1.1.out.xml -DIAG Transform of C:\xml_med7\biglinux\test_MIWC_1.1.xml via C:\xml_med7\fo\xml_med7_MIWC.fo took 2813 ms I'm confused. That's only the uncommented one, right? What about the time for the commented one? snip/ In the end, the following took just over 4 seconds, which means I don't think it was xalan which took so long. snip/ Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
Jeremias Maerki wrote: On 23.01.2003 22:47:20 Clay Leeds wrote: snip/ That worked great (except I had to change the version numbers for xerces (xercesImpl-2.0.1.jar) xalan(xalan-2.3.1.jar) (which was probably expcected :-): C:\Program Files\Java\fop-0.20.4java -cp lib/xml-apis.jar;lib/xercesImpl-2.0.1.jar;lib/xalan-2.3.1.jar org.apache.xalan.xslt.Process -IN C:\xml_med7\biglinux\test_MIWC_1.1.xml -XSL C:\xml_med7\fo\xml_med7_MIWC.fo -OUT 030123_test_xml_med7_MIWC_1.1.out.xml -DIAG Transform of C:\xml_med7\biglinux\test_MIWC_1.1.xml via C:\xml_med7\fo\xml_med7_MIWC.fo took 2813 ms I'm confused. That's only the uncommented one, right? What about the time for the commented one? snip/ Jeremias Maerki Sorry. Brainfart. I just got back from lunch and I used the wrong file... I'll re-run the test. -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Re-design
On Thursday, January 23, 2003, at 06:37 PM, LENEVANEN Cedrick wrote: Confronted to volumetric problems I am very interested in the re-design branch of the FOP project, in particular the FO SAX input and ASAP rendering tasks. I wonder if I could try helping in order to make possible getting a release available this year. The asap rendering is mostly done, we still need to bring back many of the renderers. The SAX input is really about processing the layout as the fo comes in. This depends mainly on the FO tree and the layout system. Any help would be great. But I have not been able to catch the real design/development state of the 1.0 branch. Does anyone already work on the preceding items ? Generally yes, but we could use any help if you can contribute. There are lots of areas that need development. CÈdrick Le NÈvanen Airbus France - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: strokeSVGText in Postscript format
On Thursday, January 23, 2003, at 07:32 PM, George Yi wrote: Has anyone made or is making an effort to implement strokeSVGText==false feature in PS renderning? Not that I am aware of. I don't want to reinvent wheel here, if no effort is there, I would like to dive into this. Whenever I talk to my collegures or boss about how wonderful FOP is for PDF publishing, the feedback alway is PS SVG sucks. It was written quickly quite some time ago and has been waiting for someone to say it sucks :). My goal is to make PS SVG rendering a decent one. Three things I wanted to achieve, display right color stroke, Quadratic Bezier Curve and text embedding. the first two are relatively easier, I have submitted two patch #16182 and #16306. So far, colors, curves and text are displayed correctly but the file size is huge when you have text in your SVG. This is because the PS renderer actually draws text in SVG. I would like to implement a strokeSVGText like feature in PDF here. Thats great. If any committer has this on his radar, that's a great news to me:-) ( Or give me a boot ) This is an area that would be best tackled with the redesigned code as far as development is concerned. The handling of this issue in the redesign has improved quite a bit (but still has some issues left). If you want it sooner then I can give you a few pointers. The PDF renderer handles this issue in the same way that the PS renderer should handle it. Batik uses a concept of a GVT (graphics vector toolkit) that has a TextPainter that handles text. The default TextPainter is the StrokingTextPainter, when not stroking text it replaces this with a PDFTextPainter. The PDFTextPainter then draws the text using the drawString method instead of creating shapes and drawing them. So for the PS renderer you will need to register a TextPainter in the same way which should do the same sort of thing as for the PDFRenderer. Keiron. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
I ran the XSLT transform twice (just out of curiosity), and there was about 300ms difference between the two identicalk runs. However, it is more in line with the results we were expecting. However, it was still about 15-18 seconds shorter than my previous results (diligently watching the clock). This does indeed provide some food for thought. Keeping in mind the difference between the previous times I submitted (01:05 for 0.20.4--00:58 for 0.20.5rc) I see that xalan-2.4.1 xerces-2.2.1 have some improvements. So, where does this leave us? Should we drop a note to the xalan folks? Should we make a note in the FOP docs? Here's the output from the DOS window: === C:\Program Files\Java\fop-0.20.4java -cp lib/xml-apis.jar;lib/xercesImpl-2.0.1. jar;lib/xalan-2.3.1.jar org.apache.xalan.xslt.Process -IN C:\xml_med7\biglinux\t est_NCWC_sm_1.1.xml -XSL C:\xml_med7\fo\xml_med7_default.fo -OUT 030123_test_xml _med7_NCWC_sm_1.1.out.xml -DIAG Transform of C:\xml_med7\biglinux\test_NCWC_sm_1.1.xml via C:\xml_med7\fo\xml_me d7_default.fo took 46671 ms C:\Program Files\Java\fop-0.20.4java -cp lib/xml-apis.jar;lib/xercesImpl-2.0.1. jar;lib/xalan-2.3.1.jar org.apache.xalan.xslt.Process -IN C:\xml_med7\biglinux\t est_NCWC_sm_1.1.xml -XSL C:\xml_med7\fo\xml_med7_default.fo -OUT 030123_test_xml _med7_NCWC_sm_1.1.out.xml -DIAG Transform of C:\xml_med7\biglinux\test_NCWC_sm_1.1.xml via C:\xml_med7\fo\xml_me d7_default.fo took 47030 ms C:\Program Files\Java\fop-0.20.4fop -d -fo 030123_test_xml_med7_NCWC_sm_1.1.out .xml -pdf 030123_test_XSLT_002.pdf C:\Program Files\Java\fop-0.20.4java -cp build\fop.jar;lib\batik.jar;lib\xalan- 2.3.1.jar;lib\xercesImpl-2.0.1.jar;lib\xml-apis.jar;lib\avalon-framework-cvs-200 20315.jar;lib\logkit-1.0.jar;lib\jimi-1.0.jar org.apache.fop.apps.Fop -d -fo 030 123_test_xml_med7_NCWC_sm_1.1.out.xml -pdf 030123_test_XSLT_002.pdf[DEBUG] Input mode: [DEBUG] FO [DEBUG] fo input file: 030123_test_xml_med7_NCWC_sm_1.1.out.xml [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: 030123_test_XSLT_002.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [DEBUG] base directory: file:/C:/Program Files/Java/fop-0.20.4/ [INFO] FOP 0.20.4 [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [DEBUG] setting up fonts [INFO] [1] [DEBUG] Last page-sequence produced 1 pages. [INFO] Parsing of document complete, stopping renderer [DEBUG] Initial heap size: 726Kb [DEBUG] Current heap size: 2191Kb [DEBUG] Total memory used: 1464Kb [DEBUG] Memory use is indicative; no GC was performed [DEBUG] These figures should not be used comparatively [DEBUG] Total time used: 1843ms [DEBUG] Pages rendered: 1 [DEBUG] Avg render time: 1843ms/page -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
Would you think we should put a Xalan.bat/Xalan.sh file into the FOP distribution? (or xslt.bar/xslt.sh) J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
Clay Leeds wrote: It took 2 seconds of rendering time compared to 65 seconds of time taken from command line [Enter] to FOP output completion. This latter time includes JVM startup, loading all the code and whatnot. Occasionally the OS is busy and it takes longer to load an executable and the data. How often did you execute the experiment? If you want to have more accurate measurements you should install cygwin and use the time command. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
J.Pietschmann wrote: Would you think we should put a Xalan.bat/Xalan.sh file into the FOP distribution? (or xslt.bar/xslt.sh) Very good idea. Probably most people create these batchfiles/shellscripts anyway. Might also lead to more people trying the transformation step separately to see where the real problem is... For FOP beginners, it's a real hurdle writing the one-liner that does the transformation alone... BTW: In any case I'd prefer the naming xalan.bat(.sh) I actually have a saxon.sh(.bat), xalan.sh *and* xslt.sh. The latter calls whichever xslt processor my project is currently using. Just my 2 cents. -- Cappelino Informationstechnologie GmbH Arnd Beißner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
J.Pietschmann wrote: Would you think we should put a Xalan.bat/Xalan.sh file into the FOP distribution? (or xslt.bar/xslt.sh) J.Pietschmann That's an intriguing idea. Assuming that it would help trouble-shoot problems like this, that might be good for this type of testing. Also, I noticed a difference in the amount of time, when FOP transformed rendered the PDF file from start to finish (01:05 for 0.20.4), versus when xalan-2.0.1 transformed to XML, and then FOP transformed what was essentially an FO file to PDF (47030ms+1843ms=48873ms). Any idea where the additional 15+ seconds went? -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP 0.20.4 5rc timing w large COMMENT sections
I think it would be preferable to have a FOP option to output the intermediate FO file that it uses in its processing, similar to the way many compilers can output some of their intermediate files. Just today I've finally diagnosed a strangeness in my program to the fact that using FOP to transform gives a different result sometimes than doing the transform manually and following it with a FOP run on the .fo file. In my case, the difference was from having the following line in my XSL file: xsl:output method=xml indent=yes/ This is respected when doing the manual transform, but the FOP run seems to treat it as no. I'll shortly be posting an email related to this latter issue. Patrick Rusk P.S. I think that XEP provides separate files for doing the transform followed by the rendering. I found them handy. Of course, I've created some for FOP, as I'm sure most do. -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 5:25 PM To: [EMAIL PROTECTED] Subject: Re: FOP 0.20.4 5rc timing w large COMMENT sections Would you think we should put a Xalan.bat/Xalan.sh file into the FOP distribution? (or xslt.bar/xslt.sh) J.Pietschmann - 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 0.20.4 5rc timing w large COMMENT sections
Patrick Dean Rusk wrote: I think it would be preferable to have a FOP option to output the intermediate FO file that it uses in its processing, similar to the way many compilers can output some of their intermediate files. It's well-known feature request, see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14351. Just today I've finally diagnosed a strangeness in my program to the fact that using FOP to transform gives a different result sometimes than doing the transform manually and following it with a FOP run on the .fo file. In my case, the difference was from having the following line in my XSL file: xsl:output method=xml indent=yes/ This is respected when doing the manual transform, but the FOP run seems to treat it as no. Sure! There is no room for indentaion in SAX events stream and as there is no serialization altogether the whole xsl:output element is ignored (rememeber - it's just a hint according to the spec). And after all it's not FOP, but a XSLT processor. -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP 0.20.4 5rc timing w large COMMENT sections
Patrick Dean Rusk wrote: Just today I've finally diagnosed a strangeness in my program to the fact that using FOP to transform gives a different result sometimes than doing the transform manually and following it with a FOP run on the .fo file. In my case, the difference was from having the following line in my XSL file: xsl:output method=xml indent=yes/ This is respected when doing the manual transform, but the FOP run seems to treat it as no. You have to understand that XSLT can be a multiphase process 1. Parsing the source XML into a tree 2. Transforming the source tree into a result tree 3. Serialize the result tree. If you run the transformation as integral part of the FO processing, there is no serialization of the transformation result, the FO processor takes it input directly from the result tree of the transformation. Consequently all options regarding result serialization are ignored. This includes everything in the xsl:output element (you could have specified mathod=text :-) ) as well as disabling output escaping. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
