Skip to content

Instantly share code, notes, and snippets.

@gettalong
gettalong / links.rb
Created August 1, 2021 07:17
PDF link modifier script
@gettalong
gettalong / knuth.pdf
Last active August 26, 2020 18:52
Answer for superuser question 1580595
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@gettalong
gettalong / README.md
Last active July 16, 2020 22:08
PDF AcroForm with radio buttons not working

I'm currently implementing support for AcroForm radio button fields. The resulting PDF objects look fine to me but the radio buttons won't work in Adobe Reader and Evince.

@gettalong
gettalong / README.md
Last active June 10, 2019 16:07
PDFs not opening in Adobe Acrobat Reader but working fine in all other tested PDF viewers

Edit: I think I found the problem: Acrobat needs the Catalog dictionary to be an indirect reference that is not in an object streams.

  • good3.pdf: PDF encrypted with (A)RC4 using V=4, PDF version 1.5, cross-reference and object streams, Catalog dictionary not in the object stream.

@gettalong
gettalong / bm.rb
Created September 15, 2018 07:19
Transducer vs Ruby vs Lazy Ruby performance
require 'benchmark-driver'
setup_code = <<EOF
require 'ramda'
def transduce(transformation, reducing_fn, initial, input)
input.reduce(initial, &transformation.call(reducing_fn))
end
PUSHES = -> list, item { list.push(item) }
@gettalong
gettalong / pdfkit.js
Created January 28, 2018 08:58
pdfkit.js
const readline = require('readline');
const fs = require('fs');
var PDFDocument = require('pdfkit');
var top_margin = 72 + 0.5 * 72;
var bottom_margin = 842 - 72 - 0.5 * 72;
var margins = {top: 0, bottom: 0, left: 72, right: 72};
var pdf = new PDFDocument({size: 'A4', autoFirstPage: false, margins: margins});
var y = 842;
var font = process.argv[4] || 'Times-Roman';
@gettalong
gettalong / README.md
Last active March 10, 2020 02:17
HexaPDF examples

HexaPDF - A Versatile PDF Creation and Manipulation Library For Ruby

HexaPDF is a pure Ruby library with an accompanying application for working with PDF files. In short, it allows

  • creating new PDF files,
  • manipulating existing PDF files,
  • merging multiple PDF files into one,
  • extracting meta information, text, images and files from PDF files,
  • securing PDF files by encrypting them and
  • optimizing PDF files for smaller file size or other criteria.
@gettalong
gettalong / README.md
Last active January 22, 2020 02:13
Performance comparison of line wrapping between Ruby Prawn and HexaPDF

This is a follow-up benchmark to the one comparing the basic text output performance between Hexapdf, Ruby Prawn and other libraries.

This time the performance of line wrapping and simple general layouting is tested. Again, the Project Gutenberg text of Homer's Odyssey is used for this purposes. The used Ruby scripts are attached below.

The text of the Odyssey is arranged on pages of the dimension 400x1000 and 200x1000, and once with the standard PDF Type1 font Times-Roman and once with the TrueType font Times New Roman. In the case of pages of size 400x1000 no line wrapping needs to be done because each line is shorter than 400 points. In the other case (200x1000) lines need to be actually wrapped and the resulting PDF has roughly twice the number of pages.

Results:

|-------------------------------------------------------------------|
@gettalong
gettalong / README.md
Created May 10, 2017 18:29
Simple Text Metrics
@gettalong
gettalong / README.md
Last active October 29, 2017 16:41
Unicode NFC/NFD differences in PDF

When creating a PDF it depends on the application writing the PDF whether decomposed Unicode characters ("combining sequences") are correctly positioned.

The basic way (that most applications use) is to just treat the separate Unicode characters as if they were normal characters. This leads to incorrectly positioned combining marks as the glyph width of the combining mark is not suitable for all characters it can be combined with.

A better way would be to perform Unicode normalization (see http://unicode.org/reports/tr15/), more specifically Normalization Form C (NFC) which composes characters if possible (in contrast to NFD which decomposes them). However, this may lead to changes in the meaning of some characters (see the link and scroll down to figure 3).

The best way would be to use fonts that contain all needed information to correctly position combining characters. Many modern OpenType fonts include such information in internal structures (like the GPOS table). Note that the application writing the P