Avoid using <code> in translation strings (wp-admin/options-general.php)‎

[ramiy]

Related: #30612, #30614, #31840, #31848, #31851

[SergeyBiryukov]

Now that we have better fuzzy matching, I guess it's time to handle this and other tickets.

Refreshed the patch. Not sure if we should also add translator comments for all placeholders as we go, or just for the ones that are not clear from the context.

I've found a lot of placeholders without comments, e.g. in a similar string​ in user-edit.php.

Will wait for Dominik's return next week to coordinate the changes.

[ramiy]

Replying to SergeyBiryukov:

Not sure if we should also add translator comments for all placeholders as we go, or just for the ones that are not clear from the context.

If we already fixing the strings, let's add translator comments. I don't know when we will be the next time we fix those string.

[wonderboymusic]

In 34294:

Don't use <code> in translation strings in options-general.php.

Props ramiy, SergeyBiryukov.
Fixes #31852.

[SergeyBiryukov]

In 34300:

Add missing translator comments after [34294].

See #31852.