JabRef has translation files
JabRef_it.properties, ... There are translated and unstranslated strings. Which ones should be in the translation file?
Translators should find new strings to translate easily
New strings to translate should be written into
JabRef_en.properties to enable translation by the translators
Crowdin should be kept as translation platform, because 1) it is much easier for the translators than the GitHub workflow and 2) it is free for OSS projects.
Only translated strings in language file
Translated and untranslated strings in language file, have value the untranslated string to indicate untranslated
Translated and untranslated strings in language file, have empty to indicate untranslated
Chosen option: "Only translated strings in language file", because comes out best (see below.
Good, because Crowdin supports it
Bad, because translators need tooling to see untranslated strings
Bad, because issues with FXML (https://github.com/JabRef/jabref/issues/3796)
Good, because no issues with FXML
Good, because Crowin supports it
Bad, because untranslated strings cannot be identified easily in latin languages
Good, because untranslated strings can be identified easily
Good, because works with FMXL (?)
Bad, because Crowdin does not support it
Related to ADR-0001.