After some searching upon this, I must admit that I am confused.
Do I get it right that there is no possibility to have a Discourse forum running with formal german? In the business world, the informal german is not very common…
We cannot use an informal german forum here.
If I just did not find the right point, would you please give me a hint?
Thank you,
DDo
Discourse currently has one German translation on Transifex.
I’m not aware of Transifex offering a discrete formal German offering, or any other projects which offer both the formal and informal, but if Transifex supports it then Discourse can too.
Last time this was discussed at Support for formal/informal language variations the conclusion was that Transifex doesn’t support those variations:
I think that highly depends on the type of business… and speaking for myself, I always find it strange when a computer (piece of software) addresses me formally. But yeah, I know that everyone feels different about such things.
I guess it could make sense for some businesses to use formal language for emails sent by Discourse as well as texts like Privacy Policy and Terms of Services. But you most likely want to edit those anyway, so it shouldn’t be a big problem.
Thank you all for your rapid replies.
I am sorry, I didn’t want to start a discussion if informal german is ok or not - since we address the majority of our customers in conversations and E-Mails in formal german, a forum that is only capable of informal german is not choosable.
I am afraid but it is as simple as that. Althhough I like what I saw of Discourse up to now.
Does someone know: How can I find out if there is a formal german version somewhere on transifex?
@gerhard Maybe I’m old-fashioned, but for me in the non-private sector informal language is still something that has to be agreed upon by both sides. Addressing someone informat without their consent is impolite or at least a form of disrespect. I would not expect that in a supermarket, hotel or bank without being puzzled.
I’m not aware of a formal German translation.
I would analyze the language strings if I were you. Maybe you‘ll just need to replace several phrases from casual “du” to “Sie”.
On the other hand, if German is too personal, I‘d leave the locale to English. Most of the conversations in Discourse are either self explaining or have common icons.
We use Discourse at work, and didn‘t care about a German version. Probably because the majority of our tools in IT are English only.
You would need to replace hundreds (I estimate around 450) phrases, and not just from “du” to “Sie” - you’d also need to change the verb forms. So this is not an easy task.
Furthermore, it is not a one-time task. Discourse evolves rapidly. New strings are added and existing strings go through changes.
Hello - I’m back again.
I just had an email conversation with Thelma from Transifex. She informs me that
“you can select as many target languages as you want and as many locales as you want. For example, you can add German (de) and German (Germany) (de_DE)”
So, is it possible to just add German (Germany) (de_DE) as the formal variant of german, based upon the existing German (de)? It should be possible with overseeable effort to translate all strings containing “dein*” and “du”.
Is it correct that all phrases that show in the users area are in files named “client” ?
kind regards,
Dorothea
User-viewable strings come from both client and server localization files. For a complete* translation, you’d need both. client vs. server is only relevant as to whether the strings are accessed via back-end Ruby code or front-end JavaScript code — from the end user’s point of view, they’re basically indistinguishable.
*“Complete” comes with the caveat that @rizka mentioned, namely that the available strings are constantly changing. I’m not sure how configurable fallbacks are in Transifex, but my guess is that de_DE would fall back to de by default. Someone please correct me if I’m wrong.
Can someone please add a second german language into Transifex? Best based upon the existing informal german translation, so that it would not be necessary to translate everything again, but only the phrases with personal addressing.
I am not afraid to do the work. 450 phrases do not sound too much. And yes, I have seen the constant changing in the translation files in the last weeks. I’m sure you noticed me doing some work there.
I believe the possibility to have a formal german translation will make Discourse interesting for a larger amount of users. Other forum softwares offer those. But Discourse is a better forum, don’t you think?
So I kindly ask to add a second german translation.
kind regards,
Dorothea
Hi Discourse Team,
who must I ask about the Transifex languages, who is able to add one?
I don’t seem to find the attention that I need…
Merci,
Dorothea
Sure, I could add de_DE as an additional German language, but please be advised that this solution is suboptimal and will be very frustrating for translators.
There is no way to tell translators that de uses informal and de_DE uses formal language.
The source language will be English. You need to start from scratch. Sure, you could import the existing German translations as a starting point, but afterwards there’s no way to sync them automatically. And as far as I know de and de_DE do not share the same translation memory, so that’s no help either.
If you need the source language to be German you could create your own project on Transifex, add the German translations as source files and optionally configure automatic updates for source files.
I’ll be sending a feature request to Transifex, but honestly I’d be surprised if this will be improved in the near future. Other platforms like Crowdin do a better job by allowing custom languages.
Dear @gerhard,
thank you again for your help.
I’ve tried what is described here Gender neutral German translation by
Still have to figure out how I can mark all those terms which don’t need to be altered as translated.
Still have no clue how to Configure auto update for the source files by pointing them to the German locale files (raw) on Github.
And “Replace the existing German locale files with the new ones in your Discourse instance.” is also on the list.
But hey! It’s a start. And if there comes the opportunity to do a formal german translation within the official project, we can use this.
regards,
Dorothea
Okay, I think I need some advice - on “Replace the existing German locale files with the new ones in your Discourse instance.”: How can that be done? Where do I tell my installation where to get the translations from?
Thank you for your hints,
Dorothea
May I ask again?
Still haven’t figured out how to “Replace the existing German locale files with the new ones in your Discourse instance.”
Now I have translated files on Transifex (not all ready, but on the way. Filed as de_DE).
Still have no idea how to get them into my Discourse which lives in a docker container in an ubunto environment. Can anyone help me?
Thank you,
Dorothea
When I wrote “Replace the existing German locale files with the new ones in your Discourse instance.” I should have mentioned that this isn’t as easy as it sounds. 
You will need a development environment in order to follow Add a new locale from plugin and you will need https://github.com/discourse/translations-manager to pull translations from Transifex and apply some transformations to the locale files.
Unfortunately this is a non-trivial task if you aren’t familiar with the tools. I’d really like to improve the whole process of creating language variants, but that’s probably a project for next year. However, I can give you a hand if you are willing to wait until the end of June.
Hey @gerhard,
I think I have a running Development environment now (still trying to set it up within docker, but the one set up along the instructions in Beginners Guide to Install Discourse on Ubuntu for Development seems to be willing to run), but struggling with Add a new locale from plugin and https://github.com/discourse/translations-manager.
Can you give some advice?
Thank you,
Dorothea
That’s good to hear that you managed to figure out most of the stuff on your own! 
Is your plugin available on GitHub, so that I can take a look at what you have right now.