Translate WordPress

Tagged: glotpress Toggle Comment Threads | Keyboard Shortcuts

  • Daniele Scasciafratte 4:26 pm on April 26, 2016 Permalink | | Flag unresolved

      Mte90it_IT PTE
      Tags: , , glotpress   

      GlotDict 1.0.6 – After the GWTD 

      At GWTD I have done a super easy fast session about how a browser extension can change your translation workflow on glotpress, in this case on translate.wordpress.org.
      Link for the live session about this extension for the new users: https://www.crowdcast.io/e/wptranslationday/18
      So what is the new features of this awesome super cool extension?

      • Fix for terms detection near () symbols
      • Fix alignment of toolbar for PTE
      • Enhancement: New UI on first use
      • Enhancement: No default language on first use
      • Feature: Shortcut on Ctrl+Enter to click “Suggest new translation” or “Add translation”
      • Feature: Shortcut on Page Down to open the previous string to translate
      • Feature: Shortcut on Page Up to open the next string to translate
      • Enhancement: New glossaries: he_IL, ro_RO, th, en_AU, en_CA
      • New icon by Crowdedtent

      Actually the languages supported are 18!
      How to add a new locale? see the video!

      The interesting part of this version are the hotkeys to speed up the translations!
      With ctrl+enter (ctrl not command for the OSX users) the string that your are translating is saved (you don’t need to click with mouse, is automatically done by GlotDict) and with Page Up and Page Down you can switch between the strings (on the switch they are not saved).

      For issues: https://github.com/Mte90/GlotDict
      Changelog: https://github.com/Mte90/GlotDict/blob/master/CHANGELOG.md

    • Daniele Scasciafratte 10:38 pm on April 5, 2016 Permalink | | Flag unresolved

        Mte90it_IT PTE
        Tags: , extension, glotpress   

        GlotDict – Custom glossaries for GlotPress in the browser 

        First of all thanks everyone for all the job that you done for translate the WordPress world.

        I’m Daniele Scasciafratte a Mozilla volunteer and also a WordPress Italian contributor so when in the Italian community @Xtraboy ask about someone that can develop a browser extension for the community itself I jump that opportunity to help.

        This browser extension fix an annoying problem for the non-english translators that use a custom glossary for their languages and need that information on https://translate.wordpress.org/ on terms (the terms with a dotted bottom border).
        Actually GlotPress have only one glossary that contain English information and not for specific locales so this extension fix that problem.

        This extension support different glossaries (actually only the Italian is available) to add the same look and feel and experience of the native English terms.

        Download for your browser

        How use it


        After the installation you get on https://translate.wordpress.org/ the dropdown menu on the right “Pick the glossary” to choose the glossary (that information is required only the first time, it’s saved in the browser for the future).
        After the installation and this step you can use the glossary automatically!
        As you can see in the screenshot the username term get the dotted bottom border and a tooltip with the Italian terms information.

        Developer zone

        How works

        The code is very simple, the core part is loaded on every https://translate.wordpress.org/ page of the JSON that contain the glossary: the terms to highlight, comment, pos and translation.
        Here you can find the Italian JSON that actually is the only one available but I wait for your pull request to add new glossaries.

        Generate the glossary

        The Italian community maintain a glossary on Google Drive so for a developer like me was not a big problem to create a script that generate the JSON automatically for the extension.
        This python script use the Google APIs to parse that document and save a compatible JSON for the extension and can be an useful start point for the other communities.

        The next steps

        • New glossaries for many languages
        • Improve the UI/UX of the extension (if there are suggestions)
        • New icon (actually is the glotpress icon)
        • Better readme (I am a developer but the target of that extension is also for non-developers so need to be more simple)

        Thanks to the Italian community for their work not only on translation but also for support and promotion!

      • Guido 11:21 am on February 15, 2016 Permalink | | Resolved
        • Birgit Olzem marked this resolved
          12:09 pm on February 18, 2016
        • Birgit Olzem marked this unresolved
          12:09 pm on February 18, 2016

        Guido07111975nl_NL PTEen_CA PTE
        Tags: glotpress   


        The last couple of weeks I have translated several of my favorite plugins into my native language and run into an issue.

        I was not able to find an answer at glotpress site:
        Editing a string

        So I posted my question at WP forum a week ago:

        Unfortunately no response so far, can anybody here take a look?

        I don’t want to create incorrect translations…


      • Torsten Landsiedel 10:48 am on December 18, 2015 Permalink | | Flag unresolved

          zodiac1978de_DE GTEde_DE editor
          Tags: , glotpress, informal,   

          As the end of the year is near, I want to share something for future thinking:

          There are more languages coming with more than one language variant (mostly default and formal). At the moment de_DE and pt_PT have two variants. nl_NL is the latest language that has added a new (formal) variant.

          But at the moment GlotPress is not optimized to handle that well. We should look for optimizations to handle languages with more than one language-variant better.

          What would be helpful?

          • A side-by-side-view for example would be great. But do we have enough space/width?
          • Or should we add the variant(s) below the default translation? Could be very long/confusing if you have plurals, which have already more than one textarea …
          • Or a copy from (x) feature – where (x) is a select with all variants, suggested here #432
          • Adding a diff view, to just see the strings which differ between the variants …

          This is a problem for the future of translating WordPress and I want to start the discussion about possible solutions. This has not to be solved fast, but we should think about it. If GlotPress is handling this better, I think, more languages will use more variants.

          Do you have an idea? Want to make a design mockup? Every help is appreciated.

          Maybe we can help making GlotPress better for handling more language variants in 2016.
          This would be great!

          • Marko Heijnen 10:59 am on December 18, 2015 Permalink | Log in to Reply

            The idea I wanted to implement a few months ago was to show possible translations from a translation memory kind of system. And give these possibilities on top of the translation box. The first step was to focus on translation sets with the same locale.

          • Luis Rull 1:05 pm on December 18, 2015 Permalink | Log in to Reply

            Great issue to be addressed. es_ES team decided long ago to do only informal and all other versions of spanish have their on locales (we are Spanish for Spain), but I wonder if we can address your problem to unify languages like ours to join forces or it’s better to keep they way we are right now.

            • Bego Mario Garde 1:38 pm on December 18, 2015 Permalink | Log in to Reply

              Skipping formal translation for German would make WordPress entirely unusable for corporate usage. “Unify languages” is no option and given the complexity of our grammar can not be solved with a plugin either.

          • Alvaro Gois dos Santos 1:24 pm on December 18, 2015 Permalink | Log in to Reply

            Wow, exactly my point @zodiac1978, as I commented on your ticket a few moths back.

            I do feel we need to take a different approach to variants, since there are a lot of common strings. Consolidating terms is way more difficult with separated translation flows, like we have now.

            More than a translation memory (it has its merit, of course, but we’re already having enough problems with automated string translation across projects…), I believe there should be some kind of visual comparison approach (side-by-side could be an option) along with a “copy from variant X” process.

          • Ruben Martins 5:48 pm on December 18, 2015 Permalink | Log in to Reply

            I will leave here one more option to handle this.
            What about add one field checkbox that mark a string translation with a possible variant translation?

            That will leave the another ones duplicate automatically on new versions of WordPress from the “default” variant and that ones marked as a variant will need to be checked separately in the translation of that variant so the Editors can validate easly the default string in every variants and the strings marked need to be checked as a “new translation”.

            With this in mind the Editor dosen’t need to valide twice or more the same translation in all the variants.

        • Samuel Sidler 6:44 pm on July 14, 2015 Permalink | | Flag unresolved

            samuelsidleren_AU editor • en_AU editor • nl_NL editor
            Tags: glotpress, meta, ,   

            Translating Themes and Plugins 

            Howdy all you wonderful polyglots!

            We’re getting very, very close to turning on translations for themes and plugins. Within the next few days (or weeks), we’ll start importing active themes and, shortly there after, plugins to translate.wordpress.org.

            The first import might be a bit… painful. There aren’t a lot of sorting options built-in to GlotPress, so importing, say, 1500 themes will make it hard to see which theme is important. We’re working on that. After import, it will be important to use translate.wordpress.org and find “pain points” in the experience. Then… let us know! You can file a ticket on meta trac with an idea for improvement and we’ll work to improve things over time. Or, you can ping me personally (sam on Slack) or even just leave a comment here.

            For themes and plugins with their own, external translation sites, we’re recommending the author post here on make/polyglots with a list of their translation editors and request that they be added to translate.wordpress.org with project-level permission. That means that they’ll only be able to approve translations for the specific theme or plugin, which they can already approve translations for on an external site.

            That might sound a bit complicated, but I wrote up a handbook page with all of the details. Please read through and let us know if you have questions.

            One thing I’m recommending to everyone is to follow a hashtag for your locale. For example, the Swiss German translation editors would follow #de-ch in their WordPress.org profile notifications. Any time, across WordPress.org, someone enters #de-ch, they’ll receive an email notification about it. It’s a great way for anyone “in the know” to ping translation editors and entire teams.

            P.S. If you haven’t already, now is a great time to translate the theme and plugin directory interfaces.

            Related posts: Meta team, Theme team

          • Peter Holme Obrestad 11:52 am on December 17, 2014 Permalink | | Resolved

              Tags: glotpress   

              I have given out our language url (https://translate.wordpress.org/languages/nb) to potential translators. I recently discovered that the “Administration” partial of the WordPress translation isn’t visible there. This led to me not getting any help with that one this time… What’s up with that? 😉

            • Kenan Dervisevic 1:12 pm on November 23, 2014 Permalink | | Resolved

                kenan3008bs_BA GTE
                Tags: , glotpress,   

                I keep getting all sorts of warnings like “Warning: Lengths of source and translation differ too much.” or “Warning: Lengths of source and translation differ too much.” when I try to translate a string at translate.wp.org. This happens for every string. Could someone please take a look?

              • Petya Raykovska 12:56 pm on November 7, 2014 Permalink | | Flag unresolved

                  petyabg_BG GTEbg_BG editor
                  Tags: , , glotpress,   

                  Notes from the GlotPress discussion at #WCSF Community summit 

                  Notes from the discussion on improving GlotPress (Mon, Oct 29th), suggested by Marko for the Community Summit in San Francisco.


                  Birgit Olzem, Catia Kitahara, George Stephanis, Mayo Moriyama, Marko Heijnen, Paolo Belcastro, Petya Raykovska, Rafael Funchal, Sam Sidler, Stephane Daury, Xavier Borderie.

                  If you were there and I missed your name, please leave a comment.

                  (More …)

                  • Marko Heijnen 1:21 pm on November 7, 2014 Permalink | Log in to Reply

                    I do want to state two inconsistencies:

                    • I didn’t say anything during the discussion about fixing glossaries. I understand the issues but don’t want to give hope for that support soon.
                    • We already use memcache on translate.wordpress.org which is causing some issues like incorrect counts now. Which is still something that need to be researched. To fix the issues and find other use cases where we need to cache.
                    • Petya Raykovska 2:05 pm on November 7, 2014 Permalink | Log in to Reply

                      Thanks, Marko.

                      The notes don’t state anyone making any promises on any of the mentioned issues. Their main purpose is to inform people who were not there on what we talked about.

                      Making a single glossary available throughout all the projects of a single locale (if that’s what you mean by “Fixing Glossaries”) is a serious issue we need to talk more about.

                    • Catiakitahara 1:23 pm on November 9, 2014 Permalink | Log in to Reply

                      Hey Marko, I see that @yoavf did a patch that creates Glossary Hierarchy (https://glotpress.trac.wordpress.org/attachment/ticket/97/glossary_hierarchy.2.diff). I guess this is the one you told me about at SF, but it seems it isn’t accepted as WordPress subprojects for pt_BR locale hasn’t inherited the parent project glossary yet. Could you at least accept this patch, please? It would help a lot. Also, I remember we spotted a bug with a missing ‘edit’ link on the Glossary page. It is still missing, should I create a ticket for that?

                      • Marko Heijnen 7:55 pm on November 12, 2014 Permalink | Log in to Reply

                        That code still need to be checked and validated. Also some other changes need to happen. I will look at it when I got the time.

                        I fixed it but it’s still need to be deployed. No reason to make a ticket for that.

                • Petya Raykovska 9:37 am on October 6, 2014 Permalink | | Flag unresolved

                    petyabg_BG GTEbg_BG editor
                    Tags: glotpress, , ,   

                    Notes from the Polyglots meeting at WordCamp Europe 

                    Hey everyone,

                    Here are my (slightly) structured notes from the Polyglots and GlotPress meeting at WordCamp Europe Contributor day on September 29th.

                    If you were there, please feel free to add to the notes if you feel I missed something important.

                    Roadmap for GlotPress

                    • GlotPress is not even at 1.0 – Doesn’t have caching, doesn’t have translation memory. Who’s gonna work on it?
                    • Scaling
                    • Data Schema, different one – Nacin and Nikolay are going to work on that
                    • Next step: Include Themes and Plugins in GlotPress
                    • Be prepared for hundreds of new validators
                    • Find a way to fight spam and security issues

                    Promised: Marko will ship profiles for GlotPress before WCSF

                    Scaling the community

                    A lot of languages don’t have an active validator – we need to change that

                    Average number of strings:

                    • Themes – 200-300 strings
                    • Plugins – 150-200 strings
                    • Core – 4000 strings
                    • BuddyPress – 1400 strings

                    Next step for Polyglots and i18n: Plugins & Themes

                    There needs to be a way for readmes to be translated.

                    There’s a lot of potential to get WordPress to 90 different languages.

                    We need to find developers to help with translations who are not heavily involved with core.

                    How do we put all the plugins on GlotPress (translate.wordpress.org)?

                    30 000 plugins that need to be translated

                    Rosetta sites will have their own theme and plugin directories with all translated plugins and themes

                    need a search that will work across languages. Search for plugins and themes should target both the translated language and English.

                    We start with 25 plugins

                    We need a mechanism to block spammers better. For forums, for local sites.

                    Global Communities

                    • agreed that each global communit should have their own P2
                    • there will be functionality to approve comments as approve/delete/move to forum
                    • @siobhan to get in touch with Jetpack ppl about subscribing to tag
                    • global.wordpress.org
                    • should have lists of validators. Lists of validators should also be on local sites.

                    Promised: Remkus is doing the forum theme for BB Press for the local sites/forums 🙂

                    We need to make it easier for validators to work

                    Redesigning GlotPress, improving the tools

                    Security concerns with strings

                    Possible decision: Two tears of validators. Trusted validators for the core project and some of the other main projects.

                    Other validators for all of the plugins etc.

                    Polyglots team leads

                    The current goal is to split the role of Polyglots lead in two:

                    Technical role/team
                    Community role/team – pushing validators, pushing people, finding validators, pinging validators, giving validator rights, helping validators and translators get started. The goal is to have a team of community ppl from at least three different parts of the world.
                    Sam will document the specific tasks of the role of Community Lead for Polyglots and also the technical lead

                    Selection process

                    • Select people from the existing validators and community
                    • Select people who we know are responsible and will get the job done
                    • Give them a long term role and back them up with others
                    • Siobhan 9:53 am on October 6, 2014 Permalink | Log in to Reply

                      thanks @petya – I’ve added a few things.

                    • Marko Heijnen 11:42 am on October 6, 2014 Permalink | Log in to Reply

                      On GlotPress side:

                      • We do have caching (seems broken sometimes).
                      • Some basic translation memory has been committed and I do try to get more things done before WCSF like be able to replace it with elasticsearch.
                      • A final roadmap will be submitted today/tomorrow on http://blog.glotpress.org as a living page.
                      • Will also create a post about profiles and user dashboard in the next few days.

                      Polyglots side:
                      I would also like to see that the updated bbPress theme will be kind of ready before WCSF. This because I’m sure people who are really into bbPress can do for example the final work at contributors day. I’m more then happy to help and I assume other are too.

                    • Mark Thomas Gazel 12:13 pm on October 7, 2014 Permalink | Log in to Reply

                      Sounds really great. Look forward to (hopefully) seeing all of this happen.

                  • Justina 10:17 am on September 18, 2014 Permalink | | Flag unresolved

                      pokeraitislt_LT GTE
                      Tags: glotpress, ,   

                      As I understand, there are no (active) validators for Lithuanian at the moment. I would like to be one.

                    • Brian 9:55 am on June 24, 2014 Permalink | | Resolved

                        brianrourkebollga GTE
                        Tags: , glotpress, ,   

                        How do the translations of the GlotPress web interface itself (i.e., those at https://translate.wordpress.org/projects/glotpress/dev) get implemented?

                      • Daisuke Takahashi 9:03 am on June 5, 2014 Permalink | | Flag unresolved

                          extendwingsja GTEja editor
                          Tags: , glotpress   

                          I found that wrong “Untranslated” count is displayed for “Swiss German (Formal)” in GlotPress.


                          Anyone can recount this (like forum)?

                        • Stephen Edgar 10:59 am on April 23, 2014 Permalink | | Flag unresolved

                            netweben_AU GTEen_GB PTEen_CA PTE
                            Tags: glotpress,   

                            As there are currently three separate discussions regarding GlotPress enhancements I’ll post this here as it probably should have been posted already.


                            Arian Allenson M. Valdez (@secretmapper) — Working on GlotPress UI and profiles with Yoav Farhi (@yoavf) and Marko Heijnen (@markoheijnen) as mentors

                            Secretmapper will post updates to http://blog.glotpress.org/

                            Now is probably be a great time to get more involved and help shape the direction of GlotPress


                          • Gary Jones 10:22 am on April 23, 2014 Permalink | | Flag unresolved

                              GaryJen_GB GTE
                              Tags: glotpress,   

                              Something that would really help the English variants is to have a feature that can copy all of the original strings for untranslated as the translated string, and leaves them as Waiting status.

                              Being able to check and bulk accept these strings (fixing variations where necessary) would be considerably quicker than going through each string one by one to click on Copy original and accepting.

                              ~95%+ of strings are going to be identical anyway between US English and British, Canadian and Australian etc. English, so I think it’s sensible to go with the assumption that strings match, and change where necessary, than assume the US English is going to be wrong (as with all other non-English variant languages).

                              • Peter Westwood 10:31 am on April 23, 2014 Permalink | Log in to Reply

                                I sort of disagree 🙂

                                I think it would be better to extend GlotPress (and possibly WordPress) to better support the hierarchical relationship between different variants of a language.

                                There are similar issues when you try and use GlotPress to have translations of both formal and informal versions of another language other than English and it would I think be better if we could document the relationship between languages and then share the translations better.

                                The only reason we are doing this copying and accepting is a hack to make it easier to find new strings to confirm for translation or not.

                                I think Wikipedia has a solution they use to solve this that it would be worth investigating.

                                • Gary Jones 10:38 am on April 23, 2014 Permalink | Log in to Reply

                                  I’m new to this so I’m only saying what I perceive on a practical level. I’m open and more than happy to see something more generic and functional if it involves significantly fewer “click, , ” for those 95% unchanged strings.

                              • Stephen Edgar 10:49 am on April 23, 2014 Permalink | Log in to Reply

                                I think this is part of the idea behind the Glossary and being able to share that Glossary between projects per https://glotpress.trac.wordpress.org/ticket/97#comment:64

                                No doubt only between single locale projects for starters and then maybe something to allow the sharing between locales down the road.

                              • Marko Heijnen 11:11 am on April 23, 2014 Permalink | Log in to Reply

                                This should not be implemented because it’s an exception and not a rule. Also you can also only translate the strings that are needed and skip the rest.

                                • Gary Jones 1:20 pm on April 23, 2014 Permalink | Log in to Reply

                                  From a technical standpoint, you’re probably right, but it’s much easier to see that a language is now 99% complete (because some new strings have been added late in the cycle) when it was previously 100% complete, than having to look through 95% of strings again in case new ones happen to contain a spelling that needs to be changed. Being able to mark off those that don’t need changing (i.e. by just copying the original) is pragmatically more convenient for accuracy purposes.

                                  If I didn’t make it clear, my intent would be to only have this feature enabled for English variants, but then as Peter said, variants in other languages may be based on a certain base translation with only a few changes needed.

                                  • Ze Fontainhas 2:22 pm on April 23, 2014 Permalink | Log in to Reply

                                    The reasoning is valid for any language that belongs to a macro language, really, not to mention the ones which can additionally have “non-regional” variants, such as formal and informal, and so on.

                                    Even if a language does not belong to a macro language group, it could still be the case that the difference from one variant to the next is small enough for a copy feature to make sense.

                                    tl:dr I’m not sure it’s an actual, bona-fide, exception.

                              • Ze Fontainhas 6:34 pm on April 23, 2014 Permalink | Log in to Reply

                                Marking as “not request”. Also, this debate should move to the GlotPress blog

                            • Emre Erkan 10:11 am on April 23, 2014 Permalink | | Flag unresolved

                                wordpress-trtr_TR GTE
                                Tags: , glotpress,   

                                One glossary to rule them all 

                                First of all, thanks for glossary. It’s a life saving functionality.

                                I’m currently validating lots of project and trying to maintain order between them. Glossary is a very helpful tool to accomplish this but it’s project specific. Is there a way to use a common glossary for selected projects or for all of them?

                                Please don’t say import/export. It’s not functional when you try to keep all glossaries from all projects updated. For example when translating or validating a project, you see a term which needs to be put in glossary. You can’t add it to just that project if it’s a very general term. You have to put it to all glossaries. Yoı choose a projects glossary as primary glossary and update it, export it and import it every project you’re validating.

                                Possible solutions;

                                • A single glossary for all projects
                                • Import functionality betweeen glossaries
                                • Inheritance (When you create a glossary you choose a parent and with this it contains all the terms of parent glossary)

                                TL;DR -> title ^ ^

                              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