WP-Members now available in the WordPress translation project

  • Plugin Author Chad Butler

    (@cbutlerjr)


    8 years, 6 months ago

    I am excited to announce that WP-Members is now included in the WordPress translation project at translate.wordpress.org.

    If you would like to contribute to better (or for some languages, new) WP-Members language packs, just go to translate.wordpress.org, select your locale, click on “Plugins”, then search for WP-Members.

    Keep in mind, there may be some growing pains during this process but I expect it will be a lot better than the past.

    With the latest update (3.0.5), the plugin is configured to prefer the translation project language packs over those shipped with the plugin, so if you have a translation project language pack in /wp-content/languages/plugins/ it will load that. If that does not exist, it will load from the language packs shipped with the plugin.

    Both of these processes have filter hooks so you have the option of loading a language pack from another location.

    As the language packs from translate.wordpress.org become more complete, I will eventually stop shipping language packs with the plugin and will rely on the others as the official translations.

    https://wordpress.org/plugins/wp-members/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Manuel Fritsch

    (@let-me-see)

    8 years, 3 months ago

    Dear Chad,

    today I took some hours to update, complete, de-formalize, check and double-check the current main German (informal) locale. I now would like to become the Translation Editor for this locale to finish the job.

    A free pass for premium content would be appreciated, since I could not identify some strings (which are probably related to premium content) and so I am not really sure if my translations hit the mark. 😉

    Looking forward to hear from you, and thanks for maintaining the one Members plugin to rule them all!

    Best
    Manuel

    Plugin Author Chad Butler

    (@cbutlerjr)

    8 years, 3 months ago

    Translation is a sub-project of the WordPress translation project (https://translate.wordpress.org) and is managed by the polyglots team, so unfortunately I don’t have the control over who is a translation editor. If you’re not already on the team for this locale, then you can get in touch with them here: https://make.wordpress.org/polyglots/teams/?locale=de_DE

    Manuel Fritsch

    (@let-me-see)

    8 years, 2 months ago

    Hi Chad,

    I assumed you might want to retain overview of who will or won’t be approved as Project Translation Editor for your plugin, and the process were that you to ask for me to be added to the team here.

    However, I contacted one of the General Translation Editors of my locale if he can help out. If, in the meantime, you would post a quick request as explained above, this would be great and will probably work even faster.

    EDIT: I got a quick response, and indeed the process should go via you as plugin author. But they made an exception in my case 😉

    Best
    Manuel

    Manuel Fritsch

    (@let-me-see)

    8 years, 2 months ago

    Finished! German main locale is at 100%, quadruple-checked and cross-checked with the glossary. What happens now? I still am not sure about some strings, are you @cbutlerjr in Slack? If so, please check your messages.

    Plugin Author Chad Butler

    (@cbutlerjr)

    8 years, 2 months ago

    What happens now?

    Nothing magical, unfortunately 😉

    Since it’s at 100%, it is available to be loaded from wordpress.org. So when German is selected as the language, WP checks language packs and, if available, they are downloaded.

    In preparation for this, I made the logic in the plugin to prefer the .org language pack over anything packaged with the plugin. That way, we could phase out the language packs with the plugin as new full translations became available on .org. So it will check the WP language folder first and if a language pack for the plugin is there, it will use that, otherwise it would then use the plugin’s included language pack.

    (That’s a little bit of a complicated explanation – hope it made sense.)

    Manuel Fritsch

    (@let-me-see)

    8 years, 2 months ago

    Alright, thanks for the explanation! Since I assume you are then not cbutlerjr on Slack, this is what I wrote to him regarding translations:

    1. I have a question regarding one string – does this one really make sense in English? Because I had a hard time translating it: “Additional information for field upload fields” – I think you might have misspelled “…upload files”
    2. Also, the original strings for reCAPTCHA seem outdated.
    3. Also, I suggest you replace the question marks in some or all of the original strings with the correct html code: & # 6 3; (take out spaces) – since they are not shown on the front-end (at least in my case; I refer to “Forgot Password?” and “Forgot Username?”).
    Plugin Author Chad Butler

    (@cbutlerjr)

    8 years, 2 months ago

    I have a question regarding one string – does this one really make sense in English? Because I had a hard time translating it: “Additional information for field upload fields” – I think you might have misspelled “…upload files”

    Ahhh… that is a mistake. It should be “Additional information for file upload fields”. However, the file upload input type is not yet fully supported, but will begin to be in 3.1. This is timely since that string is in an area of the plugin that is currently being updated.

    Yes, the reCAPTCHA strings are outdated. In fact, they aren’t even used for reCAPTCHA version 2. They are for version 1, which is deprecated. However, it remains in the plugin for now as there are likely people still using it (even though they should not be).

    I’ll give #3 some consideration.

    Manuel Fritsch

    (@let-me-see)

    8 years, 2 months ago

    I was just told on Slack that “WP-Members has a wrong stable tag in the readme file/missing SVN tag, that’s why stable gets ignored.” – regarding the issue, why dev locale is preferred to stable locale in German. I understand this is something in the original strings, not in the translations, or am I wrong?

    Plugin Author Chad Butler

    (@cbutlerjr)

    8 years, 2 months ago

    There are two ways to handle plugins in the SVN – either /trunk/ or /tag/

    When /tag/ is used, the /trunk/ is the development version and the tagged version is the main available download.

    When the /trunk/ method is used, the /trunk/ is the main available download (although in the polyglots project, this will be labeled “Development”.) This is the way that WP-Members is maintained, since GIT is actually what is used during development instead of SVN.

    I’ve considered changing the process to the /tag/ method, and probably will at some point. But I’ve run into problems in the past with the wordpress.org SVN system when doing it that way.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘WP-Members now available in the WordPress translation project’ is closed to new replies.