From: andrew welch <andrew.j.welch@gm...> - 2006-06-13 10:13:47
Just came across this error after a typo:
SESU0007: Encoding US-ASII is not supported: using UTF8
Is there any reason this isn't a compile time error instead of a
recoverable run-time error? I can't see why you would want this
fallback behaviour here....
From: Michael Kay <mike@sa...> - 2006-06-13 10:40:09
The serialization spec has gradually changed (like the rest of XSLT) from a
philosophy of "carry on at all costs" to a philosophy of "report errors
early and make them fatal". This recovery action is a hang-over from the
earlier approach, and it will change in the next Saxon release. In fact the
spec currently allows the fallback recover in the case of the XML and XHTML
output methods, but not for HTML and TEXT. The logic to this, I suppose, is
that with XML, UTF-8 is always valid, and even if it wasn't your preferred
encoding, any XML parser is going to accept it.
(Incidentally, I see that the 8 June editions of the specs are now online, a
few days later than planned...)
> -----Original Message-----
> From: saxon-help-bounces@...
> [mailto:saxon-help-bounces@...] On Behalf
> Of andrew welch
> Sent: 13 June 2006 11:14
> To: saxon-help@...
> Subject: [saxon] Output encoding not supported
> Just came across this error after a typo:
> Recoverable error
> SESU0007: Encoding US-ASII is not supported: using UTF8
> Is there any reason this isn't a compile time error instead
> of a recoverable run-time error? I can't see why you would
> want this fallback behaviour here....
> saxon-help mailing list