>The meta tags on the pages all say <meta http-equiv="Content-Type"
>content="text/html; charset=iso-8859-1">
>
>If your whole application is designed in ISO-8859-1, you must inform CF,
>at least CFMX, because
>CFMX automatically generates headers that you don't see and that declare
>the content to be UTF-8.
>
>I have some applications in ISO-8859 that for some reason must be
>compatible with CF 5 AND CFMX,
>and this is what I'm using in Application.cfm:
><CFSET request.CFversionDetail =
>listGetAt(server.coldfusion.productVersion, 1)>
><CFIF request.CFversionDetail GT 5>
> <CFSET request.CFversion = "MX">
> <cfcontent type="text/html; charset=ISO-8859-1" RESET="no">
> <cfset setEncoding("url","ISO-8859-1")>
> <cfset setEncoding("form","ISO-8859-1")>
><CFELSE>
> <CFSET request.CFversion = "5">
></CFIF>
Things are working correctly now.
For the record, while PayPal did in fact offer the ability to specify encoding,
it did nothing and the PayPal folks blamed CF (incorrectly IMHO).
I prefaced the page that contains the PayPal form with this:
<cfcontent type="text/html; charset=ISO-8859-1" RESET="no">
(in place of the previous directive) and it is now fine.
Thanx to all for the ideas and help. John.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;207172674;29440083;f
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:318902
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
