Advanced Mobipocket Features - Page 2

Nate the great · 04-03-2009, 12:27 AM

Quote:

Originally Posted by HarryT

This is not a bug. Not all versions of Mobi support all features. Suggest you test your file on Windows Desktop version of Mobi - that implements all features of the format.

I decided to answer this a second time so i could explain and expand on my previous post.

Bookeen says that the Cybook supports Mobipocket. They did not add any caveats saying that the Cybook only provided partial Mobipocket support.

I understand why this feature isn't supported, but that isn't the point. Without a statement from Bookeen concerning the limitations of Mobipocket support, any part of the spec not supported is by definition a bug.

Jellby · 04-03-2009, 07:57 AM

Quote:

Originally Posted by Nate the great

Without a statement from Bookeen concerning the limitations of Mobipocket support, any part of the spec not supported is by definition a bug.

Unless it is marked as "optional" in the spec. Since there is actually no spec, a note saying "not supported by all platforms" is as close as "optional" as you can find.

Nate the great · 04-03-2009, 08:10 AM

Quote:

Originally Posted by Jellby

Unless it is marked as "optional" in the spec. Since there is actually no spec, a note saying "not supported by all platforms" is as close as "optional" as you can find.

True, except Bookeen has never linked to the spec. Even if they had, I wouldn't expect most users to be able to understand it. That's why I keep saying that Bookeen needs to state what is and is not supported.

=X= · 04-03-2009, 10:33 AM

Well even though you didn't ask for feedback from. Blackberry users
I can tell you the file works great on my storm.
=X=

Nate the great · 04-03-2009, 10:44 AM

Quote:

Originally Posted by =X=

Well even though you didn't ask for feedback from. Blackberry users
I can tell you the file works great on my storm.
=X=

Thank you. I forgot to ask.

ProfJulie · 04-03-2009, 11:17 AM

Quote:

Originally Posted by Nate the great

True, except Bookeen has never linked to the spec. Even if they had, I wouldn't expect most users to be able to understand it. That's why I keep saying that Bookeen needs to state what is and is not supported.

I agree with you in principle, but Bookeen is about as hard to pin down or commit to anything as trying to grab a greased pig! We are just hoping for their promised Firmware in this century and that it provides some of the enhancements we've all be waiting and waiting for (and Bookeen has confirmed will be available sometime in the future). I will wait until this Firmware materializes before I start sending emails to Bookeen for even more functionality.

HarryT · 04-03-2009, 11:24 AM

My understanding is that there are two distinct "code bases" for the MobiPocket Reader - a C++ implementation, which is "full featured", and which runs on Windows desktop, Pocket PC, and perhaps a few other platforms, and a more portable Java implementation which is used on all the eInk devices; this Java version lacks the "advanced" features of the format. Even though the CyBook does not run Java directly, it is my understanding that its version of the Mobi Reader is essentially a machine translation of the Java into C or C++ for the device.

wallcraft · 04-03-2009, 11:42 AM

Quote:

Originally Posted by HarryT

My understanding is that there are two distinct "code bases" for the MobiPocket Reader.

Yes, see post #5 for a link to the feature list of the C++ and Java versions. However, the BlackBerry is running the Java version and it works in this case.

=X= · 04-03-2009, 12:14 PM

Quote:

Originally Posted by HarryT

My understanding is that there are two distinct "code bases" for the MobiPocket Reader - a C++ implementation, which is "full featured", and which runs on Windows desktop, Pocket PC

The fact that both the Desktop and MS Reader are C++, I think that is more incidental than design, they might share some code base but not much form the GUI standpoint. The PocketPC version is extremely tailored to the PocketPC GUI and fully maximizes/optimizes the reader for those devices. A good example of how all readers should design their UI.

Personally I think the feature limitation is due to vendor/hardware limitation. Many of these eBook readers have a limited input mechanism and probably a limited port of the java virtual machine. Where as the PocketPC and BlackBerry Java have much more capabilities.

=X=

wallcraft · 04-03-2009, 07:42 PM

Quote:

Originally Posted by Nate the great

I particularly want Iliad, V3 owners to tell me if any of these features work.

They don't work on the iLiad. On the "Scientific Articles" page, only the "Table of contents" is selectable with the stylus. In any article, all three links at the bottom fail to work (although there is a "back" icon that works).

On the EZ Reader (Hanlin V3) everything works except for search. So on the Keywords page, for example, there is no word search panel, but there is a list of keywords which is selectable.

