Syntax highlighting of search input

[maBarabas]

Describe the issue

1. Go to a screenshot
2. Enter "not found" as the search term
3. A lot of strings appear as search results, most of them not containing anything related to "not found"

If I enter "not" or "found" then fewer results are found compared to "not found".

I already tried

• I've read and searched the documentation.
• I've searched for similar issues in this repository.

Steps to reproduce the behavior

1. Go to a screenshot
2. Enter "not found" as the search term
3. A lot of strings appear as search results, most of them not containing anything related to "not found"

Expected behavior

Search only lists strings containing "not found"

Screenshots

Exception traceback

No response

How do you run Weblate?

weblate.org service

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

[nijel]

Use "not found" in this case. Search supports boolean operators, so you search for all strings not containing string found. See https://docs.weblate.org/en/latest/user/search.html#boolean-operators

[maBarabas]

I see, I'll keep the issue open as a UI bug, as this is not obvious.

Maybe there should be an English representation of what I have searched for, for example: Strings not containing "found", or a mention of the search syntax next to the text box, or a graphical representation of how my query was parsed.

Just looking at the box, I think most users would assume it's a plain text search.

[github-actions]

This issue seems to be a good fit for newbie contributors. You are welcome to contribute to Weblate! Don't hesitate to ask any questions you would have while implementing this.

You can learn about how to get started in our contributors documentation.

[nijel]

I don't think English representation would be useful for possibly long queries. Instead, doing syntax highlighting on the search input would show how it is interpreted.

What I'd like to see:

• Uppercase logical operators upon typing/pasting, so this query would become NOT found
• Highlight syntax using PrismJS (which we already use)

[buhtz]

IMHO the current search behavior is a bug because it do not fit the users expectations (#10793). Keep in mind the "the user" especially in translation context is (for me) a non technical person knowing nearly nothing about computers.
But having syntax enlightening is a good workaround to be more explicit about the fact that the search might behave different then the user expect.

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.