unity-lens-applications doesn't search the "GenericName" field

There's a keywords field in desktop file specification (AFAIK it used to be a GNOME extension but then was mainlined), so it should be fixed either in keywords or in description (to conform http://elementaryos.org/docs/human-interface-guidelines/desktop-integration/app-launchers)

Okay, it looks like applications lens doesn't look for anything in GenericName. It only looks in the "Comment" field... should I report the bug to 'unity-lens-applications'?

Marking as Invalid since this is a Unity error. http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html suggests not to use the Keyword entry to duplicate the Generic Name.

Can I just set it to affecting 'unity-lens-applications' instead and just
change the information to fit, or should I just report a new bug (and mark
this as a duplicate?)?

Sincerely,
Kroq-gar78

On Sat, Apr 28, 2012 at 7:17 AM, Andrea Basso <email address hidden>wrote:

> Marking as Invalid since this is a Unity error.
> http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html
> suggests not to use the Keyword entry to duplicate the Generic Name.
>
> ** Changed in: lingo-dictionary
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/975733
>
> Title:
> When "Dictionary" is searched in Unity, Lingo doesn't appear
>
> Status in Lingo Dictionary:
> Invalid
>
> Bug description:
> Lingo version: 0.8-0~r127+pkg5~precise1
>
> I know this is probably not that important (especially because this is
> elementary and not Ubuntu), but when I search for "Lingo" in the Unity
> Dash, I don't get Lingo as a result. I think this is because the
> correct words aren't in the .desktop file.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/lingo-dictionary/+bug/975733/+subscriptions
>

I'd suggest reporting another bug and making it more generic (maybe using Lingo only as an example), but I think reassigning it is fine all the same.

Ok I converted it to be a unity-lens-applications bug.