tompe · 04-03-2009, 07:43 PM

Quote:

Originally Posted by wallcraft

On the EZ Reader (Hanlin V3) everything works except for search. So on the Keywords page, for example, there is no word search panel, but there is a list of keywords which is selectable.

So is this code based on MobiPocket's code and does this meant that it is not a limitation of the MobiPocket code we see in for example the Cybook?

wallcraft · 04-03-2009, 08:01 PM

Quote:

Originally Posted by tompe

So is this code based on MobiPocket's code and does this meant that it is not a limitation of the MobiPocket code we see in for example the Cybook?

Yes, this is MobiPocket's Java code. On the other hand, this might just be a side effect of how the Hanlin treats formal MOBI TOC's. It brings them up as numbered lists (8 items per page, selectable using keys 1-8), and this is what is happening in the index and article views (but not for Table of Contents, which seems to be an internal TOC that works like any list of HTML links).

DaleDe · 04-03-2009, 08:49 PM

Please check the wiki https://wiki.mobileread.com/wiki/Mobi_Comparison for a chart of what is supported on what platforms. Please add to it or fix anything that is wrong.

Dale

Nate the great · 04-03-2009, 08:49 PM

Quote:

Originally Posted by tompe

So is this code based on MobiPocket's code and does this meant that it is not a limitation of the MobiPocket code we see in for example the Cybook?

The difference is probably that the Cybook uses the older Java code, and the V3 and Blackberry use the newer one. If you follow the link in post 5, you'll see the 2 different categories.

pshrynk · 04-04-2009, 09:58 AM

Okay, I downloaded it to my K2 and it seems to work. the TOC has a link that it goes to. the Lookup links don't seem to go anywhere, there is no little pointy finger.

TOC links on I. Definitions which goes to a page with just "Definitions" at the top.
Algebraic Number goes to a page that has a definition of an AN. The links below it don't have a pointy finger. In fact it's the same with all the other linkys.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Advanced ebook formatting tips	Nate the great	Workshop	46	03-30-2012 08:54 PM
PRS-505 Advanced customization	surquizu	Sony Reader Dev Corner	1	12-13-2009 06:32 PM
Create your own advanced stylus	adi	iRex	6	07-26-2009 04:45 AM
Advanced options for PDF files	npavkovic	Sony Reader Dev Corner	5	02-22-2008 12:53 AM
Advanced Linux Programming	Alexander Turcic	Deals and Resources (No Self-Promotion or Affiliate Links)	0	03-28-2003 01:20 PM

04-03-2009, 10:33 AM	#19
=X= Wizard Posts: 3,671 Karma: 12205348 Join Date: Mar 2008 Device: Galaxy S, Nook w/CM7	Well even though you didn't ask for feedback from. Blackberry users I can tell you the file works great on my storm. =X=

04-03-2009, 11:24 AM	#22
HarryT eBook Enthusiast Posts: 85,544 Karma: 93383099 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	My understanding is that there are two distinct "code bases" for the MobiPocket Reader - a C++ implementation, which is "full featured", and which runs on Windows desktop, Pocket PC, and perhaps a few other platforms, and a more portable Java implementation which is used on all the eInk devices; this Java version lacks the "advanced" features of the format. Even though the CyBook does not run Java directly, it is my understanding that its version of the Mobi Reader is essentially a machine translation of the Java into C or C++ for the device.

04-03-2009, 08:49 PM	#28
DaleDe Grand Sorcerer Posts: 11,470 Karma: 13095790 Join Date: Aug 2007 Location: Grass Valley, CA Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7	Please check the wiki https://wiki.mobileread.com/wiki/Mobi_Comparison for a chart of what is supported on what platforms. Please add to it or fix anything that is wrong. Dale

04-04-2009, 09:58 AM	#30
pshrynk Beepbeep n beebeep, yeah! Posts: 11,726 Karma: 8255450 Join Date: Apr 2008 Location: La Crosse, Wisconsin, aka America's IceBox Device: iThingie, KmkII, I miss Zelda!	Okay, I downloaded it to my K2 and it seems to work. the TOC has a link that it goes to. the Lookup links don't seem to go anywhere, there is no little pointy finger. TOC links on I. Definitions which goes to a page with just "Definitions" at the top. Algebraic Number goes to a page that has a definition of an AN. The links below it don't have a pointy finger. In fact it's the same with all the other linkys.

Advert

Advert