Just to follow up, here's what I decided to do: 1. Execute a head request for the feed 2. If the head request returns a charset in the response header, store it in a variable. Otherwise, default to UTF-8 as the stored charset. 3. Execute the get request using the charset as identified in #2
After that, I'll have to figure out how I want to insert it into my transformed XML, but I can think of several ways to do that. Anyone see any problems (or better ways) of handling the acquisition of the target file's encryption? Thanks again for everyone's help with this. I learned a lot more than I bargained for. On 5/18/06, Claude Schneegans <[EMAIL PROTECTED]> wrote: > >>There should be another argument called 'encoding'. That would end > lots of confusion between the two. > > I think the confusion lies in the W3C standard first, with META tags like: > > <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"> > > Most charsets are both a charset and an encoding system. UTF is a kind > of exception. > > -- > _______________________________________ > 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:240935 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
