Alex Lion (阿力獅)

Whatever this plugin’s current changes are, its text domain should be advanced-custom-fields, or the language packs delivered by GlotPress can’t be affected.

https://developer.www.ads-software.com/plugins/internationalization/how-to-internationalize-your-plugin/#text-domains

If this plugin should have a new slug/text domain, the new developers should create a new SVN repository for it, and then maybe add a migration feature for ACF to SCF.

This issue is resolved in 1.0.4.

Sorry for late reply.

I compared the modified files I provide with 1.2.7 files, all I18N issues are not fixed.

If all I18N issues are fixed, there should be 88 UI strings totally, NOT 69.

If this plugin has its own GitHub repository, I can submit a PR for these I18N code changes.

For your convenience, I updated all modified files based on 3.4.3. Same download link.

There are so many UI strings which can not be localized, these modifications can improve them.

Again, if possible, please take a look at I18N issues.

Please take a look of these I18N issues.

The same issues and the same download link because these above I18N issues still existed.

I modified a new version based on 5.2.2.

If possible, please take a look at these I18N issues.

Same issues and same download link.

I modified a new version based on 5.2.1.

Modified 7.2.2 for improving I18N issues is ready, same download link.

One of this plugin’s I18N issues, please don’t ignore it: This “Requires at least” is below 4.6. so the developer needs to set a Text Domain in file_folder_manager.php, and it needs to be?wp-file-manager?to internationalize your plugin correctly! Please refer to?this article.

Yes, of course.

https://www.ads-software.com/support/topic/awesome-support-really-good/

I quickly check the 5.6.0, it seems all I18N issues are improved. Thanks a lot.

Mark this thread as “resolved”.

After version 6 is released, I will recheck it because I don’t see any new release.