Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translation plan and progress tracking (version 1.0) #16

Open
iJackUA opened this issue Oct 28, 2015 · 3 comments
Open

Translation plan and progress tracking (version 1.0) #16

iJackUA opened this issue Oct 28, 2015 · 3 comments

Comments

@iJackUA
Copy link

iJackUA commented Oct 28, 2015

How to help with translation

  • Select a page with ❔ not assigned status
  • Write a comment in this issue like I am taking page-name.md
  • Create fork of this repo
  • Be sure that you are making a translation based on lang-ru branch
  • Create a pull request to this repo with name [WIP] page-name.md even if/while translation is not completed yet (for everyone to know that you are really working on it, or if you will leave it - someone could use your starting point and continue, so your work would not be lost in any case)
  • Refer to previous docs version translation, maybe the docs article you are working on was already translated and you can find some text parts.
  • When you finish a translation rename a pull request and repo [WIP] prefix
  • Be sure that your branch is up-to-date with latest state of this repo's lang-ru and pull request could be merged without conflicts
  • Make a comment here like Finished page-name.md <link to pull request>
  • Someone will review your translation and I'll accept a pull request

Review

Even if you are not very good in English to translate by yourself, or have no time etc. You still can contribute.
If you see a 🙈 review needed label on page. It means that translation is completed, but some native speaker should review it in Russian. To track down bad wording, mistypes or anything that "looks weird" for a Russian native-speaker. If you found something - ideally make s fix pull request, or at least create an issue with back links to "error" lines.
If you have reviewed some doc and it looks fine for you - write here in comments to mark it as done 👍

Priorities

Pages are ordered in the table as they are ordered in docs, so it is supposed to translate them in the same order. You are free to select any page, but it's better to go one-by-one in the list

/source/guide

Page Translator Reviewer Status
installation.md ❔ not assigned
index.md ❔ not assigned
overview.md ❔ not assigned
instance.md ❔ not assigned
syntax.md ❔ not assigned
computed.md ❔ not assigned
class-and-style.md ❔ not assigned
conditional.md ❔ not assigned
list.md ❔ not assigned
events.md ❔ not assigned
forms.md ❔ not assigned
transitions.md ❔ not assigned
components.md ❔ not assigned
reactivity.md ❔ not assigned
custom-directive.md ❔ not assigned
custom-filter.md ❔ not assigned
mixins.md ❔ not assigned
plugins.md ❔ not assigned
application.md ❔ not assigned
comparison.md ❔ not assigned

/source/api

Page Translator Reviewer Status
index.md ❔ not assigned

/source/examples

Page Translator Reviewer Status
all pages description ❔ not assigned

/themes/vue/layout/*.ejs

Page Translator Reviewer Status
all pages description @iJackUA 🚧 work in progress

Setup gh-pages site for 1.0 http://vuejs-ru.github.io/vuejs.org/

@iJackUA 🚧 work in progress

Legend

Emoji Status
👍 done
👀 in review
🙈 review needed
🚧 work in progress
not assigned
@simplesmiler
Copy link

So what we can salvage from the pre-1.0 translated docs?

@iJackUA
Copy link
Author

iJackUA commented Oct 29, 2015

@simplesmiler Hard question. I tend to consider everything as translation from the scratch.
Just consider that some parts are already translated and while working on 1.0 docs, for example "computed.md" refer to 0.12's "computed.md" - maybe some parts could be "reused". But as a general rule it seems to be hard (maybe I am wrong, let's start and then we'll see).

@iJackUA
Copy link
Author

iJackUA commented Oct 29, 2015

Updated lang-ru branch with actual docs state (not translated).
Previous progress transferred to [email protected].

In nearest days hope to bring back CircleCI for automatic docs site rebuilding. And to transfer back all Hexo parser features - like markdown plugin with abbr support etc. To try to push it to main Vue docs repo.

@iJackUA iJackUA mentioned this issue Jun 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants