The default language of WordPress is always English (en-US). Regardless of what your site language is set to. This is what the entire WordPress community expects for the language of source strings, and how many translation projects for WordPress will be set up too.
So yes, it is bad practice to choose use different source language from the system you’re writing for.
You could choose to ignore best practice, but with Polish you will run into a technical problem too. WordPress has a built-in limitation that you can only define two source forms of a pluralized string. This is actually a limitation of the gettext system, which is biased towards English. In their own words: “the coding standards for the GNU project require program being written in English”. You could say the same of WordPress.
Related Posts:
- Override default WordPress core translation
- How to debug failed load_theme_textdomain()?
- How to escape the single quote character in i18n translation strings?
- How do translated, escaped strings (esc_attr) in Themes work?
- Changing the language of a single page
- what’s different between _x() and _()
- Obtain a list of available translations
- How do I translate: “2 hours and 15 minutes”?
- How to escape single and plural i18n text strings?
- List of Default Translated Phrases
- What are the most used WordPress localization?
- How to add extra language packs to WordPress
- load_plugin_textdomain in `plugins_loaded` or `init`?
- Difference between 2 internationalization (i18n) functions __() & _e()
- How to extract translatable (double underscores and _e) strings?
- Translate Navigation Menu & Sidebar Widget Titles
- Translate content, not instance, per-post
- How to load theme textdomain from plugin?
- How to handle single quote in a translatable string in WordPress
- Make theme translatable for WPML
- How can I make “Leave a comment” translation ready?
- Multiple text-domains per single plugin – admin and frontend
- Where the WordPress Core Translation is “actually” taking place?
- How to translate theme name
- How to save a translation of a plugin in “CodeStyling Localization”?
- Using polylang, how can I see which post is the “original” and which are the “translated children”? [closed]
- Use WordPress default text domain for translating labels
- Where is the right .mo file inside the language repository?
- setlocale for date
- where to set the PO file for a plugin?
- Replacing strings within posts with the translatable string
- Should I include colon in my msgid in PO file?
- Replace text string on individual page
- Change template copy with po/mo files
- How to syntax Json output for translation?
- Translating a word with locotranslate, but wordpress does display another by default
- Can’t generate pot file using wp cli
- How do I translate month names in post metadata?
- How to avoid override string by child theme mo files when the string is empty?
- How to translate timestamp?
- How can i merge the translations from one .po file into the source on another .po file?
- Add a string to file .pot using Poedit
- Use the wp-admin translations on the front end
- Translatable Categories
- Force translated language on front
- Translate theme only
- what’s different between _x() and _()
- WordPress translation loading english file
- How can I see my theme’s text domain?
- WordPress Theme .mo-file won’t load
- Making a string translation ready with html in it
- Translation for plugin
- How to become a translator on wordpress.org?
- How to solve a translation function issue with no arguments and missing a text-domain?
- Plugin has no US english translation file
- Localization, escape html elements mid-sentence
- English version of my site show french strings [closed]
- Translation with wordpress what does the process involve?
- How to translate custom Divi module using POEDIT and Polylang [closed]
- How to translate functions.php?
- How do you translate comments_number function text in a theme?
- How to add a translatable string to post date
- Proper way to use esc_html__ and esc_attr__ etc for escaping value for translation
- How to use esc_attr__ with custom translation function?
- Programmatically choose language for translation
- Post types translation
- Translate arguments of a user added custom code [closed]
- How to define theme translation file?
- String translation for esc_html__() when registering string [closed]
- Automatic translation with different domains per languages?
- Translations not working on Safari
- __() function inside html tags
- How to do translations in WordPress?
- printf, translation function and date_i18n adds extra characters
- Qtranslate-X get raw post title value
- How to deal with differently translated prepositions?
- Interface translation without plugins
- Debug WordPress gettext function
- qtranslate loading the wrong language
- issue in translating a wordpress them
- Understanding WordPress Default Theme – twentyfifteen.1.4 >> Languages Folder
- WordPress Localization error within return value
- Custom theme .mo translation file not working
- Plugin translation not displaying
- Adding a translation phrase to WordPress Theme
- Language & translation
- GlotPress – WordPress integration
- White Space on translated strings lost
- Translating form labels shortcode output
- How to translate placeholder?
- Archive widget numbers translation?
- Poedit ASCII errors ( WordPress )
- Does WPML translate numbers automatically, or do I have to do the string translation? [closed]
- Translations in source code
- WPML & Events Manager translatable fields after duplication
- Theme translation file translating some strings and not translating others
- multisite same language different translation
- How to find posts that are missing translation? (wpml)
- Translate via URL parameter working only in localhost
- .po file is loaded but changes are not appearing