Hello all.

I've globalized an asp.net application and so far we've localized into
en-GB, de and fr. We have several more European languages to go as
well as Chinese, simplified and traditional. I'm using the Enterprise
Localization Toolkit introduced by MS which is working real well.
Culture-specific satellite resource dll's get created and used in
separate directories. With Chinese, I face a dilema. Our content is
going to be targeted for Simplified or Traditional. Each of these is
used in several countries. I understand that people in Singapore
might prefer either one. Rather than name my cultures zh-CN, zh-TW,
zh-HK and so on, I am figuring to go with

zh-TR - Chinese traditional
zh-SI - Chinese simplified

Our base page code will determine from the culture specifier in the
request which to present. For the PRC user, zh-CN will map to zh-SI
and so on.

We are really using the secondary code as a language variant rather
than a country code. en-GB usage for Hong Kong is the other example.
This is a departure from Microsoft's recommendations but seems more
akin to reality.

Will this create problems for me later or have others made this same
choice?

Thanks!

Hi Murphy,,

Thanks for your post. As I understand, you have a set of culture names of
your own and will convert between them with the default ones. Based on my
experience, I did not find potetial problems. In addition, I suggest that
you can put the culture mapping table into a xml file which can be loaded
and extended easily.

Hope this helps.

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.