Re: how to get unescaped $body?

On Mon, 25 Jul 2005, martin f krafft wrote:
>
> To do this, the EntryBase class would need to be extended to store data 
> and data_unescaped. I am not sure whether this is a sensible way to do 
> it as it seems even more like a hack. Please advise in which direction I 
> should be looking.

Adding it to the EntryBase class is a good idea.  I can toss something in 
right now and build a nightly tar thing for people to test.  More on plans 
below....


> I would nevertheless add body_unescaped and keep body unchanged so as to 
> not break everyone else's setup.

Hrmmm...  I'm thinking it's better to have body and body_escaped and the 
two should be consistent in terms of the format of the data they hold 
(i.e. body is always unescaped and body_escaped is always escaped 
regardless of what the content-type is).  That would be a 
backwards-incompatible change and people with feeds will have to adjust 
their feeds.

Otherwise what we'd have is body which changes between escaped and 
unescaped depending on whether the content type is xml or not and 
body_unescaped which is always unescaped.  People will continue to be 
confused about why body changes.  And it's a hack which should go away.

Also, there's a title plugin which escapes the title (good for Google 
links) and a date plugin which builds the date variables needed for RSS 
2.0 and Atom.  I'm thinking of merging all those into PyBlosxom as well. 
Then it's possible to have Atom and RSS 2.0 flavours which aren't possible 
without helping plugins now.

Anyone else have any thoughts on this?

/will


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click