Database Localization.
Posted in 2000
I'm embarking on a journey into the unknown. A client of mine has a software system that interfaces with various database vendors. The "configuation" data that exists in the database for the product is in english. The customer would like to "localize" their database for multiple language support. Their are several approaches that I can think of to resolve this issue ranging from modifying the logical model, to actually packaging the software so that a customer selects a language to use, and based on that selection the appropriate configuration data is loaded. Is there any precedent here to use as a guideline? Any gotcha's, pros-cons?(I'm familiar with the way Sybase does this, but have never installed any other language but english on Oracle) Thanks in advance