i face the problem to develop a database with a support of multi languages. My first approch was it, to write for each language a extra table. For example I handle recipes, so I created various templates according to the language:
- enRecipe
- deRecipe
- frRecipe
Is this correct or is their a better approach?
The main problem with the design will be shown when other languages needs to be added to the design, when you will need to add more tables.
Also it would be hard to find witch language have not implemented specific recipe keys.
I will suggest having a design like bellow:
About the comment:
To generalize the solution for other entities like Ingredients, there may be alternatives:
Note that in this design text keys are separated from business entities like Recipe and Ingredient.