DO NOT REPLY [Bug 33801] - FOP 0.20.5 AWTRenderer: Sometimes rendering fails in the middle of a table with no error message

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 33801] - FOP 0.20.5 AWTRenderer: Sometimes rendering fails in the middle of a table with no error message

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 33801] New: - FOP 0.20.5 AWTRenderer: Sometimes rendering fails in the middle of a table with no error message

gzilla/show_bug.cgi?id=33801 Summary: FOP 0.20.5 AWTRenderer: Sometimes rendering fails in the middle of a table with no error message Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows XP Statu

DO NOT REPLY [Bug 3497] - id already exists error when using span="all" attribute

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug

Re: Error in computation of inline progression dimension ?

--- Jeremias Maerki <[EMAIL PROTECTED]> wrote: > > It doesn't really matter if the FOs generate > reference areas or not, the Well, the Recommendation declares which of the three types each FO belongs to, in the "Areas" section in each FO definition. It is a static answer that holds for all FO's

Re: Error in computation of inline progression dimension ?

Damn, Glen, thanks for being so insistent. I was indeed wrong. You didn't really give me the prove I needed to be rewired but you got me looking again all over the spec and I found what was wrong: It doesn't really matter if the FOs generate reference areas or not, the key is that 5.3.2 is talking

Re: Error in computation of inline progression dimension ?

--- Glen Mazza <[EMAIL PROTECTED]> wrote: > > This IMO is the fatal flaw in your logic in your > previous email. You determined fo:s-p-m and fo:r-b > to > be type (1) FO's, and hence used the wrong equations > in 5.3.2 to determine calculated values for them. > They are type (3) FO's, and hence t

Re: Error in computation of inline progression dimension ?

--- Jeremias Maerki <[EMAIL PROTECTED]> wrote: > I'm afraid that you're wrong here. It's true that > s-p-m and region-body > don't directly generate reference areas but they > also can't, because > they are only used as a template for each new page. Jeremias, so you are in agreement with me that

Re: Error in computation of inline progression dimension ?

Jeremias Maerki wrote: >> [Glen Mazza] >> So Luca is correct that both fo:simple-page-masters >> should generate the same overall margins of 50 pt. >> each, no? > >No. :-) Ok, now I am convinced you are right. Thanks for all your explanations, I always found this part of the recommendation quite

Re: Error in computation of inline progression dimension ?

I'm afraid that you're wrong here. It's true that s-p-m and region-body don't directly generate reference areas but they also can't, because they are only used as a template for each new page. For for each page they serve as FOs that generate reference areas. But let me give you another example wh

Re: Error in computation of inline progression dimension ?

90pt, no less. On 16.02.2005 05:15:36 Glen Mazza wrote: > On second thought, Jeremias, instead of arguing this, > why don't we just compromise at 75pt. margins? ;) Jeremias Maerki

Re: Error in computation of inline progression dimension ?

On second thought, Jeremias, instead of arguing this, why don't we just compromise at 75pt. margins? ;) Glen --- Glen Mazza <[EMAIL PROTECTED]> wrote: > --- Jeremias Maerki <[EMAIL PROTECTED]> > wrote: > > > Hi Luca, > > > > the reason for the effect you're seeing is the > > inheritance of >

Re: Error in computation of inline progression dimension ?

--- Jeremias Maerki <[EMAIL PROTECTED]> wrote: > Hi Luca, > > the reason for the effect you're seeing is the > inheritance of > start-indent and end-indent. In your exapmle, if you > specify a > margin-left and margin-right on the > simple-page-master, (margin-left and margin-right of 50pt each

Re: Error in computation of inline progression dimension ?

Jeremias, I am wrong here. This phrase in 5.3.2: "If the corresponding absolute "margin" property is specified on the formatting object..." Clearly means that margin *is* a CP, and hence is a CP with start-indent/end-indent as appropriate. Forget that argument--never mind, and I'm sorry that y

Re: Error in computation of inline progression dimension ?

In mid January Peter helped me understand what's going on. Please have a look at his explanation [1]. Maybe that makes it clearer. The margin properties are never used directly in the layout engine (I think and hope). I'm always working from *-indent and space-*. I think it's obvious enough from 5.

