> If I thought you were a programmer, I would suggest that you write a patch
> to the Plucker parser, to allow it to handle Javascript, but I think
> that's probably beyond your current skill level, and I know that it's
> beyond mine.
Let's also not forget that Javascript isn't "parsed" like HTML, it
is "executed". This means someone (i.e. not me =) would have to write a
javascript "engine" for Plucker and then link that into the distiller code
to be run for each page that contains Javascript tags and blocks. Not fun,
and certainly not a really interesting task within the scope of Plucker.
There is, however, a Perl module that purports to do this[1], but
I'm not sure how much current javascript it supports. Lots of javascript
"programmers" (and I use that term VERY loosely) do not know how to write
clean, leak-free javascript.
Personally, I yank Javascript blocks, CSS blocks, and font face
attributes out of the pages BEFORE I parse them with my tools, which makes
them much smaller and faster to manage, and in less than 10 lines of code.
> I also expect that the people on this list who could write such a patch
> aren't interested in doing so, so the chances of your ever plucking that
> page are very low.
Probably a good assumption. I'd stick with the proper HTML pages and
inform the website maintainer of those using Javascript for basic links and
navigation to stick to standards-compliant technologies to deliver content.
Good luck.
[1] http://www.cpan.org/modules/by-module/JavaScript/
d.
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
