Jili jackpot 777 login philippines registration,IGT slot games play free online.REGISTER NOW GET FREE 888 PESOS REWARDS!

ResolvedModerator Yui
(@fierevere)

永子

4 years, 4 months ago

Hi.

Your plugin is currently translated to 4 languages and has 4 language packs generated, but translation seem to not work because:

ERROR: Your plugin slug is webp-converter-for-media, but your Text Domain is set as webp-converter. As the “Requires at least” is at least 4.6, you could remove the Text Domain tag, but you still need to modify the text domain in all your source files. Make sure it is equal to your plugin slug. (see https://developer.www.ads-software.com/plugins/internationalization/how-to-internationalize-your-plugin/#text-domains)

You have to fix textdomain.

Additional minor remarks:
WARNING: Please reduce your readme.txt in /trunk as it is over 10k (see https://developer.www.ads-software.com/plugins/wordpress-org/how-your-readme-txt-works/#file-size)

WARNING: The plugin sources used by everyone are in /trunk, is this what is expected? (see https://developer.www.ads-software.com/plugins/wordpress-org/how-your-readme-txt-works/#how-the-readme-is-parsed)
Tag folders found: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0, 1.1.1, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7 (but none are used, only trunk)

WARNING: Setting a License header is mandatory for new plugins since April 2020. Consider adding one, preferably the same one as WordPress itself: “GPLv2 or later”. (see https://developer.www.ads-software.com/plugins/wordpress-org/detailed-plugin-guidelines/#1-plugins-must-be-compatible-with-the-gnu-general-public-license)

Note: “Requires at least” (5.0) is at least 4.6 so no load_plugin_textdomain is needed. No check in the source files have been performed, but if you have the function somewhere, you can remove it. (see https://developer.www.ads-software.com/plugins/internationalization/how-to-internationalize-your-plugin/#loading-text-domain)

The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)

Plugin Author Mateusz Gbiorczyk
(@mateuszgbiorczyk)

4 years, 4 months ago

Hi @fierevere,

Thank you for your message.

Yes you are right. I immediately released the update v1.3.1, which fixes a translation errors.

As for your other comments:
1. Unfortunately, I am not able to shorten readme.txt – I want all the necessary information in the FAQ.
2. I keep the current version in the trunk. Can you explain this point carefully?
3. I have the license given. Could you check it out?
4. I do not use this function.

Thanks again for paying attention and reporting.

Moderator Yui
(@fierevere)

永子

4 years, 4 months ago

1 FAQ is good. Changelogs are often unnecessary.
All the readme is translateable, despite changelog strings are automatically marked as low priority, some translators still translate them, IMHO this is not really necessary. Usually short readme’s are better translated, including descriptions and FAQ, than long scary looking readme’s with changelog.
But its your choice.

2 Its ok, if its intentional. Most plugins have Stable and Development, where Development branch allows translators to translate strings for upcoming version of the plugin.
…

I have used automated tool to detect problems. Most important is to fix textdomain. The rest remarks are up to you, here are links provided, they explain why and what should be done,
I see License is specified correctly, and load_textdomain() – its clearly said that tool does not performed the full check.

Thanks for fast response and fix.

Plugin Author Mateusz Gbiorczyk
(@mateuszgbiorczyk)

4 years, 4 months ago

Thanks again for reporting bugs.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Not properly prepared for localization’ is closed to new replies.

Tags