A sort of bug was recently fixed by github user Mtnadi recently.
Previously if you wanted to add the in: filter (e.g. in:vinaya) it had to be the very first thing in the search string. Now that is no longer the case.
So, for example, you can search for bowl and then decide that you want to narrow it to Vinaya with bowl in:vinaya (of course you can just search for that directly too. But now you don’t have to worry about putting the in: filter as the first item in the string).
The segment link is to https://suttacentral.net/dn21/en/sujato#1.4.7.0 The problem is that that segment anchor isn’t available to the browser. Headings have segment numbers, but they are hidden. So when you click the segment in the search result, you are just taken to the top of the page.
No. In this case because you have searched for Pali words, it is returning a document (which includes root documents and translation documents) that has your search phrase. In this case a root document. And all root documents are aligned. Which, yeah, is kind of an odd thing to say since you can’t get translations if you go to that page.
So it’s not a bug, just an odd wording. Perhaps instead of aligned it should say “root”?
Well it is aligned with all the bilara translations of that root text. Semantics, I know. When you go to a translation page it’s not aligned with anything until you activate the root text. But it’s still an aligned text.
In any case, it would be more informative perhaps to have the language there like the suttaplex card does:
This thread if for the search function on the Suttacentral.net website. Perhaps you could start a new thread and loop in @helpdesk-dd. You have a great point.
Today I was searching for ‘potters shed’.
In the quick search it returned a sutta that had ‘potter’s shed’ but when I hit return It showed no results.
The SERP? seems to not filter apostrophes in the same way which is annoying