You have nicely summarised the references to the user agent in the spec 
(except for the first one, invalid markup error handling, which I think 
you have added.)  However, my problem with the notion in the spec of 
user agent remains.  The authors have never bothered to define it, and 
we are left to work out what, exactly, it is from the various 
references.  The references that we have - certainly the references to 
non-interactive agents - are all to configuration items.  At the moment 
these things are, as I said, in the XML files.  It would, prima facie, 
be straightforward to get this from the configuration, in whatever form 
that eventually takes, whether we continue to use the XSLT, or introduce 
the properties into the CVS tree.  I.e., whatever form the expression of 
the properties takes, we would need to extract certain key property 
values from the configuration.

Assuming that we have no plans to go into the interactive presentation 
business as yet, we can disregard the interactive elements.  Even where 
an interactive agent would presumably expose the options for 
modification, those elements would still require initial values.  For 
our purposes, I think that "user agent" functions should be merged into 

Incidentally, I think the multi-properties, title and hot links elements 
should be in the "Interactive" list.  The aural properties 
(pause-before, pause-after, voice-family) are not necessarly 
interactive.  It would be quite feasible to produce an audio file 
rendering of a document within FOP.


Keiron Liddle wrote:

>maybe this could answer your question:
>ie. FOP is the user agent but in some cases people might want to alter
>certain behaviour. So we provide a class to enable this.
>On Tue, 2002-06-04 at 19:29, Peter B. West wrote:
>>As a result of this exercise, I remain as confused as ever. The most 
>>general sense of "user agent" seems to be "fo processor". There are 
>>"interactive user agents" which may have "user agent windows". User 
>>agents determine actual values for a number of enumerated values, and 
>>determine a number of critical default values. Things which are 
>>currently defined in Properties XML files, and transferred from there 
>>into the source code, are therefore user agent functions.

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

Reply via email to