Quote:
Originally Posted by atjnjk
In my opinion, a good ebook reader's first priority is to improve speed, stability and legibility. I hope M3 will open books (with large sections, lots of pictures) faster than M2. Multimedia annotation is a plus but not necessary.
|
For you... For me, audio (if not hand-drawn/video) annotations are a necessity. Since Marvin doesn't have them, I'm forced to use an array of other apps/software services to get around the limitation. So my workflow currently is:
- open Marvin's annotation window
- minimize Marvin and launch the fabulous DropVox app (sits in my iOS dock just like Marvin) to speak your annotation
- DropVox automatically sends the MP3 recording to Dropbox
- an IFTTT channel/recipe notices the new recording in Dropbox, and submits the link to listen to it as a new entry in the Day One journaling app (but not instantly, unless you prompt IFTTT manually in the IFTTT app – otherwise, it can take up to 15 minutes)
- I open the Day One journaling app and copy the link to the MP3 annotation from there to Marvin's annotation window, storing it there.
Quite a runaround, eh?
I would really appreciate if Marvin eased this workflow for me one day.
As to "improving speed, stability and legibility", I'd call Marvin rock-solid in those regards. Yes, there may be an occasional crash here or there, but for me, those would not be priorities.
As can be seen, every user's mileage may vary.
Quote:
Originally Posted by atjnjk
What I miss in Marvin is the ability to import/export individual book with its metadata and annotations, e.g., a zip including the book file and metadata files. That would make it easier to archive in pc (I'm a Calibre fan) and/or share with others.
|
Yes, that would be a great feature.
Quote:
Originally Posted by democrite
not sure if this has ever been brought up. If the viewing options haven't been refined yet, there's one particular thing. I've noticed some books use colors, like foreign language learning works that use bold/color to distinguish language, or some works that might have a special font for headers, it'd be nice if the default non-publisher view settings kept those. Perhaps allowing color changes for a default p/div and any other styles that use the same color, while leaving other colors and perhaps fonts alone.
|
Marvin's (mis)treatment of original font colors has been a Marvin weakness from the start. I've been trying to alert Kris to this weakness in Marvin for years now, but with no success so far.
Here is a thread on this issue I started in GitHub back in 2013:
https://github.com/kguil/Marvin-Roadmap/issues/99