Bug 184418 - font dialog: font names are not sorted correctly
Summary: font dialog: font names are not sorted correctly
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-15 16:49 UTC by Maciej Pilichowski
Modified: 2023-01-05 05:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2009-02-15 16:49:50 UTC
Version:            (using KDE 4.2.0)
Installed from:    SuSE RPMs

I am configuring fonts for KDE4 and I see the list:
Sans Serif
Serif
Monospace
1980 Portable
256 Bytes
6809chargen
Abberancy
...
Comment 1 FiNeX 2009-02-15 17:17:31 UTC
Can you check the filename of the fonts? It could be that the font list is sorting per file name...
Comment 2 Pino Toscano 2009-02-15 17:54:38 UTC
It looks like it is wanted, so the generic aliases
> Sans Serif
> Serif
> Monospace
are always on top.
Comment 3 Maciej Pilichowski 2009-02-15 21:01:38 UTC
But there is no hint, no nothing that there are some kind of meta fonts -- aliases. Anyway, the issue is still valid -- the names should be sorted, otherwise it is really hard to manage anything that starts with "s" or "m". Besides, there could be more aliases, so the problem would only be more difficult to handle.
Comment 4 Andrew Crouthamel 2018-11-02 04:21:25 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 5 Andrew Crouthamel 2018-11-16 02:37:39 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?

Thank you for helping us make KDE software even better for everyone!
Comment 6 Justin Zobel 2022-12-06 00:56:58 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 7 Bug Janitor Service 2022-12-21 05:18:22 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 8 Bug Janitor Service 2023-01-05 05:27:31 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!