Closed glixx closed 6 years ago
Thanks.
The usual way of doing this is that you fork the repository (button at the top right), make your changes locally, push them back to GitHub in your forked repository, and submit a pull request. https://help.github.com/articles/fork-a-repo/#propose-changes-to-someone-elses-project
In this particular case, I think the wording for the keys is wrong. The way I read the spec, and all the examples I've seen elsewhere, have GenericName
as a noun phrase (e.g. 'web browser') and Comment
as a verb phrase (e.g. 'browse the web').
You understood specification wrong. GenericName is tooltip for Classic Menu KDE and menu item for Modern Menu KDE.
Total rule: Name(short)<>GenericName(short enough)<>Comment(short or long)<>X-GNOME-FullName(short or long)
But all the other examples I see use a noun phrase for the GenericName
and a verb phrase for the Comment
, including the actual specification.
Are they all wrong?
It is simple coincidence. Look at KDE apps. GenericName is any string, but short enough to be placed as menu item. GenericName must not be the same with Name, Comment, etc. Good to add X-GNOME-FullName also for GNOME apps.
I've looked at the GNOME apps -- and system-config-printer is a GTK+ application, not one that will be used in KDE -- and all of them use it the way I described.
So I would much rather be consistent with both existing practice and the specification, and use noun/verb phrases.
I also do not want to have "Graphical interface to" in there. It's redundant.
Please re-submit as a pull request.
If you don't like my patch, then please write GenericName and X-GNOME-FullName what you like.