![]() |
#1 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
kobopatch users & non-Kobo-supported languages
A few days ago this post by Vetchy started me thinking a bit more about the day-to-day problems of Kobo users who's native language is not one of those currently supported by Kobo.
I have since spent a bit of time digging around in the GUI-related bits of the firmware, trying to understand it better. I've also tried to answer a few other language-related queries. Some of those were dictionary-related which is NOT what I want to discuss in this thread. What I'd like to discuss here is the general Kobo GUI. The main problem appears to be that the 2 main Kobo system fonts Georgia (serif) and Avenir (sans-serif) are not well-suited to some languages, Avenir in particular. The default fallback font used when Avenir is inadequate (probably one of the CJK fonts) is not good either. I'm going to assume that those of you who find the GUI unsatisfactory have at least managed to sideload one good font which makes reading your books tolerable. Otherwise you'd presumably have bought a better eink device by now, right? ![]() If we wait for Kobo to package better unicode system fonts we may be waiting a long time - possibly licensing cost is an issue. So I'd like to see if there's anything we can do to improve things using your sideloaded 'good' fonts and the current kobopatch system. There may not be a single "quick fix" so, what I'd like to know is, which parts of the GUI need early attention. vostro here suggested the various Book lists would be a good start. This is your opportunity to have a say. To make progress I will also need the help of experienced kobopatch users who are willing to beta test any new patch ideas and report back here in a "timely" manner. By "timely" I mean responding in <24hours, not weeks between posts. There may not be a 100% perfect solution but I hope it's worth a try. ![]() I wait to hear whether there are enough willing volunteers to get started. Here is a summary of findings, post #63 Last edited by jackie_w; 10-03-2019 at 06:35 PM. Reason: Added link to summary |
![]() |
![]() |
![]() |
#2 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
I've paraphrased these notes from one of my posts in the kobopatch request thread. I may need to refer to them later in this thread.
Important general info about customising font-family in the Kobo GUI. It is particularly relevant to users who mainly read standard epubs rather than kepubs. After a full reboot, as far the GUI is concerned, the Kobo only has immediate access to a limited number of its built-in fonts, Georgia, Avenir and possibly one or more of the CJK fonts. The rest of its built-in fonts and all your sideloaded custom fonts are only loaded "as necessary". I don't know the exact rules, only what I've observed. After a full reboot I've always found that the following will force the Kobo to access all fonts. You won't have these problems if you only put the Kobo to sleep.
N.B.: *** Update for firmware 4.21.15015+ *** It is now possible to avoid having to do the above after every reboot. See the *** Update in the post #63 Summary for more details. Last edited by jackie_w; 05-26-2020 at 04:54 PM. Reason: updated info for fw 4.21.15015 |
![]() |
![]() |
Advert | |
|
![]() |
#3 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,785
Karma: 6990707
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
|
reserved for myself
|
![]() |
![]() |
![]() |
#4 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 83
Karma: 15734
Join Date: Dec 2016
Device: Scribe,Elipsa,PWSE,FORMA,KOA2,KV,KA1, KAH2O, PW1-4, KA, AKT,
|
thanks a lot jackie for getting this start, i have forma, aura one and kobo H2O running latest patched version and am willing to test new patched version regarding to this feature and report back asap.
|
![]() |
![]() |
![]() |
#5 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
![]() Can I ask:
|
|
![]() |
![]() |
Advert | |
|
![]() |
#6 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 83
Karma: 15734
Join Date: Dec 2016
Device: Scribe,Elipsa,PWSE,FORMA,KOA2,KV,KA1, KAH2O, PW1-4, KA, AKT,
|
after some test, only sideloaded CD2000 font solved the missing content in some dictionaries(the only hack I used is changing dictionary font). although kobo added trational chinese(which is my native language) in recent version, the booklist still has some missing content.
|
![]() |
![]() |
![]() |
#7 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
My hope was to try to start with simpler left-to-right horizontal languages, e.g. those who use the Cyrillic alphabet or perhaps Vietnamese. Sorry to disappoint. |
|
![]() |
![]() |
![]() |
#8 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 83
Karma: 15734
Join Date: Dec 2016
Device: Scribe,Elipsa,PWSE,FORMA,KOA2,KV,KA1, KAH2O, PW1-4, KA, AKT,
|
if you could just patch the UI font replaced by customized name assuming you could decrypt the related font name and path, it would be sufficient I guess. you don't need to recognize the correctness of content of text as that's tester's job.
|
![]() |
![]() |
![]() |
#9 |
Evangelist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 469
Karma: 600816
Join Date: Sep 2009
Device: Kobo Aura HD, Kobo Aura One
|
I think I can turn my Aura HD into a test device, assuming it'll take a charge, boot up and update — will get back on that. Can test Cyrillic. What I've done for it is side-load the version of Amasis from Nook. I'm really curious to see how that works since it's the same as the built-in one. I used to remove the built-in version but I no longer do that, so both co-exist.
|
![]() |
![]() |
![]() |
#10 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
@dmapr,
Thanks for responding. I used my old abandoned AuraHD for the same purpose. ![]() I've attached a simple patch which works on the biggest CSS stream in nickel which handles all the basic GUI widgets. It will change all occurrences of Georgia and Avenir to use whatever sideloaded font(s) you specify in the patch. N.B.: I have tried this myself so I don't think there's much risk involved (but still a good idea to test on a device you don't use much). To begin with, it might be an idea to set up your kobopatch.yaml file so that this patch is the only one installed so as not to confuse matters. After you've installed the patched KoboRoot.tgz, and the Kobo has rebooted don't be at all surprised if you don't see your new font on the Home screen. At least some of the Home screen widgets are not affected by this patch, they are in a different CSS stream. In addition, if you haven't already, please read post #2. You need to force the Kobo to load all its fonts (built-in and sideloaded). Once you've done that, the best place to check whether it was successful is in the My Books book list. I believe most (all???) its widgets will be affected by the patch, if the patch has worked. In this patch all the usual Kobo fontname rules apply:
Change the blue bit to your new sans-serif font of choice, but do not remove the ',Avenir' after it. If you want an easy life you could use your Amasis name for both the Replace strings. It would give the GUI a more uniform look. Put in nickel.yaml (or wherever you normally put your customised nickel patches): Code:
Custom GUI system fonts beta1: - Enabled: yes - Description: Change font-family of basic GUI widgets - FindZlib: "QWidget[smallIconHeight=true][qApp_deviceIsTrilogy=true]" - ReplaceZlibGroup: Replacements: - {Find: "font-family: Georgia;", Replace: "font-family:your_serif_name,Georgia;"} - {Find: "font-family: Avenir;", Replace: "font-family:your_sans_name,Avenir;"} Last edited by jackie_w; 09-30-2019 at 09:56 AM. Reason: typo |
![]() |
![]() |
![]() |
#11 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
I don't know enough about fonts to pursue replacing the physical system UI fonts. If you had asked me yesterday I would have said that it was not even possible because of their encryption. However, earlier today, someone posted elsewhere in the Kobo forums that they had done precisely that to fool the Kobo into thinking their hacked Arial font was Georgia so they could read Vietnamese. I've done a bit more thinking about using kobopatch with the 'special case' Chinese font. I think it would be quite easy to create a patch very similar to dmapr's in post #10, but targeting the CSS for Chinese fonts rather than Georgia/Avenir. Kobo's nickel CSS streams are packed with code similar to this (82 in fact): Code:
DisplayLabel[localeName="zh"] { font-family: Sans-SerifZH-Traditional, sans-serif; font-style: normal; } DisplayLabel[localeName="zh-HK"] { font-family: Sans-SerifZH-Traditional, sans-serif; font-style: normal; } DisplayLabel[localeName="zh-TW"] { font-family: Sans-SerifZH-Traditional, sans-serif; font-style: normal; } Code:
font-family: Sans-SerifZH-Traditional, sans-serif; Code:
font-family: CD2000, sans-serif; I'm assuming, but don't know, that the 'sans-serif' fallback font above is Kobo's built-in 'Kobo UD Kakugo'. My concerns are:
Another, less risky, way forward would be for me to prepare a patch which only targets one small part of the GUI, e.g. the Book title in the My Books book list. We could try that as a first step if you want. What do you think? |
|
![]() |
![]() |
![]() |
#12 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 83
Karma: 15734
Join Date: Dec 2016
Device: Scribe,Elipsa,PWSE,FORMA,KOA2,KV,KA1, KAH2O, PW1-4, KA, AKT,
|
thanks a lot for the help, as i'm not sure if the bricked kobo could be revived without need of opening the case(with models what i have mentioned plus kobo aura which is not patched--they are all not easy to get case opened--and UI font i set should be zh-TW), i prefer less risky approach you said:"prepare a patch which only targets one small part of the GUI, e.g. the Book title in the My Books book list." thanks again.
Last edited by vostro; 09-30-2019 at 01:53 PM. |
![]() |
![]() |
![]() |
#13 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
You do accept that I still can't make any guarantees about what will happen? This is new ground for all of us. |
|
![]() |
![]() |
![]() |
#14 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,785
Karma: 6990707
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
|
Quote:
|
|
![]() |
![]() |
![]() |
#15 | |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 83
Karma: 15734
Join Date: Dec 2016
Device: Scribe,Elipsa,PWSE,FORMA,KOA2,KV,KA1, KAH2O, PW1-4, KA, AKT,
|
Quote:
|
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
PRS-T1 Support for FB2 format, folders & non-Latin languages? | boren | Sony Reader | 8 | 08-08-2023 12:43 PM |
Oddball writing systems & Non-ISO 639-2 Languages | Fiat_Lux | Library Management | 0 | 10-31-2014 01:35 PM |
Fonts supported by K4 & KT | ElMiko | Amazon Kindle | 28 | 09-05-2012 03:19 PM |
Touch Ad-supported Kobo Touch? | FJames | Kobo Reader | 6 | 11-25-2011 08:26 PM |
TOPAZ & Other Languages | molochei | Kindle Developer's Corner | 1 | 06-06-2008 06:57 AM |