you’re asking what we think of using paid Google translation, after you stopped translation support for activity stream. This is my opinion:
I don’t want Google translation at all, but I want my users to be able to read a language filtered activity stream. The best status updates are manually translated and doesn’t make sense with automatic translation anyway. So this ist my favourite scenario:
- A language selection beneath the “what’s new” form, that the author himself can decide what language his post belongs to.
- One language selection (dropdown) in buddypress profile, that each user can set his default language to WRITE. (this will be the preselected language at the “what’s new” form)
- Another language selection (multiple checkboxes) in buddypress profile, to set the preferred languages to READ. (this will filter the stream – if he wants to read everything, he can choose “all languages”)
- Filtering the activity stream: Show each user the other’s updates only in his preferred languages. (and change filtering to the selected language set by language switcher).
Not so important, just a maybe:
– A translation option for users who are marked as translators, at each activity update, to translate activity updates if they want to. (But that’s not so important. I think the updates would filter well by the original post and the language set by the author. I don’t think that many translators would like to translate so many user updates).
- The topic ‘Manual translation in activity stream instead of Google API’ is closed to new replies.