G'day all,
Hi Sean!
For those who don't know who Sean is, then he is a i18n guy that suddenly
showed up
and wanted to help us i18n JBDS and by consequence also JBoss Tools - so
help him
out if he gets lost ;)
I gather that a lot of the Tools code already uses externalised
strings
(ie using ResourceBundles to fetch strings from .properties files), and
I don't think it uses the English text as the key (the way GNU gettext
does in Linux land), but rather the usual Java convention of artificial
string keys like "SharedIntroConfigurer_gettingstarted_nav".
Yes, it uses the standard eclipse way (this is not ResourceBundles in the
code,
but the property files are the same)
I personally prefer the English-as-key approach (smaller code
changes,
somewhat more readable code, and no artificial keys to keep track of),
but artificial keys have their advantages too, and of course it's
important to maintain a consistent approach.
sure, gnu text seem to be cool but I haven't seen a tooling stack for it
that
will work on windows where most of our devs (and users) are currently.
Do you have any tools or scripts that you use to manage the
artificial
keys, make sure they're unique, remove obsolete keys, things like that?
How do you deal with this sort of thing?
No, not in particular. But eclipse has a few validation checks for some of
these things. I haven't used them much so can't even really point to them
;)
/max