Skip to content

Releases: rorycl/rm2pdf

v.0.1.7 : security update

26 Dec 16:05

Choose a tag to compare

A security update for golang.org/x/image.

v0.1.6 : detect version 3 remarkable files and fail early

22 Feb 22:40

Choose a tag to compare

This release aims to detect reMarkable software version 3 files, which include .rm files in version 6 format, and stop processing early.

This closes issue 11, but unfortunately not by processing the new format.

Progress however has been made on supporting the new .content file format.

0.1.5 : fix for missing bundle metadata, rmapi 0-indexed .rm files

27 Sep 07:06

Choose a tag to compare

This release provides fixes for issue 9, to skip missing bundle metadata files for older reMarkable bundles, and support 0-indexed (rather than uuid-indexed) .rm files for older rmapi zip files. Thanks to qwert2003 for the report and invaluable help.

0.1.4 : support rmapi zip files

24 Sep 14:06

Choose a tag to compare

This release provides support for rmapi zip files.

For example: rm2pdf input.zip output.pdf

0.1.3 : use embedded template

14 Sep 23:46

Choose a tag to compare

In this release an embedded template will be used when a template is not provided when rendering a notebook or annotated pdf with inserted pages.

This saves on from having to specify a template. So instead of

rm2pdf -c custom_pens.yml -t templates/A4.pdf 3b7cbdbc-3487-11ed-9aba-13885c4da644.content /tmp/output.pdf

One can simply do

rm2pdf -c custom_pens.yml 3b7cbdbc-3487-11ed-9aba-13885c4da644.content /tmp/output.pdf

0.1.2 : support custom pen configuration by layer

14 Sep 14:52

Choose a tag to compare

This release supports custom pen configuration by layer.

See config_example.yaml for an example.

0.0.3 : Support inserted pages in annotated pdfs

09 Sep 21:29

Choose a tag to compare

This release provides support for the new "insert page" feature when annotating pdfs.

Error handling is also improved.

0.0.2 : Fix for empty layers

28 Mar 21:36

Choose a tag to compare

A fix to not crash on empty layers as reported in #6.

In investigating this it seems there is a bug on the actual rm layers written on the last page of my reMarkable v1.If only the second layer is written to, the first layer is ignored.