[Kindle Touch] Font Hack

[knc1]

Originally Posted by KillerKlown

ok, I'm starting to lose my mind here... I just can not find the original ones. I can only see the ones I put. People, I'm a blonde guy who just wants his default fonts back... share more detailed tips to do that. Please

Well, then you must have over-written them with files of the same name if everything has the same (or similar) date-time stamps.

Next way to do this - -
Download the mmcblk0p1 image file for your machine - -
Mount it, find the "stock" fonts - -
Anything other than those on your machine are the ones you added.

[KillerKlown]

Thank you so much for helping! I finally solved the mystery :P

[ixtab]

For the record: the original fonts are NOT displayed in Font Hack. Just use the "reset to default" button

[MarvinO]

What is the right way to replace the default Caecilia LT font with a newer version? I got my hands on the new and improved version 5.40 (used in kindle 4.1.0 and kindle keyboard 3.4 - both have identical font files after latest update).

I made "Caecilia LT" directory and renamed:
Caecilia_LT_65_Medium.ttf > Caecilia LT Regular.ttf
Caecilia_LT_66_Medium_Italic.ttf > Caecilia LT Italic.ttf
Caecilia_LT_75_Bold.ttf > Caecilia LT Bold.ttf
Caecilia_LT_76_Bold_Italic.ttf > Caecilia LT Bold Italic.ttf

Then tried to activate it, it told to rebuild cache, I did, it found the new fonts and asked for framework restart. After restart whenever I enter the "Font Hack" application the kindle just reboots.

It created fonts.dir and fonts.scale inside "Caecilia LT" directory and 00-Caecilia LT.conf in /fonthack. When I remove them the Font Hack application starts, but when I activate "Caecilia LT" it behaves just as I described.

Does it need unique names and when I want to use newer version font with the same name this hack can't be used?

[kacir]

Originally Posted by knc1

What is "low-res" about a 168 ppi display?

ANYTHING below 300dpi is low-res as far as typography is involved.

168 is pretty high resolution *for a display*, but not for printing. Old monitors had approximately 75dpi and 168 dpi is only high when comparing with that. Even lousiest laser printers have at least 300DPI. And that is not considered enough. They have RET technology and other features, and often 600dpi and more to let you print fonts and vector graphics nicely.

[ixtab]

Originally Posted by kacir

ANYTHING below 300dpi is low-res as far as typography is involved.

168 is pretty high resolution *for a display*, but not for printing. Old monitors had approximately 75dpi and 168 dpi is only high when comparing with that. Even lousiest laser printers have at least 300DPI. And that is not considered enough. They have RET technology and other features, and often 600dpi and more to let you print fonts and vector graphics nicely.

... and to add a bit to the off-topic discussion: the Kindle paperwhite has a 212 dpi (1024x758) display, and I will probably still be able to read the letters.

[knc1]

Originally Posted by kacir

ANYTHING below 300dpi is low-res as far as typography is involved.

When you get the printer on your Kindle working, we can re-address this question as the new topic that it is.

The topic under discussion (dispute?) here is the Kindle display.

[geekmaster]

Comparing printers and eink is complicated by the fact that printers can only display pure black and white, while the eink can anti-alias with 16 shades of gray.

At the normal distance range that you hold a Kindle while reading, the human eye can perceive the anti-aliasing as increased resolution, allowing much LESS than 300 DPI to look great, while on a pure black and white printer, 300 DPI looks crude in comparison and you really need 600 DPI or better.

So anti-aliased eink displays have a higher "effective" resolution than their technical DPI ratings would otherwise indicate.

References:
http://www.ncbi.nlm.nih.gov/pubmed/9304755

Anti-aliasing is a technique for improving spatial resolution at the cost of luminance resolution. Dithering is a technique for improving luminance resolution at the cost of spatial resolution. These techniques are applied to the testing of visual function in the 'Freiburg Visual Acuity Test': by employing anti-aliasing, spatial resolution was improved.

Interesting anti-aliasing tutorial:
http://www.beatstamm.com/typography/RTRCh2.htm

[franco1387]

Here is a spanish translation made by me, i didn't know were to put it, so i post it here.

[blanca_luz]

Amazing!!!!

You can use the font you like the most for the main text, and still it respects all the embedded fonts.
I,ve just tested a KF8 (made by me) and it works so well

[orpheus2011]

Apologies if this has been answered elsewhere, but does this hack work for the Paperwhite on 5.2.0, now that we have a working jailbreak, or do we have to wait for an update to the font hack 1.3.2 version for it to work on the PW?

Many thanks!

[knc1]

Originally Posted by orpheus2011

Apologies if this has been answered elsewhere, but does this hack work for the Paperwhite on 5.2.0, now that we have a working jailbreak, or do we have to wait for an update to the font hack 1.3.2 version for it to work on the PW?

Many thanks!

Fonts in the Kpw are stored in a read-only, compressed, file system.
This is different than the other machines, which may mean changes are required to how fonts are added / changed.

Let us know what progress you make in trying to get this to work on your Kpw.

[twobob]

Originally Posted by knc1

Fonts in the Kpw are stored in a read-only, compressed, file system.
This is different than the other machines, which may mean changes are required to how fonts are added / changed.

Let us know what progress you make in trying to get this to work on your Kpw.

Refs:
http://en.wikipedia.org/wiki/Cramfs
http://sourceforge.net/projects/cram...urce=directory

[orpheus2011]

Originally Posted by knc1

Fonts in the Kpw are stored in a read-only, compressed, file system.
This is different than the other machines, which may mean changes are required to how fonts are added / changed.

Let us know what progress you make in trying to get this to work on your Kpw.

Thanks for this. If I understood correctly, the jailbreak and installation part (installing kindlet, the certs and the fonthack 1.3.2) should go through fine, and we would be left with problems in placing the ttf fonts in the right directory. Is this correct? Would anyone have any pointers on how to modify the cramfs image?

[twobob]

Mount the cramfs file system image as a loop device
find stuff/Make stuff
mkcramfs stuff newFile

I believe roughly

http://manpages.ubuntu.com/manpages/...kcramfs.8.html

and the other stuff I posted has more general concepts.