Re: Failing tests

Same here. Christian, can you give us some details about your environment? JDK version, OS, Ant Version... On 14.11.2005 03:38:58 Manuel Mall wrote: > On Mon, 14 Nov 2005 10:19 am, Christian Geisert wrote: > > > In BugZilla terminology: WORKSFORME > > > > > And a dozen more with the same error.

Re: System.err

FYI, I'm working on that. The strategy is to remove stray System.out/err or Exception.printStackTrace() calls where possible, or pipe them to a logger instead. Some of those will need some additional work in the area of exception handling. On 13.11.2005 23:37:17 Nils Meier wrote: > Hello > > jus

Re: Failing tests

Jeremias Maerki schrieb: > Same here. Christian, can you give us some details about your > environment? JDK version, OS, Ant Version... I just tried it with a fresh checkout and it worked. Sorry for the noise. Christian

DO NOT REPLY [Bug 37330] - [PATCH] FOP Bridges not properly registered with Batik

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: System.err

This is done now. Some printStackTrace() calls are left mainly in the Graphics2D implementations. That will be looked at when we move them to Commons. We'll have quite a pile of work before us to improve the whole exception handling. But that's not for today. Thanks for reminding us about fixing

DO NOT REPLY [Bug 37330] - [PATCH] FOP Bridges not properly registered with Batik

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 37236] - [PATCH] Fix gradients and patterns

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: Hyphenation

Manuel Mall wrote: In preparation for the upcoming 0.90 release I was reviewing the examples in examples/fo/basic. When looking at the output of hyphen.fo I noticed that in both the English hyphenation example and the German hyphenation example 4 consecutive lines ending with hyphens were gen

DO NOT REPLY [Bug 37330] - [PATCH] FOP Bridges not properly registered with Batik

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: Hyphenation

On Mon, 14 Nov 2005 09:54 pm, Luca Furini wrote: > Manuel Mall wrote: > > In preparation for the upcoming 0.90 release I was reviewing the > > examples in examples/fo/basic. When looking at the output of > > hyphen.fo I noticed that in both the English hyphenation example > > and the German hyphena

DO NOT REPLY [Bug 37330] - [PATCH] FOP Bridges not properly registered with Batik

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 37236] - [PATCH] Fix gradients and patterns

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: Preparing for the first release

Manuel Mall schrieb: [..] >>IMHO there should be a changes document (as part of the >>distribution), at least starting after the 1.0 release. > > Yes there should - but for now: Just remove CHANGES and update README? I'd say yes. -- Christian

DO NOT REPLY [Bug 36480] - [PATCH] Space support in RTF rendering

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: Preparing for the first release - Examples

On 13.11.2005 19:53:32 Andreas L Delmelle wrote: > On Nov 13, 2005, at 18:00, Andreas L Delmelle wrote: > > > On Nov 13, 2005, at 17:36, Jeremias Maerki wrote: > > > > > >> The other question is: > >> What's the "box"? The containing area? > > > > Yep. I think this is answered in the definition

Re: Preparing for the first release

Manuel Mall a écrit : As the project hasn't done a release for a long time and especially no release of the new codebase we should test probably a bit more extensively than usual that the distribution builds actually are working and don't contain any 'cheap' errors. To that effect I have buil

Re: Preparing for the first release

I agree with you two. Therefore, I've resurrected status.xml, added it to our website again and prepared it so we can start using it after the release. BTW, I think I'm through with all the things I wanted to do. What's left now: - write the README/release notes - Create a copy of the xdocs/trunk

fo:marker and white space

I was looking at clipping warnings generated by examples/fo/markers/hide.fo when I noticed that white space around fo:marker seems significant with respect to the output generated when the marker is retrieved, e.g.: some text when retrieved produces: some text while: some t