current fork here
current demo site here
@gbezyuk (general translation)
@kojoru (proof-reading and styling)
@moonlik (proof-reading)
more contributors are welcome
Essentials
Advanced
Migrating
translation in progress by @gbezyukMeta
[x] Server-Side Rendering
[x] Markdown Editor
?
Essentials
Advanced
Migrating
Meta
proof-reading and styling in progress by @kojoru
?
(currently for uniformity only, a subject to change in the future, not a complete list yet)
instance — инстансprops — входные параметрыcalculated props — вычисляемые свойстваnative — нативныйcallback — // this thread was originally started with:
Being a native speaker and an amateur linguist, I would be more than happy to help with Russian translation. Is it, by any chance, already in progress?
Ok, I'll take this silence for "there's no translation in progress as far as we know" and start my own.
The translation is started at https://github.com/gbezyuk/ru.vuejs.org
@simplesmiler might know better, but there's none that I know of.
There was an initiative around the time of transition 0.x -> 1.x (https://github.com/vuejs-ru/vuejs.org). But it didn't finish, and most likely is unusable now, because 2.0 were rewritten pretty much from scratch.
I am close to finishing the API translation now, as well as first parts of the Guide. Should we move the repo under vuejs?
UPD: API translation draft is finished. It requires proofreading.
UPD. Guide's Essentials section is almost finished. Guys, let's move the repo to vuejs and start proofreading. Anybody? )
I've opened a PR at https://github.com/vuejs/vuejs.org/pull/548 as a demo.
We'll move this to its own repository under the vuejs organization once it's done, but in the meantime, it's generally easier to just manage the translation in a personal repo, where you'll have full control over collaborators.
API docs proofreading/styling started by @kojoru.
Guide's Essentials section initial translation is completed.
"Reactivity in Depth" section from Guide/Advanced is translated.
"Plugins", "Mixins", "Join Vue.j Comminity", "Custom Directives" and "Deployment" sections of the Guide are translated.
"Render Functions", "Routing" and "Single File Components" sections of the Guide are translated.
"Server-Side Rendering" and "State Management" sections of the Guide are translated.
"Transitioning State" section of the Guide is translated.
"Transition Effects" section of the Guide is translated. My gosh, we don't seem to have a proper translation for "transition" in Russian =(
"Unit testing" section of the Guide is translated. Thus, the Guide translation seems to be complete now.
@chrisvfritz, maybe it's time to move the repo under vuejs now? It's certainly not the end of the work, as there should be more proof-reading and styling, as well as "migrations", "comparison with other frameworks" and "examples" sections translation, but I guess the translation is already useful for Russian developers not having enough skill in English to read the original documentation.
@kojoru, would you please mark the checkboxes indicating the sections you've already proof-read?
maybe it's time to move the repo under vuejs now? It's certainly not the end of the work, as there should be more proof-reading and styling, as well as "migrations", "comparison with other frameworks" and "examples" sections translation, but I guess the translation is already useful for Russian developers not having enough skill in English to read the original documentation.
@yyx990803 What do you think?
"Comparison with Other Frameworks" chapter is translated. That was a big one =)
Translation was updated to v.2.0.5 via an upstream merge in order to reflect the changes of the original documentation.
layout elements translated
@moonlik has joined the team, providing his first PR with typo fixes
Self-proff-read "comparison", "class-and-style-conventions" and "components"; disabled 'Source Sans Pro' font which doesn't seem to play nice with Cyrillic text at the moment (see _settings.styl for details).
@yyx990803, how about moving the repo to vuejs team?
We've returned Source Sans Pro as a locally hosted font since Google Fonts does not support Cyrillic for it.
There was a massive proof-reading / styling work done today. Also, the examples section was translated. So now, basically, we have only the migrations docs left to be translated, and just a few sections of the guide to be proof-readed.
Which returns me to the original question about the repository position. @chrisvfritz, @yyx990803 — what do you think, guys?
I have translated migrations docs for Vuex.
Vuex migration docs were proof-read.
Translated migrations docs for Vue Router.
Merged upstream to reflect 2.1.x version docs update; thus some new parts of docs are not yet translated. @chrisvfritz, what about finally creating a Russian version docs repo under @vuejs?
@gbezyuk Sounds great! I don't have access to create new repos, but I think this should now be ready @yyx990803.
2.1.x stuff is also translated.
look forward to official Russian docs at ru.vuejs.org
+1
Awesome, in Paris with shitty wifi right now, will setup the logistics once I get back to US.
Btw is the demo site up to date? Seems it doesn't have the new ecosystem dropdown.
+1 for official Russian docs
@yyx990803 sorry, the demo site isn't up-to-date. @kojoru, could you please fix it?
@gbezyuk done
+1 for official Russian docs
Looks good! So, for the deployment logistics:
You can deploy via either surge or GitHub pages. For either you need to update the src/CNAME file to ru.vuejs.org - I will add a DNS record and update the languages dropdown on the main site once that's done.
We will likely not be pulling translation repos into the vuejs organization in the future, as it just adds admin complexity for little benefits. I'd recommend continuing to work in your current fork and update the contribution link at the bottom of each page.
Nvm! I looks like you already updated the CNAME
It seems Surge does not support subdomain CNAME? Maybe we need to use GitHub pages instead.
@yyx990803 I guess it already works somehow with Japanese and Mandarin? Shouldn't we just use the same approach?
@gbezyuk my experience is that moving them into the organization didn't provide any practical benefits except that it is now "part of the organization", and adding contributors etc. became more complex because it now has to go through the organization instead.
@yyx990803 I got it and I don't insist. I was addressing the issue of CNAME.
@gbezyuk ah, ok. Both the Chinese and Japanese versions are using GitHub pages. I tried pointing the CNAME to surge but it doesn't seem to work: https://ru.vuejs.org/
what does the original site use?
Also GitHub pages. I've already pointed the domain to GitHub now, but it seems the gh-pages of translation-gang/ru.vuejs.org is out of date.
Since you've already edited this line, you should be able to just run hexo deploy to deploy to GitHub pages.
oh, the line is outdates as I've moved the repo to @translation-gang. Seems like it's my fault in the end of the day. Let me fix it.
finally, it seems to work now! hooray!
once again, Evan, thank you very much for everything you've done!
Yay! Do you want to make a PR to the main repo to add Russian under the translations dropdown?
Sure, in a minute.
I've also created a PR for Japanese translation (https://github.com/vuejs/jp.vuejs.org/pull/195)
Can't find a way trough Chinese characters, unfortunately. 对不起.
And BTW, there's vue-router's translation awaiting a merge, too.
Woohoo! Thank you @gbezyuk for pushing this forward and also everyone else who contributed. I just deployed the link to the Russian version. Is this good to close now?
@chrisvfritz thank you too :) I think it's okay to close this issue now, as all further work could be coordinated under @translation-gang.
Could you please deploy vue-router's up-to-date version as well? Russian docs are merged in, but not yet deployed, which makes me feel a bit incomplete )
Reading through this thread, this looks like it was good to close about a year ago. I'm closing it out but feel free to reopen if I misunderstood. Thanks!
Most helpful comment
+1