Before work on "Bug 58989 - Transfer additional info to EXTENSIONSWEBSITE" can start we need an enhanced forward mechanism what forwards links to localizations what do not exist to English language. Without that wor on that bug would be rather useless.
when I try http://extensions.libreoffice.org/?set_language=nl then it defaults to the English language. So I don't think I understand the problem?
Can you please explain.
I can't reproduce your observations, with some nonsense-localizations like <www.extensions.libreoffice.org/?set_language=zz> as a bookmark I reached the German localization of the site, not the English one. But when I modify "set_language=cs" to "set_language=zz" in the browser URL pane, view switches to the English localization.
Nevertheless, the result is the same, you do not reach nirvana with a link to a not existing localization, but a real web page where you can select an existing localization. So we currently we do not have a real problem here, I will do some further investigation and think about it, may be we can close the report for now.
I still don't experience your problem. But what I see is another problem. We have for portugese (Brizilian) pt-br. But other languages are only 2 chars long. So it is impossible to be able to have both. We should then OR remove the brazilian or always accept the complete locale otherwise it would be a nightmare to sort this in LibreOffice.
There is no real problem, only some things I do not understand (or what are unexpected)
So this one is more or less only still active because there might appear unexpected (or difficult to handle) aspects aus you found and what might have influence at many places (Website, LibO UI, LibO Localization, ...).
This "pt-br" problem is the same for "Chinese (simplified)", Chinese (traditional) at international sites, and may be additional ones as we see in Extension repository (it-it, es-es, hu-hu). We urgently need some unification here.
Can you help with some advice?
Just checking on this bug to see if it has been resolved? It sits as unconfirmed. Do we change its status?
the problem still persists. So setting it to NEW
ticket moved to redmine https://redmine.documentfoundation.org/issues/1524