Thanks for all the feedback! I'll try to reply to most of it in this answer.
@diba, IcyVeins:
correct, of course. Hopefully, you didn't only realize it at the last line of text
. Karma to both of you, if only for the reason that all hope is not lost yet, as long as people still appreciate literature, and as long as not everybody has fallen victim to the private TV stations' mission to totally dumb down the people.
Quote:
Originally Posted by alaiksander
I think you should mention this on the hack's post.
 |
Well, it's already documented (albeit with slightly different wording) directly inside the configuration file, right before the relevant setting, and it's even prefixed with "IMPORTANT". How much more can I do?
Quote:
Originally Posted by alaiksander
Hmm..will there be support for arabic with your hack? currently it displays arabic but doesnt support RTL (on mobi/azw).
|
There won't be support for arabic with mobi/azw, because this file format inherently does not support RTL languages. It should work out of the box with KF8 (.azw3) files though, at least from what I read so far. Just look around on the forum, you should find something useful.
Quote:
Originally Posted by morantis
I hope you don't get into one of those chess matches with Kindle where they alter the next update to stop your script, so you re-write the scripts and back and forth. We had written a bunch of libraries for Android and I do believe we finally got them to give up on ICS.
|
I hope so too, but you never know. It's one thing if a class changes from one release to the next, because it has been improved. This can easily be "fixed" by adapting the patch to it.
It's a completely different thing if Amazon starts to aggressively obfuscate their classes (as they did from 5.0.* to 5.1.0) because of some irrational fear. We are not bad crackers. We don't steal code and make millions by selling it. We are wearing white hats, and we are doing all of this because we want to make the device more useful. Why don't the people at Amazon understand that we are dedicating our time to actually add value to their product? Instead, they seem to see us as some kind of evil adversary, and spend their time and money to throw wrenches in our path. This ends up being counterproductive for everyone: both sides have to spend more effort, and instead of actually getting a better product, it just ends up deteriorating (or, in the best case, stagnating). Is that really what you want, Amazon?(*) That said, let's see what the next firmware update will bring.
@eureka: I'm using Eclipse for a good reason (well, at least, a good reason for me): it makes life much easier while developing. I'm aware that the compiling step could be extracted into a javac task in the ant file, but it's just not worth the hassle for me. Anybody who is in for serious patch development needs a correctly set up IDE, which includes both the Amazon jars, as well as jbpatch and serp, anyway.
Quote:
Originally Posted by Zema
ixtab, I'm very happy with your margin patch, I've been waiting for this solution for ages. The only thing that I'd like to improve is possibility to change top/bottom margins for PDF reader only without changing anything in MOBI reader. Is it possible? The point is that PDF documents usually already have margins, but MOBI files are rendered on the fly and margins are necessary. Finally, changing of margins from menu (launcher) separately for PDF and MOBI readers would be incredibly excellent.
|
I agree with the separate settings for PDF and mobi, and I actually already thought about how this could be done. Unfortunately, they both access the same properties, but with slightly different semantics (meaning: the current default Kindle behavior can actually be considered a bug, and I have to find a workaround to fix it). I'll look into this in the next two weeks, but not right now. In other words: thanks for the comment, the issue is now on my agenda. Just don't hold your breath
@pirl8: Thanks for the hint. Unfortunately, this method requires changes to the underlying book ("compile-time", so to say, whereas my method should be applied at "runtime"), and, if I understand it correctly, it only applies to KF8 books. Nevertheless, I think it is a good idea. Actually, I don't have any KF8 book around, so I don't even know if my method would affect it at all. (Maybe someone has a link to a free KF8 book?). In the end, we might also end up with a combination of both methods.
Finally, @all: Thanks for the positive feedback (seriously!). It's encouraging to see that my efforts are appreciated. This really helps to keep the motivation up.
PS: (*) Color emphasis added for Amazon. If you are reading this, please do us all a favor and consider it.