[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

thanks Julian and the others!

changing the channel description field within Manila did it. 

But Julian, you are right ... shouldn't Manila encode the "& "? And 
what about the validator? Why is the code accepted as valid if 
there ARE unencoded ampersands? 

Anyway, thanks everbody for taking the time to give me a hint.  

Best regards

Sebastian








--- In syndication@y..., Julian Bond <julian_bond@v...> wrote:
> In article <000501c172fc$255161a0$0b07010a@l...>, James 
Lindën
> <jlinden@a...> writes
> >Your browser's XML parser is simply noting that you have 
unencoded
> >ampersands. Technically, any HTML/ish/ entities should be 
encoded, so an
> >ampersand would be "&amp;" instead of "&" -- without quotes 
of course.
> >
> 
> >> http://cognitivearchitects.weblogs.com/xml/rss.xml
> 
> I wonder how it got there. Manila automatically encodes "&" in 
the text,
> doesn't it? I'd be surprised if he had to enter &amp; manually.
> 
> But then this is in the <channel><description> taken from the 
> 
http://cognitivearchitects.weblogs.com/admin/sitePrefs/default$s
yndication 
> page. Maybe that's not getting encoded.
> 
> -- 
> Julian Bond    email: julian_bond@v...
> CV/Resume:         http://www.voidstar.com/cv/
> WebLog:               http://www.voidstar.com/
> M: +44 (0)77 5907 2173  T: +44 (0)192 0412 433
> ICQ:33679568 tag:So many words, so little time