Translators needed

[return42]

We need translators, suggestions are welcome at https://translate.codeberg.org/projects/searxng/searxng/

Any help is welcome / BTW thanks to all, helping us to make SearXNG better from day to day!

[Gert-dev]

I just added some translations for nl (Dutch) because I encountered some rather horrible translations on an instance and some were missing. However, it turns out there is a separate nl_BE for Belgium, known as Flemish in Weblate, and this is the one actually containing the horrible translations (een privacyrespecterend, aanpasbaar metazoekmachien in the footer already contains at least three, maybe four, grammatical errors).

Was this one added on purpose? If not, I suggest just (re)moving nl_BE and letting it fall back to nl, unless someone severely objects. nl_NL specifically for The Netherlands also does not exist and, even though there can be slight differences in phrasing or use of specific words, both The Netherlands and Dutch-speaking Belgians use the "same" language; it seems an additional burden to manage the same language twice for the rare occasion differences might exist. ("Flemish" is also not an actual language AFAIK, only Dutch is, there are only various dialects and region-specific turns of phrases, use of words, accents, and more, but both countries share the same language, at least when it comes to Dutch - Belgium also has two other official languages, German and French.)

FWIW, fr_BE does not exist, which can have the same kind of differences from fr_FR.

(FYI I am a target of the nl_BE locale myself.)

EDIT: Judging from some of the translations, perhaps the current nl_BE was somewhat intended as so-called "speaking language" - the way most Dutch-speaking Belgians speak to one another in common conversations. GNOME also used to have a special variant of Dutch as locale like this (I think it was li_BE for "Limburgs Dutch" and wa_BE for French from Wallonia, these actually still exist in /etc/locale.gen).

Having this variant is fine in itself, but it would probably be improper to put that under nl_BE as this variant is almost never used as written language on websites (modulo people conversing over chat systems), and that is what all Dutch-speaking Belgians will now see by default if they have their browser language set to Belgian Dutch, rather than "proper" and well-formed Dutch.

[return42]

See comment from @unixfox "We speak three languages in Belgium: German, Dutch and French."

• German is de @weblate
• Dutch is nl @weblate
• French is fr @weblate

However, it turns out there is a separate nl_BE for Belgium, known as Flemish in Weblate, and this is the one actually containing the horrible translations

AFAIK ..

Belgium is split in three parts, beside Brussels there is the Walloon (French) region in the south and the Flemish (Dutch) region in the north. Flanders is the Dutch-speaking northern portion of Belgium and the Flemish community do speak Flemish.

• official language of Flanders is Dutch (nl)

• Flemish is nl_BE @weblate (I can't judge the quality of this translation).

• Flemish & Dutch are based on the same language but different (like the German language from Germany and the German language from Austria).

.. this is what I know / perhaps @unixfox can clarify ..

[unixfox]

These languages should just be an alias:

• nl_BE should be an alias of nl
• fr_BE should be an alias of fr
• de_BE should be an alias of DE

It doesn't make sense for a product like searx to have specific translations for one country language derivation because searx is not an operating system and doesn't have a lot of translated sentences. So the odds of having in Searx a different word in fr_BE compared to fr/fr_FR is very small.

[return42]

It doesn't make sense for a product like searx to have specific translations for one country language derivation because searx is not an operating system and doesn't have a lot of translated sentences. So the odds of having in Searx a different word in fr_BE compared to fr/fr_FR is very small.

that's right for BE .. but I assume it make sense in some other languages / I have pt_BR & pr in mind.

[unixfox]

It doesn't make sense for a product like searx to have specific translations for one country language derivation because searx is not an operating system and doesn't have a lot of translated sentences. So the odds of having in Searx a different word in fr_BE compared to fr/fr_FR is very small.

that's right for BE .. but I assume it make sense in some other languages / I have pt_BR & pr in mind.

Probably yeah. Do note that you might delete better translations if pt_BR was translated by more experienced translators than pr. I think it's a choice only a native can do.

[AHOHNMYC]

@return42 hello! Please, approve suggestions for 14 locked strings in Russian section. I've corrected a lot of errors in translation and machine translated strings, but these are out of my hands :)

[return42]

Please, approve suggestions .. I've corrected a lot of errors in translation and machine translated strings

@AHOHNMYC done ... thanks a lot!!! But we have to wait until next Friday .. we have a job running once a week fetching translations from weblate and merging them upstream.

[AHOHNMYC]

@return42 oh, thank you for this fork and fast response! I'm looking forward to next week :)

[michaelradu]

@return42 Hello! I just wanted to say I added some new Romanian translations, I don't know if they need to be approved or if they automatically get added so I just wanted to let you know. :)

[return42]

@michaelradu thanks a lot! .. I already approved your suggestions this morning :-)

There a 5 Romanian translations open: https://weblate.bubu1.eu/translate/searxng/searxng/ro/?q=state:%3Ctranslated%20AND%20NOT%20has:suggestion

If you have time to give suggestion it would be great.

[return42]

@michaelradu thanks for adding suggestions to left open translations .. I approved them .. But we have to wait until next Friday .. we have a job running once a week fetching translations from weblate and merging them upstream.

[gkkulik]

@return42 Hi, I'm the owner of the Silesian SearX instance at https://szukocz.slon.ski. I'm planning to switch to SearXNG, so I uploaded Silesian (szl) translations to Weblate. Not sure where you get native language names from but if you pull them from Wikipedia, then don't in this case. We changed the alphabet 13 years ago and can't make Wikipedia replace the old spelling. The correct native name for Silesian is “Ślōnski”.

