Source format? - Page 2

HarryT · 03-12-2012, 02:04 PM

That is your viewpoint; mine differs.

JSWolf · 03-12-2012, 09:50 PM

Quote:

Originally Posted by HarryT

That is your viewpoint; mine differs.

So you enjoy editing the source used for generating the Mobi, generating the Mobi, then generating the ePub, editing the ePub to fix the formatting and then if an error is found, going back and doing it all again? WHY?

JimLL · 03-13-2012, 06:26 AM

Quote:

Originally Posted by JSWolf

So you enjoy editing the source used for generating the Mobi, generating the Mobi, then generating the ePub, editing the ePub to fix the formatting and then if an error is found, going back and doing it all again? WHY?

1. I have no such agenda. I make attempts to do something there is no instruction for. If I do it wrong, what rules have I broken. None, because there ARE NO rules given.

2. I'd much rather have a guide to take me through it right the first time.

What IS all this effort to defend and maintain the status quo?

JimLL · 03-13-2012, 06:35 AM

Quote:

Originally Posted by Shack70

Get the Send to Kindle app and Amazon will convert it. Select the free conversion and when on Wifi it will show on your Kindle.

I've had Send to Kindle for months. Amazon simply gives you back a long, formatted gob of text. No features. If I have a 700 page book I need features, even if it isn't for sale.

HarryT · 03-13-2012, 06:55 AM

Quote:

Originally Posted by JSWolf

So you enjoy editing the source used for generating the Mobi, generating the Mobi, then generating the ePub, editing the ePub to fix the formatting and then if an error is found, going back and doing it all again? WHY?

Because that's my preferred workflow. As I said, we all have our own way of working. Mine suits me; I'm happy that yours suits you.

HarryT · 03-13-2012, 06:56 AM

Quote:

Originally Posted by JimLL

1. I have no such agenda. I make attempts to do something there is no instruction for. If I do it wrong, what rules have I broken. None, because there ARE NO rules given.

2. I'd much rather have a guide to take me through it right the first time.

What IS all this effort to defend and maintain the status quo?

Jon was not talking to you, Jim. He was replying to me.

JSWolf · 03-13-2012, 03:55 PM

Does anyone know a way around the bug in Mobipocket that fails to go back to the screen page in view when you go to an endnote and then back using links?

HarryT · 03-13-2012, 04:28 PM

Mobi Reader is "stateless" - it does not maintain a parse tree in memory, as an ePub device does. When you follow a hyperlink, it starts rendering from the jump destination point onwards. The concept of jumping to a "screen page" is therefore meaningless in a Mobi book - all you can do is jump to a specific location in the text. However, given that every implementation of the Mobipocket Reader that I know of has a "back" facility for returning from a jump to an endnote (which DOES take you back to the page jumped from) it's an entirely moot point; there is no reason to use a link to return from an endnote in a Mobi book. Indeed, most Mobi books do not even HAVE back links.

But you know all this as well as I do - why try to pretend otherwise.? Is this simply the latest episode in your eternal anti-Amazon tirade, Jon?

osnova · 03-13-2012, 04:31 PM

Quote:

Originally Posted by HarryT

Because that's my preferred workflow. As I said, we all have our own way of working. Mine suits me; I'm happy that yours suits you.

My workflow also starts with sources for mobi. Once mobi is done, I modify the same source files for an epub.

JSWolf · 03-13-2012, 05:13 PM

Quote:

Originally Posted by HarryT

Mobi Reader is "stateless" - it does not maintain a parse tree in memory, as an ePub device does. When you follow a hyperlink, it starts rendering from the jump destination point onwards. The concept of jumping to a "screen page" is therefore meaningless in a Mobi book - all you can do is jump to a specific location in the text. However, given that every implementation of the Mobipocket Reader that I know of has a "back" facility for returning from a jump to an endnote (which DOES take you back to the page jumped from) it's an entirely moot point; there is no reason to use a link to return from an endnote in a Mobi book. Indeed, most Mobi books do not even HAVE back links.

But you know all this as well as I do - why try to pretend otherwise.? Is this simply the latest episode in your eternal anti-Amazon tirade, Jon?

