Yes, I wouldn't have assumed that Asian character sets would be so easy. This is maybe another case for adding yet more "Value" columns which have their own Collation set properly to the appropriate Asian language. It is possible to have multiple collations in a table, but only one collation on the database. You have to modify your queries and procs to explicitly set the collation for those languages because SQL won't do it for you in some cases.

For example:

ALTER TABLE dbo.ObjectGlobalization

ADD [Value_] NVARCHAR(MAX) COLLATE Chinese_PRC_CI_AS

I don't know, but as a developer and DBA I am not one to want to maintain 32 different sets of code for one application and 32 different databases. There should be an easier way and if you have experience in this, can you shed some more light?