: Re: How should we go from Stack Exchange Q/A to publishable PDF with the least hassle? Over on another site we're talking about taking some of our content (on a particular theme) and re-packaging
If you only want to convert a handful of pages into PDF, then you can do that in Microsoft Word and you will probably be ok.
If you want to convert a large quantity of webpages into PDFs and wish to preserve their edibility and eliminate unnecessary information, I am going to strongly suggest the following:
Export the webpage with the source information as HTML. Open the saved page in Adobe Dreamweaver (or similar) and make all the changes to the text and page layout in HTML and then save the new content again as HTML. When all final changes have been made, then create the PDF from the HTML in Adobe Acrobat (or similar).
Why this and not Word? Two reasons.
One, I find that Word tends to get mucked up when you've cut and paste from the web. Things tend to flow incorrectly and un-mucking it up tends to be quite frustrating. You experience may vary.
Two, if you wish to be forward thinking and want to eventually create an ePub or a Kindle book or what have you I have found in my experiences that you get better results when you create your e-book from HTML as opposed to MS Word or even PDFs.
If you want to be forward thinking it's better to handle your product once through HTML editing than to handle it twice through Word.
More posts by @Speyer920
: In a situation where the policy position might be implemented in more than one form, your first step should be to lay out the underpinning principles that you recognise. In the example you
: How to publish public domain books? It is known that the copyright permission is not needed for old books (usually 70 years after the author's death), because the copyright has been expired.
Terms of Use Privacy policy Contact About Cancellation policy © selfpublishingguru.com2024 All Rights reserved.