Lists Home |
Date Index |
- From: Miles Sabin <firstname.lastname@example.org>
- To: David Megginson <email@example.com>, XMLDev list <firstname.lastname@example.org>
- Date: Wed, 5 Jan 2000 11:51:04 -0000
David Megginson wrote,
> Miles Sabin writes:
> > [snip: query about Parser.setLocale()]
> Error reporting.
OK, I've slept on this and, although I can see there's a case
to be made for it, I'm not convinced.
Many software modules need to do error reporting of some sort
or another. Typically they'll simply use the platform default
Locale for localization rather than allowing it to be
configurable. That's the right thing to do, because error
messages are normally delivered locally, and the rare cases
where they're not aren't enough to justify adding setLocale()
methods to an interface (cp. pretty much all the standard
java.*.* classes, eg. java.util.HashMap).
I'm not convinced that an XML parser is special in this
respect, so I don't think org.xml.sax.Parser should have this
method. For the most part error messages will be delivered
locally, so the platform default Locale is fine. And in the
cases where error messages are delivered non-locally (ie.
an XML parser as part of a web application which delivers
errors to a remote user) the non-local Locale probably won't
be available _anyway_ ... we might have a character encoding
or language preference (via HTTP's Accept-Charset: and Accept-
Language:) but there's no defined mapping from those
preferences to a Locale. Worse still, there's no defined
mapping from a Locale to a preferred character encoding, so
a configured Locale wouldn't help all that much anyway.
Miles Sabin Cromwell Media
Internet Systems Architect 5/6 Glenthorne Mews
+44 (0)20 8817 4030 London, W6 0LJ, England
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)