-
Notifications
You must be signed in to change notification settings - Fork 10
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
Keeping track of Translation progress #5
Comments
Ofc @mrcego, your help is more than welcomed! 😄 Right now we are translating in smalls chunks (i.e. Mar-1/Mar-8) at a time, once a section is done we move onto the next one, meaning one is dependent of the previous one. What do you think of this approach? How is it being done on Vite.js and Elk? |
In the first instance, I was working like you describe (chunks of sections for each commit). Since I finished the translation, every friday or twice in the week release an update with the new translations via issues using ryu-cho. Telling this, it's not very different to your strategy, so we could work in the same line. I'm happy to help, so let's hands on, just tell me what I can start 🫡 |
Oh didn't know about ryu-cho 👀 we'll integrate it as soon as we finish with the tranlation. Right now @glopzel is working on Mar-1/Mar-8. How about you do Mar-11, there are many commits so, let's do just one day for that chunk. |
When you say Mar-11, what do you mean? March 11th? The date in the Github historial from Vue.js docs? |
Here, we are monitoring the current translations and identifying the individuals responsible for them. We are working towards translating what's missing by addressing the commits made to the main Vue docs during a specific time frame.
The text was updated successfully, but these errors were encountered: