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

[shalym]

Didn't this thread used to be in the dev area? Or am I crazy?

Shari

[eschwartz]

Sorry.

Must've happened when I merged the other thread in.

[conan50]

Thanks very much for this hack. It enables me to use my Paperwhite 1 with nice control of my fonts. PW1 5.6.1.1
I have some vision issues so I went with larger font settings:
12.30 12.72 14.14 14.56 15.98 16.40 17.82 18.24

[ersott]

Thank you very much for this hack, works perfectly.

I have a doubt. When I use this hack, I notice that line spacing has increased. Is it possible?, Has anyone noticed this?

Thanks again.

[knc1]

Originally Posted by ersott

Thank you very much for this hack, works perfectly.

I have a doubt. When I use this hack, I notice that line spacing has increased. Is it possible?, Has anyone noticed this?

Thanks again.

Hmm....
I haven't seen anyone posting comments about the spacing.

But considering that what appears to be 'line spacing' is part of the glyph of each character, it is reasonable that when you scale the glyph, you scale the 'line spacing' also.

The 'line spacing' part of each glyph is also under the control of the font layout engine.
That may be affected by these scaling entries, in addition to just the scaling of the glyph.

If willing to jail break your device, you could then install the custom fonts support package.
Those should be free of the 'line spacing' problems that you are seeing.

[ersott]

Thanks knc1 i'll wait for jailbreak and try to install several fonts.


:Gracias:

[JSWolf]

What are the default font sizes in px for a Voyage or PW3?

[knc1]

Question asked and answered in first few pages of this thread.
Sorry, I don't have a link, but I read it just this morning.

[odamizu]

From Post #22:

Originally Posted by tono1020

... Default values are: 7.13 7.81 8.49 9.17 10.53 12.56 16.98 29.2.
You can recalculate those values in pixels (approximate): 19.2; 21.1; 23; 24.7; 28.6; 33.9; 45.8; 78.9.

However I'm not sure those default values are exactly right. When I used some of them in font_ramp, they seemed a tad off compared to when I wasn't using font_ramp (which would have been true default values). But I'm not positive. It was just an impression.

[knc1]

Originally Posted by odamizu

From Post #22:



However I'm not sure those default values are exactly right. When I used some of them in font_ramp, they seemed a tad off compared to when I wasn't using font_ramp (which would have been true default values). But I'm not positive. It was just an impression.

Screenshot both cases -
Then load into a graphic's program that let you measure and/or count the pixels per line of text.

Be sure your using the same baseline and topline when counting as the font is specified by (a xxx pt font is only a nominal xxx points high).
There are strange ways of including/ignoring ascender/decenders, top/bottom spacing, and a whole lot of things I am uncertain about.

[odamizu]

While a tiny part of me wants to confirm whether or not those default values are correct, a bigger part of me doesn't have time right now to go to all that effort. Maybe later

[knc1]

Originally Posted by odamizu

While a tiny part of me wants to confirm whether or not those default values are correct, a bigger part of me doesn't have time right now to go to all that effort. Maybe later

It was just a thought.
File it for "someday".

The numbers don't count (no pun intended), only if the user is satisfied with the result of whatever change they make.

[blue_skies]

I bought a Paperwhite 3 during the Prime sale. I have an old Kindle Keyboard and use the font size that is number 6 from the left, with the Sans Serif font. It looks really nice to me on the KK. The two larger fonts are huge though. There is a much larger jump between the 6th and 7th sizes and the 8th is really huge.

I thought the Paperwhite 3 was going to be so much easier to read with it's sharper text, but it turns out that the text sizes are just terrible for me. The font size #6 from the left is tiny compared to how it is on my KK, and #7 is just way too big - there's barely anything to read before I need to turn the page.

I realized that the change from the KK is probably just due to the higher resolution making the same font size display much smaller.

I was so happy to read this easy fix. I made up and tried several Font_Ramp files before I found one I love. The problem, of course, is that Amazon delivers formats other than AZW3. I had really been hoping I could just have my Kindle books delivered without having to fuss with them.

I got so excited when I tried downloading to USB and they were AZW3s... but then some ended up being AZW... which doesn't work with the FONT_RAMP.

I'm totally bummed that it's not consistent. Any idea why some are and some aren't? Does it have to do with publication date or something? Or the publisher vs self-published?

Is there any way to get only AZW3 format books delivered from Amazon? Is there a setting somewhere on my account that lets me choose the format delivered?

I may need to send the Paperwhite back. The screen is kind of blotchy anyway, and there are shadows at the bottom. I have a Boyue T62+ android eReader with a Carta screen, and it is perfect... so I was expecting the Paperwhite screen and frontlight to be as nice.

The font issue is just one more problem with the Paperwhite. I'm not impressed with the Bookerly font either, and really would prefer a "bold" option and the previous Sans Serif font.

[knc1]

If you purchased the book(s) from Amazon, they should be able to send you azw3 - ask customer service.

Blotchy lighting with shadows?
That was a problem with the first run of the PW-1.
On the PW-3, that is a defective Kindle - tell customer service about it, they should be willing to replace it. (Buying it on sale doesn't change that.)

Edit:

I have an old Kindle Keyboard

If by that you mean a K3 model (not a K1 or K2, which also have a keyboard). - - -

If you purchased the book(s) **before** the K3 firmware was updated to handle azw3, then the Amazon distribution system will be sending you azw format books.
(Also, if you still have the K3 set as your 'default' device.)

Do -

• Check your account, see that the default device is your PW-3, not your K3.
  (This should be optional, but it may not be.)
• Update your K3 to the most recent firmware (3.4.2 - which handles azw3).
  If it is jail broken, follow any jb instructions about preserving or replacing you jb.
  Sorry, device is too old, I don't recall the procedure - just check the 'legacy' jb thread header.
• Remove one of the Amazon azw books and then re-download it from your account (with the K3, not with your PC).
  Again, device too old for me to recall the 'HowTo' do that on a K3.
• Did that result in the book being updated to the latest publication and in the azw3 format?
  (I have never checked if the K3-3.4.2 firmware sends your firmware build id to the Amazon distribution 'bot so that you get the most recent supported book format. I have checked the PW-3, it is sending the firmware build id with the download request.)
• Did all of that get you an azw3 formatted book?
  No - same as above - contact Amazon Customer Service.

[eschwartz]

It depends how you download a book -- like knc1 said, if you downloaded the book with your K3 and your K3 doesn't have the latest firmware, you cannot get AZW3.
You can also download directly from http://amzn.com/myk for your PW3 if you don't want to get KFX on your PW3.

...

None of this helps if the book is old enough that it was published before AZW3 was developed.
Some books are just only available in MOBI.

In that case, you can import the book into calibre and convert it from MOBI to AZW3.