![]() |
#16 |
Sigil Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 8,019
Karma: 5449552
Join Date: Nov 2009
Device: many
|
Unfortunately, fonts and font foundries are idiosyncratic that way. One may draw a font and give it a font weight of 650 or 750 and call it "bold" while others call weights with 700 normal. The font engine and browser determine the mappings from numeric weights to descriptive terms and not everyone agrees. Qt has its own. Most times the definitions are similar and things work but sometimes not. It was worse in the old days when font metric info was stored in a second file.
If in doubt on Linux, fire up FontForge to get a full readout of what the font metadata and metrics actually say. |
![]() |
![]() |
![]() |
#17 | |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 696
Karma: 150000
Join Date: Feb 2010
Device: none
|
Quote:
in the end, I have Sigil 2.1.0 with Qt 5.15.30 and as for the preview problem it behaves just like Sigil 1.9.30 So I guess this confirms it's nothing wrong with Sigil itself; but I'm not sure I have exactly the same fonts installed on both machines. BTW if a font substitution is made, is there any way to tell what font it decided to use? I always code a fall-bac font of, say, "serif" in any font specifications, and that has always worked before now ( and still does on other epub readers AFAIK). again, using the same file on both machines, I get the following: Albert |
|
![]() |
![]() |
Advert | |
|
![]() |
#18 | |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 696
Karma: 150000
Join Date: Feb 2010
Device: none
|
SOLVED!
In my first post, I wrote: Quote:
After closely examining the inspector's "computed styles" column, I noticed that the rendered font was "aakar," which I think was a leftover from an over-zealous installation of foreign-language fonts by LibreOffice. In contrast, on the machine that WAS displaying correctly, the rendered font was Times New Roman. So on the problem machine, I deleted the "aakar" font. Now the rendered font became "Noto Serif" which behaves as expected with no modifications to the epub's CSS (e.g. changing font-weight: to 900 instead of "bold") Many thanks to all the commentators for giving me the clues I needed! Albert |
|
![]() |
![]() |
![]() |
#19 |
Sigil Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 8,019
Karma: 5449552
Join Date: Nov 2009
Device: many
|
Glad to hear you got it working! And thanks for showing how to fix it!
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Note preview disabled? | franklekens | Kobo Reader | 7 | 11-15-2019 08:54 AM |
Preview/Book View and Stylesheet Errors | ChrisI | Sigil | 10 | 08-08-2018 12:39 AM |
User agent stylesheet: a proposal | roger64 | Editor | 4 | 12-27-2014 02:00 AM |
uninvited "user agent stylesheet" | roger64 | ePub | 2 | 12-26-2014 07:50 PM |
User agent | DigitalDuke | enTourage Archive | 3 | 06-04-2010 03:20 PM |