 Okay, so let me start with this buff, with some explaining that Ovaishino Ritada is unfortunately not here today because he had other consequences. So, unfortunately he's not here, but he has simply some questions, and he's currently online on IRC, watching us in Japan. He has a lot of questions for the other teams, because we have many problems in Japanese translation teams, and we would like to know much about the best practices that the French teams have gone through, and other teams have gone through, and maybe other teams can learn from it. Okay, so the main situation with currently the Japanese translation team is that we are doing translation with a mailing list. We have mailing lists where people talk translations and submit to the BTS on other things, and they are sometimes reviewed, sometimes not, and they are reviewed on a mailing list, and they are sent down to the mailing list. What's the problem is that the review is sometimes thorough, sometimes not, and it's not really easy to tell whether it was a thorough review or not. How much review you have to go through, you have to go through the mailing list to check. So, for this information, it's not really tracked. So we're kind of feeling that Japanese translation is not getting enough reviews, and it's not really easy to track how much review is done. So, how do you do that? I think LUTO have a model to manage revisions. LUTO is called to have a model for this. I'm not completely sure that it's already implemented. So, it's under the roadmap. Now you can make suggestions, and you can review one person or some person can use it. There is a constant of suggestions and a concept of commit. So, this is something we don't have in the process of... with the mailing list where someone translates, good or bad, no one knows, and other people make reviews in public. That's one of the main points, I think, doing review in public. Because if someone... OK, I spoke slowly enough. If someone makes a stupid suggestion, it has to be seen by others. So, not only the review should review the translation, but the review should review the reviews. OK? Do you get it? Yeah, it's very important that some people... And this is more or less what I'm doing in the French team. Just spot the review and say, hey, no, don't suggest this. This is not a good idea. This is not the way we usually translate this. OK? But tracking the review, how many reviews are needed? I can't say. Basically, I think that more or less conscientiously, that this is a strange word, conscientious without knowing what to do. When the translator is someone well known, the review is less stored. And when the translator is a well-known one, someone we know more or less that he or she is doing a good job, well, when it comes to me, actually, I just overread the things and say, OK, some spare. Just check the spelling and whatever. So I think there is a kind of informal rating of people, but nothing written. Just the newbies will be a little bit more careful because they will make the mistakes we all made. But nothing really... I know that speaking in the name of the French team, we have the reputation of very complicated and very detailed processes. This is not completely true. So you don't have a very complex process in the French team? We do have a complex process. When something is to be translated, we post a message to the list with a kind of standard subject. Translation, T-A-F. Translation to do means in French. And then someone says, OK, I want to translate this, so intent to translate. This is a well-known process and other teams use it. And then someone picks up the translation, you can translate, and then does translation and posts a request for review. And then people review. And here it stops being formalized. There can be 10 reviews. There can be one or no review at all. And at some moment the translator by himself has to decide, OK, then last change four comments, and then I send the translation. So you send the translation? The translator, always the translator. Not some kind of detective of the team who does everything. The translator. This is the translator's duty. But no one in the team says to him, OK, go. It's hard to decide. I don't know about the Brazilian-Portuguese team. The Brazilian-Portuguese team is the same for two years. Basically the French team. The Dutch team is using, the Spanish team is using. I'll tell you it's not the same robot, but it's the same. It's the same workflow. Romanian, so now. There are some things that's impossible, right? We have one translator doing everything. The small team, they just can't do anything but just translate. I have no solution to this. Being a team of volunteers, it's very hard to say we have no, and I don't know of any team having an assignment process. Say, OK, there's something to do. I'm the boss and I give it to you. It's completely voluntary. If I post a translation to do somewhere, well, it has to wait until someone picks it up. OK. That's interesting. Do you have a comment? Have sense to make the same workflow for every team? Separately the small teams. The small teams, which one person has no sense to make a workflow, but use the same workflow. Use and do-do. Is the workflow, do you mean inside Google or at any time? I mean proceed. A way to work similarly. In fact, the workflow is open. It is curious because you don't have it written anywhere, so usually teams that are looking for some organization starts looking for other teams. That's the way that happens in Portugal. And I found these strange tags in the French team that they have with staff, RFR. And I started asking people. And somebody said, look, read this document. And there is an HTML that explains the workflow, but it's not well known. And it's up to you. You just need to start using, and you can activate the robots that sends that on the maintenance. So the workflow is based on a page that is generated hourly with who owns a translation or a review or whatever. This is outside of Google. I think we should... It's testing for now. Sorry? Now maybe we will change the future. I think it should be useful to integrate all the tools because in this way there are more tools separated between each other and should be integrated. And if the tool is not used, just remove it because it's so much confusing when you try to make the work. That's my experience about this. It's brutal and currently used. Yeah, it's used, isn't it? No. It's not easy. No, but you can do it. No one uses putty. So if you're still at stone age, maybe at each other. Not yet using any tools. Well, maybe this is a tool. Maybe it would be convenient if someone has a laptop to just show which we have tools. These robots and the like. So we do have tools. We can use your computer again? Yeah, but Grizu wants to hack. So... I can do it. And he has a damn German keyboard. Just this one. I like to use it. Mine doesn't really switch country. I don't know why. Yeah, about Junichi's question and we do have a power factory. We do have a computer, but it's not just using putty. It's very short. I don't know. Even with the young keyboard. Oh, here, this one. This one was yours? Yeah, I used it yesterday. It's got an American keyboard. Not exactly my favorite one, but... That's worse than German. Okay, thanks. Shit. If you can use the browser. I may need to get the URL. I have a quick question. Which language teams members are here? I know French. Brazilian, Portuguese. I'm not really as French as they say. We are a little bit short of official language. I can speak for the... I know about the processes of the Spanish team. More or less. Because we talked a lot with Padilla Fernández. I'm not sure about the German team. The German team uses... The German team seems to use the robot too. The robot now. I've seen that a few people popped up recently and now they use the robot. So the Catalan team more or less uses the robot also. The Japanese team uses a web page made by Kenshi Muto. And there's a manual process. The words are in the internet. You can probably use this one. You were explaining the Japanese team. The Japanese team uses a manual process. Especially for the weekend news. That was an exceptional process for the weekend news. But that was the one which was most active. When it was active. They had assignments of the searches to people. And they assigned the parts to people. And they were meant to translate it by the deadline. And that seemed to go around very well. But the weekly news is no longer weekly. So people are looking for something to translate. And what other parts are the Japanese team working on? Is this done on a team-based process or not? Well, here is done by Kenshi Muto and Yamane-san. So there's only two people working on it. And Kenshi Muto does a web page of tracking who is doing what. And Kenshi Muto does the difficult part. And Yamane-san does the easier part. So there's a very simple goal and responsibility. Anything that is a file can go under the rules. Because of the way that it was designed. So WMLs, PO files, PO.com. What else can we do? Man pages, documentation, anything can go because we use URLs. This is the PC rule, URLs. And we can do that. We can even relearn that, at least the Brazilian Portuguese team, while we are translating the policy. The policy is 2D. So a team of people was translating the policy. So to register the different chapters, you can use different URLs. So it's quite easy to use URLs to track things out manually. Yeah. We have problems. We can bring back to here. Yeah, we can. This is the problem here. Hopefully it's not. Yeah. Maybe it would be nice to show if you have a browser. Yeah. The screen really needs, this end of the screen needs to know if it's a big problem. It's okay. Yeah. Bar with your laptop, just to make sure, I think it would be more. Okay. Now, do you need to be rude? No, I don't need to be rude. I just need a browser. For working network. All right. We can show, maybe it's easier to show the process with the browser, making this and whatever. So I hope it's listening on the other side of the planet. Item.n. Item.n. Item.n. I want to show the robots first. It's on cloud. And a slash. Item.n. Dash. Okay. Everybody spotted the URL. Okay. So there is no home page or whatever. Here we see the output of the robot for all teams. Nineteens. Nineteens will use it. So I apologize in advance. I take the French part because I more or less know what's happening there. So here we see all activities. Either it's sorted by bugger code, by date, package, etc. I take it by package. So here we see first the type. Because I'm not the one using this page most. So we have a kind of coordinator who tracks this down and wakes up people when something is waiting for too long. By status is the best way. By status is the best way. By status is the workflow. Okay. Here we have the first step of the translation work. The TAF. TAF means in French translation to do. It's playing on words actually. TAF also means slang for work. So this DAF FS2. This is a... Oh, PO. Why PO? I want to show you. Let's throw PO. This DAF FS2 program. TAF PO means this is an upstream translation. So this is not the PO. It's not the main page. Just a program. Okay. The file is always named. Nearly always after PO. The TAF has been sent on 5th of March. And there is a link to the list archive. Which I put in the new card. And it just says it points to the list archive. Tomar just sent this mail. And you see the subject. It's kind of spandalized. It says DAF. Okay. See what you have to do. PO type the package. Name of the file. And 137 U. So 137 strings to translate. So if I want to pick this up, I know I have a lot of them. So this is basically talking about why no one need this. What are you talking to me? I have to talk to someone. Okay. This was the first step. See. And then we have a few others. So the coordinator. As you see. That needs kind of coordinator. Someone who watches this frequently. And you can see. Okay. I posted this on 5th of March. And no one picked up. I should maybe ring the bell. And we have to start again. This was DAF. N-A-G. Here also this is one of the acronyms. Which is French. Mise à jour update. Means update. This is the same thing. For the package name. There is a pure death confirmation. Post it on 11th of June. And if I look at it. I see. Yeah. I did post it on. Yeah. I did post it on 11th of June. And probably no one picked up. On this. Update to do. So we should break it up. Because there were nine fuzzy. And three untranslated. So small work. It should be done. But I am in depth of this. I cannot. Next step is ITT. To translate. So let's take an example. On 12th of June. Sibyl. For an unboxing. Just say. Okay. I'm okay. I will do this translation. It was like 10 days ago. It did nothing. So I should beat him. And get the translation. The text is not really relevant. Anyway. The most important is that. The ITT is on which we avoid. The application of work. You know that somebody's. I forgot to mention this. This is pretty much important. So ITT. There should be. Few things in ITT. Because. It's just temporary states. And if you look. There are many various. Different type of translation. That could be PO4A. That means. Probably. This is a big document. I think. Manuers. There are a lot of translation. DDB type. Because this is not PO. In that case. This is probably. XML. XML translation. So he posted PO. Nobody speaks French around. This is awful Spain. I don't want this translator. He said. I will do this part. I remember. I saw him and I said. Not him. Okay. There are a few such. Status. Which is. Yeah. PO. The biggest part is probably. The biggest part is probably. I never heard. RFR. RFR. Request for review. Here the acronym is. English. All things use it. Just like ITT. And we see a lot of such. Request for review. For instance. This one. Yeah. And here. And then we point to my message. My last message. With. Complete. Everything goes to the list. So. Robots. Yeah. The robot scans the mailing list. And. Generate these pages. The robot is maintained. In the. And it runs. And it runs. On the. Host. Which is named. True. True. True. For the German people. Who can. Also. Okay. The host that has been donated. By. Region of. In Spain. So. This machine already runs to a robot. And actually. The robot has only to be. Teach. That this team. For this language. Uses that mailing list. It's only they go. It's on a flag. You just say scans this mess. This list. And use this language code. Last time this was. 17. If I'm not wrong with this GMT. Or GMT was chosen. Like that. And it's already. And it. Closes the bugs in these pages. Once a day. That's another advantage. But. I will go. So if I go down. I saw the request for review. Of course, because this is work in progress. I don't remember. I think they are sorted. By date. So actually. The coordinator. No. The RFRs are by. By letter. Yeah. Because it could be easier for this coordinator. To spot. There is an option by date. There is another page. And then the coordinator. Can. Just look at all things that. Everybody forget about it. And just bring it back again. So that needs again. You see the coordinator. Someone who cares. One or two or three or whatever. I'll see. Next status is LCFC. Last. Change for comments. And this is the moment where. This is. We reviewed everybody agrees. There has been some changes or not. Or maybe not as I told. This we cannot control. Sometimes you have a huge threat. Sometimes there is nothing. And at some. Moment without. Explicit definition. Some moments. We decide. The next step. Say okay. Reactive. Correct. Then. For Brazil. Portuguese. If you have. Date. Timelines. Then. If you have no. Time. You send your translation. But if there is no timeline. You have to wait until somebody. Review at least once. The fact. The system is. Simple enough. To allow. But there is nothing to give. To track the fact. That you have. That's probably a weakness. Then. After the LCFC. The translator. Will send the report. The package. Related to a package. Example. Let's say. A user. Sent. First. It sent a bug report. With the file attached etc. So we have a link. For this bug report. So you scan the BTS as well? No. I will go for it. If it sends. It gets a bug number back. And then. It has to send. A message. To the mailing list again. To say hey. BTS. For this translation. And there is a new field. Or yeah. Which gives a bug number. You can use various options. You can use dessert. You can use sugar. That one. So this is more historical reasons. It's more logical to say. BTS column. Or whatever. BTS shop. And a bug number. That's probably more logical. For things who begin their work. It's more logical. And then. So. There are several manual operations. And. If I come back to the bug report. There is some. Non-written rule. That says. The subject should be. Kind of. Formalized or kind of. Stand out. But actually. It's not used by anything. You see the subject here. It's. And then. Column. French translation updates. It's not really used. It could be. It could be for instance. If I send. By report. And then. The robot calls. The BTS. But. But. Because here we have two manual operations. The translator has to send a bug report. He has to remember. That when he gets back the number. He has to make to the many. Otherwise. But we will see it. Because the coordinator. We see. Okay. This package is in LCFC. For a one week. This is not normal. Actually here. There are a few that are not normal. And. When. Felipe said. The robot. Scans. The BTS. And goes to take each of these bugs. Here. Just checks. Whether they are closed or not. And when they are closed. The line is removed. And. Disappears. The process is complete. So. This. Helps to track down. The bad maintainers. Who do not fix. Their bugs. At least for organization. By date. For instance. Any new campaign. For instance. There are a few. Special types. Like fix. Fix. So. The same but. The bug is fixed. One fix is. I think. Fabulous. Done. Is also special. I usually use it when I. I have commit access. Some parts. Some package development. And I directly commit. I don't send a bug report. So it's not trapped in the BTS actually. It's considered done. And hold. Is hold. Most of the time. Sees to say. We know that there is some work to do. For this package. For instance. But for whatever reason. It's not a moment. To do it. Because the maintainer said. Okay. Yeah. I bought some stuff. But I will break. Another stuff. So that's most. What. Usually when you remain. It's about the robot. French robot. Dutch robot. And live. Absolutely. Yeah. It's not a package to use. For teams who want to start their own. Process. If I. Take the Japanese team as example. That could be interesting. If. I think that. Some man for. Because you need a coordinator. Enough. Enough translators. There are only two people walking. And not sure it's really useful. I don't know. I don't know because. She mentioned. Maintaining a web page. So. It could. Maintain the web page by using the robot. That. Because. Is that what we do? It makes. It's not. One of the things that like. We have. You. About small things that. If you are only one translator. Like. You can use the robot just to track. Your. On this page. So you can just send a mail to the list. And said. BTS. But number. And it will appear. And it will be closed automatically. So you know when to. And during enemy campaigns we also. It can help also. People. The bots are are extensively. And like. You said that you assign. Different paragraphs. You can change the URL. Because for the robot. The URL is the most important thing. So once. Once you change the URL to say. Like. WML. You can use. Weekly. 50. One for paragraph one. That's that's an absolute main. You can divide it by 12 paragraphs. And you can have multiple review. Process running. That's that's the advantage. Of the road. You are. The unit of the robot. Is the subject line. It's in the format of a URL. It is type. Column. Lash. Column slash slash. Name of the package slash. Or sub directory. Or whatever it is. So it's. I assume that. Over the Arabic and Turkish. That is not. That is not in one. Can Japanese teams join this system? Or is it difficult? I think you were over. Yeah. I think that the Japanese team. Good. That wouldn't be an obstacle. You know the Arabic. He was using. It's a very small team. I'll be team actually. So. The system is not very widely used. But. It. It is more or less used. We look at. My days. A lot. Stop. You can also use this kind of. You see the URL. Using like. Regular expression. Name of the package. Package. Package. I can check with. But I'm pretty sure that. There is. If there is. Most of the. Robots. By. Write it down. Or. H. U. R. I. A. U. X. So. Because. I. I just. I think on the page. Or. Or. Yeah. Yeah. Yeah. But. Yeah. Yeah. Yeah. Plus plus. Great. What do you think? Can you read it? I think he has. The page. No. It might be useful for the people. During the stream. I have some. You have some. Okay. Anyway. You have the contact. Person doing the work. Anything. About this. Can and should. I think. I think. I think. More than. So. Yeah. Want to see the German. Okay. They. Can see the virus. Close it. Registry. Some. Yeah. Interesting. Not because. Mine. I did send. Automated. Review campaign. And. We see. For. And then. More. All. Yeah. Transform this. Request. Means it picked up the translation. Because it's probably. And then. He may be sent. Request for review. As a follower. What's interesting is. To do to use threads. Because it helps a lot. Here we see. Tom. We are in. process. Because he sent. And then. Sent. Okay. And. So. I don't know what you want to say. But. The main point being. It has to be easy to both. Read. And apply. The German. Compressed. One does not. It's up to. I think it's. Discussed at one time. It's probably some years ago already. On the. Known D. Meaningless. That. Seems to be a part within some evolution. Giants. Version that. Wasn't able to properly view. Text attachments. Which have a different. Encoding. Than the mail itself. And. Completely fucked up something. So they started using. Zipped file. Attachments. This is a. Common trick. To send. Five. To avoid encoding. This was also. Very often used by the Japanese. Because of. Messing up with encodings. Than. People opening your nicely encoded files. And breaking them down. Like. Well this is something I personally don't like very much. Because. I think that now. We are over these problems. So it makes just a little bit more. Worked. When you receive such fight. Because you are. Unzip it or whatever. Make just one more step. When you have 10 of these. It's kind of boring. So. But the main point is yeah. This person sent the leaf. And then what happens after. Can you. About the answer again. Okay. This is a. Not useful. Okay. So. No. Here in the process to discuss. Okay. There is something. You made a remark. When they. Skipped. The last chance for comments. Step. And actually jumped. Step. This is probably the. Process of. Yeah. When I already choose. The. This process is an agreement that. When there is a correction. A correction. Somewhere. You use LCFC. When the review everybody says that's okay. Go ahead like three or four times. There is no need for. Last chance for time. But again it's working in Brazilian Portuguese. Probably. Yeah. Use. Then. Send. Okay. This has to be translated. This is an update. Not a new. Then. Then. A few days later request for you. A few. More or less. This one. Okay. It says there's a typo somewhere in the. So even. He didn't send anything. Because it was completely obvious. Yes. And. Finally. Some moments. Last chance for comments. With encoding. Problems. Whatever. Yeah. Yeah. And maybe. There has been some comments. And. No. That's interesting. Data dates. LCFC. It was May 2nd. May 2nd. Last chance for comments. Then nothing happened. And our beloved. Coordinator. 26. So. Three weeks after. Just look at the robot page. And say oh. What's happening. And it says. It just says. Okay. And then. We are. One day after. Okay. So. He has reviewed. The transition. With the. Energy and emotion that. Which is not. True. Anyway. These days we have a lot if you see. This is only May. And we have a lot. Of threads. Each one of these threads. And if I look very carefully. I certainly find. You are. That. LCFC. And nothing happens. No one. Just given. This is. Not the best. The best we can do. Some teams. Have the robot receiving the emails. That's slightly different. There is only the Dutch. So. They have many. East. But they use. Right. Yeah. I think it's. Yeah. This is basically the same. But they use. My SQL. My SQL database. And the robot has. So. Does not. They send them to the robot. And the robot. Keeps tracking on that. And you say they. Because. Yeah. Yeah. I can see four names. I'm not sure. About their color. Colts. Conventions. Probably. Seems to be related. It's pretty much like ours. Yeah. RFRs. Yes. One looks at the. They have all the discussions. Yeah, only discussion. You have the RFA. LCFC. And then it stops. But that probably depends on. Various. We must discuss. And he said that. We can have that also on our robot. There is no problem. And actually eventually. You. Merge everything to one single point. Because it's easier for everyone. What to say more about. QA. I know if he has other topics. So what. Where does. Come to this picture. No way. Okay. No way. Photo. It's currently outside. It's considered to be. Experimental. Stuff. Artinens.dbm.net. Column 8080. The main point currently. It's saving. This is the experimental server. Don't waste. If I take. Something like. It's. What we need to see. At the moment is. How to. Interface. Put on and the material. So the main point can be. Try to automate. The import of the material. Into put on. Then. Take care of what to do. Question about this. So. We have the main list now. So we send. By touch. Is the. To view them. Is there any to. Facilities that we use. Checking. Is that. Overcoming. To answer. Who does. Over there. You do. Time to. How do you do it. I. I. Depends completely on. What kind of translation I do review. I. Often review. Also upstream things. I'm. The best not on the game. Translation team and do. Review the pao files. Directly there. Mark into the file up until where. I. Review it at the time because I don't. Have. The time to go through one file. Completely because they are huge. Um. Well. Really. I have found my own workflow for doing it. And I'm. Sending. Badges of. Updates. The complete file but. After some. Some stages I did. The review I send it on. Something that. Work. More. Like. Something like that. Probably. Maybe. To. This is one of the main. Things I want to get in a word. This. I like the way that the. Is doing it with the review system. Um. And more or less. This is the only thing where I really. See that review. Is part of the workflow and is really. Done. I don't see you refuse. Done in very much other areas. To some degree. My complete system is switched to. German so. You can. Take that as part of review too. Because I'm usually sending in. Problems when I notice them. My system. So. Review is that using the system you will notice. So that's one review. I mean you can review the role. Be all essential data. But that's sometimes big. So. Is there any tools to facilitate. Looking at the files except for. Using. Whatever. Yes. There are a couple of different. For. Stuff. That runs. Under. Right. Will also does that. Which is checking for parentheses. Checking for variable names. Checking for. Spell check. Spell check. For language that wants to enable that. That. Happens on the. There are. Just checking and you can go to a page and see all. Brazilian Portuguese has. For. Broken names because probably. We don't spot the there is a change. That we didn't see or it's just a title. So it can. Hunt it. And there is also a spell checking. Words that they can't find. And. Who does that. When we import. He. Does checks like. Number of parentheses in the message. Like you have four parentheses. So the translation doesn't have four parentheses. It's broken. And there's a lot of other kind of checks in this way. For. For vi. And this is basically what I use. And I know that Nicola. Also is using vi. I use a spell checker inside vi. Which makes the. Work easier. I don't need to look for spell checking. Which means big. Focus on translation. And now we have the companions. Which in some. Graphical tools it works off the box. In the case of vi we need to merge. Before starting translating. So you get the companion. You get the new PO. You merge it. And then you start translating. So what he finds in the companion. That's translated. At this point. How do you get the companion. To work. To work on the tools. I really don't know. Because I don't use graphical tools. But usually they like cable bell has a few. For companions. You get the file and you say to cable bell. Here is the companion. But it seems that Eddie is the only one. That is able to do the companion. To work on cable bell. I can't. That's the mainly. That's the mainly key tools. That I know. Vi has some nice tools. For the translations. But we are not using that. Overall. Overall our kind. Not yet. I press before review. Actually I just open the file. And agree. Change it. And where all this is being wrapped. Into a script. That first copy the file. That is the original file. Then I open in an. Emacs. And then modify. What I consider to be. To be changed. And then the script creates a deep file. The point is sending the deep file. So that you can see the original. And. Modify. Because the important thing is to use a rule. It's an informal rule. Every time that our review happens. You should send. The new file. The deep from the read. And the reasons. For your change. Not only because we have translators like. Just sending the new translation. So what have you. Translate. What have you changed. That there is a need to regenerate the deeps. With the deep. And the new P.O. If the translator accepts everything. It's easier. To just say ok I accept everything. Less chances for comments. And also I explain. I fix a typo. Or I fix. That's not the best way to translate that. In Brazil we use a standard vocabulary. From the Brazilian. Linux documentation. Project. Because you want to keep the consistency. With the rest of the translations. Most of them are using this. But I don't know if it's using other languages. Actually. We're pretty. Bad. As far as I know. Are only. To. These are our memories. Which is not. Very good. And we are talking about very. Different size things. That's another. We have things in that. And that's really only one person. We are not kidding. They are doing much more job than. Some of the things that have 5-6 people. And we have the French teams. That there are. With like 20 people working. Depends on the moment. More or less. It's usually like 20 years. Largest teams have like 20-25 people. Working on sometimes. I have a question about. Your files. If you. Sent your files through message merge. You would change this. So you have problems with this. Are you. Carefully not to send this. Or how to go around here. Message merge with some options. Smart mix with the. Ideas. Yeah. This is mostly related to the. Various versions of get text. Get text change a lot. It's default behavior. Not. From version to version. So yeah. Sometimes when you're not careful enough. You can just. Completely. Find. What we recommend. Especially with the. Dimension where I just. And then. I usually recommend to not. Change the wrapping. And not send. The file. To message cats for instance. We format. That's important. I think that during the. The. Layout. Should not be changed. Make easier to spot. Really. We try to keep it rapid. To make lines. Yeah. I learned that. That should be done. When I am when I send a bug report. I do it with a script. I just go to the directory. And I send. A bug. Update. The package. There is first a message cat. The file. The very. The last step. In the review process. It's better to not change the layout. And. For the review process to happen. The PO files. Must. Be. Very long. Like. Yeah. When you say. It says. With. One nine. It makes. Yeah. Forget about. Format. To use. Yeah. I do. I do. I do. Is that music? Me too. Is that useful to use kebab? Yes. In my opinion. Yes. Because I use it so. Isn't. What do you think of the. Project I can't remember the name. Start with it. And four letters. In four letters. And it. Puts everything out as an object. So you don't have the whole file. You only have the department. Exxl. This is exxl format. What? Exxl. Exxl. Exxl. That's not the one I was thinking about. But anyway. When you. When you. Talk about the file. Are you taking the whole file with the. All of the C plus plus or. Python or whatever code. And. And translating that or. You just translating the. You're only translating the part that's. The. The user sees. But. But is that in a separate place? This is. This is the PO file. The PO file. This is all what's around. Get text software. Which extracts. Translatable strings. Which are marked for translation. And then puts them in a. Dedicated file. Where you have the original. Original strings. And then. Translations. You can use special tools. Like. But also. Just text. For instance. You have a. That you can. Use some special combination. Call strings. Go for the next. To find the next. There is a. Max. I think. Processing Japanese. Sometimes. I can't remember which one. So we really have for Japanese. Is. Or. Some people use. To edit. To edit. To edit. To edit. To edit. It's quite good tool recently. It has. New features by. Get text. I don't have. The recent version of get text. When. You find a message. Message merge. And. Because the strings. Change. The former string is kept. As a comment. With. A. Sharp pipe. And. And. Doesn't cope very well with this thing. Because. The comments are the top of the blocks. Which is not. There is a. A. Against. Because it completely breaks. To fight. Apart from that. Is a lighter than. It is still. The advantage of these tools. You see. The original. Fine. And the translation. Below together. And there are internal checks. Like. Of course. Also. Variable checking and the like. Well actually you can use. Bull. Sometimes. So. Exactly. You can have. Yeah. There's a. For the. Improve. For. That's. Useful. It has. To jump. To the next. And you can even. When you're in the. When you have the complete sources. You can also open. The place where this string was defined. So you. Can look around in the source if you. Are. Unfamilar with how this string might be really used. In that place. So you can look at that one too. I just sent. And. Message to the. Container of that script. That he adds. Support for this new get text. Previous. Thing so. Might be possible. Soon. To get. The previous and the current. Original string. For those. Yeah. Showing a different both would be very. Yes. Message ID. To the. Of the message ID. If a string is marked fuzzy. It's you. It's done because the message ID. That's currently there for the screen. Is similar to a previous translated. Message string. And if you can. Get. Between those two strings. It would be immensely useful. Because you see what really has changed. And not only see the new string. And have to figure out yourself. If there was something changed. And I send a message to. I made this morning. To the. Maintainers. To. So he can add a new. Keyboard shortcuts. To. Just get the tip of those. Strings. Yeah. That would be interesting. Nicholas asked me. In one of the. I 18N sessions. Yeah. That would be useful. Keyboard has nothing. You just see. Former transaction. But you have to guess what has changed. Exactly. Better than before. Before you had just a fuzzy. No idea of what changed. And this is a user. Line of. I would like to find what. Change. The tools can be still in post. What to do with the tools. And we know there's. Problems. We have the web interface. And we have the editor so. Well. I think when it comes. All these. Processes. All the work we're currently. Doing on the. Put observer. Is the place. To improve. All this. That's where it has to go on. And I think. This is mostly not thinking. Deeper about processes. Is mostly. What is. Kind of. Missing. Of. Of. Because the tool is here is very nice. Is. Flashy and. Very easy to use. But. As far as I know. There are no. Processes behind. So. Anyone can jump and say. I'm. Georgian and I speak Georgian. Very well. Okay. Comments. Okay. This goes to. Direct. It does not. We are. When it comes. These things. Better to be slow. Than to do things. To hastily. Organize. Two years ago. Two. Each. Its own. Now we have. Maybe. The chaos. Organized. And. There will be. Anyway. Yeah. Yeah. We are most. Cooperation. Between. Consonants. Discuss. Well. Question. What are the places you think. That you want to improve. Working on this. Question. Question. We have been discussing that. Since. Christian probably has. Been discussing that. Much more. Than. Since that. We have. Defined some process. Some work. Some. Assumptions that. We must have some things. We need to have orders. We really would like to have. Another. Moving some things in the direction. That we want. Yesterday we still find some critical things. That. Are not working exactly like we want. I think. I think that. One of the things. That needs improvement. We will work on that. That's consensus during. Documentation. We need to spread some information. So we. Doesn't know about the robots. Doesn't know about how they work. What they do. They don't seem to remember. That we now have. An I18N server. That should be used. So. I think that. Things that we need. Need improvement. Some documentation. And the whole. Of what we are doing. Needs. To achieve what we really want them. To do. But that really needs coordination. With people. That we learn in the past. That there is not just. Pop up. Write something. And tries to force people to. Merge. Do not work that way. It needs to come from. Working. How. Do you think there are some other topics. Things. One of the things that there is. Is not. There is no problem that from time to time appears. Is that. Why we are building the consensus of being a team. We still have the. Afraid of being a team. Sometimes. That's why we look to the I18N. We can you see that we. Start by calling. The Knights of. Because that way nobody will complain. Because that way nobody will complain. But. We really. Want to. Have more visibility. Of. Being working on key. And having people doing coordination. Now. Inside the I18N. We don't say me. We say. How do you choose the name. Nicky Nicky. It's a. All day. It's the same guys that. Give names to this fund. The. They have one. So. The Knights of. Yeah. Because they said. We. We talk too much. In the translation stuff. So we say. Nicky Nicky wiki. For. For. Yeah. Stupid jokes. Yes. You should zoom on. Interesting. Which is. You know. He has a lot of work to do. No. I think he has. I don't know. I'm not. Time or whatever. 535. I think you have more. 10 minutes. 10 minutes. It's not. Good. Good enough. You know. You know. You know. I'm. For. We have discussed. Yeah. Maybe. Maybe. Do. Thank you. It's very nice to have. All of you. And. The Japanese. It's so nice. You have. He's probably not, because it's 1am, he's already asleep. Without this meeting, I don't think we really saw the value of IT and the robots are useful. Yeah, it can give some more publicity about these tools, which we should do more often, actually. I always forget to know. Yeah, thanks for proxying me with the ISE effect. Thank you very much.