Instructions for patching firmware 3.3.x, 3.4.x, 3.5.x - Page 9

violent23 · 05-26-2014, 11:05 PM

Quote:

Originally Posted by GeoffR

The margins slider actually has nine values, zero plus the eight that are set in the patch. I haven't tested this but you could try extending the patch to replace the zero margin too (note the added replace_int line at the beginning)

This does work, thank you! Now I have fixed margin settings with any font used. Personally I would like to sugest this as the default in the Patch until Kobo fixes the cut off text problem. Which will most likely resemble this fix by using a slightly larger margin that results in un-cutoff text.

Quote:

Originally Posted by GeoffR

Gothic seems to used if Document Default is selected though. Another font can be hard coded for the footer, but then there will be a mismatch with the header which will still be using Gothic if Document Default is selected, or something else if a font different from the hard coded font is selected.

If there is a way to un-list "Document Default" in the font selection menu along with the other fonts that result in a cut off footer then having only custom fonts should not be a problem as they are used for the footer (which is not cut off) anyways. I don't know if this can be done but having this option would be great for those that use an Aura and don't want to see font options that result in cut off footers. It would seem that if "Document Default" was some way non select-able/non-default then having a mismatched header should not be a problem.

GeoffR · 05-27-2014, 04:19 AM

Here is the patch locations of the CSS stylesheet fragment used for the kepub header text if anyone wants to play around with it. Any changes affect the home page header, library header, etc. too.

There seems to be a difference between the Touch and the Glo/Aura/AuraHD, on the Touch the header always uses font-family: Avenir; but on the other models no font-family is set, so whatever is selected fom the font menu is used, or Gothic if Document default is selected.

This example patch forces the Glo/Aura header to use font-family Avenir, the same as the Touch. If you set the footer to match, that would avoid the buggy Gothic/Ryumin fonts from being used at all when Document Default is selected.

firmware 3.3.0:

Spoiler:

firmware 3.3.1:

Spoiler:

Edit: Note for kpg.exe: Change "replace_string" to "replace_xor_00" and add "\x00" to the end of the replacement string if using kpg.exe.

mattington · 05-27-2014, 05:17 AM

I just applied the patch to my Aura 6" running 3.3.0, but there are still several system fonts showing up in my font menu, namely:

Gothic, Ryumin, Dyslexie, OpenDyslexic

Particularly the Dyslexic fonts are quite annoying as I'll never use them... any idea why these still appear?

GeoffR · 05-27-2014, 05:41 AM

Quote:

Originally Posted by mattington

I just applied the patch to my Aura 6" running 3.3.0, but there are still several system fonts showing up in my font menu, namely:

Gothic, Ryumin, Dyslexie, OpenDyslexic

Particularly the Dyslexic fonts are quite annoying as I'll never use them... any idea why these still appear?

I don't know why the `Remove system fonts in reader list` patch only removes some fonts and not others, sorry. I'm not sure if the patch always worked that way, or if it was something to do with the changes in recent firmware. For some reason the firmware processes those four fonts seperately from the others.

Edit: I found how to remove Gothic, Ryumin, OpenDyslexic, and Dyslexie from the fonts menu, but unfortunately some of my sideloaded fonts such as Dark Courier get removed along with them. I also noticed that the original patch removed my sideloaded Times New Roman font along with the system fonts. So that patch obviously has some problems.

tshering · 05-27-2014, 06:51 AM

Quote:

Originally Posted by mattington

I just applied the patch to my Aura 6" running 3.3.0, but there are still several system fonts showing up in my font menu, namely:

Gothic, Ryumin, Dyslexie, OpenDyslexic

Particularly the Dyslexic fonts are quite annoying as I'll never use them... any idea why these still appear?

You could simply delete the fonts that you don't want to use. If you don't want to modify your device in order to be able to run scripts or execute commands, you could also overwrite the font files with empty files via the update mechanism.

violent23 · 05-27-2014, 07:26 AM

Quote:

Originally Posted by GeoffR

Here is the patch locations of the CSS stylesheet fragment used for the kepub header text if anyone wants to play around with it. Any changes affect the home page header, library header, etc. too.

There seems to be a difference between the Touch and the Glo/Aura/AuraHD, on the Touch the header always uses font-family: Avenir; but on the other models no font-family is set, so whatever is selected fom the font menu is used, or Gothic if Document default is selected.

