HPCE/gitea-pages
0
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Activity

content updates

Browse Source
This commit is contained in:
Tom Johnson
2015-04-21 11:47:52 -07:00
parent e7fce15f70
commit 149f9b2f6d
51 changed files with 2028 additions and 32636 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
pages/publishing/create_pdf.md
View File

@ -13,6 +13,8 @@ remaining tasks:
- handle page 0 links -- which indicate that there is no cross reference. maybe add note in instructions.
{% endcomment %}
{{warning}} The PDF creation process has some bugs and is still being worked out... {{end}}
This process for creating a PDF relies on Prince to transform the HTML content into PDF. Prince costs about $500 per license.
1. Download and install [Prince](http://www.princexml.com/).
@ -23,12 +25,16 @@ This process for creating a PDF relies on Prince to transform the HTML content i
{{note}} Although you're creating a PDF, you must still build a web target before running Prince. Prince will pull from the HTML files and from the file-list for the TOC.{{end}}
3. In the css folder, open the print-header-fe.css file. Change the filename to your audience. Customize what appears in each of the page margins.
3. In the css folder, open the print-header-writer.css and print-header-designer.css files. Change the filenames to your audiences. Customize what appears in each of the page margins.
4. In the default_print.html file in the layout folder, customize the conditional logic to match your audience with the stylesheets you created in the previous step.
5. In the _data folder, open sidebar.yml and add `print: true` for each page that you want to appear in the print version. (The pages in the topnav aren't pushed to PDF, so if you need some of the pages there, add them to the sidebar and add a `web: false` property to each of them (in addition to a `print: true` property).)
6. In the project's root directory, the logic in the prince-file-list.txt will pull all files from the sidebar.yml file to be included in the PDF. You can adjust any of the logic there as needed, but you shouldn't need to do anything to the file.
5. In the root directory, rename the pdf_fe.sh file and customize its contents to point to the right folders on your computer (the configuration file and the output destination).
6. In the root directory, open the pdf_writer.sh file and customize the directory paths. They should point to where this project builds, so the script can find the processed prince-file-list file and so it knows where to build the output. This .sh file allows you to run the PDF build.
7. Browse to the directory containing pdf_writer.sh file and type `. pdf_writer.sh`.
5. In the root directory, rename the build_writer_pdf.sh file and customize its contents to point to the right paths on your computer.
5. In the root directory, rename the build_writer_prince.sh file and customize the input and output directories. The input should point to where this project builds, so the script can find the processed prince-file-list.txt file and so it knows where to build the output.
7. In iTerm, first run `. build_writer_pdf.sh` to get the pdf version of the content ready.
8. Now run `. build_writer_prince.sh` to generate the PDF from this version.
8. Check for links to non-existent topics in the PDF by looking for "page 0".
9. For those broken links, conditionalize the content to whether site.print == true or not.
10. Stop the server that has the build_writer_pdf preview.
{{note}} Ideally, I wanted to create a script that launched the server, then built prince, and then stopped the server, but I haven't figured that out yet. You have to detach the server, and once you detach it, the only way to kill it is by referencing a dynamically generated PID. {{end}}