From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: Jeffrey DeLeo <JeffreyDeLeo@gmail.com>, orgmode <emacs-orgmode@gnu.org>
Subject: Re: [off-topic] E-readers and Org-Mode
Date: Mon, 24 Oct 2022 18:34:04 +0000 [thread overview]
Message-ID: <87fsfdt6jn.fsf@posteo.net> (raw)
In-Reply-To: <877d0pi1kn.fsf@ucl.ac.uk> (Eric Fraga's message of "Mon, 24 Oct 2022 17:16:56 +0000")
Fraga, Eric writes:
> On Monday, 24 Oct 2022 at 17:42, Jeffrey DeLeo wrote:
>> I am very happy with my Kobo Elipsa
>
> Your workflow is very similar to that of mine on the reMarkable and the
> two units are similar in size etc. It's a workflow that is fine for
> annotating documents (which is what I want) but definitely no link to
> org mode for the OP... ;-)
Indeed. Both Kobo Elipsa and reMarkable are very tempting and in a
similar price range. The main problem I find is that they both also run
closed and, presumably, proprietary software. I don't know if my
knowledge (and my time) would be enough to try to hack them. And I
imagine that I would run the risk of ending up bricking the gadget.
The annotations by hand with the stylus are difficult to translate to
Org :-) but in any case they are tremendously useful and save
considerable paper and ink.
I wonder if these devices are capable of exporting normal annotations in
plain text or xml? Anyway, I think it would be possible to write some
python script[1] to extract the annotations and then parse the resulting
xml from there to get a nice and beautiful Org document. Which also
leads me to wonder if anyone has tried that. I think it's a good
entertainment for a vacation...
[1] https://stackoverflow.com/questions/1106098/parse-annotations-from-a-pdf
next prev parent reply other threads:[~2022-10-24 18:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 15:16 [off-topic] E-readers and Org-Mode Juan Manuel Macías
2022-10-24 7:09 ` Fraga, Eric
2022-10-24 11:50 ` Juan Manuel Macías
2022-10-24 15:30 ` Fraga, Eric
2022-10-24 16:42 ` Jeffrey DeLeo
2022-10-24 17:16 ` Fraga, Eric
2022-10-24 18:34 ` Juan Manuel Macías [this message]
2022-10-25 7:57 ` Fraga, Eric
2022-10-25 12:55 ` Juan Manuel Macías
2022-10-25 13:59 ` Fraga, Eric
2022-10-26 13:31 ` L.C. Karssen
2022-10-26 14:00 ` Quiliro Ordóñez
2022-10-26 16:27 ` Fraga, Eric
2022-10-29 9:03 ` Juan Manuel Macías
2022-10-25 11:06 ` Eduardo Suarez-Santana
2022-10-25 14:03 ` Fraga, Eric
2022-10-25 14:37 ` Max Nikulin
2022-10-25 15:21 ` Fraga, Eric
2022-10-25 16:59 ` Ken Mankoff
2022-10-27 17:20 ` Max Nikulin
2022-10-27 17:53 ` Juan Manuel Macías
2022-10-28 4:40 ` Ihor Radchenko
2022-10-29 12:54 ` Max Nikulin
2022-10-31 12:18 ` Juan Manuel Macías
-- strict thread matches above, loose matches on Subject: below --
2022-10-23 16:29 Ypo
2022-10-24 7:12 Pedro Andres Aranda Gutierrez
2022-10-24 14:11 ` Juan Manuel Macías
2022-10-25 14:44 Payas Relekar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsfdt6jn.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=JeffreyDeLeo@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).