The motivation to "diss" the member who provided such a shallow question had nothing to do with a "passing on" motive. My motives are explained in the prior posts. Noob or not, to ask if there is such an option when looking at the options once would provide the answer is a ballzy move, you have to agree.

Then again I was not "dissing" the user who provided the answer (i did as well if you care to read more closely), also the second posting was adressed to the first user who finally got it the way he wanted - dont look for yourself, dont even try to learn the way a straight forward piece of software (from an ui perspective) works, dont bother asking in depth what you actually mean - just spout out 3-5 words of minimalistic question asking and let the internet do your bidding.

Of course you must protect such behavior. Because we not only nurture our noobs, no - we feel that asking before doing the slightest bit of research (actually research doesnt even fit in this context) is a viable mode of behavior in community forums. Much more viable than a bit of cynicism.

In the question to Kovid case I did search the forum prior to asking, I did search google - to no avail, because I had insufficient clues on how to single out the problem in search. As you can imagine searching for "Cover" in regard to the cover that only shows up in the Kindle Interface upon longpress is entirely futile. I didn't complain when Kovid answered though.

Will read asap. And no - dont want a flamewar here (please dont), just wanted to drop a bit of cynicism, thats all. Its a personal thing.

I cant stand onelined openly phrased questions where the person who answers has to answer for more than one eventuality (what did he actually mean), especially when the person asking, could have found out for him/herself with minimal effort, prior to asking. (Strike the "flaming" conotation from that sentence... ) For me such questions are linked to a "enthusiasts communities are the better clerks, faster, more accurate" attitude which I deeply despise...

iXtab, I've been reading about JBPatch with much interest. Has/how can this be ported to K3 devices? I'm predominantly interested in the cover view. Apologies if the answer is buried in the preceding 42 pages.

It has not been ported.
It may not be possible to port to the K3 devices because the systems are very different.
Greyed out is correct - the package does not work for the model of Kindle you are trying to install it on - so it will not install.

Will read asap. And no - dont want a flamewar here (please dont), just wanted to drop a bit of cynicism, thats all. Its a personal thing.

I cant stand onelined openly phrased questions where the person who answers has to answer for more than one eventuality (what did he actually mean), especially when the person asking, could have found out for him/herself with minimal effort, prior to asking. (Strike the "flaming" conotation from that sentence... ) For me such questions are linked to a "enthusiasts communities are the better clerks, faster, more accurate" attitude which I deeply despise...

But again, its a personal thing.

We have all felt the urge to say things that in retrospect seem a bit disrespectful of others. It is all too tempting to answer with RTFM, but I stopped using that after a huge flamewar erupted from non-technical people who came here from the ebook reading crowd, when they took it as an insult (much more than its humorous intent amongst techogeeks).

Your post did seem a bit harsh and a bit broad, but that was my own interpretation. I have occasionally been proven to be human, with various accompanying foibles associated with that condition, and one of those is occasional misinterpretation of intent in a post such as yours. English is prone to that with various words having multiple meanings, often allowing statements to be interpreted more than one way, leading to perceived ill will where none may have been intended. Flame wars are made of this, wherein English is a powerful weapon with which to shoot your opponent or yourself in the foot. Simple URLs as shown above are a much safer weapon of choice.

Thanks for the clarification. I was under the assumption that due to similar java frameworks existing across Kindles, it could be possible.

Even the K5 firmware 5.0.x and 5.1.x are not all that similar. JBPatch has not even been ported to 5.0.x firmware. Porting to K3 would be more difficult. But don't let that stop you from trying. You can start with ixtab's published source code. And please share your results.

iXtab, I've been reading about JBPatch with much interest. Has/how can this be ported to K3 devices? I'm predominantly interested in the cover view. Apologies if the answer is buried in the preceding 42 pages.

I asked this question before, without realizing it would require more than the knowledge I have. ixtab suggested to me [and i suggest this to anyone who wants to port] to go look at the source for it, and find a way to hook JBPatch into the system.

I have updated the JBPatch to 2.3.1 and enjoy very much the process bar. Thank you very much ixtab. For this process bar I would like to ask for an additional feature.

The process bar is based on the whole book size. If a book has chapters, is it possible to only show the chapter statistic? I mean the process bar reflects the chapter length and the indication what is the remaining part.

It would be useful if a book has a lot of chapters and you want to read until next chapter. Then you need no painful scrolling within the book.

hi there,
I have a weird problem with hyphenation and text justification. I have a book that just does not want to be justified and/or hyphenated. I tried converting from mobi to mobi as mentioned in the wiki, I even converted the mobi to epub and that epub back to a mobi. I changed the language to check if anything happens at all. It does show up in the log as detected and the language rules are loaded, but nothing happens to the actual layout, neither text justification nor hyphenation.
I am running all the latest jbpatch files as of 10 minutes ago.

this is the original mobi file, maybe you can find anything in there...

hi there,
I have a weird problem with hyphenation and text justification. I have a book that just does not want to be justified and/or hyphenated. I tried converting from mobi to mobi as mentioned in the wiki, I even converted the mobi to epub and that epub back to a mobi. I changed the language to check if anything happens at all. It does show up in the log as detected and the language rules are loaded, but nothing happens to the actual layout, neither text justification nor hyphenation.
I am running all the latest jbpatch files as of 10 minutes ago.

this is the original mobi file, maybe you can find anything in there...

thanks a lot for all your work mate, i appreciate it a lot.

PLEASE EDIT YOUR POST TO REMOVE THE LINK TO COPYRIGHTED MATERIAL! Distributing copyrighted material is not allowed on Mobileread, and you may get banned for doing so.

That said, I have downloaded it for testing purposes (yes, I have already deleted it again). After converting the book from mobi to mobi, the hyphenation does work, but the alignment doesn't. I don't know what the reason is, but it's probably due to the book itself specifying that the text is not aligned.

But I'm not an expert on mobi/KF8/epub formats, and I can't look into every single book... You may have more luck by asking in a book formats-related subforum about how to fix the alignment. Good luck