Re: Building fop and batik
Jeremias Maerki wrote: The latest revision of FOP Trunk right before my next commit which will add Commons is 390222 (or date: everything before today). Thanks. Peter
FOP Error in servlet logs
Hi, I am continuously getting the following error in the servlet logs : [Wed Apr 05 06:11:19 EDT 2006] [ERROR] Logger not set[Wed Apr 05 06:11:19 EDT 2006] [WARNING] Screen logger not set - Using ConsoleLogger.[Wed Apr 05 06:11:19 EDT 2006] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser[Wed Apr 05 06:11:19 EDT 2006] [INFO] building formatting object tree[Wed Apr 05 06:11:19 EDT 2006] [INFO] setting up fonts[Wed Apr 05 06:11:20 EDT 2006] [INFO] [1][Wed Apr 05 06:11:20 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table.[Wed Apr 05 06:11:20 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table.[Wed Apr 05 06:11:21 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table.[Wed Apr 05 06:11:21 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table.[Wed Apr 05 06:11:21 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table.[Wed Apr 05 06:11:21 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table.[Wed Apr 05 06:11:21 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table.[Wed Apr 05 06:11:21 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table.[Wed Apr 05 06:11:21 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table.[Wed Apr 05 06:11:21 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table. I am uable to find out the reason for the error or what the error means . Any help would be appreciated Thanks Metrona NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited.
DO NOT REPLY [Bug 39215] New: - [PATCH] To render GIF external images in RTF output via PNG
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=39215. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39215 Summary: [PATCH] To render GIF external images in RTF output via PNG Product: Fop Version: 1.0dev Platform: Macintosh OS/Version: Mac OS X 10.3 Status: NEW Severity: normal Priority: P2 Component: rtf AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: [EMAIL PROTECTED] A patch to RtfExternalImage to convert GIF to PNG using javax.image.ImageIO -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: FOP Error in servlet logs
D'Souza, Metrona (IT) wrote: Hi, I am continuously getting the following error in the servlet logs : [Wed Apr 05 06:11:19 EDT 2006] [ERROR] Logger not set [Wed Apr 05 06:11:19 EDT 2006] [WARNING] Screen logger not set - Using ConsoleLogger. [Wed Apr 05 06:11:19 EDT 2006] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [Wed Apr 05 06:11:19 EDT 2006] [INFO] building formatting object tree [Wed Apr 05 06:11:19 EDT 2006] [INFO] setting up fonts [Wed Apr 05 06:11:20 EDT 2006] [INFO] [1] [Wed Apr 05 06:11:20 EDT 2006] [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on table. It means you need to specify width on fo:table. Chris snip/ BTW, this forum is for discussing the Java coding of FOP internals. User questions should be posted to the fop-user mailing list.
DO NOT REPLY [Bug 39215] - [PATCH] To render GIF external images in RTF output via PNG
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=39215. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39215 [EMAIL PROTECTED] changed: What|Removed |Added Keywords||PatchAvailable --- Additional Comments From [EMAIL PROTECTED] 2006-04-05 13:07 --- Thanks for the patch, Ian. However, there's a fundamental problem with it: It generates a dependency on JDK 1.4 or later due to the use of ImageIO. FOP must, for the time being, remain compatible with JDK 1.3. FOP's image package contains adapters to several image libraries which can read GIF images. The problem is that you cannot easily use them for this particular use case because they currently create a decoded bitmap image as a byte array. It would have to be converted into a BufferedImage and then written to a PNG through the ImageWriter interface provided by XML Graphics Commons (http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/src/java/org/apache/xmlgraphics/image/writer/). I've started documenting requirements for an improved image adapter package: http://wiki.apache.org/xmlgraphics-fop/ImageSupport. But that's probably for later since this will take some time to implement properly. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
[EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 33 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - xml-fop : XSL-FO (Formatting Objects) processor Full details are available at: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: xmlgraphics-commons unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/rss.xml - Atom: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2705042006, vmgump.apache.org:vmgump-public:2705042006 Gump E-mail Identifier (unique within run) #77. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 33 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - xml-fop : XSL-FO (Formatting Objects) processor Full details are available at: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: xmlgraphics-commons unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/rss.xml - Atom: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2705042006, vmgump.apache.org:vmgump-public:2705042006 Gump E-mail Identifier (unique within run) #77. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
Re: [EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed
On 05.04.2006 14:37:30 Sam Ruby wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 33 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - xml-fop : XSL-FO (Formatting Objects) processor Full details are available at: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: xmlgraphics-commons unknown to *this* workspace I fixed this already. It should go away with the next Gump run. Hopefully this will make the Gump run work again. -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/rss.xml - Atom: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2705042006, vmgump.apache.org:vmgump-public:2705042006 Gump E-mail Identifier (unique within run) #77. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] Jeremias Maerki
DO NOT REPLY [Bug 39215] - [PATCH] To render GIF external images in RTF output via PNG
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=39215. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39215 --- Additional Comments From [EMAIL PROTECTED] 2006-04-05 14:08 --- Is it Ok to use JAI to build the BufferedImage ? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: [NOTICE] XML Graphics Commons is now a dependency of FOP Trunk
On Apr 5, 2006, at 5:39 AM, Jeremias Maerki wrote: On 05.04.2006 01:31:53 Web Maestro Clay wrote: I was going to fix up the xmlgraphics page, but it doesn't look like the src files were committed for the web site (src/documentation/ content/xdocs/*.xml). Am I missing something? Hmm, sorry, but I don't know what you mean. So far, there's no website for Commons. I was talking about for xmlgraphics/site (not commons... that'll come later!). I couldn't find any svn updates to xmlgraphics, so I thought your changes must be local... Then again, it's possible you made those changes a while ago... Clay Leeds [EMAIL PROTECTED] My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet
Re: [EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed
On Apr 5, 2006, at 5:59 AM, Jeremias Maerki wrote: On 05.04.2006 14:37:30 Sam Ruby wrote: The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: xmlgraphics-commons unknown to *this* workspace I fixed this already. It should go away with the next Gump run. Hopefully this will make the Gump run work again. My Inbox thanks you! :-) Clay Leeds [EMAIL PROTECTED] My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet
Re: [NOTICE] XML Graphics Commons is now a dependency of FOP Trunk
On 05.04.2006 16:13:34 Clay Leeds wrote: On Apr 5, 2006, at 5:39 AM, Jeremias Maerki wrote: On 05.04.2006 01:31:53 Web Maestro Clay wrote: I was going to fix up the xmlgraphics page, but it doesn't look like the src files were committed for the web site (src/documentation/ content/xdocs/*.xml). Am I missing something? Hmm, sorry, but I don't know what you mean. So far, there's no website for Commons. I was talking about for xmlgraphics/site (not commons... that'll come later!). I couldn't find any svn updates to xmlgraphics, so I thought your changes must be local... Then again, it's possible you made those changes a while ago... Ah. Some changes, yes, but obviously not all of them. I've updated the repository and mailing list info for Commons now. Jeremias Maerki
Re: [NOTICE] XML Graphics Commons is now a dependency of FOP Trunk
On Apr 5, 2006, at 7:13 AM, Clay Leeds wrote: On Apr 5, 2006, at 5:39 AM, Jeremias Maerki wrote: On 05.04.2006 01:31:53 Web Maestro Clay wrote: I was going to fix up the xmlgraphics page, but it doesn't look like the src files were committed for the web site (src/documentation/ content/xdocs/*.xml). Am I missing something? Hmm, sorry, but I don't know what you mean. So far, there's no website for Commons. I was talking about for xmlgraphics/site (not commons... that'll come later!). I couldn't find any svn updates to xmlgraphics, so I thought your changes must be local... Then again, it's possible you made those changes a while ago... It looks like the Commons info is in the SVN... never mind! Clay Leeds [EMAIL PROTECTED] My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet
DO NOT REPLY [Bug 38457] - white-space=pre doesn't work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=38457. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=38457 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 38457] - white-space=pre doesn't work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=38457. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=38457 --- Additional Comments From [EMAIL PROTECTED] 2006-04-05 17:19 --- (In reply to comment #3) This is a known problem. Unfortunately there is no simple workaround. Replacing all spaces with non breaking space would do the trick but that is not easily done using a stylesheet I believe. Is there already any resolution for this problem with white spaces on the beggining of the line? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 38457] - white-space incorrectly handled after linefeed
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=38457. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=38457 [EMAIL PROTECTED] changed: What|Removed |Added Summary|white-space=pre doesn't |white-space incorrectly |work|handled after linefeed --- Additional Comments From [EMAIL PROTECTED] 2006-04-05 17:21 --- Hmm... changing the summary, because it's misleading (maybe there's a duplicate of this bug somewhere, I'll look it up later). Very briefly, to bar all t's: The white-space property is implemented, only the small part white-space-treatment='after- linefeed'/'preserve' isn't handled correctly, but in essence, the properties infrastructure does offer full support for the shorthand. :-/ -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: Generalized Knuth-Plass Linebreaking Algorithm
On Tue, Apr 04, 2006 at 10:15:26PM +0200, Jeremias Maerki wrote: I agree with Chris' comment about isBP. BP could easily be misunderstood as block progression, for example. Furthermore, you talk I can do that. about border and padding, but as Manuel notes there's also space (the margin-kind, not whitespace). Note that spaces have stretch and shrink while border and padding do not. You don't have any reference to it in I will add the margin. My boxes can have stretch and shrink, so that is no problem your essay, but I assume that space resolution would still be possible with the current SpaceResolver. It would simply have to be adjusted to the new model, right? While I was digging into letter and word spaces I Space resolution occurs before linebreaking. It is one of FOP's components that building sequences of Knuth elements. It will have to build a sequence of the new elements, which should not be a problem. realized that it will be worthwhile (even necessary) to look at the FO-specifics for these two properties if any bigger refactoring of the current inline progression handling is to be done. Both properties create (potentially conditional) spaces which would all need to be processed by the space resolver. So, I'm not sure, yet, if we already have the full picture here. I've got to find some quiet time to reflect on that some more. As I said above, the two problems should be unrelated. Space resolution has its own logic, but the outcome is an amount of space that should be presented to the line breaker. The Knuth element system provides the elements that can be used, and I expect that my modified elements are sufficient for letter and word spacing. In fact it would even be possible to have a single box for a word, its letter spacing and its following word space (apart from hyphenation). Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Generalized Knuth-Plass Linebreaking Algorithm
On Tue, Apr 04, 2006 at 11:26:38PM +0800, Manuel Mall wrote: On Tuesday 04 April 2006 03:38, Simon Pepping wrote: Hello, snip/ Simon, very interesting approach to the problem. You obviously gave this quite a significant amount of thought. While your approach may simplify many Knuth sequences for the less common (or more convoluted) cases you clearly state that the only case where the original Knuth algorithm has no solution is this blasted spaceborderspace case where the XSL-FO rules say we have to suppress the space before the border (assuming the usual property value settings). The solution in the context of the Knuth algorithm I had in mind is to do a simple re-ordering of the generated elements. Instead of generating the Knuth sequence for spaceborderspace we generate a sequence matching borderspacespace which would suppress all spaces if a line break is created. However, if the spaces are not removed we render it as spaceborderspace. While I have not looked into the details of how this could be implemented in the current FOP code it didn't strike me as overly complicated. On the other hand your solution may well make such workaround unnecessary. IMO, your best bet to prove that it works is to branch the FOP code and plug your new model in. As you have outlined the mapping from old to new that shouldn't be too invasive. I do not like workarounds very much. Often I prefer to reconsider the basis. And it is a nice project to try to make a variant of Knuth's method work. I will first expand by implementation with a method to easily feed test cases and with Knuth and Plass' bells and whistles. Then I may try my hand at an implementation in a FOP branch. But that will take a while because I have only a limited amount of time to spend on FOP. Simon -- Simon Pepping home page: http://www.leverkruid.nl
Encoding issue in PDFOutputIntent.java
I am getting the warning below when compiling the latest trunk Manuel [javac] /home/mm/fop-trunk/src/java/org/apache/fop/pdf/PDFOutputIntent.java:121: warning: unmappable character for encoding UTF8 [javac] * document�s source colors to output device colorants.
Re: Encoding issue in PDFOutputIntent.java
Fixed. Don't know how I managed to type this special apostrophe. On 06.04.2006 00:29:31 Manuel Mall wrote: I am getting the warning below when compiling the latest trunk Manuel [javac] /home/mm/fop-trunk/src/java/org/apache/fop/pdf/PDFOutputIntent.java:121: warning: unmappable character for encoding UTF8 [javac] * document�s source colors to output device colorants. Jeremias Maerki
