Yeah, that's what I was thinking too. I know that the original feed I referenced did not return a content-type response header so it will be no help. And even using getEncoding()...how would this work? I'd have to get the content, get the encoding and then get the content again (this time specifying the "proper" charset). Is that right or have my brain cells just withered to the point of nothing at this point?
Also, I thought I could only use getEncoding() on the form and URL scopes... On 5/17/06, Claude Schneegans <[EMAIL PROTECTED]> wrote: > >>getEncoding() > > This will "Retrieves the Charset as guessed from the underlying > InputStream". > But if the charset is not specified in the response header and if CF > does not interpret characters correctly, > it is probabilly that CF "guesses wrong", so this won't really help. > > The only way I can see would be to get the page first, in whatever > charset, decode the line > <?xml version="1.0" encoding="iso-8859-1" ?> > and repeat the HTTP request specifying the right charset. > > -- > _______________________________________ > 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:240803 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
