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.


            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.”

    • Daniele Scasciafratte 5:47 pm on May 31, 2016 Permalink | | Flag unresolved

        Mte90it_IT PTE
        Tags: PTE,   

        PTE Bot – Do you want review a plugin for me? 

        Hi everybody,
        the awesome Italian community created another tool for the Polyglots after GlotDict!
        After an Italian meeting about the PTE roles and review I proposed a bot.

        A bot?
        Yeah, inspired from https://triagebot.mozilla.org/ The Triage Bot of Mozilla that is a simple form where a volunteer can subscribe to receive weekly an email with different tickets to triage (check if the bug it is happening etc.).
        In the Italian community we have the problem of many strings to review, actually 40000+ check on https://translate.wordpress.org/stats, but we are few PTEs.

        So I proposed a daily task for PTEs pick a random plugin and review like 20-30 strings, so if we work together we can approve many strings together.

        To add a little bit of gamification I created a WordPress plugin this afternoon (4 hours) so it is very experimental and actually enabled only for the Italian community.

        Why only italian??

        Because that bot it is on my server so I don’t want to send many email daily to avoid problem with my hosting but I think that the bot will works without problems we can move outside on a specific site.

        Who works?

        Every day check the email frequency for every PTE subscribed and pick a random plugin what have strings not approved.
        Actually do a scraping from the HTML because GlotPress don’t have a REST API so this pick 1 plugin from a list of 20 plugins.

        I can install on my site?

        The plugin is in alpha and require few step not already described in the readme (like for the taxonomy).

        I want discover more!

        Plugin: https://github.com/Mte90/PTE-Bot
        Website: http://ptebot.mte90.net/


      • ThemeGrill 5:54 am on May 31, 2016 Permalink | | Unresolved

          Tags: ,   

          Hello Polyglots!

          I am the theme author for the following themes and would like to request respective GTE’s to add the following WordPress.org users to translation editors for their respective locales.

          Spacious: https://wordpress.org/themes/spacious/

          ColorMag: https://wordpress.org/themes/colormag/

          Thanks in advance!

        • jmviade 12:34 pm on May 29, 2016 Permalink | | Resolved
          • Alin Marcu marked this resolved
            6:17 pm on May 31, 2016
          • Alin Marcu marked this unresolved
            6:17 pm on May 31, 2016
          • Alin Marcu marked this normal
            6:17 pm on May 31, 2016
          • Alin Marcu marked this resolved
            6:17 pm on May 31, 2016

          jmviadeca PTEes_ES PTE
          Tags: ,   

          Hello Polyglots!

          I am the plugin author for Spanish Quote of the Day and I would like to be editor for the next languages.

          Thank you.
          Regards, Joan Miquel

        • mbrsolution 1:38 am on May 29, 2016 Permalink | | Resolved
          • Luis Rull marked this resolved
            10:38 am on May 30, 2016

          mbrsolutiones_ES PTE

          Hello Polyglots!

          I am the plugin helper in the forum for PayPal Donations – https://wordpress.org/plugins/paypal-donations/. I would like to be added as the Spanish Translator Editor. Please add me for the respective locale:


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

        • lesarck 7:41 pm on May 27, 2016 Permalink | | Unresolved
          • Dominik Schilling (ocean90) marked this unresolved
            9:46 pm on May 30, 2016

          Tags: ,   

          Locale: es_BO
          Country code: BO
          Plural forms: nplurals=2; plural=(n != 1);
          Language native name: Español de Bolivia
          Sub-domain: es-bo.wordpress.org
          Site Title: Español de Bolivia
          Site Description: WordPress en español de Bolivia
          Admin Username(s): lesarck
          Admin Email: lesarck at gmail.com

        • Frenchtastic 10:56 pm on May 26, 2016 Permalink | | Unresolved
          • Alin Marcu marked this unresolved
            5:15 am on May 27, 2016

          Tags: ,   


          I’m the author of the following themes and would like to be added as an editor for French (#fr_FR):

          Thank you!

        • bhaldie 2:01 pm on May 26, 2016 Permalink | | Flag unresolved

            Tags: ,   

            Hello Polyglots!

            I am the plugin author for Memphis Documents Library https://wordpress.org/memphis-documents-library. We have a number of great translation editors that we’d like to be able to approve translation for our plugin. Please add the following WordPress.org users as translation editors for their respective locales:

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

          • Jory Hogeveen 1:07 pm on May 26, 2016 Permalink | | Resolved
            • Dominik Schilling (ocean90) marked this resolved
              2:10 pm on May 30, 2016
            • Dominik Schilling (ocean90) marked this unresolved
              2:10 pm on May 30, 2016
            • baet marked this normal
              3:22 pm on May 27, 2016
            • Chantal Coolsma marked this resolved
              1:13 pm on May 26, 2016
            • Chantal Coolsma marked this unresolved
              1:13 pm on May 26, 2016

            kerawebnl_NL PTE
            Tags: ,   

            Hi, I’d like to be added as editor for the following plugins since I’m the author:


            Thanks in advance!

          • Niels Lange 10:03 pm on May 25, 2016 Permalink | | Resolved
            • Dominik Schilling (ocean90) marked this resolved
              12:46 pm on May 27, 2016

            nielslangede_DE PTE
            Tags: ,   

            Hello polyglots,

            I’m the plugin author of SMNTCS Google Webmaster Tools (https://wordpress.org/plugins/smntcs-google-webmaster-tools/). As a German, German is my mother tongue. Roughly five weeks ago I suggested some translations in German. Unfortunately these suggestions haven’t been checked yet. What do I need to do in order to become PTE to approve translations of my own plugin? Beside German I also speak fluent Dutch and English, thus I would love to provide a Dutch translation for my plugin as well. Looking forward to receive your reaction on this request.

            Best Niels

          • Bego Mario Garde 11:36 am on May 25, 2016 Permalink | | Flag unresolved

              pixolinde_DE GTE

              Notes from the Polyglots chat on May, 25th 

              Locale stats after the 4.5.2 maintenance release

              Releases​: 162 locales. 61 locales up to date. 2 locales behind by minor versions. 14 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. 62 locales at 100%. 3 locales have more than 95%. 5 locales have more than 90%. 22 locales have more than 50%. 60 locales have less than 50%. 10 locales don’t have a WP project.

              Thai and Welsh are behind one major version, @kazama and @gwgan were kindly asked to look into releasing.

              Petya (@petya) is in active conversations with the current Persian GTE team regarding the waiting new GTE requests. Hopefully an active discussion will happen this week in the comments below the requests.

              Taco (@tacoverdo) will ping the GTEs of locales that are at 95%+ in a post on make/polyglots

              Technical Updates

              No technical updates this week.

              WordPress Translation Day Videos

              The twenty videos taken from the sessions on WPTD shall be published at WordPress.tv. Those who did a session are kindly asked to log in, download their video and upload it to WordPress.tv The description should explain the video was part of the event. It would be OK to edit the videos to remove the introduction. More editing shouldn’t be necessary. @casiepa volunteers to upload the remaining videos on Monday next week.

              • Please comment below if you will take care of your own video
              • If you’d like to help out and need access to Crowdcast, please ping @petya on Slack
              • Might be good for @oleg to get on board (Oleg, please let us know if you also want access to the raw videos)

              Handbook FAQ page draft Google Doc by @casiepa

              Handbook draft has been published as Google Doc at https://docs.google.com/document/d/1g4If4Tb8rjAob5F66031ve4MXK64cYE5tuuNuSpWlsc
              Everybody is welcome to contribute.
              Before being published, new entries for the FAQ will be proof read by other team members (pinged in the polyglot channel)
              Pascal (@casiepa) now has access to add content to the handbook alongside Naoko (@nao), @coachbirgit, @pixolin, @petya, @ocean90, @chantalc, @deconf and @tacoverdo. Any of them can proofread and publish drafts if needed.

              WordCamp Europe contributor day: @tacoverdo set up a hackpad doc

              @tacoverdo worked on a hackpad but will publish it as a blog post here.

              Things to decide are:

              1. Who’s leading new contributors–needs to be a current experienced GTE with the help of current translation contributors
              2. Who’s leading the extra activities & discussions – needs to be someone closely involved with activities, who’s attended the weekly chats, ideally someone from the Leadership team or most active contributors.

              While the meta team is available for contact, we should try and push for the Rosetta P2s again and remind the meta team of our current priorities regarding GlotPress and features of translate.wordpress.org, such as “Reject with feedback”, “Notifications for GTEs and PTEs” and Global Glossary.

              Current contributor day stats for polyglots:

              • We have 57 people signed up for Polyglots so far
              • Of them 9 are completely new (so will need to attend the onboarding workshop)
              • 26 have translated but are not very experienced
              • 22 are either very experienced or team leads

              WordPress.org forums upgrade timeline

              The polyglots team is happy to hear about the planned update of the support forums to bbPress 2.x
              Naoko (@nao) will add a blog post for discussions shortly.

              Open discussion

              Naoko (@nao) would like to discuss PTE status for multiple locales. She’ll write a blog post here, soon.

              • Olegs Belousovs 12:54 pm on May 25, 2016 Permalink | Log in to Reply

                Hey, thanks for reaching out on WPTV. I think it’s better not to edit those videos, because the quality is already not HD and we can lose more if edited and transcoded.

                You can upload them from this page: http://wordpress.tv/submit-video/ Be sure to insert the right title and some description… and we can take care of the missing meta data, but if you have time, please fill in all the data you have 😉

                Please, feel free to ask in the #wptv channel on Slack if you need some more help, me or the team can respond to you with all the necessary information. Bye 😉

              • Samuel Sidler 3:38 pm on May 25, 2016 Permalink | Log in to Reply

                On the forums upgrade: Please comment on the post if your locale is interested in being first to upgrade. Make sure your moderator team agrees. 🙂

                • Bego Mario Garde 4:31 pm on May 25, 2016 Permalink | Log in to Reply

                  Hello Samuel, the German community has been waiting for the upgrade desperately for a very long time. I have just pinged our moderators to get some feedback, but would imagine, everyone here will be excited to see the upgrade as soon as possible (or sooner). Is there anything in particular we can do, to support the upgrade? Best regards, Bego (@pixolin)

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

                    Qualifications include moderator consensus and having fewer than 10k combined topics and posts.

                    Unfortunately this is not the case for the German forums. 🙁

                • Sergey Biryukov 9:53 pm on May 27, 2016 Permalink | Log in to Reply

                  As stated at the May 19 Support Meeting, Russian locale is interested in being one of the first to upgrade due to numerous issues with the existing forums.

              • Es piaT 7:37 pm on May 25, 2016 Permalink | Log in to Reply

                Hi. I would appreciate it if we could get this update.
                Yours sincerely, a german forum-moderator.

              • Kazama 3:33 am on May 27, 2016 Permalink | Log in to Reply

                just release 4.5.2 for ‘th’ 😛

            • raselahmed7 8:52 am on May 25, 2016 Permalink | | Unresolved
              • Dominik Schilling (ocean90) marked this unresolved
                9:48 pm on May 30, 2016

              Tags: ,   

              Hi Polyglots,
              I’m the author of the plugin: https://wordpress.org/plugins/resultpress/
              Can you please allow Bangla (#bn_BD) language edits for me?
              Thank you.
              Best regards

            • Naoko Takano 8:08 am on May 25, 2016 Permalink | | Flag unresolved

                Naoja editor

                Agenda for the Polyglots chat on May, 25th 

                Dear Polyglots,

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

                • Locale stats after the 4.5.2 maintenance release
                  • Taking care of 100% translated locales that haven’t released
                  • Pinging GTEs of locales that are at 95%+ for manual release
                • Technical update (GlotPress releases and changes, WordPress releases)
                • WPTranslationDay videos – let’s get them to WP.tv
                • Handbook FAQ page draft Google Doc by @casiepa
                • WordPress.org forums upgrade timeline
                • WordCamp Europe contributor day: @tacoverdo set up a hackpad doc
                • Open discussion

                See you there!

              • goranpro 7:15 am on May 25, 2016 Permalink | | Resolved
                • Marko Z. marked this resolved
                  6:10 am on May 27, 2016
                • Alin Marcu marked this unresolved
                  5:16 am on May 27, 2016

                Tags: ,   

                i submitted/corrected a translation for bbpress for Slovenian language.
                It is critical because there is a bug and a warrning appears if i use the current translation.

                I sumitted this on 18.5.2016. How long should it take that the corrections are accepted?
                You can see it here:

              • cubsus 12:09 pm on May 24, 2016 Permalink | | Unresolved

                  Tags: ,   

                  Hi Polyglots,
                  I’m the author of the plugin: https://wordpress.org/plugins/free-forms-and-crm/
                  Can you please allow following editors for it:

                  Thank you.
                  Best regards

                  • Bego Mario Garde 8:48 am on May 25, 2016 Permalink | Log in to Reply

                    Hello cubsus,

                    while we appreciate every effort to translate WordPress and all themes and plugins, we only grant permissions as Project Translation Editor to contributors, who have worked on translations for a while using our Glossary and Translation Style Guide. We do this to achieve the best possible quality for all translations and generally provide a good user experience.

                    @worldsoftwbs is cordially invited to contribute with translations and we will be please to grant permissions as described on our web page How the German community grants PTE permssions. In between we kindly ask @worldsoftwbs to ping us on the German Slack when a translation is ready so we can approve the text strings or edit where needed.

                    Thank you for your understanding and
                    Viele Grüße, Bego (@pixolin)

                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