Hello Rodrigo,
On Sep 11, 2007, at 18:08 , Rodrigo Madera wrote:
Thanks guys, but I still think that's not enough.
I believe you also agree.
I agree, it's not enough, and to be honest I would love to have the
time to write a book. :) Tom's suggestion about the white board
pattern actually is a very valuable one, btw!
How would you guys recommend implementing i18n support for an
application
that is modularized? Create a service that translates? Like
MyAppInternationalization, with
methods such as getMessage(). Or do you have a better approach?
There are two questions regarding modularization that come to mind:
1. Do individual modules have new strings that need translation, or
is there only one module that contains all these strings?
2. Do you want to be able to plug in new languages or is the set of
languages fixed?
If you look at the OSGi specification, they use fragment bundles to
add translations to modules that need translating. In general, that
would be my advice.
On the other hand, I've used a service in the past too (either one
service, or multiple ones). A third option is to use a listener that
listens to bundles and inspects their manifest to check if they have
specific properties (something indicating this bundle contains
property files with translations).
Also, where can I find more examples?
I'm sure you already googled, there are quite a few articles and
snippets of documentation around. Are you looking for anything specific?
Greetings, Marcel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
