🇩🇪 Error in the German translation? Report it here!

[gerhard (Gerhard Schlager)]

“Server and Protocols” would actually fit space-wise. The discussion about & and u. escaped me. As long as there is no solution in the UI itself, we probably have no choice but to shorten texts or omit less important information.

If I notice that a text doesn’t have enough space, I adjust it in the translations. If you notice something, please just suggest a suitable translation on Crowdin and, if necessary, point out in a comment that it makes sense for space reasons.

[GuidoD (Guido Drehsen)]

I do not have any error to report.

I just want to say goodbye. After 8 years we did shut down our self hosted discourse instance End of March since we did dissolve our political party End of March.

During the last 8 years I have been the admin of our instance and during that time I did also do a lot of the translations into German for Discourse (discourse, discourse-ai, data-explorer and some other plugins). This has been my way to give something back to Discourse for using this great software on our server for free.

But now the time has come so say goodbye to the community.
@Moin is doing also quite a lot of the German translations, so this great software does still have besides @gerhard other persons doing the translations into German.
@gerhard you can remove me in Crowdin from the discourse translators for German.

Keep up the good work.
Thanks and all the best for everyone
Guido

[tobiaseigen]

Wow, Guido! We will miss you. Thank you for your contributions to the German translation over the years. Good luck with your future endeavors and of course when you spin up your next online community, we hope it will be with Discourse!

[gerhard (Gerhard Schlager)]

Thank you for all your contributions over the years. I checked — turns out you’ve translated around 30,000 words in that time!

Wishing you all the very best, and I hope our paths cross again someday.

[Moin]

Some texts related to “Impersonation” were recently added. For example, “You are impersonating %{username}” and “Stop impersonating”.
Certainly, the current translation “Nutzersicht” (user view) is not a mistake, but I always felt something was missing that creates awareness that you are not only seeing the same as the user, but also acting as them. Therefore, I thought it might be interesting to hear what other admins think about this.

There was even a short conversation about this on Crowdin:

Is the existing one an accurate translation (I assume it should be understood as “view page as certain user”)?

Yes, admins can impersonate other users which allows them to see and do everything the user is allowed to do. I’m not sure if the current translation is accurate enough. Probably.

The error message when impersonating fails currently speaks of “slipping into the role”^[1]. The same applies to the explanatory text of the button^[2].
If we orient ourselves by this, we could change the impersonate button to “In Rolle wechseln” (Switch role). “Als Benutzer anmelden” (Log in as user) might be even clearer, but I feel it fits less well with the new feature, where you can switch back without logging out. “Benutzer übernehmen” (Take over user) might also be possible. It’s not quite as long, but perhaps a bit drastic.

Maybe someone has even better ideas than what I came up with shortly before midnight

---

1. admin_js.admin.impersonate.invalid: Sorry, you are not allowed to slip into the role of this user. ↩︎

2. admin_js.admin.impersonate.help: Use this tool to slip into the role of another user for troubleshooting. You must log out when you are finished. ↩︎

[asa]

Perhaps the word “imitate” would be better as “imitate user” or “You are (currently) imitating, %{username}”.
I would understand that better if I saw it for the first time.

[tobiaseigen]

Thanks for raising this issue, Moin! While you are talking about the German translation, I think it makes sense to raise this also in Add 'stop impersonating' link to user avatar dropdown when impersonating - #41 by ted where changes to the feature are being talked about.

In my personal opinion, the fact that “impersonation” doesn’t translate well is a case for changing how the feature is named. I like “log in as user”. I also can imagine “Switch to @impersonated_user account” and then “Switch back to @my_account”. I think this works in english and also suspect it translates better into most languages.

[Moin]

@tobiaseigen

I think it makes sense to raise this also in Add ‘stop impersonating’ link to user avatar dropdown when impersonating - #41 by ted

I don’t quite understand the connection: Why should the choice of the term “Impersonation” be discussed now in a topic about a new option to more easily leave this mode? The text of the button (which, by the way, has existed for more than 5 years) is not related to ending user impersonation.

