I think once it offers stability in v1.0 it will be way more easy, but it is definitely possible, and specially appealing to me in Julia thanks to meta-programming, I already had a working proof of concept to translate the language itself to any other language, back when I was a recent newcomer to Julia!
I can’t wait to put my hands on JuliaParser.jl
v1.0.
But the ever changing guts of Julia made me keep waiting and develop patience, in the mean while I also got in love with this community, learned lots thanks to them, and started working on the none code parts of internationalization.
- manual (I choose Transifex for the website, but Crowding for the manual, since they provided me there with machine adied translation and machine memory, things that cost in Transifex, but transifex live, made very easy to translate the website and put the languages widget, etc.)
- websites
And
Before all this I did’t even knew what i18n stands for.
At times it seemed like a bad idea, at times I was discouraged by others (thankfully I am stubborn), at times it seemed like if I was alone in these lines of thought (but many others had though along the same lines before me), then I started exploring all these languages:
Clearly I’m not alone! - I said
Clearly it is possible! - I thought
It is a daunting task indeed, so I turned to the community (this also made me use Twitter for the first time, and still I only use it for Julia stuff mostly). I learned the ins and outs of social networks and opened Julia groups in Spanish in Facebook, Google groups, Gitter, etc. so people didn’t get stuck, I also wanted to meet amazing people, help and learn from them, which I still do.
Not all of those ideas worked great, turns out social engineering is way more difficult for me than software engineering.
I am extremely inclusive, I have been inviting everyone from day 1.
There were other i18n efforts for the manual, in some languages, each on their own, I wanted to bring organization to the table, reuse of resources and to eliminate redundancy caused by each separate effort trying to do the same things on their own, but at times people perceived the project as my personal project. So I started delegating responsibilities (the idea of me dying in an accident and the project dying with me gave me nightmares), creating groups for each language, and each variation, invited Viral and others core devs to join, so others could see the support from the founders and the community.
Then the magic happened, people started to step in, and take initiative, and make progress, but as you point out, keeping up with Julia currently fast moving target has proven very trying (good luck I’m still young and full of energy!).
So for me currently the priority is to have the proper communication, support from the community, infrastructure, workflow and tools, not having 100% professional grade translations now.
I want 100% i18n Julia, with errors, warnings, docstrings and all, and packages too (opt in, ie. Gettext.jl)
It’s not that I don’t like or believe learning English is important, it is! What I’m not OK is that it is required to first learn English, then learn programming. I would be OK if I could teach programming 100% in Spanish, and then make an interactive Julia package to teach English so children and adults alike can also learn it, but this I haven’t even started yet.
We need help and support from all of you guys, but if this is not needed I will keep doing it by myself anyway, I guess I am greedy …full Julia i18n, that is my only “ungracious demand”