Re: Rendering time configuration settings using fo:declarations

[Chris Bowditch]

Adrian Cumiskey wrote:

snip/



Something like this shouldn't be too difficult to implement (any 
volunteers?) and I think it might provide quite a bit of value.  It 
would be important to remember that the lifetime of these settings would 
only remain within the rendering run of the particular document that is 
being processed and subsequent documents being processed would revert 
back to FOP's default startup time settings.


Yes I think this would definitely be a useful feature :) A number of 
Renderer options such as ps-page-setup are implemented as extension 
elements which allows them to be changed on a document by document 
basis. Currently its not possible for options which are not implemented 
as extension elements which can be an annoying restriction in some projects.


I have no time to help with the implementation though!

Thanks,

Chris



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Rendering time configuration settings using fo:declarations

[Andreas L Delmelle]

On Jan 15, 2008, at 18:11, Adrian Cumiskey wrote:

Hi

A thought occurred to me whilst implementing something and I  
thought I would share it with you..  I don't have time to implement  
this but maybe somebody else would like to pick up this idea/ 
suggestion...


Basically, I was wondering if anyone thought it would be a useful  
feature to be able to provide renderer configuration settings  
within the fo:declarations section of an FO document?




Splendid idea to post it here. I sure do hope it reaches the right  
person for the job.


These settings could resemble and override any user configuration  
settings that may have been set at startup time through the API or  
user configuration file (e.g. fop.xconf).  So the top of your FO  
document might look something like the following :-


fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
   fo:declarations
  fox:strict-validationtrue/fox:strict-validation


Basically a cool idea, but I would not put it in the default  
extension namespace. Instead, we could reserve a special FOP-config  
namespace for it.
Definitely seems to have a lot of potential to be able to include the  
configurable settings at the XSLT stage, if desired.


Those using Saxon 8-SA, could then have that config file validated  
against the fop-configuration.xsd at runtime.



Cheers

Andreas

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]