![]() |
#1 |
Onyx-maniac
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,688
Karma: 15675331
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
|
![]()
Onyx uses their own sans-serif fonts in preference to Roboto (the standard by Android).
Those fonts are OnyxCustomFont-EN-Regular.otf and OnyxCustomFont-EN-Bold.otf Internally, they are named "Source Hans Sans". Their use is indicated in /system/etc/fonts.xml You may not have noticed anything goofy unless you have something that uses u2019 (right single quotation mark) which is sometimes used (wrongly, I think) for possessives or contractions. The font generates a slanted squiggle, but then gives about 2 blank spaces to the right. Has anybody run into this? Do you care? Do you feel like complaining? Me, I'm just going to dump the Onyx fonts. (The example was done in Libre Office on a PC using the Onyx font.) |
![]() |
![]() |
![]() |
#2 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,498
Karma: 5000046
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
|
I didn't encounter this issue, but yesterday I just "magisk-replaced" the Roboto fonts by another font and it worked ok! I used a package with all sorts of variations of Roboto.
|
![]() |
![]() |
![]() |
#3 |
Onyx-maniac
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,688
Karma: 15675331
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
|
You shouldn't goof around renaming fonts.
You should just edit /system/etc/fonts.xml and keep the fonts named what they are. Fixed. |
![]() |
![]() |
![]() |
#4 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,498
Karma: 5000046
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
|
I hope the magisk font package is safe. What they’ve done is to rename the font to Roboto in all variations. So the font is named correctly in filename and font name
![]() |
![]() |
![]() |
![]() |
#5 | |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 977
Karma: 2209358
Join Date: Nov 2011
Location: London, UK
Device: Kobo Aura, Kobo Aura ONE, PocketBook InkPad Color 3
|
Quote:
Wikipedia suggests the use of U+2019 for possessives and contractions is preferred over U+0027 which for me has always been a "straight" apostrophe. I'd report this to Onyx, because it really ruins their typography. |
|
![]() |
![]() |
![]() |
#6 |
Onyx-maniac
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,688
Karma: 15675331
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
|
Most of you haven't noticed this because undoubtedly you've been wasting all your time reading books in your favorite (non-Onyx) font.
There is an additional problem with this whole setup. There are these RobotoFake.. fonts that are the first choice for a system sans-serif font. They have widths and kerning but no actual glyphs. I haven't run into this before but apparently they're in there for efficiency. Normally the second choice would be the normal Roboto... fonts. The way this should work is when doing layout or ellipsising. You ask Android, "How many pixels wide is 'my test message'?" Android consults RobotoFake... and says, "112 pixels exactly". You say, "Ok, I have room, draw it." Android needs the glyphs to draw, consults normal Roboto..., draws it, then says, "Hey that was actually 112 pixels!" Unfortunately, Onyx made their fonts the second choice and even the widths of normal characters are not going to be the same as what RobotoFake... said. This could exhibit itself as even normal text not fitting (or maybe ellipsising?). There are two clean ways of fixing this in /system/etc/fonts.xml:
The additional example below has no space characters inserted. Last edited by Renate; 12-27-2022 at 06:29 AM. |
![]() |
![]() |
![]() |
#7 |
Junior Member
![]() Posts: 1
Karma: 10
Join Date: Jan 2023
Device: Boox Leaf 2 and Nova Air C
|
I've created a Magisk Module to fix the unicode quote spacing issue: https://github.com/sargunv/magisk-onyx-font-fix/
The tweak eliminates RobotoFake, and sets the underlying fallback font family (mix of Roboto and OnyxCustomFont-EN) as the new default sans-serif. If you've rooted your device, you can try installing that. Tested on a Leaf 2. |
![]() |
![]() |
![]() |
#8 |
Ebook fanatic since 1962
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 92
Karma: 3033
Join Date: Apr 2008
Location: By the sea in Southern England
Device: Cybook3/REB1100/Kolin/iRex iLiad/JetBook & JB Mini/Onyx C67, T68.
|
I have the problem - but wottinell's Magisk?
Don't answer - with luck Google is my friend, but I may be back. |
![]() |
![]() |
![]() |
#9 |
Onyx-maniac
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,688
Karma: 15675331
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
|
Magisk is a method to give you root (administrative access to your device).
A side effect is that it allows you to override files that you can't just easily replace. The first requirement is that you get a copy of your boot image. Then you install and use the Magisk application to transmute that boot image. Then you replace your current boot image. Finally you do what you really wanted, use the Magisk module in the previous post to fix your device. Look here for "rooting with Magisk". |
![]() |
![]() |
![]() |
Tags |
fonts apostrophe unicode |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Adding fonts to Onyx Boox Poke 3 | Waylander | Onyx Boox | 5 | 08-14-2021 07:24 AM |
Classic Goofy things happening on screen... | VACaver | Barnes & Noble NOOK | 2 | 10-15-2010 06:39 AM |
Goofy IOS 4 questionS | Maggie Leung | Apple Devices | 26 | 07-16-2010 12:34 PM |
Onyx boox 60, is it possible to read czech fonts? | messenger | Alternative Devices | 0 | 06-15-2010 11:50 AM |
Goofy titles in pdf metadata... | TheDragonMaster | Sony Reader | 3 | 10-31-2007 05:13 PM |