This example patch forces the Glo/Aura header to use font-family Avenir, the same as the Touch. If you set the footer to match, that would avoid the buggy Gothic/Ryumin fonts from being used at all when Document Default is selected.

firmware 3.3.0:

Spoiler:

firmware 3.3.1:

Spoiler:

Edit: Note for kpg.exe: Change "replace_string" to "replace_xor_00" and add "\x00" to the end of the replacement string if using kpg.exe.

Thanks for this, is there a similar code to set the footer to match?

Quote:

Originally Posted by tshering

You could simply delete the fonts that you don't want to use. If you don't want to modify your device in order to be able to run scripts or execute commands, you could also overwrite the font files with empty files via the update mechanism.

How does one go about removing the fonts they do not want and how will this effect the Document Default setting if/when all system fonts are removed and only custom fonts remain?

GeoffR · 05-27-2014, 08:15 AM

Quote:

Originally Posted by violent23

Thanks for this, is there a similar code to set the footer to match?

Here is the Glo/Aura footer example for firmware 3.3.0, but with font-family set to Avenir:

Spoiler:

violent23 · 05-27-2014, 08:27 AM

Quote:

Originally Posted by GeoffR

Here is the Glo/Aura footer example for firmware 3.3.0, but with font-family set to Avenir:

Spoiler:

Okay so with this custom footer and the custom header from post #122 I will have Avenir set as the Document Default (which does not suffer from a cut off footer), is there a way to now remove or hide the few fonts like Gothic/Ryumin that do have a cut off footer? I see you say in post #124 that you found a way but that it hid some custom fonts as well. If this is the only way to remove the fonts that do not work correctly on the Aura with your custom footer I am willing to test and see if it hides any of my custom fonts. Of course I would need a way to keep Avenir for the Document Default.

*edit - Okay I think I misunderstood. With the new footer and header patches that set them to Avenir, they now just stay at Avenir no matter what font is selected, resulting in the footer never getting cut off. So the caveat is that they do not change but it does fix my footer problem so thank you.

I am wondering though if there is a way to completely remove/hide Document Default and the other fonts while only listing custom fonts or setting a custom font to Document Default and just hiding all the other system fonts, thus allowing the footer and header to change with whatever font is selected without having to run into the cut off footer problem with the Custom reading footer style patch.

tshering · 05-27-2014, 09:03 AM

Quote:

Originally Posted by violent23

How does one go about removing the fonts they do not want

The fonts are located in usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/fonts of the system partition. You can access this partition for instance by script files, which you can start for instance by fmon, KoboLauncher, Kobo Start Menu, or by modifying the rcS script. You can access them also using telnet. The Kobo Start Menu also contains a small terminal simulator, which could do the job.

The other way is to prepare a KoboRoot.tgz that contains the path usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/fonts, and to put there empty files with the names of the font files you want to get rid of. Then copy the KoboRoot.tgz to the .kobo folder. You can find the font names by inspecting one of the more recent update files (cf. the sticky Direct Links to Kobo Firmware).

Quote:

Originally Posted by violent23

and how will this effect the Document Default setting if/when all system fonts are removed and only custom fonts remain?

I don't know. In any case I would not delete Avenir and Georgia, because these two fonts and Gothic, are the only fonts that nickel loads at start up. If you delete Avenir and Georgia, you might possibly be left with an interface without visible captions. If Gothic is still there, some models might use this font. (If you want to test it, a factory reset will bring you back to normal, if anything happens.) The other fonts don't become available to the interface unless you open the font settings menu, or if you open a kepub that has a certain font assigned to it, this font becomes available to the interface.

mattington · 05-27-2014, 09:18 AM

Quote:

The fonts are located in usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/fonts of the system partition.

tshering: You da man.

Thanks for this little tip and all the work you've done hacking the Kobo and making it a much more enjoyable device to own. Cheers!

violent23 · 05-27-2014, 09:43 AM

Quote:

Originally Posted by tshering

The fonts are located in usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/fonts of the system partition. You can access this partition for instance by script files, which you can start for instance by fmon, KoboLauncher, Kobo Start Menu, or by modifying the rcS script. You can access them also using telnet. The Kobo Start Menu also contains a small terminal simulator, which could do the job.

The other way is to prepare a KoboRoot.tgz that contains the path usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/fonts, and to put there empty files with the names of the font files you want to get rid of. Then copy the KoboRoot.tgz to the .kobo folder. You can find the font names by inspecting one of the more recent update files (cf. the sticky Direct Links to Kobo Firmware).

