This is done by passing all strings that your custom code outputs through the translation API functions. This is used to both swap your strings for their translated variant at runtime depending on the language of the site, and also be used as markers for generating translation template files (POT files).
Once you have generated a POT file for you custom code, you can provide your translators with these files. Typically programs such as poedit are used to author translations.
Whenever you output a string in code, you must use a translation function. Altis uses the WordPress Translation API to provide code level internationalization (i18n). Translations in code are tied to a "Text Domain" which is an identifier for which translation file should be used for a given translation. It's recommended you use a single translation domain for all your project's custom code. This will mean you only need to get a single POT file translated.
Whenever you "hardcode" strings in PHP, you should wrap them in the appropriate translation function for the context. For example, consider the following code.
To make this translatable, it must be wrapped in a translation function, so the string can be swapped at runtime. In this case the translation function
echo). It takes the string and text domain, translates it, and escapes the output for use between HTML tags.
<h2>'Search Results', 'my-text-domain' ) </h2>esc_html_e(
Whenever strings are directly outputted, always use the appropriate escaping translation function. Below is a reference for the translation function that should be used in which context.
||Output a translated string between HTML tags|
||Output a translated string in an HTML element attribute.|
||Return a translated string intended for use between HTML tags|
||Return a translated string intended for use in an HTML element attribute.|
When strings are used for further processing, function calls and or more advanced translation usages, the general class of translation functions should be used.
||Return the translated string for a given text domain.|
||Return a translated string for a singular / plural variation.|
||Return the translated string for the text domain, specifying a context string to be provided to translators.|
In situations when the strings contain dynamic data, use placeholders as part of the translation string, and pass the result to
sprintf (and to an escaping function when outputting.)
echo esc_html( sprintf( __( 'We found %d search results.', 'my-text-domain' ), $results_count ) );
See Translatable Strings for details on the functions you should use, depending on context.
Once you have ensured all the strings in your custom code are using translation functions, you must generated a POT file from the codebase. This is done use the cli command
wp i18n make-pot. If you want to generate a POT file for your whole project:
wp i18n make-pot content --domain=<your-text-domain> <your-text-domain>.pot
This will place a new file at the path
The POT files you create should be passed to your translation team. Their translations should be exported as
.mo files. Each language will have it's own translated file. Copy the
.mo files to