Edit jars on 5.6.1.0.5 (margins, font sizes) -- and non-jb fonthack

[NiLuJe]

Yup, most probably, since after all, it's going to get gobbled up by a Java piece of code, which I'm hoping is doing things smartly given its multi-platform nature .

[knc1]

Originally Posted by thomass

The file on this zip has no line ending in it (ie it contains only 1 line of text) I think for this particular file editing software does not matter. (also pay attention to the extension of the resulting file.)

Attachment 137584

Correct.
My comment about line-endings naturally only applies to files that require them.
This file is a rare exception.
(POSIX standards **require** an end-of-line. Used to detect an incomplete line. But this is Java as NiLuJe points out. It does a formated read of a series of floating point numbers and stops when that fails (for any reason) - see post #3 of this thread. )

[knc1]

Originally Posted by odamizu

- - - -

There was something in there about increments of .34, and indeed the default settings increase by multiples of .34 (.68, 1.36, 2.03, 4.42, 12.22). Though I notice you increased each setting by .94 and it worked, so clearly the .34 thing isn't required.

- - - -

The name of the file is FONT_RAMP not FONT_CURVE.

[odamizu]

Originally Posted by thomass

The file on this zip has no line ending in it (ie it contains only 1 line of text) I think for this particular file editing software does not matter. (also pay attention to the extension of the resulting file.)

Yes, indeed. I edited tono1020's file and also created new plaintext files. The text editor automatically added an extension to the plaintext files, which I took care to delete.

[eschwartz]

Text editors should not add extensions you didn't ask for. Sack it and get a new one.

[odamizu]

Suggestions for Mac?

(To be fair, this was an HTML editor, since that's mostly what I do)

[thomass]

Originally Posted by odamizu

Suggestions for Mac?

(To be fair, this was an HTML editor, since that's mostly what I do)

A non-free option: Sublime Text

[NiLuJe]

And a couple free ones: TextMate 2 or Atom

[tono1020]

Originally Posted by odamizu

Thank you again everyone for all your help, with a special to ecostin for finding and sharing this hack. It works great!



That's interesting. I wonder why some of your sets didn't work and what criteria the numbers need to follow in order for them to work. I went to the Russian forum, but I didn't really understand it, even with the help of Google Translate

There was something in there about increments of .34, and indeed the default settings increase by multiples of .34 (.68, 1.36, 2.03, 4.42, 12.22). Though I notice you increased each setting by .94 and it worked, so clearly the .34 thing isn't required.

Those numbers are font sizes in 1/100th of an inch. So if you want to transfer them to pixels or another way arround you must know DPI (300 for KV and 216 for PW2).
Pixel height for KV is 1/300" = 0.00333" or 0.08467mm
For example:
if you want fonts with those sizes (in pixel):
22px, 24px, 26px, 28px, 30px, 32px, 34px, 36px
you have to use file with those numbers (in 1/100"):
7.33 8.00 8,67 9,33 10.00 10.67 11.33 12.00

(22px*0.00333"=0.07326 or round up to 7.33 in 1/100"
24px*0.00333"=0.07992 or round up to 8.00 in X/100" and so on...)

BTW: I used Notepad++ for creating FONT_RAMP file

[tono1020]

Yes, some sets did'n work for me. Fonts were default (huge). I didn't have time to discover why. So I just use numbers from ecostin. Thanks again for that!!!

[hontehai]

Originally Posted by ecostin

I was editing, monkey style (i.e. without putting any effort into understanding), the jars in version 5.6.1.0.5 for a Kindle Voyage, to get the margins, font sizes, etc. right.

The margins editing is ok, small changes, but it seems to work fine, same with the progress bar size (ReaderSDK-impl-en_GB.jar). Instead of fixed values, now the numbers are used to multiply the pixVal value, which for KV is 0.4245.

Apparently the mobi and PDF readers still have the same resource names, so it should work as well.

The problem is with the kf8 resources (HTMLReader-impl-en_GB.jar) which are now changed and the htmlreader.font.size.list* constants are missing from the resources. Maybe the new sw version uses the same parameters for kf8 as for mobi, I've got no clue.

Before I start spending lots of time to actually be able to understand what has to be edited, I though I might get lucky and some good soul on this list has already identified the resources to edit to get the font sizes right ... anybody?

Could you explain the margin ? I try to change pixVal but it not work.

[odamizu]

@thomass, @NiLuJe, @tono1020

Thanks for text editor recommendations. I don't mind paying for good apps/programs. Developers should be compensated for their time and efforts

Originally Posted by tono1020

Those numbers are font sizes in 1/100th of an inch ... Pixel height for KV [at 300 dpi] is 1/300" = 0.00333" ... For example:

22px*0.00333"=0.07326 or round up to 7.33 in 1/100"
24px*0.00333"=0.07992 or round up to 8.00 in X/100" and so on...

Ahhhhh! I understand now. Thank you!

[odamizu]

Originally Posted by tono1020

Default values are: 7.13 7.81 8.49 9.17 10.53 12.56 16.98 29.2.

Where are default values to be found? There was no default FONT_RAMP file in root directory before I put one there.

Originally Posted by tono1020

Yes, some sets did'n work for me. Fonts were default (huge). I didn't have time to discover why. So I just use numbers from ecostin. Thanks again for that!!!

It is curious that some sets don't work. No big deal since we have sets that do work, but the little demon inside me likes to understand everything

I did more playing, this time increasing by increments of .36 and .42 and these also worked:

7.49 7.85 8.21 8.57 8.93 9.29 9.65 10.01

7.13 7.55 7.97 8.39 8.81 9.23 9.65 10.07

[tono1020]

Originally Posted by odamizu

It is curious that some sets don't work. No big deal since we have sets that do work, but the little demon inside me likes to understand everything

I was curious enough to take another look and find FONT_RAMP, which didn't work for me. Hmmm, I found stupid mistake: for one of the number I used wrong decimal symbol - comma (,) instead of point (.)
I didn't research any longer at that time and just used ecostin initial set which worked well. My mistake!
So .. yes, every combination works just fine. Unless you use comma for decimal sign of course
Thank you for being "stubborn" enough

[odamizu]

Originally Posted by tono1020

... So ... yes, every combination works just fine. Unless you use comma for decimal sign of course
Thank you for being "stubborn" enough

Excellent! Thank you for double-checking :