View Single Post
Old 12-07-2010, 06:08 PM   #10
Mekk
Member
Mekk is on a distinguished road
 
Mekk's Avatar
 
Posts: 21
Karma: 50
Join Date: Jun 2010
Location: Poland
Device: Sony PRS-600
Post

Quote:
Originally Posted by kovidgoyal View Post
well the annotations will definitely be stored separately, but they may in addition, be stored in the epub.
If thing is saved in two places, one goes out of date ;-)

Quote:
I find sending two files to give someone annotations is unnecessary complicated.
But note also the case mentioned above: if the book annotated is commercial, I may not feel allowed to send the book itself. At the same time sending or even publishing on the web "my annotations to such and such book" is OK (and people who also bought this book would be able to review what I marked as important - for example).

Whatever - it need not be resolved straight away.

Quote:
Annotations will be handled like the rest of the metadata in the calibre library (i.e. they will be updated in the file when saving to disk and sending to device).
I am not very happy with having to "save to disk" my book to preserve annotations. My book usually already is on the disk, annotations are just extras.

In fact, I'd love most the scenario in which whenever I connect my reader, I'd be able to just "sync annotations" without having to worry about which books I annotated since prev sync etc.

Quote:
except that annotations will probably be stored in the sqlite database or in a separate file in each books directory in the calibre database.
Considering loose structure and possibly large size (I happened to make hundreds of notes in some book) I suggest a file in book directory.

Also, some idea of where to save graphical annotations (likely as .svg) is needed. Subdirectory below book dir? Paste them inside actual annotations file? Sth else?

Quote:
And I'd prefer to use JSON rather than XML for the annotations.
I feel sick whenever I see XML namespaces so I like this idea, I offered XML as everything in .epub is <so>taggy</so>.

Another reason for XML is that it may be easier to embed data inside (like aforementioned graphics files). But, well...

I will try to draft some sketch of how could such .json possibly look like (but not today ;-)). Once it is defined I can also volunteer to work on converters to/from sony (=adobe) format.
Mekk is offline   Reply With Quote