swinton / pdfify

Generates Octocat-friendly PDFs from Markdown
MIT License
3 stars 1 forks source link

Shrunken PDF #3

Closed hectorsector closed 7 years ago

hectorsector commented 7 years ago

This is continued conversation from #1. There seems to be an issue with the size of the outputted PDF, which appears to be related to wkhtmltopdf.

Version:

$ wkhtmltopdf --version
wkhtmltopdf 0.12.4 (with patched qt)

HTML output:

<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <meta name="generator" content="pandoc">
  <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
  <title></title>
  <style type="text/css">code{white-space: pre;}</style>
  <!--[if lt IE 9]>
    <script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
  <![endif]-->
</head>
<body>
<h1 class="letterhead">
  <svg height="42" width="42" class="octicon octicon-mark-github" viewBox="0 0 16 16" version="1.1" aria-hidden="true">
    <path fill-rule="evenodd" d="M8 0C3.58 0 0 3.58 0 8c0 3.54 2.29 6.53 5.47 7.59.4.07.55-.17.55-.38 0-.19-.01-.82-.01-1.49-2.01.37-2.53-.49-2.69-.94-.09-.23-.48-.94-.82-1.13-.28-.15-.68-.52-.01-.53.63-.01 1.08.58 1.23.82.72 1.21 1.87.87 2.33.66.07-.52.28-.87.51-1.07-1.78-.2-3.64-.89-3.64-3.95 0-.87.31-1.59.82-2.15-.08-.2-.36-1.02.08-2.12 0 0 .67-.21 2.2.82.64-.18 1.32-.27 2-.27.68 0 1.36.09 2 .27 1.53-1.04 2.2-.82 2.2-.82.44 1.1.16 1.92.08 2.12.51.56.82 1.27.82 2.15 0 3.07-1.87 3.75-3.65 3.95.29.25.54.73.54 1.48 0 1.07-.01 1.93-.01 2.2 0 .21.15.46.55.38A8.013 8.013 0 0 0 16 8c0-4.42-3.58-8-8-8z">
    </path>
  </svg>
  <span><em>GitHub</em> Professional Services</span>
