cvs commit: xml-fop/conf fop.xconf

2004-03-05 Thread pbwest
pbwest 2004/03/05 22:03:44 Added: conf Tag: FOP_0-20-0_Alt-Design fop.xconf Log: For later use in integrating alt-design with HEAD Revision ChangesPath No revision No revision 1.3.2.1 +0 -0 xml-fop/conf/fop.xconf

Re: fop.xconf

2004-03-04 Thread J.Pietschmann
Peter B. West wrote: What's the intention for fop.xconf? It's been there for ages with the intent to provide for configurable, easily changed defaults. Unfortunately 1. There's not much more than PDF filters (in the maintenance branch), and if all filters are deleted, the code uses a flate

fop.xconf

2004-03-03 Thread Peter B. West
Fops, What's the intention for fop.xconf? Is it to be processed by the user agent? What about user configuration? Have these things been decided yet? Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html

Re: fop.xconf

2004-03-03 Thread Glen Mazza
I haven't looked at it--but this was before my time on the project, fop.xconf hasn't been altered since December 2002. It appears to be related to Avalonization of FOP. For the benefit of other relative newcomers, it is located here: http://cvs.apache.org/viewcvs.cgi/xml-fop/conf/fop.xconf

cvs commit: xml-fop/conf fop.xconf

2002-12-14 Thread olegt
olegt 2002/12/14 07:35:28 Modified:conf fop.xconf Log: Fixed well-formedness. Revision ChangesPath 1.3 +1 -1 xml-fop/conf/fop.xconf Index: fop.xconf === RCS file: /home/cvs/xml-fop

cvs commit: xml-fop/conf fop.xconf

2002-07-10 Thread keiron
keiron 2002/07/10 01:59:16 Added: conf fop.xconf Log: start of example configuration file contains default values so that if used will have no effect by default no configuration is needed, only if values need to be changed Revision ChangesPath 1.1