Most of the time we try to use English for technical identifiers and German for business langugage, leading to lets say "interesting" code, but it works for us.
Most of the time we try to use English for technical identifiers and German for business langugage, leading to lets say "interesting" code, but it works for us.
Compounds have to be translated using multiple words, yes - that's just a few extra white space, it doesn't result in loss of precision.
And yeah, you can see with those two latter terms where the issue lies :)
Those two were traditionally actually used this way in the safety and security context - I think I even have the script for the "Datenschutz und Datensicherheit" lecture I had on uni in the '90s lying around somewhere in the attic.
But their meaning has changed and muddled so much over the years - probably not helped by the fact that "Sicherheit" is much closer to "security" in colloquial usage, and probably vice versa(?) - that they stopped being useful and used in this context.
Schutz is protection. Can refer to both I guess. E.g. Datenschutz would be about security, while Arbeitsschutz is about safety.