Conversation
supportI fully localized this plugin to zh_TW. It displays localized UI strings incorrectly because this plugin’s text domain should be duplicate-content-addon-for-polylang . Click here to download modified files and compare them with the original files, and you will get the modifications.
Hi @alexclassroom , Thanks for localizing the plugin into zh_TW — we appreciate your effort! Just to clarify, the correct text domain for this plugin is dupcap , not duplicate-content-addon-for-polylang . That’s likely why the translated strings aren’t showing correctly. We’ll check the files you shared and make sure everything works with the correct text domain. Thanks again for your help! Thank You.
I am sure this plugin’s text domain should be duplicate-content-addon-for-polylang . Please refer to this official document . If your plugin is hosted on wordpress.org it must be the slug portion of your plugin URL ( wordpress.org/plugins/ <slug> ). This reply was modified 1 year ago by Alex Lion (阿力獅) .
Hi @alexclassroom , Thank you for pointing that out and referencing the official guideline. You’re correct — for plugins hosted on WordPress.org, the text domain should match the plugin slug (in our case, duplicate-content-addon-for-polylang ). We’ll review this and plan to align the text domain with the WordPress standard in a future update to ensure better compatibility with translation tools. We appreciate your help and attention to detail! Thank You.
These issues still exist in 1.2.4.
Hi @alexclassroom , Thanks again for your continued feedback. We’ve just released a minor update to ensure compatibility with the latest WordPress version. This was an urgent release focused on addressing potential issues related to the recent WordPress core update and ensuring security — so we haven’t yet made changes to the text domain. However, we absolutely acknowledge the importance of aligning the text domain ( duplicate-content-addon-for-polylang ) as per WordPress.org standards. This will be included in one of the upcoming updates to improve translation compatibility. We appreciate your patience and support! Thank you.
Hi @alexclassroom , Thank you once again for your valuable feedback and continued support. We’re happy to confirm that the text domain issue ( duplicate-content-addon-for-polylang ) has been fully resolved in the latest plugin version 1.2.5 . This update is now live on WordPress.org and ensures full compliance with WordPress.org translation standards. If you have any further suggestions or run into any issues, feel free to reach out — we’re always here to help! Thank you.
Please refer to my modified codes again, I also merged some split content to complete sentences. Complete sentences help translators produce good translations, as not all languages have grammar similar to English. Confirm no text domain issues in 1.2.5.
Hi @alexclassroom , Thanks again for your helpful feedback. We’ve rechecked your modified files and agree — merging split strings into full sentences improves translation quality. We also confirm there are no text domain issues in version 1.2.5. Your suggestions will be considered for the next update. We’ll plan to include your suggested string improvements in our next update to further enhance the translation experience for all users. Thanks again for your contributions — your support makes a big difference! Thank you.
Hi @alexclassroom , Thanks for localizing the plugin into zh_TW — we appreciate your effort! Just to clarify, the correct text domain for this plugin is dupcap , not duplicate-content-addon-for-polylang . That’s likely why the translated strings aren’t showing correctly. We’ll check the files you shared and make sure everything works with the correct text domain. Thanks again for your help! Thank You.
I am sure this plugin’s text domain should be duplicate-content-addon-for-polylang . Please refer to this official document . If your plugin is hosted on wordpress.org it must be the slug portion of your plugin URL ( wordpress.org/plugins/ <slug> ). This reply was modified 1 year ago by Alex Lion (阿力獅) .
Hi @alexclassroom , Thank you for pointing that out and referencing the official guideline. You’re correct — for plugins hosted on WordPress.org, the text domain should match the plugin slug (in our case, duplicate-content-addon-for-polylang ). We’ll review this and plan to align the text domain with the WordPress standard in a future update to ensure better compatibility with translation tools. We appreciate your help and attention to detail! Thank You.
These issues still exist in 1.2.4.
Hi @alexclassroom , Thanks again for your continued feedback. We’ve just released a minor update to ensure compatibility with the latest WordPress version. This was an urgent release focused on addressing potential issues related to the recent WordPress core update and ensuring security — so we haven’t yet made changes to the text domain. However, we absolutely acknowledge the importance of aligning the text domain ( duplicate-content-addon-for-polylang ) as per WordPress.org standards. This will be included in one of the upcoming updates to improve translation compatibility. We appreciate your patience and support! Thank you.
Hi @alexclassroom , Thank you once again for your valuable feedback and continued support. We’re happy to confirm that the text domain issue ( duplicate-content-addon-for-polylang ) has been fully resolved in the latest plugin version 1.2.5 . This update is now live on WordPress.org and ensures full compliance with WordPress.org translation standards. If you have any further suggestions or run into any issues, feel free to reach out — we’re always here to help! Thank you.
Please refer to my modified codes again, I also merged some split content to complete sentences. Complete sentences help translators produce good translations, as not all languages have grammar similar to English. Confirm no text domain issues in 1.2.5.
Hi @alexclassroom , Thanks again for your helpful feedback. We’ve rechecked your modified files and agree — merging split strings into full sentences improves translation quality. We also confirm there are no text domain issues in version 1.2.5. Your suggestions will be considered for the next update. We’ll plan to include your suggested string improvements in our next update to further enhance the translation experience for all users. Thanks again for your contributions — your support makes a big difference! Thank you.