Closed raphodn closed 1 month ago
raphodn
commented
9 months ago @Apurv428
Can we make the translation of the landing page by using libraries or Google Translate? This way, we can cover various languages that users might use. Instead of creating separate folders, like it's done in this https://github.com/openfoodfacts/open-prices/pull/155, can we explore the above approach?
What would be your approach ? You're right that there's some duplicated code like the <head>
Apurv428
commented
9 months ago I'm considering using Google Translate and incorporating the languages we need, or if necessary, incorporating all the languages it offers.
Apurv428
commented
9 months ago Could you please provide guidance and insights on this issue mentioned? @raphodn
raphodn
commented
9 months ago @Apurv428 what language do you want to translate to ? A simple PR would be to "duplicate" #155 but for another language.
Apurv428
commented
9 months ago @raphodn I wasn't considering a specific language. Instead, I was contemplating the incorporation of a feature that enables the translation of the website into any language the user might prefer.
raphodn
commented
9 months ago I see, we could leverage https://translate.openfoodfacts.org which is the crowdsourced plateform to translate Open Food Facts content. But I'm not sure how to integrate it. Maybe move the landing page to the frontend app ? @raphael0202
raphodn
commented
8 months ago Frontend issue to migrate the landing page(s) there : https://github.com/openfoodfacts/open-prices-frontend/issues/364
raphodn
commented
1 month ago Closing as the landing page has been migrated to the Frontend 🎉
Story
Currently the landing page is available in only 2 languages :
Help
See this PR - https://github.com/openfoodfacts/open-prices/pull/155 - for an example (French translation).