Reading within tiddlywiki

[Sinan Caliskan]

Hi friends

Is there anyway of reading a book which is stored in calibre or zotero library.  Taking notes simultaneously on tiddlywiki and highligt  book and make tiddly?

[Saq Imtiaz]

There is an ePub Slicer plugin mentioned here:

https://groups.google.com/d/msg/tiddlywiki/_VLufc4Svp8/jALzYZ09BAAJ

Not sure how much work it would be to convert an epub, but once done you could presumably use the tools presented in that thread for annotations/notes.

Cheers,
Saq

On Saturday, June 6, 2020 at 12:11:32 PM UTC+2, Sinan Caliskan wrote:

Hi friends

Is there anyway of reading a book which is stored in calibre or from zotero library  and taking notes simultaneously on tiddlywiki?  Or could we  highligt from book and make tiddly? Can we open  book pdf from tiddlywiki.

[Sinan Caliskan]

Hi Saq

Thank you for your suggestion. Its is really good for epub.I mostly study with pdfs from my zotero library.

My request is to open a pdf  from my zotero library. You know we can import zotero bibliography as a bibtex file to tiddlywiki thanks to bibtex importer plugin. But it doesn`t contain any path to locally stored pdf files. If we have a pdf link within a reference tiddly, we can easy open pdf easily while reading the reference. We can open pdf with any pdf viewer or  either if it  is possible open within  tiddlywiki.

Do you think it can be possible ?

Edit:

Actually i discovered that imported references have the file path. But it is not showing on the the tiddler. Is it possible to show file path on the tiddy.

  https://imgur.com/QRXS5w2( there is a bibtex file path ) but  i cant see in tiddly  https://imgur.com/CG6IzNl

How can i see this path on tiddly and lastly Could i open it with with pdf  viewer?

[springer]

Sinan, 

*Seeing* the path is easy: You can make any tiddler display that field by adding {{||bibtex-file}} within the tiddler itself, or adding {{!!bibtex-file}} somewhere in your ViewTemplate.

The PDF can be displayed, too...  the trick is just to create a _canonical_uri field in an associated pdf-display tiddler for each article, and populate it with whatever's in the relevant bibtex-file field, spcifying the Type as application/pdf ... one thing to note is that IF you're using _canonical_uri field then you can't (at least not straightforwardly) also display text for that tiddler, so you'd want the pdf-viewing tiddler to separate from your notes, if your notes live in a text field.

Hopefully those things get you started, and those with more wisdom can follow up...

-Springer

[Sinan Caliskan]

Dear  Springer

Thank you for your reply, it is very important for me. Hopefully i can manage first part, now i can see pdf path.  But i couldn"t understand second part. I am sorry i am not good at tech.

Should i add new tiddler which is containing a _canonical_uri field ?

[TonyM]

Sinan,

I rarely share a different approach than tiddlywiki integration, but for me I currently annotate pdfs with FoxIT reader, and once done drop it into a wiki, I am keen to have a method to export it again, and use foxit and return it. Foxits annotations a world class and so I go with the flow. I actually made a tiddlywiki who's main use is to generate pdf's from a database.

Though my pdfs are not too big.

Regards

Tony

[Sinan Caliskan]

Hi

Thanks for suggestion Tonym. I added "file://" prefix before {{!!bibtex-file}}. So after i copy it with the file path, i am pasting it to firefox browser so  i can open the pdf on the browser. But it can be very usefull directly clickling a file link.

Thanks

[Sinan Caliskan]

Dear Springer

After some search  i got what you mean. Now I can embed pdfs but as you mentioned they are separate tiddly and i have to create for each pdf.

I think that the embeded pdf  should be under  the linked reference tiddly or as a link. Thus we can see embeded pdf under reference tiddly. I think this can be very amazing.

Is there way of converting {{!!bibtex-file}}  to a clickable link? At least this can be enough for me ?

On Saturday, June 6, 2020 at 1:11:32 PM UTC+3, Sinan Caliskan wrote: