I think these type of checks would be useful if available as an option (perhaps part of an extended 'debug' mode?). The default, of course, would be OFF, but could be enabled so users could 'see' what's happening.

Web Maestro Clay

On Jun 24, 2005, at 9:01 AM, Jeremias Maerki wrote:
Ah, ok. Thank you. Will shut up then. These checks would only have eaten

On 24.06.2005 17:44:28 Glen Mazza wrote:
The recommendation allows any property to be on any FO (First sentence
of section 5 of 1.1[1], but also somewhere in 1.0), regardless of its
utility.  So we don't need to mention this as a warning.

We *might* want to do this in a few areas though where newbies might
make very common mistakes (and be upset that FOP isn't working they way
they think it should be as a result), however.


[1] http://www.w3.org/TR/xsl11/#refinement

Jeremias Maerki wrote:

While creating the check for the span attributes a few minutes ago, I
wondered if we shouldn't actually warn about explicit non-inherited
properties on FO they don't apply to. We currently don't do that AFAICS.
Am I right that this is a task that we shouldn't forget?

Jeremias Maerki

Jeremias Maerki


Web Maestro Clay
<[EMAIL PROTECTED]> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Reply via email to