Can reproduce for azwiki:
https://az.wikipedia.org/wiki/X%C3%BCsusi:%C4%B0cmaKonfiqurasiyas%C4%B1

Thank you, @Shirayuki for filing this issue (and @Nemoralis for finding another example)!

The message MediaWiki:Communityconfiguration-babel-description shows <nowiki> in translated message for the following wikis (see https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3ACommunityconfiguration-babel-description&namespace=8)

• azwiki
• jawiki
• trwiki

Should the translation be corrected?

In T412159#11449375, @Etonkovidova wrote:

Should the translation be corrected?

Wouldn’t that break other stuff? I guess there is a reason @Nemoralis added this paragraph to the documentation.

By the way, the last change in this field was in late October for T401905: Unparsed non-breakable space in Special:CommunityConfiguration, although I don’t think it made the situation any worse.

In T412159#11449821, @Tacsipacsi wrote:

I guess there is a reason @Nemoralis added this paragraph to the documentation.

T379558: Using number sign as first symbol causes message to render as numbered list item

Change #1218758 had a related patch set uploaded (by Urbanecm; author: Urbanecm):

[mediawiki/extensions/CommunityConfiguration@master] fix(DashboardEditorCapability): Parse the description

https://gerrit.wikimedia.org/r/1218758

Change #1218758 merged by jenkins-bot:

[mediawiki/extensions/CommunityConfiguration@master] fix(DashboardEditorCapability): Parse the description

https://gerrit.wikimedia.org/r/1218758

Thanks for parsing the description! Couldn’t the title be similarly problematic, though?

In T412159#11467624, @Tacsipacsi wrote:

Thanks for parsing the description! Couldn’t the title be similarly problematic, though?

I don't think so. The titles are meant to be wikitext-free, mostly because they already have their own formatting added on CC's side. For example, adding a numeric list or making a part bold wouldn't make sense, because the whole title is already made bold, by CC itself. Similarly, adding a link doesn't make any sense there, because the title (as a whole) already links somewhere (namely, to the configuration editor).

On the other hand, the descriptions are meant to be longer, include explanations, and links (or potentially bold font) make sense there. In fact, the descriptions of the guidelines already include links that provide further context.

Does this make sense?

The patch https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CommunityConfiguration/+/1218758 hasn't been merged - wmf.7 still shows <nowiki> tags.

In T412159#11467955, @Urbanecm_WMF wrote:

In T412159#11467624, @Tacsipacsi wrote:

Thanks for parsing the description! Couldn’t the title be similarly problematic, though?

I don't think so. The titles are meant to be wikitext-free, mostly because they already have their own formatting added on CC's side. For example, adding a numeric list or making a part bold wouldn't make sense, because the whole title is already made bold, by CC itself. Similarly, adding a link doesn't make any sense there, because the title (as a whole) already links somewhere (namely, to the configuration editor).

The problem here was that the description was sometimes parsed, sometimes not. So it would also be a solution to ensure that the title never gets parsed – “similarly problematic” doesn’t necessarily imply a similar solution.

By the way, I could imagine that a translation needs to use italic. On the other hand, if a translator used a link or something like that, they would screw up the markup (cause invalid HTML), so it’s probably best not to allow markup – just ensure that it’s consistently not allowed.

In T412159#11474480, @Etonkovidova wrote:

The patch https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CommunityConfiguration/+/1218758 hasn't been merged - wmf.7 still shows <nowiki> tags.

Actually, it has been merged – it just hasn’t been deployed. And given the end-of-year schedule, it won’t be deployed in 2025, the next deployment train departs on 6 January 2026. (https://wikitech.wikimedia.org/wiki/Deployments is self-contradictory about whether there are backport windows in the week of 29 December, but this is such a minor issue that I’d definitely not backport it to wmf.7, so it doesn’t matter. Maybe it could be backported to REL1_45, though.)

In T412159#11480091, @Tacsipacsi wrote:

The problem here was that the description was sometimes parsed, sometimes not.

The reported problem was "wikitext is not recognised", which is why I understood "similarly problematic" as "doesn't recognise wikitext as well". In any case, I understand what you meant now.

So it would also be a solution to ensure that the title never gets parsed – “similarly problematic” doesn’t necessarily imply a similar solution.

I believe that should already be the case. If you're aware of a place where title is parsed in CommunityConfiguration, it would be helpful if you filled a task for that.

I noticed there is one last description not being parsed, so I'll go ahead and upload a patch for it.

Change #1219992 had a related patch set uploaded (by Urbanecm; author: Urbanecm):

[mediawiki/extensions/CommunityConfiguration@master] feat(DashboardEditorCapability): Consistently parse descriptions

https://gerrit.wikimedia.org/r/1219992

Change #1219992 merged by jenkins-bot:

[mediawiki/extensions/CommunityConfiguration@master] feat(DashboardEditorCapability): Consistently parse descriptions

https://gerrit.wikimedia.org/r/1219992