Edward Rayl wrote:
That explains my problem since I use <br><a> instead. XSLT scares me, I'll just wait for your fix :)Taras wrote:Also I find that plucker has issues with plukering <a name=> tags. It seems to scroll to the wrong part of the page when <a href="#somename"> is used.
I ran into this problem. The viewer scans backwards from the <a name=> tag to the first <p> tag PRIOR to it. You can modify this behavior by modifying your website to include a <p><a> combination, wait for my enhancement request to fix this, or use XSLT to fix the problem.
Well, I was hoping so, however jpluck can't seem to be able to crawl this website. I suspect the problem is that the website is on an embedded web server that likes to be lazy and omits most of the http headers. If I don't find another solution to the crawling problem, I'll have to do some debugging on jpluck(never used a jave debugger before though).
With regard to speed and memory problems, you might want to take a look at JPluck at http://jpluck.sourceforge.net and see if this product works better for you. It can also do XSLT transforms, but this is not documented yet.
*JPluck author please help help :)*
Thanks,
Taras
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
