With the snapshot 23w35a, a bug fix for the issue MC-264558 has been released, proving a correctly spelled "connect.reconfiguring" translation key. However, the incorrectly written "connect.reconfiging" key still remains in the en_us.json language file.
Linked issues
relates to 1
Attachments
Comments 5
Our language content supports multiple versions. Removed keys are left in to avoid translations breaking on older versions.
Shouldn't they only exist on older versions then? en_us is included in the version jar, so removing strings that are no longer used won't break old versions, as they still have the old en_us file in their version jars.
Crowdin and non-en_us are understandable.
Speculation on my part, but I'd imagine the en_us file is uploaded to Crowdin, where all strings in there are then being translated for all versions. So removing the string from en_us would probably break that automation and delete the translation strings on Crowdin as well.
That is correct, en_us.json is uploaded to Crowdin with every snapshot, pre-release and release candidate and thus automatically updated. Translations are supposed to be preserved and can even be retroactively updated for older versions if necessary, in case a harmful mistake slipped in. This retroactive fix would not be possible without the (outdated) string.
Could be intended; see this comment regarding backwards compatibility of translations.