Bug 326088 - KFontComboBox::setCurrentFont() does not work with fonts those names include foundry
Summary: KFontComboBox::setCurrentFont() does not work with fonts those names include ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdeui (show other bugs)
Version: 4.11.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-16 10:12 UTC by Eugene Shalygin
Modified: 2023-01-30 05:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Illustration of the problem and fix (650 bytes, patch)
2013-10-16 10:17 UTC, Eugene Shalygin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Shalygin 2013-10-16 10:12:17 UTC
I have many fonts installed from two different sources:  font packages and TeXLive  font- packages. These fonts are visivle to me as fonts havind different foundries. Any of these can not be selected in KFontComboBox via setCurrentFont() call.

Reproducible: Always




Do not know is it change of QFontInfo behaviour after  KFontComboBoxPrivate was written, but QFontInfo reports family name without foundry. Therefore KFontComboBoxPrivate::updateIndexToFont() can not find the font name in its list. Removing QFontInfo call solves the problem for me.
Comment 1 Eugene Shalygin 2013-10-16 10:17:04 UTC
Created attachment 82875 [details]
Illustration of the problem and fix
Comment 2 Eugene Shalygin 2013-10-16 10:40:51 UTC
Forgot to mention that I'm using Qt 4.8.5
Comment 3 Christoph Feck 2013-10-23 16:19:11 UTC
From looking at the patch, I would say this should be fixed in Qt? Or is there a reason, why using QFontInfo discards foundry information?
Comment 4 Eugene Shalygin 2013-10-23 17:01:37 UTC
Does it mean then that QFontInfo is used to find a match for the requested font (as `fc-match`)?
Comment 5 Andrew Crouthamel 2018-11-10 03:14:41 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-11-20 03:59:45 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Justin Zobel 2022-12-31 00:24:18 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 8 Bug Janitor Service 2023-01-15 05:11:31 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2023-01-30 05:08:09 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!