> I guess the first way with EVERYTHING in a message resource
> is the only way to go? Just curious what the best way and
> any pit falls for supporting internationalization even with
> all the built in locale stuff already in the framework?
That's basically the way my company is doing things.
Everything is in a resource file, including image file
names that need to change based on the locale.
Stuff like James Mitchell's (I hope I remembered that
right) DBMessageResources implementation helps a little bit,
but this is still a major issue as far as maintaining the
resources goes.
The obvious alternative is to use locale specific JSPs,
but that introduces even more issues (thinking of doing
a major look-and-feel change? Oh boy...).
-TPP
-----------------------------------------
This email may contain confidential and privileged material for the sole use of the
intended recipient(s). Any review, use, retention, distribution or disclosure by
others is strictly prohibited. If you are not the intended recipient (or authorized to
receive for the recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data corruption, interception,
tampering, unauthorized amendment and viruses. We only send and receive emails on the
basis that we are not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
