Glad you're problem is worked out. However, I think the solution is a ton easier than using that tag or any character sleauthing conversion technique via java.neo, if you're using CFMX.
CF-5 rendered in UTF-7 by default. We had the same issue at my company when upgrading. We did the same thing you did with cfhttp to render the text correctly. We deal in 22 languages and had the highest volume CF site in the world before converting to .NET via C#. When we upgraded to CFMX, we even had to start using DW8 instead of studio because studio saved the file in UTF-7 and had no option available to save in UTF-8. The only thing I don't understand is that if your application is rendering 8859-1 in UTF-8, what could possible be the problem? If your data is stored in a varchar field, CFMX automagically down-encodes the results and you wind up with garblage. However, if the data is coming from an nvarchar or ntext field, the unicode is rendered correctly. Please let me know. --phillip -----Original Message----- From: Claude Schneegans [mailto:[EMAIL PROTECTED] Sent: Friday, November 17, 2006 5:18 PM To: CF-Talk Subject: Re: Convert UTF-8 to ISO-8859-1 under CF5 >>Yep. So, this is the wrong name for the attribute. There should be an >>encoding attribute and a charset attribute. Who cares? As far as Internet is concerned, there is no difference. The only problem will be when (and if) UTF-8 is used to represent something else that Unicode, which is not close to happen. >>Allaire got this wrong and it should be corrected, IMHO. Allaire has been wrong in several issues in their design, but in not this event, ie: Meta tags and HTTP headers, there is nothing they could do. When they have an attribute "charset=", it is just intended to pass a value to the charset attribute used in the HTTP header. What is your point? Should we write: <CFHEADER encoding="UTF-8"> in order to generate a header containing charset="UTF-8" ? This is ridiculous. The W3C got ot wrong, but not Allaire. >>There is no such thing as converting a character set from 8859-1 to UTF-8. You're not slouthing 8859-1 characters to UTF-8, you're rendering the page UTF-8 using content that's charset s 8859-1 charset. This is right, but as far as Internet is concerned, these considerations are purely academic. >>CF 5, by default renders the page UTF-7. That is your problem. UTF-7? CF5? What are you talking about? By default, CF5 sends 8bits characters, whatever the charset you use. If your text is iso-8859-1, then no problem, this is the charset used by default by most browsers. You better specify it in some META tag though. CFMX renders the page UTF-8, THAT's my problem. >>If you're seeing some type of garbling because you're rendering the page in UTF-7, all you have to do is tell the browser (via CF) to render the page UTF-8, just like you would do through your browser options. My feeling is that you didn't follow the thread completely: I have an application in CF5, not able to understand UTF-8, which is CFHTTPing another page from another server under CFMX which renders the content in UTF-8. I have no control on the CFMX server, and It is out of question I convert all my CF5 application to use UTF-8 instead of iso-8859-1. So the solution is CF_CharsetConvert which works pretty well, even with no Java. -- _______________________________________ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:260995 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