For me, “Impersonation” is also a sensible name for the feature because it is easy to search for in the documentation and other topics on the forum. “Log in as user” would make that more difficult. These are all very commonly used words, it’s less suitable as a keyword, and the previous posts would still use the old term.

In translation, one often has to choose more suitable terms anyway. We also translate “staff” as “Team” and “to tag” as “mit einem Schlagwort versehen”. There isn’t always the perfect term for something in every language. But then it is sufficient to optimize the translation. There’s no need to rename the feature.

[Moin]

@Moin

I also tried to suggest “unbegrenzt” for the chat history (js.chat.retention_reminders.indefinitely_short) because for me “unbestimmt” sounds like “not defined”.
…
But I cannot suggest “unbegrenzt” because it has been suggested before.

That is still the case. What do I need to do for something to change about that?

[gerhard (Gerhard Schlager)]

@Moin

Aber ich kann „unbegrenzt“ nicht vorschlagen, da es bereits zuvor vorgeschlagen wurde.

I’m setting a reminder to look at this when I’m back from vacation.

[Moin]

I noticed that the German translation for “dismiss” varies greatly. Even in the same context, different phrasings are used.

Here is an example of what is displayed when you call /unread:
The “Dismiss” button is immediately present next to the “new topic” button. If you then use the mass selection, there is a second “Dismiss” button in the menu:

In German, we use “Ignorieren” and “Verwerfen” once, even though both buttons do the same thing.

It’s the same with the modal that asks if you are sure.

• Without selected posts, it looks like this:
  
  
  
  
  In English, “Dismiss” is used in both the heading and the button. The German heading uses the 3rd term after “Ignorieren” and “Verwerfen”: “Ausblenden”. The button at the bottom uses “ignorieren” again.
• With selected posts, “ignorieren” is used in both places:
  
  
  

In the notification menu, “Alles gelesen” (read all) is used. I think that fits very well there, even though it is of course another term for pretty much the same thing.

I find it less bothersome that we use something different in another context, like in the notifications on the dashboard where “verwerfen” (discard) is used.

But in the context of “dismiss unread topic/post/notification,” I would find consistent phrasing more helpful. Especially “ausblenden” (hide) sounds to me more like a phrasing for “not listed” / “invisible” (en: “unlist”).

[Moin]

Previously, I thought it would be easier to discuss one change at a time. Now I have the impression that it might be better if I post more at once. Maybe everything can be improved at once if someone takes the time for it.

onebox.github.opened

opened

offen

I think “geöffnet” would be more appropriate. It’s not about the current status, but about when the PR was opened.

admin_js.admin.backups.files_title & admin_js.admin.backups.menu.backup_files

Backup files

Dateien sichern

As Dax confirmed with that one text, this is a noun. Under the heading, you can see the backups that have been created.

reports.signups.title

Signups

Neue Benutzer

“Neue Benutzer” has a lot of connection to trust level 0 (new user) for me. I think “Anmeldungen” or “Registrierungen” would clarify that better.

site_settings.chat_auto_silence_from_flags_duration

Number of minutes that users will be silenced for when they are automatically silenced due to flagged chat messages.

Anzahl der Minuten, für die Benutzer stummgeschaltet werden, wenn sie aufgrund markierter Chat-Nachrichten automatisch stummgeschaltet werden.

It should be “reported” and not “flagged”.

js.discourse_ai.embeddings.semantic_search_results.new

Press ‘search’ to begin looking for new results with AI

Drücke auf „Suchen“, um mit der KI nach neuen Ergebnissen zu suchen

I think “Suche” would better match the text on the button.

discourse_ai.ai_bot.tool_options.update_artifact.update_algorithm.name

Update Algorithm

Algorithmus aktualisieren

As Nat confirmed in the comment, “update” is a noun and not a verb.

js.discourse_automation.scriptables.suspend_user_by_email.fields.suspend_until.label

Suspend until (default)

Aussetzen bis (Standard)

In most places, “suspend” is translated as “sperren”. This includes the name of the script (discourse_automation.scriptables.suspend_user_by_email.title).

js.discourse_automation.triggerables.after_post_cook.fields.restricted_tags.description & js.discourse_automation.triggerables.post_created_edited.fields.restricted_tags.description

