I found and reviewed the discussion regarding the move to Avalon (ref: http://marc.theaimsgroup.com/?l=fop-dev&m=102266666606705&w=2 ).
I also appreciate your point that some aspects of configuration have already been 're-enabled'; as exemplified in CommandLineStarter.run() which calls commandLineOptions.getOutputFile() and commandLineOptions.getRendererOptions().
I want to use the -c option to import a font refed in a userconfig.xml file as per http://xml.apache.org/fop/fonts.html#Register+the+fonts+within+FOP- N10261
I can see that CommandLineOptions.parseOptions(...) is caching my userconfig.xml file in its userConfigFile member. Grepping the source does not reveal anyone calling the getUserConfigFile() accessor and I'm unable to find anyone parsing the userConfigFile, so this is what I mean when I say that I suspect configuration is not completely "re-enabled."
So, I guess my question now is: Are CommandLineOptions.userConfigFile font tags being processed? If so, then where? If not, then... yes, given some pointers, I'm interested in helping to get it working.
-- Bob
On Tuesday, April 1, 2003, at 05:23 PM, Keiron Liddle wrote:
I'm reviewing the developer branch code and believe that although
CommandLineOptions parses the -c option and caches a userConfigFile,
the config file is not processed. FOP 0.20.5rc2 has an
org.apache.fop.configuration package for handling the -c option. Hence
it appears the -c option is not yet implemented on the developer branch.
That is correct. The old configuration package has been removed and we will be
using the avalon-framework configuration to do the work.
As for re-enabling it, it depends on what part you mean. To do the loading, parsing
it is only a couple of lines of code.
To do more of the using that configuration will need a bit more work but some of it
has been done. That also depends on how the avalon integration will be put
together.
Maybe Jeremias could give some more pointers in this area.
Do you want to give a go helping out. What areas are you looking for to configure?
Could someone please confirm if this is correct and tell me the status of re-enabling the -c option on the developer branch?
Thanks, Bob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
