create a language file with the i18n string en_US, also the same procedure how with other languages, if the original is english. WordPress set the language key to en_US, if the key is empty in the wp-config.php.
Use the plugin Codestyling Localization for easy create the language files inside your WordPress Install.
Related Posts:
- How to get a translated string from a language other than the current one?
- Working with l10n contexts (_x etc)
- WordPress localization – gettext and git
- How to get a localized version of WordPress from a repository?
- How to escape the single quote character in i18n translation strings?
- How do I translate: “2 hours and 15 minutes”?
- Gettext details
- How to escape single and plural i18n text strings?
- What are the most used WordPress localization?
- Difference between 2 internationalization (i18n) functions __() & _e()
- Localization works but still get “This plugin is not properly prepared for localization” msg in directory
- How to load theme textdomain from plugin?
- get_the_date() for translating date format
- Should i use _n for pronouns in translation?
- POEdit with Custom mu-plugins code
- How does WordPress choose which translation file to use?
- Proper way to create / manage gettext (.po, .pot) files?
- Should I include colon in my msgid in PO file?
- _e() function get text_string from function
- Translations not returning translated strings
- Single translation for many locales
- Force translated language on front
- Translating dynamic strings
- WordPress translation loading english file
- Easy export/import of data for Translation
- WordPress Theme .mo-file won’t load
- How to become a translator on wordpress.org?
- Translation from .mo file not working in theme
- Localization, escape html elements mid-sentence
- Can I set WordPress to display languages based on system language without a plugin?
- /languages/ folder missing in default themes
- How to translate functions.php?
- WordPress Translations
- Post types translation
- Translate arguments of a user added custom code [closed]
- Internationalize plugin so strings can be translated in WPML [closed]
- How to ‘manually’ load translations/test domain outside theme context?
- Interface translation without plugins
- Plugin localization persistance (woocommerce)
- WordPress Localization error within return value
- Custom theme .mo translation file not working
- Plugin translation not displaying
- WordPress translation
- Tweak the loop for translation
- Translating form labels shortcode output
- Website Language/Locale Switching
- .po file is loaded but changes are not appearing
- How to create .pot files with POedit?
- Translate a plugin using .po .mo files
- How to make a WordPress plugin translation ready?
- Theme localization of “slugs” (custom post types, taxonomies)
- Override default WordPress core translation
- Different Language for Frontend vs Backend
- Custom strings for translation using Polylang plugin
- How to print translation supported text with HTML URL
- Localization: I want the backend: english and frontend in defined language
- How-to: Translate plural forms for themes/plugins with PoEdit
- generating po mo translating files from scratch in a wordpress theme
- How to integrate get_post_time with date_i18n function?
- gettext does not translate when called in ajax
- How to debug failed load_theme_textdomain()?
- How to provide translations for a WordPress TinyMCE plugin?
- How do translated, escaped strings (esc_attr) in Themes work?
- Changing the language of a single page
- what’s different between _x() and _()
- How to handle text with function __(?
- Obtain a list of available translations
- Disabling Translation Update
- custom theme: english .mo file not working
- Unknown language json files
- How to save a translation of a plugin in “CodeStyling Localization”?
- Best pratice to make taxonomy terms translatable without changing slugs?
- Set language per post
- List of Default Translated Phrases
- What is the purpose of an extra file for translation?
- How to add extra language packs to WordPress
- load_plugin_textdomain in `plugins_loaded` or `init`?
- How to extract translatable (double underscores and _e) strings?
- How to Translate Contact Form 7 using qTranslate? [closed]
- Localizing strings that come from outside of plugin?
- How to set locale in ajax requests?
- Translate Navigation Menu & Sidebar Widget Titles
- Problems with localization
- Translate content, not instance, per-post
- Best location for theme translation files
- `wp_set_script_translations` with `wp.i18n` does not return translated strings in simple plugin
- Localization / textdomain is slow and chaotic
- Why should I escape translatable strings? and how shall i do that?
- Can’t translate the post meta data (Date) in another language
- Change language of comments template
- How to handle single quote in a translatable string in WordPress
- Make theme translatable for WPML
- Can’t we use strings defined as PHP constants if we want to translate them in a plugin?
- WordPress: After Gutenberg plugin migration to block.json the localization/ translations with PolyGlot in JavaScript does not work anymore
- Translation of plugin in MU-PLUGINS directory not working
- Singular name Plugin localization
- How can I make “Leave a comment” translation ready?
- Plugin Localization
- Custom translation of Month names
- I can’t translate text in my plugin using a .mo file, load_plugin_textdomain() function is always false