View Single Post
Old 03-02-2010, 08:39 AM   #124
Mr. Goodbar
Wizard
Mr. Goodbar makes omelettes without breaking eggs.Mr. Goodbar makes omelettes without breaking eggs.Mr. Goodbar makes omelettes without breaking eggs.Mr. Goodbar makes omelettes without breaking eggs.Mr. Goodbar makes omelettes without breaking eggs.Mr. Goodbar makes omelettes without breaking eggs.Mr. Goodbar makes omelettes without breaking eggs.Mr. Goodbar makes omelettes without breaking eggs.Mr. Goodbar makes omelettes without breaking eggs.Mr. Goodbar makes omelettes without breaking eggs.Mr. Goodbar makes omelettes without breaking eggs.
 
Posts: 1,005
Karma: 98078
Join Date: Jul 2006
Location: Atlanta, GA
Device: iPad Mini 4
Quote:
Originally Posted by Matthijs View Post
The problem with dictionary support is the availability of dictionaries. In the Mobipocket days, dictionary support was part of the Mobi document format and it was possible for publishers to create a dictionary, protect it with DRM and sell it to end-users. End-users could then use these transparently, this was built into the Mobi SDK.

In the Adobe RMSDK, there is no support for dictionaries, so any dictionary support will have to be 'home-brew' and/or relying on open source dictionary software like e.g. StarDict. This reduces availability of dictionaries a lot.

We were initially planning for Online Lookup functionality in the DR800SG (using Wikipedia, Google, ...) but that went into the freezer for several reasons: technical, planning and business.
I would look at the Sony and Kindle model for how to do a dictionary. I realize there might be incremental cost associated with this, but I would even be interested in paying for this feature. Set it up as a paid for upgrade if necessary. It would seem the coding would be relatively straightforward and content costs couldn't be above a few dollars per device. Charge ten to twenty dollars for the upgrade and bring your device to feature parity with your main competitors.
Mr. Goodbar is offline   Reply With Quote