Bug 243287 - KNewFileMenu: Improve template file format
Summary: KNewFileMenu: Improve template file format
Status: CONFIRMED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.48.0
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-06-30 21:42 UTC by Alexander Potashev
Modified: 2019-03-10 00:09 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Potashev 2010-06-30 21:42:39 UTC
Version:           4.4 (using KDE 4.4.4) 
OS:                Linux

File template .desktop files have only 2 entries with text: Name and Comment. The "Name" entry is used for the "New" menu item, and text in the "Comment" entry appears as a label in file name dialog.

The way it chooses the default file name is ugly: it truncates the "..." at the end of the "Name" entry, to say nothing of translation teams who put a unicode ellipsis character instead of 3 dots (I know, they could fix it, but here is one of the weak points of the current approach).

But the main problem of using the "Name" entry in 2 places is that you cannot have different translations. Read here for more on this: http://lists.kde.org/?l=kde-i18n-doc&m=127750010729111&w=2

I suggest to introduce 2 entries (in .desktop file) in place of the "Comment" entry, something like "DefaultFilename" and "FilenameLabel".

Reproducible: Didn't try
Comment 1 Kai Uwe Broulik 2011-07-19 17:36:17 UTC
Just looked into the code and saw a comment
"// KDE5 TODO: remove the "..." from link*.desktop files and use i18n("%1...") when making the action."
So it seems that changing the parsing of those .desktop files will break the API? And I am not in a mood of adding just another layer of compatibility:

If DefaultFilename → use it. If not → use name. If not → use this. blabla
Comment 2 Nate Graham 2018-04-13 17:04:40 UTC
Is this still an issue with KDE Frameworks 5.44 or greater?
Comment 3 Andrew Crouthamel 2018-09-28 03:19:27 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 set the bug status 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 4 Alexander Potashev 2018-09-28 09:34:50 UTC
Still an issue with KDE Frameworks 5.48.0.
Comment 5 Andrew Crouthamel 2018-09-28 16:59:34 UTC
Thanks for the update!