On 10/18/06, Thomas Lockney <[EMAIL PROTECTED]> wrote:
> If you have to go the hard route, XSLT can be both a godsend and a
> curse.
No thanks, don't need more problems than I already have. ;~)
Not that it hasn't been massively oversold, but XSLT actually isn't a
bad tool within its original problem domain: basic transformation of
predictable XML content. If your apps all produced valid XHTML, you
could probably just toss an extremely simple XSLT filter on top which
extracted the body content you were interested in and wrapped it in
your standard header and footer.
Presumably, though, the backend apps aren't going to exclusively
produce well-formed content. In that case, I'd probably try
post-processing using mod_ruby and Hpricot (or your choice of HTML
parsing tools). (_why has an example of writing a mod_ruby output
filter on redhanded[1] that might be useful as a starting point.)
Regardless, I think some sort of scraping/extraction followed by
generation of entirely new HTML output is going to be the way to go.
-Lennon
[1] http://redhanded.hobix.com/inspect/inAndOutFiltersForHackedMod_ruby.html
_______________________________________________
PDXRuby mailing list
[email protected]
IRC: #pdx.rb on irc.freenode.net
http://lists.pdxruby.org/mailman/listinfo/pdxruby
