|
I tried posting another version of this earlier but I must have clicked preview instead of post....
So I've been thinking about a couple outstanding issues and have an idea on how to solve them, but it may not fit how most folks are using the plugin and wanted to get a bit of feedback.
Right now I'm passing the current document url to web2lrf. This means all of the proxy settings and ad blocking software is bypassed. What I could do is save the current document to a temporary file and run html2lrf on it. I could try to grab any images to be displayed and update the html to point to the local copy.
This would work well for me, since I usually switch to a printable, single page version of the document if it's available and generate the ebook from there. This won't work so well if folks are generally creating ebooks from multipage sites.
So it's a trade off, better control over the content vs spaning multiple pages. It thought about spidering the page from inside the plugin, but that may be more work than I have time to do right now.
Thoughts?
|