Re: Next release - when?

Sorry to be a little late but I'm -1 on merging product documentation with project documentation again. I found that VERY nice to have because it gives us a cleaner structure. For me, the most important thing is to be able to simplify release management which is still somewhat too work-intensive. I

Re: Next release - when?

On 14.01.2008 08:58:04 Max Berger wrote: > Dear Fop Devs, > > I think we are mixing two ideas here: > > One idea (1) was to release 0.95rc, and then two weeks later 0.95 > > The other idea (2) is to release 0.95 and call it 0.95rc instead of 0.95beta. > > (1) I think makes sense. It would mean

Re: Next release - when?

Hi, Jeremias Maerki wrote: > On 14.01.2008 08:58:04 Max Berger wrote: >> Dear Fop Devs, >> >> I think we are mixing two ideas here: >> >> One idea (1) was to release 0.95rc, and then two weeks later 0.95 >> >> The other idea (2) is to release 0.95 and call it 0.95rc instead of 0.95beta. >> >> (1)

Re: Next release - when?

Hi Clay, Sorry I have to agree with Jeremias here, I think the 0.93, 0.94, Trunk tabs are ok. In fact the general structure of the website is more or less ok to me. But I think the following could be improved: - the skin looks a bit old now. Maybe upgrading to Forrest 0.8 (+1, BTW) will impro

Namespaces for attributes in instream objects

Dear Fop-Devs, I've just recently encountered a possible "bug" in the jeuclid plugin for fop. A complete .fo file is added at the end of the mail. In this file there is a foreign math object: x , which, as you can se

Re: Namespaces for attributes in instream objects

I use attributes in the default namespace in Barcode4J and have no problems there. I've just updated my local JEuclid working copy and tried once again to build it or set it up in Eclipse but I failed. Once again. I have no nerves for Maven and won't waste one more second of my life on a Maven-enab

Re: Next release - when?

I'll spend some more time working on the 0.8 upgrade. I'll also look into implementing 'views' for the versioned docs. I guess things have changed enough between 0.93 & 0.94 so we really do need 0.93 (although when 0.95 is released we should be able to omit 0.94?)... If we're going to have release

DO NOT REPLY [Bug 42845] - Printing error. Prints charater+1.

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: Disable 900 penalty when not all cells have contributed in tables?

Thanks for all your feedbacks. Hearing no objections, I’ll then commit the change in the next days. Vincent Vincent Hennebert wrote: > Hi, > > The title may be a little cryptic for those who aren’t familiar with the > table layout code :-\ But basically it corresponds to the following: > > Wh

DO NOT REPLY [Bug 44229] - Replacing GU in slot 0. Some content may not be painted.

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 44229] - Replacing GU in slot 0. Some content may not be painted.

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 42845] - Printing error. Prints charater+1.

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 44229] - Replacing GU in slot 0. Some content may not be painted.

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 44229] - Replacing GU in slot 0. Some content may not be painted.

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 44229] - Replacing GU in slot 0. Some content may not be painted.

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 44229] - Replacing GU in slot 0. Some content may not be painted.

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 44229] New: - Replacing GU in slot 0. Some content may not be painted.

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 44229] - Replacing GU in slot 0. Some content may not be painted.

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: Next release - when?

On Jan 10, 2008, at 18:05, Jeremias Maerki wrote: Apologies for the rather late reply: I think we should start to plan the next release. How about targeting the end of February or beginning of March? Good idea. Without much thinking, the following items are on the table: - Stabilizing tabl

Re: Namespaces for attributes in instream objects

On Jan 14, 2008, at 14:23, Max Berger wrote: Hi Max, I've just recently encountered a possible "bug" in the jeuclid plugin for fop. Just checking (would make tracking it a bit easier): Do you have any idea if this ever worked, and if yes, when this stopped working? (or: Do you remember havi

Re: Namespaces for attributes in instream objects

On Jan 14, 2008, at 19:04, Andreas L Delmelle wrote: On Jan 14, 2008, at 14:23, Max Berger wrote: - If it is not, where do i need to start looking for the bug? Jeuclid completely ignores namespaces in attributes, so it is either in the fop/plugin interface, fop itself, or the xerces parser?

DO NOT REPLY [Bug 42845] - Printing error. Prints charater+1.

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