RE: [syndication] HTML Encoding BooHoo...

[dave.cantrell@gunter.af.mil]

>It does that because that's what it's supposed to do; XML processors
>must resolve entities automagically. If they want "<XML>" to be
>rendered by the final browser, it should be encoded in the RSS feed
>as:
>
>  &amp;lt;XML&amp;gt;
>so that it will come out of the XML parser as:
>  &lt;XML&gt;
>which will be rendered by the HTML parser as:
>  <XML>


Maybe I'm missing something here, but...

Any reason why you can't scan the feed as plain text before passing it to
the perl module, and replace all instances of &lt;XML&gt; with
&amp;lt;XML&gt;&amp; etc? Variations can be done ad nauseum to get the
effect you need.

Seems everything is working for you except this one problem -- I'd focus on
working around it before creating my own parser to handle HTML in the RSS
feed. Then again, I don't really like the idea of HTML in the feed to begin
with...

Ref:  http://c2.com/cgi/wiki?DoTheSimplestThingThatCouldPossiblyWork

;)

________________________________________________________
SSgt Dave Cantrell, USAF
Web Developer, Logistics Information Systems
[DSN] 596.6277  [COM] 334.416.6277
dave.cantrell@gunter.af.mil
https://web2.ssg.gunter.af.mil/IL  (.mil/.gov only)
--------------------------------------------------------
 We have the enemy surrounded. We are dug in and
 have overwhelming numbers. But enemy airpower is
 mauling us badly. We will have to withdraw.
             -- A Japanese infantry commander's
                situation report to HQ
                Burma, WWII
--------------------------------------------------------
 This e-mail does not constitute endorsement of any 
 product by the U.S. Air Force, nor can it be used to
 obligate the U.S. Air Force in any legal, financial, 
 or contractual arrangement.