WordPress.org

Translate WordPress

Welcome to the official blog of the translators team for the WordPress open source project.

This is where we discuss all things related to translating WordPress. Follow our progress for general updates, status reports, and debates.

We’d love for you to help out.

Translate WordPress

You can help translating WordPress to your language at any time. Just log in to the translation platform with your WordPress.org account, and suggest translations. If you want to help in managing and validating translations, please make sure to get in touch with the existing language team first.

Don’t see your language?

Request support for it by following this guide. We’ll have you up and running in no time.

Weekly Meetings

We have a weekly meeting on Slack in #polyglots, Wednesday 10:00 UTC. If you have any questions, bring them to the weekly chat!

Posting here

In order to post to this site, you will need to log in with your wordpress.org account. Your first post may take a while to show up, as it is moderated. Please follow our tag policy when posting.

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Naoko Takano 3:16 pm on May 27, 2016 Permalink | | Flag unresolved

      Naoja editor  

      Cross-Locale PTE Trial 

      As I briefly mentioned in the last weekly chat, I want to discuss the way we handle importing translations of multiple locales. For the sake of simplicity , I’m only referring to plugins here but this applies to themes as well.

      The question is this:

      What is the best way for an organization/business with a team of in-house (or hired, third-party) translators to import their Plugin translations into translate.wordpress.org?

      There was an in-depth discussion on this on Slack, in which @matt suggested testing a small number of cross-locale PTE accounts.

      (More …)

       
      • Torsten Landsiedel 3:09 pm on May 29, 2016 Permalink | Log in to Reply

        I’m really interested to hear the opinion from @samuelsidler here. As a translator and GTE I am more than happy if professional translations for large plugins (Jetpack, Yoast, etc.) come in. But in the past we followed the path from #meta-i18n to just allow single people speaking the language fluently. In the end it is a matter of trust: Do we trust them to provide good translations although we aren’t involved in the process anymore (because it is handled externally). For companies like Automattic, Yoast, etc. this will be easy. But what to do with all the other? Do we trust them or not? This is the overall question.

        And if we trust them, what can go wrong? Translation propagation is critical here, I think.

        • Mattias Tengblad 10:47 pm on May 30, 2016 Permalink | Log in to Reply

          Translation propagation is critical here, I think.

          I agree. If translation propagation “breaks” because of this, it will probably discourage community translators.

      • Alvaro Gois dos Santos 11:34 am on May 30, 2016 Permalink | Log in to Reply

        I’m not sure even companies with relevant (and premium) plugins can control the quality of professional translations. I have too many examples in Portuguese pt_PT that they do not – and I mean BIG. Therefore, as this can be a good way to accelerate translation import, there’s also a huge slip hazard.

      • Dominik Schilling (ocean90) 1:09 pm on May 30, 2016 Permalink | Log in to Reply

        I agree that this all about the right amount of criteria.
        The list mentioned by @Nao is a good start. Some other ideas are a random review process and imports by “Cross-Locale PTE” should be publicly logged (like in #polyglots-warnings).
        An open question might be whether a “Cross-Locale PTE” is allowed to override existing translations which were suggested/approved by another translator/GTE/PTE.

        Pinging @niallkennedy since he requested the same for Twitter. @niallkennedy: I’d like to know your thoughts on this as well.

      • Petya Raykovska 4:53 pm on May 30, 2016 Permalink | Log in to Reply

        Мost of us know why we handle PTE and plugins / theme translations the way we currently do, but let’s drop what we know from experience for a second and think about possible ways we can solve the problem with professional translations before we dismiss all of them due to a few mistakes in the past and potential mistakes in the future.

        As this is clearly pushed as the way forward, I’d like to focus on discussing ways to potentially execute it that will also ensure:

        • Keeping/Improving the quality and consistency of plugin and theme translations
        • Maintaining a healthy relationship with all plugin authors
        • Maintaining the growth and the motivation of the translation community we’ve witnessed in the past 24 months

        I think there are four main things to address:

        General translations quality and consistency

        In regards of the quality and consistency of translations, if a plugin author makes sure their professional translators follow a locale’s guidelines and glossary, that will eliminate the high risk of inconsistencies. We can make that a requirement and a failure to comply will result in eliminating their access to import translations.

        If a locale does not have a Glossary or a Style Guide, which is the case for a lot of plugins, there might be a case to be made around the professional translators being asked to create one based on current WordPress translations and the terms they’re using. That will also benefit locales that are running a bit behind on documentation and can be one way for the whole community to benefit from having professional translators involved.

        Problem: Potential inconsistency between plugin/theme translations and WordPress Core translations
        Solution: Require that professional translators follow the community created guidelines for a specific locale

        Eliminating the risk of mistakes

        The main issue here is that access to import strings currently means access to approve strings as well.

        I think in the case of professional translations and access to upload to all locales, we need to make a clear distinction between users with that access being able to import vs being able to approve translations.

        Importing professional translations for languages you don’t speak is one thing – you have the guarantee of your provider that what you’re getting is quality and the right thing. Bulk approving suggestions by the community without speaking the language should not be allowed for anyone. Currently PTEs and GTEs can both import and approve. We need a technical solution – a new user role maybe, that only allows importing strings.

        Problem: Approval of community suggested strings by people who do not speak the language
        Solution: Access to import vs access to approve strings – requires development

        Translating in context – plugin/theme translations QA

        When experienced translators or users translate an interface, they do it with a clear knowledge of the context the string is used in – that means they either text translations before shipping them (as we do with all language versions), or being users, they are very clear on where the string will be used and how to test it. As professional translators are often not users, a requirement would be for their translations to be tested in a real environment. There are several ways that can happen:

        Problem: Gramatically correct translations breaking the UI because they’re not used right in a particular context
        Possible solutions:

        • The plugin author can ask users for the locale for feedback after importing
        • The plugin author/whoever has the access, can ask the GTEs for a specific locale to test with no expectation of immediate response or reaction

        Overwriting existing translations

        If an import is made by a cross-locale PTE for an existing string translations, submitted/approved by the community, those should not be overwritten. The process goes the other way around: the translations need to be coordinated with the locale glossary and style guide and if there’s a conflict somewhere, it’s the cross-locale PTE’s job to clarify the issue between their professional translators and the General Translation Editors for a locale

        Problem: Contributions submitted in accordance to community guidelines getting overwritten by imports
        Solution: Imports from cross-project PTEs should not be able to overwrite existing translations

        Technical implementation of the cross-locale PTEs

        Problem: Currently, adding PTEs happens through the backend of each Rosetta site associated with a locale. To add cross-locale PTEs, we would need to go to 100+ separate websites. That is not going to scale as only three people active in the Polyglots team have access to all Rosetta sites (myself, Dominik and Sam).

        Solution: We need a separate UI for this, maybe tied to a user’s .org profile as opposed to their profile in a Rosetta site. Maybe @ocean90 can suggest the right approach here.

        The issues listed above are not the only ones that need to be addressed, but discussing them would be a good start.

        Something I’d like to hear from active GTEs about would be:

        • What do you think a good trial period should be?
        • How do you think we should check about consistency?
        • What would the process be if someone fails their trial – would they be granted a second chance?

        I like the criteria Nao suggested about qualifying for a trial. What can we add to that?

        Please get involved. This is an important discussion. Looking forward to hearing from active Polyglots members – @chantalc @tacoverdo @deconf @casiepa @pixolin @fxbenard @wolly @alvarogois @coachbirgit @luisrull as well as all the rest of the General Translation Editors.

        • Chantal Coolsma 5:03 pm on May 30, 2016 Permalink | Log in to Reply

          In my opinion we should start with some bigger developers. I remember we had a request by Twitter in the past. That would be a good start. Give some of those some room to do their thing and let GTEs monitor how it is going. For example: do translations match the current core translation for their locale, etc etc. After everything is going ok, we can let more and more cross locales PTEs do multiple languages.

        • Wolly aka Paolo Valenti 5:07 pm on May 30, 2016 Permalink | Log in to Reply

          I think that we can ask to follow lines guide and glossary, but anything more.

          i think that this trial is an external project, not part o the community.

          GTEs, IMVHO, cannot spend theire time to check professional tranlations.

          Professional translators are not part of the community, they don’t live in te locale communities, they are external.

          Giving theme full access to all locales, about their projects mean that we accept that translations will be not only community based.

          It’s good? It’s bad?
          I don’t know, but external translations will foolow a different path.

          Those are my 2 cents,

          • Mattias Tengblad 10:39 pm on May 30, 2016 Permalink | Log in to Reply

            GTEs, IMVHO, cannot spend theire time to check professional tranlations.

            +1

            I think it’s important to recognize that there are small Polyglot teams too, we can’t expect GTEs to take on this type of growing work load.

        • Wolly aka Paolo Valenti 5:28 pm on May 30, 2016 Permalink | Log in to Reply

          Two minutes ago I deleted a DM in Twitter.

          The modal window translation was really bad, wrong and confusing.

          In my opinion the professional italian translation of twitter is not made by italian mother tongue.

          Professional translations are not better translations, are, maybe, faster translations.

        • Alvaro Gois dos Santos 5:46 pm on May 30, 2016 Permalink | Log in to Reply

          I believe @petya‘ suggestions are the minimum reasonable conditions for having cross-locale PTEs.

          On the other hand, the problem of non-native translators is real, like @wolly remembers. From my experience, there’s not a lot of web focused professional translators, let alone WordPress focused.

          Is there a way to have GTE pre-approve translations before being imported? As an option or, at least, dependent on a previous contact between the plugin/theme author and GTEs?

          I sometimes suggest people to be PTE for a specific plugin, because I know that person is able to assess the context in which the plugin is used or is likely to already use it or a similar plugin, and, therefore, is more qualified than average to validate translations.

          This would somehow take the community in consideration and what is being achieved.

        • Alin Marcu 6:06 am on May 31, 2016 Permalink | Log in to Reply

          I do agree with all the above. In addition, eliminating the risk of mistakes will be quite a challenge. Bulk importing without speaking the language can also result in importing a translation, the wrong one, into a different locale.

          I’ve always wondered: If you’re hiring professionals to translate your plugin/theme, is it so hard to make a requirement for them to contribute as other community members do? I mean, each professional translator will have his own w.org account and will be PTE for one locale. By doing so, as a plugin/theme author you’re eliminating some of the risks mentioned above and you’re allowing the community to easily review, spot and correct possible translation errors or consistency issues.

      • Pascal Casier 7:10 am on May 31, 2016 Permalink | Log in to Reply

        @alvarogois: The “pre-approve” is exactly what should not be done, otherwise we all become even more bottle necks in the process.
        @petya: The UI for adding those PTE should not be a priority when going in a pilot phase. As the number of cross-locale users will be limited, it’s sufficient to find e.g. a correct update query in the central database to add that user or if not possible a mix of asking all GTE to add that specific user and then manually going over the remaining ones not done.
        I agree with @ocean90 that to get to the “trust but verify”, there should be a clear way of getting notified in one or the other slack channel when an import has happened, easily identifiable.

        So my first remarks:
        1. GTE should be allowed to overwrite the strings and get the priority over the imported strings. The locale GTE/PTE are supposed to know the local language and style guides, so they have the final word on the strings.
        2. Add (trusted) PTE next to the cross-locale accounts so they can help and correct where needed.
        3. We need to work on the import for the cross-locale. In a first phase we could grant them PTE rights as that’s the only thing we have, but a different way for ‘importing without overwriting’ should be found
        4. We need to continue our effort into style guides and glossaries as those are our bibles for doing the work we do and where we refer to in case of doubts
        5. A notification system for those accounts needs to be setup so GTE get notified when an import happened
        6. An ‘import-but-not-overwrite’ option should be given to these cross-locale PTE (this might be used later for all contributors)

        My main worry in all of this is that currently an import will overwrite whatever a GTE has adapted before, so an endless fight could start in having the correct string translation. So having an import that cannot overwrite validated strings seems to me the priority to avoid loss of quality/reputation.

        So it’s clear that development will be needed next to adapting our way of working. But like @petya indicated and probably all of you agree, we might find more agile and innovative ways of working, but we should not lower the high quality standards we have reached so far.

        • Alvaro Gois dos Santos 8:27 am on May 31, 2016 Permalink | Log in to Reply

          Yes, @casiepa, I agree that a “pre-approve” is just not possible and GTEs shouldn’t be a barrier. However, a way of notifying GTEs prior to an import would be important, if not essential. You have to have a way to include this translations in the community workflow, or it’ll be like a whole separate thing. I mean, @deconf is right: “Bulk importing without speaking the language can also result in importing a translation, the wrong one, into a different locale.”

        • Bego Mario Garde 7:19 am on June 1, 2016 Permalink | Log in to Reply

          GTE should be allowed to overwrite the strings and get the priority over the imported strings.

          While I certainly agree that we want to keep sort of control over translations to ensure an overall good user experience, I would imagine that developers who hired a professional translator would feel upset if the work they paid for was edited by a Translation editor (who in worst case even might not see the source of the translation and consider their effort as a benefit for the overall user experience). As a result, the quality of work of translation editors could be questioned and compared with the work of professional translators, who by definition should deliver a better work.

      • Wolly aka Paolo Valenti 10:17 am on June 1, 2016 Permalink | Log in to Reply

        With regards to the cross-locale PTE issue, the Italian Community in yesterday’s meeting has agreed to the following

        • we do not oppose the initiative of cross-locale PTEs
        • we are neutral with regards to the trial, willing to help if it should be a go, but ok even to just go without it
        • we feel Devs should be free to decide whether or not to translate directly or to pass through the Community. Both have advantages and disadvantages
        • we think that the Community, though, should cater to those who decide not to proceed with their own translation and therefore should not be asked/required to work (voluntarily) on projects that are being translated by paid professionals. For this reason we encourage the development of a specific team that could supervise this work. This solution would free up resources in the Community and at the same time allow for Devs the opportunity/freedom to make whatever choice they deem in their best interest
        • we think that the translations should be “signed” in some way as being “proudly provided by the Community” or provided by Dev/whomever. This will induce a clearer view as to the quality of the work (and also gratify the work of the Polyglots”
        • obviously style guides, glossary and indications will be freely shared and Devs encouraged in asking their translators to follow them
        • the “pro-*TE” team could also randomly test and verify translations periodically to assure quality standards are kept high
        • this way, we feel, we could allow both the freedom for the Developers and the standards of the platform, giving value to the work of the Community and of all parts in the process
      • Naoko Takano 8:46 am on June 2, 2016 Permalink | Log in to Reply

        Thanks everyone for participating in the conversation, both in this thread and the meeting yesterday. This is not a simple change, but I’m happy to see many polyglots are diving in deep to figure things out together.

        To use as a base for the discussion on the criteria, I added this section on the “Roles and Capabilities” page.

        Cross-Locale Project Translation Editor (Title/Details Pending)
        This section is still being discussed (more info).

        A Cross-Locale Project Translation Editor is an account owned by a plugin or theme author (or the authoring organization), which has can validate strings on a specific project for more than one locale. This role has the same capabilities as a Project Translation Editor over multiple locales instead of one. Cross-Locale Project Translation Editors need to meet a set of criteria before being appointed by General Translation Editors.

        And this on the “Translating Themes & Plugins” page.

        Criteria for a Cross-Locale Project Translation Editor (Pending information)
        This section is still being discussed (more info).

        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 accont 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

        None of these are set in stone, just some examples of how we would document it if the trial goes well. Let’s talk about what need to be changed, clarified, or added in the next meeting.

        • Petya Raykovska 11:28 am on June 9, 2016 Permalink | Log in to Reply

          Hey @nao, just seeing this now, sorry I didn’t react earlier.

          Let’s please not add anything to the handbook before we have a final agreement on what we’re doing.

          These things are still under discussion and can be misleading in our documentation right now.

          These updates also don’t make it clear that this is a trial role that does not apply to every plugin or theme author that wishes to have an account like that.

          If we’re going to add anything to the documentation pages, it should be information that these trial projects will start running soon. But as it is now, the role seems a valid one for each author to request.

          • Naoko Takano 12:53 pm on June 9, 2016 Permalink | Log in to Reply

            Ok, removed them from both pages – at the meeting “draft on the handbook” was requested but probably not meant to be *on* there — yet.

            The exact information is in my comment above.

      • Alvaro Gois dos Santos 7:53 pm on June 8, 2016 Permalink | Log in to Reply

        I am skeptical about the hypothesis of a Cross-Locale Project Translation Editor replace a translation already made by the community when importing a full translation. I suppose one of the criteria, in addition to a prior contact with locale GTEs, could be the percentage of strings already translated in the project. In a project with a low percentage of translated strings, import will not do major damage. But what about projects where there is already a translation by an established community?

        Chating on the #polyglots slack channel I remembered the example of WooCommerce: the Portuguese (pt_PT) community has a very active translation team working with WooCommerce, the devs could hardly find better translators – not because they’re professional translators but because they’re community members, WordPress professionals and know a lot about e-commerce. What would happen if the WooCommerce Cross-Locale Project Translation Editor just imported a new translation and overide the current one?

        I’m using this as an example, I’m sure they wouldn’t do that because there’s already local PTEs that would be contacted, I imagine.

        • Naoko Takano 1:26 pm on June 9, 2016 Permalink | Log in to Reply

          I commented on Slack too but will leave a reply here for everyone to see. Heres’ what I said

          If there is a situation like what you describe for any other plugin/locale combination, I think it’s ideal for a few of active translators to become reviewers (if they have time to do so), so that they can review the professional translations and correct anything out of context, etc.
          Otherwise, PTEs and GTEs can make corrections after imports are done. The downside of this latter method is that their correction may not go into the professional translator’s translation memory (TM) so they will not correct the mistake at the source. Also, the translators (non-*TEs too) can contact the cross-locale PTE to point out things like misuse of a term.

          Also, I agree the GTE/PTE translations should NOT be overridden by Cross Locale PTEs.

        • Naoko Takano 2:38 pm on June 9, 2016 Permalink | Log in to Reply

          Added a new issue to the GlotPress plugin: “Import: Avoid overwriting current translations

      • Claudio Sanches 4:24 pm on June 15, 2016 Permalink | Log in to Reply

        > Conduct a trial: allow the account associated with a Plugin author to become PTEs for multiple Locales, which can then import languages files translated and reviewed outside of translate.wordpress.org.

        I understand that many people are pushing for something like this to happen… But I see this as something necessary or good, the way we’re doing things are going very well.
        And most importantly, since the launch everyone knew that plugins/themes were not required to use the translate.wordpress.org. If people want professional translation, they still can using other translations system for they own plugins/themes and they can also hire professionals today to translate in translate.wordpress.org as any user who can go there and translate.
        I don’t see why this need to have “special permissions”, seems like give plugin/theme authors the capacity to able to edit/delete topics and reviews from the forum, I see a lot of people wanting it, but the authors also are not required to use the forum too 🙂

      • Charles E. Frees-Melvin 11:36 pm on June 16, 2016 Permalink | Log in to Reply

        I think perhaps opening up the import option to anyone is the solution here, and if the are not a PTE or GTE then it goes to moderation just like the one by one. If the translations are good make them a PTE. It would be nice if there was a button next to the name in GlotPress to make someone a PTE rather then going to rosetta and finding the user and project.

      • Pascal Casier 6:51 am on June 22, 2016 Permalink | Log in to Reply

        Hi all, I have started to draft some scenarios. Global comments can go here, specific comments can be added to the document: https://docs.google.com/document/d/112jTcnuIgpGqsGaTwJpW91pitKFlETTKdFFYJvF27iY/edit?usp=sharing
        Thanks, Pascal.

    • Pierre Lannoy 11:42 am on June 23, 2016 Permalink | | Unresolved

        PierreLannoyfr_FR PTEfr_CA PTEfr_BE PTE
        Tags:   

        Hello Polyglots!

        Sorry for the second request in a row, it seems that my plugin attracts many talented translators 🙂

        I’m the plugin author for Live Weather Station (https://wordpress.org/plugins/live-weather-station/). Could you please add the following user as translation editor:

        Thanks a lot.
        Pierre

         
        • Chantal Coolsma 11:52 am on June 23, 2016 Permalink | Log in to Reply

          Most of the Dutch translations are ok. However I see some string which wrong are translated. Maybe @hanstis first could join the Dutch Slack at wpnl.slack.com. We can help him in the #polyglots channel overthere to improve the translations.

          • Pierre Lannoy 11:57 am on June 23, 2016 Permalink | Log in to Reply

            Hi Chantal!
            And thanks for your prompt answer. I doesn’t know the existence of this slack team. What I told him to do to register?
            Thanks in advance.

      • Pierre Lannoy 8:35 am on June 23, 2016 Permalink | | Unresolved

          PierreLannoyfr_FR PTEfr_CA PTEfr_BE PTE
          Tags:   

          Hello Polyglots!

          I’m the plugin author for Live Weather Station (https://wordpress.org/plugins/live-weather-station/). Could you please add the following user as translation editor:

          Thanks a lot.
          Pierre

           
        • Krzysztof Trynkiewicz (Sukces Strony) 8:18 am on June 23, 2016 Permalink | | Flag unresolved

            eclarepl_PL editor  

            New string up for translation in WordPress 4.5.3 

            Due to a seeming mistake WP 4.5.3 introduced a new string up for translation:
            https://translate.wordpress.org/projects/wp/dev/admin/pl/default?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=2998716&filters%5Btranslation_id%5D=43663861
            (if using this URL, change “pl” to your language; otherwise find the string in the directory: 4.5.x / Administration)

            This new string is exactly the same as the one already existing in previous and current WP versions ( https://translate.wordpress.org/projects/wp/dev/admin/pl/default?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=27222&filters%5Btranslation_id%5D=1259303 ) – only the %1$s was mistakenly typed in by someone as %s, so a new string was generated. The %2$s was left unchanged,.

            You can translate this extra string. It should remove itself with the next WP version (assuming someone changes back %s to %1$s).

             
            • Pedro Mendonça 8:29 am on June 23, 2016 Permalink | Log in to Reply

              Filtering by ‘addressed’ in admin one can also find two strings that could easily become one with singular/plural:
              Version %s addressed one security issue.
              Version %s addressed some security issues.

          • Pär Thernström 8:46 pm on June 22, 2016 Permalink | | Unresolved

              eskapismsv_SE PTE
              Tags:   

              I am the plugin author for Simple History (https://wordpress.org/plugins/simple-history/).

              Please add the following WordPress.org user as translation editors for their respective locales:

               
            • Bego Mario Garde 11:05 am on June 22, 2016 Permalink | | Flag unresolved

                pixolinde_DE GTE
                Tags:   

                Notes from the Polyglots chat on June, 22nd 

                Locale stats

                Releases:162 locales. 21 locales up to date. 46 locales behind by minor versions. 10 locales behind by one major version. 15 locales behind more than one major version. 61 locales have a site but never released. 9 locales don't have a site.

                Translations:162 locales. 19 locales at 100%. 48 locales have more than 95%. 3 locales have more than 90%. 24 locales have more than 50%. 59 locales have less than 50%. 9 locales don't have a WP project.

                Technical updates

                No technical updates this time.

                Cross locale PTEs

                Pascal Casier (@casiepa) created scenarios and published them as a Google Document. We will discuss his proposals at Contributor Day of WordCamp Europe in Vienna on June, 26th 2016. A chat will be scheduled so everybody can take part.

                While it is good to understand people’s concerns, Naoko Takano (@nao) suggests to make a poll after separating different opinions.

                Open discussion

                No topics this time.

                 
              • dudo 10:55 am on June 22, 2016 Permalink | | Flag unresolved

                  Dudoit_IT PTE
                  Tags: , yasr   

                  Hello Polyglots!

                  I am the plugin author for [YASR](https://wordpress.org/plugins/yet-another-stars-rating/) Please add the following WordPress.org user as a translation editor for his locale:

                  Thanks!

                   
                • Birgit Olzem 7:18 am on June 22, 2016 Permalink | | Flag unresolved

                    CoachBirgitde_DE editor
                    Tags:   

                    Agenda for the Polyglots chat on June 22nd 

                    Dear Polyglots,

                    Here’s the agenda for the chat today, see you on Slack!

                    See you there!

                    P.S. Wishing everyone who is traveling to WordCamp Europe a safe trip.

                     
                  • Philip Arthur Moore 2:29 am on June 22, 2016 Permalink | | Flag unresolved

                      philiparthurmoorevi editor
                      Tags:   

                      Hi All,

                      I’m the author of Subtitles and a user has translated it into Slovak. How would we go about getting those approved for him? Thanks a ton.

                       
                    • thomasplevy 4:20 pm on June 21, 2016 Permalink | | Resolved
                      • Sergey Biryukov marked this resolved
                        5:56 pm on June 22, 2016
                      • Sergey Biryukov marked this unresolved
                        5:56 pm on June 22, 2016

                      thomasplevy
                      Tags:   

                      Hello Polyglots!

                      I am the plugin author for [LifterLMS](wordpress.org/plugins/lifterlms) Please add the following WordPress.org user as a translation editor for his locale:

                      Thanks!

                       
                    • Marco Milesi 6:49 pm on June 16, 2016 Permalink | | Unresolved

                        Milmorit_IT PTE
                        Tags:   

                        Howdy Polyglots!

                        I am the plugin author for https://wordpress.org/plugins/telegram-bot/
                        We have a number of great translation editors that we’d like to be able to approve translatio. Please add the following WordPress.org users as translation editors for their respective locales:

                        #fa – @seaniour
                        (persian fa_IR)

                         
                      • Nilambar Sharma 6:59 am on June 16, 2016 Permalink | | Unresolved

                          rabmalinne_NP editor • en_CA PTE
                          Tags:   

                          Howdy Polyglots!

                          I am the theme author for

                          We have a number of great translation editors that we’d like to be able to approve translation for our theme(s). Please add the following WordPress.org users as translation editors for their respective locales:

                          If you have any questions, just comment here. Thank you!

                           
                        • Themeisle 11:43 am on June 15, 2016 Permalink | | Unresolved

                            themeisle
                            Tags:   

                            Hello Polyglots,

                            I would like to ask you to assign @warnetsabily as a PTE for Zerif Lite for #id_ID locale
                            Theme: https://wordpress.org/themes/zerif-lite/

                            Also we’ve had one more request here (https://make.wordpress.org/polyglots/2016/05/20/hello-polyglots-i-am-marius-ghitulescu-from-themeisle/#comment-272815 ) which is still unresolved.
                            The GTEs for #fa_IR locale are not active, can someone make @alibaba66 our PTE for Zerif Lite?

                            @ekajogja @petya

                            Thank you!

                             
                          • Bego Mario Garde 11:34 am on June 15, 2016 Permalink | | Flag unresolved

                              pixolinde_DE GTE
                              Tags:   

                              Notes from the Polyglots chat on June, 15th 

                              Locale Stats

                              Releases: 162 locales. 67 locales up to date. 0 locales behind by minor versions. 10 locales behind by one major version. 15 locales behind more than one major version. 61 locales have a site but never released. 9 locales don’t have a site.

                              Translations: 162 locales. 66 locales at 100%. 1 locale has more than 95%. 3 locales have more than 90%. 23 locales have more than 50%. 60 locales have less than 50%. 9 locales don’t have a WP project.

                              Tech stats

                              No updates this time.

                              Cross locale PTEs

                              All polyglots are reminded to comment their thoughts on the blog post by Naoko Takano (@nao).

                              Status of the Handbook FAQ page

                              Pascal Casier (@casiepa) has added two more topics to the handbook, which had been published previously. Everybody is invited to contribute.

                              Francesca Marano (@francina) suggests linking the videos of the Global WordPress Translation Day to the handbook as the videos are a great source for users who want to start contributing to translations. It would be helpful to link the video “How to prepare your plugin for translation” in the handbook. Any video that gives clear instructions on doing something should have maximum visibility. (Francesca has more ideas about sharing knowledge via the handbook, which she would like to discuss during WordCamp Europe.)

                              WordCamp Europe contributor day

                              The tasks for the contributor day have been collected in a Hackpad (https://hackpad.com/WordCamp-Europe-2016-Polyglots-6uvZpM1aQ5G) .
                              Some tasks still need team leads. So far nobody has been assigned to take notes of the process and outcome of the Contributor Day.

                              Everyone who is not attending to the Contributor Day can add comments below on topics that should be included/discussed on WordCamp Europe and that we haven’t covered yet.

                              Open discussion

                              Mohammad-Mostafa Yousefzadeh (@mohammad-yousefzadeh) and Farhad Sakhaei (@parsmizban) have reported difficulties to get in touch with the General Translation Editors of the Persian locale. Petya Raykovska (@petya) already contacted Mani Monajjemi (@mani_monaj) but (being organizer of WordCamp Europe) hasn’t been available for this topic lately. The team mentors are aware of the situation and will take care.

                              Reminder: Don’t forget to post a sketch for your dream GlotPress UI and comment on the blog post at https://blog.glotpress.org/2016/06/08/exploring-design-for-glotpress/

                               
                            • Birgit Olzem 10:02 am on June 15, 2016 Permalink | | Flag unresolved

                                CoachBirgitde_DE editor
                                Tags:   

                                Agenda for the Polyglots chat on June 15th 

                                Dear Polyglots,

                                Here’s the agenda for the chat today, see you on Slack!

                                See you there!

                                 
                              • socialdude 2:49 pm on June 14, 2016 Permalink | | Flag unresolved

                                  socialdudede_DE PTEid_ID PTE
                                  Tags: ,   

                                  Hello Polyglots!

                                  I am the plugin author for the following plugin https://wordpress.org/plugins/ultimate-social-media-plus/. I’ve found great translation editors that I’d like to be able to approve translations for the plugin.

                                  Please add @magister65 for all the Spanish-speaking locales, i.e.:

                                  #es_ES
                                  #es_AR
                                  #es_CL
                                  #es_CO
                                  #es_GT
                                  #es_MX
                                  #es_PE
                                  #es_VE

                                  And @aproxa for tr_TR.

                                  If you have any questions, just comment here. Thank you!

                                   
                                c
                                compose new post
                                j
                                next post/next comment
                                k
                                previous post/previous comment
                                r
                                reply
                                e
                                edit
                                o
                                show/hide comments
                                t
                                go to top
                                l
                                go to login
                                h
                                show/hide help
                                shift + esc
                                cancel
                                Skip to toolbar