https://bugs.kde.org/show_bug.cgi?id=378523
--- Comment #23 from RJVB <rjvber...@gmail.com> ---
Probably a redundant observation, but doing something like
QSettings().setValue("font", font)
instead of
QSettings().setValue("font", font.toString())
saves the font in the legacy way, without the problematic stylename extension.
To react to Nate's remark: all required information IS already contained in the
fontspec string, esp. weight is represented as a standardised numerical value
(e.g. 63 = medium/semibold, regular is 57, bold is 75). Qt does have some
remaining issues with the less usual weights (AFAICT) and saving the exact
stylename could help. The problem is that this is font-specific: some fonts
have Medium where others call that Semibold (in all kinds of spellings) or even
demi-bold - which is how other fonts call their actual bold face. So a
canonical stylename shouldn't be inherited, should be regenerated on the fly
when queried and should be overridden by any of the other methods of changing
how a font looks (other than size).
It's of course possible that Qt only have to fix their QFont::setBold()
implementation but they will almost certainly not do that in all affected
(older) versions.
--
You are receiving this mail because:
You are watching all bug changes.
