Yes this is problematic as i18n tools that parse your theme to generate a *.pot file for translation can’t understand this as they do not run PHP code but just search your code as text.
Here is a blogpost detailing on why this may cause trouble:
Bottom line: Inside all translation functions, no PHP variables are allowed in the strings, for any reason, ever. Plain single-quoted strings only.
But nevertheless the fact that you think about DRY is great! Actually as I’ve already talked about the i18n tools they can help you with automatically adding a textdomain. There even is a Grunt plugin to automate this plus the option to replace/rename textdomains which would solve your actual issue. Just comment if you need more help on that.
Related Posts:
- What is the difference between the .po .mo and .pot localization files?
- How to make a text with hyperlink translatable in WordPress?
- What’s the point on gettext syntax?
- Translate a string to a language with masculin/feminine nouns
- Change locale manually at runtime?
- Text Domains Across Multiple Plugins & Themes
- Can we load “load_theme_textdomain” multiple times with different domains?
- Where are the official i18n WordPress versions stored (SVN)?
- localize inline css
- Locale filter in conjunction with new datepicker localization
- How to use is_rtl with my main style.css?
- Localizing text from XML files
- Localizing strings that come from outside of plugin?
- Alphabetical sorting – local language
- How to detect if text domain is already loaded?
- does a translation (i18n) have to start from an english PO?
- _n() Single and Plural for search results?
- __() with sprintf returns untranslated string
- How to add i18n to a plugin’s Twig template files?
- load_child_theme_textdomain doesn’t work in function.php
- How to prepare SimplePie_Item’s get_date() for l10n?
- The effect of x() family of functions
- How to translate multi-line strings?
- get_locale() behaving strange in same functions.php file
- Do I need the .po file for my plugin?
- WordPress theme with frontend in different language than backend?
- Change WordPress Language
- Strings including html for localisation
- What does the underscore translate function do in my code without a textdoman
- Is it possible to set a different frontend- and backend-language?
- Possibility to use WordPress built-in localization
- Can any users change locale language?
- Localized version offers upgrade to en-us version
- Local WordPress installs don’t verfiy against wp-cli checksum check and how to fix that issue.
- Loading custom language file for plugin
- sprintf bloginfo odditie
- Unable to find where to translate certain tooltip string
- WP core emails translated
- How to translate theme content using site language?
- How can i localized html or php source code from wordpress [closed]
- Setting frontend locale based on postmeta not loading translation
- Using esc_attr function
- Change WordPress language based on user setting
- Define locale WordPress uses with gettext functions?
- Site does not display translations
- Theme doesn’t want to load localization files
- User specified Timezone
- Plugin translation ready – mo file not loaded
- Problem with adding a new post type
- Do I have to use load_plugin_textdomain() or is there any default folder for languages?
- Get localized user roles
- Internationalization of strings with html tags and numbers in WordPress
- Change post date format to hebrew calendar
- failed to open stream: Permission denied warning while load_textdomain
- Requiring Once into plugin PHP File not working
- Where does the locale come from?
- When localizing a theme do I create the .mo and .po
- Localization Problem: Doesn’t Display Translated Words
- wordpress localization extending
- How to localize built-in strings in a future-proof manner?
- Is there some ways to autofix the mo or po files instantly?
- I want to dynamically create i18n ecosystem in WordPress
- Language string not detecting used within the function
- Why does my WordPress Upgrade version have a language suffix?
- How to disable gettext feature?
- WordPress in French Language [closed]
- How do I make this plugin translation-ready?
- how to use a default MO file
- Localization of menu items
- Warning: The actual loaded translation content contains mixed textdomains and is not pure translateable within one textdomain
- Is it wrong to use the English version of WordPress to server a site in a different language?
- Hack nav menu to add gettext() to menu items?
- WordPress NavXT plugin localization
- Why is setlocale() returning false on WPEngine?
- WordPress emails translate to French
- How to create some sort of word mapping?
- Is this really always bad? (variables in l10n functions)
- How to change text depending on the country
- How to dynamically change the locale?
- How to show the front end in a different language? I am using the twentytwentythree theme
- i18n: How do I load translations for a language specified in the request?
- en_US or en-US, which one should you use?
- What is meant by __(‘page’,’twentytwelve’)
- Localizing a string with html tag with word inside that tag
- Localized Date Format for Custom Field
- WordPress: After Gutenberg plugin migration to block.json the localization/ translations with PolyGlot in JavaScript does not work anymore
- Use a language specific thousand separator
- Making my plugin translation ready. Poedit not working
- Why is the generated POT file from WordPress.org not adding my plugin description to the POT file?
- Should I include colon in my msgid in PO file?
- Theme translation not applying
- Localize strings for translation
- How to localize something coming from theme customizer
- Localize script not working
- Post types translation
- How to find which .mo file is responsible for displaying a particular localized string?
- Menu names not getting translated
- How to generate a rtl.css file for themes?
- Tool bar in editor missing in WP
- Save translation file of third party plugin in a custom plugin?