Have you been able to do it @rand_om?
Jupp, sry forgot to post it. I also asked Nick if he could give us the english transcript, so it’s easier for the other languages. Im finished with german, but I had to watch the video to do it, which just takes more time.
Alright, so here’s the transcript in english, thanks to Nick. Should make it easier to translate.
Anyone else interested? So far we have German and Spanish. @casko? @Krekc?
After having a lot of fun reading the script generated by the “Auto-translate” feature, I made an Spanish version of the script.
As you can imagine I’m not an expert, or even a translator, so I did my best to keep it close to the English version and in a neutral Spanish. If you need help placing them in the timeline on Youtube let me know when it’s available to do.
I’ve just enabled it and sent @rand_om a link. Hopefully that will work.
Okay, here is the link to enter subtitles/translations.
You enter the lines/sentences one by one, and adjust the time and duration each one is shown. Then you need to submit. You don’t have to do it all at once, I think. Unfinished translations are stored as drafts, an you can even submit unfinished ones so others can do the rest. But as the video isn’t that long, I guess that won’t be necesary.
It doesn’t take that long afterall, maybe an hour or so.
German translation now live on YouTube. Thanks for the effort @rand_om, superb!
I just submitted the Spanish ones on the video for review. Let me know if something needs to be change or enhanced.
Thanks Gabriel. Now added to the video!
I’ll do the Dutch translation later today. I’ll post it here so that Dutch people can suggest improvements.
I did the Dutch translation yesterday, only need a review from someone 
Dutch subs are now live as well, with thanks to @Melvin for the translation and @nicklambert for adding them to YouTube because I’m too stubborn to make a YouTube account 
I finished slovenian traslation. Any other videos?
Ah right! Haven’t thought about others
Yes, I have a good idea of how translations could be managed
It depends what you want to translate. Currently we have the following websites for documentation:
The SAFE Network Wiki has barely been updated for more than a year. A lot of the content is outdated and I think we should have a discussion about whether we want to continue using MediaWiki. I personally prefer static websites, they are a lot of easier to maintain and I think it’s essential to have the ability to accept pull requests. That way, anyone can easily suggest improvements, and discussions about improvements happen in a very open and transparent way (e.g. in the comments of a pull request).
One of the reasons for switching from GitBook to MediaWiki was that GitBook wasn’t ideal for FAQs. But now they have a theme made specifically for FAQs, so I think it would make sense to create an FAQ site that would look something like this: https://help.gitbook.com.
Another reason was that MediaWiki has good support for translations. Previously we were trying to manage multiple GitBook translations using the same GitHub repo. I think a better strategy would be to have one GitHub repo per translation. There is not much advantage to having all the translations in one repo. I feel it would be much easier to manage the translation process if each group of translators focus on their own repos (that way each group can self-manage and doesn’t necessarily have to get its changes approved by the authors of the original English version).
I am currently testing this process with @nbaksalyar. He translated the first Dev Tutorial in Russian (ru.tutorials.safedev.org) using this GitHub repo.
So I wouldn’t recommend working on translating the wiki right now, since the content will likely change a lot and we might even decide to use another tool (e.g. GitBook). I’m currently busy with the Dev Tutorials and the API Docs, so I can’t really focus on the wiki right now. Once I’m less busy, I could write a proposal and present an example FAQ site 
Readme.io is currently used for user documentation (SAFE Launcher and SAFE Demo App). Previously it was also used to host the API Docs, but we recently rewrote them using GitBook. Readme.io makes it hard to have multiple users working on the same documentation compared to simply using a GitHub repo. I think it would be worth it to completely move away from readme.io at some point. We could host the user documentation using a static website. I have a few ideas related to how it could be organized and how translations could be managed, but it’s something I’m planning to work on later. I think it’s fine to continue using readme.io for the short term
The Dev Tutorials were built using GitBook and it’s easy for anyone to contribute by submitting a PR to this GitHub repo.
I can also create a new GitHub repo for each translation.
There is still a lot of work that could be done to improve the existing tutorials. I’m not sure it’s worth focussing on translating them just now. I think it would be worth waiting until all the tutorials have been released before considering translating them.
The API Docs are also built using GitBook. See this GitHub repo.
We haven’t written the documentation for Launcher API v0.6 yet (I’ll start working on it soon, maybe next week). I think it would be preferable to wait at least until Launcher API v0.6 has been documented before considering translating the API Docs
@nicklambert, casko submitted a translation, can you publish it?
@frabrunelle, do you have other videos you would like us to translate?
/edit woops, great timing
Sounds good, very well thought-through. The faq you linked looks good imo, would be great though if we could fold down (bad english?) each question. We will probably have a lot to answer…
FAQs should probably be translated first or very early? We could plan to make this our first larger attempt on translations, and also make a thread here for suggestions. This thread might come in handy.
@MrAnderson also wanted to know if there might be bounties.
Now, go to bed or have a drink or something. You need to take care of yourselves 
@frabrunelle this is a valuable post, maybe worthy of a topic such as State of the Documentation / Plans for Translation.
Now published. Thanks for @rand_om for the heads up and of course @casko for the Slovenian translation!
A lot of work to do, great! I can help with reviews, proofreading, transaltion to slovenian language.
Translation and pull requests are a must.
Translation of Wiki/FAQ has a priority imho, developers (Dev & API) are usually quite skillful in English, at least in my country.
Hi. I can do Italian translations.
Awesome, check this post:
