View Single Post
Old 02-16-2011, 11:37 AM   #15
yelloguy
Enthusiast
yelloguy is fluent in JavaScript as well as Klingon.yelloguy is fluent in JavaScript as well as Klingon.yelloguy is fluent in JavaScript as well as Klingon.yelloguy is fluent in JavaScript as well as Klingon.yelloguy is fluent in JavaScript as well as Klingon.yelloguy is fluent in JavaScript as well as Klingon.yelloguy is fluent in JavaScript as well as Klingon.yelloguy is fluent in JavaScript as well as Klingon.yelloguy is fluent in JavaScript as well as Klingon.yelloguy is fluent in JavaScript as well as Klingon.yelloguy is fluent in JavaScript as well as Klingon.
 
Posts: 30
Karma: 4698
Join Date: Jan 2011
Device: none
@wolf: some fonts look readable on paper but on these devices they are not as readable. these screens do not match the resolution of paper+print and a majority of fonts, especially one with thin parts or strokes look very unreadable. I think it would be a bad idea for publishers to emulate print fonts for these devices. In fact they shouldn't have *any* font information. It should be left to the rendering device if possible. Device manufacturers should study what fonts look good on their screens and make those available for their devices.

@drdann: what?
yelloguy is offline   Reply With Quote