Quote:
Originally Posted by ashkulz
Nick/Michael: have either of you figured out enough of the .IMP format so that you can write an image-only IMP [no text at all] so that I can incorporate it into pdfread? That way there'd be no dependency on eBook Publisher....
|
Yeah, still trying to get there...
A minimal list of .RES filetypes that are used (when using solely images as ebook pages) and what they do is presented below:
Code:
Filetype: (DATA.FRK text with control codes for images)
Filetype:!!sw (Standard coding can be obtained from sample .imp build)
Filetype:AncT (optional - if want to be able to link to images from TOC)
Filetype:AnTg (optional - if want to be able to link to images from TOC)
Filetype:BGcl (default = FFFFFF [white])
Filetype:BPgZ (actual ebook screen - the HARD one!!!!)
Filetype:BPgz (actual ebook screen - the HARD one!!!!)
Filetype:Devm (default = 01)
Filetype:ESts (use default x-sbp-widow-push and x-sbp-orphan-pull)
Filetype:ImRn (list of images stored with particulars and assigned Image ID)
Filetype:Mrgn (default, not used)
Filetype:PcZ0 (holds actual picture sizes to display on ebook screen)
Filetype:Pcz0 (holds actual picture sizes to display on ebook screen)
Filetype:pInf (compute last page number/image resources count info)
Filetype:GIF (repack list of images)
Filetype:JPEG (repack list of images)
Filetype:PNG (repack list of images)
Filetype:PPic (summary of number of images and borders used)
Filetype:StRn (optional - if want styles for headings and such)
Filetype:Styl (optional - if want styles for headings and such)
The above remaining filetypes to reverse-engineer are few, if any. The creation/combination of the pieces into a .IMP without using the eBook Publisher /dll's should be trival afterwards.
Close but just not there yet...
