Standard system fonts for Kindle Fire?

[sjkramer]

I can't seem to find this anywhere, can anyone tell me what they would be? I'm working on creating ebooks for Kindle (KF8) and would like to know what can be specified in the style sheet without having to embed. If this has been discussed elsewhere, I'd be grateful for a link to the thread. Thanks.

[wallcraft]

The fonts supported by the Kindle reader app on the Fire are: Georgia, Caecilia, Trebuchet, Verdana, Arial, "Times New Roman", Courier, and Lucida.

[sjkramer]

Thanks SO much!

Why specify the font at all? It is better for the person reading if s/he can choose the font to match their own tastes. IMO, eBooks are like web pages in that the reader (person) should be able to choose the font they like best. With print books you have no choice but to force a font selection, but with eBooks it should be up to the reader.

[Jessica Lares]

Originally Posted by jswinden

Why specify the font at all? It is better for the person reading if s/he can choose the font to match their own tastes. IMO, eBooks are like web pages in that the reader (person) should be able to choose the font they like best. With print books you have no choice but to force a font selection, but with eBooks it should be up to the reader.

It makes for a better experience if the reader doesn't have a choice because it allows for better WYSIWYG formatting that is universal across all PC/Mac/Kindle/iPad platforms and allows for richer content to be put in more prominent places. We want to make reading more easier, but at the same time, you don't want to let that beautiful 1024x600 screen go to waste.

Originally Posted by Jessica Lares

It makes for a better experience if the reader doesn't have a choice because it allows for better WYSIWYG formatting that is universal across all PC/Mac/Kindle/iPad platforms and allows for richer content to be put in more prominent places. We want to make reading more easier, but at the same time, you don't want to let that beautiful 1024x600 screen go to waste.

I totally disagree with that. The idea behind reflowable text is to allow the reader to set the formatting. Forcing a font on a reader is so Apple-like. Plus I guarantee a forced font won't have a uniform look or quality across devices as each device renders text uniquely.

[sjkramer]

I happen not to agree with the reader's insistence on setting a body typeface (begin the rotting-egg pelting now). However, I recognize that this is overwhelmingly the advice given (demanded?) by all. For clarification, I'm referring to the display font, not the body font. Even Amazon, which bleeps out the "reader experience" line at every chance, encourages designing these elements of the book (chapter headings, subtitles, title page, etc).

[astrodad]

Originally Posted by jswinden

I totally disagree with that. The idea behind reflowable text is to allow the reader to set the formatting. Forcing a font on a reader is so Apple-like. Plus I guarantee a forced font won't have a uniform look or quality across devices as each device renders text uniquely.

You do realize that iBooks lets you change the font of text as well, as long as the book supports it.

[HarryT]

Originally Posted by jswinden

Forcing a font on a reader is so Apple-like.

Can you explain what you mean by that? Apple's "iBooks" reader lets you choose the font, as long as it's not hard-coded by the book.

[DiapDealer]

I totally disagree with that. The idea behind reflowable text is to allow the reader to set the formatting. Forcing a font on a reader is so Apple-like. Plus I guarantee a forced font won't have a uniform look or quality across devices as each device renders text uniquely.

I see nothing wrong with "forcing" a reader to see certain fonts for chapter headers and other special text (verse, song, signage, drop-caps) that may occur in a book... not to mention being able to use glyphs or characters that may not exist in standard, included fonts. After, all... what's the point of having the ability to embed (or choose) different fonts if it's considered bad form to do so. There still needs to be a level of artistic freedom in creating an ebook... otherwise, what's the point of having the ability to style the text at all?

I will agree that forcing a reader to endure your particular font of choice for the main, basic text of the book is a bad idea (unless you need access to special characters that would otherwise be rendered as ugly question-marks or weird squares.)

Originally Posted by HarryT

Can you explain what you mean by that? Apple's "iBooks" reader lets you choose the font, as long as it's not hard-coded by the book.

By Apple-like I mean the "do it Steve Jobs's way are not at all" mentality that has been the Apple SOP for over a decade. In other words, forcing a font in a Kindle book is like telling me I have to read your book using your font. That is annoying as my eyes work best with certain fonts and I should be allowed to choose those fonts. I will regardless because I can strip the DRM and clean up the CSS, but most folks with a eReader probably don't have that expertise.

Originally Posted by DiapDealer

I see nothing wrong with "forcing" a reader to see certain fonts for chapter headers and other special text (verse, song, signage, drop-caps) that may occur in a book... not to mention being able to use glyphs or characters that may not exist in standard, included fonts. After, all... what's the point of having the ability to embed (or choose) different fonts if it's considered bad form to do so. There still needs to be a level of artistic freedom in creating an ebook... otherwise, what's the point of having the ability to style the text at all?

I will agree that forcing a reader to endure your particular font of choice for the main, basic text of the book is a bad idea (unless you need access to special characters that would otherwise be rendered as ugly question-marks or weird squares.)

I was referring to the MAIN BODY TEXT. I agree special characters, etc. can be embedded, though I'm no fan of bloating files for artistic flair. I read to absorb knowledge not to see how artsie-fartsie the book designer can be. An eBook is not a photo are painting or a special print edition of a book. All of those definately have reason for artistic design. However, an eBook is more often than not more about reflowing text in a manner which allows the reader (person) to read the text in the most satisfying manner. Therefore I believe the focus should be on the content with as little forced formatting as possible.