We had a ‘speak your own language day’ on our forum. We don’t want it to automatically translate everything because AI translations aren’t perfect, but I did use the AI translate a lot during that day.
I found that highlighting the text of the post and clicking “Ask AI” then “Translate to English” was a bit fiddly, especially on mobile. Can’t we add a “translate” button onto a post, either under the “…” menu or automatically when a language is detected?
It also made me think - if I use AI to translate a post to English, and so do 100 other people, that’s 100 uses of the API which costs money… why don’t we have a way to save the English version to the post automatically after 1 person has translated it?
Then it can show a button to switch to English or read in the original language.
Here you are kinda fighting against the specific system we created to address this UX nightmare of having to invoke translations manually.
Your site could have enabled the automatic translation for the day of the event, and users could then opt-in or out of the automatic translations with the toggle we add on all topics when the feature is enabled.
That is why we built the automatic translation to cover this exact inefficiency.
Well the event was all around celebrating the diversity of cultures and languages we have on the site, and it was meant to add a little bit of friction. So just automatically translating everything is not what we’re going for.
I just thought there are some ways to improve the per-post translating.