OK, welcome to the translations everyone. We will have nice talks from different points
of you at translations. This bedroom would like to showcase that no matter your field of
skills, no matter if you are a developer or an end user. Translations are a great way to
influence the adaptation of your project to make it welcome. To make it better for everyone
and to actually change something if you want to contribute. So my kick of talk will just
showcase some ideas and then with following talks, you will see how some things can
be done. If you were yesterday or on my lightning lightning talk, don't worry, this one is
kind. I'm not going to be renting about anything here. Basically, an open source usually
have tools for everything you need. If there is a tool that fills most of your needs, it's
quite a good idea to add up to that tool and just add more features to that than inventing
a complete new tool that applies to translation software. It applies to many other software
and that also applies to translation file formats. Make it easy for everyone involved
is very connected to not inventing solutions that are already there. Good thing is to use sustainable
solutions to be sure that once you are building the community, you can keep that community
you won't be priced out away from your community of translators you build and you can just
create the features, the things you are missing. You can work on what you really need, not
on those things that are already done. Just like a bit differently than you would like to see.
You will hear more about it in Nikostov, how to bridge the gap between Weblight and Workpress
at 1510. Then important part for translations is to make it easy for everyone. Yes, let's
say you are developer and you want to make it easy for you. You are just accepting poor requests
in your GitHub repository or Microsoft or GitLab repository. Well, you know, not everybody
is fluent with code hosting sites and working with Git, so make it easy for the contributors,
but still keep it easy for you as a developer or for your management team. It's a diverse set
of roles and skills in your team. You are either having or you are trying to build with your
community, so please mind everyone that's there. They don't have to do regular tasks and something
that can be solved easily. Make it easy to join localization. That's another thing. Make it
to communicate that you really accept localizations that you have the desire of the with your
project, be it a small mobile app. You have plenty of spaces where you can tell your users that you
are interested in enlarging the community and to make your software easy to start to use for
different generations for different countries all around the world and so on. So make it easy to
contribute and even if you have the system and it just system has the documentation. It's good
to inform your community about how to start contribute. It's good to place there a contact that
will be there for everyone who consider starting it and finding it hard.
For responsibility to your community is important. If you want to do the translations,
it's not one time think. You should keep it up, look after your community. That might be mentioned
in Diana's talk at 345. Then there is important part. Anybody of us sometimes is too deep
in the solution they are trying to find and they forget that there might be help in translations
in how to integrate one tool with other things and there is also machines that can help you.
It's quite popular these days. You shouldn't let them let those machines do all the translations
stuff but consider when it makes sense and some will talk about that how to properly use
and get benefits of the machine translation at 140. And that is important part to communicate
with your community because if you let people to translate your software and you just
give them things in the change lock, what's in it for them? They already localized the up.
Are they going to stay to do it for future versions? Are they really feeling connected?
Do they know what's happening inside our project? If they don't, if you don't
keep them in the loop, they will probably find something interesting elsewhere and contribute
with their work in other projects. And then it's important to share stories not just to build
your community but also inspire other communities on how your project, how your efforts came
in good and made people happy and bring them closer to its users and because storytelling,
sharing stories is motivating. Bogot will share his story about how he localizes for a long time
Thunderboat at 250 and then we have the last part. We have the translations and are
sure that the translations are good quality. Are we sure that are actually useful? If we make
the software available in other languages, do people speak in that language using it? Do they
know about it? Or are they just having default English because that's what's the easiest and when
they set in default English in their system than all the other apps are in English? Can we
when we have the translations, are they in the quality that's comfortable? That's understandable
or that we end up with new words, nobody actually understands. Or is it partially unfinished?
So everybody opens Wikipedia page and then, oh, that's just partial. I'll go back to English
or other big language. Susan will talk about that at Forten and Steven will talk about grammar.
So yeah, and it shouldn't be a boring topic as he described in the proposal. And then when
you have the community, when you have the translations, there are something you shouldn't do.
Like translate names of your product because if you translate the name of your app, then in multiple
countries around the world, you might have communities that are not talking to each other because
they don't know they are using the same software. It has the same or similar icon but can anybody
really tell the difference between multiple icons with the same color or are they using
quite similar software? Oh, that's the same software and you couldn't even find it in your
own system that happens as well when you translate something that shouldn't be localized at all.
You fragment your community. And last, it's impossible to that if you contribute, if you
put the effort no matter from what field you come to to the project, if you are a developer,
if you are translate, if you are managing the effort, if you are taking care about the community
and informing everyone, to have fun to see what you get out of the efforts and having fun should
be related to Lucas talk about how they localize and taking away the difficulties of understanding
foreign language in Luonti in a game. So that will be the last talk to finish a long conference
in a hot room. There are a few people from Weblight in this room that's just to mention that
we try to to organize this. This is me. I'm Benjamin. You can have questions. We still have time
for the questions. We have plenty of times of the questions. So we can maybe
take some and some will be talking about his practice with automatic translation in on
much most projects. So, are there any questions at the moment? I go on.
I think sadly we have to close the door to hear each other.
So, the question, if I hear it well, was, come on in. Broken AC1 stuff us.
So, the question was about machine translation with multiple languages. Can you repeat that please?
That doesn't take much time for a similar real-time use case. What else is something like
that or something similar to the philosophy? So, not certain machine translation from English
to other sources, but from other sources in two English. From multiple sources, I'm not sure
what some will know and historic that's coming out. Is it going to be discussed this way? The other way
then that's you usual.
Okay. Emily has this.
Sorry, can I use it as an idea on this one?
Okay. So, the question, the topic we are currently discussing is that the dev room is called
translations and it's more about localizing software, but you probably would like to have
a solution to make the whole internet in a different language is easy to understand in a one language
and have a no-gift, a browser like it was suggested that there is a local translations
possible within the browser, but you would like to have an API or a server that you ask for
translations, not for one topic, into from multiple languages, but from different topics in different
languages into English so we can understand it. There is not a talk about that.
Do we still have more than five minutes time?
Okay. You can start now if you want.
There are two, yeah, go on.
What any settings do you see in the translation ecosystem that makes you feel optimistic about the
future of translation in the open-source ecosystem or what are the things that you see that
scares you about what we do in translation. Can you finish on a little bit of your insight as
someone is walking in looking at it? Yeah, so the question is that if we can
inspire us in weblight or working with translations all the time, in the world of localization,
what inspires and what scares us? What scares us is easier to answer and that's not AI that it will take
our job. That's not going to happen anytime soon, but people relying on big models that are
getting not just proposed by some companies but basically pushed by other companies and that's
some of the users and users are just now I'm a translator just because they are using any big language
model or companies that are saying, okay, I will solve everything for me, it will do the
full translation. Yes, that's what was set years ago about machine translations like a good
translate, you could take a widget, put it in your website, it's technically translated but is it
really properly translated? Here we are in this in this place once more that we have a technology
that's promised or market it as it will solve for your issues, you will just put it there
get locked in sometimes and it's not providing the outcome. We are not losing weblight users,
projects using the library for localization to some big model but we have options to integrate these
models into a weblight so it's a good helper but what scares me is that people see those models
as solution which is not true and they are damaging their long time efforts with that and losing
their or losing given away they can still use it but there are sometimes given away
their long time build efforts in terms of translation memory and stuff. What inspires us or me personally
is seeing room full of people or nearly full of people no matter it's awfully hot here
wanting to talk about translation wanting to listen of different success theories
and every time I'm on any event I can see that people are happy that they are able to
contribute to their favorite project no matter they are not very technically skillful so
making, making translations is a way to contribute to something to make your
whatever you like more accessible and anybody can do it. You don't have to you can learn a new language
and localize into that but seeing either new translators that got amazed that they can do that
easily because their project started using a translation management system that made that
possibilities for the technically lineman. He was available and seeing people translating
some big projects like LeBro face four tens of years and getting new features that's
I didn't happen yesterday work because it's easy they can do more yeah that's what inspires me
and makes me happy and that there is a big community seeing that translating software it's not
about just making people be able to making the software so the people are able to use it
but I actually enjoy it and choosing the software that they feel it's there they they're happy
using it and sometimes the translation can do the tipping point between one and the other project
that one is sort of a localized so yeah it's more convenient and nice to feel at home even though
you might live be living in abroad that you have your computer that's talking to you in your
own language and all the software and you can change it so yeah that's inspiring