> 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?
I would prefer java.util.Locale:
setLocale(java.util.Locale locale)
is the standard Java pattern. Since Java also provides a 3-argument
variant of the Locale constructor, I don't think setLocale(String
language, String country) is sufficient.
James