Hi @alexclassroom
thank you for your thread.
The text domain is eos-dp instead of freesoul-deactivate-plugins to reduce the size of the files. The slug freesoul-deactivate-plugins repeated many times in the files means some kilobytes more. A few kilobytes more would not be a big problem for PHP files, but until all work right with all the available translation tools, I will keep the shorter text domain, even if the guidelines suggest something different. The translation files are loaded only on the backend, never on the frontend. I don’t totally exclude you may have issues on the frontend if you add your custom translations, but this can’t be the case for this plugin, because on the frontend you have no translations.
You should not have problems with any translation tool. At least nobody until now has reported issues with the translations due to the text-domain.
This is a plugin that has problems with the translations: https://translate.ww.wp.xz.cn/projects/wp-plugins/kolorweb-log-manager/ You will see the message “This plugin is not properly prepared for localization. …”. In the case of Freesoul Deactivate Plugins, you don’t see any warning: https://translate.ww.wp.xz.cn/projects/wp-plugins/freesoul-deactivate-plugins/
I know that the guidelines suggest that the text domain and the slug must be the same, and if you have noticed any malfunction with the translations, I will not hesitate to change the text-domain. But until all works without problems with all the available translation tools, I prefer to keep a shorter text-domain.
It’s important this plugin is as light as possible, but as said, if you have seen any malfunction let me know. In that case, it’s more important that the translations work without problems.
