• Add "Pushing to applications" section comment across 25 language files
• Remove obsolete "Could not call executable" error message translations
• Normalize whitespace and formatting in localization properties files
• Update translations for Vim-related error messages and UI strings

Add Vim section comment and normalize spacing

jablib/src/main/resources/l10n/JabRef_ar.properties

Remove obsolete executable error, add Vim comment

jablib/src/main/resources/l10n/JabRef_da.properties

Remove obsolete executable error, add Vim comment

jablib/src/main/resources/l10n/JabRef_de.properties

Description

The key "Could not call executable" is still used (e.g., in AbstractPushToApplication), but its
translations were removed from many non-English bundles (e.g., JabRef_de.properties), so users will
see the raw key text instead of a translated message. This regression is silent because the
localization bundle returns the key itself for missing entries and does not log the missing
translation.

Code

jablib/src/main/resources/l10n/JabRef_de.properties[126]

-Could\ not\ call\ executable=Konnte das Programm nicht aufrufen

Evidence

AbstractPushToApplication still requests the localized string for "Could not call executable". After
this PR, the German bundle no longer contains the corresponding properties entry (it jumps from
"Copy to clipboard" to the next key), so the localized resource set for that locale will not provide
a translated value. The localization layer loads only the locale-specific ResourceBundle (base name
"l10n/JabRef") and the fallback behavior returns the key itself when the lookup map lacks an entry,
which means the untranslated English key becomes user-visible without a warning.

jablib/src/main/java/org/jabref/logic/push/AbstractPushToApplication.java[95-105]
jablib/src/main/resources/l10n/JabRef_de.properties[121-131]
jablib/src/main/java/org/jabref/logic/l10n/Localization.java[103-107]
jablib/src/main/java/org/jabref/logic/l10n/Localization.java[139-168]
jablib/src/main/resources/l10n/JabRef_en.properties[128-134]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The localization key `Could not call executable` is still used in code (`Localization.lang("Could not call executable")`), but the corresponding properties entry was removed from many non-English localization files (e.g., `JabRef_de.properties`). This causes non-English locales to show the raw key text (English) instead of a translation.
### Issue Context
`Localization` loads `ResourceBundle.getBundle("l10n/JabRef", locale)`. For missing keys in a locale file, `LocalizationBundle.handleGetObject` returns the key itself, and `containsKey()` always returns `true`, so the issue becomes a silent UX regression.
### Fix Focus Areas
- jablib/src/main/resources/l10n/JabRef_de.properties[121-131]
- jablib/src/main/java/org/jabref/logic/push/AbstractPushToApplication.java[95-105]
- jablib/src/main/resources/l10n/JabRef_en.properties[128-134]
### Expected fix
Re-add the properties entry `Could\ not\ call\ executable=...` to each affected non-English `JabRef_<lang>.properties` file (ideally restoring the previous translations). If restoring per-locale translations is not possible in this PR, add at least an English placeholder value to prevent a missing-entry fallback, and ensure Crowdin will later overwrite it with proper translations.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Multiple localization .properties files introduce whitespace-only lines that do not change any
keys/values, creating review noise and increasing merge-conflict risk. This is unrelated
reformatting rather than a functional localization update.

Code

jablib/src/main/resources/l10n/JabRef_de.properties[R61-62]

+
+

Evidence

PR Compliance ID 2 requires avoiding unrelated formatting changes; the diff shows multiple
added/removed empty lines in translation files without any accompanying functional key/value changes
in those hunks.

AGENTS.md
jablib/src/main/resources/l10n/JabRef_de.properties[61-62]
jablib/src/main/resources/l10n/JabRef_ar.properties[32-33]
jablib/src/main/resources/l10n/JabRef_da.properties[37-38]
jablib/src/main/resources/l10n/JabRef_es.properties[61-62]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Several l10n `.properties` files include whitespace-only additions/removals that are unrelated to actual translation key/value updates.
## Issue Context
These changes increase diff noise and merge-conflict likelihood without improving functionality.
## Fix Focus Areas
- jablib/src/main/resources/l10n/JabRef_de.properties[61-62]
- jablib/src/main/resources/l10n/JabRef_ar.properties[32-33]
- jablib/src/main/resources/l10n/JabRef_da.properties[37-38]
- jablib/src/main/resources/l10n/JabRef_es.properties[61-62]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools