Re: User configuration

Yes, I think we agreed (when we were discussing the Avalon Logger to Commons Logging switch) to stay with Avalon configuration unless and until something better is found. If you find something different you'd like to recommend, just let us know--now's the time! Only concern I have about Avalon

AW: [Patch Proposal] Integrate FOP with Cocoon/Excalibur Source Resolving

> What about interface javax.xml.transform.URIResolver with > > javax.xml.transform.Source resolve(String href, String base) ? > > Note that org.apache.xml.resolver.tools.CatalogResolver is an > implementation of this interface using various sorts of catalogs. Well, i'm not sure if thats hel

User configuration

If I understand correctly, apps.Fop.main() does not do much with the user configuration file that can be specified with the -c command line option. I would like to make this work. Before I put work in it, I would like to ask: Do we stick with avalon configuration? I had a quick look at Jakarta Com

Re: [Patch Proposal] Integrate FOP with Cocoon/Excalibur Source Resolving

On Fri, Apr 30, 2004 at 10:28:17AM +0200, Stefan Seifert wrote: > I understand understand your concerns concering avalon (and followed myself the > thread you noticed in the last weeks). > > But it would be great to have any possibility to "plug in" a own source resolving > concept in FOP in any

RE: [Patch Proposal] Integrate FOP with Cocoon/Excalibur Source Resolving

OK - i will do that! Stefan > -Original Message- > From: Glen Mazza [mailto:[EMAIL PROTECTED] > Sent: Friday, April 30, 2004 2:35 PM > To: [EMAIL PROTECTED] > Subject: Re: [Patch Proposal] Integrate FOP with > Cocoon/Excalibur Source > Resolving > > > Absolutely, thanks! Indeed, if th

Re: [Patch Proposal] Integrate FOP with Cocoon/Excalibur Source Resolving

Absolutely, thanks! Indeed, if there is *functionality* you need that can be programmed natively into FOP--for the use of all, without needing to tie us to particular frameworks--fantastic--please just enter this enhancement request into Bugzilla so it doesn't get lost (you can just reference

DO NOT REPLY [Bug 28705] - PDF Text search doesnt work for embedded fonts.

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: [Patch Proposal] Integrate FOP with Cocoon/Excalibur Source Resolving

I understand understand your concerns concering avalon (and followed myself the thread you noticed in the last weeks). But it would be great to have any possibility to "plug in" a own source resolving concept in FOP in any case! This could be Excalibur or anything else. Consider something like

DO NOT REPLY [Bug 28706] - [PATCH] More justification problems

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 28314] - [PATCH] Alignment of the last line in a justified block

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 28706] New: - [PATCH] More justification problems

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 28705] New: - PDF Text search doesnt work for embedded fonts.

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: [Patch Proposal] Integrate FOP with Cocoon/Excalibur Source Resolving

I don't think so. For one, the 0.20.x branch is basically frozen. But more fundamentally, we're moved away from Avalon in 1.0. Like Xalan, Batik, AntennaHouse and RenderX, we're a base tool--we shouldn't be sitting on frameworks which would then require other users of FOP to import that fram