FOP is not permitted to consider it an error, and in fact really should not 
even warn about it. See Section 2.2 in the specification: an element from 
the XSL namespace (e.g. fo:block) may have an attribute from a non-XSL 
namespace, provided that the namespace prefix maps to a non-null URI. The 
processor may act on such an attribute provided that it doesn't affect 
behaviour otherwise mandated by the spec, and a processor must ignore such 
an attribute if it doesn't know what to do with it.

Arved Sandstrom

At 12:34 PM 10/23/01 -0400, you wrote:
>   That's  a good idea, my only concern is that at some point in the future
>FOP might  consider it an error and not a warning.   Should  I be concerned
>about this?   Scott    -----Original Message-----
>From: Giannetti, Fabio    [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, October 23,    2001 11:54 AM
>Subject: RE:    XSl-FO question
>   Hi    Scott,       you can generate your own namespace with a field that
>   tells you if that block is containing a data, then when FOP will process
>the    document it will ignore this property .. giving you some Warnings,
>but the    file will be rendered fine.   So    you can define a new
>namespace like:      xmlns:foo=http://foo";   then you can define    this
>attributes in your blocks that contains the data   <>   and    modify only
>them.   Hope    this helps, Fabio        -----Original Message-----
>From: Scott Moore      [mailto:[EMAIL PROTECTED]]
>Sent: 23 October 2001      16:12
>To: Fop-Dev (E-mail)
>Subject: XSl-FO      question
>      >  I      need to save the XSL-FO files for later "concatenation"
>with other generated      reports.            <> as containing a date
>string?             distinguish parts of      the document that are
>related.           Thanks for any      help!     Scott
Fairly Senior Software Type
e-plicity (
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia

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

Reply via email to