[Plugin: Codestyling Localization] Separately translating plugins that have the same textdomain

  • Resolved Matt Cohen

    (@mattyza)


    14 years, 8 months ago

    Hi guys,

    Firstly, thanks for the great plugin. We’ve found it to be incredibly useful and time-saving when updating translation files across themes.

    We’ve recently stepped into using the plugin for translating strings in our plugins and have run into a small speed bump.

    Using the latest versions of WordPress and the plugin, when two plugins share the same textdomain, only the first plugin is listed with the language options to the right of the list, with the other plugins being grouped under that plugin, due to the shared textdomain. I’ve tested this by adjusting the textdomain in one of the additional plugins, which resolved the issue.

    Is it possible, without changing the textdomain per-plugin, to “ungroup” the plugins and translate them separately using CodeStyling Localization?

    Thanks guys. We’d really appreciate your assistance in this regard. 🙂

    Thanks and regards,
    Matty.

    http://ww.wp.xz.cn/extend/plugins/codestyling-localization/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author codestyling

    (@codestyling)

    14 years, 7 months ago

    it’s not intended to support “ungrouped” handling, because 2 plugins should not have the same textdomain.
    Reason: depending on their load order and lets say both have the same term but with different translations, you will get only one of this translations and never see the 2nd.

    Thread Starter Matt Cohen

    (@mattyza)

    14 years, 7 months ago

    Hi codestyling,

    Thanks for clarify this.

    Thanks and regards,
    Matty.

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

The topic ‘[Plugin: Codestyling Localization] Separately translating plugins that have the same textdomain’ is closed to new replies.