Re: Error in computation of inline progression dimension ?

But if start-indent and margin-left are not Corresponding Properties, then the inheritance of 50pt. you gave in your example would not occur. IMO, if start-indent and margin-left were actually intended to be Corresponding Properties, the former would have been named margin-start. Also, margin-bef

Re: Error in computation of inline progression dimension ?

Yes, I was probably not 100% correct in my explanation though my interpretation still stands. On 15.02.2005 18:02:14 Glen Mazza wrote: > Oh--5.3.2 says: "There are two more properties, > "end-indent" and "start-indent" (block-level > formatting objects) which correspond to the various > absolute "

Re: Error in computation of inline progression dimension ?

Oh--5.3.2 says: "There are two more properties, "end-indent" and "start-indent" (block-level formatting objects) which correspond to the various absolute "margin" properties." I'm uncertain that that means that they are Corresponding Properties however--I wonder if you are reading too much into th

Re: Error in computation of inline progression dimension ?

On 15.02.2005 17:46:54 Glen Mazza wrote: > --- Jeremias Maerki <[EMAIL PROTECTED]> wrote: > > > Hi Luca, > > > > the reason for the effect you're seeing is the > > inheritance of > > start-indent and end-indent. In your exapmle, if you > > specify a > > margin-left and margin-right on the > > si

Re: Error in computation of inline progression dimension ?

--- Jeremias Maerki <[EMAIL PROTECTED]> wrote: > Hi Luca, > > the reason for the effect you're seeing is the > inheritance of > start-indent and end-indent. In your exapmle, if you > specify a > margin-left and margin-right on the > simple-page-master, this results > (corresponding properties) in

Re: Error in computation of inline progression dimension ?

computed ipd is right when the margins are set in region-body, but it is 0 > if they are set in simple-page-master, because relDims.ipd is already 100 > and start- end-indent are 50. > > As this method has not been modified recently, the error (if this > behaviour is really wrong) must be elsewhere ... > > Regards, > Luca > > Jeremias Maerki

Error in computation of inline progression dimension ?

ified recently, the error (if this behaviour is really wrong) must be elsewhere ... Regards, Luca http://www.w3.org/1999/XSL/Format"; xmlns:svg="http://www.w3.org/2000/svg";> corto piccolo mini super q

DO NOT REPLY [Bug 31063] - "id already in this document" error with no duplicate id

gzilla/show_bug.cgi?id=31063 "id already in this document" error with no duplicate id [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 31063] - "id already in this document" error with no duplicate id

gzilla/show_bug.cgi?id=31063 "id already in this document" error with no duplicate id [EMAIL PROTECTED] changed: What|Removed |Added URL|http://tigreraye.

DO NOT REPLY [Bug 31063] New: - "id already in this document" error with no duplicate id

gzilla/show_bug.cgi?id=31063 "id already in this document" error with no duplicate id Summary: "id already in this document" error with no duplicate id Product: Fop Version: 0.20.5 Platform: PC URL: http://tigreraye.org/essai.f

XMLParser error with unicode characters in XML file.

I am getting a XML parsing error from weblogic.apache.xerces when I parse a XML document which contains accented characters. This is what I am doing 1) Some database columns have accented data for spanish,japanese etc languages like NÃmero de identificaÃÃo: and nÃmero de identificaciÃn. 2) I am

DO NOT REPLY [Bug 29459] - Error in processing xml-file with xsl-stylesheet

gzilla/show_bug.cgi?id=29459 Error in processing xml-file with xsl-stylesheet [EMAIL PROTECTED] changed: What|Removed |Added Component|general |pdf renderer

DO NOT REPLY [Bug 29459] - Error in processing xml-file with xsl-stylesheet

gzilla/show_bug.cgi?id=29459 Error in processing xml-file with xsl-stylesheet [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 29459] New: - Error in processing xml-file with xsl-stylesheet

gzilla/show_bug.cgi?id=29459 Error in processing xml-file with xsl-stylesheet Summary: Error in processing xml-file with xsl-stylesheet Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity:

