Not sure what Scrivener for Windows says in this menu, but I’d imagine very few users dare to click on it to find out what actually happens:
Instead of “Beenden und Fenster schließen”.
There’s only one possibility what “Windows beenden” means in German, and it’s “Shut down (Microsoft) Windows.” 
It’s normal to have translation issues, and there are more problems on the Windows side. It often translates the ‘&’ in shortcuts like ‘&Editor’ into ‘and’, causing the meaning of the entire statement to be incorrect.
Shit happens. That’s normal. Doesn’t mean it can live there rent-free forever.
Thanks, I’ve changed it to “Beenden und Fenster schließen” for the next update. This was the problem we had with hiring a translation company without knowledge of context and the software.
Thanks for the quick response!
The German Scrivener localization (at least on macOS) is actually not that bad in the grand scheme of things, especially compared to the horrors other users have reported regarding their languages.
But I can see when it went off the rails at the latest, there are plenty of places (even in this one screenshot) without translation. It’s a luxury problem, since our languages are so closely related *, but going through all the menus one by one is a sobering experience.
* Would you understand “Lizenz deaktivieren …”? Yeah, works in both directions.
On the plus side, the AppReg translations you have done for that “other project” will ensure “Deactivate License…” gets translated in Scrivener, too, since that’s a framework shared between our apps. 
We really need to make all of the Scrivener translation files available for anyone who wants to correct anything…
Almost forgot, this one has a dark twin when holding ⌥, if “Reopen projects that were open on quit” is enabled disabled in Settings → General → Startup: “Quit and Keep Windows”
Currently: “Beenden und Windows behalten” (
)
Should be: “Beenden und Fenster beibehalten”
YES!
Scapple is also mixed between Portuguese and English.
Mac Scapple has no German translation at all (it’s better that way than a partial one, I guess). Keith is probably starting to hate us. 
Fixed, thanks!
Ha, all I hate is how difficult it is to keep translations inline. I think we do just need to create a thread with a link to all the translation files (maybe a thread for each language), so that if users wish to provides with some fixes, they can, or the threads provide easy places to report translation issues that we can fix our end.
Thanks! 
If you can make this process work without too much hassle, that would be great. I like the idea of one thread per product and language (assuming very specific debates will break out sooner or later).
