HexaPDF VS Puppet

An example for a very simple setup is the cmdparse gem documentation. It only has a few additional documentation files that accompany the main API documentation. The other end of the spectrum is the documentation for HexaPDF which encompasses many additional documentation files besides the API documentation and deeply integrates the API docs into the whole documentation website.

HexaPDF is a Ruby OSS library with a commercial version available and profitable.

So I'm collecting feature ideas for that table implementation at https://github.com/gettalong/hexapdf/discussions/231.

Hi there! I'm the author of HexaPDF.

git clone https://github.com/gettalong/hexapdf.git

You can use this HexaPDF script to do this:

I have just released my new gem hexapdf-extras which provides additional functionality on top of the HexaPDF library.

You can use HexaPDF together with a small script to do this (see the third line on how to use the script):

TrueType subsetting mainly consists of generating the necessary glyph and various index tables, and copying over all the other necessary tables which don't need to be adjusted. See https://github.com/gettalong/hexapdf/blob/master/lib/hexapdf/font/true_type/subsetter.rb for what is needed to subset.

for all my PDF processing needs, courtesy of HexaPDF,

The Puppet 8 compatibility guide detailed the major changes we had to be aware of and we found it invaluable the effort. It's probably worth bookmarking that page until you're done with the upgrade.

I will happily direct your attention here: https://github.com/puppetlabs/puppet

We started by decoupling Puppet from Facter as much as we could, introducing the possibility of having multiple Facter backends. While Puppet would use the default Facter implementation when running on its own, external users would be able to define and pass their own Facter implementation when initializing Puppet, similar to how puppetserver configures Puppet to use its JRuby-compliant HTTP client.