Re: Getting breaks: revisited

On Tue, 2002-12-03 at 21:56, J.Pietschmann wrote: > Oleg Tkachenko wrote: > > btw, how does such a case addressed by the spec? Apparently FOP, antenna > > and xep do squeeze content. Isn't it an example of overconstrained > > geometry (5.3.4)? > > It can be interpreted as such in the presented c

DO NOT REPLY [Bug 15048] - Unwanted page break after image linked by external-graphic in region body

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 3044] - keep-together not functioning

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://nagoya.apache.org/bugzilla/show_bug

Re: alt.design info

sri vela wrote: I would like to know about fop alt.design. Where can i find the documentation for this? will it change the entire old design ro part of it? What should i do to involve in alt.design. It's http://xml.apache.org/fop/design/alt.design/index.html -- Oleg Tkachenko eXperanto team Mul

CVS of the maint. branch

Hello together, i'm looking for the current cvs version of the maintenance branch (0.20.5). I have no possiblity to get it through CVS (our firewall blocks that). Is there another way to get the source of the current version? -- regards Timo Haberkern EMEDIA OFFICE GmbH Wingertstr. 4 74850 Sc

Re: CVS of the maint. branch

Timo Haberkern wrote: i'm looking for the current cvs version of the maintenance branch (0.20.5). I have no possiblity to get it through CVS (our firewall blocks that). Is there another way to get the source of the current version? afaik, no way. Nightly snapshots hold the trunk code. Ask your

bug #13586

Hello there! What do you think about http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13586? Stefan asks us to use something like float currentLetterSpacing = (float) 9.99; instead of float currentLetterSpacing = Float.NaN in PDFRenderer.java due to jre-1.3.1 for linux-alpha bug. For me i

DO NOT REPLY [Bug 14248] - 51-page FO example, could be added to the samples

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://nagoya.apache.org/bugzilla/show_bu

Why use XML configuration files?

Hello, I noticed that the apache project uses mostly XML files for configuration. Personally I prefer using ".properties" files because then I don't have the overhead of parsing the file each time. So what's the advantage of using XML files? Thanks for any answers... Roland ---

DO NOT REPLY [Bug 8635] - FOP replace japanese chars into # on Linux

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://nagoya.apache.org/bugzilla/show_bug

DO NOT REPLY [Bug 12268] - FOP 0.20.4 cause PDF buffer append for each 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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 12864] - Incorrect behaviour for multiple columns on page

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 13295] - different results using xml or fo (from the same xml-file)

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 13451] - rendering of SVG with "strokeSVGText" = false causes exception

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://nagoya.apache.org/bugzilla/show_bu

FOP schema

While working on an FAQ for FO dtd & schema, I see that we have two schema in docs/foschema: fop4f.xsd & fop4.xsd. They are similar. Does anyone know what the purpose for both is, why we have 2, or the 4 & 4f designations? Thanks. Victor Mote

bugzilla shake-up is over

Hello there! Well, bugzilla shake-up is over, sorry if I closed something not-to-be-closed or leave something-to-be-closed, but anyway I believe we can say bugzilla is cleaned up now. Now it's 111 entries in there (it was 188 IIRC): Blockers: 3 Criticals: 6 Majors: 17 Normals:

Re: FOP schema

Victor Mote wrote: While working on an FAQ for FO dtd & schema, I see that we have two schema in docs/foschema: fop4f.xsd & fop4.xsd. They are similar. Does anyone know what the purpose for both is, why we have 2, or the 4 & 4f designations? I think fop4f.xsd is the latest one. Anyway Chuck Paus

Re: alt.design info

sri vela wrote: Hi all, I would like to know about fop alt.design. Where can i find the documentation for this? will it change the entire old design ro part of it? What should i do to involve in alt.design. Thanks in advance. Sri, Sorry I wasn't able to get back to you earlier. There is a new

Re: FOP schema

Victor Mote wrote: While working on an FAQ for FO dtd & schema, I see that we have two schema in docs/foschema: fop4f.xsd & fop4.xsd. They are similar. Does anyone know what the purpose for both is, why we have 2, or the 4 & 4f designations? Victor, I think that Chuck was appending a letter to

Redesign issues

Arved Sandstrom wrote: You're being absolutely honest, which is cool - I'll be absolutely honest also. It seems to me like the mainstream rewrite is in trouble. Very few people understand it or have [clearly] bought into it. This is no comment on its technical merits, by any means. OTOH, only on