matthiaskramm

6 ms·

1. 31.▲
   by matthiaskramm 16y ago

   Understandable concern. For now let's just say that we have a blog post in the queue (part 3/3 of the HTML5 series) that describes exactly how (and to which degree) we store and (re-)distribute fonts.
2. 32.▲
   by matthiaskramm 16y ago

   We're looking into releasing as much of our HTML5 conversion as possible as open source. For starters, basic technical details on how our conversion works will appear on our tech blog http://coding.scribd.com in the next few days.
3. 33.▲
   by matthiaskramm 16y ago

   We totally love your j/k keybinding idea. Consider it implemented. Maybe we'll additionally do s/w, a binding that comes more naturally to people unfamiliar with VI, but familiar with computer games :)
4. 34.▲
   by matthiaskramm 16y ago

   does fullscreen help? what's your screen resolution?
5. 35.▲
   by matthiaskramm 16y ago

   about 3: there is a way to tone that down- click on "fullscreen" (the square with the arrow) on the bottom toolbar.
6. 36.▲
   by matthiaskramm 16y ago

   We're aware that there are text-selection inconsistencies (caused by the way browsers handle text above images). We're working hard on improving that.
7. 37.▲
   by matthiaskramm 16y ago

   stay tuned.
8. 38.▲
   by matthiaskramm 16y ago

   custom fonts, for starters :)
9. 39.▲
   by matthiaskramm 16y ago

   Investment risk. Scribd is a small company, and putting a whole battalion of developers on a PDF to HTML5 conversion for half a year without even knowing whether that'll turn out to be possible (as in, good enough for 10,000,000 documents)