Viewing 5 replies - 1 through 5 (of 5 total)
  • Tim W

    (@timwhitlock)

    The problem is the use of unload_textdomain called here without the reloadable flag. This actually locks the domain for use with installed (GlotPress) translations.

    Separately it requests translations too early, which may cause different issues for different people.

    Being “compatible with Loco Translate” actually just means following WordPress i18n conventions. Introducing my plugin as if it has special requirements just muddies the waters.

    Thread Starter kampot888

    (@kampot888)

    Thank you for your reply.

    From now on, should I request modification of POT files using WP’s i18n rules?

    I’m sorry I’m a beginner,

    but even if the translation of WC Vendors Marketplace is successful,

    it won’t be reflected on the management screen,

    so how should I modify the LOCO settings? Please tell me how to set it up

    Tim W

    (@timwhitlock)

    I don’t understand your question, but this plugin ships a POT file which the developer no doubt keeps up to date with each release of the plugin. This will work fine with Loco Translate, as with any PO file editor you might use. If you have a specific question about my editor, please post in the Loco Translate forum.

    Thread Starter kampot888

    (@kampot888)

    the Loco Translate forum

    I will post the rest on the Loco Translate forum Thank you

    Thread Starter kampot888

    (@kampot888)

    How do you feel after that?

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