 Yeah. So, welcome everyone. Here I will do a quick introduction to the WordPress polyglots team. And it all starts with the WordPress mission statement. So the whole basic big idea about WordPress is to democratize publishing. And today already more than going to use US English, which means that they are using translated versions of WordPress. And this is very important because if we want WordPress to be available to allow people to publicize all over the world, then we should remember that only 5% of the world's population has English as their native language. And only 15% of the world's population know English. So there are 85% of the world's population that would be able to use WordPress only if they had it available in their own language. And that is what polyglots is all about. Of course, as a WordPress team, we need to have our Wappu and we even got several of them. He may be wearing a hat or not. He may be talking more about communication or more about different languages. But he always has this very nice feather pen. So now you know what a polyglot looks like when you meet them in the street. And the polyglots is one of the ways you can contribute to WordPress, give back to the project without even knowing any programming languages. We still work with languages. Of course, we need to understand English well enough to say the same thing in our own language in a way that makes it possible to use WordPress. And like everything WordPress, this is all volunteer based. So when you translate WordPress, when you validate strings, when you act like I do as a global mentor for the polyglots team, it's all volunteer contributions. And we are very thankful for this because this is an important part of WordPress. Here I have gathered quite a few useful links. In the invitation to this meeting, you can open a PDF with these slides so you will have all these links available. We have our own Slack channel. Of course, it's named Polyglots. And if you happen to not be on Polyglots yet, you can join via the link in the first row. In the second row, you have a list of all the polyglots teams. And there you can click through and open to see names of the people who are on your specific team. And also a lot of teams have Slack or some other way for their own communication in their own language. We currently don't use the global WordPress Slack for that. So most of them are on the Slack free service where you get 90 days of history. But that is of course enough to coordinate your work, ask someone to give feedback on your translated strings and so on. And in the same Slack, very often, you also find discussions about setting up some meetups or preparing for a WordCamp and so on. And also in some cases, you have some help happening there, although of course, in several of the localized WordPress instances, we also got a localized support forum that may be more or less active. Of course, we've got our own handbook. So you can see it here. And there you find a lot of information. Some are about the general expectations for the translations and also about how we work and what different rules we've got. And links to various local resources, like I said here, local Slack teams, but also we've got glossaries, style guides and so on. And we also got various additional tools. A lot of active development is happening right now with how you can use machine translation and so on. And in the handbook, you will find links to get started around these things. The translation itself is located on a translation platform, translate.wordpress.org. And if you at any point want to see how the translations are moving, what locales have a lot of unchecked translations or what locales are at 100% on the core translation, then this last link translate.wordpress.org stats will show you at the quick glance how the important translations are moving. To get started, you would of course first need to register an account with WordPress.org. And the link for that is in the first line here. And on that page, you can actually ask to get the same page in a different language if you want to. A lot of languages are available. And to communicate with the team, you would also need to join Slack. And the global Slack team for WordPress contributors, you can join by going to this make.wordpress.org slash chat. So notice that this is not on the main WordPress domain, but on the make one where we have all the contributions happening. And on the make WordPress.org slash polyglots slash teams, you can find people from your own team. And next, you go to this translate.wordpress.org and find your own locale. If it is, if your locale, your language is not defined yet in WordPress, then you can go to the handbook to find details about how to request a new locale. And then of course you will need to find some people to do this together, because it's a huge task to build a new translation. And find also some already experienced GTE, perhaps from a different locale, who would be happy to help you a bit with some tricks on getting started. Perhaps if your language is very much like a different language, perhaps you can reuse the translation that someone has already done for a different language and so on. And let's look at some pages, what this looked like. So if you go to translate.wordpress.org, then you will see this huge list of all defined languages. And in the top field, you can filter here to quickly see just the language that you are looking for. So I just entered two letters here and on the Swedish was left. So I clicked to contribute translation. Well, not I did, it was the test account I used. And here we are on the main page for Swedish. You can see that you've got various places for your, where you can translate. So WordPress is the core translation of WordPress itself. Teams are translations for the free WordPress teams that are published in our team directory. Those are teams that are made available by volunteers for anyone to use around the globe. Plugins in the same way is where we do translations of WordPress plugins that are in our plugin directory and made available for anyone to use. Patterns is where we translate or can translate various patterns that are available for use in the log editor to make the sample text and the descriptions available in various languages. This is a huge project, and not all locals have translated much here, but there are some who are really brave in doing that. And I must say it's Vita is the interesting part. That is where we have all the projects that make up the WordPress.org site. So if you have your, we call them Rosetta, the localized versions of the WordPress main site, all things that you can see there except for the content itself is translated through the Mita project. And that is also where you've got strings to help you localize WordCamp theme. If you are using the ordinary theme for your WordCamp, then you may want to translate the WordCamp project. You can also translate WordPress.org to get your Rosetta translated and so on. Apps is for the iOS and Android app. And there may be some peculiarities if you want this to be available in the language that is not yet defined. But you can always contact in the main Polar Gloss channel if you want to ask for it. That is a special page where you can find the most popular globally, most popular plugins and themes and see how much of them are translated to your language. And this is the place where Nilo suggested that we should be able to hide some plugins that are not really using the translations that come from this platform. So that people don't spend time on translations that won't be used. On the right side, you can see that you can filter or sort in which order all the projects you see here are. So if you for instance go to the plugins page, then you can filter or sort in such a way that you see all the plugins where you still need to translate something, but they are only a few strings needed to reach 100%. So if we go to the list of the most popular plugins, it looks like this for Swedish. And some of these projects are noted 100%. And if we go to one of them, we can see here that this plugin that we just opened here is, if you look at the first line, the stable latest release, you can see that the plugin itself is fully translated. But the read me, that is the content of the localized plugin page for this plugin is only partially translated, about 50%. And many locals actually do like this. They put most effort on translating the plugin itself, and when you have at the first time reached 90%, the plugin package will be, language package will be generated, and the plugin is translated. But for the read me, there are usually some strings that are less important. Those could be like some notices about what was changed or fixed in the latest versions. And if those strings aren't translated, that is usually not the big deal, as long as you have the most important things translated that tell you what this plugin actually will do. The plugin, the translation interface itself looks like this. So a string that is translated and approved shows like green. A string that is not yet translated shows in white. And then we have another couple of colors like red and yellow, yellow is for pending translations translations that need to be verified before they get public. And if you open up as one of these items, you will see something like this. So in this field enter translation here, we could write the translation of this source string. And if there was a very similar string translated before for this language, it might show up here under translation memory. If we would open these other languages, we could see how this very string has been translated to some other languages. And the same information we can also open here on the right side. So the meta block here is where we can have actions like approval translation, or disapprove it or redirect it. Disc is short for discussion, where we can have discussions, comments on various translations and questions perhaps to the developer. Hist is about history, translation history, how this very string has been translated before if there are any previous translations. TM is about translation memory. It's the same thing that we could see here below the translation. And the other is for other languages. So you can see that the same information here is actually visible or can be visible in two different places. And the reason here is that this is being actively developed as we speak. So this may change a little bit, but the main idea will still remain the same. The short way of standing in a translation to suggest it, or if you're a translation editor to save it, is to use shift enter. And the short way to copy the source string, if you want to use it and just change what needs to be changed for your language, is with control plus enter. And for those of you who are reviewing something, plus enter. And for those of you who are reviewing strings, if you're happy to be on a keyboard that has numeric keys on the right side, then you can use control and plus to approve and control and minus to reject. And that will allow you to work a bit quicker than if you only use your mouse. So currently, the polyglots team status as of yesterday, as I mentioned before, 56% of all word precise use a translated versions of WordPress. Some of those are still English, like English, Great Britain, English, South Africa, but I would say that at least 50% of all word precise are all on non English now. In our system, we've got 202 different languages defined. And the total of 208 different variants because, for instance, German have two different variants. One is the default where they have the informal address. And then they've got the formal address where they use Z rather than do. And we've got these things in a couple of languages. Right now, 68 locations are up to date and released with WordPress 6.2. And most of these are in well shape for WordPress 6.3 that is about to be released in a week or two. Right now, overall look helps, we've got 730 global translation editors defined. Here, you should note that a few people are GTs for several languages. And therefore, they may count two or three times. In the same way, we've got 5,535 users defined as translation editors for one or more projects that could be a team or plugin or several teams and several plugins. And here again, a few users are defined for several languages. And we've got the total of 66,000 active translation contributors over the last year. So I usually say that WordPress Polyglots is the biggest team of them all. And Polyglots is not the only place where translations happens. So the documentation team also does translation to a few languages. And we're looking into how we can cooperate in a good way for content translation, but we aren't there yet. And this is one of the topics that will be discussed at the Community Summit in August. Unfortunately, I will not be able to go. The training team also has contents in different languages and are looking at ways to keep track of this content and making it easier to find things you need. The marketing team also looks into content in various languages. And WordPress TV, of course, has content in different languages, and they do subtitling so that even if content is in a language you don't know, you could still watch it and understand what is said. Rosetta content is about the content that various language teams can put directly in their news section or in their handbook section on their teams site. And that is something that happens locally for each local team. And that was my presentation. It's time for questions.