Properly support i18n, please

  • poi3

    (@poi3)


    9 years, 4 months ago

    Since WordPress is making a big effort advocating the importance of releasing plugins/themes that support internationalization, i think that the team on iThemes needs to make an effort to make it right on the iThemes Scurity.

    1) Why doesnt the POT filename have the same name as the text domain?
    2) Why does the plugin’s main file mentions the translation path as being /languages when what actually comes with the plugin is a folder called “lang”?
    3) If the translation path is /languages why does the function loat_text_domain tries to load translation from /langs?
    4) Why does the plugin comes with a spanish translation that is already with an error on the filename spelling?

    The only way i got the translation to load was for me to create my own function, which isnt ideal since its not translating everything like the the submenus of the plugin’s menu.

    For what i saw on the support foruns, im far from the only person facing this problems. Hope that our americans friends remember that there are other languages in the world 😉

    https://wordpress.org/plugins/better-wp-security/

Viewing 4 replies - 1 through 4 (of 4 total)
  • xnscripter

    (@xnscripter)

    9 years, 4 months ago

    We would appreciate a prompt reply.

    P.S. Some problems (language localization):

    better-wp-security/core/content/system.php line 196 – _e( ‘PHP Allow URL Include’ ); – not set text domain: it-l10n-better-wp-security
    better-wp-security/core/content/system.php line 238 – _e( ‘PHP Max Script Execution Time’ ); – not set text domain: it-l10n-better-wp-security
    better-wp-security/core/content/system.php line 239 – _e( ‘Seconds’ ); – not set text domain: it-l10n-better-wp-security

    better-wp-security/modules/free/core/class-itsec-core-admin.php line 184 – _e( ‘Get tips for securing your site + the latest WordPress security updates, news and releases from iThemes.’, ‘better-wp-security’ ); – incorrect text domain value
    better-wp-security/modules/free/core/class-itsec-core-admin.php line 191 – _e( ‘Email Address’, ‘better-wp-security’ ); – incorrect text domain value
    better-wp-security/modules/free/core/class-itsec-core-admin.php line 194 – _e( ‘Subscribe’, ‘better-wp-security’ ); – incorrect text domain value

    better-wp-security/core/class-itsec-core.php line 411- load_plugin_textdomain( ‘it-l10n-better-wp-security’, false, trailingslashit( $itsec_globals[‘plugin_dir’] ) . ‘lang’ ); :
    – the function “load_plugin_texdomain” is initialized after the translatable strings
    – trailingslashit( $itsec_globals[‘plugin_dir’] ) . ‘lang’ – returns “/home/httpd/vhosts/domain.name/httpdocs/wp-content/plugins/better-wp-security/lang” instead of “better-wp-security/lang/”

    From Russia with love.

    xnscripter

    (@xnscripter)

    9 years, 4 months ago

    *localization

    Kniebremser

    (@kniebremser)

    9 years, 4 months ago

    Hey Guys!

    I have informed the developers of iThemes Security weeks before it.
    It is interested there is no one for.

    regards

    xnscripter

    (@xnscripter)

    9 years, 4 months ago

    good news

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Properly support i18n, please’ is closed to new replies.