Some of the initial data was stored in char, varchar. But the bulk of it (95%) was n type from the beginning. Since then we had updated all the fields to nchar, nvarchar I hope that we don't have to translate everything again. We were supposed to go live in June and delayed to July to take advantage of CFMX Unicode features.
Is there a fix to the problem Thanks Marius ----- Original Message ----- From: "Paul Hastings" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Friday, June 07, 2002 3:53 AM Subject: Re: CFMX and unicode > > the application has all the information translated in Korean and it > display > > perfectly (well with the exception of CFtree). > > you mean in cf5? > > > Tried it under CFMX and the forms display garbage. > > initially all the forms had the following at the top: > > welcome to world of legacy data: cfmx wants/expects ucs-2 encoded > data. your kr data is encoded how? stored in "N" datatype fields? > > > <meta http-equiv="content-type" content="text/html;charset=euc-kr"> > > The above works in CF5 but does not work in CFMX > > cfmx wants to spit out utf-8 encoding. > > > and added the following to each form > > <cfprocessingdirective pageEncoding="euc-kr"> > > this should actually work, provided the data is stored > in something neo likes. how was the data stored? > > > <cfprocessingdirective pageEncoding="ks_c_5601-1987"> > > how was the data stored? > > ______________________________________________________________________ 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/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
