Turning off inappropriate errors?

[Timothy Dean <ti...@guidant.com>]

Hello,

I have an XSL-FO file that I want to generate into PDF. Along with the usual
FO content, the file contains miscellaneous attributes that are not part of
the XSL namespace. My goal is to embed a variety of custom "tags" into the
FO I'm generating that will later be used by an in-house automated testing
tool.

According to the XSL-FO spec, I should be able to do this. Specifically,
section 2.2 of the spec states the following:

"An element from the XSL namespace may have any attribute not from the XSL
namespace, provided that the expanded-name of the attribute has a non-null
namespace URI. The presence of such attributes must not change the behavior
of XSL elements and functions defined in this document. Thus, an XSL
processor is always free to ignore such attributes, and must ignore such
attributes without giving an error if it does not recognize the namespace
URI. Such attributes can provide, for example, unique identifiers,
optimization hints, or documentation."

Despite this statement in the XSL-FO spec, I find that FOP gives me a bunch
of error messages like this:

"[ERROR] property 'xform:resourcePath' ignored"

Obviously, FOP is correctly ignoring the stuff it does not recognize.
However, this does not comply with the spec which says that this condition
should not give an error.

Is there any way to configure FOP so that it will not flag these attributes
from an unrecognized namespace as errors? I don't want to turn off the
flagging of real errors, just these particular ones that probably shouldn't
be there.

Any ideas?

Thanks,

- Tim


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org

Re: Turning off inappropriate errors?

[jim kraai <ji...@kraai.org>]

J.Pietschmann wrote:

> Timothy Dean wrote:
> 
>> Is there any way to configure FOP so that it will not flag these 
>> attributes
>> from an unrecognized namespace as errors?
> 
> 
> There is no easy way to configure FOP this way. Your best bet is
> to disable the message in the source and recompile.
> 
> J.Pietschmann

What's your environment?  Some un*x, Windows, or Mac, or ???

What about piping the output through something like so:
fop_cmd infile.fo outfile.pdf | \
   grep -Ev 'namespace:|\[info\]|anything-else-annoying'

a workable grep string could be:
   grep -Ev 'ignored$|not implemented yet$'

--jim



---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org

Re: Turning off inappropriate errors?

["J.Pietschmann" <j3...@yahoo.de>]

Timothy Dean wrote:
> Is there any way to configure FOP so that it will not flag these attributes
> from an unrecognized namespace as errors?

There is no easy way to configure FOP this way. Your best bet is
to disable the message in the source and recompile.

J.Pietschmann


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org