Wich solutions is better for translate some data?
You should only store your data in one language and handle the translating of text on the application side, for a multitude of reasons:

Different languages use different characters which may affect the data type and collation of how you store the translated data. This can affect you from a flexibility standpoint and potentially a performance standpoint (depending on the size of your data) and what collations you're using elsewhere.

Different languages have different dialects which means there's more rules to how you store the translated words. For example, Spanish spoken in parts of Spain may vary from how it's spoken in Brazil or Mexico.

Per #2, there may be different words in each of those dialects for the corresponding English word, and you'll then need to store more translations than anticipated.

Even within the same dialect of a language, a word may translate differently depending on the context it's used it. Building out a relational model to manage all the contexts of a given word sounds like a nightmare to me.

There's already a multitude of APIs out there that can be consumed on the application side and take care of all the aforementioned issues, such as Google's Translate API. There are other free ones as well. This is probably the simplest solution to this kind of problem.