Re: FOP extension to output custom PostScript instructions

Well, in a certain aspect that is already the case today. I've recently added to possibility to dynamically add renderer-specific XML handlers. I need this for the Barcode4J extension for example (directly prividing EPS and PDF versions of the barcode to the renderer). Furthermore, you can always s

Re: Let's write the release plan for the first preview release

Excellent - I like the sound of it :-). Personally, after having now used the trunk a bit and seeing the test cases, etc., I would be a bit "bolder" and go for a name like "1.0 alpha" or "1.0EA" (I think that's the terminology Sun is using for unstable early releases). The big disclaimers still

Re: Wrongly positioned image in PDF renderer

I'll have checked these against my fop version and it appears the problem is fixed as part of the "revised percentage handling" patch. On Mon, 29 Aug 2005 05:03 pm, Jeremias Maerki wrote: > The background image is horizontally misplaced in the table-cell and > in the block-container not aligned t

Re: Percentages on region margins

On Mon, 29 Aug 2005 11:31 pm, Manuel Mall wrote: > On Mon, 29 Aug 2005 11:28 pm, Jeremias Maerki wrote: > > On 29.08.2005 17:18:18 Manuel Mall wrote: > > > On Mon, 29 Aug 2005 08:20 pm, Jeremias Maerki wrote: > > > > You probably missed the following: > > > > > > > > 7.10.1 "margin-top" says for pe

Re: Margins and writing mode

Just to flag that I have a patch for this. However, it depends on the big "revised percentage handling" patch. So I'll hang on to it for the time being. Manuel On Tue, 30 Aug 2005 02:31 pm, Jeremias Maerki wrote: > margin-left always stays on the left side. The FO spec makes a clear > distincti

DO NOT REPLY [Bug 36432] - [PATCH] JAI image does not release all resources / LinkageError not caught

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 36432] New: - [PATCH] JAI image does not release all resources / LinkageError not caught

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

Re: Error loading GIF image using JAI in FOP Trunk (was: Error w hile processing a PDF - OK)

Stephen, thanks for pointing this out (again). I'll post a patch to fix this. Manuel On Wed, 31 Aug 2005 07:02 am, Stephen Denne wrote: > Regarding a fop-users email mentioning: > > com/sun/media/jai/codec/FileCacheSeekableStream > > Reminded me of something I encountered recently: > > In my bri

Re: svn commit: r264856 - in /xmlgraphics/fop/trunk/src/java/org/apache/fop/render/rtf: TextAttributesConverter.java rtflib/rtfdoc/RtfText.java

[EMAIL PROTECTED] wrote: + + private static void attrBaseLineShift(EnumLength baselineShift, RtfAttributes rtfAttr) { + + String s = baselineShift.getString(); Use baselineShift.getEnum() to get the enum values that is assigned to a length. Never ever use the getString() me

Re: svn commit: r264863 - /xmlgraphics/fop/trunk/src/java/org/apache/fop/fo/FOText.java

[EMAIL PROTECTED] wrote: Modified: xmlgraphics/fop/trunk/src/java/org/apache/fop/fo/FOText.java URL: http://svn.apache.org/viewcvs/xmlgraphics/fop/trunk/src/java/org/apache/fop/fo/FOText.java?rev=264863&r1=264862&r2=264863&view=diff ==

RE: Error loading GIF image using JAI in FOP Trunk (was: Error w hile processing a PDF - OK)

Regarding a fop-users email mentioning: > com/sun/media/jai/codec/FileCacheSeekableStream Reminded me of something I encountered recently: In my brief experience (of a modified version of FOP 0.20.5 that I inherited), if the href is to a file, then its input stream is being given to JAI, JAI is

Re: FOP extension to output custom PostScript instructions

[Jeremias on extensions] Anybody opposed to my adding this? ... Not at all, but I assume that you ask because it can't be added as an extension that is completely seperated from FOP. That you have to make changes to FOP sources in order to add it. Yes, that's true. And that is IMO a bi

Re: API discussion (revived)

Jeremias Maerki wrote: I don't think you missed anything important except maybe your personal opinion how you'd propose to go on. :-) Ok. Step 0: Baseline rules. - No new Errors except possibly some sort of a FOPConfigurationError (JAXP implementations tend to have an equivalent). Does anybody

Re: page-number and page-number-citation problem

Luca Furini wrote: The Knuth-style page breaking algorithm gets a representation of a whole page-sequence Ah, I wasn't aware of this. Well, operating on a whole page sequence makes implementing widows/orphans and other keep conditions possible without backtracking, interesting. Very interestin

Let's write the release plan for the first preview release

The subject says it all: http://wiki.apache.org/xmlgraphics-fop/ReleasePlanFirstPR This is open for discussion. I'd really love to get the first release out by the end of September. Jeremias Maerki

Bug in PDFNumber.doubleOut()

It's interesting how many bugs you can find in ancient code that thousands of people use every day. :-) While debugging rendering differences between SVGs painted to PDF and PS I found some weird numbers being written into the PDF while basically the same code for PS wrote the expected numbers into

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

Chris Bowditch wrote: Peter B. West wrote: Couldn't let that one go by, Chris. These issues, which were critical to the creation of both Folio and FOray, were being thrashed out around the beginning of 2003. You've been around long enough to know that, haven't you? So for more than two yea

DO NOT REPLY [Bug 36408] - FOP hyphenation splits consecutive digits onto separate rows

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

Re: FOP extension to output custom PostScript instructions

On 30.08.2005 16:06:08 Finn Bock wrote: > [Jeremias on extensions] > > > Anybody opposed to my adding this? ... > > Not at all, but I assume that you ask because it can't be added as an > extension that is completely seperated from FOP. That you have to make > changes to FOP sources in order

