SAX 1.0beta: Three bugs so far

[David Brownell]

> > BUG #2: Parser.setLocale takes only one String argument
> > 
> >    As will quickly become apparent, I am not an expert in
> >    localisation.  I have discovered that localisation requires both
> >    a language code _and_ a country code, so I have changed the
> >    interface prototype to
> > 
> >      public abstract void setLocale (String language, String country)
> >        throws SAXException;
> > 
> >    Does this look correct?  Would people prefer that I use the
> >    java.util.Locale class?

Locale ...

> I think a single string, or unspecified parts, would be better.  XML
> allows RFC 1766 language identifiers, which can include i-cherokee and
> x-klingon.  The language-country form is only one class of valid
> language identifier.

But this is instructions to the parser, which will be using the
standard Java localisation facilities which center around Locale
objects in order to format any messages.  It's not related to the
text of the document.

- Dave


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)