That would require that admins can limit which locale their users can choose. That would also be a solution, but it would prevent communities from benefiting from the increasing number of translations that discourse provides out of the box.
You are fixating on problems specific to you, that is, you believe that customizing text in one language should somehow magically customize the same text in every available human language. I do not share this belief and I feel, very strongly, that you should bear the burden of your own choices with regards to text customization. If you want to customize text in every language, you take responsibility for that work, not us.
Furthermore, I also fail to share your belief that non-customized text is some kind of disaster of epic proportions. Default text is harmless.
My reply was actually based on my understanding of the code when I last changed it. I guess it was a while back 
I very much prefer that we are now consistent across all UI text even though it means more work on admins when they customize some text. I also 
your suggestion.
4 „Gefällt mir“
No, this is a misunderstanding. I am merely looking for a way to allow users to use existing locales while still allowing site admins to customize texts, especially the discobot welcome message. Currently, you have the choice of either allowing user locales or customizing.
I have said nothing to convey such a belief. However, default text can be a problem under certain circumstances, for example when you have customized the welcome message to provide certain site specific information to new users but then some users nevertheless receive the default welcome message.
Untrue, you can customize in both cases. Just not to your satisfaction.
Simply customize all affected locales, this already works.
Since you cannot exclude any locales, that would be “all locales”, which brings us back to
Why not just customize it in the ~4 most common languages after English? Surely you’re not going to have users speaking American Cherokee Indian anytime soon.
Yes, as I said, limiting the locales that users can choose would also solve the problem, albeit in an unnecessarily limiting way.
What do you think about @tgxworld’s proposal above?
I don’t know about this. A new user wouldn’t have had the chance to select her/his preferred locale before the welcome message is sent out. I’m pretty sure they are most likely going to get your customised message in the default locale of the site.
Unless you have set locale from accept language header turned on
Or if users choose to respond to the bot after they have customized their locale (though that would not concern the welcome message)
1 „Gefällt mir“
If you’re knees deep into customisations, wouldn’t it be better to just turn off set locale from accept language header ? Even with my proposed fix for your use case, they are going to end up getting the welcome message in the default locale of your site. I don’t feel very strongly about this and like @codinghorror said, customising the welcome message for the 4 next common languages would be good enough.
1 „Gefällt mir“
Yes, I did that, of course, when I realized the consequences. But I think it’s a really great setting for multi-lingual sites because it immediately sends a message to new users when they first visit the site. In fact, even on mono-lingual sites, people who are not native speakers of the site language might be attracted by having the UI in another language.
Yes, unless their browser locale is in one of the languages for which I customized the message. But that, I think, is fine because on the plus side, what users get is the whole UI in their language. You can’t have it all. And you might even speculate that if that UI brings more people from that language community to my forum, chances are that eventually someone helps translate the welcome message (or whatever else is missing).
Since this would also require a new feature (limiting which locales are available on a site) I guess it’s a matter of cost/benefit calculation. The benefit of limiting user locales would be tangible but rather limited and with negative side effects (but still a viable solution). The benefit of your suggestion would be great and would increase in time as more discourse locales become available. So, in my mind, it is clearly the better solution in terms of benefit and openness for future development.
I have no clue about the cost dimension. Could you add it to the equation?
SInce this topic has been somewhat inconclusive I’d like to return to what I think was an excellent suggestion:
This would be immensely helpful and as far as I can tell (which is not very far) it’s probably a rather easy thing to accomplish. Any chance that this could get implemented?
Just to reiterate why this is useful, since the discussion above is somewhat complex: basically, it solves the problem that once you customize any text element in your site’s default language, you can no longer allow users to choose their own locale (let alone enable set locale from accept language header) because they will be seeing the default texts in their respective language and those will no longer correspond to the texts in the site’s main language.
I should add one important detail to the proposed solution:
if you customize a translation of the default site locale, all the other locales should treat its corresponding translation text as missing unless the translation text has also been customized
In other words: if my site is in English and I customized a specific text in English but also in French, all locales will fall back to the default locale for that specific text except for the French locale, (because it has also been customized so that a correspondence between the translations can be assumed).
5 „Gefällt mir“
Any news on this? I’d love to know if this is planned in any way:
If it’s not planned, could someone give an indication of what kind of work would be required to implement this?
To me it looks like what is needed is an routine that is activated whenever a page is served in a language other than the site’s default language. That routine would check if any of the text elements on that page have been modified in the default locale. If not, exit. If yes, it checks if they have also been modified in the current language. If yes, exit. If no, serve the text in the default language.
Alternatively, instead of checking things every time a “foreign” page is served, all current procedures could be left unchanged and instead changes are made whenever default texts are customized. For example, whenever a default text is modified in the default language, all default copies of all other languages are deleted so that the default text will be served (or will it?)
That latter option has quite some pitfalls though, because you need to make sure that only default copies are deleted, not modified ones. And what happens if the default translation is updated on transifex? That should not lead to the copy magically reappearing when the discourse instance is upgraded.
So the first option is probably the better one, but I have no idea how much extra resource use it would imply for serving pages in a foreign language…
1 „Gefällt mir“
@tophee Did you find a solution to this? I’m currently looking at how to restrict the locale list. If there is no solution yet, I will look to implement on… Thanks in advance for your feedback
The solution is here:
But I don’t think it has been implemented yet.
1 „Gefällt mir“
I suppose @tgxworld’s fix is low priority? Or is it on the roadmap at all?
I don’t think I’m able to implement this myself but I’m thinking of maybe trying a kind of brute-force solution by simply deleting (or making unaccessible) all locales that I don’t want to customize (and hence want to prevent people from using).
Could someone give me a hint as to how to gi about tbis? I’m guessing that I need a rather simple plugin that “breaks” the unwanted locales?
3 „Gefällt mir“
@tophee Entschuldige bitte, dass ich ein altes Thema wiederbelebe, aber ich habe in letzter Zeit viel an der mehrsprachigen Unterstützung gearbeitet, daher bin ich neugierig, etwas mehr darüber zu verstehen, worum es dir hier geht.
Ich gebe zu, ich bin etwas verwirrt, warum deine vorgeschlagene Lösung ein besseres Benutzererlebnis bietet, als einfach die angepassten Texte in die verschiedenen Sprachen deiner Benutzer zu übersetzen?
Ich habe das Gefühl, es wäre eine seltsame Erfahrung für einen Nutzer auf einem mehrsprachigen Forum, einige automatisierte Nachrichten in der Standardsprache deines Forums und andere in seiner eigenen Sprache zu sehen. Aber vielleicht habe ich deinen Punkt missverstanden.
In jedem Fall kannst du jetzt die Anzahl der verfügbaren Schnittstellensprachen einschränken, indem du Multilingual Plugin 🌐 besuchst.
8 „Gefällt mir“
Wow, das sieht fantastisch aus. Ich werde mir das so bald wie möglich genauer ansehen.
In einer perfekten Welt ohne Ressourcenbeschränkungen wäre es natürlich besser, alles zu übersetzen. Das Problem, das zu lösen versucht wurde, ist jedoch, dass Sie im Grunde alle angepassten Texte in jede Sprache übersetzen müssen (da es nicht möglich ist, festzulegen, welche Sprachen den Benutzern zur Verfügung stehen). Wenn Ihr Plugin dies nun löst, wäre dies, wie bereits erwähnt, ein großer Fortschritt:
Um zu klären, was ich mit „negativen Nebeneffekten
1 „Gefällt mir“
Ja, ich verstehe, was du meinst.
Allerdings frage ich mich, ob du den Bedarf, den angepassten Text in jede Sprache zu übersetzen, nicht überbetonest, anstatt einfach die häufigsten Sprachen deiner Nutzer ins Visier zu nehmen?
Lass uns das einmal durchspielen. Ich finde, es ist einfacher, das anhand von Beispielen zu diskutieren.
Angenommen, du hast ein Forum in Belgien über Radfahren 
. 95 % deiner Nutzer sprechen entweder Niederländisch 
(40 %), Französisch 
(30 %), Deutsch 
(15 %) oder Englisch 
(10 % – Touristen). Die anderen 5 % sprechen eine Mischung aus anderen Sprachen. Die Standardsprache des Forums ist Niederländisch.
Nehmen wir nun an, wir passen den Text des narrativen Bots nur in Niederländisch an, verlassen uns auf die „Fallback“-Funktion, und die niederländische Anpassung wird jedem Nutzer des Forums angezeigt. Technisch gesehen würde jeder denselben Text sehen, aber 60 % der Nutzer des Forums würden ihn möglicherweise nicht oder nur teilweise verstehen (zumal die Französisch- und Deutschsprachigen das Forum möglicherweise als „flämisch“ empfinden).
Im Gegensatz dazu: Angenommen, du hast (mit Hilfe einiger Moderatoren oder erfahrener Nutzer, die Muttersprachler sind) den angepassten Willkommens-Text auch ins Französische, Deutsche und Englische übersetzt, und die „Fallback“-Funktion wäre nicht vorhanden. Dann würden 95 % der Nutzer des Forums den angepassten Text in einer Sprache sehen, die sie vollständig verstehen (und mit der sie sich identifizieren können), und 5 % der Nutzer würden einen anderen Text sehen.
In einem solchen Szenario mag die Fallback-Funktion für diese 5 % der Fälle nützlich sein, aber das größere Problem scheint darin zu bestehen, den angepassten Text in die wenigen am häufigsten verwendeten Sprachen zu übersetzen, anstatt dass eine kleine Minderheit der Nutzer einen anderen Text sieht.
4 „Gefällt mir“