From: Dalibor Topic <robilad@yahoo.com>
To: Mark Wielaard <mark@klomp.org>, Andrew Haley <aph@redhat.com>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: ResourceBundle variants and child variants
Date: Tue, 10 Dec 2002 08:45:00 -0000 [thread overview]
Message-ID: <20021210164514.8588.qmail@web10006.mail.yahoo.com> (raw)
In-Reply-To: <1039458865.2921.233.camel@dogx200-017>
--- Mark Wielaard <mark@klomp.org> wrote:
> Hi,
>
> On Mon, 2002-12-09 at 12:27, Andrew Haley wrote:
> > Mark Wielaard writes:
> > > Mauve contains a couple of
> java.util.ResourceBundle checks that test for
> > > "child variants". The Java Class Libraries,
> Volume 1, Second Edition
> > > explains these things and gives some examples.
> e.g
> > > ErrorResources_de_CH_WIN_95 and
> ErrorResources_de_CH_WIN_311 are both
> > > child variants of ErrorResources_de_CH_WIN.
> Mauve even contains some
> > > tests to check that these child variants are
> correctly searched for.
> > >
> > > The API Spec as found online however does not
> talk about child variants
> > > at all. And a quick test against the Sun JDK
> 1.4.1 implementation seems
> > > to suggest that it does not implement support
> for these child variants.
> > >
> > > Which specification should we take as
> normative?
> > > Do the different class libraries
> implementations implement it?
> > > (GNU Classpath and libgcj don't support them,
> kaffe does.)
> > > Should these tests be removed from Mauve?
> >
> > I would think so. There's no way that Mauve
> should be testing
> > anything outside the specifications.
>
> But the question is, what is considered The
> Specification?
> I use The Java Class Libraries books a lot when
> implementing classes.
> And since it describes the child variants it could
> also be argued that
> the online API doc (and most implementations except
> for Kaffe) is
> flawed.
I think I remember the time when there were child
variants for *Locales* in wide useage in the EU, due
to pending conversion to a new currency. de_DE_EURO
anyone?
I don't know if that means anything to ResourceBundle
support, but I'd expect it to match Locale's rules for
resolution. I think one of the examples for Locale in
Java Class Libraries 2n Ed Volume 1 mentions a
norwegian Locale with the child variant "bookmal".
As I understand the spec for Locale, it says "Where
there are two variants, separate them with an
underscore, and put the most important one first." ,
so it is possible to have child variants. They also
give an example in the next sentence,
"Traditional_WIN" . See
http://java.sun.com/j2se/1.4/docs/api/java/util/Locale.html
, the paragraph just below the country code link.
best regards,
dalibor topic
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
next prev parent reply other threads:[~2002-12-10 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 10:46 Mark Wielaard
2002-12-09 9:39 ` Andrew Haley
2002-12-09 10:34 ` Mark Wielaard
2002-12-09 10:38 ` Andrew Haley
2002-12-09 11:10 ` Mark Wielaard
2002-12-10 3:03 ` Andrew Haley
2002-12-10 8:45 ` Dalibor Topic [this message]
2002-12-10 12:23 ` Mark Wielaard
2002-12-10 14:18 ` Tom Tromey
2002-12-10 14:31 ` Mark Wielaard
2002-12-12 7:39 ` Mark Wielaard
2002-12-11 2:47 ` Andrew Haley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021210164514.8588.qmail@web10006.mail.yahoo.com \
--to=robilad@yahoo.com \
--cc=aph@redhat.com \
--cc=mark@klomp.org \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).