You can't generally use an embedded font to add new content (because it usually misses parts in the font data structure; even if usable it might be missing characters).
Viewers work around this by loading the same font from the system paths.
With HexaPDF you need to specify the font yourself.

Yes!

But did you know that you can even parse arbitrary strings? 😆

Example: github.com/gettalong/he... (used for interleaving and handling file names and options).

Maybe bind ALT-C to a command that sends CTRL-C? Or do something like this: unix.stackexchange.com/questions/78...

* KDE lets you configure which short-cut switches between applications (ALT-Tab) and which between their windows (Alt-`).
* The built-in KDE krunner application is sufficient as launcher for my needs.
* Clipboard history just works in KDE.
* Vim GUI -> gvim

If you are using KDE, you should be able to just configure this system-wide for all KDE based apps.

Or just use BreakVer www.taoensso.com/break-versio... and break things like before 😁

Thanks for the great meetup! And thanks to @hansschnedlitz.com for organizing it and doing the cool Ruby quiz!

And now the code is available at github.com/gettalong/ve...

It is not yet finished and not really polished etc. but already in a good state.

This will be the basis for still more easily creating PDF documents with HexaPDF 😀

Worked now! And just released the new version - see hexapdf.gettalong.org/documentatio...

Array#[]=(e.g. ary[-10, 10] = EMPTY_ARRAY) won't create an additional array but is slower then Array#pop, so I'm staying with the latter.

Full benchmark info here gist.github.com/gettalong/b8...

Ah, I forgot up that - thank you! You can further optimize it by using a constant empty array and doing `array[from, size] = EMPTY_ARRAY`.

I did a benchmark comparing pop, slice! and your method using benchmark-driver. Interestingly pop was faster even though it creates arrays.

Can also recommend weasyprint if you need HTML/CSS -> PDF.

If you want more quality and better conversion, a commercial solution based on PrincePDF is available via www.europdf.eu

And a heads up from me: There will be a markup-to-PDF pipeline for HexaPDF in the near future :-)

I use unary + for normal UTF-8 encoded strings and "literal".b for binary ones.

Yes, I also think so. When I wanted to formulate the versioning scheme for HexaPDF, I came across BreakVer 🙂