I don't know. In any case I would not delete Avenir and Georgia, because these two fonts and Gothic, are the only fonts that nickel loads at start up. If you delete Avenir and Georgia, you might possibly be left with an interface without visible captions. If Gothic is still there, some models might use this font. (If you want to test it, a factory reset will bring you back to normal, if anything happens.) The other fonts don't become available to the interface unless you open the font settings menu, or if you open a kepub that has a certain font assigned to it, this font becomes available to the interface.

Ah okay good to know. Mainly I was just trying to hide the fonts that are broken on the Aura with the custom (shorter) footer patch but seeing how the system is dependent on some of these I may just stick to the stock footer size. I do really appreciate everyone's patience to explain all of these aspects of the system though as I find it very interesting and enlightening.

makara · 05-27-2014, 12:15 PM

On my Aura HD after installing patches from the first message stopped opening book fb2. On "clean" firmware books in fb2 can be read.

GeoffR · 05-27-2014, 06:25 PM

Quote:

Originally Posted by violent23

I see you say in post #124 that you found a way but that it hid some custom fonts as well. If this is the only way to remove the fonts that do not work correctly on the Aura with your custom footer I am willing to test and see if it hides any of my custom fonts. Of course I would need a way to keep Avenir for the Document Default.

Here is a patch to remove "non-system" fonts from the selection menu.

Firmware 3.3.0:

Spoiler:

Firmware 3.3.1:

Spoiler:

I don't have many sideloaded fonts to test with, but from what I can tell the "system" fonts include the built-in fonts Amasis, Avenir, Caecilia, Georgia, Gill Sans, Kobo Nickel, Malabar, and some sideloaded fonts such as Times New Roman which were included in older firmware versions. The "non-system" fonts are everything else: Gothic, Ryumin, OpenDyslexic, Dyslexie, and other sideloaded fonts such as Dark Courier.

Note that Document Default is not a font, selecting it just tells the reader to to use whatever fonts are specified in the book itself, possibly embedded fonts. If the book doesn't specify any font then it uses a default font, which on the Glo seems to be Georgia for the body and Gothic for the header/footer.

GeoffR · 05-27-2014, 06:32 PM

Quote:

Originally Posted by makara

On my Aura HD after installing patches from the first message stopped opening book fb2. On "clean" firmware books in fb2 can be read.

I had no idea Kobo devices could even read fb2 books at all. All I can suggest is to enable each patch that you want to use one at a time, to find out which one is causing the problem.

makara · 05-28-2014, 12:11 PM

My Kobo Aura HD with firmware 3.2.0 and 3.3.0 (no patches) reads fb2, creates collections

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Firmware Update Instructions and the latest Firmware Versions	mitchwah	Ectaco jetBook	113	10-24-2023 09:02 PM
Touch Patching nickel to leave the wifi active	schlecky	Kobo Developer's Corner	4	01-23-2017 11:46 AM
Instructions for patching firmware 3.2.0	DNSB	Kobo Developer's Corner	66	12-05-2014 07:28 AM
Instructions for patching firmware 3.1.1	GeoffR	Kobo Developer's Corner	64	04-18-2014 01:23 PM

05-27-2014, 05:17 AM	#123
mattington Member Posts: 12 Karma: 10 Join Date: Mar 2014 Location: Charlotte, NC (USA) Device: Kobo Aura 6"	I just applied the patch to my Aura 6" running 3.3.0, but there are still several system fonts showing up in my font menu, namely: Gothic, Ryumin, Dyslexie, OpenDyslexic Particularly the Dyslexic fonts are quite annoying as I'll never use them... any idea why these still appear?

05-27-2014, 12:15 PM	#132
makara Connoisseur Posts: 79 Karma: 10000 Join Date: Jul 2012 Location: Israel Device: KA1, KLH2O, Oasis 3	On my Aura HD after installing patches from the first message stopped opening book fb2. On "clean" firmware books in fb2 can be read.

05-28-2014, 12:11 PM	#135
makara Connoisseur Posts: 79 Karma: 10000 Join Date: Jul 2012 Location: Israel Device: KA1, KLH2O, Oasis 3	My Kobo Aura HD with firmware 3.2.0 and 3.3.0 (no patches) reads fb2, creates collections

Advert

Advert