What if all languages were together on the same page, but the user could expand and collapse posts based on their language tag? So if a user selected ‘German’ they would see full posts that were in German or had been translated to German. All other posts would be displayed as titles.
There could also be a tag for posts that are in need of translation.
It would be nice to have the option to create translations through different methods. Machine translation of Persian and Arabic doesn’t seem to be very good
As someone who was involved in that earlier debate, I am really excited to see this level of UX sophistication being applied to this concept.
I love the idea of language tags to identify the language of the post, but I think the default behavior of such a site should be multi-lingual. All posts are displayed for all users by default, and users could choose to mute out posts of one language or another. But it wouldn’t make sense to mute out a langauge in my context (montreal) because people want to be able to converse in both languages interchangably.
The question of a translation feature - automatic or contributed - i think is separate but related. The best UX for post translation i’ve seen is Facebook’s: a small ‘see translation’ link underneath a post that displays an automatic translation when clicked. I don’t know if that would make sense for a multi-lingual Discourse.
Sure, show-all could be the default. The important thing is either set-up is easily doable with the approach I and @resplin have described.
Functionally speaking, translation is a very different type of functionality from what we’re discussing here, so I would strongly suggest starting a linked topic for any further discussion about such features.
“this”=best practice recommendations, plugins, etc for multilingual forums. I really don’t like the option of running multiple forums, but I have/will have content in 3 languages w/ very little crossover in audiences. I saw several different topics related to suggestions/improvements to handle multilingual requirements, but none of the threads ever seemed to a) result in actual feature development or b) consensus best practices. I was just hoping I missed something.
Why is there no crossover? Because the people in each language community have nothing to say to each other (i.e. they’re talking about different things) or because they don’t understand each other or because they couldn’t be bothered to talk to each other because they have enough interesting conversations within their language community?
In the first case (different topics), there isn’t really any reason to combine them in a single forum.
In the third case (“couldn’t be bothered”), the question would be whether you want to encourage interaction between through the way you organize the forum or whether you are happy with three more or less separate communities with the occasional interaction and “invisible” flow of information through multi-membership.
If you want to encourage interaction between language communities, you might want to consider not creating the same category in different languages but have everyone use the same category and use the translator plugin. If you don’t want to push people to interact across languages, my proposed solution above seems to be the way to go.
A feature that may indeed be useful for several of these scenarios are translatable categories. It has been requestedbefore.
It would be nice to have the categories by language and when you write a message, a flag of language or something like that would appear. The problem with the Translator+++ is that you have to register for paid services.
In Azure, the first 2 million characters every month are free. And when your forum has become so big that you need more than 2 million chracters and your users appreciate the translation service, I would hope that you can get the money from them.
Note that post are only translated upon request, which means that the 2 million characters are only consumed when someone clicks the translate button. And I believe the translation is then stored locally so every post only needs to be translated once per language.
I don’t think so. Discourse doesn’t know what language posts are in. The source language is determined by Azure once the post gets sent there for translation.
Assuming that Azure returns the detected source language and that the translator plugin saves it (though why would it?), the maximum you could get is a list of all posts in Portuguese that have been translated at least once.