Erica Varlese 5:35 pm on December 12, 2022
Tags: , , , , , , , , ,   

Reflecting on 2022 in Polyglots

As 2022 comes to an end, it’s nice to reflect on everything we’ve accomplished. Whether you submitted your first translation or your 1,000th translation this year, there’s much to celebrate.

Thanks to 19,357 of you who contributed translations this year, WordPress is more accessible to more people in more languages. Whether you contributed one stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. or more of the 8,454,029 translations in 2022, your contribution matters. Thank you!

People are what make the WordPress project great. So let’s celebrate a few of you!

Congratulations to the following localesLocale 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/ for having the highest number of active contributors this year:

Bravo to the following Polyglots for translating the most stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. this year:

In addition to translating, we can’t forget everyone who reviewed suggested translations. Thank you to the following top users of the new feedback tool this year:

Localizing WordPress often goes beyond translating the software and plugins. Thank you to everyone below who helped make learning materials on Learn WordPress available in additional languages, by reviewing and translating lesson plans, hosting workshops, or creating new tutorials:

Let the Training team know if you’re interested in helping to create more material for your 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/ on Learn WordPress!

Continuing in the theme of educating and helping others with WordPress, kudos to these locale teams with the most replies in their local forums:

  • German (#de_DE) – 12,585 replies
  • Spanish (#es_ES) – 5,038 replies
  • Russian (#ru_RU) – 3,422 replies
  • Dutch (#nl_NL) – 2,400 replies
  • Japanese (#ja) – 2,298 replies

And thank you to these Polyglots for helping MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. organizers around the world share their thoughts on the official WordPress Chapter Meetup program by translating the 2022 Annual Meetup Survey:

A moment of remembrance

Each WordPress contributor helps create a path for others to contribute more easily. This is especially true of the prolific contributor and member of the Polyglots community, @wolly, who passed away earlier this year. Let’s take a moment to remember him with these kind words from @francescodicandia and @lasacco:

Wolly took care of the WordPress Italian translation from the beginning. During his life, he contributed a lot to the dev and Polyglots teams, supporting people and helping them to use and translate WordPress. He passed away in June 2022, leaving great sadness in all of us and in the WordPress community. We have no words for the void he left behind, but we know how great his commitment was and how lucky we were to have met him.

I know these are just a small snapshot of all the hard work that Polyglots contribute throughout the year. If you have any special achievements that you’re proud of – for yourself or your locale team – please share them in a comment on this post. 

Congratulations on all that you do to make WordPress available to so many people! 🎉

Thank you @nao @bsanevans and @tobifjellner for contributing to this post.