 Thanks everyone. I'm Jeff Huang. My topic is challenges in translation team, for example, Taiwan. About me, I'm a KDE traditional Chinese translator. Yeah, and a chocolate, chocolate news picture. And LibreVis, also traditional Chinese native language project member, and the TDF member. And I'm also translate XFC and MAT. And the next one. This is my community. This is localization Taiwan, L10N Taiwan. And that is our local. And you can, this is a lion, but it's in Taiwan style. And this is my, this is our GitHub organization. We can see it has 13 members, but not all active. Yeah, and only about two or three are active. So, yeah, we are relaxed of main power. And this is our body source site. Not so active, but yeah, just that. Okay, finally, we can talk about KDE. Yeah, first, we can see our L10N.KDE. We can see L10N.KDE.org. Yeah, and L10N.genome.org. We can see that's not so, not so many difference in its UI. But genomes, you can upload translation file direct into, direct using web UI. Yeah, and the next one, we can see how to, how to update our translation. Yeah, we can see like XFCE and the MAT, they use TransFax. TransFax is a translation platform based on web. And LXQT and LXDE use Puto. It can, it can host yourself. Yeah, and the next one, we are KDE Taiwan and that is KDE China. They use CloudIn managing their translation recently. But yeah, so they use CloudIn, but they still need some process to make translation file to let KDE use. And this is weblet. It's also like, it's such as like Puto. Yeah, you can, you also can host yourself. And the next one, what branch should I submit? Yeah, Genome and KDE, yeah, again. And Genome has, you can see L10n.genome.org. They have every major version in different branch. You can see just a 3, 3.25, 22 and 24. Yeah, in different branch. You can see each branch like this. But KDE, we just have trunk and stable. And recently we have LTS, Norton support branch. But I think it's not clear of different group like frameworks. We know it is use trunk branch. And the applications, we use both trunk and stable, but trunk for master branch in Git. And stable for like, now it should be 17, 17.04. Yeah, it should be. Plasma, Plasma use all these branches. And we even have playground and extract gear. But we don't know how upstream we'll use them and use host branch. Because we have trunk, we have stable, we have Norton support. But in different group, we use different branch. And it's not, I don't know, conclusions. I think we should at least make a web UI like Genome, or XFC, or MAT, or LSQT. Yeah, we can direct use web UI to upload translation. And it is easier for beginners. And furthermore, we can even switch to the weblet or puto. You can host it yourself. Lo, it should be processed. But I think we can use them and we can make translators life easier. Thanks for your listening. Thanks, Jeff. We have time for just one question. Any question? It's a comment because some of the topics were touched in my talk previously. So about which branch is tracked by what I understand it can be confusing. Sometimes we send out the email which says, hey, we moved this branch to track these master or applications or whatever it is. One solution for that is to use Summit, which puts together all the branches in one file. So you just have one branch to translate and you don't have to care which one. About the web UI and about Genome, even in one of my slides, I said one of the possible solutions for our website is to switch to Dumnet Lies, which is the infrastructure used by Genome. And about puto, another tool. As discussed many times, there is a list of requirements that must be fulfilled. And there is a shortage of manpower. So when someone will come out with a working demo which works in our environment, then it's fine. It will be set up and working. But we need someone to do the work. That's it.