emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ramon Diaz-Uriarte <rdiaz02@gmail.com>
To: Matt Price <moptop99@gmail.com>
Cc: Ramon Diaz-Uriarte <rdiaz02@gmail.com>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Org Mode and PDF Notes!
Date: Thu, 12 Nov 2015 13:23:43 +0100	[thread overview]
Message-ID: <87wptnqucw.fsf@gmail.com> (raw)
In-Reply-To: <CAN_Dec9zt=8roZ5kwsN7UN1xTyvTCvh4Zb2u-N601kXni6-nhw@mail.gmail.com>




On Wed, 11-11-2015, at 21:33, Matt Price <moptop99@gmail.com> wrote:
>>
>>
>>   instead of the text. Bummer! I wonder if RepliGO gives you a lot more
>>   than the rest, or if I am doing something silly.
>>
>> I think that there is no standard way of storing the highlight contents. I
> chose Repligo over EZPDF because it gives you access to the text of the
> highlights!


I'll try to see if I can get repligo (I had it a few years ago)

>
> Okular, I think, stores your annotations in its own database, rather than
> in the pdf. You can (I think!) attach the annotations to the pdf from
> inside Okular.  At leasts, that's what I remember from when I was looking
> around.

Actually, Okular stores the annotations in the PDF itself if you do "Save
As". (It still keeps an internal db, but I never use it anymore). It is
easy to check by doing that and then opening the file with another reader
in another machine (e.g., in an android).



>
> Repligo stores the highlighted text in the "subject" field of the
> annotation. It's possible that the content of the annotation is stored in
> some other field, like "content".  Maybe you can try:
>
> M-: (pdf-annot-get-annots) and look at the output in the *Messages*
> buffer.  Can you see any evidence of the the text? Can you share what you
> learned?

Nope, no evidence of the text. I get things such as

(((buffer . #<buffer Frank_2015_Commentary.pdf>) (page . 13) (edges
0.113553 0.31717 0.868657 0.361746) (type . highlight) (id . annot-13-0)
(flags . 4) (color . "#ffff00") (contents . "") (modified 22081 45188)
(label . "TF201") (subject . "Highlight") (opacity . 1.0) ...)


so we get the location of the highlight (and its properties), but not the
textual contents. And this is the case whether I make the annotation with
EzPDF or Okular or, for that matter, with pdf-tools itself.

So it seems RepliGO is actually giving you a lot more by default :-)


>
> Politza and I are discussing this here:
> https://github.com/politza/pdf-tools/issues/137
>
> that might be a good place to ocntinue the conversation.
>

I'll do. In the meantime, I think this is a limitation coming from
poppler. Other people have mentioned similar things (e.g.,
http://coda.caseykuhlman.com/entries/2014/pdf-extract.html) and using other
tools that depend on poppler (such as Leela:
https://github.com/TrilbyWhite/Leela) also will not give us the text
itself. 



>>
>> Until I found pdf-tools, I had planned to write a node wrapper for pdf.js
> and grab the annotations that way.  But I don't really know how to do that,
> so this turned out to be easier :-)
>
> Anyway, I've judated the post, and it's now possible to create links to
> individualt annotations, though you will have to use my updated version of
> org-pdfview, until/unless Markus accepts my patch.


I just updated packages, and things are working perfectly: I am jumping to
the page and location.



Thanks,


R.




-- 
Ramon Diaz-Uriarte
Department of Biochemistry, Lab B-25
Facultad de Medicina
Universidad Autónoma de Madrid 
Arzobispo Morcillo, 4
28029 Madrid
Spain

Phone: +34-91-497-2412

Email: rdiaz02@gmail.com
       ramon.diaz@iib.uam.es

http://ligarto.org/rdiaz

  parent reply	other threads:[~2015-11-12 12:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 14:42 Org Mode and PDF Notes! Matt Price
2015-11-11 14:59 ` Kaushal Modi
2015-11-11 20:38   ` Matt Price
2015-11-11 20:48     ` Kaushal Modi
2015-11-11 20:58       ` Matt Price
2015-11-12 12:02         ` Sebastian Christ
2015-11-12 11:58       ` Sebastian Christ
2015-11-11 15:06 ` Xebar Saram
2015-11-11 15:10 ` Russell Adams
2015-11-11 16:40 ` Jeffrey DeLeo
2015-11-11 20:18   ` Matt Price
2015-11-11 17:09 ` Memnon Anon
2015-11-11 20:34   ` Matt Price
2015-11-12 17:31     ` Memnon Anon
2015-11-11 20:17 ` Ramon Diaz-Uriarte
2015-11-11 20:33   ` Matt Price
2015-11-11 22:43     ` Matt Lundin
2015-11-12 12:23     ` Ramon Diaz-Uriarte [this message]
2015-11-12 13:11       ` Matt Price
2015-11-13  0:39         ` Ramon Diaz-Uriarte
2015-11-12 14:28       ` Matt Lundin
2015-11-12 22:52         ` Matt Price
2015-11-12 23:51           ` Ramon Diaz-Uriarte
2015-11-12 23:55         ` Ramon Diaz-Uriarte
2015-11-12 11:30 ` Karl Voit
  -- strict thread matches above, loose matches on Subject: below --
2015-11-11 15:15 Peter Davis
     [not found] <20@gmane.emacs.orgmode.nnrss>
2015-11-13  8:04 ` Matti Minkkinen
2015-11-16 10:07   ` Ramon Diaz-Uriarte

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=87wptnqucw.fsf@gmail.com \
    --to=rdiaz02@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=moptop99@gmail.com \
    /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).