Translate WordPress

Tagged: import Toggle Comment Threads | Keyboard Shortcuts

  • Taco Verdonschot 2:17 pm on June 30, 2016 Permalink | | Unresolved
    • Dominik Schilling (ocean90) marked this unresolved
      8:29 pm on July 1, 2016
    • Dominik Schilling (ocean90) marked this normal
      8:29 pm on July 1, 2016
    • Dominik Schilling (ocean90) marked this resolved
      8:29 pm on July 1, 2016

    TacoVerdonl_NL GTEnl_NL editor
    Tags: cross-locale pte, import,   

    Over the last few weeks, we've been talking about introducing/testing cross-language PTE's. Yoast would like to be amongst the first to get this.

    Most of you know that Yoast's had its own Yoast Translate for quite a long time. The majority of validators there is also GTE on translate.wordpress.org, so they're the skilled polyglots you know.

    With the upcoming changes in the way translations are handled, Yoast is willing to make a move towards translate.wordpress.org. However, we don't want any translator to do double/unnecessary work.

    That's why I hereby request cross-locale PTE access for the following plugins:

    In this post by Naoko we've formed a set of conditions a company would fulfill before they can enter the trials. Let me touch them one by one.

    1. Use the community style guides and glossaries, or create ones based on them and provide public links.
    2. Disclose the sources of translation (e.g. translation vendor) and reviewers (.org username)
    3. List steps for other .org community volunteers to get involved in the review process
    4. Create a new account for this role rather than using a personal one, and fill in the profile page with contact information
    5. Have a Slack account and ping GTEs (TBD – unless auto-notification is possible) after imports

    So, how are we doing on all of these?

    1. All translations are (or should be, as I can only check a few languages) based on the rules set for each locale on translate.wordpress.org. That why we asked .org GTE's to validate the translations done at Yoast Translate.
    2. They're all community translations, so there's no company behind any of them.
    3. Getting involved is easy, just sign up at https://translate.yoast.com/register/ and we'd be happy to have you as translator.
    4. We've created the Yoast profile for this. We're currently adding it as plugin author to all plugins.
    5. You can always reach me on Slack, I'm online whenever my laptop's open (which is oftentimes even after office hours)

    And I would like to add a very important fact. We're talking about a one time import. We don't need to do this more often. We'll just move from https://translate.yoast.com to translate.wordpress.org. This really makes it a one time import.

    Summary of my request: I ask you to make Yoast a Cross-locale PTE for the above plugins, so that we can do a one-time import of the translations of our free plugins.

    • Naoko Takano 2:00 pm on July 3, 2016 Permalink | Log in to Reply

      I don’t see any reason not to accept the request!

      I’m a little confused on one thing – you wrote “Getting involved is easy, just sign up at https://translate.yoast.com/register/” but moving forward, is this still going to be the case? I’m just curious, my list of criteria is for ongoing projects so this requirement isn’t necessary for one-time import anyway.

    • Taco Verdonschot 8:51 am on July 5, 2016 Permalink | Log in to Reply

      On Slack,@ocean90 stated that this should be a one-time import. He feels that getting CLPTE rights isn’t necessary/useful in our case.

      If we decide to do a one-time import, signing up at https://translate.yoast.com will not be necessary for the part of the plugin that’s translated on translate.wordpress.org.

      • Dominik Schilling 9:26 am on July 5, 2016 Permalink | Log in to Reply

        Hi @TacoVerdo,

        here is what I need from you:

        For each plugin I need one ZIP file. In this file should be one .po file for the current translations and one .po file for waiting translations, for each locale. The .po file should be named like {$plugin_slug}_{$wp_locale}_[current|waiting].po.
        If the translations were submitted by a user who has an account on w.org add them to a file translators.txt in the same ZIP file. Format: {$plugin_slug}_{$wp_locale}_[current|waiting].po: {$wp_org_username}`. (Note: Only one user per file works, otherwise we’d have to split them somehow. If no user was defined I’ll use @yoast.)

        • Taco Verdonschot 12:21 pm on July 7, 2016 Permalink | Log in to Reply

          @ocean90, if I understand your requirements correctly, this would mean that all translations for a locale/status would be attributed to a single person. E.g. all current translations for Dutch would be attributed to @tacoverdo.

          All translations on translate.yoast.com are done by the WordPress community. Importing their translations without making sure people get the credit they deserve (e.g. the badge on their wordpress.org profile) just isn’t acceptable in an Open Source community.

          We currently have 2269 people who translated one or more strings in the projects on Yoast Translate with current status ‘current’ or ‘waiting’. They all deserve credit for their work.

          A better solution would be if we provide the w.org username of the translator for each string in the .po file. Is there a format you can use to import the translations that supports this?

          • Dominik Schilling 12:32 pm on July 7, 2016 Permalink | Log in to Reply

            @tacoverdo That’s correct. If you have time to compare 2,269 people with their wp.org profile, sure, go for it.

            I’ll perform the import via wp-cli, the command will probably look like this:

            $ wp --url=translate.wordpress.org --user= glotpress translation-set import [--set=]

    • Dominik Schilling (ocean90) 2:36 pm on September 19, 2016 Permalink | Log in to Reply

      @tacoverdo Are there any updates on this?

      • Taco Verdonschot 7:22 pm on September 20, 2016 Permalink | Log in to Reply

        It still requires a bit of work on our side. We should be able to provide the necessary information fairly soon after my paternity leave.

  • Anvar Ulugov 8:29 pm on August 19, 2015 Permalink | | Resolved

      Ulugovuz_UZ GTEuz_UZ editor
      Tags: import, merge   

      Hello dear Administrators!
      We have finished translating the development version. I wanted to merge the developemnt verstion’s translation with the 4.2.x but something went wrong, and translations percentage got 104%. Please, check it. Thanks!

    • roznicki 2:29 pm on November 4, 2012 Permalink | | Flag unresolved

        Tags: , import,   

        I would like to import whole pot format file for bbPress plugin. Glotpress has this functionality but i can’t find import file link.

        • Ze Fontainhas 2:32 pm on November 4, 2012 Permalink | Log in to Reply

          Only language validators have permissions to bulk upload translations, did you get in touch with your language’s team?

          • roznicki 2:37 pm on November 4, 2012 Permalink | Log in to Reply

            Thank You for ultra fast answer. I will contact Polish language team. Unfortunately they are so slow at Polish translation (only 6%),
            Please add information about permissions to help page of GlotPress.

      • alhoseany 1:58 am on April 9, 2012 Permalink | | Flag unresolved

          Tags: , , , import,   

          i have a translation file for bbpress and would like to import in into the translation project on glotpress. it is for arabic language.

        • potbot 6:17 pm on December 1, 2010 Permalink | | Flag unresolved

            Tags: import, ,   

            Trying to import translations @ wpcom with no luck. Keep getting 503 and 504 errors 🙁

            Whoops! There was a small systems error. Please try refreshing the page and if the error is still there drop us a note and let us know.
          compose new post
          next post/next comment
          previous post/previous comment
          show/hide comments
          go to top
          go to login
          show/hide help
          shift + esc
          Skip to toolbar