MobileRead exclusive : sneak preview of the Bookeen Opus

[zelda_pinwheel]

Originally Posted by Crusader

Some people have all the luck.

I guess I'll just have to keep myself busy reading some actual books in the meantime...

i know...

by the way, watch this space, a little bird told me that tomorrow clément will put some videos on line as well ! (then i *really* don't know how you will be able to wait. )

[tompe]

Originally Posted by zelda_pinwheel

it's a restriction from Mobipocket / Amazon, Bookeen can't do anything about it sadly.

Are you sure. What can prevent them from porting FBReader and use that? Since they are not using any MobiPocket programs I do not get what hinders them.

[zelda_pinwheel]

Originally Posted by tompe

Are you sure. What can prevent them from porting FBReader and use that? Since they are not using any MobiPocket programs I do not get what hinders them.

that i do not know, you would have to ask bookeen directly. i am repeating what i read about the question over here :

Originally Posted by Godzil

Like someone say before, Bookeen is the only (with iRex) device that is able to read DRMed PRC, and for this they NEED to use the Mobipocket SDK. To use the Mobipocket SDK, you can't put OTHER DRM support, and they can't use this SDK without the DRM support the Mobipocket contract disallow them. To support ePub/PDF with Adept DRM, Bookeen need to use the Adobe SDK, and the Adobe contract does not allow them to use the SDK WITHOUT the DRM.

So if Bookeen want to support PRC withtout DRM, they will need to develop a new PRC reader, and that the same for ePub without DRM.


Until Mobipocket/Amazon forbid the use of multiple DRM on the same device, from a legal point of view Bookeen will never be able to release a firmware with both DRM, and I doubt they have time to develop something that will double their development time/debugging etc...

[tompe]

Originally Posted by zelda_pinwheel

that i do not know, you would have to ask bookeen directly. i am repeating what i read about the question over here :

Yes, but that post says they cannot use the MobiPocket SDK at the same time as the Adobe SDK. But FBReader does not use the MobiPocket SDK. I suppose there might be other strange contractual reasons but there do not seem to be any obvious reasons.

[zelda_pinwheel]

Originally Posted by tompe

Yes, but that post says they cannot use the MobiPocket SDK at the same time as the Adobe SDK. But FBReader does not use the MobiPocket SDK. I suppose there might be other strange contractual reasons but there do not seem to be any obvious reasons.

that's a question for bookeen, i really don't know.

[DaleDe]

Originally Posted by tompe

Yes, but that post says they cannot use the MobiPocket SDK at the same time as the Adobe SDK. But FBReader does not use the MobiPocket SDK. I suppose there might be other strange contractual reasons but there do not seem to be any obvious reasons.

The most obvious reason is that Bookeen has their own reader and software. They have a single look and feel. To use FBReader would not allow that as it is a separate program with its own look and feel so they would have to rewrite the manual and the ease of use would be less. Perhaps they could write their own mobi parser but that would be a large task.

Dale

[Crusader]

Originally Posted by zelda_pinwheel

i know...

by the way, watch this space, a little bird told me that tomorrow clément will put some videos on line as well ! (then i *really* don't know how you will be able to wait. )

Guess I'll have to avoid Mobileread then... or try to ignore the urge to watch the videos.

[zelda_pinwheel]

Originally Posted by Crusader

Guess I'll have to avoid Mobileread then... or try to ignore the urge to watch the videos.

yeah. good luck with that.

[tompe]

Originally Posted by DaleDe

The most obvious reason is that Bookeen has their own reader and software. They have a single look and feel. To use FBReader would not allow that as it is a separate program with its own look and feel so they would have to rewrite the manual and the ease of use would be less. Perhaps they could write their own mobi parser but that would be a large task.

Of course there are more or less possible obvious reasons why they do not want to do it. My statement was about reason why they cannot do it.

But I thought FBReader could just be plugged in and uses as an reader from the launcher. And most of the look and feel is in the launcher.

[rlparker]

Originally Posted by zelda_pinwheel

...
(then i *really* don't know how you will be able to wait. )
...

bwahaha, you have a kinda mean streak dontcha?

[zelda_pinwheel]

Originally Posted by rlparker

bwahaha, you have a kinda mean streak dontcha?

well, if it makes it any better, i have to wait too.

[junkyardwillie]

But FBreader doesnt support DRM Mobipocket right? So even if you put FBreader on there you could get support for MobiPocket but would need to jailbreak your DRM files to view them.

I would still rather they support Adobe DE over Mobipocket, I have devices that support Mobipocket but I need something for Adobe DE and this could make a good choice.

[Hadrien]

The Cybook Opus uses a new version of the Reader SDK: unlike the Sony Reader it can properly display justified text. Too bad that Sony isn't releasing a firmware update...

[kacir]

Originally Posted by Godzil

They are in fact 166dpi to be exact. Sony advertise 170dpi, but it's false

Aehm ...
Math was not you favourite subject, was it?

Sony (Kindle 1 and 2, cybook, ...) has 6 inch screen with 800x600 pixels
new Opus has 5 inch screen with 800x600 pixels resolution.

let's do a little bit of math here:
5 inch diagonal 800x600 screen makes classical pythagorian triangle 3,4,5
let's check it:
3^2 + 4^2 = 5^2
9 + 16 = 25

OK. we have established that 5 inch screen has dimensions exactly 3 x 4 inches.

Now, bear with me
800 pixels / 4 inches is ...
TADAAAAAA
200 pixels per inch. *Exactly* 200 pixels per inch.

[zelda_pinwheel]

Originally Posted by kacir

Aehm ...
Math was not you favourite subject, was it?

Sony (Kindle 1 and 2, cybook, ...) has 6 inch screen with 800x600 pixels
new Opus has 5 inch screen with 800x600 pixels resolution.

let's do a little bit of math here:
5 inch diagonal 800x600 screen makes classical pythagorian triangle 3,4,5
let's check it:
3^2 + 4^2 = 5^2
9 + 16 = 25

OK. we have established that 5 inch screen has dimensions exactly 3 x 4 inches.

Now, bear with me
800 pixels / 4 inches is ...
TADAAAAAA
200 pixels per inch. *Exactly* 200 pixels per inch.

i believe godzil was referring to the 6" screen. the 5" screen does indeed have 200ppi.