Best Font for Libra 2

[ZodWallop]

Originally Posted by Deobulakenyo

Pardon my ignorance but is ligatures GOOD or BAD in ereaders?

What is the implication if a font has ligatures?

The only implication is they make the layout look nicer to me, personally

[JSWolf]

Originally Posted by hobnail

Not all ebooks have css for the body tag. Or they may have a div tag that encloses the entire chapter, which may need its css fixed. If your stylesheet.css or whatever it's called doesn't have anything for the body tag you can add it;

body {
  line-height: 1.2;  /* or normal */
}

A line height of 1.2 (IMHO) is too large.

[JSWolf]

Originally Posted by Uncle Robin

Ligatures are joined characters - some people consider them to be absolutely indispensable to the reading experience, others care so little about them they may not even notice their presence or absence. YMMV, personally, I couldn't give a Continental for them in English, but empathize with those who do care because I hate their absence in Hindi.

I don't mind not having ligatures. What I do mind is not having kerning.

[jasius]

Does anyone know what font this is? The novel is Beasts and Beauty by Soman Chainani

[hobnail]

Originally Posted by tschucha

Did you do this by creating a rule in Calibre by going to Preferences-Conversion-Common Opitions-Look & Feel- Transform styles?

Also on the in Preferences-Conversion-Common Opitions-Look & Feel- Styling page at the bottom is a Filter style information box that allows you to completely remove stuff. Do you know if it is safe to remove Fonts and Margins? Some converted epub books do not allow a kobo reader to change fonts at all and others seem to have a large margin on the left side for no apparent reason. I'd love to get rid of both of these issues.

Sorry, I missed this question.

Yes, I remove the fonts and margins when doing a conversion. I have all of those boxes checked, fonts, margins, padding, floats, and colors.

Adding extra css doesn't fully fix the warts with things like line-height, margins, etc. because the files almost always have a class on every p tag, on the body tag, and often a div tag around the entire chapter. So the css for p.indent will have precedence over a plain unadorned p. This is why I go in with a big sledge hammer and remove the class on the p tags for the chapters, and the one on the body tag, and the one on the div tag. Even that's often insufficient because, lord knows why, but they put spans with a class inside the p tags for each paragraph so I remove that class as well. And sometimes they randomly use different classes on the p tags (and spans) so I have to do a search for p class= and fix those. And then they'll use a span for italic and that needs to be changed to a plain i tag, or they'll use a class on an i tag, but in both cases they may change the font-size so I just delete the class on the i tag and change the italic spans to i. The joys of being overly fussy and wanting "normalized" epubs that all have the same font size, line height, etc.

[aussetg]

Originally Posted by Deobulakenyo

Pardon my ignorance but is ligatures GOOD or BAD in ereaders?

What is the implication if a font has ligatures?

Ligatures are *always* good because the font is designed for them.

Fonts without any ligatures are designed differently.

[Moonbase59]

I still love Linux Libertine and Linux Biolinum, mainly because I use these when producing PDF/real books. Then again, I have a 7" 300ppi reader, and these might not be the perfect fonts for any eReader.

When I want real good Unicode coverage, I use a combination of Kurinto Text (serif), Kurinto Sans (sans) and Kurinto Mono Narrow (monospace). These are huge fonts, due to their number of Unicode glyphs, but there exist "tuned-down" smaller versions (labelled "core"). Kurinto fonts are carefully tuned for size, so you can mix-and-match different languages and writing systems easily.

The attached screenshot from my Tolino Vision 5 shows text in Kurinto Text (note sub- and superscripts, greek delta and the asterism), and a headline in Olde, a blackletter font from the Kurinto project. Disregard bad formatting—this was just a test for embedding font subsets into an EPUB, to keep the file size manageable.

[martinot]

I have loaded a lot off different fonts on my e-reader, but what I always come back to is the Kobo Nickle font. I think it is really one of the best font for reading books.

[Deobulakenyo]

I got this Sabon etext font. This has the usual 4 types (regular, italics, bold and bold-italic) and when i transfer this to my Libra 2, and choose the font, the text is italicized. Even when i deleted the three types and retained the regular one, it is still itlicized.

What is the solution for this?

https://www.cdnfonts.com/sabon-etext.font

[Barruel]

Originally Posted by Deobulakenyo

I got this Sabon etext font. This has the usual 4 types (regular, italics, bold and bold-italic) and when i transfer this to my Libra 2, and choose the font, the text is italicized. Even when i deleted the three types and retained the regular one, it is still itlicized.

What is the solution for this?

https://www.cdnfonts.com/sabon-etext.font

TTF names for the italic variant are wrong. Open the italic font in FontForge and change "Regular" at "Styles (Subfamily)" under "TTF Names" in the dialog at "Elements > Font info..." to "Italic".

[Deobulakenyo]

Originally Posted by Barruel

TTF names for the italic variant are wrong. Open the italic font in FontForge and change "Regular" at "Styles (Subfamily)" under "TTF Names" in the dialog at "Elements > Font info..." to "Italic".

I am lost already hahahaha. Why is it that even if i use only the regular one and deletes the other styles, the text remains itallic?

[Sirtel]

Originally Posted by Deobulakenyo

I am lost already hahahaha. Why is it that even if i use only the regular one and deletes the other styles, the text remains itallic?

Because the font metadata is wrong.

Here are detailed instructions for fixing the fonts for Kobo readers (which are quite fussy in that regard):
https://wiki.mobileread.com/wiki/Kob...play_Correctly

[RobertJSawyer]

Originally Posted by ZodWallop

The only implication is they [ligatures] make the layout look nicer to me, personally

But don't ligatures make it harder to search? If the typographic character in the ebook is actually a single "fi" ligature glyph, won't a search for the word "fine" fail?

[jackie_w]

Originally Posted by RobertJSawyer

But don't ligatures make it harder to search? If the typographic character in the ebook is actually a single "fi" ligature glyph, won't a search for the word "fine" fail?

That would (may???) be true if the ebook text actually contained the 1-char "fi" ligature rather than the 2-char string "fi".

This is not usually the case, though. Usually the ebook text only contains the normal 2-char strings (sometimes 3-char strings). It's the decent rendering apps (eink reader or phone/tablet) coupled with a font which actually contains ligature glyphs which automatically read the 2-char "fi" string and convert to the 1-char "fi" ligature on-the-fly before displaying on the screen.

It's somewhat similar with hyphenation. Decent rendering apps don't need "soft hyphens" to be present in the ebook text.

[RobertJSawyer]

Thank you, @jackie_w