BookDesigner Quirk

maggotb0y · 10-25-2008, 09:54 PM

Haven't seen any updates to BookDesigner for quite a while, but I've noticed a bug, thought I'd post it here.

If a book has a chapter that takes up exactly one page, the next chapter is not defined as a chapter in the Table of Contents in the LRS file generated. If it would be helpful, I could create a test html0 file that would show this and post it, but it's fairly easy to reproduce with a few junk paragraphs and an HR.

Also, is development on BD dead at this point? If so, is there any hope that the source could be released so that the open source community could get their hands on the code?

Thanks,
-xopher

Strether · 10-25-2008, 10:16 PM

Can't speak for others, but I've noticed this problem for quite a while. I always go through and check chapter titles by hand and make necessary page breaks before making the toc. It only takes a minute unless your book is really large, and even then you have to do it.

Can't answer your other question, but I was looking at the Book Designer site the other day and noticed that vvv is still posting there and that Astra, who occasionally posts here, understands Russian so perhaps he could respond and tell us what he knows about what's going on.

Jim

HarryT · 10-26-2008, 04:22 AM

Quote:

Originally Posted by maggotb0y

If a book has a chapter that takes up exactly one page, the next chapter is not defined as a chapter in the Table of Contents in the LRS file generated. If it would be helpful, I could create a test html0 file that would show this and post it, but it's fairly easy to reproduce with a few junk paragraphs and an HR.

It's not a bug, as such; it happens if you have automatic page breaks enabled, because BD won't insert a page break if it considers the previous page to be too short.

You can avoid the problem by inserting a manual page break at the appropriate point.

maggotb0y · 10-27-2008, 10:12 AM

Sorry, should have probably mentioned that automatic page breaks are disabled, and the chapters have a manual page break at the appropriate point. The only way I've been able to get around it is by pausing the build process (not for the faint of heart) to manually fix the .LRS file, then letting the build proceed.
I'll try to put together a sample to post this evening.

HarryT · 10-27-2008, 10:15 AM

Have you got the "User page breaks" box checked?

Patricia · 10-27-2008, 10:16 AM

I find that inserting a manual page break will work. But it also helps to add some empty lines between the chapter title and the page break: I usually add about 15.
This works perfectly.

maggotb0y · 10-27-2008, 09:34 PM

AHA!
While poking around in the options to make sure I knew what I was talking about, I discovered the "toc" option (set to short). I set it to long, and everything is good.

Also discovered the "long" dashes option, and I'm in type-A heaven!!!

Thanks for all the suggestions, which led me to the correct answer.

(Also, a note to an admin - if you would be so kind as to change the topic title from "BookDesigner bug" to "BookDesigner quirk", I think that would be more appropriate.)

Patricia · 10-27-2008, 11:05 PM

Thread title amended, as you requested.

JSWolf · 10-28-2008, 10:57 AM

Quote:

Originally Posted by maggotb0y

[B]AHAAlso discovered the "long" dashes option, and I'm in type-A heaven!!!

Actually, using the long dash option ruins the books. What you should do (IMHO) is it go to the Book Cleaner thread and install the Book Cleaner files. That way you will have proper emdashes and other assorted fixes applied as you load in the book.

https://www.mobileread.com/forums/showthread.php?t=11649

maggotb0y · 10-28-2008, 09:01 PM

Quote:

Originally Posted by JSWolf

Actually, using the long dash option ruins the books. What you should do (IMHO) is it go to the Book Cleaner thread and install the Book Cleaner files. That way you will have proper emdashes and other assorted fixes applied as you load in the book.

Well, I've been doing that for quite a while, but based on your comments, I've dug a little deeper into how this works, and have come to realize that "as it is" is the correct setting for me (to the point that I wonder why there are other options). So to assist everyone else considering dash options and rendering, I'll do my best to explain how things work.

First, I'll say that using the BookCleaner files linked above may have absolutely no affect on your generated LRF file, depending on what your "dashes" options on the "Make Sony Reader file options" page are set to. I've been using the BookCleaner files for a very long time, with no impact on my LRF files because of the way my BookDesigner settings files were configured.

Here is a quick explanation of the options:

"as it is" (recommended for type a personalities) - emdashes are rendered as long, and hyphens are rendered as short no matter where they appear in a line
short dashes- emdashes and hyphens are rendered as hyphens regardless of spacing/line position
middle dashes - hyphens and emdashes are rendered as short unless they are surrounded by spaces or at the beginning of a line, in which they are a little bit longer
long dashes - hyphens and emdashes are rendered as short unless they are surrounded by spaces or at the beginning of a line, in which they are rendered as emdashes

It makes more sense if you see it in action, so I've attached samples of the same document, rendered with the various settings.

