I do not know German, but at this
stage of development perfect translation is not required. What is actually required is
a set of strings that will look like German, or at least will be clearly distinguishable
from English messages and labels.
In practice, I use an online tool, like Babel Fish Translation (http://babelfish.
altavista.com/) or Google Language Tools (http://www.google.com/language_
tools). Here is what I was able to produce:
authentication-failed=Wir k?¶nnten nicht dich beglaubigen. Versuchen
noch einmal oder Register.
login-here=LOGON hier
user-name=Benutzer-Name
password=Kennwort
or-register=Oder Register
log-in=LOGON
This is probably a very rough approximation of a proper German text, but it will
do for now. At a later stage, when preparing the close to completion application for
deployment, we shall send all the message catalogs to real translators, and they will
do everything properly.
Okay, we have German messages ready, but to see them displayed by the
application, we need to learn how to switch the application's locale first.
Switching Locale
Basically, to switch the locale of our web application, all we need to do is to tell
Tapestry which locale we want to see as current.
Pages:
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235