Okay, Matthias and I will tell a great story about inspiring kids.
When I think of my childhood, I had two grandfathers that had a shed with a workbench.
I had a father that told me about hardware and electronics, had a mother that told me crafts
and sewing, and I think that has changed my will for you on technology.
And if you look at today, you have magical devices, but hardly any interfaces.
You can't even open up that are glued together with software that's all polished up.
So it's even harder to get started with anything chinkering hacking.
So I think it's up on us to make the effort to break through that barrier and inspire
kids for today.
And with the free software foundation Europe, I think it's very good that we have a goal for 2048,
which is ambitious to actually get kids to go on this topic.
Now the question is, how do you do that?
Well, we have something very concrete, a very concrete project, which you also can contribute.
Yeah. So in 2017, I was thinking about what can I do to tell my children,
or that they feel why it's so cool to tinker and experiment with technology and to program.
And why it was so cool for me to enter the free software community and share knowledge with others,
learn from others, how can I explain them this whole area of where I'm involved in?
And so I did what I was used to do at the times I wrote an email to mailing this
and asked if there are any resources out there, how I can teach my children, what is free software,
what is software, what is hardware, I don't expect it or something, what is free software.
But yeah, how to introduce them to this and how to get the spark, some interest to tinker with technology.
And yeah, there was not that much that came back there.
And so what I did then was I invented some bedtime stories.
So in the evening, before they had invented bed, I thought about what happened during the day,
or during the week and invented some stories with things devices they saw with things that happened during the days.
And it's always something about computer software, something.
And the good thing with children is that they are very good Q&A.
So they give you very good feedback.
They are not, they tell you that's boring, I want to have more of this.
Why don't you include that anymore?
And so over the time they developed the story.
And then there was a time when I met one of the FSF installers and we talked about different projects for the future.
And many different things came up there also for example, you're taking for freedom, our coding competition for teenagers.
And at the end he asked like anything else, you plan to do in the future.
And I said like, yeah, maybe I might write a children's book about free software.
And he said like, if you do this, I will buy 1000 copies and we will give that to our customers.
And then I said, okay, I need to start.
So until now all the stuff was in my head of what I did then was I wrote down the story.
Pencil paper and started to write that down.
And then I also got a agreement from the Free Software Foundation Europe that I could get a children's book editor.
And send it to her and see about the feedback is something just my children like or is that something with potential.
And the feedback there was quite positive.
So I got that back and then he said, okay, let's find a publisher for this and really do it as a book.
And yeah, so in this process, I already included a lot of other people.
So I send it to people at the FSF, I send it to people in the Free Software community.
They were eagerly testing the script with their children.
This one here is from a daughter of someone from Apache Foundation who could not wait for the illustrations.
And then she painted the illustrations herself, the editor.
And we included others to in many different aspects of this book.
It's wouldn't have been possible without so many help by others.
Yeah, and then it developed into a book.
And this one was the result, there were some hurdles before.
So we decided very early on, we want to do it as under Creative Commons license.
And not any Creative Commons license, but Creative Commons, by share like.
So not with the ANC edition.
And people in the publishing who know the publishing world said, that's not possible.
You will never find publishers who do that in different languages.
You will not be able to find illustrators who do that.
And yeah, it took a long time to talk, I mean, the editors that was fine,
but finding illustrators explain great common slices and it's very difficult.
And then also with the publishers, also took a long way.
But yeah, what happened?
Until then, was actually I, before I went to any other publishers,
I wrote an email to Orile in Germany and with the idea.
And I got an email back after three hours, we would like to talk.
And if I have something more, and I wrote them to scripted,
I said, oh, this looks very good.
So one day after that, another two days after the initial email,
we already had a call and the day afterwards, the CEO of the company
really said, like, we are going to publish this.
So that was the start.
Good start.
There were some hurdles afterwards with the Creative Commons licensing.
And so on, but that's how it started.
And here are all the language versions where we have printed copies already.
It's over 20,000 copies now that are in different languages out there.
One great thing that already happened very early,
because of Creative Commons licensing was here at Boston,
someone from the French Ministry of Education saw the book,
saw that it's available in a Creative Commons license.
And I didn't hear from them for a while.
And then they came back and said, oh, we now have a translation.
We had a pro-check with four schools in France, with over a hundred pupils.
And they did pro-check weeks about book and translated that in a collaborative manner
between all of them.
And yeah, now we have a translation.
And they helped to find a publisher and in the end,
even the Minister of Education in France, in a German French parliament hearing,
show the book as a good example of French German collaboration.
And yeah, so that was one thing that happened.
Before that, we had someone and there were a lot of refugee children from the Ukraine coming to Europe.
And someone said, let's have that also in Ukrainian.
And we were able to pay someone to do a translation.
And then also the lay out for the Ukrainian one and send a few thousand copies to,
organizations working with refugee children.
They told us, after a while, do you also have that in a rapid?
We have a lot of refugees from Arabic speaking countries.
We got another donation and then were able to actually also do that with 7,000 copies of Arabic.
I got a call from the head of HR in Spain.
From Volkswagen, distributed Spain.
He said, they had nothing to do with free software.
They said, we have a program to get more young women and girls involved in STEM.
And we think your book is great.
Is it also available in Spanish?
Said, no.
They tried first to find a publisher.
The publisher said, like, oh, no.
I want to have exclusivity.
That's communism.
If everyone can do whatever.
It was like, oh, that's like the free software 20 years ago.
But yeah, they did not stop.
They continued, paid someone themselves.
They did the translation.
And actually, this person here on the right side, look up on this.
Oh, he's here.
A lot of people who continue to die here.
Look, I helped them in this process.
So look, I was also one of the first ones who did the volunteer translation.
So he did the Italian translation of the book.
And with that also pulled all the translations.
We had at that time, which were text files.
Into a Git repository structure that made it possible to build something.
The outputs out of that.
And yeah, and he helped them also the Spanish ones to print a larger model of books
who then go with an electric bus with two female engineers, with three deep printers,
two different places in Spain, read the book and afterwards do a pretty printing with the girls.
And look, I helped with that and set up this repository.
And did a lot of improvements there to make it easier to do all the transitioning from text
to actually books, also did hand drawing of some of the illustrations.
The illustrator was amazed what he did there as someone who's not professionally doing that.
And yeah, but the problem was that Luca was over the time involved in lots of FFEs activities,
including one activity where he also gave a first term talk three or two or three years ago
about the Windows text refund, where he was suing Lenovo, because he didn't want to refund him
the Windows license for his laptop.
And in the end, Lenovo had to pay him 20,000 euros and fines.
And he donated that to the FFEs and other free software organizations.
And we wanted to set that up so others can also do that.
So Luca was very, very busy at that time.
And we thought, OK, he cannot set up the refund for freedom,
campaign with others and be involved with our translator team.
If he also has to do that.
And that's when the others, super hero came in.
Yeah, I might as well.
But this.
So I'm the coordinator for the FFEs in the Netherlands,
and I was, like many others, inspired by this story.
And one example that he really hit me was David Vfoy,
maybe you know from the webcomic pepper and carrot,
made this illustration that it's not just maybe a child,
this kid's book, this is badass, right?
This is inspiring.
And so we brought the English and the German edition to the info booth
that we were having in the Netherlands.
And we noticed that the book, even though it was not in Dutch,
we could talk over the illustrations.
And it really helped us explain control of a technology
and importance of it in a good way.
For example, this illustration about it's sort of in one few highlights
the power dispelence in the net of things.
So people ask us, when will there be a Dutch book?
But of course, you need to arrange something
to get a translation done.
We started translating, and in about two to three months,
we had the base text done, some back and forth.
And I, maybe now, easily assumed that look at this so much work,
with the press of a button, I would have a PDF,
I could send to the printer and get a book done.
Well, it was not so simple.
The automation at the time was that there was a custom text format
which contained the actual text, but also some specific characters
to signify which were like their chapter markers,
different pages, to deal with the parsing and finally the rendering.
And it could render to different outputs.
So scribers, given this is a desktop publishing application,
you can use to get a file that can be sent to a printer,
that takes care of embedding the fonts,
and all the coloring, all the specifics of it for that.
Also, reading text, so if you do a book reading,
you have the text and you know, went to put through the next slide,
because we have slide-ext available for that,
and the presentation with the notes in there.
And look, it was already working on the book,
but seeing that it was also doing the parsing of this text format,
and inviting to the different output formats in one go,
which is good to start, but if you want to add more and more formats,
the code of course becomes much more complex,
because there's no separation between the two.
And to make it specific, here you see some parts of the book.
And on the left, you see the subtitle, the laptop,
that is hand-drawn, meaning that if I wanted to do that for Dutch,
I had to get a drawing tablet and actually hand-letter that.
I mean, I can do a bit of drawing, but I didn't have a tablet at the time.
So I wanted to use fonts to make it easier.
There was also an illustration with a protest page in that,
that also has to be hand-drawn.
Each chapter starts with a drop cap, this initial at the first paragraph.
Somehow, you also have to do that, and make sure that it's in the right color
for the different page, depending on the text.
There's some headings at the end of the book,
and on the right-hand side, you see text flowing around the image.
Of course, many graphical applications offer you to do that built in,
but in this case, it will hardline breaks to do that,
because it was not set up that way yet.
So I wanted to make an improvement.
Technically driven, I wanted to see how can I improve this,
to not just make my life easier as a Dutch translator,
but to solve it for everybody else that would come after me.
So I wanted to separate the automation,
and actually make sure that we could support more output formats,
and from Norway, Petter Reynoldson,
was using web-lay to do the translation for Norwegian bookmail.
And he was so fond of that, he said,
we should have the other ensemble book on web-layed,
but the custom format was really difficult to actually publish the web-layed directly,
because it was not a standard format.
So how do we do that?
We split up the parsing, we use a more standard source format,
we start using fonts, and get it to web-layed.
And looking for a standard, of course,
I didn't want to extend the text format even more
and start building our own standard.
I thought, what should be there as an existing standard?
And my first idea came to mind was Markdown.
But Markdown doesn't cope anything with the drop gaps,
and the color of it.
Maybe if you do a Pendock Markdown,
you have some specific details you can encode.
But that also means that everybody that wants to create a new format
would have to parse this specific markdown,
making it quite hard to maybe get started,
because it's not really a nice data structure.
I thought about askydog, because you have a macro syntax there,
and I have a history where to program,
but then you're still running to similar issues,
or with restructure text.
So then I came across dogbook.
Does anybody know dogbook?
Okay, a couple of hands.
Yeah, dogbook is XML.
So I know what you're all thinking.
Oh no, why would you choose XML?
We don't do any XML anymore, but let me explain,
because it really makes sense.
Dogbook is built for books, meaning it knows about a color form.
It knows about illustrations, not about all texts.
You can add metadata to it.
It's a standard, so it's supported by a variety of tools already.
And because it is XML, it's a data structure,
meaning everybody don't want to write their own
format and automation for it.
It can actually parse the structure, maybe even validate the field.
And in XML, there's already known extensions.
So it's the ITS standard to encode information about the translation.
So if you have translations, you have translator comments
that convey to the translator how this you translate the text,
I could embed that in the same dogbook format.
Also XML ideas to make specific references
in the file.
And I could create a separate namespace for everything
that was specific with elements and attributes
for the other ensemble book.
And this was four months extending to a year of work
to get this off the ground.
But finally, we now have this dogbook set up as the standard,
meaning because we already excuse an existing format
with existing tools, it was very easy to get Markdown output,
to get HTML output, to get a basic e-pop published.
And there's now also a fallback to the previous custom TXT format,
so that we also have the other formats available when
you did.
And now we work the script set up to make sure they're used fonts.
And actually we're already working on additional formats,
meaning e-pop also a braille, and even subtitles for the movie.
So you translate once and you get all the formats,
or if you contribute a format, you would have all the translations.
And this script is filling is something that I was looking
around to find something, but I didn't find it,
so I built it myself.
And the way I did it is that in the script, it's a template,
and there's an attribute that refers to a specific XML idea
in the document.
And it knows whether to fill a text field or an image field,
and based on that, gets the whole from the whole section
all the paragraphs, and it can deal with specific condition,
whether or not there's a drop cap involved.
And if it's an image, it can actually get just image
you're well from the double file.
Because most of the parsing is built around taking a talkbook text,
and then append more pages to the book.
But if you append more pages to the book,
in this case, the book is a fixed format,
it has a fixed layout.
So actually, we have to fill the specific template,
and that is what I reworked.
In this case, I implemented an ExcelT transformations,
which were really well with XML, as the script as file is also XML,
but maybe for compatibility towards the future,
if the script is format develops, it would be good to use the Python API.
But it's an idea for the future.
And what was really pushing me forward was the fact that the Danish team
with Carson and Ovent were trying to get the book out.
They also made a translation, and it's like,
we want to get this translation published.
Can you please send us a preview PDF and then we can prove read?
And by the way, you see the result of them setting up their own publisher
to actually get the book in Danish.
So this is like in the living room, a lot of books.
And here, they were showing the movie in our house at the premiere.
It's the one in Copenhagen, but oh.
Something specific about how I set up the translation.
I was already talking about ITS as a format that is standard.
Because I was using the standard, there was already an existing tool, ITS tool.
So I could feed this document, dogbook format, to ITS tool.
It extracts the translations into get text.
Like the command translation format.
That could be uploaded to web late.
People could contribute to web late right away.
So once I had dogbook in place, web late was easy.
Now, some people prefer not to use web late, and they use just the get text file.
There's also a find there in the repository.
And yeah, just using standard tools really help.
Now, as Petra from Norway was really pushing for it,
he now also has the Norwegian book out.
And what I think is very neat is that he worked the way of print on the map,
which is currently available.
The book is already available on ludo.com.
And with print on the map, you could do a global distribution,
meaning that if we tie this up the right way,
everybody that submits the translation, maybe can have the book on order globally.
By now, right?
That's chain everything together.
Now, something about the impact of web late,
because Petra was really pushing for web late,
and oh, did it pay off.
On the left, you see, last year when we had the initial translations,
I bit later added some other existing translation.
But the fact that it was on web late,
and it was easy to contribute.
And it was discoverable.
And people that were normally maybe translated software,
just happened to come across this project and started translating,
really made the amount of languages larger,
but also to make it more complete.
So there's all text, for example.
And some of the books, they were just translated for print.
But the old text was not considered.
Or the headings were not considered, which you need for ebook.
And there was this story with the translations.
That once it was on web late, people would find the project.
And one morning, I had 32 emails in my inbox.
And it was a start of the Persian translation,
and then all different people contributing.
And I was suspicious.
I was suspicious, like, how does it get started?
And so many emails.
So I started validating the translation with Libertranslate.
And then it turned out it was actually a valid translation.
So I asked them, email the persons from the death contributed.
There has to be a story.
So what did happen?
But turns out they were organizing an event
to come together and translate the book in one go.
So this team in Iran really made a good impact.
And in a couple of hours, I think, translated the whole book.
And we're looking to publish this.
And it's so inspiring of a story.
Now, with translation and localization,
you run into all particular issues that I want to address over time.
For example, you have right to left languages.
And when you come across right to left,
actually, the support and script is not so great yet.
Also, I have the template in left to right.
So ideally, I want to not have a duplicate of the template.
So if I make changes, I have to duplicate the effort.
Rather, I would like to have a script that converts it.
Well, Iran from Israel was working on getting this script across.
And he made this initial script.
And we found each other in the chat of the previous team.
But Ali, who was contributing there, hacking on this script.
And we were telling everybody how awesome this event was
to contribute online directly with maintainers.
And it proved not just the translations, but also the software.
And then there's something specific about the fonts.
Because the amount of support of characters in fonts
that look a bit hand drawn is quite limited.
I think David Reefow, again, with peppering characters
doing an amazing job in trying to build this font set.
That has a wide support of different languages.
And it seems for now the book we would have to switch fonts
based on different languages.
Also, something particular you already mentioned.
The Ukrainian book for the refugees coming.
The Sangamam had a logo and it's in many of the pictures.
But of course, the Z would remind the Ukrainian context to the Russian aggressor.
So all the illustrations were adapted to have a different symbol in the illustration.
And there's also something that the automation would have to take care of.
Also, something I want to highlight is the image descriptions.
You see the half of the text that describes the image on the left.
And this is to make sure that everybody that gets the book can actually get the story.
So even if you have a visual impairment or just maybe listening to the book in the future
that you have a good sense of what is actually conveyed also with nice illustrations that are in the book.
But also for me, reading the illustrations actually made me attentive to details I missed initially.
Because did you see that Maria actually has an artificial leg?
I didn't at first.
But there was a story of one kid that found the book and saw that.
Because the kid also had an artificial leg really fun and love the story.
When I was presenting about the book in a conference at a podcast in 2024,
one of the regular hosts there was visually impaired.
So they were challenging me.
Like, oh, you do this translation yet.
Will it also be in Braille?
And I thought, well, technically, why not?
But having submitted the Dutch book now to the publisher in December,
I thought, I'll be presenting about this.
I've lost them.
I might as well give it a go.
And so also, I got some good feedback on what a PEPOP should be the requirements for an EEPOP to be more accessible.
So that if you have these mechanical devices with PSO elements to put up the dots that actually works well.
But also, I wanted to do a real and boss version.
And I found this project online, Open Hardware, the Breyer rep,
which is basically a device, like a 3D printer, Open Hardware.
And here's, yeah, stay fun, good day, showing it out.
If you hold in a bit longer, the camera will point at you, yeah, yeah, yeah.
So this is an Open Hardware project.
And I thought, maybe in a year, I can first build my own embosser, open hardware,
and then we could do a print.
And a word of an email explaining that, and he said, no, no, no, skip that.
You can do that later.
I'll just make sure to have the prints at Boston.
And so we work together what do you need for the digital format?
And we actually have embossed version of Ada and Sangamam for Boston.
So thank you very much for that, Stefan.
Yeah.
And to make it more impressive, this was the first real book that was printed.
And the embosser doesn't have an automatic document feeder.
So the fun would be two days feeding paper in the machine to make sure that we have the book,
because 56 pages of text actually becomes like 150 pages of Breyer.
So multiple books.
And it's not just the text, also we did some illustrations.
And we have to find out how well this works.
Is it recognizable enough?
Or do we have to make things bigger or have something else?
So where we can experiment.
Now that we did something initial, we can actually start validating and learning from that.
That's very thanks to that.
But here you see a squeak from France, who is very interested in doing laser-cut wood.
And he had this format of Kamishibai, which is a Japanese format.
Maybe I'm mispronouncing it.
Either way, it's a Japanese format.
Think before we had any electronics, like an analog television, where people on the street
would have this display of pains with illustrations.
And one by one, they would lift up the illustration to show the next.
And they would have the text to read to continue the story.
And so he adapted the story to this Kamishibai format.
And for me, as an engineer, it's like, why not embed this as well as a traditional format
to the automation.
It's just another PDF output we can generate.
So I have this on the wish list.
Or what about this format?
The bilingual format, but see enough additions.
Where they have France and German next to each other or French and English.
And we have about 33 languages now in development.
So could you imagine, you give up two languages.
You want to have side by side.
You press the button and you have a print to go.
And you can have a side by side book to have any language that you want.
Or this, but everything that the French Ministry of Education did,
it was not just that they had the book.
Also, they have the website where the digital book,
you can actually open on any mobile device and start reading the book.
And they have various materials that were created for classrooms,
like games and quizzes that also teach about societal subjects that talk about math,
all tied up to the story of Adam Sangaman.
We could translate that to any language if we just kept going.
Because it's all creative comments.
Now, during the process of the automation,
because we were using standard tools,
I tried to do my best to report all the issues upstream.
And some of the issues are harder than others.
And in the case of Pandok, actually there were some misconceptions
how the standard was implemented.
And some of them are already fixed.
But in the scripts community, some of them
was already being worked on.
Are we now working on a bit of community to improve it?
And yeah, so hopefully through this effort,
we also improved the whole ecosystem of software that is around it.
And I would really like to maybe enable other books to be used
everything that was built for Adam Sangaman automation.
Of course, there's also other documentation that not only explains
how it's set up technically, but also what
do you need to get started with translating,
and how do you publish a book?
Because it was very hard to get all this information from different places,
to make it as easy as possible for every country,
a language team to get the book out.
And all the automation, it's a command line to at the moment,
but there's also a nice help command to show you what output
formats you can create.
And all this together, we now also have,
even though we have the Danish earlier,
we also have the Dutch book.
We have many books here with us.
So if you're interested in a Dutch book,
please go to the FSF East stand, just right outside of this whole.
And so we're now close to the idea where the translate ones
and push a button, and you've got all the output formats.
And like Ada in the story, I too have new ideas every day
to improve this project, and just following through,
and I hope with all the effort I've seen over the last months,
that people that have helped me, not just with the translation,
but all the automation that we together can even make this project much bigger.
Going back to the time when people told me, like from children,
people who know about children, books, and so,
even never gone a work with creative comments.
You've never been able to get that out.
You will never find a publisher.
Well, I think already till here, you see that with some energy,
with some hackout friends, with some lawyers,
and a lot of other skills in our community,
you can actually accomplish a lot.
So, many people here help with getting to this point.
So, thank you very much already for showing the publishing industry
that you can do it with free software, with open educational resource licenses.
So, thank you very much.
But, yeah, it didn't stop there, that it's just a book,
but what also happened then was that many people were using the book
and giving readings, like at schools, at libraries, at hackout spaces,
I myself, during the last months, read the book to over 2,000 children myself.
And there are here at free software conferences, where there are readings from,
I don't know, yeah, also here around here.
And then there are teachers using the book in school projects,
like here in France.
There are teachers, like here's one teacher from Spain.
She used the book in school for a week, for a project week,
and at the end, what the children did,
was they sent a letter to Tsangman, and telling Tsangman what they think about his behavior of this book.
So, the antagonist in this book, and it's so great to see those letters,
the teacher and the parents agreed that we can publish them on the website.
If you want to read what seven, eight year old think about free software,
and the aspects of proprietary software with free software,
have a look at that, it's really, really cool.
Or, we received inventions by children after reading the book,
what they want to invent when they have more technical skills like this.
Machine that can scan any object and afterwards,
you can see it from the outside and the inside.
And so, really, really cool stuff, and I'm very much looking forward to see
their custom talks in 20 years and what they accomplish.
And yeah, and even then afterwards, we run into one issue that we saw that many people
would like to hear the book, and they were requests for reading it,
and we cannot always fulfill it, and this pie, the automation for the book,
it's still really difficult to distribute books and to send them around the world
and to make sure that even if something is published by a publisher in one country,
that the book is then awaitable in another language that you can order it there,
and it's not like you're ordering it and you pay double the amount of the book for shipping.
So we thought about why not also do a movie about that.
And we did a fundraiser about that and accomplished to get the funds together to actually produce that.
So we now also have a movie available in English, German, French, Spanish, Danish,
Italian now also, so one of the speakers of the book here, and that's out there.
And people cannot watch that, and this one, this picture here is from the premier in Germany.
We rented the biggest cinema in Germany.
We had 800 children there, and TV moderator from children, TV channel,
moderating this whole event, and 800 children screaming in this cinema,
that's who I mean here you see it from behind.
Yeah, and the good thing now is that with this setup,
it's when you have an existing translation from that late,
and we can work around 3600 euros, tell the studio that we would like to have it in that language,
and then they can produce that.
We of course also had some community contributions like from Italy,
where a theater group was doing the audio recording, and then we can send it to them,
and it's done a bit cheaper, and we have really great contribution from the community there,
or our Danish one, where Ivan was doing the,
who is also doing the FSB podcast, was doing the audio there.
So, and if we get that money together, we can do it in the other languages,
and then it's also there available.
And it's not just a way to watch it online, but when we reached out to it for the premier in Germany,
they told us, yeah, can you send us a DCP file then?
They're like DC, what?
So, I learned that professional cinemas use DCP files for the movies,
and then you, they did the conversion for us,
and when they found out what the movie is about, they contacted me and said,
we will do any other translation for you for free,
because our whole tool chain is resolved there.
We are using handbrake subtitle added, open short, we,
all those tools, and we would love to contribute back and do the other,
the other encodings for you, then as well.
So, on our website, you can also download a DCP file,
random movie, theater, and have a really cool screening with kids.
All possible.
Yes.
Do mics, yeah, it's confusing.
So, as said, multiple times already,
you can become part of it.
You can do translations to get to book in your language
if it's not available.
You can do a book reading, but it's just in the local school,
maybe something organized in the library.
You can also share your thoughts.
We have a share pic at the FSV, where you just put in your name and your quote,
and get a nice picture to share on social media.
You could please, if you do any installation,
whether it's hosting a service, or maybe doing a Linux install for your friend.
You can add these files.
You can just hit the software because it's a creative comments license.
Organize the screening, as you said,
and maybe help with the automation.
I'm happy to accept any changes request.
And I think all of this, when we done, was really bit the help of FSV,
FSV staff, also supporting this, FSV infrastructure.
So please also consider becoming a supporter and donating financially.
Because for me, as a volunteer, I rely on FSV infrastructure,
also with my contributions.
And this is the 25th year, where FSV is at Phosdam.
So we said the goal to get 25 more supporters.
So please go to the stand and register yourself.
Go online and register yourself as a supporter.
And maybe also become more active with the FSV,
because it's a very nice community.
And there's a lot of things we can do together.
Now, if you join the project,
maybe you find yourself in an event where you have a nice ice cream
to get all the good memories you have from reading the book or contributing to the book.
And many thanks to Luca, who now also has a bit more time
for us, great hobby of making ice cream.
So thank you all.
APPLAUSE
And with that, we'd like to open it for questions.
APPLAUSE
I have a question about how images are translated now.
Is it automated process and with templates?
Because in the beginning, everything was a blob in a,
and get repository.
Yeah.
How the question is, how are the images translated?
Previously,
every hand-drawn text was an image.
Most of that is now a font.
So it's no longer an image.
There's a couple of images.
Specifically, there's a protest page image in the spread of the book
that still requires hand-drawn illustrations.
I've considered maybe adding something with inkscape or maybe in scripts.
Also, I have a font there.
We could do that as well, currently it's not.
And also, the cover page can be done in scripts,
but there's also still a gimp file.
And depending on the output format, for example, for the movie,
we need to 16 by 9.
It's yet still a gimp file to translate.
So it's still a bit of a working progress to make sure
that we add fonts to more and more setups.
But that means that also we have to incorporate,
essentially, the support from multiple fonts,
depending on the language.
Any more questions?
Well, people are thinking about another question.
Maybe one thing, if there are any,
if you know any teenagers around Europe,
or if you know how to reach them,
please also tell them about efforts
if these coding competition for teenagers.
It's called Youth Hacking for Freedom.
The idea there is that they can do whatever they want with free software
for several months.
The goal is then just that afterwards it's free software.
And they can win awards from 1,024 euros to 4,069 euros.
And we bring them together here in Brussels for a nice,
of what so many people like Nico,
on the jury, others from the free software community.
Not on the jury.
I think the photos.
And it's a really great event.
So inspiring.
So we learned a lot about how to adapt the book
for different languages, different formats, etc.
But once you're estimation to adapt the framework
for a complete new book.
Yeah, that is my ultimate goal is to make it as adaptable
to use for other formats as well.
We contacted our profended publishers
that are very friendly towards free software
and started looking online,
like what is actually available in terms of automation.
I found one or two pipelines that are based on Markdown
and produced an e-pop.
But it's very limited in scope,
what they actually do with the amount of translation.
It was not fitting for this book.
As you see, we now also support more and more formats.
And at the moment it's sort of a hotspots together
of different convergent tools and a make file
and a folder structure.
So if there's any ideas,
how do we make that like a universal template
so to make it less specific and more generic,
I would really want to do that.
So it can be done.
You can copy what is there and adapt it.
It is intended that way,
but there are some custom things at the moment.
In terms of generalization,
I guess that beyond having a generic template,
which is indeed a good thing.
I was thinking also to kind of a front-hand software
to make it usable to make the whole system usable
to, I mean, not developers.
Common users of PC, so a UI, front-hand,
which makes it easier to do all the whole process.
Yeah, I recall I didn't repeat your question
for the audio recording,
but the previous question was about making a generic for other books.
And this is a similar question.
I suggest in actually to use a front-hand to make it easier.
Yeah, why not?
Why? We could make a front-hand and do that in support that.
I could totally see that.
We were already thinking like,
how do we get this web-lay translation and somebody contributes?
Ideally, you want to have in minutes get the PDF output.
Normally, I check my email, but sometimes I'm at a conference.
It happens, and then it takes a couple of days.
And wait, so maybe you want to have some automation in place.
But if we can make that easier, why not?
The nice thing is already now at this stage.
I recently bought an email and someone was sending me a dialect,
which is spoken between France and Germany,
and it turned out that it was the father of someone from the German
from the French Ministry of Education, and they did that.
And we were able to produce a whole PDF with our tooling there.
It looked great.
And like yesterday I was in the legal and policy there,
and I left and someone said, are you Matias?
Yeah.
He gave me a book, which we himself printed in check with the tooling here.
I didn't know that anyone was already printing it.
So it's possible, and you can do it very easily,
or kind of different dialects.
You can also, I mean, the license allows you to do this.
If you don't like anything about the story, I mean, that's the cool thing.
You don't have to use it the way I wrote it down.
If you want to change something, well, just do so.
Press the button, and you have a book, which you can send to the printer,
and with a very low investment, you have a book in a few thousand copies out there.
For the translation, you show that you go from the book to get text,
and then to reply it.
Why doesn't the reply it's support the book directly?
Wouldn't that be easier?
Yeah.
Why does it not support the book directly?
I think it's support XML in general.
But as far as I know, the reply does not support the ITS information.
So I used the ITS standard to add translation comments.
That's like, oh, this is a acknowledgment.
It's in the book.
It's a very generic term.
How do you translate it?
It depends.
I just want a short word.
That is in the book and describes the acknowledgment of the author.
Something like that.
And that is what I get with the get text format.
Plus, again, some people are very much on their file-based workflow.
And they prefer to use a get text file rather than going through the online editor,
which myself, I can understand.
So this is a more generic approach.
But I think it's, if it would be in Weblight,
and there's already a lot of support in Weblight.
Yeah, hello.
How would you deal with Miss representing the messages?
Yeah.
Malware.
Well, the question is then, who would publish the book?
And the Dutch translation, for example, the FSFE logo is on there.
Meaning, it's under the umbrella of the FSFE, and we looked at the translation.
Sometimes with translators, there's a brief discussion.
This everybody reads the story and the things like, oh,
but this is not really fitting in our national context or in our language.
So there's always decisions.
Whether it's intentional or maybe a less intentional,
maybe it's malicious or not malicious.
But how do you adapt the translation?
And I think it ultimately, if you publish it yourself,
we have a stamp for remix.
You put your own logo on it.
It's like the branding is one way in licensing.
You can also protect the representation.
And besides that, I had a lot of discussions with illustrators,
finding an illustrator who accepts creative comments licensing
because they are very afraid of someone taking their illustrations,
doing something else with it.
And my conclusion there is, if you try to make it very,
difficult for people to, if you make it,
if you prevent bad things from happening,
and then you also prevent a lot of really, really cool things
from happening and good things from happening.
So in the end, we also decided there,
like, let's publish this this way.
Yes, people can also do some things with it,
which I as an author or others who contributed might not like.
But on the other hand, I mean, this whole story, what happened there,
many of those translations, many of those things,
they wouldn't have happened, if it wouldn't have been also possible
for someone who wants to do bad things to do bad things with it.
Thank you very much.
Thank you guys, that was it.
Thank you very much.
If you want to have anything from the bookstickers,
about the book, the books themselves,
up there at the FSF Ebooth, and they all lot of them there.
Thank you.