RE: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

Chris Bowditch wrote: > ideas because they didn't yield 100% compliance. Regardless, > my main point in this thread was simply that compromise is > the key to getting to a release. Which is one of your points > above, right? Not really. I agree with the importance of getting along where possib

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

Peter B. West wrote: Couldn't let that one go by, Chris. These issues, which were critical to the creation of both Folio and FOray, were being thrashed out around the beginning of 2003. You've been around long enough to know that, haven't you? So for more than two years, the "pragmatic" Fop

Re: FOP extension to output custom PostScript instructions

[Jeremias on extensions] Anybody opposed to my adding this? ... Not at all, but I assume that you ask because it can't be added as an extension that is completely seperated from FOP. That you have to make changes to FOP sources in order to add it. And that is IMO a bit of a failure of FOP

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

Chris Bowditch wrote: Manuel Mall wrote: Fair enough, btw its not painful for me at all. I have joined the project with the goal to help to get FOP 1.0 out of the door in a relatively short timeframe (meaning months not years). To achieve that I am more than prepared to be pragmatic in the se

DO NOT REPLY [Bug 36408] - FOP hyphenation splits consecutive digits onto separate rows

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

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

Victor Mote wrote: Chris Bowditch wrote: This is an excellent goal. Sometimes it is all too easy to aim for 100% perfection and then FOP gets stuck - just like it has been for 2 years prior to 2005. Compromise is the key to getting 1.0 out of the door. This is grossly foul. I don't remem

DO NOT REPLY [Bug 36418] - [PATCH] PreviewPanel docs changed to reflect introduction of Renderable

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

RE: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

Chris Bowditch wrote: > This is an excellent goal. Sometimes it is all too easy to > aim for 100% perfection and then FOP gets stuck - just like > it has been for 2 years prior to 2005. Compromise is the key > to getting 1.0 out of the door. This is grossly foul. I don't remember anyone strivi

DO NOT REPLY [Bug 36418] New: - [PATCH] PreviewPanel docs changed to reflect introduction of Renderable

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

RE: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

Manuel Mall wrote: > Fair enough, btw its not painful for me at all. I have joined > the project with the goal to help to get FOP 1.0 out of the > door in a relatively short timeframe (meaning months not > years). To achieve that I am more than prepared to be > pragmatic in the sense of "getti

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

Manuel Mall wrote: Fair enough, btw its not painful for me at all. I have joined the project with the goal to help to get FOP 1.0 out of the door in a relatively short timeframe (meaning months not years). To achieve that I am more than prepared to be pragmatic in the sense of "getting things

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

On Tue, 30 Aug 2005 08:43 pm, Victor Mote wrote: > Manuel Mall wrote: > > PS: I can imagine Victor smiling now :-) : "I told you so > > that not leaving all property resolution to the LM stage is > > going to cause trouble". > > Trust me, I'm not smiling. As one of our U.S. Presidents was known > f

RE: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

Manuel Mall wrote: > PS: I can imagine Victor smiling now :-) : "I told you so > that not leaving all property resolution to the LM stage is > going to cause trouble". Trust me, I'm not smiling. As one of our U.S. Presidents was known for saying, "I feel your pain". In fact, it might be fairly

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

Manuel Mall wrote: PS: I can imagine Victor smiling now :-) : "I told you so that not leaving all property resolution to the LM stage is going to cause trouble". Not just Victor, Manuel. But please press on re-discovering the wheel. Peter smime.p7s Description: S/MIME Cryptogra

DO NOT REPLY [Bug 36379] - [PATCH] Revised percentage resolution system

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 36379] - [PATCH] Revised percentage resolution system

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 36379] - [PATCH] Revised percentage resolution system

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 36379] - [PATCH] Revised percentage resolution system

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 36379] - [PATCH] Revised percentage resolution system

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 36408] - FOP hyphenation splits consecutive digits onto separate rows

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

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

On Tue, 30 Aug 2005 04:16 pm, Manuel Mall wrote: > On Tue, 30 Aug 2005 04:05 pm, Finn Bock wrote: > > [Manuel] > > > > >>Agree, and I have a solution for that ready to go. > > > > > > I think this deserves some further comment / discussion. One, IMO > > > important, reason I want to do the evaluati

Re: page-number and page-number-citation problem

J.Pietschmann wrote: Maybe I'm wrong in trying to do so, but I'd like to handle both formatting objects in the same way. If page numbers can be resolved to strings early, it should be done. All the hassle for space readjusting, and perhaps reflowing content, should be reserved for forward refe

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

No, SVN doesn't have an attic. It operates on revisions exclusively, so you have to find out the revision (equals to the state of the repository at a certain point of time) in which the thing you look for is present. Try this: svn log http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/src/java

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

On Tue, 30 Aug 2005 04:05 pm, Finn Bock wrote: > [Manuel] > > >>Agree, and I have a solution for that ready to go. > > > > I think this deserves some further comment / discussion. One, IMO > > important, reason I want to do the evaluation during the FO parsing > > stage is that once we are in the L

Re: DO NOT REPLY [Bug 36379] New: - [PATCH] Revised percentage resolution system

[Manuel] Agree, and I have a solution for that ready to go. I think this deserves some further comment / discussion. One, IMO important, reason I want to do the evaluation during the FO parsing stage is that once we are in the LMs we lost the property inheritance information. That is someth

Re: Non-implemented props: border-*-precedence

[Jeremias Maerki] Perfect, Finn! I've just hacked together a little test extension that lets me evaluate properties and write failure messages to a singleton which a JUnit test case could process. It's very rough right now, but with a little more work this could really be cool for checking the F