11–20 of 29 posts
This is a trick with Unicode RTL. The search query in the URL contains the character U+202E RIGHT-TO-LEFT OVERRIDE, followed by the searched-for text in normal (nonreversed) order. Apparently Google ignores this character when searching for matches (so the matches are displayed normally), but the character appears when the query is reproduced in the search box at top of the screen, so the search string appears backwa…
sdrowkcab hcraes nac elgooG
egap siht etalsnarT
tnahC aykanahC
lortnoc txet lanoitceridiB
weiver koob a
yhw nosaer yna
All I get are results from elgoog.rb-hosting.de or none at times!
they might have just index that phrase backwards. if you were to search for "hacker news" backwards, you get nothing related. http://www.google.com/search?gcx=w&sourceid=chrome&i...
This is a trick with Unicode RTL. The search query in the URL contains the character U+202E RIGHT-TO-LEFT OVERRIDE, followed by the searched-for text in normal (nonreversed) order. Apparently Google ignores this character when searching for matches (so the matches are displayed normally), but the character appears when the query is reproduced in the search box at top of the screen, so the search string appears backwa…
they might have just index that phrase backwards. if you were to search for "hacker news" backwards, you get nothing related. http://www.google.com/search?gcx=w&sourceid=chrome&i...
so can bing, yahoo and every other search engine.
looc s'taht llew
For example, if I want to search in Hebrew for "חיפוש בעברית" but accidentally typed in English and typed "jhpua gchcr," (same keys as the Hebrew chars) - I'll still get the results I was looking for [1].