Skip to content
TORNLIFE More

Chat translator

Started by GIJoe [2439908] on in Suggestions.

1 replies · 50 views · thread synced · 3 days ago · View on torn.com
About this thread

Posts archived: 2 / 2 posts (100%) · the total is Torn's reply count + the opening post at the last fetch

Counted by TornLife from the archived posts.

Archived posts
2
Discussion span
→
People posting
2
Likes on archived posts
5
Authority score
25 / 100
Historical score
14 / 100
Story score
31 / 100
Engagement score
35 / 100
GIJoe [2439908]

As we all know Torn is an English-speaking game, leaving some at a huge disadvantage. Google Translate is used by most who do not speak English leaving them having to go back and forth and copy-paste and all that hoo doo stuff. I play other online games and they have an in-chat translate button. This allows them to quickly communicate without the need to leave the game to translate and copy paste and back and forth.

 

I have noticed too that Google Translate does not work very well and has led to misunderstandings and some rather tense moments in chats. I'm not exactly sure how hard it would be to add such a convenient button to the chat, but I can almost promise you that it would lead to less stress and a much better flow of communications.

 

Anyway, this is my suggestion to the community people, and find this to be one thing missing from the chat 2.0.It would help in many areas of the game experience. Hope you can at least consider my thoughts. 

Zeendin [2201518]

Good suggestion, but implementation could get costly, developer time + cost of the API usage, since they aren't gonna write their own translate bot.

 

Only way I see it working is as a reference only kinda of thing, IE button to translate to the language of the user's choice, but only from English. Chat rules would still require English, that way they wouldn't have to add staff to moderate every language.

 

Could save some time and possible headaches, but it won't fix the issues you mentioned where Google translates something incorrectly.