All I was asking is if someone knows of a work around. I never mentioned Amazon. You did that. I know Mobipocket Reader has a back button that works. But as I've not tried all the different readers/software that support Mobipocket, I can't say how many have a back button./feature.

I do remember back in the early days when I a lot ePub that had endnotes did not have a link back because of the source they had not having such. But that seems to pretty much gone away with ePub these days.

HarryT · 03-13-2012, 05:19 PM

These days there's only one Mobipocket reader that people are going to encounter: the Kindle devices, and the various Kindle reading apps (PC, Mac, Android, iOS). They all have a "Back" facility.

You're being disingenuous in describing the Mobi jump behaviour as a bug. You know as well as I do that it's because Mobi is stateless. That's not a bug; it's simply a fact, and it's the book designer's responsibility to allow for it (eg by not putting jump destinations inside tags that change the text state).

JSWolf · 03-13-2012, 07:15 PM

Quote:

Originally Posted by HarryT

These days there's only one Mobipocket reader that people are going to encounter: the Kindle devices, and the various Kindle reading apps (PC, Mac, Android, iOS). They all have a "Back" facility.

You're being disingenuous in describing the Mobi jump behaviour as a bug. You know as well as I do that it's because Mobi is stateless. That's not a bug; it's simply a fact, and it's the book designer's responsibility to allow for it (eg by not putting jump destinations inside tags that change the text state).

Just because that's how it works does not mean it's not a bug and it is. It's the reason why page numbers are broken with Mobipocket Reader. Same bug.

jgaiser · 03-13-2012, 07:31 PM

Quote:

Originally Posted by JSWolf

Just because that's how it works does not mean it's not a bug and it is. It's the reason why page numbers are broken with Mobipocket Reader. Same bug.

I curious about how many mobi devices you own and why you are so concerned about mobi *bugs*. I've always thought you were an epub exclusive user.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
New source format .xz	SkyDream	Calibre	10	12-11-2011 07:26 PM
Tracking original / source format?	threejosh	Library Management	10	01-28-2011 08:47 PM
Missing Source Format	ehall71	Calibre	3	11-05-2010 09:47 PM
No Suitable Source Format...	amalgam12	Calibre	2	04-16-2010 05:07 AM
No Suitable Source Format Found	taildragger-j3	Calibre	3	01-14-2010 04:13 PM

03-12-2012, 02:04 PM	#16
HarryT eBook Enthusiast Posts: 85,560 Karma: 93980341 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	That is your viewpoint; mine differs.

03-13-2012, 03:55 PM	#22
JSWolf Resident Curmudgeon Posts: 80,718 Karma: 150249619 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Does anyone know a way around the bug in Mobipocket that fails to go back to the screen page in view when you go to an endnote and then back using links?

03-13-2012, 04:28 PM	#23
HarryT eBook Enthusiast Posts: 85,560 Karma: 93980341 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	Mobi Reader is "stateless" - it does not maintain a parse tree in memory, as an ePub device does. When you follow a hyperlink, it starts rendering from the jump destination point onwards. The concept of jumping to a "screen page" is therefore meaningless in a Mobi book - all you can do is jump to a specific location in the text. However, given that every implementation of the Mobipocket Reader that I know of has a "back" facility for returning from a jump to an endnote (which DOES take you back to the page jumped from) it's an entirely moot point; there is no reason to use a link to return from an endnote in a Mobi book. Indeed, most Mobi books do not even HAVE back links. But you know all this as well as I do - why try to pretend otherwise.? Is this simply the latest episode in your eternal anti-Amazon tirade, Jon?

03-13-2012, 05:19 PM	#26
HarryT eBook Enthusiast Posts: 85,560 Karma: 93980341 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	These days there's only one Mobipocket reader that people are going to encounter: the Kindle devices, and the various Kindle reading apps (PC, Mac, Android, iOS). They all have a "Back" facility. You're being disingenuous in describing the Mobi jump behaviour as a bug. You know as well as I do that it's because Mobi is stateless. That's not a bug; it's simply a fact, and it's the book designer's responsibility to allow for it (eg by not putting jump destinations inside tags that change the text state).