I18N: Use /* */ block style for translator comments

[itzmekhokan]

Trac ticket: https://core.trac.wordpress.org/ticket/65518

What

Converts the remaining // translators: line comments in core to the /* translators: */ block comment style that is used consistently throughout wp-admin and wp-includes (2,636 block-style vs. 27 line-style before this change).

Why

Per the ticket discussion, this is a coding-standards consistency change. To be clear about scope: the // translators: style is still extracted correctly by wp i18n make-pot / xgettext when the comment sits directly above the gettext call, so this is not fixing broken extraction — it is aligning the few outliers with the documented block-comment convention.

Scope

This PR covers the 8 core-authored files (14 occurrences):

• wp-admin/site-health.php
• wp-admin/includes/class-wp-site-health.php
• wp-includes/abilities-api/class-wp-abilities-registry.php
• wp-includes/abilities-api/class-wp-ability-categories-registry.php
• wp-includes/class-wp-icons-registry.php
• wp-includes/fonts/class-wp-font-collection.php
• wp-includes/html-api/class-wp-html-processor.php
• wp-includes/rest-api/endpoints/class-wp-rest-icons-controller.php

The // translators: comments in wp-includes/blocks/*.php are intentionally excluded, as those files are maintained in the Gutenberg plugin and need to be changed there first (per @sabernhardt in comment:2, +1 @mukesh27 in comment:3).

Notes

• Pure comment-style change; no functional impact, no string changes.
• php -l passes on all touched files.

[github-actions]

Hi there! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

• PHP Coding Standards
• CSS Coding Standards
• HTML Coding Standards
• JavaScript Coding Standards
• Accessibility Coding Standards
• Inline Documentation Standards

Thank you,
The WordPress Project

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props khokansardar.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[mukeshpanchal27]

Make sure to add end period.

Suggested change

	/* translators: %s is the name of any user-provided key */
	/* translators: %s is the name of any user-provided key. */