Skip to content

Bugs in the new site interface

User Avatar
#85
Auto-translated
Mооnst@r
HwKeeper

The ability to disable auto-translation globally without providing a translation at all destroys the very essence of this feature; right now it can already be disabled by simply clicking the manual translation button.

The problem here is different: if the author believes their topic is not needed on the .net (English-language) domain and wants to restrict their topic to the Russian-speaking audience, that is a separate question — such a checkbox could be added, and the topic simply would not be displayed to those who do not know Russian, overall.

The feature is designed for the convenience of those who do not know Russian and works better than just pasting the text into Google Translate, since it provides context, subject matter, and the message section, as well as a jargon dictionary for different versions of Heroes.

Otherwise, a person who does not know Russian would be left with the option of pasting the text into Google Translate or a similar translator. That is, the translation process would still happen, just less conveniently and with even lower quality.

Here we need to decide: what do we want to achieve? What problem are we solving?

What about performance when navigating between sections, reading topics, and so on? Is all of this done with every navigation and refresh? And I do not see the "manual translation" button. Again, you have to go somewhere and search for it.

Performance does not suffer; the translation is done in the background on the server by sending a request to the API with an LLM, providing context, and it does not create load — we receive the response, save it to the database, and displaying the original and the auto-translation takes the same amount of time.

Attachments 1
1 file attached • Total size: 25.1 KB