At 11:21 AM 7/13/01 +0200, Keiron Liddle wrote:
>
>On Thu, 12 Jul 2001 22:50:44 Karen Lease wrote:
>> We also need to think about what to do when we encounter this kind of
>> case. Obviously we want to inform the user. We could either stop on an
>> exception or just ignore the offending FO and keep going.
>
>Usually a spec has a section on how the processor should handle errors but
>I couldn't find it in the XSL spec.
You're right, doesn't seem to be anything said about content-model errors. I
like the idea of trying to help out the user; I would say that we ignore the
offending FO (and all descendants), with a warning (line, column, name, and
short explanation if possible), and continue if possible.
For example, let's say that someone's XSL has produced FO with a
page-sequence containing not only an fo:flow and a couple of
fo:static-contents, but a top-level fo:block by mistake. I can see errors
happen fairly often as people work up stylesheets. The user-friendly thing
to do would be to emit a warning about the fo:block, and continue checking
the tree. Maybe we'd catch several independent errors that way, and help
the user speed up the debugging/correction process.
One thing to consider is stopping the process after refinement, but before
layout, if there are any content-model errors. Or maybe all of this can be
subject to user control?
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
