Honor queries with codes like zh_CN or pt_BR

[teolemon]

What

• The Android app is making queries like that return nothing:
  https://ssl-api.openfoodfacts.org/api/v0/product/6924743919235.json?fields=ingredients_text_zh-CN%2Cproduct_name_zh-CN
• On the other hand, this works.
  https://ssl-api.openfoodfacts.org/api/v0/product/6924743919235.json?fields=ingredients_text_zh%2Cproduct_name_zh
• Can we add Country removal to the API so that we can serve the values stored ?
• Other impacted locales: pt-BR, nl-BE, …

Part of

• 🌍 Make Open Food Facts work well in all countries in the world #5690

[teolemon]

We already do it in write mode:

openfoodfacts-server/cgi/product_jqm_multilingual.pl

Line 216 in f62ffba

# some apps may send pt-BR

[hangy]

IMHO, the app shouldn't be sending these requests right now. The pt_BR to pt change was implemented as a workaround for some misbehaving external client, but we currently don't support more complex ISO codes officially (also see #667). Simply removing stuff could be really hurtful in cases like zh-hans vs zh-hant vs zh-tw.

[stephanegigandet]

I agree with @hangy, we don't want apps to send us extended language codes, the more workaround we had, the more bugs we will have down the road. Here the right thing to do is to change the OFF app so that it sends only the 2 letter code.

[github-actions]

This issue has been open 90 days with no activity. Can you give it a little love by linking it to a parent issue, adding relevant labels and projets, creating a mockup if applicable, adding code pointers from https://github.com/openfoodfacts/openfoodfacts-server/blob/main/.github/labeler.yml, giving it a priority, editing the original issue to have a more comprehensive description… Thank you very much for your contribution to 🍊 Open Food Facts