You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a problem for all non-latin languages: you forget to switch the layout from one language (e.g. Russian) and type something in another language (e.g. English) only to find yourself with a weird looking string
For instance: you want to write pull request, with wrong layout it becomes згдд куйгуые
It would be nice if Maccy supported searching in the wrong layout.
That would probably mean that every search string would be searched twice: for original string and for layout-converted one. Google probably uses heuristics to only search with one of those, but that would be overcomplicated. Therefore that feature should be turned off by default, so that one layout only users would not be punished (and they are probably the majority of your app users)
Implementation wise: the app could use predefined mappings between layouts. I saw something like that on github. Worst case scenario: users could provide their own mapping, in case their layout is not supported
The text was updated successfully, but these errors were encountered:
Before Submitting Your Feature Request
Problem
This is a problem for all non-latin languages: you forget to switch the layout from one language (e.g. Russian) and type something in another language (e.g. English) only to find yourself with a weird looking string
For instance: you want to write
pull request
, with wrong layout it becomesзгдд куйгуые
Search engines added support for this a long time ago, see google: https://www.google.ru/search?q=%D0%B7%D0%B3%D0%B4%D0%B4+%D0%BA%D1%83%D0%B9%D0%B3%D1%83%D1%8B%D0%B5
A screenshot
Solution
It would be nice if Maccy supported searching in the wrong layout.
That would probably mean that every search string would be searched twice: for original string and for layout-converted one. Google probably uses heuristics to only search with one of those, but that would be overcomplicated. Therefore that feature should be turned off by default, so that one layout only users would not be punished (and they are probably the majority of your app users)
Implementation wise: the app could use predefined mappings between layouts. I saw something like that on github. Worst case scenario: users could provide their own mapping, in case their layout is not supported
The text was updated successfully, but these errors were encountered: