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

[roger64]

Maybe

Here is what I see

[shalym]

Originally Posted by roger64

Maybe

Here is what I see

Yup--just drop the file right there--don't put it inside a folder.

Shari

[roger64]

I have the explanation of my previous "failures":

I used this set of values already published (rather smaller font-sizes):
7.13 7.81 8.49 9.17 9.85 10.53 11.21 11.89

When you look at the menu, it seems nothing changed.
"Only issue is that the 'preview' sizes you get on the font menu stay the same."

For this reason, I thought it was not working but when I tried even with the biggest font-size, it was OK.

Thanks for your kind help.

[Josieb1]

Will this work for a Voyage?

[eschwartz]

Originally Posted by shalym

This should probably be in the dev area, but I need to ask why you think it doesn't work with a PW 3? It definitely works on mine...

Shari

Originally Posted by shalym

Follow the instructions in this thread exactly https://www.mobileread.com/forums/sho...d.php?t=256969

Shari

Moderator Notice

Threads merged.

[eschwartz]

Originally Posted by Josieb1

Will this work for a Voyage?

Take a look at the first page.

Not only will this work on the Voyage -- it was originally discovered on the Voyage.

[Josieb1]

Originally Posted by eschwartz

Take a look at the first page.

Not only will this work on the Voyage -- it was originally discovered on the Voyage.

[Josieb1]

Before I try this on my Voyage, if i don't like the results is it just a case of removing the file? It doesn't disappear does it?

Also I use Send to Kindle for mobi files, when they download are they azw format and therefore will this hack work for them? I rarely read books actually bought from Amazon

Thank you

[eschwartz]

Just remove the file and reboot, yes.


You will need to start using AZW3 in order to see results.

[Josieb1]

Originally Posted by eschwartz

Just remove the file and reboot, yes.


You will need to start using AZW3 in order to see results.

Thanks for the reply. It won't work for me then as I don't sideloaded, I only read my ebooks via the Amazon Cloud.

[thatworkshop]

Originally Posted by eschwartz

You will need to start using AZW3 in order to see results.

Now that we are talking about this, I was wondering why Amazon doesn't support AZW3 format for the personal documents?!!!

[eschwartz]

If they supported sending AZW3, then there would be no fallback for devices that only support MOBI.


And as a matter of fact, if you send a dual-MOBI through Personal Documents, you DO get an AZW3 (on supported devices). This directly imitates how the KDP publishing workflow operates.
Note: that has its own bug, specifically you will be missing the cover thumbnail in Cover View.

[Josieb1]

Originally Posted by eschwartz

If they supported sending AZW3, then there would be no fallback for devices that only support MOBI.


And as a matter of fact, if you send a dual-MOBI through Personal Documents, you DO get an AZW3 (on supported devices). This directly imitates how the KDP publishing workflow operates.
Note: that has its own bug, specifically you will be missing the cover thumbnail in Cover View.

The cover is important to me so that won't work either. Thanks anyway.

[thatworkshop]

Originally Posted by eschwartz

...

Well, that's good to know. I am assuming by dual-MOBI you mean an AZW3 file with .mobi as its extension, eh?
Update: Figured it out here.

@Josieb1: That's not too bad actually, but yeah I feel you.

[eschwartz]

Originally Posted by idoit

Well, that's good to know. I am assuming by dual-MOBI you mean an AZW3 file with .mobi as its extension, eh?

@Josieb1: That's not too bad actually, but yeah I feel you.

An AZW3 with a *.mobi extension is still an AZW3, the same way a DOCX with the *.monkey extension is still a DOCX.
However, the application handling it may or may not know how to recognize the file if it lies about itself (though unix will rely on magic numbers instead of or in addition to file extensions).


As for Amazon Kindles and dual-MOBI, a dual-MOBI is exactly what it sounds like it should be -- a file that contains both mobi7 and KF8 sections.
Used to display KF8 on newer devices, but still be readable on ancient devices that don't support AZW3, since they can read the mobi7 section of the file.

They have the *.mobi extension though, true enough.
That's how the old devices realize it's a mobi7 file.