Markus Heiser

FYI: last force push was a rebase on SearXNG's master branch to get https://github.com/searxng/searxng/pull/3836

> @return42 Would you happen to have any context into the `unknown_params` dict? See the below commit. Sadly no .. its very old code and the intention is not clear...

> I tested undoing these changes. While it does remove code that appears to be risky @glanham-jr would you like to implement a PR that removes the risky code. /...

> I would see: > - ... > - src/searx/static > But a lot of stuff expect searx source code in the searx directory. For the first step we should...

Leave them where they are .. in a second step, we can have a look what files can be generated ... E.g. - `searx/searx/static/themes/simple/img/favicon.png` can be genrated from `searx/static/themes/simple/img/searx_logo.svg` and...

@dafl are you implementing the move to `src/` .. or should I give it a try?

In #151 we have moved source files to the `src` directories below the `themes/*/src`, this was the first step. The next step should be to move the `themes/*/src` to `/src/*/static`,...

The solution oft this PR is based on entries like ```json "polish złoty": [ "PLZ", "PLN" ], ``` but might cause unexpected results with ambiguous currency names, a search term...

Did not get a hint on how to solve the issue in a better way https://github.com/searxng/searxng/pull/3716#issuecomment-2276272872 / going to merge the PR as is.

I'm not sure its a good idea to enable more than one auto-completer. It will spread what the user types into the search field to more than really needed origin...