MobileRead Forums - View Single Post

AlPe · 02-06-2014, 11:22 AM

Hi, I'm Alberto Pettarin, mentoring the students developing EPUB3Reader.

Thanks for appreciating our project! Please note that so far the code has been written by students developing on Android for the first time*.

Hence, I would discourage taking the code "as is", but I encourage you to "steal" as many ideas as you like. (Additional ideas: http://www.albertopettarin.it/rs.html )

A word of caution: regrettably, the EPUB specification does not contain an explicit way of describing parallel texts in a declarative way (metadata, RDF properties, etc.) --- nor the IDPF does seem to care about it. Hence, we adopted the naming convention described in the GitHub main page --- please be aware of the (arbitrary) nature of this convention if you plan to support parallel texts**.

Happy reading!

* Actually, next month there will be a heavy refactoring round, where we will fix many open issues, and better structure the code for future development by another set of students.

** For example, we are going to support the same naming convention, but applied to the OPF manifest id's instead of the actual filenames.

EDIT: there is another MR thread about EPUB3Reader here: https://www.mobileread.com/forums/sho...d.php?t=222054

02-06-2014, 11:22 AM	#8
AlPe Digital Amanuensis Posts: 727 Karma: 1446357 Join Date: Dec 2011 Location: Turin, Italy Device: Several eReaders and tablets	Hi, I'm Alberto Pettarin, mentoring the students developing EPUB3Reader. Thanks for appreciating our project! Please note that so far the code has been written by students developing on Android for the first time. Hence, I would discourage taking the code "as is", but I encourage you to "steal" as many ideas as you like. (Additional ideas: http://www.albertopettarin.it/rs.html ) A word of caution: regrettably, the EPUB specification does not contain an explicit way of describing parallel texts in a declarative way (metadata, RDF properties, etc.) --- nor the IDPF does seem to care about it. Hence, we adopted the naming convention described in the GitHub main page --- please be aware of the (arbitrary) nature of this convention if you plan to support parallel texts. Happy reading! Actually, next month there will be a heavy refactoring round, where we will fix many open issues, and better structure the code for future development by another set of students. ** For example, we are going to support the same naming convention, but applied to the OPF manifest id's instead of the actual filenames. EDIT: there is another MR thread about EPUB3Reader here: https://www.mobileread.com/forums/sho...d.php?t=222054 Last edited by AlPe; 02-06-2014 at 11:26 AM.