Wish There Were Separate Kobo Reader and Kobo Reader Modified Forums

[ZodWallop]

Originally Posted by JSWolf

From what I recall of the nook STR, you could side load fonts and then reference them in the CSS. Same with Sony Readers and Kobo.

In the end, I'm not that picky about fonts. All the ones look pretty similar.

I'd still like it if fonts could be added. I also wish they'd bring back the ability to add your own screensavers. But I guess this isn't a thread about changes I would like to see on the Nook.

[cgsmom]

Originally Posted by ZodWallop

The bezel is not rubbery. The Nook STR is the only one that ever had a rubbery bezel. I liked it. If Nook would take the old ST chassis and slap a 300ppi screen in it with orange lighting and waterproofing, I'd be a happy customer.

I agree with you. All this talk about the NST made me curious about it so I got mine out and charged it. It still works. I had forgotten how comfortable it is to hold. The screen contrast is great. If it had a light I might still be using it. It won’t connect to BN anymore but the SD card still works. I am very happy with the Glowlight 7.8 but it is a little heavy.

[ZodWallop]

Originally Posted by cgsmom

I agree with you. All this talk about the NST made me curious about it so I got mine out and charged it. It still works. I had forgotten how comfortable it is to hold. The screen contrast is great. If it had a light I might still be using it. It won’t connect to BN anymore but the SD card still works. I am very happy with the Glowlight 7.8 but it is a little heavy.

I have the Nook ST with Glowlight. I broke the screen on my original and got a replacement on eBay, but it has the screen tearing, so I bought my first Kobo.

Since then, the better half has moved from her ST with Glowlight to the Glowlight 3, so I do have a perfectly functional Nook ST with Glowlight sitting on a shelf. I just leave it powered off and charge it periodically.

The Nook ST and the 2015 Glowlight Plus are my two favorite Nooks. I still use my Glowlight Plus daily.

[ZodWallop]

Originally Posted by JSWolf

There are ligatures put of the box with no patching needed. Kerning too. I have both kerning and ligatures when I read.

Please explain what the patch 'optimizeLegibility' is for.

[DNSB]

Originally Posted by ZodWallop

Please explain what the patch 'optimizeLegibility' is for.

Sheesh... Jon rather proudly proclaims he only reads epubs. RMSDK quite happily handles kerning and ligatures out of the box. Whatever Adobe's other failings are, their font handling is very good.

The 'optimizeLegibility' patch is for kepubs as might be guessed from the header for that patch section which is "KePub stylesheet additions:".

Personally, I prefer epubs partly due to what I feel is an overly aggressive approach to putting more text on the page when reading kepubs despite the occasional oddities this causes with fully justified text even without the Kepub stylesheet patches enabled.

[ZodWallop]

Originally Posted by DNSB

Sheesh... Jon rather proudly proclaims he only reads epubs. RMSDK quite happily handles kerning and ligatures out of the box. Whatever Adobe's other failings are, their font handling is very good.

The 'optimizeLegibility' patch is for kepubs as might be guessed from the header for that patch section which is "KePub stylesheet additions:".

I was aware that he was talking about ePubs and the patch is for kepubs.

Kobos and Nooks both handle ePubs using Adobe's software, so Kobo gets no credit for how well ePubs work on a Kobo.

Kepubs are Kobo's home-brewed format and you do have to patch to have ligatures. That Kobo also handles ePub doesn't mean a lot to me if their layout on their preferred format sucks.

How much leeway would he give Amazon if the Kindle did some things better on mobi than it does on KFX?

[DNSB]

Originally Posted by ZodWallop

I was aware that he was talking about ePubs and the patch is for kepubs.

So you were trying to drag the irrelevant into the discussion?

Originally Posted by ZodWallop

How much leeway would he give Amazon if the Kindle did some things better on mobi than it does on KFX?

Now that you mention it, I've seen a couple of books where the azw3 version looked better than the KFX version. At least to a typography enthusiast.

As for Nook software? I've only handled three Nooks and I was not impressed by the software. I also found the packaging pretty meh given that most electronics these days have been shrinking the bezels so being handed an ereader with large bezels is like being asked to admire the fins on a 1959 Cadillac Eldorado.

That at this point in time, B&N's epub3 support is, at best, pathetic doesn't help matters.


“If the facts are against you, argue the law. If the law is against you, argue the facts. If the law and the facts are against you, pound the table and yell like hell”―Carl Sandburg

