Opened 4 days ago
Last modified 3 days ago
#65815 new task (blessed)
I18N string fixes for 7.2
| Reported by: | joedolson | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.2 |
| Component: | I18N | Version: | |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: |
Change History (3)
This ticket was mentioned in PR #11946 on WordPress/wordpress-develop by @khokansardar.
4 days ago
#1
- Keywords has-patch added
@SergeyBiryukov commented on PR #11946:
4 days ago
#2
Thanks for the PR! Merged in r63030.
This ticket was mentioned in PR #12841 on WordPress/wordpress-develop by @Soean.
3 days ago
#3
The $domain parameter of __(), _e(), _x() and the other translation functions already defaults to default. Passing 'default' explicitly in core files is redundant, and core convention is to omit the argument entirely.
Trac ticket: https://core.trac.wordpress.org/ticket/65815
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
This PR adds missing translator comments for translatable strings that include a trailing space after the colon, as part of the WordPress 7.1 I18N string improvements.
### Changes
the_tags()default prefix (Tags:) incategory-template.php.Trackback excerpt:andPingback excerpt:) inwp_notify_moderator()withinpluggable.php.These follow the established pattern used in
WP_PHPMailer(/* translators: There is a space after the colon. */) so translation tooling (WP-CLIi18n make-pot, Poedit) correctly preserves the trailing space for translators.Trac ticket: https://core.trac.wordpress.org/ticket/65815
## Use of AI Tools
N/A