 Okay, so let's go ahead and get started on the next one. This is Michel and he's going to talk about the web late. I'll say that, right? Yeah, thank you. Hello, I'm a culture and I'm out of no problem, right? Which can help you with localizing the source term or not only source term, but I kind of pleasure with my use of localization. Maybe let's start from the beginning. Do you know what localization and internalization is? There are two things of the process. One part of the process is to make some questionnaires possible to use in different languages. That's called internalization or in the short term, with 18 in the total being because it is long and it has to enter all together. And the other part of the process is localization, which actually does the translation itself of the software, so you need to be prepared for that. And then you can use some tooling to make it possible. There are a lot of channels making possible localize and the place tends to be framework agnostic. So whatever you use on your platform with Android application, which has native support for localization or iOS things or web extension localization or get text, the website can use all of that. But we need people to do localization and working with the people is sometimes hard because they have different knowledge, different backgrounds and you need to make it easy for them to contribute. Especially if you are focusing on languages which are not that widely used, there are minor communities and you will not find technical skills for people to contribute to the translations. And at the same time it's needed to provide fansatars context so that they know what they are translating. There are a lot of words which can have different meanings depending on the context. The favorite example is the name of the poster style which is a sum. If you just look at the text, you will probably figure out that it's this name. But if you will just see these three letters, it can be as well short cut or something. And if you don't know where this thing is being used, you will miss it out in the translation because it's not that easy to figure out just on this thing. So that's something what tools should make it easy to contribute to us. At WebLine we have made in the beginning one design choice that we will use of interface to make localization really easy for everybody to contribute. That means that fansatars don't have to care what's underneath. They don't have to care that there is some good version control and there is full request that has been open with the translations and whatever the developers actually would like to have. So it's done on the tooling side and WebLine tries to hide as much as possible from the fansatars. The other thing we have decided is the version control integration. There was one of the main reasons why WebLine at first started in the beginning because there was no other localization framework that we would integrate with the version control system. Now there might be some options possible but in that time it was the only one and he started really with simple integration that whenever somebody edited single string it made a commit and that led to thousands of commit and it wasn't really working well. So over the years we have developed something which works more clever and tries to do commits on every day and can do full request with GitHub and similar additions. I've already mentioned about context. One of the things which might be useful is just described where this thing is used. That helps in the thing like the star and Sunday I mentioned before. But there are many more useful things to add. For example, if you have a screenshot context then even if the people are not that technical skill they can see where the thing is used they can see other buttons on the page and can understand what is being used. But still people will make mistakes and the tool should be able to figure out that they have made some mistakes that are easy to fix or easy to spot. So we have some kind of quality checks and these are focused on things which are to some degree certainly detectable so that we don't annoy people that much. It's like missing format strings, a broken HTML map markup or similar topics or things which are actually enforced from the developer side like length of the string or space in which it should be rendered. And not everybody fits the same workflow. So in the end we have came up with add-ons to customize the workflow. It can help you, it can make you change the way the localization format is stored or it can customize how you accept the translations. You can have some review process, you can have both intro suggestions, all these minor details that make possible to work within different scenarios. And how can you start with app using WebLite? You can start your own instance, it's just docker in which you can start with a click on pause and get a thing done quite fast. You can use also our hosted service which has been here for the software or if you are looking for some commercialization you can do that as well. Let's take a quick look how it looks like. I hope the screen show will work fine. When creating a project, basically the most important thing you need to do that in the final is to store the repository. WebLite will connect to that, will present you set of localization files which has found in the repository. So we have some choices here, there are some under-properization, it's our demo project, it's not probably something that you will see, but it just will have some more choices. So it has different performance, it's detected where the files are stored and when you imported a shop in the interface you can see the status of the post. Individual translation sent to individual languages. So we can see the only complete language is source language, it's English. That's because we always track all source things as well. That's quite recent change, if you are looking at all the versions before it was not does under, but it was tracking underneath an area and now it's just more visible. And for the other transactions, you can see some code for progress bar which indicates different states of the string, the green one is translated, then there are some things needing action or the other ones that indicate some false checks. You can look into some of the 10-sided string or actually not 10-sided string, you can see the quite simple user interface. The most important thing is you can actually enter the translation and you can see other information which Vibrate has figured out about the string. This is the way the project was imported from the PO files. So you don't see much additional information here. There is which translation file is there. There is source code where it was expected by Vitex. And you can see, you can add screenshots at some additional context here and there is a glossary on top which is also empty right now. The other thing which we have is quality checks. This is again, as it was imported, so it's things which were built in and don't need any configuration and there are some things which can be configured as well. So the most incredibly interesting thing is the writing format thing. It's the check that indicates that the translation is missing from that thing. You can see it's highlighted in the source and it's missing from the check translation so that indicates some sort of problem in the translation. It's highlighted like this. It's listed in the things to check on the right side of it so that it's view visible and you can dismiss it if you think it's post-pository. Actually, it takes that. There's also indication that person as it's missing in this thing here. That's pretty much all I wanted to show in this short demo. If you want to figure out more, there will be a longer talk later today at 5 p.m. for which communities. I will go in more details that if you want to chat with us in less formal way, you can join us for a bit today evening. And there's also WebLite tomorrow at lunch where we will discuss with the objectives in WebLite and going in more details about how we know to develop WebLite later on. So thanks for your attention and do you have any questions? We'll hear you somewhere. Hi, thank you for the talk. Can you quickly say how if you're dealing with Cdata and Xlib annotations or like this used in Android? Xlib and Android are quite different. Beats with Android, the thing is that it doesn't, the format itself isn't well-defined behavior in XML. So whenever there is some markup, it tries to use it as a markup but if it's not a live markup, then it still does something. But we try to display the markup as is for the translation so that people can do the original thing which was intended there. The similar thing which is in Xlib, the support of the XR placeholders and they are encoded as XML and shown as XML in the interface. And Cdata, is that the problem? Cdata is a lot, probably won't be as a bit counter as it might be, so it won't be passed as data and I'm saying I don't think we will. So you have time for one more, okay? I would like to read the WebLite to our view workflow and are there some API that can be called to say to WebLite or from WebLite to say to our Jenkins environment, this is cool by the side of the translations? We have WebLite has API so we can control most of the things. It's not yet complete that it will be able to do all the things which are able to do in the UI but most of the things can be done on the API. You can also use some webbooks notification to let the player know that there are some changes in your AFTIM level. We have suffered most of the code testing services and for letting the other side now, that's currently almost the whole program, things like all of us are pushing to get depository or direct delivery but we don't have any outside hooks right now. Okay, so. But you can always write your add-ons to integrate with us. Let's just do lines of Python and you can do your customization with that guy as well. So there's a way when, for example, when an editor approves the translations or something else, put the translations to say to the CIA or whatever, the translation are done correctly. Yeah, that's it, then we'll have to be integrated with some more, I don't know, that's currently not supported directly. Okay, thank you. You're welcome.