I’ve tried to do some translation projects as well in my past (target german), but during this I learned, that such a project is unmaintainable.
The process of translation is very longwind and important bits will not be translated fast enough, such that at the end you have a page which is only translated partially, but those parts that are are mostly out of date.
Also, as soon as one wants to use just another library, he will hit the english wall again.
So, in my opinion (not related to phoenix team though), if you want to create a japanese version of the page, have fun by doing so, but do not expect it beeing linked as an official translation.
That sucks … even in my (Polish) language there are some tutorials.
That’s really awesome idea. Let me know if you would need a help. As @NobbZ it’s really, really hard to make it working really good with multiple languages, but personally I believe that creating a working translating system is possible - hard, but possible.
I asked @josevalim similar question. I wanted to create a Polish translations, but at least for now there are no plans for it and thinking how hard it could be to make it working up-to-date I’m not surprised.
I’m going to learn Japanese. If there is something I can help just let me know.
Maybe consider reach somebody from elixirschool Japanese translators. As they are in topic maybe they could help you. Maybe they know about some Japanese tutorials. Also I heard that Koichi Sasada helped translate Dave Thomas’ Programming Elixir into Japanese.
Here is what I think you need in your website:
Good database versioning
Difference support which would be easy to process and preview for human is definitely must-have and it’s what lots of translator would see as comfortable.
Well designed translation support
That’s general, simply good idea on bad practices fails especially if something is really hard to finalize.
Auto-import articles from official sources
In most cases you need to have pretty good web scraping experience. You are probably going to change one document struct into your own to style it on your own, but without losing whole structure.
Really good notification system
Translators would be located in lots of countries. Different habits, different communicators, different apps, so different notification procedure. One notification way is definitely not enough. Translator needs to receive short, fast and good quality message as notification and described details when he will login.
You need to know which people are ready to make translations and how much they are busy. I’m generally busy, but I should not have problem with creating Polish translations enough fast.
Only with all of this (+ of course much more) you are able to achieve your goals.
I don’t recommend this. I would use database instead, so you would be able to have translations for every article per publish date and not everything statically. You also would have a problem with introducing notifications for developers and then they would need to contribute instead of nice translations web editor. I believe that it would be hard to maintain in such way.
Also I’m planning to work on my own version of ex_doc which would support translations and compiling documentation into scenic GUI app if you would be interested. However I would need to have some funds for that, because I would need to delay my other project from which I’m expecting to earn some money.