_n_noop() does not accept a textdomain

[scribu]

A plugin tryng to use register_post_status() will have a hard time making the 'label_count' property translatable, since _n_noop() doesn't have a textdomain parameter, although translate_nooped_plural() does have it.

Previously: #13996

[nacin]

It actually doesn't need it.

makepot does not use textdomains when scanning a file for strings. (It may in the future as an enhancement, to allow us to do things like move all multisite strings to their own pot, even if they exist in a regular core file.) The only job of _n_noop() is to get the string into the POT file. After that, translate_nooped_plural() is used to translate a string according to the textdomain.

We can consider this one an enhancement + maybelater, I think.

[johnbillion]

This is in fact a bug.

Example: a plugin registers a post status and uses _n_noop() for its 'label_count' parameter, and its parameters are correctly added to the plugin's POT when it's scanned. However, when the label is output by WordPress using translated_nooped_plural() there's no textdomain parameter present, so gettext will try to translate the string according to core's textdomain rather than the plugin's.

I have a patch for this which I'll upload later when I'm back at my computer.

[nacin]

Not sure I am following. Example usage in a plugin:

$num_apples = 12;
$apple_string = _n_noop( 'Apple', 'Apples' );
translate_nooped_plural( $apple_string, $num_apples, 'my-plugin-textdomain' );

When makepot.php runs over this file, the strings 'Apple' and 'Apples' will be picked up and added to the plugin's POT.
When translate_nooped_plural() fires, it will call _n() internally with the domain passed to it.

[scribu]

The trouble comes when translate_nooped_plural() isn't called by the plugin, but by Core. This happens with register_post_status(), as mentioned in the ticket description.

[nacin]

Replying to scribu:

This happens with register_post_status(), as mentioned in the ticket description.

Kind of. I would have had to look up exactly how core translates 'label_count', as that's just about all that's mentioned. That's okay, though — I get it now.

Okay, so, let's fix it.

[nacin]

Patch doesn't touch docs, just the code. Allows a domain to be specified, in which case it will override whatever is passed to translate_nooped_plural().

[nacin]

In [20648]:

Allow nooped plurals to receive a textdomain on registration to then be used on translation.

This is good for when the code registering the plural is not also translating it. This occurs
in core with register_post_status(), which accepts a nooped plural as an argument, and then
calls translate_nooped_plural() without a domain.

translate_nooped_plural() can still be called with a domain. The argument will just be overridden
if the nooped plural contains a domain key.

fixes #20188.