Nook Glowlight 3 sale 89.99 at B&N website - Page 9

ZodWallop · 01-09-2018, 06:16 PM

Quote:

Originally Posted by robko

Widow/orphan settings and how they are handled in epub I believe. There has been a number of different discussions of it over the years in the Kobo forums.

So am I safe to assume those are the same issues plaguing the Glowlight 3? Maybe the solution is easier than B&N realizes?

I'm out of my depth, I admit.

robko · 01-09-2018, 09:27 PM

Quote:

Originally Posted by ZodWallop

So am I safe to assume those are the same issues plaguing the Glowlight 3? Maybe the solution is easier than B&N realizes?

I'm out of my depth, I admit.

Honestly, I'm way out of my depth which is why I didn't expand on my answer.

If IIRC and understand it, the issue at it's core is in the Adobe epub rendering code, and may not be easily be manipulated/changed by the ereader companies. I *think* there were a couple of hacks for Kobo that people were using to try and get around this problem but they had their own potential downsides. I can't say I've ran into it or looked at it closely as I usually use kepubs so I could be wrong on all this

. Check the Kobo forum if you want correct details.

What I can say with certainty is that B+N answer that it's because ebooks are designed for a specific number of pages is completely wrong

tiltowait · 01-09-2018, 09:38 PM

Quote:

Originally Posted by robko

What I can say with certainty is that B+N answer that it's because ebooks are designed for a specific number of pages is completely wrong

Yeah, that part struck me as odd. And I noticed that they only responded to one of the (two) issues I wrote about. I'm not going to write back, and instead hope the person responding really did kick it up the chain (to someone who can do something about it).

DNSB · 01-09-2018, 11:02 PM

Quote:

Originally Posted by ZodWallop

On the weird paragraph breaks, I seem to remember The eBook Reader complaining about the same thing on various Kobo reviews from a while back. Does that sound familiar to anyone?

There was an issue in RMSDK a few years back where very long paragraphs started breaking at odd points. That bug in RMSDK was swatted but the patch still lives on since it's side effect was disabling widows/orphans effectively setting them to 1 regardless of the CSS settings.

I've attached a rather short test epub to this message. It should have a cover page and a page with a single paragraph. Could someone test it on a GL3 and see if the paragraph gets borked. The CSS sets widows/orphans to 1 so the paragraph should not split. I tested it on 4 Kobo ereaders and a Tolino epos all of which displayed as expected. Thanks for your help!

ZodWallop · 01-10-2018, 11:13 AM

Quote:

Originally Posted by DNSB

There was an issue in RMSDK a few years back where very long paragraphs started breaking at odd points. That bug in RMSDK was swatted but the patch still lives on since it's side effect was disabling widows/orphans effectively setting them to 1 regardless of the CSS settings.

I've attached a rather short test epub to this message. It should have a cover page and a page with a single paragraph. Could someone test it on a GL3 and see if the paragraph gets borked. The CSS sets widows/orphans to 1 so the paragraph should not split. I tested it on 4 Kobo ereaders and a Tolino epos all of which displayed as expected. Thanks for your help!

I'm off today. I'll check it after the repairmen finish fixing the heater.

ZodWallop · 01-10-2018, 12:58 PM

I tested the book, but am not sure what I was supposed to see. Here are two pics, one justified and one left at auto.

barryem · 01-10-2018, 01:04 PM

Quote:

Originally Posted by DNSB

There was an issue in RMSDK a few years back where very long paragraphs started breaking at odd points. That bug in RMSDK was swatted but the patch still lives on since it's side effect was disabling widows/orphans effectively setting them to 1 regardless of the CSS settings.

I've attached a rather short test epub to this message. It should have a cover page and a page with a single paragraph. Could someone test it on a GL3 and see if the paragraph gets borked. The CSS sets widows/orphans to 1 so the paragraph should not split. I tested it on 4 Kobo ereaders and a Tolino epos all of which displayed as expected. Thanks for your help!

I put it on my Glowlight 3 and it looked just fine. I also looked at it in the Calibre reader and it looked the same there.

Barry

DNSB · 01-10-2018, 03:29 PM

Quote:

Originally Posted by ZodWallop

I tested the book, but am not sure what I was supposed to see. Here are two pics, one justified and one left at auto.

Quote:

Originally Posted by barryem

I put it on my Glowlight 3 and it looked just fine. I also looked at it in the Calibre reader and it looked the same there.

Barry

What you saw was a short paragraph not being split over multiple pages. This came from an earlier message where a short paragraph was being split over two pages (a few lines at the top of one page, a few at the top of the next page.) The test epub has widows/orphans set to 1 and very simple CSS.

See tiltowait's message here for the original: Post 108 in thread .

Thanks for the feedback.

JSWolf · 01-10-2018, 06:36 PM

Quote:

Originally Posted by ZodWallop

Depending on the type of reading you are doing, it is more useful to count screens.

I'm not too worried about having to cite pages from The Sonora Noose in a scholarly paper. But if my break is winding down, it is handy to know that 5 pages left = 5 screens of reading.

Both styles are useful. But what is the overwhelming use case for e-books?

Number of screens as the page numbering is not real. nooks uses RMSDK and thus, real (ADE) page numbers.

JSWolf · 01-10-2018, 07:02 PM

Quote:

Originally Posted by tiltowait

The kepub renderer also happily rips paragraphs apart. I think it's unique to ePub.

You cannot compare the kepub renderer to RMSDK on the nook. You have to compare RMDSK on the Kobo to RMSDK on the nook and Kobo's RMSDK used to have a long paragraph bug, but that's since been fixed. It now behaves as it should.

However, I prefer to set widows and orphans to 1 so the screen ends in rouchly the same place.

ZodWallop · 01-10-2018, 08:03 PM

Quote:

Originally Posted by JSWolf

Number of screens as the page numbering is not real. nooks uses RMSDK and thus, real (ADE) page numbers.

I'm not sure that arguing what is 'real' when it comes to displaying ebooks on a screen even means.

But if I have five minutes left on a break, it is a LOT more helpful to know that five pages means five screens as opposed to 5-10 screens.

tiltowait · 01-10-2018, 08:41 PM

Quote:

Originally Posted by JSWolf

You cannot compare the kepub renderer to RMSDK on the nook.

You can if your goal is to show that only RMSDK has a particular behavior, which is what I was doing.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
B&N to release NOOK GlowLight 3	ZodWallop	News	479	02-02-2018 05:37 PM
Adding cover thumbnails to the Nook ST (Nook Color & Nook Glowlight): how-to	kalwisti	Barnes & Noble NOOK	0	10-31-2014 04:15 PM
Barnes & Noble One Week Sale on Nook STR, Glowlight, Nook HD	charmian	Deals and Resources (No Self-Promotion or Affiliate Links)	6	09-26-2013 10:36 AM
Brand New Nook Wifi $99 On Sale NOW at Best Buy website	sun surfer	Which one should I buy?	10	11-27-2010 06:27 PM

01-10-2018, 12:58 PM	#126
ZodWallop Gentleman and scholar Posts: 10,994 Karma: 108312789 Join Date: Jun 2015 Location: Space City, Texas Device: Clara HD; Nook ST w/Glowlight, (2015) Glowlight Plus, Paperwhite 3	I tested the book, but am not sure what I was supposed to see. Here are two pics, one justified and one left at auto.

Advert

Advert