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

doc: Starting translate Docs to PT-BR #14665

Closed
wants to merge 2 commits into from

Conversation

jorgeluisrezende
Copy link

@jorgeluisrezende jorgeluisrezende commented Aug 7, 2017

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Aug 7, 2017
@jorgeluisrezende jorgeluisrezende changed the title Starting translate Docs to PT-BR doc: Starting translate Docs to PT-BR Aug 7, 2017
@tniessen
Copy link
Member

tniessen commented Aug 7, 2017

Thank you for your contribution! Has this been discussed anywhere? I am not sure we want to translate our README as it is updated frequently and not necessarily part of our docs, which should probably have priority. Even if we wanted to translate the README, we probably don't want to cram our root directory with all those files.

@refack
Copy link
Contributor

refack commented Aug 7, 2017

Hi @jorgeluisrezende, welcome and thank you for the contribution. As @tniessen commented and IMHO there are parts of the README that could simply be cross-linked to the english one (especially the list of Collaborators and CTC members as it changes frequently).
Also a more structured solution should be created for the location, and linking for translation files.
Two references:
https://github.com/nodejs/nodejs-pt
And https://github.com/nodejs/nodejs.org/blob/master/TRANSLATION.md

@refack refack added the discuss Issues opened for discussions and feedbacks. label Aug 7, 2017
@jorgeluisrezende
Copy link
Author

Right, well my idea is translate the instrunctions and other documents and keep some originals links like collaborators etc...In Brazil, a lot of prople need docs in pt-br...

@refack
Copy link
Contributor

refack commented Aug 7, 2017

In Brazil, a lot of prople need docs in pt-br...

Sure 👍
Ref: https://nodejs.org/static/documents/casestudies/Nodejs_2017_User_Survey_Exec_Summary.pdf (page 23)

@jasnell
Copy link
Member

jasnell commented Aug 23, 2017

It looks like we need a new nodejs/nodjs-br repository!

Hmmm... @hackygolucky ... thinking about it, these types of localization efforts would be an amazing opportunity for the CommComm.

@BridgeAR
Copy link
Member

BridgeAR commented Sep 2, 2017

How should be further progress here? I think it is great that there is a initiative for translating the docs to PR as I can personally tell how badly this is needed here in Brazil but I also agree that it is the wrong spot to add this.

@nodejs nodejs deleted a comment Sep 2, 2017
@nodejs nodejs deleted a comment Sep 2, 2017
@BridgeAR
Copy link
Member

@jasnell is there a good way to preserve the changes - anything where this should be redirected to?

@jasnell
Copy link
Member

jasnell commented Sep 13, 2017

Ping @nodejs/community-committee ... can someone help out here?

@jorgeluisrezende
Copy link
Author

how you guys gonna do? you'll create a new repository nodejs-ptbr?

@jorgeluisrezende
Copy link
Author

BridgeAR do you live in Brazil?

@BridgeAR
Copy link
Member

@jorgeluisrezende sim

@jorgeluisrezende
Copy link
Author

po legal, vc pode trocar alguns emails comigo?

@BridgeAR
Copy link
Member

Ok, I am closing this for now. @nodejs/community-committee if you find a way to handle this, it would be great to hear from you.

@jorgeluisrezende thanks a lot for your contribution anyway! Much appreciated.

@BridgeAR BridgeAR closed this Sep 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Issues opened for discussions and feedbacks. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants