View Single Post
Old 04-09-2019, 04:39 PM   #67
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,238
Karma: 148951761
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by rfog View Post
Of course, but both things need to be addressed.

I can understand that a generic eBook reader like Marvin needs to resolve rendering and other bugs before, but as developer myself, it could be advanced in both frontlines. What I mean is the perfection does not exists and we don't need perfect and exact rendering before start with other parts.
Yes we do need proper rendering first. That is the most important part of a reading program. Syncing annotations come after we get correct rendering. So Marvin needs the rendering issues fixed before anything gets done with annotations. The majority of people who read eBooks want them rendered properly more so then syncing annotations.

Fix the rendering and then fix the annotations and voila, done. But annotations is last.
JSWolf is offline   Reply With Quote