Is it possible to define the language of a plugin as something other than en-US?

  • Blucube

    (@edhicks)


    2 years ago

    Hi,

    On launching a plugin that’s set up for i18n the default is that the language you’ve written it for is en-US. So translators can come along and translate that into (say) French.

    What if the plugin is actually already in French? Is there a header/readme directive that can be set to point this out, so that translators can pick that up and translate it into English, as opposed to the wp.org translation system assuming that this existing French text is English? I’ve scoured the docs and come up blank.

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator t-p

    (@t-p)

    Review Plugin Handbook:
    https://developer.www.ads-software.com/plugins/internationalization/localization/

    Also https://www.ads-software.com/support/topic/how-to-change-language-of-the-plugin/

    • This reply was modified 2 years ago by t-p.
    Thread Starter Blucube

    (@edhicks)

    Thanks. I’ve read that and it doesn’t answer the question. There’s nothing about setting the main/root/base/initial language. Unless the default language of a plugin must be English? That seems like an odd restriction if so.

    Moderator bcworkz

    (@bcworkz)

    If you will provide your own translation files I’m pretty sure the gettext system will translate in either direction. You could set up a minimal test to confirm.

    If you will rely on translate.www.ads-software.com for translations, using a different base language doesn’t seem to me like a good fit for the system. Translating to English wouldn’t be the hang up so much as translating your non-English base (say French) to other languages like Italian. We have English to Italian translators. French to Italian probably less so.

    If you want to utilize translate.www.ads-software.com, I suggest asking for guidance through the Slack #polyglots channel where the actual translators can best answer your question. If you haven’t yet joined Slack, free registration is required.

    Thread Starter Blucube

    (@edhicks)

    Thanks. I think you’re right, I think the “base” language is always assumed to be en-US, I just wanted to ask people who know the system better than I do in case it was something you can change!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Is it possible to define the language of a plugin as something other than en-US?’ is closed to new replies.