Skip to content

[Data]: Have a native Korean speaker review the Korean safety copy #10

Description

@jubalm

Suggested follow-up

Consider having a native Korean speaker review the /ko/ localization introduced in #9, particularly the migration instructions, self-custody terminology, exchange-support language, and scam warnings.

The copy appears broadly understandable, but it is identified as machine-assisted and contains several phrases that may benefit from native review for clarity and naturalness.

Areas that may be worth reviewing

  • self-custody wallet is translated as 본인 지갑, which means “your own wallet” but may not clearly distinguish a non-custodial wallet from an exchange account.
  • ${endpoint}을(를) 통해 exposes the editorial particle form 을(를) directly to users.
  • REP 마이그레이션까지 남은 시간 can mean “time until migration” rather than “time remaining to migrate.”
  • The latest particle changes (REP을/REP이/REP은) depend on whether REP is pronounced “렙” or “알이피” and may benefit from a consistent Korean style.
  • Operational phrases such as 예약된 이더리움 읽기 and 이더리움 메인넷 읽는 중 read like literal translations.
  • 포크 미지원 예정 may sound less definitive than the English “will not support the fork.”

Suggested outcome

Consider reviewing the complete Korean dictionary against the English source of truth with a native Korean speaker.

Potential review points:

  • Choose clear Korean terminology for a self-custody/non-custodial wallet.
  • Replace the visible 을(를) placeholder with natural phrasing.
  • Confirm consistent particles and pronunciation for REP.
  • Check that deadlines and exchange-support statuses retain their intended meaning and urgency.
  • Refine literal system-status translations where more natural Korean is available.

It may also be useful to record the reviewed terminology in the glossary so future Korean updates remain consistent.

References

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions