#7898 NORM 8.2.0 (: Sugar handbook should not be in PDF

[Zarro Boogs per Child]

#7898: Sugar handbook should not be in PDF
----------------------------+-----------------------------------------------
 Reporter:  skierpage       |         Owner:  sj                  
     Type:  defect          |        Status:  new                 
 Priority:  normal          |     Milestone:  8.2.0 (was Update.2)
Component:  library         |       Version:  not specified       
 Keywords:  joyride-2273:-  |   Next_action:  never set           
 Verified:  0               |     Blockedby:                      
 Blocking:                  |  
----------------------------+-----------------------------------------------
 Browse > OLPC Library > activities > find activities > "Making your own
 activities" has a link to "Sugar Activity Handbook"

 This should be an HTML document.  A partial list of the problems (this is
 Read 49 on joyride-2273):

 * The Browse-download-Journal-run-Read dance is irritating, and until
 #6729 is fixed it saves multiple copies of the PDF in the journal[[BR]]
 * The many blank even pages (2, 4, 8, 16, 26 ...) are silly in an
 e-book.[[BR]]
 * The acres of whitespace on chapter pages are wasted; clicking the arrow
 to advance to a chapter page puts me at a blank screen with part of a
 number in the lower left corner.[[BR]]
 * The uneven left-right page gutters are distracting[[BR]]
 * It breaks concentration to have a page break in the middle of a
 paragraph[[BR]]
 * The page margins are arbitrary.  Every third PgDn leaves me showing the
 bottom of one page and the top of the next, i.e. a lot of white.[[BR]]
 * The hyperlinks e.g.QEMU on Windows p 18 don't work, and even if they did
 you'd leave Read and lose back-forward.[[BR]]
 * Unless each "page" is exactly one XO screen (as in a presentation or
 flash card), the "page 13" metaphor is mismatched with e-book reading.  If
 you use the prominent Back Forward arrows, you skip over most of the
 content!

 etc. The margins and blank pages might be fixable by tweaking the
 generation process, but a PDF in Read on an XO of an electronic document
 doesn't have anything going for it besides embedded fonts.   In HTML in
 Browse is MUCH better.  There are samples on the Web that show book-like
 high-quality display done with HTML and CSS, e.g.
 http://www.alistapart.com/articles/boom

-- 
Ticket URL: <http://dev.laptop.org/ticket/7898>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system