</h1>
<h1 id="let-us-introduce-you-to-github-for-insert-customer-name-here">👋 Let us introduce you to <em>GitHub for <code>Insert Customer Name Here</code></em></h1>
<h3 id="our-promise">Our Promise</h3>
<ul>
<li>We'll adjust the <strong>difficulty</strong> as needed, so that both newbies and pros can get the most out of training.</li>
<li>We'll adjust the <strong>time spent</strong> on topics that your learners are comfortable with, or those that need a little extra attention.</li>
<li>We'll allow plenty of <strong>time for Q&amp;A</strong>, so that no questions remain unanswered.</li>
<li>We'll prioritize <strong>hands on keyboard</strong>. No boring lectures, here!</li>
</ul>
<p>Our classes result in:</p>
<ul>
<li>cleaner, safer project histories</li>
<li>quicker development cycles</li>
<li>more frequent ships</li>
<li>self-efficacy</li>
</ul>
<p>Below are high level topics that will be covered in your class. The focus of this content isn't just learning lines to type out of a book: it's to level 🆙 a learner's understanding of Git from the inside out.</p>
<h3 id="intended-audience">Intended Audience</h3>
<p>This class is designed for people who are:</p>
<ul>
<li>Involved in software development</li>
<li>At all levels of version control experience</li>
<li>Comfortable with command line basics</li>
</ul>
<h2 id="getting-started-with-collaboration-the-github-flow">Getting Started with Collaboration &amp; The GitHub Flow</h2>
<p>Using GitHub to the fullest means more than just following a tutorial. It's necessary to know the most common workflow for best results. We cover the existing tools in Git and GitHub in your GitHub Enterprise version as well as best practices for workflows. Already had a GitHub Workflow Consultation? We come armed with the details of your existing situation. Participants come out of this section armed with answer to these questions (and more!):</p>
<ul>
<li>Where does Git start and GitHub end?</li>
<li>What is 'GitHub Flow', and how does it apply to us?</li>
<li>What are some key features of the Github ecosystem?</li>
</ul>
<h2 id="working-locally">Working Locally</h2>
<p>Developers want to use Git in our most comfortable environment. We work through how to use Git and GitHub locally, as well as the complex relationships that exist in branches, remote tracking branches, and multiple remotes. When working locally, the commands to type seem like the bread and butter, but don't be fooled: Git proficiency comes from understanding the <strong>how</strong> and <strong>why</strong>. Hands on experience and critical thinking do more than any cheat sheet ever could. We focus on addressing the following topics and questions:</p>
<ul>
<li>Why do we clone? How?</li>
<li>How can I configure Git locally?</li>
<li>Understanding the staging area and working directory, and what those mean for our daily operations</li>
<li>Interacting with the remote server</li>
<li>Collaboration &amp; Pull Requests</li>
<li>Understanding the nature of the working tree</li>
<li>What are the ways that merging can happen? What are best practices?</li>
<li>How can I view my project's history and changes?</li>
</ul>
<h4 id="new-commands-covered">New commands covered</h4>
<ul>
<li><code>git clone</code></li>
<li><code>git checkout</code></li>
<li><code>git add</code></li>
<li><code>git commit</code></li>
<li><code>git pull</code></li>
<li><code>git push</code></li>
<li><code>git log</code></li>
<li><code>git config</code></li>
<li><code>git status</code></li>
<li><code>git merge</code></li>
</ul>
<h2 id="the-workflow-end-to-end">The Workflow End-to-End</h2>
<p>Hands on experience is good, but scaffolded and personalized hands on review is better. We work through the same key steps and principles of the GitHub Flow while introducing more complex structures like Forking and merge conflicts. We focus on addressing the following topics and questions:</p>
<ul>
<li>What is a Forking Workflow?</li>
<li>What happens if a file has been changed on the same line at the same time by different developers?</li>
<li>How do repositories interact with multiple remotes?</li>
<li>How big should commits be?</li>
</ul>
<h4 id="new-commands-covered-1">New commands covered</h4>
<ul>
<li><code>git remote</code></li>
<li><code>git add -p</code></li>
</ul>
<h2 id="fixing-common-issues-with-git-rewriting-history">Fixing Common Issues with Git &amp; Rewriting history</h2>
<p>What good is version control if you can't go back and look through previous versions? Now that developers know how to create with Git, it's important to learn how to get out of history with the same level of expertise. Git is flexible and complex, and hands on practice paired with theoretical thinking and examples truly arm developers to fix any problems thrown at them. We focus on addressing the following topics and questions:</p>
<ul>
<li>What are the different ways to create repositories?</li>
<li>How can we safely undo changes?</li>
<li>What are the dangers of changing history?</li>
<li>How does git work internally, and why does that matter when changing history?</li>
</ul>
<h4 id="new-commands-covered-2">New commands covered</h4>
<ul>
<li><code>git init</code></li>
<li><code>git revert</code></li>
<li><code>git bisect</code></li>
<li><code>git reset</code></li>
<li><code>git rebase</code></li>
<li><code>git reflog</code></li>
</ul>
<h2 id="questions-and-customizations">Questions and Customizations</h2>
<p>We know that every development team is different, and uses Git differently. We build in time to focus on your questions and topics to ensure developers leave the class feeling empowered and excited to start with GitHub. We focus on addressing the following topics and questions:</p>
<ul>
<li>Using what you have learned in your day-to-day work</li>
<li>Discussing workflows and best practices</li>
<li>Any additional topics and questions</li>
</ul>
</body>
</html>
swinton commented 7 years ago

@hectorsector I think this is related to https://github.com/wkhtmltopdf/wkhtmltopdf/issues/3241

Could you downgrade wkhtmltopdf to version 0.12.3? That should rectify the issue 🙏

hectorsector commented 7 years ago

🎉 that seems to have done it, @swinton! Now off to installing required fonts!