Welcome, visitor! Log in

Source View: ngettext

To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).

Understanding Source Code

The best way to understand what a hook does is to look at where it occurs in the source code.

  • Action hooks look like this: do_action( "hook_name" )
  • Filter hooks look like this: apply_filters( "hook_name", "what_to_filter" ).

Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.

Source View

Line Code
232  * @param string $single The text that will be used if $number is 1
233  * @param string $plural The text that will be used if $number is not 1
234  * @param int $number The number to compare against to use either $single or $plural
235  * @param string $domain Optional. The domain identifier the text should be retrieved in
236  * @return string Either $single or $plural translated text
237  */
238 function _n( $single, $plural, $number, $domain = 'default' ) {
239      $translations = &get_translations_for_domain( $domain );
240      $translation = $translations->translate_plural( $single, $plural, $number );
241      return apply_filters( 'ngettext', $translation, $single, $plural, $number, $domain );
242 }
244 /**
245  * A hybrid of _n() and _x(). It supports contexts and plurals.
246  *
247  * @see _n()
248  * @see _x()
249  *
250  */