howto: Localisation - WordPress         rev 24 may 2019

> gettext | WP_LANG | sources

.......................................................
gettext:

i18n - we use these "gettext functions" for all strings.
  Then 
  1) gettext, poedit, and other tools can extract them
        to make a .po file for translation.
  2) word|classicpress can extract them from the code and use
        that .po file to emit the strings in the wanted language.

  _e( 'word or phrase', 'textdomain' );
  __( 'word or phrase', 'textdomain' );
  _x( 'word or phrase', 'textdomain' );


.......................................................
WP_LANG

  * Does changing 'WPLANG' in wp-config.php just effect the admin language or does it have other consequences?
      https://wordpress.stackexchange.com/questions/4030/does-changing-wplang-in-wp-config-php-just-effect-the-admin-language-or-does-i?rq=1
      It also changes what language strings are emitted in 
        the front end (like comment messages) for word|classicpress,
        plugins, and themes.


.......................................................
sources:

  * Localization - Developer's handbook
      https://developer.wordpress.org/themes/functionality/localization/

  * Translating - in I18n for WordPress Developers - Codex
      https://codex.wordpress.org/I18n_for_WordPress_Developers#Translating_Plugins_and_Themes

  * Using Different Languages in WordPress Theme and Admin
      https://amigotechnotes.wordpress.com/2013/12/14/different-languages-in-wordpress-theme-and-admin/
      dec 2013


_______________________________________________________
begin  9 nov 2018
-- 0 --