What should be the structure of the i18n table?

Question

PHP

Good day,
At the moment I have a project on support, and it supports two languages ​​(ru, en) Through the i18n table. The project is handwritten and written in php.
Table structure

And so for each object there is such a scheme, and in the case of a country this is the simplest. If we take for example a product, then there are much more fields that are registered for each language.
Based on the above, when outputting each object, there is a connection with the i18n table.
I don't have much experience in programming, and therefore I'm wondering how correct this solution is?
Wouldn't it be easier to make a division into ru and en in each table? And do not call the same description from another table with a language check, but store everything in one place.

Answer 1

I usually make translatable tokens table rows and languages ​​columns. Languages ​​are added very rarely, and working with such a scheme is much more comfortable.