Just the ones for the keywords or all the empty strings? There are more empty strings, so this could cause confusion. When does it make sense to “translate” an empty string, and when is it intentional that it remains empty?
My idea when I saw the PR was to add a translation of the name of the setting. Sometimes words from the settings name aren’t repeated in the description, so it’s more difficult to find them with a non-English interface language. At the moment, I usually change my interface language to English before I search because then I can find results from the settings name and description with just one search.
A simple example is searching for “whisper.” As long as my interface language is English, I can find two settings because “whisper” is part of the name in one and mentioned in the description in the other:
whispers allowed groups
Allow private communication within topics for members of specified groups.
create post for category and tag changes
Create a whisper post when a topic’s category or tags change, requires whisper posts to be enabled.
I cannot do the same while my interface is in German. I can use “whisper” to find the first one and “flüster” to find the second one. But there is no way to find both. If the name of the setting was added as a keyword and translated, searching for “flüster” would return both. This is even more relevant for all settings where, for example, “email” is only part of the name but not mentioned in the description.
Maybe adding the name as a keyword would make this more obvious. Is that a problem for English if the name is also a keyword?
But I am not sure how to find other useful keywords. I see that your PR adds the English description for context (with a lot of quotation marks), but that still doesn’t tell me what might be missing in the German translation. What else did you have in mind? Everything I can think of, like having “personal message” as a keyword for all settings that use “PM” in their name and description, would probably be helpful for all languages. But with the current implementation, every translator would have to think of that themselves and add it.