 Thank you for being here. It's awesome. We have 65 events happening in different parts of the world today. It's pretty impressive. This is now cool, right now presenting at our live stream. Are you all registered for our live stream? We have a live stream happening on Crowdcast and it's going to be 24 hours of sessions about translating different languages and from different people. This is not what we're focusing on today. Is there a clicker I can use? Or should I...? No, that's alright. I can just put supplies from here. So this is a quick introduction. How many of you have translated WordPress before? Nobody has translated WordPress before? That's awesome. So you're all new contributors? This is pretty great. I really like seeing people that have not translated before. It's very easy to get started. We are a huge team and you can be a part of it too. It's a real pleasure to be here talking to you. WordPress translation day, as I said, is today. We have a lot of things happening simultaneously. We have events in Asia, Europe, everywhere. If you go on WPTranslationDay.org, you can see the map of everything that is happening right now. We are doing this for the second time. So you're a part of the second one. This is the first event. Thank you, John, for organizing this. I hope this is not going to be the last one. Our primary goal is to show you guys how to translate WordPress. You'll probably always use WordPress in some form or another. Your work or your blogging or you're doing something. If you speak a language other than English, which you apparently do, you can help contribute to WordPress because WordPress is made by volunteers. As John said, there are 14 teams contributing. The Polyglot team has about 10,000 people already helping it worldwide. We are in 160 languages and even more. Chinese and Japanese being one of them. The other goal of the day is to learn for developers to learn how to make their software translatable. There are a couple of sessions during the livestream dedicated to that so you can check them out. The next thing that we're going to do is there are going to be live streaming sessions from all these events so you can see some of the other people that are already doing this from all corners of the world. Our primary goal is obviously to get to know each other to meet and have fun and to make the web a better place by contributing to one of the most popular open source projects. A few terms. You will probably see this a lot, L10N over there. That's an abbreviation like a shortened word for localization which literally means translating software. It means making software, like translating software in a particular language. I80N is the other kind of similar abbreviation that you're going to see and it means internationalization. The reason they're shortened like that is because both words are mouthful and also they take a lot of space on Twitter. You use internationalization on Twitter and there go your 140 characters. Developers have found a way to shorten this so localization is L10N and internationalization is I80N and the numbers stand for the number of letters that you have in the first and the last letter. Don't count them as the right one. Some of you would have noticed if that wasn't the right one. What is a locale? A locale from a geographical perspective, that's a place. From a software perspective, it's a collection of information about a certain language as spoken in a certain place. A locale is an identification that shows which language is spoken in which place and it includes information about currency conversions and data, dates and how those are spelled, currency symbols, numbers. There are different numbers in the different scripts. A locale has all that information. When we talk about WordPress translations we don't talk about languages, we talk about locales because we have, for example, different locales for Spanish. We have nine different locales for Spanish because Spanish is different depending on where it is spoken. Portuguese as well. For example, Brazilian Portuguese and Portuguese as spoken in Portugal they have big differences. They have differences in the way the sentences are constructed. They have differences in vocabulary. Some words are entirely different. You guys probably know how American English is different from British English sometimes. The British people don't really enjoy reading and using American English all the time because they find it simplified. So we have six different English locales. We have the original US American English. We have British English, Canadian English. We have English as spoken in New Zealand, Australia and Canada. So all of these people, the point of that is to make WordPress sounds a little bit more local. So when somebody from Canada or somebody from the UK opens WordPress it doesn't greet them with howdy, which is a Texas kind of way to greet people. It greets them with how do you do, which is a very British way to greet people. So this is what the local information holds. And WordPress has 164 as of today, different locales. Those may be different languages but they can also be different languages as spoken in particular places. Sorry, I didn't, I thought that I updated that. It's 164, we added several more. This is how WordPress grew. So in 2003, it was only 13% of the web. And today, it actually, as of yesterday, powers 27% of the web. This is old data as well. And a lot, a big part of that is due to the fact that very early on people started translating it. So today, until 2014, you could only download different languages from the local Rosetta sites. But after that, in WordPress 4.0, non-English locales for the non-English translations for the first time kind of surpassed the English ones, which means that WordPress is used in languages other than English more than it is used in English. All of the combined languages, they form a bigger usage than English. Yeah, so today we have 140 and 64 locales. And 73 of those are translated at 100%. So every WordPress stream is translated into those languages. The rest of them are either 90% was translated or 50% was translated. And we have several new ones that are still, you know, at 0 to 50%. This is old data. I'm going to just quickly run through this. I need three locales of more than 50. And 62 locales have less than 50% translated, which means that they have a lot of work to do yet. And our next target as a team is to get WordPress between the percent and the top plugins and teams, which are also available for translation online. We want to get them to 100% as well. So how does it work? This is the main address. This is where you'll be going today. It's translated to a WordPress adored. When you go there, you have like a big list of languages and you can search for your language and you can select it and you can start translating. You only need a WordPress adored username to do that. This is how the page looks. If you open it, you will see this. You enter, start typing the name of the language that you want to translate in. You select it like this. You see the projects that are available for translation. You click on translate projects and it starts. You will see the original stream on the back, like the fields to enter the stream. You enter the translation and you hit enter and you're done. This is your already suggesting streams. It's very, very easy. It takes two clicks. You only need to have a WordPress adored username. Everybody can suggest streams, but they don't automatically get imported to the project. For that, we rely on people that we call general translation editors. These are people who have been involved with that locale from the start or spent a lot of time dedicating efforts to it and they can approve the suggested streams. Their primary job is to make sure that there are no typos, no grammatical mistakes, no punctuation is correct and generally the translation follows the style guide for that particular language. Because you know how some people translate some words or even translate some words differently. The idea is that if there is a term, it has to be translated in the same way across all projects. For example, email, whether or not you live in English or you will transliterate it or you will spell it with a dash or something like this. The translation editors make sure that their translations are like their quality translations and that there are no mistakes so that we don't push that language to users. Then the step three is to release the translations. Those happen automatically these days for the most part. Most locales in there are 100% when a new version of WordPress is released. They get automatically released, translations get automatically released together with WordPress. For example, if we get Japanese to 100% by the time WordPress 4.7 gets pushed, which will be in December, then Japanese translations will automatically go to all the people that are using WordPress in Japanese on the day that WordPress 4.7 gets released. That is valid for each of the other languages as well. This is due to a functionality that got imported recently. There are code language packs, so those ensure that automatically all the translations will be updated on the day of the release. Then when that happens, on install, people can go and select the language. When they install WordPress, they have a list of all the languages that are 95 plus translated and have been released for WordPress. Then also from the user admin, you can go and change your language. The language is available, or again, the ones that are released for the last two versions of WordPress. There is still a way for people to download WordPress in another language. Each locale is associated with its own local WordPress.org site. For Japanese, we have ja.wordpress.org. For Chinese, we have cn.wordpress.org. You can download WordPress in that language at the latest release from this big, beautiful button over here. A little bit about the Polyglots team. This is a volunteer team. It's the biggest contributor team WordPress has. We have more than 10,000 people contributing and more than 1,000 translation editors. These are all people that are dedicated to the system we spend a lot of time translating WordPress and validating and helping the translator contributors validate their strings. Most of the Polyglots are native speakers, which ensures that WordPress will speak, will not speak, robotic language. It's easy to run things through Google Translate, but more often than not, those translations are unusable by real humans. We have real people translating in a way that actually makes sense for users. That's what we ask our general translation editors to try to do. The translation is usually started by developers who need a translation for a plan project or something like this. But over time, with the way the team is evolving, more and more non-developers join the team. You don't really need technical skills to translate. The only thing that you need is knowledge of WordPress because you have to be able to make sense of the thing you're translating. You have to know where it is in the admin, what it does, so that you can translate it. If your language is already in, you can go to make WordPress a lot of such Polyglots slash teams and find your local team. This is the blog where we communicate, where we talk to each other, where requests are published when needed and where general discussions happen for the global team. We communicate in Slack and you can register for the general WordPress Slack when you go on chat.wordpress.org. If you already have a WordPress.org username, you will automatically be assigned a chat at WordPress.org email address and you can register for the Polyglot Slack. John will help you out with that after the session is over and the people that are already on Slack can also help you out. This is how Slack looks. This is the Polyglot's channel and Slack is a chat program. When you have a problem, when you want to ask a question, when you want to find somebody, you go and you ask a question or you talk to someone. If you don't know how to translate something or you need a little bit of context, this is also the place where you ask. This is where we have our weekly meetings every Wednesday. We have two meetings, one for the Asia-Pacific region and one for Europe, Africa and the Americas. We just gather together and discuss common topics, problems that are occurring, things like that. We also have update notifications of incoming streams. This is what they look like. This means that whatever new streams get pushed to one project, Slack gets an indication about it and you can see if it can go translated. There are local Slack channels. This is the Bulgarian one. There's the Japanese one and I'm not sure there's a Chinese one of me out here. Is there a Chinese one? A Chinese Slack channel? I don't think so. That's all right. You can still use the general one and you can also create one if you want to or one of the Chinese general translation editors can. This is how a local Slack looks. The idea of a local Slack is for you to be able to discuss translations in your language because with people that are working on the same language. Then we have blogs, the made WordPress.org slash Polyglot blog that I already talked about. This is where we discuss everything that is related to the global team. The Rosetta sites are quite important. They are a primary tool for the active contributors to communicate with anyone speaking that particular language. It's the local equivalent of WordPress.org. This is where all the messages about meetups and about new upcoming releases of WordPress need to be published. A lot of communities are using their sites very, very actively. The new challenge is to translate all the plugins and themes. There are 30,000 plugins and 7,000 themes in the repo so we have a lot to do. Translating is a great way to procrastinate. It's my favorite way. When I don't feel like doing my ordinary job and instead of going to watch YouTube videos and pictures of kids online, I just go and translate. That way I feel I'm doing something useful even when I'm not really doing what I'm supposed to be doing. Translating is a great way to get away from a particular task. It's a really nice way to give back to the community. As I said, we have a lot of translating to do. By all means, if you have a plugin or a theme that you like for WordPress, you can start there and you can translate those. These are the steps. You need an account at WordPress.org to translate. You can create one when you go to login.wordpress.org. After you create one, you go to translate.wordpress.org. You just start translating. Pick a project. If WordPress is not translated, then biome suggests translations for WordPress. But if it's fully translated in your language, just choose a theme or a plugin and that's what you can contribute to. WordPress is the translation tool that we use, the translation management system that we use for WordPress. It's an open-source project as well. It lives on translate.wordpress.org. So translate.wordpress.org is powered by WordPress. That's what the software is called. And these are the translations that happen at translate.wordpress.org. I don't know why these slides are repeating. Some useful tips when you're translating. There's a translator's handbook. If you have any questions, most of the answers to those questions about translating are at make.wordpress.org.slashhandbook. You can find your local team and the general translation letters for the languages that you want to translate in. At this address, make.wordpress.org.slashpodlog.slashteams. And if there is no local community, you can create one. You can resurrect your local community. When you go to make.wordpress.org.slashteams, you will see that some of the locales will be in red. That means that they haven't been released for at least two versions of WordPress. That means that they are kind of sort of abandoned. Not being released for the last two versions of WordPress means that nobody has worked on those locales for more than ten months. Which means that maybe people don't have enough time. That is okay, because everyone's volunteering their time. But that also means that if your language is one of those red languages and you want to help it move along, you can pick it up, you can post a request to become a general translation editor, and you can help your language get to 100%. So yeah, you can request to join a team. You can contact the current general translation editors. Most of them are on Slack. If not, most of them have information on their WordPress.org profile. And yeah, you can become a general translation editor. So one thing that we need to know when we translate WordPress is that everyone's a volunteer. So we never make demands. If you join a team, we will never come to you and say, well, you know, why aren't you translating? We know that you're all doing this out of the goodness of your heart because you care, but there are never going to be any demands. Even if a language gets stuck for a couple of months or a year, that's all right. The good thing about contributing to WordPress is that WordPress is big enough these days that sometimes, at some point, somebody will step up, somebody will bring it back on track. Your participation in the team needs to be on your own time. It doesn't have to interfere with your ordinary schedules. Most of us do it because we really like each other. And a lot of us do it because we need WordPress translated into those languages for our work. So you can find your own reason over time to keep doing it or to keep contributing to the team. You can do it on your own time. Nobody will never hold you accountable or ask you to dedicate more than you can. If there is no local team for a language that you're interested in bringing WordPress to you, you can request one. There's just post a request on MakeWordPress.org slash Polyglots, and the team will work with you to create that locale and to make it available for translations for everyone out there. This is how a locale request looks. You need to provide some information, do a little research. There's language code included. You have to do a little research on plural forms. But basically you just say, hey WordPress is not yet available in this language. Can we create a locale so people can start translating it? This is just an example of one locale request. In your local team there are general translation editors, project translation editors, and translation contributors. General translation editors have the power to approve streams for all projects for that locale. Project translation editors are only responsible for, for example, a particular plugin or a team. That means that they can suggest translations for all the other projects, but they can approve translations only for a certain project plugin theme or part of WordPress. And then the translation contributors are all the people that are suggesting streams. All the people that are going and adding translations to what trans projects that don't have them yet. Every team, or most of the teams have local file guides and lossaries. Those are documents that help you know what words are translated how. So a list of general 100 or 200 terms that you need to know how to translate and how I translate throughout the project. The style guide is just instructions on how to approach certain types of translations. All these are a little, I mean, all these are a little vague. You will get to them, once you start using it, using the software and start translating, you will, you will understand what I'm talking about. So the general expectations when translating, you can't include random links in translations. A lot of people in the past have tried to like, in the first translations, have tried to promote their own services in their languages and things like that. We don't do that. That's not why we translate WordPress. So you can't include random links. Not only you shouldn't, you actually can't because the software is not going to accept a link that is not included in the original stream. Don't translate literally, that means that sometimes you might need to change the order of the words and you might need to change, you know, an entire sentence or not even use a particular word. Just make it sound as if, you know, just make it sound human. Don't translate it, don't translate every word as it is. That's what Google Translate does, we're not Google Translate for people. The same level of formality, I'm not really familiar if Japanese or Chinese have formal and informal, I'm guessing they do. But for example, in English and in a lot of languages, sometimes you use a certain language when you want to speak more politely as if, you know, you don't know the person and you use different type of language when you're speaking to people you know and you're familiar with. I can put some grammatical forms and things like that. So wordpress, look up what the general tone of wordpress in your language is and try when you translate, try and keep the same level of formality for your translations as one. Slang or audience specific terms. For example, the best example of this is actually in the original translation, so how do you slang? But you know, it's not the general hello, it's not the general hi, it's a very specific area, specific term. We forgive this sometimes and that's why we localize because we can make wordpress sounds like we want to in our language, but generally slang is not accepted. And you can, the general rule of thumb when you want to see or want to get advice on how to translate a particular thing is to look up how a particular term has already been translated in wordpress. So generally reference back to the project itself. Some common mistakes. Translation, instead of translation, we talked about this. So usually you just use the English words and spell it out in your local alphabet. You know, it's alright for some terms, but don't forget that we're translating wordpress for the people that don't speak English. Yes, a lot of us speak both English and like our local languages, but we're translating wordpress for our kids and for our mums and for grandparents and for people that want to use it that don't really know what that word means in English. So if you translate it, it's going to sound the same to them as it will sound in English and they are not going to know what it means. So try and find an equivalent of the word in your local language. Be careful of there. Sometimes translations, you will see these kinds of configurations. Those are so-called placeholders, which means that they're replaced by links or things like that in the original translation. So when you see those, you shouldn't translate them. You should keep them the same way they are in the original. Don't use Google Translate, so it's about that already. And don't translate the things that you don't understand. If you don't understand the stream, it's better to leave it. Somebody else will translate it or the translation editor will take care of it. What you can also do is look it up and try and understand what it means. It takes more time, but it's generally better than just literally translating something that you don't know the meaning of. There are translator comments. Sometimes you will see that when you start translating, you will see that on the sidebar. Sometimes developers leave comments for translators explaining what that string actually means and where it's used. Keep an eye out for that. And translation comments and contexts are important because they give you a deeper insight into why we're translating and what we're translating right now so we can do a better translation. Yes, and quality and consistency matter. So keep up with your local style guide and glossary if there is one and if there is not one and you're not sure about the terms, just look them up before you can save them. And if there isn't one, if there isn't a local style guide or a glossary, you can always start one. That's why it's an open-source project. Like everybody, you don't need any type of authority to start doing something that is missing. You can just go for it and just share it with the others so that they can expand it and work on it. That's it. Let's translate and there is a handbook page that says Getting Started Country Today. We'll leave the link to it or like write the link to it on the blackboard so you can, like if you don't remember anything of this projection. Just look at the quality of the gloss and contribute to the final product. We will write it down on the whiteboard. There is a list of steps there, all the links are there so you don't have to really remember any of this. Maybe the only link that you need to remember is this one. It's easy, translate.wordpress.org. Alright, thank you so much for being here. I'm going to go back to the live stream but I'm going to be around today so if you have any questions I'm happy to help. John is also going to answer some questions you have. Robert is a translation editor for several plugins for Chinese so he knows the platform as well so you can ask him. Deligated. You can tune into the live stream at some point if you want to watch some sessions as well. The live stream, we're going to write the live stream on the whiteboard as well. At 4 a.m. do you see what time is it? Is that here? 12. Yeah, there's going to be a community session for the Asian Pacific region. Cool. So it would be awesome if you stream these guys in. Yeah. So you guys say hi to the rest of the world. So here we go. We thank John for being so nice to you. Yeah. So if I get it correct, can I check? Yeah. I'm going to pass this guy over there. Hi, John.