website-v2
website-v2 copied to clipboard
[Translation] Portuguese Translation Planning
I did create this issue to:
- To organize the process of translating all website to Portuguese
- To gather all information about the state of translation of all website to Portuguese
- To track all voluntary translators (to know which part of the site they are translating, to avoid conflicts during all process).
I would like to ask to: @alexchopin, @Atinux, @smarroufin or someone that is maintaining this part of the project to pin this issue.
I am translating the following directories:
-
pt/docs/deployments
-
pt/docs/3-features
-
pt/docs/4-directory-structure
Next I intend to translate the pt/docs/examples
, but if someone want to translate it it's only warning.
Below there is a list of all content translated:
- [ ] announcements
- [ ] case-studies
- [ ] contribution-guide
- [x] deployments
- [x] design
- [x] docs
- [x] docs/1.get-started
- [x] docs/2.concepts
- [x] docs/3.features
- [x] docs/4.directory-structure
- [x] docs/5.configuration-glossary
- [x] docs/6.internals-glossary
- [x] docs/7.components-glossary
- [x] events
- [x] examples
- [x] modules
- [x] partners
- [x] releases
- [x] showcases
- [x] sponsors
- [x] support
- [x] teams
- [x] testimonials
- [x] themes
- [ ] tutorials
- [x] video-courses
- [x] index.md
Can I help with this issue or not?
I started my work 7 days ago and opened an issue. When I started there was no open issue on it, I even checked the old ones made by @BrendonHenrique, how would I know you were doing something without an issue?
Whoever started it, didn't put it in nuxt.config, so there wasn't a link to open the translation on the site, so I figured they had discontinued it, so I created a new 'pt-br' folder, and then put it in the project config.
I think that if you are going to start a translation you need to open an Issue. You also need to do the complete setup and also not just throw the content into Translator and paste it (the pages I modified were like this), as well as not be ignorant of others who are also contributing.
I have translated the home page completely, both the title and the navigations. If you want to accept what I worked on, I will open a PR, if not I will continue to work on the pt-br translation, because there are differences, even if minimal between pt and pt-br, precisely why in the standard there is en-us (as is in the configuration), en-uk, pt and pt-br.
I brought the 1.get-started
and started the 2.concepts
(both pages and navigation).
I have translated the home page completely, both the title and the navigations. If you want to accept what I worked on, I will open a PR, if not I will continue to work on the pt-br translation, because there are differences, even if minimal between pt and pt-br, precisely why in the standard there is en-us (as is in the configuration), en-uk, pt and pt-br.
@felipesuri I believe to maintain the things organized it's okay to create two version of portuguese, to not make you struggle with the existing differences, so you can make a PR of your pt-br
, and will continue work upon pt translation.
Make sure to do the necessary changes in configurations files to make two routes being generated one for pt
website other for pt-br
. lets make a good job and make the community grow.
@smarroufin.
@nazarepiedady All right, I will be translating pt-br
, everything is configured so that the route is /pt-br
from the start.
@smarroufin I'll create another issue so I ask you to pin this, please!
@nazarepiedady All right, I will be translating
pt-br
, everything is configured so that the route is/pt-br
from the start.@smarroufin I'll create another issue so I ask you to pin this, please!
Good, I have already seen your commits, continue doing a great job together we will make Portuguese community even stronger.
@smarroufin is there a problem in sending a huge PR?
Since, I am the only person working on pt
folder now, I would like to make a commit with all translated files.
@nazarepiedady Sure, every PR is welcome! And if this is a huge one, even if this takes time, we will handle it!
Hi @nazarepiedady @felipesuri
If one of you guys could translate content/pt/_collections/navigations/*
that would be awesome :green_heart:
Then I should be able to enable PT langugage on production!
Hi @nazarepiedady @felipesuri If one of you guys could translate
content/pt/_collections/navigations/*
that would be awesome :green_heart: Then I should be able to enable PT langugage on production!
I already did the translation for this folder, and now I only waiting the approve of the content/pt/docs
to send other folders that are ready to be reviewed and applied to the main branch. @smarroufin
Hi @smarroufin @nazarepiedady @felipesuri I guess I already showed up late, but if any help is needed, I can also help with PT translations (pt-br not much since I speak portuguese not pt-br :) )
@MonicaFidalgo nice to ear it from you, I think your help will be very useful and essential when we start to touch in NuxtJS 3 website, We will remember your availability.
The translations that already did is good but not perfect, and I personally believe that a effort to turn the sentences more clear and correct any grammatical issue would be great.
@nazarepiedady that would be awesome! I have been trying Nuxt3 and I'm loving it. And one of the best ways to learn even better would be to help with translations! I will be waiting then! Please don't forget about me :)
@MonicaFidalgo of course, when the project starts you will be there.