rmrl VS pandoc

Cool project! Note that if you want to support the Remarkable scribbles, there's a Python project that does that:

https://github.com/rschroll/rmrl

If you need a high detail at the cost of cosmetics (e.g. pencil texture), rmrl is a pretty good renderer: https://github.com/rschroll/rmrl

100% and yet it's still worth it. I write this as a programmer meaning that, ironically enough, my distraction is when I pick the reMarkable to start reading or sketching but despite the minimalist setup still get distracted. Not by social network notifications or the possibility of a web search but rather here for example to suggest you https://github.com/rschroll/rmrl for your PDF and if its too limited (it always is) to consider what prototypes I could build that challenge the very way I read and write. I believe it's worst for researchers because the process itself must be described in order to publish a result. One must step back and describe the experiment so that it can be both challenged and reproduced. Consequently there is always on the back of the mind a simple and justified question "Is this the right way to do that?". I believe it is quite taxing but it still worth because, and that's just my view, thinking itself relies extensively on tools. We like to imagine that it's a pure process of the mind but for any complex enough thought, we need tools. We run simulations, we sketch diagram, we organize a bibliography which represents the thoughts and experiments of others, etc. This is literally unmanageable without tools regardless of ones "intelligence". This in turns mean that the better the tool, at least in regard to the final goal, the further one can go.

Then use https://github.com/rschroll/rmrl to convert the data files you get from the previous point to pdf.

I love this tool: https://github.com/rschroll/rmrl

Reading/parsing .rm files has been already implemented by these 2 Python libraries: * https://github.com/bsdz/remarkable-layers (not maintained any longer) * https://github.com/rschroll/rmrl (looks up-to-date)

This would also be less of an issue if you ran your own infrastructure (see rmfakecloud, or use something like Syncthing or Nextcloud together with rmrl for file conversion).

This has been a gripe of mine for a while. The problem is that reMarkable isn't implementing the PDF standard correctly. Their highlights are just visual overlays but not Annotation objects. I have submitted a pull request to the RMRL python library to fix this, but the author has not been responsive. I also submitted a support request referencing the specific standard, but I'm not holding my breath. In the mean time you can always try using my version of RMRL, but it requires use of the command line and a working python install.

One way to manage the issue, would be to look into rmlr, install python and pip via Entware/Toltec, and try to have rmlr running on the RM if all the dependencies can be found for the ARM architecture.

My main authoring tool is then Emacs Markdown Mode (https://jblevins.org/projects/markdown-mode/). For data entry, it comes with some bells and whistles similar to org-mode, like C-c C-l for inserting links etc.

I seldom export my notes for external usage, but if it is the case, I use lowdown (https://kristaps.bsd.lv/lowdown/) which also comes with some nice output targets (among the more unusual are Groff and Terminal). Of cource pandoc (https://pandoc.org/) does a very good job here, too.

This is one of those things that the ever-amazing pandoc (https://pandoc.org/) does very well, on top of supporting virtually every other document format.

Folks feel the same way about Markdown versus LaTeX: why use something significantly more complicated where a looser, human-readable grammar works better?

For any other situations, I use https://pandoc.org/, or, generate a Word doc scriptomatically.

pandoc toolchain pour builder une version confortable/imprimable en phase de travail (ePub, pdf, docx, html)

Congrats on the launch, I guess, but there are so many free options that I can't think of a situation where paying $0.25 per document would be justified...? Just to name a few:

Back in the days, I used to use XSL-FO [0] and it was okay. It was not very precise but it rarely if ever broke, and was perfectly integrated with an XML/XSLT solution. Yeah, this was a long time ago.

Last month I used html-to-pdfmake [1] and it's also not very precise and more fragile, but very efficient and fast.

Yet another approach would be to pro grammatically generate .rtf files (for example) and use Pandoc [2] to produce PDFs (I have not tried this in production but don't see why it wouldn't work).

[0] https://en.wikipedia.org/wiki/XSL_Formatting_Objects

[1] https://www.npmjs.com/package/html-to-pdfmake

[2] https://pandoc.org/

Others have mentioned static site generators. I like Hakyll [1] because it can tightly integrate with Pandoc [2] and allows you to develop custom solutions if your needs ever grow.

[1]: https://jaspervdj.be/hakyll/

[2]: https://pandoc.org/

Have you compared it with a conversion by pandoc (https://pandoc.org/)?

I have used it to kickstart a blogging project that I wish to come back to soon. The Lua inter-op for custom readers, writers and filters is great but I wish there was more editor integration and even perhaps an official IDE/editor with built-in debugging features (probably something already do-able with Emacs but I haven't checked). The only blocker for my project is no support for "ChunkedDoc" for Lua filters [1] which forces me to write more code and a complicated Makefile.

[1]: https://github.com/jgm/pandoc/issues/9061