Salutations All,

I'm looking for some best-practice guidance here.

We're currently working on a system (with both a web-based interface
and a rich client interface) that will need to support future
localization/translation. We've got a number of database-driven text
values (for instance, our system allows you to upload an office
document, and then apply a classification to that document for
sorting/navigation purposes) and I'm at a bit of a crossroads as to how
I should handle localization. On the one hand, we don't want multiple
classifications that are really just the same thing but in different
languages (for instance, "Business Documents" and
"Geschäftsdokumente"), but I'm also nervous about storing all this
localized text in the database. The flip side is, however, also true -
new document classifications can be added by the users, and they will
do so using their native language.

So, the question is, what's the best way to handle this? Localize in
the database, or localize in the app only?

Our database backend is SQL Server 2005, if that makes any difference.
Any guidance is most appreciated!

Thanks!