I want to start translating to pt-BR (Portuguese Brazil), how do I add my fork in GitLocalize?
Fork Link: https://github.com/devtranslate/docs
@vitornogueira there are guys actually planning this translation at vuejs-br comunity. Do you want to join us?
@Atinux can you add Portuguese (Brazil) to the GitLocalize translate list or should we go by ourselves forking this repo like we do in the main Vue.js docs?
Nice! We fork the repository to devtranslate organization (https://github.com/devtranslate/docs). Can we work on that fork or will it have a fork for the @vuejs-br?
@vitornogueira Vue Brazilian Community is centralized on VueJs-Br organization. Do you mind keeping the repository there?
Hi there, it's awesome to have Brazilian translation coming!
I believe it's better to fork the repository so you can stay in sync with master branch, I think @Haeresis can explain more about his process which is really good
Hi @derevandal. If you want we can work on the fork of the @vuejs-br organization, no problems 😉
@vitornogueira, the fork https://github.com/vuejs-br/nuxt-docs is waiting for you.
@Atinux, we already work this way with the vuejs.org repo. But how you'd like to receive our updates to deploy, maybe pull requets of the pt-br folder to the main repo?
Pull requests to thr pt-br folder will be perfect :)
@ErickPetru could u add your fork in GitLocalize?
Or u should wait @Haeresis and @Atinux?
We do not use GitLocalize accross our Vuejs-FR process but we have a process to translate and review all togheter and better, a process to see all changes from last translation update to set up-to-date the documentation with English version. If you do not want use GitLocalize or if you not already have a process I can explain our process (or find post where I explain it) :) Let me know if it's useful now or let me know that later ;)
Good Luck ;)
@Haeresis thanks bro! now, we fork this repo, clone en folder and start translate making pl on your fork. what process do u use?
Manage your translation into two branch on your translation project your fork from nuxt/docs.
Your working branch will be upstreamed from nuxt/docs:master. That means each time an update will be done into the original en directory from nuxt/docs:master, a conflict will appear in your <your-repo>/docs:working at the same already translated file and line. That allows you to track all update in future, and update it.
When the <your-repo>/docs:working EN directory is enough translated / updated, you copie/past the en content into the pt directory of <your-repo>/docs:master. From now just do a PR <your-repo>/docs:master to nuxt/docs:master to update pt in orginal fork.
To allows more one person to translate files. Each translator should create it's own fork from <your-repo>/docs:working, translate the wanted file, and do a PR to <your-repo>/docs:working. That will allows all teams to review the PR and see line by line what EN line is become an PR line (and correct error translation/typo).
Example in french:
git fetch updtream
git merge working upstream/master
Normaly, it forbidden to directly update fr from original Nuxt depo because we not track fr directory but en directory. That means it's possible we erase some update do in fr directly. So it's important to do all FR fix/update into https://github.com/vuejs-fr/nuxt/tree/working/en (the real FR tracked version). It's the same for you. So that should be the same for pt