On Thu, Aug 19, 2010 at 11:30 AM, Mack <[email protected]> wrote: > > On Thu, Aug 19, 2010 at 3:40 PM, Rick Root <[email protected]> wrote: >> A fine idea... I already had a cfcontent in there so I added the charset >> >> <cfcontent reset="Yes" type="text/plain; charset=utf-8"> >> >> (also tried application/json, which is apparently the proper mime type >> for json return values) >> >> didn't make a difference. > > A few things to check: > - does the CFC have <cfprocessingdirective pageEncoding="utf-8"/> ? > - does the cfm generated page have a charset defined either in a > header or a meta tag ?
The template had a meta tag with the content type set to iso-8859-1 ... I changed it to utf-8, and also added the cfprocessingdirective, to no avail. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:336419 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
