BUG: using language indicators in search not working?

from the release notes:

• 
  Bible Search will use the Smart search engine by default, unless you enter Precise search syntax.
  • Examples:Entire query parses as a Bible reference.Entire query is in Greek or Hebrew.Query contains special syntax.Exact phrase/in quotes.

(emphasis mine) It should switch to a precise search rather than indicate invalid syntax.

Tried h:שְׁלֹמֹה, and received the same error reply, but lemma:שְׁלֹמֹה worked perfectly. Also tried g:logos and received that same error report. Don't know when, but it appears that h: and g: no longer work.

Thank you @MJ. Smith , I couldn't find the bug tag!

It is tagged bug - the tags are at the bottom of the input when you create a new post.

MJ Smith wrote: "It should switch to a precise search rather than indicate invalid syntax."

I was on Precise search when I received the error message. You are likely correct that this is a bug.

What you have entered is not valid syntax. Depending on what you are trying to accomplish, you need to do one of two things differently:

First, one usage of the h: or g: prefix is to direct the autocompleter to give you untransliterated suggestions in that language. This isn't valid search syntax, it's just something to help you select the right things from the autocompleter without having to type original language characters. https://ref.ly/logosres/logos4help?hw=Untransliteration

Second, if you are trying to constrain your search to only text that has been tagged as a specific language, then the syntax is something like french: or german:. This technically works for Hebrew and Greek, but is of extremely low value, since the glyphs you have specified are unique to those languages, so there is no need to specify the prefix if your query is written using original language characters. https://ref.ly/logosres/logos4help?hw=Advanced+Searching&off=17353

Got it - I see how it works. Shows how long since I used it lol. Thank you @Andrew Batishko