-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Korean translation #540
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
Korean translation #540
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
{ | ||
"python.command.python.sortImports.title": "Import문 정렬", | ||
"python.command.python.startREPL.title": "REPL 시작", | ||
"python.command.python.buildWorkspaceSymbols.title": "작업 영역 기호 빌드", | ||
"python.command.python.runtests.title": "모든 단위 테스트 실행", | ||
"python.command.python.debugtests.title": "모든 단위 테스트 디버그", | ||
"python.command.python.execInTerminal.title": "터미널에서 Python 파일 실행", | ||
"python.command.python.setInterpreter.title": "인터프리터 선택", | ||
"python.command.python.updateSparkLibrary.title": "PySpark 작업 영역 라이브러리 업데이트", | ||
"python.command.python.refactorExtractVariable.title": "변수 추출", | ||
"python.command.python.refactorExtractMethod.title": "메서드 추출", | ||
"python.command.python.viewTestOutput.title": "단위 테스트 결과 보기", | ||
"python.command.python.selectAndRunTestMethod.title": "단위 테스트 메서드 실행 ...", | ||
"python.command.python.selectAndDebugTestMethod.title": "단위 테스트 메서드 디버그 ...", | ||
"python.command.python.selectAndRunTestFile.title": "단위 테스트 파일 실행 ...", | ||
"python.command.python.runCurrentTestFile.title": "현재 단위 테스트 파일 실행", | ||
"python.command.python.runFailedTests.title": "실패한 단위 테스트 실행", | ||
"python.command.python.execSelectionInTerminal.title": "Python 터미널에서 선택 영역/줄 실행", | ||
"python.command.python.execSelectionInDjangoShell.title": "Django 셸에서 선택 영역/줄 실행", | ||
"python.command.jupyter.runSelectionLine.title": "선택 영역/줄 실행", | ||
"python.command.jupyter.execCurrentCell.title": "셀 실행", | ||
"python.command.jupyter.execCurrentCellAndAdvance.title": "셀을 실행하고 다음", | ||
"python.command.jupyter.gotToPreviousCell.title": "이전 셀로 이동", | ||
"python.command.jupyter.gotToNextCell.title": "다음 셀로 이동", | ||
"python.command.python.goToPythonObject.title": " Python 객체로 이동", | ||
"python.snippet.launch.standard.label": "Python", | ||
"python.snippet.launch.standard.description": "표준 출력으로 Python 프로그램 디버그", | ||
"python.snippet.launch.pyspark.label": "Python: PySpark", | ||
"python.snippet.launch.pyspark.description": "PySpark 디버그", | ||
"python.snippet.launch.module.label": "Python: 모듈", | ||
"python.snippet.launch.module.description": "Python 모듈 디버그", | ||
"python.snippet.launch.terminal.label": "Python: 터미널 (통합)", | ||
"python.snippet.launch.terminal.description": "통합 터미널/콘솔에서 Python 프로그램 디버그", | ||
"python.snippet.launch.externalTerminal.label": "Python: 터미널 (외부)", | ||
"python.snippet.launch.externalTerminal.description": "외부 터미널/콘솔에서 Python 프로그램 디버그", | ||
"python.snippet.launch.django.label": "Python: Django", | ||
"python.snippet.launch.django.description": "Django 어플리케이션 디버그", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. s/어플리케이션/애플리케이션 All "어플리케이션" in this change should be replaced by "애플리케이션" There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I didn't notice that "Application" is translated as "응용 프로그램" in Visual Studio. and how about "응용 프로그램" instead? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Then I agree with we should follow what the team has been already translated for now. LGTM. |
||
"python.snippet.launch.flask.label": "Python: Flask (0.11.x 또는 이후 버전)", | ||
"python.snippet.launch.flask.description": "Flask 어플리케이션 디버그", | ||
"python.snippet.launch.flaskOld.label": "Python: Flask (0.10.x 또는 이전 버전)", | ||
"python.snippet.launch.flaskOld.description": "이전 스타일의 Flask 어플리케이션 디버그", | ||
"python.snippet.launch.pyramid.label": "Python: Pyramid 어플리케이션", | ||
"python.snippet.launch.pyramid.description": "Pyramid 어플리케이션 디버그", | ||
"python.snippet.launch.watson.label": "Python: Watson 어플리케이션", | ||
"python.snippet.launch.watson.description": "Watson 어플리케이션 디버그", | ||
"python.snippet.launch.attach.label": "Python: 연결", | ||
"python.snippet.launch.attach.description": "원격 디버깅을 위해 디버거에 연결", | ||
"python.snippet.launch.scrapy.label": "Python: Scrapy", | ||
"python.snippet.launch.scrapy.description": "통합 터미널/콘솔에서 Scrapy 실행" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest "심벌" instead of "기호".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"심벌" is a better translation, but I think it should be a "기호" because it is translated as "기호" in Visual Studio.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Guys, could you please explain to a non-native but enthusiastic learner of Korean, why is "심벌" better than "기호"? Aren't words of Chinese origin more preferable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the case of a technical term, words that write the original pronunciation more than the translated words maybe more effective in transferring meaning. Because it is not only difficult to search for translated term, but also because there are many different translations depending on who translates the same term. But in this case, Visual Studio team has been already translated many term. so, I think we should follow.