> The original translation was on an English server with the default > installation: Language: English, Code Page CP 1252
and there's your problem. though w/sql server 2k you can actually set collations per db, per table, even per column. if you go more m17n then unicode. if you're only going to do korean & english i guess you can figure out something as is. > So the data that was saved in the database even in nchar (nvarchar) type > fields cannot be properly interpreted by CFMX? well neo's expecting ucs-2 for unicode data ala java & sql server. if you have something else you have a small problem. i guess this is going to be common enough to look at some solutions. > I know that Unicode is the way to go, but I didn't expected to have this > type of problems. i actually had more problems with neo & single locales than w/neo & unicode. after all my years of whining, i actually got a bit too much unicode....resistance IS futile ;-) > Anyway, your chapters on Internationalization in the Advanced CF5 book are thanks. > very good and I recommend it to anybody doing work for multiple locales. Do > you have something similar for CFMX in the works? i think so. ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
