Polyglots Monthly Newsletter: May 2023

To subscribe to our newsletter and receive updates in your inbox, you can sign up here.

Welcome to the May 2023 edition of the Polyglots monthly newsletter, the monthly news roundup from the WordPress Polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/.

We’re exploring a new format for this edition – a link roundup. Your input is always welcome if you have feedback or suggestions for improvement.

📰 Polyglots news roundup

  • WordPress 6.3 Planning Proposal and Call for Volunteers
    The planning proposal and call for volunteers for the next major version of WordPress—version 6.3—is published. If you’re interested in contributing, check out the post and leave a comment with your interest.
  • WP Translation Playground
    Have you ever wanted to translate WordPress and other projects in context? There is now a new tool using the GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and WP Playground, which creates a new WordPress install in the browser, that lets you do just that. Read the post or click on the new Translate Live link on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. to try it out.
  • Translate Live: Updates to the Translation Playground
    In addition to launching the Translation Playground, there is now a post describing updates to the tool. These updates include a new name, Translate Live, and the integration of glossaries, placeholder checks, DeepL and ChatGPT, among others.  
  • Adding ChatGPT and DeepL in the Translation Memory
    Automated suggestions from ChatGPT and DeepL have been integrated into the translation memory on translate.wordpress.org. If you’d like to test this new feature, follow the instructions in the announcement post to complete the setup. Note: If you have a working prompt for your language, please share on the post to help others test!
  • Some updates at translate.wordpress.org
    Building on the additions of ChatGPT and DeepL, there are some additional updates to translate.wordpress.org. These updates include external APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. checking, automatically copying 100% translation memory matches into the text box, and only using DeepL or ChatGPT suggestions if a perfect match doesn’t exist in the translation memory. 
  • Explorations for a notification form between documentation and Rosetta sites
    The Docs team is researching improvements on how to update Polyglots teams when new end-user documentation is updated or created. If your team currently uses HelpHub or is interested in translating documentation in the future, please share any feedback!
  • Polyglots outreach effort retrospective
    The Polyglots outreach effort contacted over 50 localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ teams to better understand priorities and challenges for inactive or less active translation communities. There is now a retrospective post of the feedback received and some potential next steps.
  • Defining the Polyglots contributor ladder
    Based on feedback from the Polyglots outreach effort, there is now a post proposing a general definition of the Polyglots contributor ladder. Please share your thoughts and feedback on the post, especially how or if this may be helpful for your locale team.
  • Idea: translate.wordpress.org tour
    Also inspired by feedback received in the Polyglots outreach effort, this post outlines an idea to help educate new or inactive translators by walking them through the translation process in translate.wordpress.org. Thoughts on how, or if, to implement an idea like this are welcomed.
  • The Next Generation of WordCamps
    For Polyglots who also organize and create local, community events, there is a new proposal to experiment with new community events on the Make/Community team blog. This is a great opportunity to help shape the future of global, in-person WordPress events.

🏆 Get involved

Are you looking for more ways to get started? If you’re translating or want to translate WordPress and any related projects into a specific language, there are some helpful resources.

  • View the list of currently defined locales to find your language community.
  • Review your locale’s Glossary and/or style guide before you get started submitting translations.
  • Request a review of your translation through your locale’s Slack or on the Make/Polyglots blog by following these examples.
  • Does your language still not have its own support forumSupport Forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations.? We can help you start on Make/Polyglots or the polyglots channel.
  • Want to help make the Polyglots newsletter even more global? Translate this edition to share on your locale’s /team page!

If you need help, ask in the polyglots channel in the Make WordPress Slack anytime. We’re a global team, so there’s almost always someone around!

Thanks to @kharisblank and @psmits1567 for helping to write this post!