Optional, will trigger only if the post has any of these tags

Optional. Wird nur ausgelöst, wenn der Beitrag eines dieser Schlagwörter enthält

Optional. Wird nur bei Beiträgen mit einem dieser Schlagwörter ausgelöst

I have the impression that the translations should be identical. As I understood it, “enthält” (contains), which seems to refer to the content, is rather confusing.

discourse_automation.scriptables.recurring_data_explorer_result_topic.description

Get scheduled reports posted to a specific topic

Geplante Berichte zu einem bestimmten Thema veröffentlichen

I think it should be “in a specific topic”.

[Moin]

Is there a result from viewing? I cannot see any change in Crowdin.

[Moin]

I was working on the translation for

admin_js.admin.embedding.post_author_description:
Author for all embedded topics from this host, overriding blog page meta tags. Leave empty to read author from the page’s or tags.

and

site_settings.google_site_verification_token
Google search console verification token. Will be included as a meta tag in the HTML head.

I had the feeling that “tags” here does not refer to tags that you add to a topic in Discourse and which we translate into German as “Schlagwörter” (keywords), but rather to the meta tags of a website, which I would not translate.

But then I checked other translations that refer to meta tags and found admin_js.admin.embedding.sample (It’s a little long so I won’t add a full quote, so here is a link to Crowdin).

Discourse will automatically lookup the user by the <code>content</code> attribute of the <code>&lt;meta&gt;</code> tags with <code>name</code> attribute set to <code>discourse-username</code> or <code>author</code>.

The current German translation is:

Discourse sucht den Benutzer automatisch anhand des <code>content</code>-Attributes in den <code>&lt;meta&gt;</code>-Schlagwörtern, wenn das Attribut <code>name</code> den Wert <code>discourse-username</code> oder <code>author</code> hat.

That’s what the paid proofreader entered 3 years ago to replace the translation by @gerhard , which used “meta tags” in the German translation just as I had done today

Discourse sucht den Benutzer automatisch anhand des <code>content</code> Attributes in den <code>&lt;meta&gt;</code> Tags, wenn das Attribut <code>name</code> den Wert <code>discourse-username</code> oder <code>author</code> hat.

Now I’m wondering whether to go with what I think makes sense, or to go with what the paid translator chose to keep the meta tag translation consistent.

[Moin]

The translation of Topic Timer is somehow inconsistent. Regardless of which version we choose, in the end multiple translations need to be changed, which is why I find a consolidated discussion here more practical than comments on all affected texts on Crowdin.

The ratio is nearly 50:50. Translations from 5 years ago use “Zeitschaltuhr”, while newer translations tend to use “Timer”.

“Timer”

key	English	German
js.topic.actions.timed_update	Set Topic Timer…	Themen-Timer einstellen …
discourse_automation.scriptables .set_topic_timer.description	Set a topic timer on a topic	Themen-Timer für ein Thema festlegen
discourse_automation.scriptables .set_topic_timer.title	Set Topic Timer	Themen-Timer einstellen [1]
js.discourse_automation.scriptables .set_topic_timer.fields.duration.label	Timer Duration	Dauer des Timers
js.discourse_automation.scriptables .set_topic_timer.fields.type.label	Timer Type	Timer-Typ

“Zeitschaltuhr”

key	English	German
js.styleguide.sections.topic_timer_info.title	Topic Timers	Zeitschaltuhren
js.topic.topic_status_update.title	Topic Timer	Zeitschaltuhr
js.topic.topic_status_update.save	Set Timer	Zeitschaltuhr aktivieren
topic_statuses.auto_deleted_by_timer	Automatically deleted by timer.	Automatisch gelöscht durch Zeitschaltuhr.

I would prefer “Timer” as the term. To me, a “Zeitschaltuhr” implies something that recurs regularly (the Christmas lights turn on every evening), which is not the case in this context.
But I would also use “Tags” for keywords. In general, there is a strong trend towards using German terms.
What do others think? Timer? Zeitschaltuhr? Or another German word for Timer?

---

1. yes, somehow with a space at the end ↩︎