Edit: I almost forgot. Babbel does not support Silesian because we've been working on CLDR but it's been somewhat slow. Since there is no actual CLDR strings in the UI and Silesian has the same specification as Polish, perhaps we could use a workaround by linking the pl.dat and pl_PL.dat files to szl.dat and szl_PL.dat in the Babel's localedata directory for the time being?

[return42]

@gkkulik thanks for your efforts on Silesian ...

Babbel does not support Silesian ..

TBH I did not had time to look at yet .. ATM I can only say that a language that is not supported by babel will break our toolchains / see #1179 that fails at https://github.com/searxng/searxng/runs/6318882207?check_suite_focus=true#step:7:130

perhaps we could use a workaround by linking the pl.dat and pl_PL.dat files to szl.dat and szl_PL.dat in the Babel's localedata directory for the time being?

Its not such easy .. if we do so, we need to fork babel and we do not have the resources to maintain a fork of babel. I don't really know it but I assume we will also need some more quirks in SearXNG's sources to support a language that is not supported by babel.

@dalf is the owneer of this repo, lets hear what he think about adding a language that is not supported by babel.

[gkkulik]

I assume we will also need some more quirks in SearXNG's sources to support a language that is not supported by babel

I'm actually running it on my instance the way I'm suggesting. If you link the .dat files as above, add the .po files and add the language to yaml, it works with no issues. The linking could be done by scripts after installing babel, so that there would be no necessity to fork it. Although I admit it's a somewhat dirty hack.

[return42]

The linking could be done by scripts after installing babel, so that there would be no necessity to fork it. Although I admit it's a somewhat dirty hack.

@gkkulik: it seems simpler than I thought first :-) .. thanks @dalf pushed 550f70b .. I hope I have time the next days to review the commit .. more coming soon ..

[gkkulik]

Wow, I didn't realise Occitan already had a similar but much nicer solution. Thank you, switching to SearXNG will be so much more painless. :)

[return42]

@gkkulik Silesian has been merged into master / you can test it on my instance https://darmarit.org/searx/preferences .. thanks a lot for your contribution.

[sys-256]

Hi all, I just added 3 Dutch translations to make it 100% translated (from 98%). However, I only had to create an account with my GitHub account, no confirmation needed, and the translation image in the README now shows 100% too (well it doesn't right now, but it does on https://weblate.bubu1.eu/widgets/searxng/-/multi-auto.svg so we'll have to wait for the GitHub cache to expire). Is this normal, and will my new translation automatically be merged in the new (docker) release?

Kind regards,
Bram

PS: This is my account showing the changes made: https://weblate.bubu1.eu/user/sys-256/#changes

[return42]

@sys-256: thanks a lot for your contribution on weblate ..

Is this normal, and will my new translation automatically be merged in the new (docker) release?

Yes but it will take a week .. on Fridays we have a job running to sync from weblate .. but this job has already been finished today :-)

[extremelyonline]

Hi all, if you go to searxng in Hong Kong, the interface language defaults to Chinese Simplified, whereas HK people usually use Chinese Traditional or just English. (Generally it's ok to use the Taiwan version of the translation for Hong Kong.)

Is there a way to detect a HK geo locaiton and set the interface to Chinese Traditional?

[return42]

Hi @extremelyonline .. this is an issue in SearXNG, do you like to open an issue here at github / thanks!

The language is taken from the Accept-Language header the request sends. Can you show me the Accept-Language header your browser sends to the SearXNG; I assume we have an issue in this function:

searxng/searx/webapp.py

Lines 252 to 262 in 59ef9b9

	def _get_browser_language(req, lang_list):
	for lang in req.headers.get("Accept-Language", "en").split(","):
	if ';' in lang:
	lang = lang.split(';')[0]
	if '-' in lang:
	lang_parts = lang.split('-')
	lang = "{}-{}".format(lang_parts[0], lang_parts[-1].upper())
	locale = match_language(lang, lang_list, fallback=None)
	if locale is not None:
	return locale
	return 'en'

[ghost]

its a lot of suggestions who need be approved

[return42]

@forvirretfrukt thanks for reminder .. done! .. FYI: approved translations will be automatically merged every Friday.

[enderprism]

I’m currently working on the French translation, but there’s a weird string :
“The could not download the list of Tor exit-nodes from https://check.torproject.org/exit-addresses.”
Should there be a word between “the” and “could”?

[return42]

but there’s a weird string

Thanks for pointing out, I fixed it in #2202

I’m currently working on the French translation,

FYI: Right now the translation process is a mess for us .. we are moving to https://hosted.weblate.org/projects/searxng/ but the process is dragging on. We were previously on https://weblate.bubu1.eu/projects/searxng/searxng/ but the services are no longer running .. then we moved to https://translate.codeberg.org/projects/searxng/searxng/ but that was criticized by @comradekingu, so we moved to https://hosted.weblate.org/projects/searxng/ .. but there we are now waiting for them to accept us as a libre project .. it's a mess at the moment .. I myself am very unhappy with the current state ... we are working on it, in the meantime I apologize.

[return42]

FYI we decide to stay at https://translate.codeberg.org/projects/searxng/searxng/ for now.

[Trendyne]

I've requested to translate Icelandic on the Weblate

[iamtalhaasghar]

A request for a new translation has been sent for Urdu language 🇵🇰.

[lsnnt]

Add a new language request for

• Maithii