Support » Plugin: GlotPress » GlotPress string parsing on translate.wordpress.org

  • Resolved nlpro

    (@nlpro)


    I have 2 very simple questions.

    1. Are plugin translatable strings WITHOUT a text domain specified also added to a plugin translation on translate.wordpress.org ?
    (eg: __( ‘Settings’ ) )

    Side note1: I have stumbled onto a very popular plugin in the wordpress.org repository that includes 50 of such translatable strings…

    2. Is this being done intentionally by GlotPress on translate.wordpress.org? And if so, why ?

    Side note2: I’m fully aware of the following extract from the WordPress Plugin Developer Handbook:

    If there are strings in your plugin that are also used in WordPress core (e.g. ‘Settings’), you should still add your own text domain to them, otherwise they’ll become untranslated if the core string changes (which happens).

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter nlpro

    (@nlpro)

    This topic was originally posted on the Everything else WordPress forum.

    Looks like a moderator moved it to this forum which I think is incorrect. So feel free to move this back to the Everything else WordPress forum 😉

    Plugin Contributor Pedro Mendonça

    (@pedromendonca)

    Hi @nlpro,

    1. The strings in translate.wp.org GlotPress are imported from the parsed code of each plugin. GlotPress won’t check wether there is a textdomain or not. If there is a Gettext function, the string is added/updated on the translation table.

    About the side note 1, yes there are many plugins/themes where it happens, intentionally or not, wich leads to the next anwser.

    2. I guess it’s not up to GlotPress to check if a specific string has the correct textdomain. The same happens when you import originals from a .pot file, textdomain isn’t even used. Some authors may forget adding textdomain, but surely some intentionally omit it so the plugin uses the translation from core, which is wrong, as it is explained in the quote from the developer handbook. Also this generates confusion, because translators do have to translate it so the plugin gets to the minimum threshold to generate language packs, and those translations with no textdomain will never be used.

    Thread Starter nlpro

    (@nlpro)

    Hi @pedromendonca,

    Appreciate your response 😉

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.