Database #Error

-- Partial message is available! -- Error: llegal signs in Mail-Routing -- Mail Server: ESMTP VX32.9 Version Betha Alpha Norton AntiVirus gelöscht1.txt Description: plain/text

Error

The message contains Unicode characters and has been sent as a binary attachment. <>

Re: Compile error in HEAD

Glen, On Sat, Jan 10, 2004 at 01:54:35PM -0800, Glen Mazza wrote: > Simon, > > I can't duplicate the problem on my machine but I > think I see the issue: there is *no* more > org.apache.fop.fo.properties.Constants interface > anymore, it's been gone for a month or so. I think > you just need to

Re: Compile error in HEAD

--- Glen Mazza <[EMAIL PROTECTED]> wrote: > > Yes, but the Eclipse warnings of "unneeded imports" > drives Peter West and a few others crazy. If the > above does not work, our only other solution would > be > a fully qualified import statement. > oops...I mean "fully qualifying the Constants va

Re: Compile error in HEAD

--- Simon Pepping <[EMAIL PROTECTED]> wrote: > > The cause is that the import section is not > sufficient: > > package org.apache.fop.fo.properties; > > import org.apache.fop.fo.*; > import org.apache.fop.apps.FOPException; > > With these import statements the compiler applies > interface

Compile error in HEAD

Hi, The code that I checked out this evening from CVS HEAD generates compile errors, for example, [javac] /fsd/source/xml-fop/build/gensrc/org/apache/fop/fo/properties/BorderBottomStyleMaker.java:21: cannot resolve symbol [javac] symbol : variable PR_BORDER_AFTER_STYLE [javac] loc

Error in junit tests (was: [Bug 25828] - [PATCH] fop.sh/bat should use java.endorsed.dirs)

be ascribed to incompatible combinations of versions of these three jar files. I paid special attention to the jar files that come with SDK 1.4.2_01, those that come with FOP CVS HEAD and those that come with Xalan 2.5.2; these should be compatible combinations. No error occurs with the jar files

DO NOT REPLY [Bug 16713] - Hyphenation error in tables

gzilla/show_bug.cgi?id=16713 Hyphenation error in tables --- Additional Comments From [EMAIL PROTECTED] 2003-12-21 19:01 --- The attachments require other files which are not attached: three xsl files and an external graphic.

DO NOT REPLY [Bug 16626] - Hyphenation causing java.io.IOException error

gzilla/show_bug.cgi?id=16626 Hyphenation causing java.io.IOException error [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 25411] - [WARNING] Error while constructing image from XML -- throws IOE

gzilla/show_bug.cgi?id=25411 [WARNING] Error while constructing image from XML -- throws IOE --- Additional Comments From [EMAIL PROTECTED] 2003-12-10 17:24 --- Created an attachment (id=9499) Log of messages including the error and stack trace

DO NOT REPLY [Bug 25411] New: - [WARNING] Error while constructing image from XML -- throws IOE

gzilla/show_bug.cgi?id=25411 [WARNING] Error while constructing image from XML -- throws IOE Summary: [WARNING] Error while constructing image from XML -- throws IOE Product: Fop Version: 1.0dev Platform: All OS/Versio

DO NOT REPLY [Bug 19851] - Error while opening the distribution file

