Is it advisable to separate tables in the database with a small number of languages?

Question

Database design

The site can have a maximum of 3 languages, at the initial stage there will be only 2, 3 languages ​​are not a fact at all that will be needed. For myself, I identified 2 solutions to this problem.

1. In each table where translation into several languages ​​is needed, add <field name>_<language>
   
   I don’t really like this option, since there is still a hard link in the tables themselves and it will make it difficult to add a new language, but on the other hand there will be no more languages. This is a local service.
   
   
2. For each table where there are fields with translations, make an additional table, for example, post_language, news_language, etc.
   I like this option better, but it forces me to divide almost all tables by 2. Let's say I have regions and cities that should also be translated. As a result, the tables turn into this.
   
   Each query, in fact, will need to be written one that makes a selection from the default language, if this text is not translated into the selected language.
   
   

How expedient is it to use the 2nd option, with a static number of languages?

Answer 1

> on the other hand, there will be no more languages
​​:)
You can take out one (actually two) common table with "translations"

: service), not an identifier.

Answer 2

The statement "we have three options, and there can't be a fourth" in 99% of cases is broken by the customer's Wishlist "well, we already have three options, is it not a problem to add a fourth?" :-)))