Germany’s next Suspend Modes
The German translation team changed the names of the suspend states so brace for impact.
Two months ago, Nils decided to change the current state of the world … of German-speaking KDE users. It all started with an innocent question he asked himself. “Why do the sleep states in KDE have different names than the ones in other desktop environments?” … or in German: „Muss das so?“
So he went on a journey to fight the status quo by subscribing to the mailing list of our small but cosy translation team and instantly started reasoning about a better world. He talked about how the rest of the world had come to some kind of agreement and we just didn’t notice. (BTW: reminds me of the metric system that some people did not feel the need of adopting ;)
So, what was the current state, then?
There are Suspend to RAM (S3) and Suspend to Disk (S4) in KDE. Some operating systems also support a dual suspend mode where the state is restored from RAM as long as the battery survived the sleep period and otherwise the state is restored from disk. But it’s not part of KDE, so it is of no concern here.
So, let’s have a look at the differnt contenders in English and (German).
|Windows||Stand By (Standbymodus)||Hibernate (Ruhezustand)|
|OS X||Sleep (Ruhezustand)||Hibernate (Ruhezustand)|
|GNOME||Suspend (Bereitschaft)||Hibernate (Ruhezustand)|
|KDE||Suspend (Ruhezustand)||Hibernate (Tiefschlaf)|
As you can see, everybody agreed to a consistent naming scheme. Well, not really. And furthermore this table elides the fact that even in English there are different terms used. In KDE you can find for S3 (as far as I could tell):
– sleep state
– Suspend to RAM
and for S4:
– Suspend to Disk
So why change our German translation if the terms are far from unified throughout desktop environments? Mainly because of the use of Ruhezustand. In most other environments it is used for S4 and in KDE we had it for S3. OS X does not count because they just have Ruhezustand for all suspend modes (including the combined one).
So for KDE we decided to go with:
|KDE||Suspend (Standby-Modus)||Hibernate (Ruhezustand)|
While the use of Ruhezustand is less confusing now, Standby-Modus might cause forehead wrinkles for some people. So let me explain that choice a bit.
Standby has its place in the German language for 20+ years now thanks to the HiFi ages. Yes, there was a time, when music did not come from smart phone speakers.
Bereitschaft is a great contender on that front but at least for my ears does sound like the fearful state of a worker sitting at home on Saturday, carefully nipping his beer, hoping his boss won’t call him in. If more desktops would call it Bereitschaft, I would vote for it in KDE too because I like consistency, but in this “everyone on its own” state of affairs, I prefer Standby. And we use the dashed version of Standby-Modus because we prefer to separate foreign words from native words. It’s a matter of taste and the transition from “foreign” to “native” is blurry but the German KDE team once decided to go the “dashed” way for all but two or three words.
To be honest, I do not know. Because separate parts of what was formerly called KDE are realesed separately. So maybe the new terminology will arive partly with Plasma 5.6.0 on March 17th, partly with KDE Frameworks 5.21 on the 2nd Saturday of April and partly with KDE Application 16.04 on April 20th. And then there are other applications like KTorrent, where we need to wait for the next release to deliver this change.
If you think you have urgend reasons to bring to our attention before the rollout, please do so. But remember:
– I do not like it -> opinion
– I think you should have used this other term -> opinion
– There is something you did not consider and the following problems might arise […] -> reason
Opinions are good and can be discussed but do not expect us to change anything solely on one specific opinion.
Reasons are great and we will discuss them.
You can subscribe to our mailing list to ask questions, discuss matters and offer help.
Thanks to Nils for bringing this up.
There have also been some reports on mistakes or ambiguities in our translation from other people and thanks goes out to them as well. The German translation (same might apply for other translations) is a small project. We are currently two people working in our free time. So we cannot check the context and looks of every translated string. For me it boils down to checking the translated strings in applications I use. That’s probably similar for other translators. Forthermore I cannot translate domain-specific applications like Digikam, Step or Calligra, so they are in need of helping hands.
To conclude, the German translation relies on users reporting issues they see. So what are you waiting for? :)