Hi. 

I'm investigating ways to support multiple languages in my app, without using 
the typical ResourceBundle/MessageResources approach. I was thinking that I 
would like to use a database instead. It seems to me that a large application 
trying to support multiple languages with this approach might become a real 
maintenance issue. 

What I'm interested in is three things: 

1.)Any opinions on whether this does in fact create maintenance issues (I've 
yet to write a large, i18n app). And what are the ways to mitigate some of 
these issues.

2.)Is anyone using a database-driven approach to this, storing application 
labels, etc. in tables and retrieving them. Possibly, by reimplementing 
versions of ResourceBundle/MessageResources to go against tables. You'd still 
have to update entries manually but I kind of like the idea of putting this 
info in the database.

3.)I know that some databases, Oracle, and I hear the newest version of MySQL 
support UTF-8. I've no experience in this area. Does anyone have experience 
with storing text in UTF-8 in the database? This *seems* like it could be an 
ideal approach, eliminating alot of on-going work. Obviously, the app would be 
less portable.

If anyone has suggestions/comments on any of the above, I've love to hear them.

Thanks in advance, 
Mike

 

 


                
---------------------------------
Do you Yahoo!?
 Yahoo! Mail - 250MB free storage. Do more. Manage less.

Reply via email to