Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[mod] replace utils.match_language by locales.match_locale #186

Merged
merged 1 commit into from
Feb 7, 2023

Conversation

return42
Copy link
Owner

@return42 return42 commented Feb 7, 2023

This patch replaces the full of magic utils.match_language function by a locales.match_locale. The locales.match_locale function is based on the locales.build_engine_locales introduced in 9ae409a [1].

In the past SearXNG did only support a search by a language but not in a region. This has been changed a long time ago and regions have been added to SearXNG core but not to the engines. The utils.match_language was the function to handle the different aspects of language/regions in SearXNG core and the supported languages in the engine. The utils.match_language did it with some magic and works good for most use cases but fails in some edge case.

To replace the concurrence of languages and regions in the SearXNG core the locales.build_engine_locales was introduced in 9ae409a [1]. With the last patches all engines has been migrated to a fetch_traits and a language/region concept that is based on locales.build_engine_locales.

To summarize: there is no longer a need for the locales.match_language.

[1] searxng#1652

This patch replaces the *full of magic* ``utils.match_language`` function by a
``locales.match_locale``.  The ``locales.match_locale`` function is based on the
``locales.build_engine_locales`` introduced in 9ae409a [1].

In the past SearXNG did only support a search by a language but not in a region.
This has been changed a long time ago and regions have been added to SearXNG
core but not to the engines.  The ``utils.match_language`` was the function to
handle the different aspects of language/regions in SearXNG core and the
supported *languages* in the engine.  The ``utils.match_language`` did it with
some magic and works good for most use cases but fails in some edge case.

To replace the concurrence of languages and regions in the SearXNG core the
``locales.build_engine_locales`` was introduced in 9ae409a [1].  With the last
patches all engines has been migrated to a ``fetch_traits`` and a
language/region concept that is based on ``locales.build_engine_locales``.

To summarize: there is no longer a need for the ``locales.match_language``.

[1] searxng#1652

Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
@return42 return42 merged commit 14460c4 into master Feb 7, 2023
@return42 return42 deleted the replace-match_language branch February 7, 2023 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant