Thread: Ebookwise 1150
View Single Post
Old 01-16-2009, 06:24 PM   #34
Roberts324
Mad translator
Roberts324 will become famous soon enoughRoberts324 will become famous soon enoughRoberts324 will become famous soon enoughRoberts324 will become famous soon enoughRoberts324 will become famous soon enoughRoberts324 will become famous soon enough
 
Roberts324's Avatar
 
Posts: 99
Karma: 684
Join Date: Jan 2008
Location: Gradignan près Bordeaux, France
Device: eBookwise 1150 reader, Samsung E60 reader, SAMSUNG N150 netbook
Quote:
Originally Posted by nrapallo View Post
The main hinderance to reverse engineering the dictionary format is that the data is encrypted, so it may not be easy to understand what that new HKEY filetype (I think it's a index of sorts) really does. I haven't got very far with this examination yet and unfortunately there is only ONE default "lookup" dictionary to look at for guidance (on how it works). It's not easy seeing a pattern when you only have one example to look at.

It's an uphill battle, and sure, ETI could help by publishing info how to do this or even better, publishing the .IMP file format!
I had contacted those people by mail about creating "running headers" (something you do, but BD does not unless I missed something), and they had given me an answer. You may ask them the necessary information.

Quote:
I've already started to get the .IMP file format properly document (see IMP) and that "journey" will help understand how to get another dictionary used as the default "lookup" dictionary.
I'll give a look at that; are the calls to the EBook Publisher DLLs documented? I oce was a specialist at writing import units for Delphi.
Roberts324 is offline   Reply With Quote