Missing l10n for admonseparator and version...

[ghost]

Release notes build:

[  149s] No "ca" localization of "admonseparator" exists; using "en".
[  149s] No "ca" localization of "version" exists; using "en".

[  189s] No "id" localization of "admonseparator" exists; using "en".
[  189s] No "id" localization of "version" exists; using "en".

[  189s] No "ja" localization of "version" exists; using "en".

[  190s] No "nl" localization of "version" exists; using "en".

[  193s] No "uk" localization of "admonseparator" exists; using "en".
[  193s] No "uk" localization of "version" exists; using "en".

[  193s] No "sv" localization of "version" exists; using "en".

[  129s] No "sk" localization of "version" exists; using "en".
[  129s] No "sk" localization of "showcontentsoverview" exists; using "en".
[  129s] No "sk" localization of "totopofpage" exists; using "en".
[  129s] No "sk" localization of "admonseparator" exists; using "en".
[  129s] No "sk" localization of "sharethispage" exists; using "en".
[  129s] No "sk" localization of "shareviafacebook" exists; using "en".
[  129s] No "sk" localization of "shareviagoogleplus" exists; using "en".
[  129s] No "sk" localization of "shareviatwitter" exists; using "en".
[  129s] No "sk" localization of "printthispage" exists; using "en".

These are only the things that appear with current openSUSE RN. As more translators translate more, that list of issues would inevitably grow. Additionally, it seems the in many cases, we actually use empty strings instead of the "en" string which would still be okay-ish.

• [x] ca
• [x] id
• [x] ja
• [x] nl
• [x] sv
• [x] sk
• [x] uk

[tomschr]

This was fixed in the suse2022-ns stylesheets some time ago. Not relevant anymore.