This is a little howto guide to getting the new fonts without owning a K3/K4 device. Because I used this post as a step thru and then found out things on the way read it thru before following it! Some steps are not needed or only needed to verify/find out information that I already put up here!

When looking at K3 and K4 changelogs one can see this:

K4 Software Update Version 4.1.0
* Improved reading font that is higher contrast and crisper so that you can enjoy a paper-like reading experience.

K3 Software Update Version 3.4
* Improved Font: We've improved the reading font to have more contrast and be more crisp.

That got me wondering, they are most probably using a new version of the default font on it. Let's find out.

I'm using windows so I'm going with kindletool-v1.5.1.1-mingw.zip. Extract it and put the update files inside the directory (for easy access).

Start>run>cmd for winxp or start>type cmd (newer than xp)

Go to the kindletools directory for me it is "cd C:\Users\myusername\Downloads\kindletool-v1.5.1.1-mingw"

For nice placement create K3 and/or K4 directory (you really only need one, I'm doing both to see that they contain THE SAME new font) enter "kindletool.exe extract Update_kindle_3.4_B008.bin k3" And you see information about the package and extraction of files. Look inside the k3 directory.

These are the MD5 checksums that should match after we have done binary patching.
Disregard everything else, we only need the 13 ttf.patch files

For K4 use the same extract command. kindletool.exe extract Update_kindle_4.1.0_B00E.bin k4 Now this is a newer version of patching so look inside K4 directory and there is mnt\us directory, there you'll find Update_payload.bin Move it to kindletool

directory. Make a new directory for example k4_ext and extract it: kindletool.exe extract Update_payload.bin k4_ext. Now inside that k4_ext directory you'll find the

K4 does not update Kindle_Symbol.ttf file as K3 does, there is no binary diff file for it. K4 has rootfs_md5_list.tar.gz but that is empty. So no MD5 hashes to check against there They are in fact "hidden" inside 1331440003-1615370055.ffs file. It's a mess to look at in Notepad (unix vs windows linebrake). But the hashes are as follows:
_PATCH_MD5=`md5sum "patch/usr/java/lib/fonts/Caecilia_LT_65_Medium.ttf" | awk '{ print $1; }'`

_EXPECTED_MD5=3954651ba10e35b11fe723b64749d1f0

I won't write them here, but the MD5 hashes ALL MATCH against those that are in more readable form in K3! So this is first great success! K3 and K4 use the same new version of the font!

### THIS IS FOR INFORMATION PURPOSE ONLY, IF YOU WANT TO UPDATE K5 FONTS DIRECTLY, SKIP THIS ###

You'll need the first partition and that is named mmcblk0p1. I'll go with K4 mmcblk0p1-k4-4.0.1.7z because that is only 82.5MB and the mirror seems up (github ones are all down).
Extract it to the directory you have the patch files. Now there is a problem, it is EXT3 linux file system and I (and you in this guide ) need to open it. The easiest way to do that is to use http://www.chrysocome.net/explore2fs tool. I use 1.08beta9. download, extract and run it. In File>Open Image File... point it to mmcblk0p1.img. Now use the tree in left to go to:
/usr/java/libs/fonts direcotry. Select all the Caecilia font files and Kindle blackbox files, right click, export files. Coose the directory where you have the binary patch files.

And this is where I found out that K4 4.0.1 contains the same version of fonts that K5 5.1.2

If you already have the fonts from K4 image then no need to get them from your Touch. But if you skipped the middle part as I told you need the font files from your Touch. The easiest way is to use https://www.mobileread.com/forums/sho...&postcount=293 on your jailbroken device. It takes quite a long time to dump the main filesystem but you'll end up with mmcblk0p1.img.gz file in your Kindle root directory. Extract it to your working direcotry. Now there is a problem, it is EXT3 linux file system and I (and you in this guide ) need to open it. The easiest way to do that is to use http://www.chrysocome.net/explore2fs tool. I use 1.08beta9. download, extract and run it. In File>Open Image File... point it to mmcblk0p1.img. Now use the tree in left to go to:
/usr/java/libs/fonts direcotry. Select all the Caecilia font files, right click, export files. Coose the directory where you have the binary patch files.

Now hot to use them?
Rename them to remove the _new if you used that bspatch command.

Place the 8 files on your Kindle root to /fonts directory. Now unplug your Touch and in the search field write ";fc-cache" without the "" and return on the virtual keyboard. It seems to do nothing but in about 3 minutes or so the screen will go blank and then when everything reappears the new fonts are in use (look here https://www.mobileread.com/forums/sho...&postcount=738).