ebook situation
cedounet opened this issue · comments
Let's use that as a master bug.
There are several problems with our ebooks.
- They are too big so nobody uses them on Kindle. There is an action about that #216
- The whole (sans)-serif thing i think is useless. From my experience the reader opens with last selected font...
#228 - We support 3 formats, two of them are outdated. I have no problem keeping them, if they are actually used of course. #242
- The list of flowchart does not work (despite 2 entries). This might explain why you needed to do ruby magic for the website. #240
- Some stuff don't show up greatly (degres, some tables, ...) #223
Might sound like a rant, I promise it is not, just me not being a user of ebooks I need guidance on what makes sense to do and somebody testing it.
Opinions/thoughts ?
C/
MWE for debug now in a branch https://github.com/hendricius/the-sourdough-framework/tree/225-ebook-situation
-
I don't have a kindle myself. But my dad tried with the .epub version and he could use this tool to send it over (https://www.amazon.com/gp/sendtokindle). It supports max 200mb, so that should be good.
-
This was a request originally from someone who had a hart time reading the pdf with serifs. I am no expert on accessibility, but I propose we keep it for now?
-
Agreed - let's remove .mobi and azw3. We can update the instructions on the website for kindle users? It should save a lot of build time.
-
At least for the website it works currently.
-
Agreed. I will see if PR #223 fixes it and test a bit more.
- pdf sans serif makes sense. Plenty of reasons not to like serif on low res screens… or other reasons. We should keep it.
The sans serif ebook I am more puzzled about as ebook will choose the font it wants and its size.
- At least for the website it works currently.
Yes agree.. you did a good job at working around the issues for the website, just that does not solve the ebook. And we should fix them at the root if we can :)
Agreed - let's remove .mobi and azw3. We can update the instructions on the website for kindle users? It should save a lot of build time.
I will do that in 2 steps... First remove downloads links and see if somebody is unhappy... If not I will remove the code in the makefile.
Agreed - let's remove .mobi and azw3. We can update the instructions on the website for kindle users? It should save a lot of build time.
I will do that in 2 steps... First remove downloads links and see if somebody is unhappy... If not I will remove the code in the makefile.
- pdf sans serif makes sense. Plenty of reasons not to like serif on low res screens… or other reasons. We should keep it.
The sans serif ebook I am more puzzled about as ebook will choose the font it wants and its size.
@cedounet thanks! I agree, I checked on some ebook readers and they indeed ship their own fonts mostly. So it makes no sense to have 2 versions for epub. Only for the PDF.
Look like we are done with the easy ones :D
The list of flowchart does not work (despite 2 entries). This might explain why you needed to do ruby magic for the website.