An inactive button can also indicate that a feature will be implemented in the future and is not yet available in the current version of the interface. Adding such an element can inform users about upcoming updates and new capabilities. Including a label like "coming soon" or a tooltip is one way to achieve this, but it is neither the only correct approach nor an expected behavior. In some cases, adding an inactive button without additional information might be preferable to avoid cluttering the interface.Man, an inactive button means that the functionality it activates is not available in the current ui mode. But it also implies that there is a mode exists in which this functionality becomes active. If the functionality doesn't exist in the application, you don't need a UI element for it.
Okay, you want to show that certain functionality is in development and will appear in new versions. To do this, you add an interface element in advance, which in the current version does nothing. So write “coming soon” next to it or show a tooltip when you hover your mouse over it. This is the expected behavior for most typical applications.
But somehow you expect users to guess that red buttons in your interface mean that they are non-functional elements and users should just ignore them. Well, you see how good it works.
EDIT: By the way, to the right of the language selection menu there is an "info" icon, right? Do I understand correctly that the letter "i" in a circle means "info"? Does this work or is it also "inactive"?
As for the "i" icon in the corner, it is primarily designed to attract the user's attention. In the future, it will provide information about who is the translator for a particular language.