WEBVTT 00:00.000 --> 00:14.000 OK, welcome to the translations everyone. We will have nice talks from different points 00:14.000 --> 00:20.280 of you at translations. This bedroom would like to showcase that no matter your field of 00:20.280 --> 00:27.000 skills, no matter if you are a developer or an end user. Translations are a great way to 00:27.000 --> 00:38.000 influence the adaptation of your project to make it welcome. To make it better for everyone 00:38.000 --> 00:49.280 and to actually change something if you want to contribute. So my kick of talk will just 00:49.280 --> 00:57.600 showcase some ideas and then with following talks, you will see how some things can 00:57.600 --> 01:02.600 be done. If you were yesterday or on my lightning lightning talk, don't worry, this one is 01:02.600 --> 01:11.040 kind. I'm not going to be renting about anything here. Basically, an open source usually 01:11.040 --> 01:18.240 have tools for everything you need. If there is a tool that fills most of your needs, it's 01:18.240 --> 01:26.920 quite a good idea to add up to that tool and just add more features to that than inventing 01:26.920 --> 01:32.320 a complete new tool that applies to translation software. It applies to many other software 01:32.320 --> 01:39.000 and that also applies to translation file formats. Make it easy for everyone involved 01:39.080 --> 01:48.920 is very connected to not inventing solutions that are already there. Good thing is to use sustainable 01:48.920 --> 01:56.400 solutions to be sure that once you are building the community, you can keep that community 01:56.400 --> 02:04.000 you won't be priced out away from your community of translators you build and you can just 02:04.080 --> 02:10.160 create the features, the things you are missing. You can work on what you really need, not 02:10.160 --> 02:14.800 on those things that are already done. Just like a bit differently than you would like to see. 02:16.240 --> 02:23.200 You will hear more about it in Nikostov, how to bridge the gap between Weblight and Workpress 02:24.400 --> 02:33.120 at 1510. Then important part for translations is to make it easy for everyone. Yes, let's 02:33.200 --> 02:39.200 say you are developer and you want to make it easy for you. You are just accepting poor requests 02:39.200 --> 02:48.000 in your GitHub repository or Microsoft or GitLab repository. Well, you know, not everybody 02:48.000 --> 02:54.640 is fluent with code hosting sites and working with Git, so make it easy for the contributors, 02:54.720 --> 03:02.240 but still keep it easy for you as a developer or for your management team. It's a diverse set 03:02.240 --> 03:12.880 of roles and skills in your team. You are either having or you are trying to build with your 03:12.880 --> 03:23.840 community, so please mind everyone that's there. They don't have to do regular tasks and something 03:23.840 --> 03:33.360 that can be solved easily. Make it easy to join localization. That's another thing. Make it 03:34.320 --> 03:42.000 to communicate that you really accept localizations that you have the desire of the with your 03:42.000 --> 03:50.960 project, be it a small mobile app. You have plenty of spaces where you can tell your users that you 03:51.040 --> 04:01.200 are interested in enlarging the community and to make your software easy to start to use for 04:01.200 --> 04:07.760 different generations for different countries all around the world and so on. So make it easy to 04:07.760 --> 04:12.960 contribute and even if you have the system and it just system has the documentation. It's good 04:12.960 --> 04:20.560 to inform your community about how to start contribute. It's good to place there a contact that 04:20.640 --> 04:26.240 will be there for everyone who consider starting it and finding it hard. 04:27.760 --> 04:36.240 For responsibility to your community is important. If you want to do the translations, 04:36.240 --> 04:45.600 it's not one time think. You should keep it up, look after your community. That might be mentioned 04:45.600 --> 04:56.160 in Diana's talk at 345. Then there is important part. Anybody of us sometimes is too deep 04:56.160 --> 05:04.480 in the solution they are trying to find and they forget that there might be help in translations 05:04.480 --> 05:13.520 in how to integrate one tool with other things and there is also machines that can help you. 05:13.520 --> 05:19.120 It's quite popular these days. You shouldn't let them let those machines do all the translations 05:19.120 --> 05:28.160 stuff but consider when it makes sense and some will talk about that how to properly use 05:28.880 --> 05:37.920 and get benefits of the machine translation at 140. And that is important part to communicate 05:38.480 --> 05:45.920 with your community because if you let people to translate your software and you just 05:45.920 --> 05:50.560 give them things in the change lock, what's in it for them? They already localized the up. 05:50.560 --> 05:58.240 Are they going to stay to do it for future versions? Are they really feeling connected? 05:59.040 --> 06:03.040 Do they know what's happening inside our project? If they don't, if you don't 06:03.920 --> 06:10.800 keep them in the loop, they will probably find something interesting elsewhere and contribute 06:10.800 --> 06:19.360 with their work in other projects. And then it's important to share stories not just to build 06:19.360 --> 06:27.760 your community but also inspire other communities on how your project, how your efforts came 06:27.760 --> 06:40.240 in good and made people happy and bring them closer to its users and because storytelling, 06:40.240 --> 06:46.720 sharing stories is motivating. Bogot will share his story about how he localizes for a long time 06:46.720 --> 06:57.840 Thunderboat at 250 and then we have the last part. We have the translations and are 06:57.840 --> 07:04.080 sure that the translations are good quality. Are we sure that are actually useful? If we make 07:04.080 --> 07:11.200 the software available in other languages, do people speak in that language using it? Do they 07:11.200 --> 07:17.280 know about it? Or are they just having default English because that's what's the easiest and when 07:17.280 --> 07:24.000 they set in default English in their system than all the other apps are in English? Can we 07:26.720 --> 07:32.560 when we have the translations, are they in the quality that's comfortable? That's understandable 07:32.560 --> 07:40.000 or that we end up with new words, nobody actually understands. Or is it partially unfinished? 07:40.000 --> 07:46.800 So everybody opens Wikipedia page and then, oh, that's just partial. I'll go back to English 07:46.800 --> 07:54.560 or other big language. Susan will talk about that at Forten and Steven will talk about grammar. 07:55.840 --> 08:06.000 So yeah, and it shouldn't be a boring topic as he described in the proposal. And then when 08:06.000 --> 08:10.400 you have the community, when you have the translations, there are something you shouldn't do. 08:10.400 --> 08:17.680 Like translate names of your product because if you translate the name of your app, then in multiple 08:17.680 --> 08:22.880 countries around the world, you might have communities that are not talking to each other because 08:22.880 --> 08:28.160 they don't know they are using the same software. It has the same or similar icon but can anybody 08:28.320 --> 08:35.680 really tell the difference between multiple icons with the same color or are they using 08:35.680 --> 08:40.560 quite similar software? Oh, that's the same software and you couldn't even find it in your 08:41.520 --> 08:47.680 own system that happens as well when you translate something that shouldn't be localized at all. 08:47.680 --> 08:53.600 You fragment your community. And last, it's impossible to that if you contribute, if you 08:53.680 --> 09:02.960 put the effort no matter from what field you come to to the project, if you are a developer, 09:02.960 --> 09:07.200 if you are translate, if you are managing the effort, if you are taking care about the community 09:07.200 --> 09:21.600 and informing everyone, to have fun to see what you get out of the efforts and having fun should 09:21.680 --> 09:29.520 be related to Lucas talk about how they localize and taking away the difficulties of understanding 09:29.520 --> 09:39.200 foreign language in Luonti in a game. So that will be the last talk to finish a long conference 09:39.200 --> 09:48.240 in a hot room. There are a few people from Weblight in this room that's just to mention that 09:48.240 --> 09:57.200 we try to to organize this. This is me. I'm Benjamin. You can have questions. We still have time 09:57.200 --> 10:02.960 for the questions. We have plenty of times of the questions. So we can maybe 10:04.480 --> 10:13.280 take some and some will be talking about his practice with automatic translation in on 10:13.280 --> 10:19.120 much most projects. So, are there any questions at the moment? I go on. 10:19.120 --> 10:46.960 I think sadly we have to close the door to hear each other. 10:49.520 --> 11:04.720 So, the question, if I hear it well, was, come on in. Broken AC1 stuff us. 11:05.920 --> 11:11.920 So, the question was about machine translation with multiple languages. Can you repeat that please? 11:20.080 --> 11:28.080 That doesn't take much time for a similar real-time use case. What else is something like 11:28.080 --> 11:35.680 that or something similar to the philosophy? So, not certain machine translation from English 11:35.680 --> 11:42.480 to other sources, but from other sources in two English. From multiple sources, I'm not sure 11:42.480 --> 11:48.640 what some will know and historic that's coming out. Is it going to be discussed this way? The other way 11:48.640 --> 11:50.640 then that's you usual. 11:59.680 --> 12:01.680 Okay. Emily has this. 12:12.800 --> 12:17.040 Sorry, can I use it as an idea on this one? 12:27.040 --> 12:40.480 Okay. So, the question, the topic we are currently discussing is that the dev room is called 12:40.480 --> 12:51.600 translations and it's more about localizing software, but you probably would like to have 12:51.600 --> 12:58.320 a solution to make the whole internet in a different language is easy to understand in a one language 12:59.200 --> 13:05.760 and have a no-gift, a browser like it was suggested that there is a local translations 13:06.640 --> 13:14.480 possible within the browser, but you would like to have an API or a server that you ask for 13:14.480 --> 13:22.800 translations, not for one topic, into from multiple languages, but from different topics in different 13:22.800 --> 13:27.760 languages into English so we can understand it. There is not a talk about that. 13:28.400 --> 13:35.200 Do we still have more than five minutes time? 13:35.200 --> 13:37.920 Okay. You can start now if you want. 13:37.920 --> 13:41.520 There are two, yeah, go on. 13:41.520 --> 13:52.000 What any settings do you see in the translation ecosystem that makes you feel optimistic about the 13:52.000 --> 13:58.480 future of translation in the open-source ecosystem or what are the things that you see that 13:59.200 --> 14:06.080 scares you about what we do in translation. Can you finish on a little bit of your insight as 14:06.720 --> 14:12.240 someone is walking in looking at it? Yeah, so the question is that if we can 14:13.200 --> 14:22.480 inspire us in weblight or working with translations all the time, in the world of localization, 14:22.480 --> 14:33.680 what inspires and what scares us? What scares us is easier to answer and that's not AI that it will take 14:33.680 --> 14:46.080 our job. That's not going to happen anytime soon, but people relying on big models that are 14:46.080 --> 14:54.160 getting not just proposed by some companies but basically pushed by other companies and that's 14:54.160 --> 15:02.800 some of the users and users are just now I'm a translator just because they are using any big language 15:02.880 --> 15:12.880 model or companies that are saying, okay, I will solve everything for me, it will do the 15:12.880 --> 15:23.040 full translation. Yes, that's what was set years ago about machine translations like a good 15:23.040 --> 15:30.720 translate, you could take a widget, put it in your website, it's technically translated but is it 15:30.800 --> 15:40.640 really properly translated? Here we are in this in this place once more that we have a technology 15:41.440 --> 15:47.520 that's promised or market it as it will solve for your issues, you will just put it there 15:48.720 --> 15:58.640 get locked in sometimes and it's not providing the outcome. We are not losing weblight users, 15:58.720 --> 16:10.720 projects using the library for localization to some big model but we have options to integrate these 16:10.720 --> 16:18.720 models into a weblight so it's a good helper but what scares me is that people see those models 16:18.720 --> 16:26.720 as solution which is not true and they are damaging their long time efforts with that and losing 16:27.680 --> 16:33.760 their or losing given away they can still use it but there are sometimes given away 16:33.760 --> 16:43.200 their long time build efforts in terms of translation memory and stuff. What inspires us or me personally 16:43.200 --> 16:50.160 is seeing room full of people or nearly full of people no matter it's awfully hot here 16:51.120 --> 16:55.200 wanting to talk about translation wanting to listen of different success theories 16:56.640 --> 17:07.280 and every time I'm on any event I can see that people are happy that they are able to 17:07.280 --> 17:13.440 contribute to their favorite project no matter they are not very technically skillful so 17:13.600 --> 17:23.360 making, making translations is a way to contribute to something to make your 17:25.520 --> 17:33.120 whatever you like more accessible and anybody can do it. You don't have to you can learn a new language 17:33.120 --> 17:42.000 and localize into that but seeing either new translators that got amazed that they can do that 17:42.960 --> 17:48.880 easily because their project started using a translation management system that made that 17:49.760 --> 18:03.520 possibilities for the technically lineman. He was available and seeing people translating 18:03.600 --> 18:12.160 some big projects like LeBro face four tens of years and getting new features that's 18:12.160 --> 18:18.160 I didn't happen yesterday work because it's easy they can do more yeah that's what inspires me 18:18.160 --> 18:30.560 and makes me happy and that there is a big community seeing that translating software it's not 18:30.560 --> 18:39.040 about just making people be able to making the software so the people are able to use it 18:39.040 --> 18:48.000 but I actually enjoy it and choosing the software that they feel it's there they they're happy 18:48.000 --> 18:56.480 using it and sometimes the translation can do the tipping point between one and the other project 18:56.480 --> 19:03.040 that one is sort of a localized so yeah it's more convenient and nice to feel at home even though 19:03.040 --> 19:10.880 you might live be living in abroad that you have your computer that's talking to you in your 19:10.880 --> 19:15.440 own language and all the software and you can change it so yeah that's inspiring