John Gibbs johngibbs

So you want to modify the text of a PDF by hand...

If you, like me, resent every dollar spent on commercial PDF tools, you might want to know how to change the text content of a PDF without having to pay for Adobe Acrobat or another PDF tool. I didn't see an obvious open-source tool that lets you dig into PDF internals, but I did discover a few useful facts about how PDFs are structured that I think may prove useful to others (or myself) in the future. They are recorded here. They are surely not universally applicable --
the PDF standard is truly Byzantine -- but they worked for my case.

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

	// ==UserScript==
	// @name Adalia Fundamentals
	// @namespace https://gist.github.com/adaliabooks/
	// @version 1.9.10
	// @description A package of fixes, new features and changes to improve GoG.com. I fix GoG, so you don't have to!
	// @author adaliabooks
	// @updateURL https://gist.github.com/adaliabooks/bf3cbdbb56db6c107dd8/raw/
	// @downloadURL https://gist.github.com/adaliabooks/bf3cbdbb56db6c107dd8/raw/
	// @include http://www.gog.com/*
	// @include https://www.gog.com/*

John Gibbs johngibbs

So you want to modify the text of a PDF by hand...

Conventional Commit Messages

General rules

Design rules