[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [stellation-res] To what extent should literals be named?
|
> >-----Original Message-----
> >From: stellation-res-admin@xxxxxxxxxxxxxxx
> >[mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of David Shields
> >Sent: September 3, 2002 9:07 PM
> >To: stellation-res@xxxxxxxxxxxxxxx
> >Subject: RE: [stellation-res] To what extent should literals be named?
> >
> >
> >
> >Based on the comments to date, which indicate no strong sentiment one way
> >or the other, I suggest we try some literal naming, starting with command
> >names, and possibly option-related stuff as well. Jonathan, care
> >to have a
> >go? Since this won't affect API, I can put in changes as they come in.
> >
> >working on javadoc,
> >dave
> >
The two areas (commands and options) that you suggested that I look at both
involve strings that are visible outside the program since they name
commands and options that are or can be entered from the command line by a
user. This makes these strings potential candidates for
internationalization. Therefore I propose that we use the java facility for
resource bundles and property files to manage these strings. This, in no
way, commits you to actually do any internationalization, but it facilitates
things if and when you decide to go in this direction.
With this approach the strings are accessed indirectly using keys that the
Java resoure bundle support uses to lookup the required string based on the
locale in effect. Note that the keys themselves are strings so I will be
providing symbolic definitions for them.
Regards
Jonathan Gossage
Personal Email
jgossage@xxxxxxxx
Business Email
jonathan@xxxxxxxxxxxxxx