JSWolf · 10-29-2008, 04:08 AM

I just stick with "as it is" so I have the dashes and emdashes as they are meant to be. The Book Cleaner files make sure the emdahses are properly kept. The Book Cleaner files do fix some things on load that otherwise would be incorrect. When I read something that I know is supposed to have emdashes but the dashes have been converted incorrectly, it does bug me.

10-25-2008, 09:54 PM	#1
maggotb0y Connoisseur Posts: 84 Karma: 1166 Join Date: Apr 2007 Location: New Jersey, Outside of Philadelphia Device: Sony Reader	BookDesigner Quirk Haven't seen any updates to BookDesigner for quite a while, but I've noticed a bug, thought I'd post it here. If a book has a chapter that takes up exactly one page, the next chapter is not defined as a chapter in the Table of Contents in the LRS file generated. If it would be helpful, I could create a test html0 file that would show this and post it, but it's fairly easy to reproduce with a few junk paragraphs and an HR. Also, is development on BD dead at this point? If so, is there any hope that the source could be released so that the open source community could get their hands on the code? Thanks, -xopher

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Curious Quirk- Cursed epub or bug?	p_a_smith	Kobo Reader	4	09-15-2010 12:02 AM
epub covers quirk? with 0.7.2	Allis	Calibre	4	06-24-2010 08:22 PM
Quirk Books to release Tolstoy's "Android Karenina"	Nate the great	News	87	01-17-2010 03:29 PM
PRS-600 Strange quirk with PRS-600	HarryT	Sony Reader	2	10-14-2009 10:05 AM
BookDesigner	SirWesley	Software	4	05-20-2009 06:08 AM

10-25-2008, 10:16 PM	#2
Strether Guru Posts: 760 Karma: 2825929 Join Date: Feb 2007 Location: Fresno Device: Kindle 1; iPad Air; iPhone 7; Kobo Libra; Kindle Oasis 3	Can't speak for others, but I've noticed this problem for quite a while. I always go through and check chapter titles by hand and make necessary page breaks before making the toc. It only takes a minute unless your book is really large, and even then you have to do it. Can't answer your other question, but I was looking at the Book Designer site the other day and noticed that vvv is still posting there and that Astra, who occasionally posts here, understands Russian so perhaps he could respond and tell us what he knows about what's going on. Jim

10-27-2008, 10:12 AM	#4
maggotb0y Connoisseur Posts: 84 Karma: 1166 Join Date: Apr 2007 Location: New Jersey, Outside of Philadelphia Device: Sony Reader	Sorry, should have probably mentioned that automatic page breaks are disabled, and the chapters have a manual page break at the appropriate point. The only way I've been able to get around it is by pausing the build process (not for the faint of heart) to manually fix the .LRS file, then letting the build proceed. I'll try to put together a sample to post this evening.

10-27-2008, 10:15 AM	#5
HarryT eBook Enthusiast Posts: 85,544 Karma: 93383043 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	Have you got the "User page breaks" box checked?

10-27-2008, 10:16 AM	#6
Patricia Reader Posts: 11,504 Karma: 8720163 Join Date: May 2007 Location: South Wales, UK Device: Sony PRS-500, PRS-505, Asus EEEpc 4G	I find that inserting a manual page break will work. But it also helps to add some empty lines between the chapter title and the page break: I usually add about 15. This works perfectly.

10-27-2008, 09:34 PM	#7
maggotb0y Connoisseur Posts: 84 Karma: 1166 Join Date: Apr 2007 Location: New Jersey, Outside of Philadelphia Device: Sony Reader	AHA! While poking around in the options to make sure I knew what I was talking about, I discovered the "toc" option (set to short). I set it to long, and everything is good. Also discovered the "long" dashes option, and I'm in type-A heaven!!! Thanks for all the suggestions, which led me to the correct answer. (Also, a note to an admin - if you would be so kind as to change the topic title from "BookDesigner bug" to "BookDesigner quirk", I think that would be more appropriate.)

10-27-2008, 11:05 PM	#8
Patricia Reader Posts: 11,504 Karma: 8720163 Join Date: May 2007 Location: South Wales, UK Device: Sony PRS-500, PRS-505, Asus EEEpc 4G	Thread title amended, as you requested.

10-29-2008, 04:08 AM	#11
JSWolf Resident Curmudgeon Posts: 75,860 Karma: 134368292 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	I just stick with "as it is" so I have the dashes and emdashes as they are meant to be. The Book Cleaner files make sure the emdahses are properly kept. The Book Cleaner files do fix some things on load that otherwise would be incorrect. When I read something that I know is supposed to have emdashes but the dashes have been converted incorrectly, it does bug me.

Advert

Advert