gzilla/show_bug.cgi?id=19851 Error while opening the distribution file [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Reso

DO NOT REPLY [Bug 24346] - Error when xsl file size is too large (+/- 850 lines)

gzilla/show_bug.cgi?id=24346 Error when xsl file size is too large (+/- 850 lines) [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RE

DO NOT REPLY [Bug 24346] - Error when xsl file size is too large (+/- 850 lines)

gzilla/show_bug.cgi?id=24346 Error when xsl file size is too large (+/- 850 lines) --- Additional Comments From [EMAIL PROTECTED] 2003-11-03 14:44 --- A workaround may be to do XSL transformation as a separate step. Step 1. Use Xalan to transform your XML through your XSL, to get an

DO NOT REPLY [Bug 24346] - Error when xsl file size is too large (+/- 850 lines)

gzilla/show_bug.cgi?id=24346 Error when xsl file size is too large (+/- 850 lines) [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|RE

DO NOT REPLY [Bug 24346] - Error when xsl file size is too large (+/- 850 lines)

gzilla/show_bug.cgi?id=24346 Error when xsl file size is too large (+/- 850 lines) [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 24346] New: - Error when xsl file size is too large (+/- 850 lines)

gzilla/show_bug.cgi?id=24346 Error when xsl file size is too large (+/- 850 lines) Summary: Error when xsl file size is too large (+/- 850 lines) Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Se

Re: Break-before ERROR

Alberto Rodriguez Reyes wrote: the break-before="even-page" doesn't work if last page it's even page and i put this label in into . If last page it's odd page then insert a blank page---> it's work Break-before shouldn't work in static content at all, it only works in the flow. Surely you mean som

Break-before ERROR

Hi, the break-before="even-page" doesn't work if last page it's even page and i put this label in into . If last page it's odd page then insert a blank page---> it's work What's happens??? Thanks *** ** Alberto Rodríguez Reyes *** ***

RE: OutOfMemory error

From: Alberto Rodriguez Reyes <[EMAIL PROTECTED]> Hi, i've read this document and that's only really solution.i think that must have other solution to free memory. Thanks I dont quite understand, increasing the amount of memory available to the JVM is the not the only solution suggested on the FO

RE: OutOfMemory error

utOfMemory error >From: Alberto Rodriguez Reyes <[EMAIL PROTECTED]> > >Hi, >my name is Alberto and i'm from spain, my english is not very well but i >try >to tell you what it happens. >I'm developed a single system fop based: i received a xml input and a p

Re: OutOfMemory error

plication return a OutOfMemory error. I tried to modify JVM's memory and it's run, but I think that it is not the best solution. Is there any other solution for this? Thank's Have you read the following advice regarding FOP memory usage on the web site? http://xml.apache.org/fo

OutOfMemory error

Hi, my name is Alberto and i'm from spain, my english is not very well but i try to tell you what it happens. I'm developed a single system fop based: i received a xml input and a pdf is returned, but if xml is very large the application return a OutOfMemory error. I tried to modify JV

DO NOT REPLY [Bug 3497] - id already exists error when using span="all" attribute

gzilla/show_bug.cgi?id=3497 id already exists error when using span="all" attribute [EMAIL PROTECTED] changed: What|Removed |Added CC||

DO NOT REPLY [Bug 23256] - Page reference bug - id repeat error.

gzilla/show_bug.cgi?id=23256 Page reference bug - id repeat error. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 23256] New: - Page reference bug - id repeat error.

gzilla/show_bug.cgi?id=23256 Page reference bug - id repeat error. Summary: Page reference bug - id repeat error. Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority:

DO NOT REPLY [Bug 3497] - id already exists error when using span="all" attribute

gzilla/show_bug.cgi?id=3497 id already exists error when using span="all" attribute --- Additional Comments From [EMAIL PROTECTED] 2003-09-11 19:58 --- I have attached an updated version of the patch for 0.20.5. Is there a reason this patch hasn’t made it into the main releases?

DO NOT REPLY [Bug 3497] - id already exists error when using span="all" attribute

gzilla/show_bug.cgi?id=3497 id already exists error when using span="all" attribute --- Additional Comments From [EMAIL PROTECTED] 2003-09-11 19:56 --- Created an attachment (id=8169) Updated patch for FOP 0.20.5

Re: FOP error log idea

on at the top of the ERROR/Log? > > - fop version > - jdk version > - platform on which error occurred (or where FOP is > being run) > > I don't know if there's any other information (total > RAM; RAM in use by > FOP/Java, etc.; RAM available; hard drive space &

FOP error log idea

Would it be possible and/or would it make sense to output the following information at the top of the ERROR/Log? - fop version - jdk version - platform on which error occurred (or where FOP is being run) I don't know if there's any other information (total RAM; RAM in use by FOP/Java,

DO NOT REPLY [Bug 22216] - bug in processMessage(), doesn't work for ERROR

gzilla/show_bug.cgi?id=22216 bug in processMessage(), doesn't work for ERROR --- Additional Comments From [EMAIL PROTECTED] 2003-08-08 11:14 --- A 2nd solution is to stop the processing. This may be more useful in many cases. I changed org.apache.fop.fo.flow.ExternalGraphic.layout()

DO NOT REPLY [Bug 22216] New: - bug in processMessage(), doesn't work for ERROR

gzilla/show_bug.cgi?id=22216 bug in processMessage(), doesn't work for ERROR Summary: bug in processMessage(), doesn't work for ERROR Product: Fop Version: 0.20.5 Platform: PC OS/Version: Other Status: NEW Se

DO NOT REPLY [Bug 22216] - bug in processMessage(), doesn't work for ERROR

gzilla/show_bug.cgi?id=22216 bug in processMessage(), doesn't work for ERROR --- Additional Comments From [EMAIL PROTECTED] 2003-08-08 08:41 --- An idea to solve the problem: Put some additional actions into the contructors of class FopImageException, like this: public class FopIma

DO NOT REPLY [Bug 2909] - Gradient render error

gzilla/show_bug.cgi?id=2909 Gradient render error [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comment

DO NOT REPLY [Bug 22101] - linearGradient render error

gzilla/show_bug.cgi?id=22101 linearGradient render error [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 22101] New: - linearGradient render error

gzilla/show_bug.cgi?id=22101 linearGradient render error Summary: linearGradient render error Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Com

DO NOT REPLY [Bug 21946] - [ERROR] svg graphic could not be built: null when running fop embedded

gzilla/show_bug.cgi?id=21946 [ERROR] svg graphic could not be built: null when running fop embedded --- Additional Comments From [EMAIL PROTECTED] 2003-07-29 12:28 --- Please upgrade to FOP 0.20.5 and use the Batik version that comes wi

DO NOT REPLY [Bug 21946] - [ERROR] svg graphic could not be built: null when running fop embedded

gzilla/show_bug.cgi?id=21946 [ERROR] svg graphic could not be built: null when running fop embedded [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 21946] New: - [ERROR] svg graphic could not be built: null when running fop embedded

gzilla/show_bug.cgi?id=21946 [ERROR] svg graphic could not be built: null when running fop embedded Summary: [ERROR] svg graphic could not be built: null when running fop embedded Product: Fop Version: 0.20.4 Platform: PC OS/Version:

Re: error compiling HEAD (need GraphicsConfiguration.java)

Never mind. xml-fop/src/java-1.4 directory needed updating. Had to do a cvs update w/ -d option first. Glen --- Glen Mazza <[EMAIL PROTECTED]> wrote: > I can't compile the CVS - HEAD of FOP. Unless I've > gotten something wrong, this file: > > http://cvs.apache.org/viewcvs.cgi/xml-fop/src/jav

error compiling HEAD (need GraphicsConfiguration.java)

I can't compile the CVS - HEAD of FOP. Unless I've gotten something wrong, this file: http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/svg/PDFGraphicsConfiguration.java?rev=1.1&content-type=text/vnd.viewcvs-markup is extending a GraphicsConfiguration.java that apparently needs t

DO NOT REPLY [Bug 20621] - getting "Error while recovering Image Informations" exception with nested "Stream closed" exception

gzilla/show_bug.cgi?id=20621 getting "Error while recovering Image Informations" exception with nested "Stream closed" exception [EMAIL PROTECTED] changed: What|Removed |Added --

DO NOT REPLY [Bug 20621] New: - getting "Error while recovering Image Informations" exception with nested "Stream closed" exception

gzilla/show_bug.cgi?id=20621 getting "Error while recovering Image Informations" exception with nested "Stream closed" exception Summary: getting "Error while recovering Image Informations" exception with nested "Stream

DO NOT REPLY [Bug 20453] - FOP ends with error when xsl:include tag used in xsl

gzilla/show_bug.cgi?id=20453 FOP ends with error when xsl:include tag used in xsl --- Additional Comments From [EMAIL PROTECTED] 2003-06-03 18:09 --- Actually, I believe (respectfully) that the bug is in your XSL. First of all, the xsl:include tag is not closed (although that may be just

Re: DO NOT REPLY [Bug 20453] New: - FOP ends with error whenxsl:include tag used in xsl

Jeremias, Thanks for the note! I'll POST it... BTW... On 6/3/2003 9:09 AM, Jeremias Maerki wrote: BTW, it's funny. I also wondered if the xsl:include shouldn't be top-level. But after I made his text.xsl well-formed (!) the FO got generated just fine on my machine. Strange. I'm guessing, that it

Re: DO NOT REPLY [Bug 20453] New: - FOP ends with error when xsl:include tag used in xsl

Clay, you need to consider that this guy may not see your answer if he isn't subscribed to fop-dev. You need post answers in bugzilla which will automatically send a natification to the reporter. BTW, it's funny. I also wondered if the xsl:include shouldn't be top-level. But after I made his text

Re: DO NOT REPLY [Bug 20453] New: - FOP ends with error whenxsl:include tag used in xsl

Howdy! On 6/3/2003 8:42 AM, [EMAIL PROTECTED] wrote: [INFO] FOP 0.20.4 [ERROR] null [..] http://www.w3.org/1999/XSL/Format"; xmlns:nsdc="http://www.rtf2fo.com/NSDC"; xmlns:xsl="http://www.w3.org/1999/XSL/Transform";> Actually, I believe (respectfully)

DO NOT REPLY [Bug 20453] - FOP ends with error when xsl:include tag used in xsl

gzilla/show_bug.cgi?id=20453 FOP ends with error when xsl:include tag used in xsl [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 20453] - FOP ends with error when xsl:include tag used in xsl

gzilla/show_bug.cgi?id=20453 FOP ends with error when xsl:include tag used in xsl --- Additional Comments From [EMAIL PROTECTED] 2003-06-03 15:45 --- Created an attachment (id=6614) Examples of xsd and xsl files used for generati

DO NOT REPLY [Bug 20453] New: - FOP ends with error when xsl:include tag used in xsl

gzilla/show_bug.cgi?id=20453 FOP ends with error when xsl:include tag used in xsl Summary: FOP ends with error when xsl:include tag used in xsl Product: Fop Version: 0.20.4 Platform: PC OS/Version: Windows NT/2K Status: NEW Se

Error printing from servlet

 know what is the problem ?       Thanks,     Paulo Benfatti   The error generated is:   500 Internal Server Errororg.apache.fop.apps.FOPException: Unable to print: java.awt.print.PrinterException: No printer found. at org.apache.fop.apps.Driver.render(Driver.java:462) at

DO NOT REPLY [Bug 18559] - Not enough error messages ("Marformed format string")

gzilla/show_bug.cgi?id=18559 Not enough error messages ("Marformed format string") [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 18559] New: - Not enough error messages ("Marformed format string")

gzilla/show_bug.cgi?id=18559 Not enough error messages ("Marformed format string") Summary: Not enough error messages ("Marformed format string") Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Stat

email virus error

Has anyone ever seen a situation where a pdf created using FOP and xsl:fo is sent in an email directly from Internet Explorer (File -> Send -> Page by Email), and the recipient gets this email virus warning when they receive the email? Found virus EMail_Flaw_MIME_Tag_Overflow in file The file i

DO NOT REPLY [Bug 18058] New: - Error fetching Image from URL

gzilla/show_bug.cgi?id=18058 Error fetching Image from URL Summary: Error fetching Image from URL Product: Fop Version: 0.20.4 Platform: Other OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority:

Re: Wrong operand type error in ASV 3.0

The error still persists even after I changed the width to 1. Swapan. --- Keiron Liddle <[EMAIL PROTECTED]> wrote: > > > > > > stroke="#00" stroke- > > width="0.5" /> > > IIRC It is probably an error caused by this line > bei

Re: Wrong operand type error in ASV 3.0

> > stroke="#00" stroke- > width="0.5" /> IIRC It is probably an error caused by this line being 0.5 width. In PDF lines can only be whole numbers and it might wrongly be inserting 0.5 in the PDF causing the error. Try making it width 1. If you need a

Wrong operand type error in ASV 3.0

Hi All, I have written a small svg document and embedding this svg document in an FO document to covert to pdf. I guess the FOP completely depends on batik for SVG2PDF conversion. When I try to open the resulting pdf, it says wrong operand type. Can anybody help ? Thanks in advance, Swapan. h

DO NOT REPLY [Bug 16996] - build.bat script fails with javac error.

gzilla/show_bug.cgi?id=16996 build.bat script fails with javac error. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 16996] - build.bat script fails with javac error.

gzilla/show_bug.cgi?id=16996 build.bat script fails with javac error. --- Additional Comments From [EMAIL PROTECTED] 2003-02-12 14:56 --- Does not occur with source for fop-0.20.5rc downloaded from previously mentioned distribution page, only fop-

DO NOT REPLY [Bug 16996] - build.bat script fails with javac error.

gzilla/show_bug.cgi?id=16996 build.bat script fails with javac error. --- Additional Comments From [EMAIL PROTECTED] 2003-02-12 14:24 --- Follow-up note: I worked around the problem - at least as far as getting a completed build is concerned - by providing an 'implemention' o

DO NOT REPLY [Bug 16996] New: - build.bat script fails with javac error.

gzilla/show_bug.cgi?id=16996 build.bat script fails with javac error. Summary: build.bat script fails with javac error. Product: Fop Version: 0.20.4 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Blocker Pr

DO NOT REPLY [Bug 16672] - SVG clipping error

gzilla/show_bug.cgi?id=16672 SVG clipping error [EMAIL PROTECTED] changed: What|Removed |Added Severity|Normal

SVG size error in PDFRenderer

Hi, the size of SVG is wrong when rendered by org.apache.fop.render.pdf.PDFRenderer in FOP 0.20.4. The method renderSVGDocument uses BridgeContext.getDocumentSize().getWidth() etc, which returns an integer instead of a float. This works fine when rendering to PostScript but not to PDF. I looked at

DO NOT REPLY [Bug 16713] - Hyphenation error in tables

gzilla/show_bug.cgi?id=16713 Hyphenation error in tables --- Additional Comments From [EMAIL PROTECTED] 2003-02-03 15:44 --- Created an attachment (id=4688) Example xsl-file - To unsubscribe, e-mail: [EMAIL PROTECTE

DO NOT REPLY [Bug 16713] - Hyphenation error in tables

gzilla/show_bug.cgi?id=16713 Hyphenation error in tables --- Additional Comments From [EMAIL PROTECTED] 2003-02-03 15:42 --- Created an attachment (id=4687) Example xml-file - To unsubscribe, e-mail: [EMAIL PROTECTE

DO NOT REPLY [Bug 16713] New: - Hyphenation error in tables

gzilla/show_bug.cgi?id=16713 Hyphenation error in tables Summary: Hyphenation error in tables Product: Fop Version: 0.20.4 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Com

DO NOT REPLY [Bug 16672] New: - SVG clipping error

gzilla/show_bug.cgi?id=16672 SVG clipping error Summary: SVG clipping error Product: Fop Version: 0.20.4 Platform: Other OS/Version: HP-UX Status: NEW Severity: Normal Priority: Other Component: svg Assi

DO NOT REPLY [Bug 16626] New: - Hyphenation causing java.io.IOException error

gzilla/show_bug.cgi?id=16626 Hyphenation causing java.io.IOException error Summary: Hyphenation causing java.io.IOException error Product: Fop Version: 0.20.4 Platform: Other OS/Version: Other Status: NEW Severity:

DO NOT REPLY [Bug 12565] - Embedding SVG tags like font-face causes error message and will be ignored

gzilla/show_bug.cgi?id=12565 Embedding SVG tags like font-face causes error message and will be ignored [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 16318] - NoSuchMethod - Error when embedding SVG

gzilla/show_bug.cgi?id=16318 NoSuchMethod - Error when embedding SVG --- Additional Comments From [EMAIL PROTECTED] 2003-01-22 11:57 --- Thank You! It works with batik from fop distribution. - To unsubscribe, e-mail:

  1   2   3   4   >