After my recent upgrade to the latest version, when I run pdf2htmlEX with split-pages 1 option, apart from the page files, an html file gets generated, with css being embedded in it. Before my upgrade, only page files, a css file and an outline file was generated. Is it possible to retain this behaviour?
The reason I am asking this is because we have built a tool on top of pdf2htmlEX and we use the css file generated as an input to another part of our system. Please let us know if this is possible. Thanks.
Ok, so this issue affects many people. It's just been mentioned in #125 and I've opened #141 for a possible solution.
Sorry about the inconvenience, the reason I made this change is that actually the original design was ugly, there were many people asking about how to combine the components together, and I did think that this should be a master HTML file.
For now, here are a few options:
And please except about 1-2 weeks before I will have time for this issue. Thanks.
Thanks, will wait for your resolution.
+1 on this.
@coolwanglu : removing everything in manifest whilst keeping $css is working fine for now, though we also had to keep @base.css and @fancy.css in manifest . Thanks!
@anurag29 base.css and fancy.css can be found in <data-dir> (check pdf2htmlEX -v)
Unfortunately, even when I remove everything in the manifest file (except for $css), this still results in a master html file with just the CSS, but wrapped with style tags. Is there something I am missing to get it to output just a css file, instead of an html file with style tags?
@akwok : "pdf2htmlEX 'path/to/pdf' --split-pages 1 base.css" this will rename the master html file to base.css and you are good to go!
@akwok currently there is no way to remove the tags, you might want to do some post processing.
Sorry for the inconvenience.
A new set of options: --embed and --embed-*** have been implemented. You can now specify whether to embed each specific type of element.
Please have a try.