Localize suggested recipes

[nicmart-dev]

Upon changing language with #24 and searching for recipe, the suggested recipes screen #11 shows recipes only in English:

Recipes should be using the language defined.

[yaacovkdev]

Thank you for the review! I will implement it in the upcoming updates!

[nicmart-dev]

I think this issue should be only to localize the output of the LLM from n8n workflow, as we can't rely on react-intl to localize this.
Any issues in static strings still remaining in English (like "Ingredients" or "Directions") are out of scope should be addressed separately, as part of my feedback in #41

[nicmart-dev]

I think the best may be, that if the user select a language other than English, we localize recipe (title, ingredients, directions, and overview) on user side on demand each time, using machine translation (so not through n8n which would always return recipe only in English). There appears to be such Node.js package that is still being maintained and appears popular enough: https://www.npmjs.com/package/translate

Things we don't want to do:

• we ask the LLM to provide output in every language (which would be very inefficient and increase recipe search time), not just the one selected by the user, so we can save this and display to the user the matching recipe
• if user changes language, the saved recipes are reset (even though it would avoid this issue and start fresh)

[nicmart-dev]

I noticed you made some progress to localize headers for commits like 2fe31a3 or f1aa0fb.
I noticed the cuisine type is still in English though in the recipe card and recipe overview section:

Let's keep adding those headings to client/src/i18n/strings.json

As to the recipe ingredients and directions, did you spend any time investigating that package I mentioned to not rely on n8n for machine translating those on the fly?

[yaacovkdev]

I noticed you made some progress to localize headers for commits like 2fe31a3 or f1aa0fb. I noticed the cuisine type is still in English though in the recipe card and recipe overview section:

Let's keep adding those headings to client/src/i18n/strings.json

As to the recipe ingredients and directions, did you spend any time investigating that package I mentioned to not rely on n8n for machine translating those on the fly?

Hi Nic, I haven't researched into Translate NPM package yet, but I changed the formatting in localizations. I think it's best to make a separate pull request that would translate (recipe title, ingredients, directions, and overview which includes cuisine name).

[nicmart-dev]

Yes agreed, let's address this issue in a separate branch and separate PR.