08-01-2015, 11:20 PM | #61 |
Wizard
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
|
08-01-2015, 11:49 PM | #62 | |
Wizard
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Quote:
You can find the addresses using a hex editor or the 'strings' command which comes with the GNU binutils package. Alternatively, if the strings are unique, you can let the patch locate them automatically by using find_base_address and then using adresses relative to the base address. for example if you want to change the string abcdef to abcxyz then this patch would do it automatically for any firmware version where the string was unique: Code:
<Patch> patch_name = `Example` patch_enable = `yes` find_base_address = `abcdef` replace_string = 0003, `def`, `xyz` </Patch> However if the strings are compressed then you need to use tsherings tools, because I haven't added that feature to the patch32lsb program yet. Here is an example of one of the patches you linked to (firmware 3.12.1): Code:
<patch> name=Header (Touch) enabled=true action=replace_string position=E163FC oldpart=* {\nfont-size: 16px;\nfont-family: Avenir;\nbackground-color: transparent;\npadding-top:3px;\n}\n\n oldpart=[qApp_localeName="ja_JP"] {\nfont-family: A-OTF Gothic MB101 Pr6N;\nqproperty-leading: 0;\n} newpart=* {\nfont-size: 28px;\nfont-family: Arial;\nbackground-color: transparent;\npadding-top:3px;\n}\n\n newpart=[qApp_localeName="ja_JP"] {\nfont-family: A-OTF Gothic MB101 Pr6N;\nqproperty-leading: 0;\n} combineparts </patch> Code:
<patch> patch_name = `Header (Touch)` patch_enable = `yes` replace_string = E163FC, `* {\nfont-size: 16px;\nfont-family: Avenir;\nbackground-color: transparent;\npadding-top:3px;\n}\n\n[qApp_localeName="ja_JP"] {\nfont-family: A-OTF Gothic MB101 Pr6N;\nqproperty-leading: 0;\n}`, `* {\nfont-size: 28px;\nfont-family: Arial;\nbackground-color: transparent;\npadding-top:3px;\n}\n\n[qApp_localeName="ja_JP"] {\nfont-family: A-OTF Gothic MB101 Pr6N;\nqproperty-leading: 0;\n}` </patch> Last edited by GeoffR; 08-02-2015 at 12:33 AM. Reason: added example |
|
Advert | |
|
08-02-2015, 02:12 PM | #63 |
Resident Curmudgeon
Posts: 73,983
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Thanks. I'm trying to decide if I want to go with 3.16.0 or 3.16.10. But without the patches, 3.16.10 is a no go. I'm not in a hurry.
|
08-02-2015, 04:28 PM | #64 |
Bibliophagist
Posts: 35,401
Karma: 145435140
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
If you want any help testing, I've put 3.16.10 on a Glo (original). Not much difference in operation from 3.16.0.
|
08-02-2015, 06:37 PM | #65 |
Bookworm
Posts: 975
Karma: 768585
Join Date: Aug 2010
Location: Netherlands
Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo
|
Wrong topic,delete please.
Last edited by Nick_1964; 08-04-2015 at 09:21 AM. |
Advert | |
|
08-04-2015, 09:19 AM | #66 |
Junior Member
Posts: 2
Karma: 10
Join Date: Aug 2015
Device: Kobo Glo HD
|
Confuse
I get confused like "outlandos" before. I have the Kobo Glo Hd with 3.15.0. I want update to 3.16.0. But why I need 3.16.0 before I install 3.16.0? Need I install another 3.15.0 before? Or what this mean?
|
08-04-2015, 10:04 AM | #67 | |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
Quote:
You need firmware 3.16.0 before you can install/apply a patch to firmware 3.16.0. |
|
08-09-2015, 03:33 AM | #69 |
Wizard
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Default ePub monospace font
The EPUB reader tries to use the Adobe "CourierStd" font when font-family:monospace is encountered, but it uses the wrong pathnames and that font is not supplied with Kobo devices anyway, and so the default reading font gets used even if it is not monospaced (i.e. Georgia is used if "Publisher Default" is selected.)
This patch makes the EPUB reader use a font named "Courier" (or beginning with "Courier") as the default monospace font. You can change "Courier" in the replacement string to another name if you wish, but it must be no more than 7 characters long. For example the free Courier Prime font can be used, just rename the files "Courier Prime.ttf" "Courier Prime-Italic.ttf" "Courier Prime-Bold.ttf" "Courier Prime-BoldItalic.ttf" as usual for sideloaded fonts. This patch should work on any firmware from version 3.3.0 onwards, but I've only tested it with firmware version 3.16.0. `Default ePub monospace font (Courier)` patch (paste into librmsdk.so.1.0.0.patch): Spoiler:
Edit: After further testing it appears that the font names don't have to match exactly, they just have to start with the name in the patch. So the patch above will work with any sideloaded font that has a name beginning with "Courier", I've edited the description above to reflect this discovery. Below is the same patch modified to work with HP's free "Dark Courier" font. `Default ePub monospace font (Dark Courier)` patch (paste into librmsdk.so.1.0.0.patch): Spoiler:
Edit2: The patch itself seems to work okay if there are multiple fonts beginning with "Courier", whichever one the Kobo firmware happens to choose gets used as the default monospace font. However the EPUB reader seems to have problems selecting a font from the dropdown menu if it has a name that is the prefix of another font name. I found that if I had both "Courier Prime" and "Courier Prime Sans" fonts on my Glo, I could not select "Courier Prime", I just got "Courier Prime Sans" when I tried. Both fonts worked fine if the other was not present. Last edited by GeoffR; 08-10-2015 at 05:57 AM. Reason: Problem with font names that are a prefix of another font name. |
08-09-2015, 07:19 AM | #70 |
Bookworm
Posts: 975
Karma: 768585
Join Date: Aug 2010
Location: Netherlands
Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo
|
I know the Lean and mean function is disabled in 3.16, does this one still counts in ?
ShouldDither=true |
08-09-2015, 11:25 PM | #71 |
Addict
Posts: 306
Karma: 679580
Join Date: Dec 2011
Location: Brisbane, Australia
Device: K3, K4NT, KPW2, Voyage, iP4, iP6, iPad Mini, HP TouchPad, Kobo Mini
|
I am running FW 3.16.0 and the latest patch set on my Mini, and I just wanted to say thank you to the developer(s), who have turned it into a well-nigh perfect reading device for me.
|
08-10-2015, 12:49 AM | #72 |
Bibliophagist
Posts: 35,401
Karma: 145435140
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
[QUOTE=GeoffR;3148112]The EPUB reader tries to use the Adobe "CourierStd" font when font-family:monospace is encountered, but it uses the wrong pathnames and that font is not supplied with Kobo devices anyway, and so the default font gets used instead (i.e. Georgia if "Publisher Default" is selected.)</QUOTE>
Thanks muchly! It also works for 3.16.10. |
08-10-2015, 06:08 AM | #74 | |
Bookworm
Posts: 975
Karma: 768585
Join Date: Aug 2010
Location: Netherlands
Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo
|
Quote:
Then again,maybe only for myself..why adding it.. work arounds that are tried,unsuccesful and abandoned ?? |
|
08-12-2015, 02:12 PM | #75 |
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
@GeoffR,
Re: Default ePub monospace font I've only just spotted this new patch for librmsdk.so.1.0.0.patch, so I just wanted to say In addition I was able to extrapolate to give myself a different default sans-serif font for standard ePubs. Personally I've always found the default Avenir a bit too chunky and I prefer my sideloaded Trebuchet for sans-serif. For anyone else who may be interested I include the extra patch I used below. Although it's early days it seems to work equally well on: - GloHD with fw 3.16.0 - AuraH2O with fw 3.15.0 Spoiler:
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Instructions for patching firmware 3.13.1 | GeoffR | Kobo Developer's Corner | 56 | 07-01-2016 09:59 AM |
Instructions for patching firmware 3.15.0 | GeoffR | Kobo Developer's Corner | 146 | 05-24-2016 06:10 AM |
Instructions for patching firmware 3.11.0 | GeoffR | Kobo Developer's Corner | 226 | 06-01-2015 05:32 AM |
Instructions for patching firmware 3.12.1 | GeoffR | Kobo Developer's Corner | 56 | 03-20-2015 05:14 AM |
Instructions for patching firmware 3.12.0 | GeoffR | Kobo Developer's Corner | 165 | 02-07-2015 09:22 AM |