Reasons for creating this PR

We do not want to remove key–message pairs that are likely to be needed for translation again, as that would cause unnecessary and frustrating rework and slow down the completion of translations.

The situation is quite good (around 10 removed), but after the release of Skosmos 3, the list needs to be reviewed again, since some of the key–message pairs used in Skosmos 2 will probably end up unused.

Link to relevant issue(s), if any

#1813

• Closes Match the translation tags in the translation files with those in the Skosmos code and push the changes to Lokalise #1813

Description of the changes in this PR

When a key–message pair in messages.en.json should be removed

A key–message pair will be removed only if:

• it is not used in Skosmos 3
• and it was not used in Skosmos 2 either (the probability of inheritance to Skosmos 3 is rather high)
• the key–message pair is not generic enough to being propably used later

Searching for and evaluating usage cases

Open the attached file messages.en-checklist.json, where:

• N → the pair will be removed
• ? → uncertain, difficult to decide

In the Skosmos root directory, run:

grep -nr --include='*.js' --include='*.php' --include='*.twig' "[search text]" [skosmos 2 folder] | grep trans
grep -nr --include='*.js' --include='*.php' --include='*.twig' "[search text]" . | grep trans

Command-line helpers (in Skosmos root directory)

List all found translation keys and their states

Note:
The following command also lists as unused those key-message pairs in the language file whose key and message are identical (even if the message itself is used)

php bin/console debug:translation en

Go through all translation keys found in PHP, JS, and Twig code

bin/console translation:extract en --dump-messages

When the translation file is finalized and merged into main, it can be pushed to Lokalise.

Known problems or uncertainties in this PR

Checklist

• phpUnit tests pass locally with my changes
• I have added tests that show that the new code works, or tests are not relevant for this PR (e.g. only HTML/CSS changes)
• The PR doesn't reduce accessibility of the front-end code (e.g. tab focus, scaling to different resolutions, use of .sr-only class, color contrast)
• The PR doesn't introduce unintended code changes (e.g. empty lines or useless reindentation)

messages.en-checklist.json