I'd endorse this. UTF-8 or UTF-16 (depending on what languages you're expecting
most of your data to be in) will handle anything. If you have Oracle it will
also handle anything, it had NLS support before unicode, but your database must
be set up with a suitable character set. It is completely a no
Thanks for all of the feedback. I'll think on it some more with these
suggestions in mind.
I have one additional question, *sort of* on the topic of Message Resources.
Suppose there is a database table that holds metadata used to configure some
screens, but not all. This table holds the f
Michael Klaene writes:
> 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 Fri, 3 Dec 2004 07:50:31 -0800 (PST), Michael Klaene
<[EMAIL PROTECTED]> wrote:
> 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 t
>
>
> 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
> -Original Message-
> From: Michael Klaene [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 03, 2004 8:51 AM
> To: [EMAIL PROTECTED]
> Subject: i18n and the database...
>
>
>
> Hi.
>
> I'm investigating ways to support multiple languages i
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 m
7 matches
Mail list logo
