Microsoft/TypeScript

Use 1 consistent word for the same concept in diagnosticMessages.generated.json in `ko` locale

Open

#51,237 opened on Oct 20, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (6,726 forks)batch import
Experience EnhancementHelp WantedSuggestion

Repository metrics

Stars
 (48,455 stars)
PR merge metrics
 (Avg merge 6d 17h) (9 merged PRs in 30d)

Description

Suggestion

🔍 Search Terms

translation, korean, ko, consistent, concept

✅ Viability Checklist

My suggestion meets these guidelines:

  • [ V ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
  • [ V ] This wouldn't change the runtime behavior of existing JavaScript code
  • [ V ] This could be implemented without emitting different JS based on the types of the expressions
  • [ V ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
  • [ V ] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

In 'lib/ko/diagnosticMessages.generated.json', "computed" is translated into either "계산된" or "컴퓨팅된".

I think it's better to use one consistent word for the same concept rather than using multiple similar words for it.

📃 Motivating Example

💻 Use Cases

Contributor guide

Research direction
Search for all occurrences of 'computed' in 'lib/ko/diagnosticMessages.generated.json' and replace inconsistent translations with a single consistent Korean term.
Tech stack
typescript
Domain
internationalization
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JSON
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90