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

Add PT-BR translation of Quickopen command #1900

Merged
merged 2 commits into from
Jun 11, 2018
Merged

Conversation

acwoss
Copy link

@acwoss acwoss commented Jun 7, 2018

peek 07-06-2018 16-33

@msftclas
Copy link

msftclas commented Jun 7, 2018

CLA assistant check
All CLA requirements met.

@codecov
Copy link

codecov bot commented Jun 7, 2018

Codecov Report

Merging #1900 into master will increase coverage by 0.04%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1900      +/-   ##
==========================================
+ Coverage   74.42%   74.47%   +0.04%     
==========================================
  Files         282      282              
  Lines       13260    13267       +7     
  Branches     2385     2386       +1     
==========================================
+ Hits         9869     9880      +11     
+ Misses       3260     3254       -6     
- Partials      131      133       +2
Impacted Files Coverage Δ
...ient/interpreter/locators/services/condaService.ts 96.52% <0%> (-0.87%) ⬇️
src/client/common/platform/fileSystem.ts 67.53% <0%> (+1.81%) ⬆️
src/client/debugger/mainV2.ts 80.32% <0%> (+2.4%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4ddebe2...14dbf17. Read the comment docs.

@ppcmiranda
Copy link

I really liked the translation. My only suggestion is changing “teste unitário” to “teste de unidade”. I believe this translates better to Portuguese since we are testing a unit instead of executing a single test for everything. I know some literature has it wrongly translated (as many other classical wrong Brazilian translations in software) so I understand if kept the way it is. Congratulations for pull request.

Copy link

@camilamaia camilamaia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great translation! :) Only some minor suggestions, but it is pretty good in the over all.

I would suggest to keep using only one translation of workspace to avoid confusion.
Here it is being used Espaço de Trabalho and here we have Área de Trabalho. This is a tricky translation for pt-BR actually, because Área de Trabalho may sounds like Desktop for us. So I would suggest to use Espaço de Trabalho.

"python.command.python.startREPL.title": "Iniciar REPL",
"python.command.python.createTerminal.title": "Criar Terminal",
"python.command.python.buildWorkspaceSymbols.title": "Construir Símbolos da Área de Trabalho",
"python.command.python.runtests.title": "Executar Todos Testes Unitários",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add an article here:

Executar Todos os Testes Unitários

And the same for the line bellow

Depurar Todos os Testes Unitários

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that "Espaço de Trabalho" would be a better translation for "Workspace", but it seems that VS Code has already adopted "Área de Trabalho" as default elsewhere and I have chosen to use it for consistency. About using "Espaço de Trabalho", my fault.

@brettcannon
Copy link
Member

@acwoss does the comment from @ppcmiranda need to still be addressed? Let me know as I'm ready to merge this when you give us the go-ahead.

@acwoss
Copy link
Author

acwoss commented Jun 11, 2018

@brettcannonYes, it's okay to merge.

@brettcannon brettcannon merged commit 348ac72 into microsoft:master Jun 11, 2018
@brettcannon
Copy link
Member

Thanks everyone for this!

@lock lock bot locked as resolved and limited conversation to collaborators Jul 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants