If you don’t provide any textdomain, WordPress translated strings are used. If you use, for example, __( 'Add New Tag' );, the translation from WordPress core will be used because 'Add New Tag' exists in WordPress.
Your problem is that your are defining labels that don’t exist in WordPress core, so they are not included in any WordPress translation files. I mean, strings like 'All Items' or 'Popular Items' don’t exist in WordPress and they are not translated anywhere.
I think my explanation is a little tricky, I hope you get what I mean.
Related Posts:
- How to debug failed load_theme_textdomain()?
- load_plugin_textdomain in `plugins_loaded` or `init`?
- Multiple text-domains per single plugin – admin and frontend
- How to get menu strings, categories and tags into po file for translation
- Use the wp-admin translations on the front end
- How can I see my theme’s text domain?
- WordPress Theme .mo-file won’t load
- How to solve a translation function issue with no arguments and missing a text-domain?
- Fix Problem With Textdomain Translation
- Different Language for Frontend vs Backend
- How to get a translated string from a language other than the current one?
- Is it ok to use a function to output the text domain name in a wordpress theme
- Custom strings for translation using Polylang plugin
- Is a text-domain necessary for a child theme
- How to get a localized version of WordPress from a repository?
- How-to: Translate plural forms for themes/plugins with PoEdit
- generating po mo translating files from scratch in a wordpress theme
- Disabling Translation Update
- custom theme: english .mo file not working
- Unknown language json files
- Set language per post
- Overwrite textdomain of plugins by default – Lost Translation
- How to Translate Contact Form 7 using qTranslate? [closed]
- Localization works but still get “This plugin is not properly prepared for localization” msg in directory
- Why should I escape translatable strings? and how shall i do that?
- get_the_date() for translating date format
- Translation of plugin in MU-PLUGINS directory not working
- Custom translation of Month names
- Should i use _n for pronouns in translation?
- I can’t translate text in my plugin using a .mo file, load_plugin_textdomain() function is always false
- How to add translation for a string
- How to translate a WordPress.org plugin?
- New plugin translation does not work
- Do i have make the content() also translation ready in theme?
- POEdit with Custom mu-plugins code
- Transfer from English page to Arabic page
- Make changes to translation?
- Gutenberg not all editor text translated
- How does WordPress choose which translation file to use?
- Compile errors during translation compile
- Is this a correct usage of esc_html_e?
- WPML Translated Term
- How to translate functions like get_the_date()?
- translating wordpress with poedit
- WPML custom string translation get outside of container
- Implementing conditional gettext translation
- How to add LTR to a custom theme which in RTL by default
- _e() function get text_string from function
- Updating WordPress Theme/Plugin POT file without losing line numbers consistency
- Translations not returning translated strings
- Translation for frontend
- How to override default WordPress core language file
- Translate pages and URLs without duplicating
- How can you locate the .po file used for translation of a page?
- Translating dynamic strings
- How do I troubleshoot translation issues?
- Easy export/import of data for Translation
- How to change a word in theme?
- Using _e() or __() to translate text with div
- Translation from .mo file not working in theme
- Is it best practice to use English as the base of a translation-ready theme?
- WordPress Translation Issue
- How to translate “$before” with get text in get_the_term_list?
- WordPress localization – gettext and git
- Translation is not being output in one instance
- Get Text Domain For Transalation
- Why translations?
- Can I set WordPress to display languages based on system language without a plugin?
- /languages/ folder missing in default themes
- POEDIT – Continue with translations
- WordPress Translations
- Trying to localize a Underscores starter theme [duplicate]
- mo / po translation files does not seem to work
- WPML icl_register_string() throws fatal error but works [closed]
- Problem with Language translation
- localization of theme and plugins to English (originally in another language)
- WordPress translator plugin: Google Webmaster’s Tools shows hundreds of 404 not found errors. How to clean the mess?
- POT file generated using WP-CLI does not retrieve strings from translation functions with FQN (Qualifier)
- Rename existing cpt and taxonomy with new textdomain
- Using wp-cli to create a .pot file that interprets .twig files as well
- Translate string inside twig template
- How to call wordpress API to translate a post request
- Changing text for “Continue reading…” translation
- Can’t translate child theme
- How to get dashboard langauge not the website language?
- Translate wordpress without duplicate custom post
- Translation ready code format for taxonomy
- How to ‘manually’ load translations/test domain outside theme context?
- How to Convert Date to Thai
- How to use translation functions inside WordPress page
- Custom post type translation
- Plugin localization persistance (woocommerce)
- WordPress translation
- White Space on translated strings lost
- String translation with or without po file
- Translating “comments”, “leave a comment”, “prev”, “next”, “share”
- Website Language/Locale Switching
- Can’t load text domain in a mu-plugin
- multisite same language different translation
- Translate via URL parameter working only in localhost