axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Butek" <>
Subject Re: AXIS System Integration Guide - with internationalization
Date Fri, 02 Nov 2001 13:30:28 GMT
Having a numerical suffix on a free-form string is brief and, if you've
found that it helps, it's an easy enough addition.  I'll add that to the

I've also discovered one change I'd like to make to the document.  It
states that the variable syntax is %s0, %s1, etc.  I'd like to change that
to {0}, {1}, etc.  This way we can use java.text.MessageFormat and the
getMessage code becomes very simple.

Russell Butek

Dirk-Willem van Gulik <> on 11/01/2001 11:41:59 AM

Please respond to

Subject:  Re: AXIS System Integration Guide - with internationalization

On Thu, 1 Nov 2001, Russell Butek wrote:

> 1.  Meaning.  Keys of the form: AXIS00001, AXIS00002, have no meaning and
> are merely placeholders.  You cannot read the code and get a reasonable
> idea of what the message is.  Folks can be a little descriptive with
> free-form keys:
> noOperation=No operation name specified.

>            - you must assign a key ( A-Za-z0-9 )

I really meant assiging keys as


(as I suspect that people will draw on pools with common translated
strings; i.e. some common shared pool across projects).

The '01' is there because (as you say):

> What do you mean by "reuse"?  Do you mean you should not have an entry
> abc=xyz
> and then later change that to be
> abc=vwx?
> If that's what you mean, I'd restate it:  "- you must not change entries.
> If code changes force a message change, add a new entry, don't change the
> message in an existing entry."

Aye - we 100% agree. It is just that I am very pessimistic; and expect
that people will do the above edit by accident. And wanted to suggest an
obvious way to the programmer to avoid it which would require less
polution. I've seen this rule go wrong so often on i18n projects I've
worked on.


View raw message