Calibre, MS Shell Dlg 2 missing :(

[jmurphy]

Originally Posted by JSWolf

It is as I say because that's the font used when you select MS Shell Dlg 2. It's not because I say. It's how Microsoft has defined what font is used.

As usual, you are pretending that what is true for you is true for everybody.

It didn't always require a registry edit to change the system font. Why hasn't it occurred to you that the OP may have customized their fonts at some point in the past? And that perhaps QT6 isn't using that customization?
Or... Or... There can be any number of explanations....

But as usual, you are pretending that what is true for you is true for everybody.

[Lauraq]

I have not understood. I use Tahoma as a system font and when I discovered Caliber, the first font I tried was obviously Tahoma. I don't want to change my system font to have it on Caliber. Anyway it doesn't matter, sorry I bothered you, it's just that before this font was there and now it's gone and I thought it was possible to get it back but I understand it's difficult ... thanks to all the same

[jmurphy]

Originally Posted by Lauraq

I have not understood. I use Tahoma as a system font and when I discovered Caliber, the first font I tried was obviously Tahoma. I don't want to change my system font to have it on Caliber. Anyway it doesn't matter, sorry I bothered you, it's just that before this font was there and now it's gone and I thought it was possible to get it back but I understand it's difficult ... thanks to all the same

So do you remember what the "missing" font looked like? That's what really matters. The name is only important so that you know which font you liked.
So you could just try all the fonts in Calibre until you find one you like.

Part of the problem is that "MS Shell Dlg 2" is not a real font. It gets mapped to some other real font. But without knowing what the real font was, you cannot select it in Calibre.

[BetterRed]

Maybe this, from another Qt open source app, is relevant ==>> Wrong default GUI font under Windows | MuseScore

It contains a link to a Qt bug report.

That's as much as I know.

BR

[Lauraq]

Originally Posted by jmurphy

So do you remember what the "missing" font looked like? That's what really matters. The name is only important so that you know which font you liked.
So you could just try all the fonts in Calibre until you find one you like.

Part of the problem is that "MS Shell Dlg 2" is not a real font. It gets mapped to some other real font. But without knowing what the real font was, you cannot select it in Calibre.

it must be calibre to know which font he mapped ^_^
I can't know but I know Tahoma well and I can tell you it's not that

[JSWolf]

Originally Posted by Lauraq

it must be calibre to know which font he mapped ^_^
I can't know but I know Tahoma well and I can tell you it's not that

If MS Shell Dlg 2 is not Tahoma, why is the registry showing it is?

[Lauraq]

Originally Posted by JSWolf

If MS Shell Dlg 2 is not Tahoma, why is the registry showing it is?

why, in the old version of Calibre, there were both MS Shell Dlg 2 and Tahoma?

[JSWolf]

Originally Posted by Lauraq

why, in the old version of Calibre, there were both MS Shell Dlg 2 and Tahoma?

Because Tahoma is a font in it's own right and MS Shell Dlg 2 is just a name that translates into Tahoma. I don't know if you can change this other then editing the registry.

[Lauraq]

Originally Posted by JSWolf

Because Tahoma is a font in it's own right and MS Shell Dlg 2 is just a name that translates into Tahoma. I don't know if you can change this other then editing the registry.

So, summing up:

1 - MS Shell Dlg 2 was put, no one knows why, because it is the same as Tahoma

2 - I use Tahoma as a system font, I don't know how to recognize it and I didn't try it as the first font in calibre and I put another one identical to Tahoma without realizing that they were the same

Brilliant

[theducks]

Originally Posted by Lauraq

why, in the old version of Calibre, there were both MS Shell Dlg 2 and Tahoma?

Because WINDOWS advertised it had those.
The fonts Calibre USES are supplied by Windows. You will have similar issues IF you install (and use in Calibre) 'Rickity-old-typewriter', then move your library and settings to a new PC where that was NOT available.
FWIW None of my 3 Calibre installs offer MS Shell DLG2

IT IS (your) WINDOWS that changed, not Calibre. Thank MS for doing things outside of your control.

[Lauraq]

Originally Posted by theducks

Because WINDOWS advertised it had those.
The fonts Calibre USES are supplied by Windows. You will have similar issues IF you install (and use in Calibre) 'Rickity-old-typewriter', then move your library and settings to a new PC where that was NOT available.
FWIW None of my 3 Calibre installs offer MS Shell DLG2

IT IS (your) WINDOWS that changed, not Calibre. Thank MS for doing things outside of your control.

I don't know what Windows did, I know that Windows was there before and that when Caliber opened I had both fonts. Then I updated Calibre and the font disappeared. So, in my opinion, the problem is in Calibre that has changed something.

[theducks]

Originally Posted by Lauraq

I don't know what Windows did, I know that Windows was there before and that when Caliber opened I had both fonts. Then I updated Calibre and the font disappeared. So, in my opinion, the problem is in Calibre that has changed something.

If it WAS Calibre 6, reverting to 5.44 would fix it...

[PeterT]

If you read the link supplied by BetterRed you'd see that MicroSoft had made changes to system fonts and APIs years ago, and that QT was not using the APIs correctly. Try using the font Segoe UI instead of MS Shell DLG 2 and see if that matches what you remember.

Sent from my Pixel 4a using Tapatalk

[Lauraq]

Originally Posted by theducks

If it WAS Calibre 6, reverting to 5.44 would fix it...

you've tried? I no longer have version 5.44

[Lauraq]

Originally Posted by PeterT

If you read the link supplied by BetterRed you'd see that MicroSoft had made changes to system fonts and APIs years ago, and that QT was not using the APIs correctly. Try using the font Segoe UI instead of MS Shell DLG 2 and see if that matches what you remember.

Sent from my Pixel 4a using Tapatalk

Segoe UI font is completely different, just look at the photo I posted that you can see the type of font I used, very similar to Tahoma but different