[shalym]

Originally Posted by DNSB

So you were trying to drag the irrelevant into the discussion?

Now that you mention it, I've seen a couple of books where the azw3 version looked better than the KFX version. At least to a typography enthusiast.

I'm curious...I thought that azw3 didn't support ligatures, kerning, or hyphenation. What are the other elements that would make a book look better to a typography enthusiast?

Shari

[ZodWallop]

Originally Posted by DNSB

So you were trying to drag the irrelevant into the discussion?

I don't think Kobo's ability to produce a decent layout on their preferred format is at all irrelevant.

As for Nook software? I've only handled three Nooks and I was not impressed by the software. I also found the packaging pretty meh given that most electronics these days have been shrinking the bezels so being handed an ereader with large bezels is like being asked to admire the fins on a 1959 Cadillac Eldorado.

I guess that's the different between a cursory glance and long term use.

The people that grumble about Nook bezels tend to be people who saw pictures online or played with one in a store. Shockingly, the Nook forum isn't crowded with posts complaining about the too large bezels.

“If the facts are against you, argue the law. If the law is against you, argue the facts. If the law and the facts are against you, pound the table and yell like hell”―Carl Sandburg

“There ain't no good guy, there ain't no bad guy
There's only you and me and we just disagree”―Dave Mason

[MGlitch]

Originally Posted by ZodWallop

the Nook forum isn't crowded with posts complaining about the too large bezels.

The Nook forum isn’t exactly crowded period full stop either.

[ZodWallop]

Originally Posted by MGlitch

The Nook forum isn’t exactly crowded period full stop either.

Touche!

[DNSB]

Originally Posted by shalym

I'm curious...I thought that azw3 didn't support ligatures, kerning, or hyphenation. What are the other elements that would make a book look better to a typography enthusiast?

Shari

I read with left justified where possible so hyphenation is not an issue. Ligatures and kerning when done wrong are more annoying to me than not having ligatures and kerning. That is what was happening in a couple of KFX ebooks I was looking at. I suspect that most people would not notice but to me, the errors stood out and were annoying.

[JSWolf]

Originally Posted by DNSB

Sheesh... Jon rather proudly proclaims he only reads epubs. RMSDK quite happily handles kerning and ligatures out of the box. Whatever Adobe's other failings are, their font handling is very good.

The 'optimizeLegibility' patch is for kepubs as might be guessed from the header for that patch section which is "KePub stylesheet additions:".

Personally, I prefer epubs partly due to what I feel is an overly aggressive approach to putting more text on the page when reading kepubs despite the occasional oddities this causes with fully justified text even without the Kepub stylesheet patches enabled.

I prefer ePub because of the bugs/issues with the text handling with KePub.

With KePub, you have to have a line height larger then I want in order to alleviate the bug where some of the first line on the next page shows at the bottom of the current page. There are issues with hyphenation sometimes. And then ePub allows for smaller spaces. KePub does not. So overall, the text on screen looks better with ePub then it does with KePub.

KePub forces less text per page if you want to hae the top lines complete.

[ZodWallop]

Originally Posted by JSWolf

I prefer ePub because of the bugs/issues with the text handling with KePub.

With KePub, you have to have a line height larger then I want in order to alleviate the bug where some of the first line on the next page shows at the bottom of the current page. There are issues with hyphenation sometimes. And then ePub allows for smaller spaces. KePub does not. So overall, the text on screen looks better with ePub then it does with KePub.

KePub forces less text per page if you want to hae the top lines complete.

That's dependent on the font, I think. I use Literata Book, Bookerly and a couple of others and haven't seen it. And I keep the line height slider all the way to the left.

But I have seen it in the past.

Maybe Kobo's finally fixed the bug?

[MGlitch]

Originally Posted by ZodWallop

That's dependent on the font, I think. I use Literata Book, Bookerly and a couple of others and haven't seen it. And I keep the line height slider all the way to the left.

But I have seen it in the past.

Maybe Kobo's finally fixed the bug?

Yes, as Jon often does when he's against something he's neglected to mention that the font used, the size used, and line spacing all play a role in this.

I don't have the line spacing all the way to the left, I did enable the line 10 patch though, with Lexie Dama and my settings I get 32 lines of text and the spacing between lines is just enough that a tittle could fit between an ascender and descender and there's no doubling at the bottom of the screen.

I can still get the doubling but it generally only comes when the line spacing and font size are set to points that make actually reading a pain anyway.