>John Pullam wrote: >> You are correct. When I looked at the 2 pages in Firefox there was a >> difference in the character encoding. Pardon my ignorance, but how do I fix >> that? The meta tags on the pages all say <meta http-equiv="Content-Type" >> content="text/html; charset=iso-8859-1"> > >cf doesn't care what the html meta headers are, it will output to it's default >encoding (usually utf-8) unless told to do otherwise. use cfprocessingdirecive >to change the encoding page-by-page or you can swap the whole server by >changing >the defaultCharset value in cf_root/lib/neo-runtime.xml file: > ><var name='defaultCharset'><string>UTF-8</string></var> > >to a valid charset and re-starting the cf server service. > >that said, i'm fairly sure paypal allows you to control the encoding you use >to >talk to it, check out the wrongly named (to me) "Language Encoding" in your >paypal profile. > >you should probably standardize on just the one encoding & of course that >should >be unicode.
I am just one user of an ISP who runs the CF server so I am not able to alter its parameters. Therefore I opted for the approach of including the cfprocessingdirective on my page. I added the following line to the beginning of the page: <cfprocessingdirective pageEncoding = "iso-8859-1" /> Unfortunately it had no effect. When I looked at the actual encoding on Firefox, it still shows as UTF-8. Is there something else that I need to do to make this directive work? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:318839 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
