WordPress.org

Make WordPress Core

Opened 5 months ago

Last modified 5 months ago

#38882 assigned task (blessed)

Add translator comments to every string that contains a placeholder

Reported by: johnbillion Owned by: johnbillion
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: I18N Keywords:
Focuses: Cc:

Description

Strings that contain placeholders — such as %s, %d, and %1$s — should include accompanying translator comments. This provides context to translators and allows for more accurate translations.

The meaning of even seemingly simple strings containing placeholders may not be clear to translators who are not intimately familiar with WordPress, unless a translator comment is provided.

Change History (6)

#1 @johnbillion
5 months ago

  • Owner set to johnbillion
  • Status changed from new to assigned

#3 @johnbillion
5 months ago

In 39323:

I18n: Begin introducing translator comments for strings which include placeholders but no accompanying translator comment.

Adds context to one string used in two different contexts for the new user and new site signup email notification.

More to come.

See #38882

#4 @johnbillion
5 months ago

In 39324:

Remove an erroneous @TODO introduced in [39323].

See #38882

#5 @johnbillion
5 months ago

In 39326:

I18n: Introduce more translator comments for strings that contain placeholders but don't have an accompanying translator comment.

See #38882

#6 @ocean90
5 months ago

@johnbillion Comments which are for the placeholders %s or %d shouldn't use "1", it should be the name of the placeholder.

Note: See TracTickets for help on using tickets.