The complexity of this port and the project that it originates from, is often underestimated. It has a number of components that have their own development history and continuing development. There are essentially two major rendering components one that is essentially a PDF renderer for some of the Kindle devices and the other being the cr3engine (CoolReader 3 rendering components) for most other formats. Not only must the project get the different rendering programs working in some imaginary base environment - but they are having to get it working on different hardware models from two different manufacturers. That we might see differing results for use on different models and when rendering different formats, should come as no surprise. That it works as well as it does, is amazing. The development continues and issues are being addressed.
I don't like using fixed page PDF documents on a small screen, so PDFs are not an issue for me on my AuraHD. The recent builds have brought Koreader to a usable level for the files that I use, with only some minor failings, mostly cosmetic. This is for my AuraHD, judging by posts here there may be more problems for some of the other models. Some of the "failings" are probably user related. (I only had Go To Page working on the version that Giorgio had to pull, and not at all since.)
I am sure, with the intrest there is in PDF rendering for both the Kindle and Kobo versions, that any issues will be addressed in a timely manner.
Luck;
Ken
|