 So, we will do a very short talk about how to contribute federal localization. So this is aimed to be very easy and short, so you are very welcome to ask your question in the chat or in the Q&A part of the chat, whatever you prefer, whatever the more convenient for you. So, my name is Jean-Baptiste Holcroft, I'm not a linguist, I'm not a developer really, and I'm coordinator of the localization team, so there is no official coordinator, but if you organize things and you take the lead to lead some projects and to lead some meetings and to reach up objectives, this is a role you can get in the community. So in the past, I've been contributing to a few major work and changes in our community. We changed our translation platform, we moved from Sanatata to Weblate, this is a new tool that we deployed at the end of 2019. I also worked a lot at the ability to translate the documentation of the federal projects, and a few months ago, I released with the help of Darknau, a tool to produce some statistics about the federal operating system. You can get more information about what I do, who I am and the way to reach me using the Wiki link that is available. So let's start by defining what we are talking about. As always, there is the theory and the reality. In theory, localization is the idea of adapting content or product to a specific location, a cultural group or a market. So don't sell the same way something in France, then you will do in India, in Japan, on the US. You adapt to the culture of the people you are talking with, because they need to understand you, most of the time you will try to speak their language, and they need to understand the references that you will do. If you make a reference to the family, the structure of the family is not the same in the whole country in the world. In some places, they will totally get you an advertisement. In some countries, they will just don't understand what you are talking about. Here, when we are doing free software, we are most of the time using translation. We mostly do translation and a little bit of formatting. We want the dates and currencies to be correctly displayed, but we don't go any further. Because going further requires your software to really be able to adapt to the different use cases you want to display to your users, depending if they are in one place of the world or another. And this, most of the time, is not technically feasible with the tools that we have in the open source community. And in parallel of that, there are some local communities, the advocates, the ambassadors, et cetera, that are doing local events that are designed for the local groups, and they do it very well. So there are some bridges between what we do as translators and what they do as the local communities. And sometimes the contributors are exactly the same. So what can we translate? First thing that we can see in Fedora as a community project is website. Here, you have the GetFedora website that is translated in Farsi. You can see that probably the text orientation is not correct, but you can have an idea on how it looks like. Still in Fedora as a community, you can translate the documentation. Here, you have translation in, I think it's Odia, which is a language in India. And the whole documentation can be translated. And the third aspect in which you can contribute in terms of localization is what we ship in Fedora as a Linux distribution. The release cycle and the publication is not the same if you are talking about the documentation, the website, or the software which are embedded in a major release of Fedora. Here on the left-hand side, you have DNF, which is the packaging tool of Fedora. And on the right-hand side, you have the installer, which is specific to Fedora. And you can see this installer is translated in many languages. And this is very convenient for the users. So these are the two words that we contribute to as Fedora translation community. So how do we do that? This is very, very, very easy. There is one single page to know about, and it's this one. What you need to know is where is our translation platform? Because we put everything that we can translate on this translation platform. You just go, connect, you translate, and you don't have anyone to ask about. You will see what others are doing. You will see the list of projects by the name. You will identify if this is the installer of Fedora, which is Anaconda. And you can identify if you are translating DNF or the Fedora website. And you know exactly where you are contributing. You have no Fedora accounts. Very easy. It will lead you to the place to create a Fedora account. A few information, one CLA to sign, the contributor license agreement to sign to confirm that you agree to the rules of our community. And if you need some more information, there is a wiki page. This wiki page is the localization team page. It contains hundreds of links about how to join, how to translate using weblates. What is the list of the teams? What are the different rules? It's very easy for you to find information. Of course, you will see some issues. And if you see some, you can report them to this link. We have a page of repository containing our list of tickets. You say, hey, I cannot access this project. I cannot find this thing. You can ask the question there. Or you can use directly the mailing list, the translation mailing list. In this mailing list, you will reach contributors for all over the world and the few people that are like me, coordinator or admins. But if you want, you can do better. You can try to fully join the Fedora community. There's a little guide, which is much longer than this slide. This slide will just tell you the two most important point is the first one is to ask to join the localization group, which will allow you to be free part of the Fedora community. It will allow you to edit the wiki to vote to Fedora elections. And there are some other places in Fedora where there are some technical limitations to prevent vandalism and boats. So you need to be at least one more group than the group that say that you sign the contributor license. So this group has no other meaning. It is useless. It will not give you any superpower or anything. It will just allow you to be fully part of the community. And the second thing that is very, very important is introduce yourself. We are all working remotely, not because of the COVID, but because it is an open source contribution. We don't really need to be face to face to do our work. Of course, it's better to make some projects. It's better to solve some issues. It's more interesting, but most of the times we are far away from each other. So it's very welcome. When you send a little email that say, hey, hello, I'm Jean-Baptiste. I'm new. My nickname is Fedora. In Fedora is Jebeque Fed. I'm in France. I'm in Strasbourg. And this is what I like about Fedora. This is why I'm doing what I'm doing. I want to try to do that thing, do someone have the same interest and we work together to do it. This is the value of reaching us by email. There is a template that is provided in the Elton N Guide. So if you have no inspiration, just take the template. It's totally fine. Then there is our organization. So you can see the Fedora design team did some little pandas for us. So a translator in our community can do everything, but a translator cannot create new translation components. There are about 660 people who are identified as translators. And we estimate, web-late estimated for us, that there are 70 people that are active, which is quite good. There are some coordinators. Coordinators is one point of contact per language team. So there is one point of contact for the French team. It's me. And there is one point of contact for the German team. Sometimes there are multiple points of contact because they want to make sure if one is not available, there is at least someone who can answer the question. There is no superpower in being a coordinator. You just are someone that is reachable to reach for help or to ask a collaborative question. Hey, I don't know how do we translate this and what's the usage? How should we do? This coordinator is the right person to help you. So we have 87 language teams in Fedora. Of course, if there are 70 people active, not all of these teams are active. Some languages are dead in terms of activities. And if you want to take the lead and try to translate in this language, just go ahead, very easy, nothing to worry about. And at the end, I mean the guys with the superpowers. So I have superpowers. I can create a WebLate project. That's all. No other superpower. And we are three people being able to do that. There's myself, Jean-Baptiste, Raphael, and Yuri. And all of them are reachable under the mailing list. So if you want to translate something and it's not in WebLate, you want to add it, you can join them. But don't worry, there's already a lot to translate. And that's it. Thank you very much for your attention. I wanted to keep that presentation very short. I'm showing here a few links that may be useful for you that gives you a few stats about what we do, where to find some information. And as we are a federal community, we always contribute upstream. We will not fork GNOME translation. We will go in the GNOME translation project and we will contribute there. So the translation is doing the same as the value of federal upstream first. So thank you very much. I hope that you learned something in this meeting. We will continue with the questions answered. And that's your call. So we see someone where I did recently to the federal community. So this is Luna, welcome Luna. So I did not plan to make any demonstration of the translation platform itself. So the federal translation platform looks like this. When you learn, you see a component list. Most of the time you will look at your language. So as I translate only in French, it's in French. You will see a long list of projects. You select whatever you want. You see full green means everything is done. Some arrangements, there is some work to do. So there is like 300 untranslated strings, which is quite a lot of work. And once you go there, you will have the user interface. You will see everything that requires attention. You will be able to translate. We'll see also some suggestion. You see this works. And that's all. It's very easy to do. So there is some guys already available in the internet. Yes, Luna, this is a way to use untranslated. And also in the web late, when you have the page of your language, you can see the checks. So in your language team, so I think you are translating in Norwegian. You can see here history. We tell you who is doing what. You will see the world changes in this language. But you will also see the failing checks. So these are automated detection that done by web late to tell you, oh, you see here the colon is not correct. It was in a different colon in the source string. So you can go and fix it very, very easily. So it helps you for quite a lot of things and the inconsistence were highlighted before in another talk. It tells you that there are one, two, or three times the same sentences in multiple projects. And in one project, it was translated one way. And in another project, it was translated another way. Either one translation is correct, either they are all wrong. Because normally, most of the time, you have the same context for short strings. So it should have the same translation. So it's very easy to find some very good, very big mistakes here. And also it will detect when you already translated something and it's not translated in another project, it will help you to go faster. So question, is it possible to have contextual information while doing translation? Thank you, Benjamin. When you are in the translation platform and you are editing a string, on the right-hand side you have the place where the translation occurs. Either it's one directing to source code, it will tell you in the upstream source code where is the string you are translating. Either for some projects like the typing booster, the developers can send screenshots about the user interface in English and it will tell you the string you are translating is there in the screenshot. So you will directly see in context what you are translating. It's very convenient, but it's not all project doing that. So who should I contact to correct? Indonesian plural, very good question. The first thing would be to open a ticket in Pedro. And I think the plurals that are used in web late are coming from CLDR. And the CLDR is a huge database containing a lot of linguistic related content so that the tools can reuse them. So you don't want to keep a list of what is the text orientation, what is the date format for each software that you write. So they wrote some definition, standard definition in multiple formats in JSON, in XML, et cetera. And the upstream project are using it. So web late is using the data coming from CLDR. And either the plural is wrong in CLDR and we should fix it upstream. Either this is something specific that requires a local modification and we can edit it in our own translation platform. But most of the time the CLDR is correct because these are linguistic experts defining these things. So we can help you to put you in contact with them and understanding the process because as every international organization, processes can be quite heavy and complex to understand when you don't know it. Okay, I said Norwegian and it was Swedish, sorry, Lena. So I wanted this talk to be short if you don't have any other questions, I will finish the presentation. Have a nice day and please enjoy Fedora community and Fedora operating system.