Open KaveeHana opened 3 years ago
regex or css filters are too messy not not user friendly. we need a better way to clean the page before generating the ebook.
Ok forget about the regex replacements. A method to select the html nodes for capture would do just fine. Even though this extension is more convenient because it's a standalone I mostly use grabmybooks because it gives more control over the capture and the captured html code looks a lot cleaner.
you can remove the nodes you don't want using the custom CSS rules setting display to none!important. consider what I've written in the first post of issue #50, for instance
Save-as-ebook is good at capturing everything in the page indiscriminately, which is useful because capturing everything is better than not capturing the needed part of the page. But this also makes it necessary to clean the generated epub of the unnecessary details afterwards.
Adding the ability to apply regular expression replacements on the capture, based on some site rules would significantly if not completely reduce the need to separately clean the epub afterwards.
Also as I mentioned before it would also help editing the epub if the names of the files inside the created epub are human readable.