A solution to generate a bookmarked PDF document based on a batch URL is a complete solution with four main points
(1) Detailed description of the solution of the idea,
(2) A XML file describing the URL is proposed, called h2p file.
(3) The tool that generates PDF documents according to H2P file is called H2p-tool, and H2p-tool can also edit h2p file to make his own PDF ebook.
(4) The h2p file is the resource file for the solution, and collecting URLs is a time-consuming and laborious task, so the solution also provides links to download h2p files
H2P is an XML format that I define myself, and I secretly want this format to be accepted, so I've defined DTDs and developed a tool for editing h2p files H2p-tool, and I've provided a lot of h2p files on the Javaei Web site as resources to download. With H2P, it will be easy to make your own PDF ebook.
If you want to make h2p acceptable to all, h2p must continue to develop. Because now H2P application is still very simple and original. The main manifestation is that the resulting PDF is a full representation of the original HTML, which is his strength and weakness.
That's the advantage, because the PDF has the same effect as it does in the browser.
It's a drawback because, since we've generated PDFs, we want to focus on the content of the article in the PDF, rather than having so many pictures and ads on the original page, and hoping that the page content is automatically merged into a PDF.
So, for this shortcoming, I propose two possible prospects.
(1) To develop a specification, the specification requires the site for each blog to provide a dedicated link for h2p (call h2p link bar), according to the link opened blog article is no advertising, then h2p file connection with this h2p link, the resulting PDF without the above shortcomings. This idea may be inconsistent with the profitability of the site, because if you provide h2p links, many people will click on the h2p link, so that the site to avoid ads.
(2) The second possible prospect is that each website provides a webservice programming interface, through which the program accesses each blog post, so that the article is clean articles without advertisements.
These two visions are designed primarily to produce clean PDF documents, and it is clear that it is difficult to achieve both, unless people are very receptive to the idea of h2p, and there is an urgent need for such applications to be vigorously promoted. Think about the popularity of RSS, it is also twists, and ultimately because of its convenient use of the model and be accepted by everyone.
In private, I hope everyone can accept and like h2p.