Thread: JBPatch
View Single Post
Old 08-01-2012, 02:10 PM   #389
eureka
but forgot what it's like
eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.
 
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
@ixtab, .azw3 (as NiLuJe said) is a dual .mobi with KF8 content included. On KT, Java UI for viewing KF8-formatted content recieves from rendering process BMP image with some metadata (AFAIR, raw text and locations of words on screen for selecting/translating purposes). Rendering process is the webreader (/usr/bin/webreader) process. As KF8 format is a "restricted" HTML5-like format, webreader renders it with the help of WebKit engine and sends rendered image to Java UI.

webreader could be controlled through HTTP requests (it listens on 127.0.0.1:20450, you could find simple debug page by making HTTP request to it and control commands are represented as various URL-paths with query strings). But I believe, it's impossible to intercept rendering process without binary patch to webreader (I could be wrong, though).
eureka is offline   Reply With Quote