Ah.. I thought he was still having issues with ligature characters. UTF-8 is an encoding, not a charset.
>NCR data is hust plain 7 bits ASCII, and can be fully transmitted in Yes. I know.. That was in my post: "replace those characters (NCRs will be ascii)" Warmest Regards, Phillip B. Holmes http://phillipholmes.com ==================> -----Original Message----- From: Claude Schneegans [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 17, 2006 2:30 PM To: CF-Talk Subject: Re: CFHTTP Charset Question >>The problem he is having is that the source charset is not lining up with the actual data coming across. Nope; he says "When I make the get request specifying the charset as iso-8859-1 everything returns fine", so there is no problem with the feed and the charset it specifies. His only problem is when he tries to convert to another charset using the charset attribute in CFHTTP, this won't work, since the charset in the feed is STILL is-8859-1, but CF will interpret it as UTF-8 which of course won't work. The charset attribute in CFHTTP is not intended for conversion. >>I think his issue is NCR data. NCR data is hust plain 7 bits ASCII, and can be fully transmitted in ISO-8859-1 or whatever UTF. NCR data is just HTML, compatible with any charset based on ASCII. -- _______________________________________ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240823 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
