FW 5.3.x - 5.7.x Fonts Hack - Page 3

NiLuJe · 09-05-2013, 11:34 AM

@richy1989: Huh. Good to know it works, I thought I'd tried (and failed) to squish Caecilia Condensed from my Touch's Aa menu

.

NiLuJe · 09-18-2013, 02:23 PM

Released 0.4.N.

Besides the usual binaries update, it now handles USE_ALT_FONTS itself and in a slightly smarter way, to avoid potential fun issues after full official updates.

For that reason alone, this is a strongly recommended update.

And to anyone using USE_ALT_FONTS: Disable it before doing an official update!

(And no, that's not just a hint to avoid potential issue, I did manage to lock up my PW after the 5.3.8 update. Fortunately, it stalled on the third boot (who knows why it worked the first two times...), so I already had SSH up & running).

EDIT: Forgot to mention that the FT update might bring significant rendering changes for anything using the autohinter (mainly the autohint & light FT overrides).

NiLuJe · 09-20-2013, 12:28 PM

... And 0.5.N

.

Which properly tackles the 'official full updates' thing by using our own dedicated fonts directory. The doc has been updated appropriately.

There's also a fresh FreeType update, which fixes the clipping of synthetically emboldened fonts, which is nice for those using a custom font mising its bold style(s)

.

So, again, a recommended update, and I'd also recommend everyone to run the Fonts -> Fonts Hack Behavior > * Migrate your fonts directory * KUAL button after the update to migrate to the dedicated fonts directory

.

hfpop · 09-21-2013, 04:38 PM

NiLuJe, are you certain that everything is all right with version 0.5.N? As I understand, after the migration, the folder /mnt/us/font will be removed (indeed, it is), and there will be no need for the file /mnt/us/USE_ALT_FONTS. I removed the file, and rebooted the Kindle. Afterwards, the file is still there. Is this intended? I ask, because my feeling was that user fonts are dealt by linkfonts internally.

Thank you for clarifying all these.

NiLuJe · 09-21-2013, 05:36 PM

@hfpop: There are two different aspects:

* v0.4.N handle USE_ALT_FONTS in a "smart" way: it's created at boot, and removed at shutdown/update, so that you don't end up with an USE_ALT_FONTS file after an official update. (It used to be created by the install process).

* v0.5.N added the migration of the fonts folder to linkfonts/fonts (which has been a valid & supported folder since v0.1.N, FWIW). And the doc recommends using this folder, so you don't end up with X choking on the cache regen at boot after an official update leaves you without a decent FreeType library

. [Since the folder is hack-specific, and after a full update, we lose our custom fontconfig bit asking the system to take it into account, whereas fonts would still be parsed]

In any case, we still need the USE_ALT_FONTS file to ask the framework to make the new fonts easily accessible in the Aa menu

.

TL;DR: Yep, what you're describing is the expected behavior

.

hfpop · 09-22-2013, 05:28 AM

NiLuJe, thank you for these explanatory details.

NiLuJe · 10-18-2013, 02:55 PM

Monthly updates

.

Fonts v0.6.N:
* Updated binaries.

dereker · 11-24-2013, 12:24 AM

Can I use this font hack on a pw2? Is it safe?

aceflor · 11-24-2013, 02:21 AM

Quote:

Originally Posted by dereker

Can I use this font hack on a pw2? Is it safe?

No, because we still don't know if this particular hack is safe.

NiLuJe needs a device to test it and give us his go. He has ordered a PW2 which should arrive this week so we will know soon.

Yolina · 11-24-2013, 05:37 AM

I think now is probably a good time for the devs to post again the links for donations

that should actually be in a sticky IMHO. Not only do they spend a fair amount of time making things work, it's also much easier when they have the actual devices to test on.

NiLuJe · 11-30-2013, 02:23 PM

Currently experimenting with this on the PW2.

So far, appears not to blow up horribly, so that's that, at least. Getting anything to show up in the Aa menu is possibly doable, but potentially way more trouble than I'm willing to go through.

On the good news front, font overrides work, and since Caecilia Condensed is useless with a custom FreeType, that's the perfect target for such a thing.

I'll update the snapshots in a while, but the doc updates will have to wait, so the strong warning still applies, and I'll urge anyone even remotely looking to try this to *thoroughly* read the first post, be fairly proficient in Kindle twiddling, absolutely have an SSH shell open at all times during setup, be very wary of reboots, and, as a bonus, be familiar with the specifics of this Hack on a safer device (ideally, a Touch, barring that, a PW1).

TL;DR: Here be dragons.

----

As I said, I'm not terribly inclined in digging further into the whole Aa menu thing (and I'm a bit short on time, which doesn't help), so if anyone has any insights into that, I'm all ears

.

levante · 11-30-2013, 03:02 PM

Uff, before your last post I installed the hack (kindle-linkss-0.15.N-r10182.tar.xz), restart several times with no problems... and no results.

Desinstalled and awaiting.

NiLuJe · 11-30-2013, 03:07 PM

@levante: Won't change much. Currently, the only way to actually use different fonts is via the Fonts Override feature (found in the relevant KUAL menu).

If you're expecting shiny bloated Aa menus, then you're SOL

.

NiLuJe · 11-30-2013, 03:32 PM

There we go. Updated snapshots

.

Obligatory screenshots of Crimson replacing Caecilia Condensed ^^.

mabelsound · 11-30-2013, 05:04 PM

Thanks for working on this!

09-18-2013, 02:23 PM	#32
NiLuJe BLAM! Posts: 13,497 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Released 0.4.N. Besides the usual binaries update, it now handles USE_ALT_FONTS itself and in a slightly smarter way, to avoid potential fun issues after full official updates. For that reason alone, this is a strongly recommended update. And to anyone using USE_ALT_FONTS: Disable it before doing an official update! (And no, that's not just a hint to avoid potential issue, I did manage to lock up my PW after the 5.3.8 update. Fortunately, it stalled on the third boot (who knows why it worked the first two times...), so I already had SSH up & running). EDIT: Forgot to mention that the FT update might bring significant rendering changes for anything using the autohinter (mainly the autohint & light FT overrides). Last edited by NiLuJe; 09-18-2013 at 07:27 PM.

09-21-2013, 05:36 PM	#35
NiLuJe BLAM! Posts: 13,497 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@hfpop: There are two different aspects: * v0.4.N handle USE_ALT_FONTS in a "smart" way: it's created at boot, and removed at shutdown/update, so that you don't end up with an USE_ALT_FONTS file after an official update. (It used to be created by the install process). * v0.5.N added the migration of the fonts folder to linkfonts/fonts (which has been a valid & supported folder since v0.1.N, FWIW). And the doc recommends using this folder, so you don't end up with X choking on the cache regen at boot after an official update leaves you without a decent FreeType library . [Since the folder is hack-specific, and after a full update, we lose our custom fontconfig bit asking the system to take it into account, whereas fonts would still be parsed] In any case, we still need the USE_ALT_FONTS file to ask the framework to make the new fonts easily accessible in the Aa menu . TL;DR: Yep, what you're describing is the expected behavior . Last edited by NiLuJe; 09-21-2013 at 08:49 PM.

11-24-2013, 05:37 AM	#40
Yolina Wizard Posts: 1,179 Karma: 11573197 Join Date: Feb 2011 Location: London, UK Device: Voyage	I think now is probably a good time for the devs to post again the links for donations that should actually be in a sticky IMHO. Not only do they spend a fair amount of time making things work, it's also much easier when they have the actual devices to test on. Last edited by Yolina; 11-24-2013 at 05:40 AM.

11-30-2013, 03:32 PM	#44
NiLuJe BLAM! Posts: 13,497 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	There we go. Updated snapshots . Obligatory screenshots of Crimson replacing Caecilia Condensed ^^. Attached Thumbnails

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
K5 FW 5.x ScreenSavers Hack	NiLuJe	Kindle Developer's Corner	3008	10-29-2024 12:39 AM
[Kindle Touch] Font Hack	ixtab	Kindle Developer's Corner	508	05-18-2020 12:41 PM
Hacks Kindle Touch Registration Hack	codeisnightmare	Amazon Kindle	15	10-19-2014 09:17 PM
Touch Can I get Kindle Touch Fonts On Nook Touch?	tanteoma	Barnes & Noble NOOK	5	05-17-2012 09:02 PM
Font Hack for Kindle Touch?	Sassapphras	Kindle Developer's Corner	1	02-12-2012 09:05 PM

09-05-2013, 11:34 AM	#31
NiLuJe BLAM! Posts: 13,497 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@richy1989: Huh. Good to know it works, I thought I'd tried (and failed) to squish Caecilia Condensed from my Touch's Aa menu .

09-20-2013, 12:28 PM	#33
NiLuJe BLAM! Posts: 13,497 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	... And 0.5.N . Which properly tackles the 'official full updates' thing by using our own dedicated fonts directory. The doc has been updated appropriately. There's also a fresh FreeType update, which fixes the clipping of synthetically emboldened fonts, which is nice for those using a custom font mising its bold style(s) . So, again, a recommended update, and I'd also recommend everyone to run the Fonts -> Fonts Hack Behavior > * Migrate your fonts directory * KUAL button after the update to migrate to the dedicated fonts directory .

09-21-2013, 04:38 PM	#34
hfpop Addict Posts: 250 Karma: 136662 Join Date: Apr 2011 Device: N/A	NiLuJe, are you certain that everything is all right with version 0.5.N? As I understand, after the migration, the folder /mnt/us/font will be removed (indeed, it is), and there will be no need for the file /mnt/us/USE_ALT_FONTS. I removed the file, and rebooted the Kindle. Afterwards, the file is still there. Is this intended? I ask, because my feeling was that user fonts are dealt by linkfonts internally. Thank you for clarifying all these.

09-22-2013, 05:28 AM	#36
hfpop Addict Posts: 250 Karma: 136662 Join Date: Apr 2011 Device: N/A	NiLuJe, thank you for these explanatory details.

10-18-2013, 02:55 PM	#37
NiLuJe BLAM! Posts: 13,497 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Monthly updates . Fonts v0.6.N: * Updated binaries.

11-24-2013, 12:24 AM	#38
dereker Junior Member Posts: 3 Karma: 10 Join Date: Nov 2013 Device: k3 kpw	Can I use this font hack on a pw2? Is it safe?

11-30-2013, 02:23 PM	#41
NiLuJe BLAM! Posts: 13,497 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Currently experimenting with this on the PW2. So far, appears not to blow up horribly, so that's that, at least. Getting anything to show up in the Aa menu is possibly doable, but potentially way more trouble than I'm willing to go through. On the good news front, font overrides work, and since Caecilia Condensed is useless with a custom FreeType, that's the perfect target for such a thing. I'll update the snapshots in a while, but the doc updates will have to wait, so the strong warning still applies, and I'll urge anyone even remotely looking to try this to thoroughly read the first post, be fairly proficient in Kindle twiddling, absolutely have an SSH shell open at all times during setup, be very wary of reboots, and, as a bonus, be familiar with the specifics of this Hack on a safer device (ideally, a Touch, barring that, a PW1). TL;DR: Here be dragons. ---- As I said, I'm not terribly inclined in digging further into the whole Aa menu thing (and I'm a bit short on time, which doesn't help), so if anyone has any insights into that, I'm all ears .

11-30-2013, 03:02 PM	#42
levante Connoisseur Posts: 52 Karma: 58450 Join Date: Jan 2013 Device: kindle NT, PW1, PW2, Kobo H2O	Uff, before your last post I installed the hack (kindle-linkss-0.15.N-r10182.tar.xz), restart several times with no problems... and no results. Desinstalled and awaiting.

11-30-2013, 03:07 PM	#43
NiLuJe BLAM! Posts: 13,497 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@levante: Won't change much. Currently, the only way to actually use different fonts is via the Fonts Override feature (found in the relevant KUAL menu). If you're expecting shiny bloated Aa menus, then you're SOL .

11-30-2013, 05:04 PM	#45
mabelsound Member Posts: 16 Karma: 20 Join Date: Nov 2013 Device: non	Thanks for working on this!