FYI - macOS 26 (Tahoe) issue

[MikeMaloney]

This is just a heads up. (And I hope I'm not stepping out of line.)

I don't know where in the development cycle any new OS gets built against,
but the preview panel doesn't render correctly with macOS 26 (beta 3).

Text is rendered as a question mark inside a box. (attached)

(and to further the discussion of icons on the mac, they changed the look yet again.)

Cheers and thanks for the good work.

[MikeMaloney]

More data:

I opened an e-pub file that has embedded fonts and they render correctly.

So ... is it possible Apple moved the OS fonts and Sigil is looking in the wrong place?

[KevinH]

From your photo, BookBrowser shows no embedded fonts. Please post the linked css stylesheet so that we can see what font they are trying to load. My guess is the font does not exist on your mac, and it is replaced by a font made of graphics. Notice that the fonts inside CodeView work just fine.

Or simply try another epub without embedded fonts (that never got loaded).

It could also be related to the font being chosen by Preview simply is broken.
Check out Sigil Preferences Appearance and look at the Preview tab. It uses pulldowns to specify fonts to be used if not set in CSS. Try changing those fonts.

[MikeMaloney]

The attached pic shows the default epub that is presented when I open the program.

I also opened the epub that the first pic came from and if I launch PageEdit from that project, it renders the section correctly.

I've also attached the css file, though I think the issue is with Preview.

Cheers

[KevinH]

Did you try changing the Preview font Preferences in Sigil Preferences under the Appearance, the use the Preview Tab, just like in your picture? Try changing all fonts in that setting.

The default epub when opened has no text in it to display in Preview. Try typing somethind into codeview inside the p tag. Then try changing the fonts in Sigil Preferences.

And finally try editing the css used in the epub shown in your original photo and removing the following entry completely from it as it sets a font variant that may not exist in the chosen font for Preview.

body {
  margin-left: 10%;
  margin-right: 10%;
  text-align: justify;
  font-kerning:normal;
  font-variant: common-ligatures oldstyle-nums proportional-nums;
  font-feature-settings: "kern", "liga", "clig", "onum", "pnum";
  font-family: serif;
  font-size: 1em;
  line-height: 1.5;
}

Please let me know what you find.

[Doitsu]

Originally Posted by MikeMaloney

I've also attached the css file, though I think the issue is with Preview.

There's a slight chance that UTF-8 encoding errors are causing the display problems.
Could you also please attach the HTML file that you used for the test?
(AFAIK, the Thomas Jefferson Bible is in the Public Domain.)

[MikeMaloney]

No joy.

I added text to the default document and changed the preview fonts.
The pic shows the same behavior.
I also opened the other epub that has a custom CSS file and deleted the section you suggested with no change in the preview window.

[KevinH]

Once you change the fonts in Preferences would you please try saving and exiting preferences and then quit out of Sigil completely and restart Sigil to make 100% sure Preview is using your new selections.

But it is very strange that Preview only works with embedded fonts, whereas CodeView works just fine. They would use the exact same Qt font server!

[KevinH]

I did look at the QT Bugs related to macOS26 beta but as far as I can tell, they are working on it but there is no official support for it (yet).

According to many MacOS sites even macOS26 Beta 4 exhibits lots of problems. It is not yet ready for prime time. I typically stay one full macOS release back (I am running the latest Sonoma version now) just to keep my development and personal machines really stable.

It is also strange that PageEdit works but Preview does not as they share lots of code.

One last thing to try ...

go to Sigil preferences and disable gpu acceleration and then save and quit out of Sigil and then restart to see if that impacted anything?

[MikeMaloney]

Apple dropped a new beta version last night, so I'm gonna put this on the back burner at least until a release candidate drops.

I'm comfortable using PageEdit for the time being. (No sense in potentially playing whack-a-mole.)

I did try your suggestions and they had no effect.

Cheers