spaces lost during converting to fb2 format

[n1ch0las]

Hello, i dont know if this would count as a bug or has been posted here before ( i did do a search but couldn't find anything)

i have some properly formatted standard .txt files with nice spaces in between all of the appropriate lines

Kind of like this:-

chapter one

John sat on the chair.

Elsewhere joan was standing.


When i convert the files to fb2 format it removes the spaces between the lines:-

chapter one
John sat on the chair.
Elsewhere joan was standing.

i am using the latest version of calibre and have tried using all of the options on and off during conversion, if i convert to epub then the lines stay in the right places, but if i then convert the epub files to fb2 format it removes the lines.

Not sure why it is doing this but i really wanted to use fb2 format as it gives more accurate page numbers than epub

Help!

[user_none]

Open a ticket (So I don't forget) for FB2 to support the "Insert Blank Line" option and I will implement this functionality.

[ldolse]

You just opened a bug on this, but the description here and the description in the bug tracker are different.

Did you enable the 'treat each line as a paragraph' option before you converted it?

edit:
There is also an 'insert blank line' option under look and feel that might do what you want as well.

[user_none]

@ldolse, I recently rewrote the FB2 output code. It's basic at this moment and does not currently support everything it used to. I plan to add support for the 'treat each line as a paragraph' option over the next few days.

[ldolse]

Cool, not sure I completely understand how that's even possible but I'll leave it to you

[DoctorOhh]

Originally Posted by n1ch0las

use fb2 format as it gives more accurate page numbers than epub

I'm curious, how do you perceive one format having more accurate page numbers over another? Compared to what?

[Zetmolm]

I also prefer the fb2 page numbering. On a 6" reader, one page in fb2 more or less corresponds to one screen (depending on font size of course), whereas one page in ePub may be 2-3 screens. So in that sense fb2 page numbering is more 'accurate'.

[n1ch0las]

Originally Posted by dwanthny

I'm curious, how do you perceive one format having more accurate page numbers over another? Compared to what?

When reading a mobi formatted book or an epub, page numbers are not accurate, the amount of page numbers may be 1119, when the book may stop at 950 or so, which was starting to annoy me, ( i think its an estimate by the book based on content when opening) with the fb2 format though the layout of the page is much nicer ( numbers and title at the top) and the page numbers are completely accurate.

And i have tried every option on and off methodically when converting books, the insert line and each line as a paragraph function were both tested

[itimpi]

The count of total pages being wrong when reading a book means there is a fault in the reading software I would think. Certainly on my devices the count is accurate, and if I dynamically change the font size I am using both the value for the current page and the total number of pages change accordingly.

[ldolse]

Adobe DE based epub engines do something weird with page calculation. They create some sort of canonical version of a 'page' when the file is opened and stick with that page count no matter how you change the display. Depending on the font size you're using you could page across several user perceived pages and the ADE engine will tell you you are still on the same original page number. It's weird and I just ignore it. I think this is what the users are complaining about.

[DoctorOhh]

Originally Posted by n1ch0las

When reading a mobi formatted book or an epub, page numbers are not accurate, the amount of page numbers may be 1119, when the book may stop at 950 or so, which was starting to annoy me

I have never run into that for epubs. The book *always* ends as predicated.

Originally Posted by n1ch0las

And i have tried every option on and off methodically when converting books, the insert line and each line as a paragraph function were both tested

Have you tried checking both settings at the same time? Also changing global conversion settings doesn't automatically translate to conversion setting being changed for books that had been previously converted, read this post and view attachments to it.

Originally Posted by ldolse

Adobe DE based epub engines do something weird with page calculation. They create some sort of canonical version of a 'page' when the file is opened and stick with that page count no matter how you change the display. Depending on the font size you're using you could page across several user perceived pages and the ADE engine will tell you you are still on the same original page number. It's weird and I just ignore it. I think this is what the users are complaining about.

I don't find this weird. No matter what font size you use page 124 is page 124. When the font size is larger you might need to page through 8-9 screens to get past one page. But the page doesn't change based on what font size you're using.

Basically, unless told other wise via a page map ADE creates page numbers by breaking up the data into chunks based on the following format.

From the EPUB Best Practices Guide found on Adobe's site here.

Synthetic page names
When page map is not available in the document, Adobe Digital Editions will synthesize a page-map based on the document content. The approach used is the following:

• Determine a compressed byte length of each resource which is referenced in the spine, subtracting any known encryption overhead (IV size)
• Assume that there is a page for each 1024 bytes in each resource, rounding up to the nearest whole number of pages for each resource
• To map page breaks into a resource, use the number of pages for the resource as determined in step 2, count the number of Unicode characters in the resource; distribute synthetic page breaks in the resource evenly between the characters by dividing the number of characters by the number of pages; if the number of characters don’t divide evenly among the pages, round the number of characters per page up and let the last “page” contain less characters than the rest.

I like having a relatively constant set of page numbers no matter what epub I'm reading or what font size I choose. Calibre's viewer does something similar.

[ldolse]

Originally Posted by dwanthny

I don't find this weird. No matter what font size you use page 124 is page 124. When the font size is larger you might need to page through 8-9 screens to get past one page. But the page doesn't change based on what font size you're using.

Basically, unless told other wise via a page map ADE creates page numbers by breaking up the data into chunks based on the following format.

I like having a relatively constant set of page numbers no matter what epub I'm reading or what font size I choose. Calibre's viewer does something similar.

There's nothing unreasonable about that, but I think most users (including myself) think of a page as what's visible to a user on a single page turn. It's a simpler concept to understand, even if it means the number of pages changes based on the font size.

I don't personally care either way though, and perhaps I'm putting words in the other guys' mouths.

[n1ch0las]

All i was saying was, that the reason i wanted to use fb2 as a format is that when you look at a book it will give you an accurate set of page numbers.
The epub and mobi formats used on my reader (bebook one 2010 edition) will say a book has 1150 pages when you start, when you are reading the page number will change with every page turn, but when you get to about 1000 pages in the book will end, it will go from page 999 to page 1150 on one turn and the book is finished.
It was a minor gripe with the way mobi and epub books are displayed and it was not the thrust of my original question, i only mentioned it as a reason for using fb2 as a format; which by the way, is a much better format on my reader, it has more options for changing the page layout, it keeps the time on the page and has a faster rendering time for page turns!

Since this thread started Calibre has been updated and has fixed the original problem with the formatting.

Thanks

[DoctorOhh]

Originally Posted by n1ch0las

The epub and mobi formats used on my reader (bebook one 2010 edition) will say a book has 1150 pages when you start, when you are reading the page number will change with every page turn, but when you get to about 1000 pages in the book will end, it will go from page 999 to page 1150 on one turn and the book is finished.

If my reader jumped like that I might search for a different format too. Epub on Sony's don't end abruptly like that. Maybe someday bebook will update the firmware to correct this.

Originally Posted by n1ch0las

Since this thread started Calibre has been updated and has fixed the original problem with the formatting.

I'm glad to here it's been corrected. Kudos to the developers.