Adobe Digital Editions 1.8 preview now available

[Jim Lester]

Originally Posted by charleski

1.8 still doesn't support IDPF Font-mangling, only the 16bit Adobe version. This continued split in the standard is a seriously bad idea and needs to be fixed.

It does but I see from the Adobe Labs forums thst Mike told you that already

[charleski]

Yeah, that's a bit embarrassing, it turns out I was tripping over a bug in the tool I was using to mangle them without realising it.

One nice thing I found is that 1.8 also supports automatic ligature substitution. It will be very nice to see this making its way into readers.

[JSWolf]

I am hoping the next Sony Readers will be using the latest ADE.

[EowynCarter]

Originally Posted by Hellmark

That's really common anymore. I guess they figure that so much needs .net, that you'd already have it. Part of why I like Linux, I can quickly find exactly what is needed for any app I install.

Speaking of linux, has anyone been successful in getting the preview to run ?

[nose-in-a-book]

anything else besides ade available to do the same thing - esp library books. overdrive/mobipocket apps from library require adobe de to work so computer full of applications wasting space, and ade not even user friendly to mature eyes.

does beta have bigger fonts? the regular version is awful. is the background something other than black? we would like to be able to view it without magnifying glasses... also would be nice if they abandoned the flash gunk --though given its adobe its unlikely. no end of security issues. what a pain to sandbox ade/ overdrive/ etc.

[tomsem]

Originally Posted by Jim Lester

I didn't check but I'm pretty sure I left the space in. IIRC spaces are auto removed during the hash computation.

I seem to be having a problem with this: my B&N user name has a space in it and I can't unlock with ADE 1.8 Preview or Mantano Reader (Android). However Bluefire Reader (iOS) will open the same ePub without prompting (because it remembered from opening a previous B&N book some months ago). While Bluefire updated its RMSDK recently, it was working before that as well.

I haven't changed the user name or CC# of my B&N account, ever. Is there some 'trick' to getting it to work? Should I try removing the space from my B&N user name, downloading the book(s) again, etc.?

Thanks

[Jim Lester]

Originally Posted by tomsem

I seem to be having a problem with this: my B&N user name has a space in it and I can't unlock with ADE 1.8 Preview or Mantano Reader (Android).

Make sure you are using your name (as you gave it for the billing address for the CC#), and not your user name (email address). For instance I put in "Jim Lester" not "Jim.Lester@dev.null".

[Ken Maltby]

Originally Posted by tomsem

I seem to be having a problem with this: my B&N user name has a space in it and I can't unlock with ADE 1.8 Preview or Mantano Reader (Android). However Bluefire Reader (iOS) will open the same ePub without prompting (because it remembered from opening a previous B&N book some months ago). While Bluefire updated its RMSDK recently, it was working before that as well.

I haven't changed the user name or CC# of my B&N account, ever. Is there some 'trick' to getting it to work? Should I try removing the space from my B&N user name, downloading the book(s) again, etc.?

Thanks

I would try it with the space removed and everything else the same.
If it was John Doe then enter JohnDoe not Johndoe or johndoe.

That is what you have to do with the implementation of the Adobe Reader
Mobile Version 9.1.1 on my Jetbook Lite, for the B&N DRM.

While I expect that it is correct that the hash process ignores the space,
or any other non-alphanumeric characters, it appears that in some
implementations at least, the data is being rejected if the space is there.

Luck;
Ken

[tomsem]

Yes I did try dropping the space, and yes, I am using my B&N "Name" and not my email address (though I tried that also). No go. I don't remember what I did to get it working with Bluefire - don't think it was any different than what I've been trying with ADE & Mantano...

Unfortunately I can't change my B&N account 'Name' so that it has no spaces: it insists on both a First and Last name and puts a space in between.

Surely someone tested this capability in ADE at least?

Anyway it is a little frustrating because I 'know' this is supposed to work...

[ATimson]

It's the name on the credit card, not the account name... And if you change the name on the card, you need to redownload the book for it to take effect.

[tomsem]

Okay, I finally figured it out, and it even makes sense: use the name on the credit card, not the B&N account. These might be the same for many people, but in this case, it was 'Tom' vs 'Thomas'.

[loyukfai]

FWIW, the engine used in 1.8 supports JPEG2000 images properly.

Hopefully Adobe will finish it for official release soon.

Cheers.

[JSWolf]

Originally Posted by loyukfai

FWIW, the engine used in 1.8 supports JPEG2000 images properly.

Hopefully Adobe will finish it for official release soon.

Cheers.

Doesn't matter. Most readers will not be using this version of ADE and the only way to keep compatible is not to use any new features. So really, you'll be causing an issue by using features that don't work with ADE 1.7.2.

[ATimson]

Originally Posted by JSWolf

Doesn't matter. Most readers will not be using this version of ADE and the only way to keep compatible is not to use any new features. So really, you'll be causing an issue by using features that don't work with ADE 1.7.2.

Since JPEG 2000 isn't defined as a OPS Core Media Type, ebook authors who use JPEG 2000-formatted images need to be including a fallback to have a valid book. If they don't, then they don't care about having a valid ePub, and are probably a lost cause who don't care about being incompatible with some devices.

[Hellmark]

Originally Posted by ATimson

Since JPEG 2000 isn't defined as a OPS Core Media Type, ebook authors who use JPEG 2000-formatted images need to be including a fallback to have a valid book. If they don't, then they don't care about having a valid ePub, and are probably a lost cause who don't care about being incompatible with some devices.

Plus who really uses JPEG 2000? It's been around for years, and NEVER gained any acceptance.

Also, isn't JPEG 2000 more CPU hungry? I mean, many ebook readers don't have much horsepower to begin with, so why use something that wants a decent amount of resources.