Consider a better support of ZIM files without books in HTML

[kelson42]

I think we should maybe consider a better support of ZIM files without HTML. The reasons are:

• This would save disk usage (I estimate a reduction of 30% of the whole size)
• Make easier the integration of third party ebook sources which don't (easily) provide HTML version of their content

Currently I see two big reasons to keep the HTML versions:
1 - Full text engine applying to HTML only
2 - Ability to directly see the content

These two things might be fixed with:
1 - Support ability to fulltext index EPUBs (relatively easy) see openzim/libzim#289
2 - Providing readers for multiple platforms within the ZIM... even maybe a pure Web Epub reader?

[kelson42]

@eshellman This ticket might be of interest for you

[Popolechien]

Sure, sounds good but what would the final output look like compared to what we have now?

[kelson42]

Sure, sounds good but what would the final output look like compared to what we have now?

@Popolechien Same without the book in HTML directly usable from the browser, in place we would have an info page explaining how to read the EPUB file from the Browsers, mobile, computer, etc...

[Popolechien]

@kelson42 Well, if the idea is to save some space, how about offering either Gutenberg epubs or Gutenberg HTML and hope that people would know the difference? Much like we have Wikipedia with or without images, in a way.

[kelson42]

@kelson42 Well, if the idea is to save some space, how about offering either Gutenberg epubs or Gutenberg HTML and hope that people would know the difference? Much like we have Wikipedia with or without images, in a way.

@Popolechien This might be done, can be already done, but this is not the point of the ticket which is about providing a better UX without HTML. Buy maybe you just want to say "I don't think we need that: we should provide one with HTML and one with EPUB and people can only have one or the either and live with that."

[Popolechien]

we should provide one with HTML and one with EPUB and people can only have one or the either and live with that.

Yes.

[kelson42]

@Popolechien To me this would be a fallback solution. But I believe we might be able to solve the problem properly.

We could be able to solve (2) in an even better manner by using a pure javascript EPUB reader (so for the end user) it would be a similar experience as having the HTML in the ZIM file. We could for example use https://github.com/futurepress/epub.js/

[eshellman]

only tricky thing deploying epub.js is overcoming same-origin javascript issues, but you probably are experienced with that

…

On Nov 14, 2019, at 11:00 AM, Kelson ***@***.***> wrote: @Popolechien <https://github.com/Popolechien> To me this would be a fallback solution. But I believe we might be able to solve the problem properly. We could be able to solve (2) in an even better manner by using a pure javascript EPUB reader (so for the end user) it would be a similar experience as having the HTML in the ZIM file. We could for example use https://github.com/futurepress/epub.js/ <https://github.com/futurepress/epub.js/> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#95?email_source=notifications&email_token=AAHCGMKVWBMDWPFBYGF7GCDQTVYYBA5CNFSM4JMDYFJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEECKPAY#issuecomment-553953155>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHCGMKP2IMQALSTQ7XIDM3QTVYYBANCNFSM4JMDYFJA>.