[wp-hackers] XSLT: Sample implementation

Scott johnson fuzzygroup at gmail.com
Fri Jan 27 23:17:23 GMT 2006

Can I make what may be a clue free comment?  *Response from the crowd:
Sure Scott!  Go be dumb*.

Its strikes me that there's an easy model for how to do the css / xslt
for Feeds from Wordpress: FeedBurner.  Bear in mind that they're a
smart, well funded company that likely has knocked over all the issues
wrt browser compatibility, etc.  Why doesn't someone (and oh crap I
think I just volunteered) look at how FeedBurner does it and then set
up the stubs for that for WordPress.  Clearly we can't copy their
templates but we could, for example, duplicate their approach and then
let one of the (very talented) WordPress CSS folk go with it from



On 1/27/06, Danny Ayers <danny.ayers at gmail.com> wrote:
> On 1/27/06, Phil Ringnalda <philringnalda at gmail.com> wrote:
> > On 1/27/06, David House <dmhouse at gmail.com> wrote:
> > > Really, browsers should recognise
> > > application/atom+xml as something they can parse as XML and do so.
> Indeed.
> > It will also ignore your
> > styling
> Phil, sorry, I haven't had chance to look back at the specs yet - do
> you happen to know offhand how the behaviour is determined for user
> agents when hitting a stylesheet decl? What I can't see yet is how,
> say, an Atom aggregator /should/ apply the hatom2atom.xsl when it
> encounters HTML but /not/ the atom2html.xsl  when it hits an Atom feed
> containing the decl.
> Cheers,
> Danny.
> --
> http://dannyayers.com
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list