Korean (Korea) style guide¶

Voice¶

Warm and relaxed. Natural, less formal, grounded in honest conversation. Occasionally fun.
Crisp and clear. To the point. Write for scanning first, reading second. Keep it simple.
Ready to lend a hand. Anticipate the customer's real needs and give the right information at the right time.
Be pleasant. Make explanations feel individualized and enjoyable to read.
Avoid slang. Be careful with colloquialisms. A conversational tone is fine, stay professional.
Choose words for the audience: technical terms for technical readers, common words for consumers.
Keep the style clear, friendly and concise. Use everyday conversational language, not formal technical language.
Free to choose non-standard translations when they keep the intent of the source text.
Do not translate literally. Consider the intent of the text and what the customer needs to complete the task.

Flexibility¶

Modify or rewrite translated strings so they are natural for Korean customers. Understand the whole intent of the sentence, paragraph and page, then write as if you author the content. Remove unnecessary content when needed.
en More beautiful, more flexible, more you. And very, very fast. -> 더 멋지고 더 유연하게. 놀라운 속도를 자랑하는 나만의 Windows.
en The desktop that you're used to—with its taskbar, folders, and icons—is still here and better than ever, with a new taskbar and streamlined file management. -> 작업 표시줄, 폴더, 아이콘 등 이전에 사용하던 데스크톱 환경을 그대로 계승하고 더욱 발전시켜 새로운 작업 표시줄과 최적화된 파일 관리 기능을 제공합니다.
en These lightweight PCs have fantastic battery life, and are a great option for doing stuff on the go. -> 이 가벼운 PC는 매우 뛰어난 배터리 수명을 자랑하며 이동 중에도 여러 가지 작업을 할 수 있도록 만들어 줍니다.

Words and phrases to avoid¶

Avoid an unnecessarily formal tone.
어려운 한자어를 사용하기보다는 쉽게 이해할 수 있는 우리말 표현을 사용해 주십시오.
또한 서술형 명사(작동, 동작, 설치, 제거, 검색, 감사 등)를 수식하는 표현으로 ‘수행‘, ‘실행, ‘제공‘ 등은 사용하지 않는 것이 좋습니다.
en Failed to refresh it.: 새로 고침 수행에 실패했습니다. -> 새로 고치지 못했습니다.
en Supply a suitable password.: 알맞은 암호를 제공하십시오. -> 알맞은 암호를 입력하세요.
en For more information about LUN types, see Overview of LUN Types.: LUN 유형에 대한 자세한 내용은 LUN 유형 개요를 참조를 하십시오. -> LUN 유형에 대한 자세한 내용은 LUN 유형 개요를 참조하세요.
en This document provides an overview of those features.: 이 문서에서는 이러한 기능들에 대한 개요를 제공합니다. -> 이 문서에서는 이러한 기능을 간략하게 설명합니다.
en In the <ui>Remove Virtual Machine</ui> dialog box, click <ui>Yes</ui> to confirm the removal.: <ui>가상 컴퓨터 제거</ui> 대화 상자에서 <ui>예</ui>를 클릭하여 제거를 수행합니다. -> <ui>가상 컴퓨터 제거</ui> 대화 상자에서 <ui>예</ui>를 클릭하여 제거합니다.
en Follow these steps to change your password.: 이 절차들을 수행하여 암호를 변경하십시오. -> 암호를 변경하려면 다음 단계를 따르세요.
Use the ending form 세요, not 십시오. It gives a more natural, conversational register. Use 십시오 for EULA and legal content, which need a formal tone.
다음 단원을 참조하십시오. -> 다음 단원을 참조하세요.
파일을 사용하지 마십시오. -> 파일을 사용하지 마세요.
Apple's macOS and its help still use 십시오 (다시 시도하십시오.); Glyphs, Microsoft and Adobe's current help use 세요. FontLab uses 세요 on both platforms.

Frequent errors¶

Avoid literal, word-to-word expressions.
en This app and all of its info will be removed from you PC. These apps and all of their info will be removed from your PC.: 이러한 앱과 모든 정보가 PC에서 제거됩니다. -> 다음의 앱과 앱의 모든 정보가 PC에서 제거됩니다.
en Set permissions for this app: 이 앱에 대한 사용 권한 설정 -> 이 앱의 사용 권한 설정
en Turn this off if you don't want to worry about extra roaming charges for data on a cell phone or broadband plan.: 휴대폰이나 광대역 요금제에서 데이터에 대한 추가 로밍 요금에 대해 신경 쓰지 않으려면 이 옵션을 해제합니다. -> 휴대폰이나 광대역 요금제에서 추가 데이터 로밍 요금을 내지 않으려면 이 옵션을 해제합니다.
en The application does not support printing, playing or sending at this time.: 지금은 응용 프로그램에서 인쇄, 재생 또는 보내기를 지원하지 않습니다. -> 응용 프로그램에서 인쇄, 재생 또는 보내기를 지원하지 않고 있습니다.
en PowerPoint couldn’t find ^1.: PowerPoint에서 ^1이(가) 검색되지 않습니다. -> ^1을(를) 찾을 수 없습니다.
en Do you want to continue?: 계속하기를 원하십니까? -> 계속하시겠습니까?

Word choice¶

Use approved terminology for key terms, technical terms and product names.
Product names are normally not translated. Feature names can usually be translated.
en accessibility: 내게 필요한 옵션 -> 접근성
en homepage: 홈페이지 -> 홈페이지
en trusted connection: 트러스트된 연결 -> 신뢰할 수 있는 연결
Prefer short, simple, everyday words. They save space on screen and read faster. Precise words add clarity.
영문 표현에 따라 번역하십시오. 어색하거나 친숙하지 않은 표현은 자연스러운 우리말 표현으로 바꾸고 일상 생활에서 사용하는 용어나 문구를 사용해야 합니다.
en E-mail address -> 메일 주소
en Online store -> 온라인 스토어
en Home page -> 홈페이지

Word-to-word translation¶

Avoid word-to-word translation. It makes the tone stiff and unnatural.
Check the source text in the live pages. Do not translate a list of strings without context.
Split the text into separate sentences when needed. Simplify. Omit descriptors to make the text snappier.
en Your life, connected through the cloud -> correct 클라우드를 통해 일상 연결, incorrect 클라우드를 통해 연결된 삶
en Whether you're at work or at play, you can take your friends, files, and favorite sites with you. -> correct 근무 중이든 여가를 즐기는 중이든 관계없이 언제 어디서나 친구, 파일 및 즐겨찾는 사이트를 사용할 수 있습니다., incorrect 일하거나 놀거나 관계없이 친구, 파일 및 즐겨찾는 사이트를 휴대할 수 있습니다.
en Stay in touch with Windows. -> correct Windows와 관련된 소식을 전해드립니다., incorrect Windows와 연락하세요.

Inclusive language¶

Comply with local language laws.
Use plain language: straightforward, concrete, familiar words. Use several clear words instead of one complicated term.
Be careful when naming parts of the world. Do not name politically disputed cities, countries or regions. Use equivalent references: do not mix countries with states or continents.
In text and images, show diverse perspectives and circumstances. Show a variety of people in many professions, educational settings, locales and economic settings.
Never generalize or stereotype people by region, culture, age or gender, even with a positive stereotype. When representing job roles, choose names that reflect a variety of gender identities and cultural backgrounds.
Never use profane or derogatory terms.
Never use slang that could count as cultural appropriation.
Never use terms that carry unconscious racial bias, or terms tied to military actions, politics, or controversial historical events and eras.
master/slave -> primary/secondary; 주인/노예 -> 기본/보조
demilitarized zone (DMZ) -> perimeter network; 비무장지대(DMZ) -> 경계 네트워크
phony monk -> Buddhist monk/monk; 땡중 -> 스님
country bumpkin -> country person/people; 촌놈 -> 시골 사람
woman doctor; woman teacher -> doctors; teachers; 여의사, 여교사 -> 의사, 교사
mother or father -> parent; 엄마/아빠 어머니/아버지 -> 부모

Avoid gender bias¶

Use gender-neutral alternatives for common terms. Avoid compounds that contain gender-specific terms.
여배우 여작가/여류작가 -> 배우 작가
세일즈맨 -> 영업 담당자
스튜어디스 -> 승무원
학부형 -> 학부모
편부모 가족/결손가족/미혼모/미혼부 -> 한부모 가족
Never use gendered pronouns (그, 그녀등) in generic references.
Rewrite to use the substitutive form, or omit the pronoun. Avoid demonstrative pronouns such as 그/이/저 where possible.
Do not use a possessive case. Use 문서, not 그의문서.
Refer to the person's role: 회원, 독자, 직원, 고객, 클라이언트.
en If the user has the appropriate rights, he can set other users' passwords. -> A user with the appropriate rights can set other users' passwords.; 사용자에게 적절한 권한이 있는 경우, 그는 다른 사용자의 암호를 설정할 수 있습니다. -> 적절한 권한이 있는 사용자는 다른 사용자의 암호를 설정할 수 있습니다.
en A developer needs access to servers in his development environment, but he doesn't need access to the servers in Azure. -> Developers need access to servers in their development environments, but they don't need access to the servers in Azure.; 개발자는 그의 개발 환경에서 서버에 액세스해야 하지만, Azure의 서버에는 액세스할 필요가 없습니다. -> 개발자는 개발 환경의 서버에 액세스해야 하지만, Azure의 서버에는 액세스할 필요가 없습니다.
en When the author opens her document …. -> When the author opens the document ….; 작성자가 그녀 자신의 문서를 열 때…. -> 작성자가 문서를 열 때….
en To call someone, select his name, select Make a phone call, and then select his number. -> To call someone, select the person's name, select Make a phone call, and then choose the number you'd like to dial.; 전화를 걸려면 그 이름을 선택하고 “통화”를 선택한 다음, 전화 번호를 선택합니다. -> 전화를 걸려면 원하는 사람의 이름을 선택하고 “통화”를 선택한 다음, 전화를 걸 번호를 선택합니다.
When you write about a real person and need a pronoun, use the pronoun that person prefers, whether 그, 그녀, 그들 or another. Gendered pronouns are fine for real people who use them.

Accessibility¶

Use the shared accessible content guidance for identity, readable text and input methods. Preserve the difference between selecting an object, invoking a command and performing a gesture; follow interface actions.

Abbreviations¶

Use an established abbreviation only when readers can recognize it in context. Preserve spaces, punctuation and case that belong to the approved form. Control line wrapping through layout; do not insert a nonbreaking space inside an identifier or remove part of a name to make it fit.

Acronyms¶

Keep the approved spelling and case of an acronym, including mixed-case forms. Expand it when this audience needs the explanation; an expansion is not required merely because the text is translated. Preserve identifiers exactly. See names and formats.

Capitalization¶

Korean has no capitalization. Capitalization applies only to English text kept as is, such as product names or abbreviations.

Compounds¶

Keep compounds understandable and clear. Avoid overly long or complex compounds. Unintuitive compounds hurt intelligibility and usability.
Space matters in Korean compounds. Put no space between two words that together carry the compound meaning.
구름다리 (O), 구름 다리 (X)
질그릇 (O), 질 그릇 (X)
돌다리 (O), 돌 다리 (X)
손가방 (O), 손 가방 (X)
솜사탕 (O), 솜 사탕 (X)
대한민국 (O), 대한 민국 (X)
높푸르다 (O), 높 푸르다 (X)
오가다 (O), 오 가다 (X)
A space can change the meaning: 작은 아버지 means a father with short height, 작은아버지 means younger brothers of a father.

Font localization¶

Check the selected font’s script coverage, shaping, emphasis and legibility in the actual output. Do not change a font name, size or weight during translation unless the product specification calls for it. Preserve the user’s font choice and font specimens. Follow scripts and typography for rendering checks, and messages and variables for semantic markup.

Localizing colloquialism, idioms, and metaphors¶

Culture-centric colloquialisms, idioms and metaphors are allowed.
영문 모던 보이스의 특성은 영미문화권에 특화된 구어체, 관용적 표현, 은유법을 사용하여 표현합니다. 모던 보이스에서는 영미문화권에 특화된 구어체, 관용적 표현, 은유법(통칭하여 "구어체")을 사용할 수 있습니다.
Never replace the source colloquialism literally with a Korean one: it can sound rude or impolite. Translate the intended meaning instead.
Rephrase the sentence when a colloquialism cannot be translated as it is.
Use everyday, conversational words and expressions, not a classic tone and voice.
다음 중 한 가지 방식으로 영문 의미를 적절하게 번역하십시오.
직역하면 사용자에게 무례하고 공손하지 않은 번역이 되는 경우 영문에 사용된 구어체를 그대로 옮기면 안 됩니다. 단, 어떠한 경우에도 영문에서 의도한 의미는 훼손하면 안 됩니다.
구어체가 강한 표현이 포함되어 있을 경우, 최대한 의미에 맞게 문장을 재구성해 주십시오. 단, 일상 생활에서 사용할 것 같은 자연스러운 용어 및 표현을 사용해야 합니다.
en Share files and info with people you know or send info to another app, without leaving the app you're in. You can email photos to your mom, update your Facebook status, or send a link to your note-taking app. -> 현재 앱에서 나가지 않고 파일과 정보를 아는 사람과 공유하거나 정보를 다른 앱으로 보낼 수 있습니다. 사진을 엄마에게 메일로 보내거나 Facebook 상태를 업데이트하거나 메모 앱으로 링크를 전송할 수 있습니다. Consider replacing Facebook with messaging or social networking status, by local market.
en Use all of the devices that are connected to your PC, both wired and wireless. You can print from an app, sync with your phone, or stream your latest home movie to your TV. -> PC와 유선, 무선으로 연결된 모든 장치를 사용합니다. 앱에서 인쇄하고, 전화와 동기화하고, 최신 홈무비를 TV에 스트리밍할 수 있습니다. Make sure streaming is available in all markets.
en With Windows 10, you can set up your PC in no time -> Windows 10에서는 PC를 빠르게 설정할 수 있습니다. Replace the colloquialism in no time with a Korean colloquialism of the same meaning where possible.
en The Mail Migration add-on does not work with Microsoft Office Outlook or third-party mail apps like Thunderbird, IncrediMail, or Eudora. -> 메일 마이그레이션 추가 기능은 Microsoft Office Outlook이나 Thunderbird, IncrediMail, Eudora 등의 타사 메일 앱에서 작동하지 않습니다. Validate whether the named third-party apps apply to the local market.
en At home, work, or school—do everything you need to in record time? -> 가정, 직장 또는 학교에서 필요한 모든 작업을 신속하게 수행합니다. Replace the colloquialism in record time with a Korean colloquialism of the same meaning where possible.

Modifiers¶

Translate a modifier into another part of speech where it reads better: as a verb, subjective complement or adverb.
en Invalid value for the certificate validator type.: less fluent 인증서 유효성 검사기 형식에 대한 잘못된 값입니다. -> 인증서 유효성 검사기 형식의 값이 잘못되었습니다.
en Setup is optimizing your system for better performance.: less fluent 설치 프로그램이 더 좋은 성능을 위해 시스템을 최적화하고 있습니다. -> 설치 프로그램이 성능 향상을 위해 시스템을 최적화하고 있습니다. better performance becomes to increase performance.
en For more effective troubleshooting, use this error message.: less fluent 보다 효율적인 문제 해결을 위해서 이 오류 메시지를 사용하십시오. -> 보다 효율적으로 문제를 해결하려면 이 오류 메시지를 사용하세요. more effective troubleshooting becomes to troubleshoot more effectively.

Nouns¶

Korean nouns do not copy English plural inflection. The suffix 들 can mark plurality, but it is not needed in every plural reference. Preserve number and scope through the complete sentence, especially when a count comes from a variable.

Pronouns¶

Pronouns are seldom used: they decrease readability. Omit the translation when the meaning is clear without it. Translate a pronoun specifically when the context needs it clarified.
en To use this card, you will have to use a smart card or a certificate. -> 이 카드를 사용하려면 스마트 카드 또는 인증서를 사용해야 합니다. you is omitted.
en Are you sure you want to delete this folder? This will delete all feeds in the folder. -> 이 폴더를 삭제하시겠습니까? 이 폴더를 삭제하면 폴더에 있는 모든 피드가 삭제됩니다. The second This is kept and translated as Deleting this folder for clear meaning.
en The object has changed. Do you want to update it? -> 개체가 변경되었습니다. 업데이트하시겠습니까? it is omitted.
en Verify your entry and try again. -> 입력 내용을 확인하고 다시 시도하세요. your is omitted.
en An Online Service notification email has been sent to your Subscription Contact. -> 온라인 서비스 알림 전자 메일이 귀사의 구독 담당자에게 발송되었습니다. your is kept and translated as your company.
en Do not warn me about this problem again -> 이 문제에 대한 경고 메시지 다시 표시 안 함 me is omitted.
en Send a new Welcome Kit based on my new Media selection. -> 선택한 미디어에 따라 웰컴 키트를 보내 주세요. my is omitted.
en Only allow my team members to see my email addresses -> 내 팀 멤버만 내 전자 메일 주소를 볼 수 있도록 허용 my is kept for clear meaning.

Punctuation¶

English often ends a sentence with a colon or semicolon. In Korean use a period when the sentence ends with a verb in ~하세요 or ~합니다 style, whatever punctuation English uses.
Different punctuation from the English source can cause functional problems in software localization.

Sentence fragments¶

Use sentence fragments where possible. They are short, to the point, and convey a conversational tone.
간단하면서 문법적으로 올바른 표현을 사용하십시오. 가능한 경우, 소유 중심의 영어식 표현은 존재 중심의 우리말 표현으로 바꿔 주십시오.
en Here’s how.: long 다음을 실행하려면 이 방법을 사용하십시오. -> fragment 방법 or 다음과 같이 하세요.
en You may not have appropriate rights.: long 필요한 사용 권한을 가지고 있지 않을 수 있습니다. -> fragment 필요한 권한이 없을 수 있습니다.
en This domain already has a one-way trust relationship with the specified realm.: long 이 도메인은 지정한 영역과 단방향 트러스트 관계를 이미 갖고 있습니다. -> fragment 이 도메인은 지정한 영역과 단방향 트러스트 관계를 이미 맺고 있습니다.
en This isn’t used when running on Microsoft Office 365...: long Microsoft Office 365을 사용하는 경우 이 기능이 활성화되지 않습니다. -> fragment Microsoft Office 365에서는 이 기능을 사용할 수 없습니다.
en Get the app?: long 앱을 가져오시겠습니까? -> fragment 앱을 받을까요?

Verbs¶

Translate verbs in error messages consistently. Be concise without changing the meaning of the source string.
en An error occurred while trying to create the database. -> 데이터베이스를 만드는 동안 오류가 발생했습니다. The sentence can be rephrased to An error occurred while creating the database.
en The engine input file has the wrong version. -> 엔진 입력 파일의 버전이 잘못되었습니다. Rephrase has with is.
en Reinstall if existing file has a different version. -> 기존 파일이 다른 버전인 경우 다시 설치하세요. Rephrase has with is.
Translate the English gerund of a continuous operation as ~ 하고 있습니다 or ~ 하는 중. A gerund is often used in a title sentence, so check whether it expresses a continuous operation.
en Saving text file… -> 텍스트 파일을 저장하는 중… Continuous operation.
en Now saving temporary file. -> 임시 파일을 저장하고 있습니다. Continuous operation.
en Completing installation… -> 설치 완료 중… Continuous operation.
en Completing the New Connection Wizard -> 새 연결 마법사 완료 Gerund in a title sentence.
Apply tenses by the English source. Use simple present as the basic tense unless the context needs another tense.
소스에 따라 번역문에 시제를 적용해 주십시오. 기본 시제로 현재 시제를 사용하되, 문맥에 따라 다른 시제를 적용할 수 있습니다.

Localization considerations¶

Adapt the translated text to the local language, customs and standards.
The language must look and feel originally written in Korean, with idiomatic syntax and terminology, and stay terminologically consistent.

Applications, products, and features¶

Preserve approved product names, identifiers and version strings exactly. Do not add a decimal component to a version or translate a protected name. Use names and formats for shared rules.

Software considerations¶

Check the localized text in its actual interface using the localization review.

Interface labels and messages¶

Korean interfaces use two registers, and a string belongs to exactly one. The Korean localization guide gives the full table with sources.

A command, button, option or title is a noun phrase without particles: 앵커 추가, 글리프 크기. A Sino-Korean or loan action noun stands bare (저장, 삭제, 다운로드); a native verb takes -기 (열기, 닫기, 내보내기). Do not write 저장하기, and do not end a label in 합니다.
A state is nominal: ~됨, ~ 없음, ~ 중, ~할 수 없음. Example 자동 저장됨, 업데이트 확인 중…
A full sentence ends in ~합니다., ~하세요. or ~하시겠습니까? Never mix in ~해요, ~한다 or ~이다.
Do not address the user with 당신 or 귀하, and do not stack honorifics: ~하시기 바랍니다 and ~하실 수 있습니다 become ~하세요 and ~할 수 있습니다.
Write ~할 수 있습니다, not ~하는 것이 가능합니다; ~해야 합니다, not ~할 필요가 있습니다.
Prefer the plain word to officialese: 위, 아래, 이, 반드시, not 상기, 하기, 본, 필히.

Particles after names and variables¶

A particle attaches to the word before it with no space, also after a Latin name, a digit, a closing quotation mark or a variable: Finder에서, %1이(가).
After a fixed Latin name, choose the particle by how the name is said: FontLab을, OpenType은, Apple이, Unicode를, PDF를, URL을.
After a variable, first try to add the class noun, which settles the particle: ‘%1’ 파일을 열 수 없습니다. A counter does the same: %n개를. Use the double form (을(를), 이(가), 은(는), 과(와), (으)로) only when neither is possible.

Spacing, numbers and quotation marks¶

Follow 한글 맞춤법 for word spacing: particles attached, dependent nouns apart (할 수 있습니다, 확인 중, 안 함), 하다 and 되다 attached to their noun (다운로드할 수 없습니다, not 다운로드 할 수 없습니다).
A change of script adds no space by itself. Put a space only at a word boundary: PostScript 이름, AFM 파일.
Attach a Korean counter or unit to the number: 3개, %1바이트. The standard also permits a space; FontLab attaches, as Qt and Apple do. Write 25% without a space, and 1,234,567.89.
Korean has one numerus form in Qt and one plural category in CLDR. Write one form that is right for 1 and for 100, and do not add 들 after a count.
Use half-width punctuation. Parentheses attach to the word before them: 중국어(번체).
Quote a name with curly single marks, ‘모든 서체’, as macOS does and as the national punctuation rules allow for singling out a word. Do not use 「」 in interface text.
Spell loanwords by 외래어 표기법: 브러시, 셰이프, 메시지, 콘텐츠, 디렉터리; not 브러쉬, 쉐이프, 메세지, 컨텐츠, 디렉토리.

Arrow key names¶

In prose, name an arrow key in full, as below. In a shortcut label Qt's Korean catalog shows only 왼쪽, 오른쪽, 위, 아래.
Home key -> Home 키
End key -> End 키
Up arrow key -> 위쪽 화살표 키
Down arrow key -> 아래쪽 화살표 키
Left arrow key -> 왼쪽 화살표 키
Right arrow key -> 오른쪽 화살표 키

Error messages¶

Preserve state, count, negation and obligation when translating a message. Follow messages and variables for placeholder names, markup and permitted reordering; local grammar never authorizes a parser change.

An error message tells the user an error must be corrected for the program to keep running. It can prompt an action or report an error that requires rebooting the computer.
Make the target translation natural and empathetic, not robot-like.
Use consistent terminology and language style. Do not just translate the US strings as they appear.
English error messages tend to be shorter and sometimes omit the verb be. In Korean use the fully developed form.
Translate an error message in ~니다 style and end the Korean text with a period, even when the English sentence ends with a colon. When the English text is a phrase, or ends with a colon plus a placeholder, follow the rules below.
en Specified proxy address ""{0}"" is invalid: {1} -> 지정한 프록시 주소 ""{0}""이(가) 잘못되었습니다. {1} English ends with a colon, Korean ends with a period because of the ~합니다 style.
en To install the prerequisites, choose one of the following: -> 필수 구성 요소를 설치하려면 다음 중 하나를 선택하세요. English ends with a colon, Korean ends with a period because of the ~하세요 style.
en Error Accessing URL Address -> URL 주소에 액세스하는 동안 오류 발생 English is not a full sentence and ends without punctuation, so Korean ends in an abbreviated form and without a period.
en Error attempting to read from the source install database: [2] -> 원본 설치 데이터베이스를 읽는 동안 오류 발생: [2] English ends with a colon plus a placeholder, so use the same style in Korean.
Standardize standard phrases. The English source uses different forms for the same thing: keep one consistent translation style.
en Cannot …, Could not … -> ~ 할 수 없습니다. Example 파일을 복사할 수 없습니다. Do not translate could not into past tense.
en Failed to …, Failure of … -> ~ 하지 못했습니다. Example 파일을 복사하지 못했습니다. When failure is a noun, translate it as 오류 or 실패, by context.
en Cannot find …, Could not find …, Unable to find …, Unable to locate … -> ~ 찾을 수 없습니다. Example 파일을 찾을 수 없습니다.
en Not enough memory, Insufficient memory, There is not enough memory, There is not enough memory available -> 메모리가 부족합니다. Example 파일을 저장하는 데 필요한 메모리가 부족합니다.
en ... is not available, ... is unavailable -> ~ (사용) 할 수 없습니다. Example 원본 파일을 사용할 수 없습니다. Translation varies by context: Internet access is not available -> 인터넷에 액세스할 수 없습니다.
en An error occurred while …, An error occurred when …, Error while …, Error when … -> ~하는 동안 오류가 발생했습니다. Example 파일을 만드는 동안 오류가 발생했습니다. Use ~하는 동안, not ~하는 중.
With placeholders, find out what replaces the placeholder so the sentence stays grammatical.
INI file "%1!-.200s!" section means INI file "<string>" section.
When placeholders contain numbers (%1, %2), the order can change from the English text. When the same placeholders carry no numbers, never change the order.
en Setup run at %1 on %2. -> %2의 %1에서 설치 프로그램이 실행됩니다. %2 can come before %1 because the placeholders contain numbers.
en Setup run at %s on %s -> %s(위치: %s)에서 설치 프로그램이 실행됩니다. Two %s placeholders with no numbers: the order cannot change. Parentheses may be needed.
en Step %d of %d -> %d 단계/전체 %d 단계 %d of %d uses a slash.
en Page %d of %d -> %d/%d 페이지 %d of %d uses a slash.
Add the proper measurement unit after a %d placeholder, by context.
en The string %s must be at least %d character(s) long. -> %s 문자열은 %d자 이상이어야 합니다 %d is a number, so the unit 자 (character) follows with no space.
en %d document(s) pending for %s -> %d개의 문서가 %s에 대해 대기 중입니다. The unit 개 (number) follows %d.
en You have %d days remaining before you must purchase a product license. -> %d일 후에는 제품 라이선스를 구입해야 합니다. The unit 일 (day) follows %d.
en A required keyword was not found near line %d. -> %d 줄 근처에서 필요한 키워드를 찾을 수 없습니다. Line %d becomes %d 줄, not 줄 %d, for readability. The word order may change.
Use double postpositions after placeholders, since the replacing word is unknown: 은(는), 이(가), 을(를), 과(와), (으)로.
en Unable to find the specified group "%1!s!" -> 지정한 그룹 '%1!s!'을(를) 찾을 수 없습니다.
en {0} must have the same user count as {1}. -> {0}의 사용자 수는 {1}과(와) 같아야 합니다.
en An error occurred while moving the FSS data directory from {0} to {1}. -> FSS 데이터 디렉터리를 {0}에서 {1}(으)로 이동하는 동안 오류가 발생했습니다.
en {0} is already being used. Verify your entry and try again. -> {0}은(는) 이미 사용 중입니다. 입력 내용을 확인하고 다시 시도하세요.
en The certificate issued by %1!s! will be permanently deleted. Do you want to continue? -> %1!s!이(가) 발급한 인증서가 영구적으로 삭제됩니다. 계속하시겠습니까?

Keyboard shortcuts¶

Keyboard shortcuts are the underlined or highlighted letters in menu options, commands and dialog boxes. They help the user perform tasks faster.
Slim characters such as I, l, t, r, f as keyboard shortcuts: no.
Characters with downstrokes such as g, j, y, p, q as keyboard shortcuts: no.
Extended characters as keyboard shortcuts: no.
An additional letter in brackets after the item name as keyboard shortcut: usually no. It happens when the English source uses an additional letter as the shortcut. If the source is not fixed, keep it as is.
A number in brackets after the item name as keyboard shortcut: usually no. Use a number when the English source includes a number as part of the text. Example source Memory 1, example target 메모리(&1)
A punctuation sign in brackets after the item name as keyboard shortcut: yes.
Duplicate keyboard shortcuts when no other character is available: no.
No keyboard shortcut assigned when no more characters are available (minor options only): no.
English strings mark the shortcut with an ampersand & inside the string or word. In Korean strings put ampersand (&) + uppercased keyboard shortcut at the end of the word or string.
en OK: 확인 -> 확인(&O)
en Require 256-bit encryption: 256비트 암호화 필요 -> 256비트 암호화 필요(&2)
en MIME: MIME -> MIME(&M)
When the English string is only numbers and the shortcut is assigned to a number, the translation equals the source string.
en 1: 1(&1) -> 1
en 100%: 100%(&1) -> 100%
en 800 x 600: 800 x 600(&8) -> 800 x 600
Access key: a subtype of keyboard shortcut. A letter or number the user types to reach UI controls that have text labels. Assigned to top-level controls so the user can move through the UI quickly. Example F in Alt+F. In UI localization H&ome. Most access keys are used with the Alt key.
Key tip: the letter or number that appears in the ribbon when Alt is pressed. In UI localization the key tip is the last character after the ` character. Example HomeH`
Shortcut key: a subtype of keyboard shortcut. A key the user types to perform a common action without going through the UI. Not available for every command. Examples Ctrl+N, Ctrl+V. Most shortcut keys are used with the Ctrl key. Ctrl+letter combinations and function keys F1 through F12 are usually the best choices.

Keys¶

The keyboard is the primary input device for text. Most actions must also work from the keyboard, for accessibility and efficiency. You use keys, key combinations and key sequences.
Key names such as arrow keys, function keys and numeric keys appear in normal text, not in small caps.
Add the word 키 after a translated key name, with a space between the key name and 키.
For key combinations, do not add 키 after the key names.
Microsoft surrounds key names and key combinations with angle brackets < > in software strings. FontLab does not: write key names without brackets in the interface and in help, as Qt's own Korean catalog and macOS do. Read the software examples below without their brackets.
In documentation translation, manuals and online help included, do not use angle brackets for key names.
Uppercase only the initial letter of a key name. Examples Shift 키, Ctrl 키, Alt 키, Esc 키
en Press SPACEBAR or ENTER to activate this control. -> software 스페이스바 또는 <Enter> 키를 눌러 이 컨트롤을 활성화하세요., documentation 스페이스바 또는 Enter 키를 눌러 이 컨트롤을 활성화하세요. spacebar needs no < > in either case and becomes 스페이스바.
en Press Ctrl+Alt+Del using the keyboard. -> software 키보드를 사용하여 <Ctrl+Alt+Del>을 누르세요., documentation 키보드를 사용하여 Ctrl+Alt+Del을 누르세요. Never use 키 for a key combination.
en Value may be edited through a dialog box. Press Alt+Down to open the dialog box. -> software 대화 상자를 사용하여 값을 편집할 수 있습니다. <Alt+아래쪽 화살표>를 눌러 대화 상자를 여세요., documentation 대화 상자를 사용하여 값을 편집할 수 있습니다. Alt+아래쪽 화살표를 눌러 대화 상자를 여세요.
Surround arrow key names with < > in software, not in manual or online help: en Use the up and down arrow keys. -> software <위쪽 화살표> 키 또는 <아래쪽 화살표> 키를 사용하세요., documentation 위쪽 화살표 키 또는 아래쪽 화살표 키를 사용하세요.
Surround function key names with < > in software, not in manual or online help: en Press F1 for more help. -> software 자세한 내용을 보려면 <F1> 키를 누르세요., documentation 자세한 내용을 보려면 F1 키를 누르세요.

English pronunciation¶

Pronounce English terms and product names left unlocalized the English way.
When Korean has an established pronunciation for a common term such as server, use the local pronunciation.
Adapt pronunciation to the Korean phonetic system when the original sounds very awkward in Korean.
Refer to the Korean Alphabetization of Foreign Words at https://www.korean.go.kr/.
RADIUS: 레디우스
RAS: 라스
ISA: 아이사
LAN: 랜
WAN: 완
WAP: 왑
MAPI: 매피
POP: 팝
Skype: [skaip]
ICMP: 아이씨엠피
URL: 유알엘
TCP/IP: 티씨피/아이피
Rqc.exe: 알큐씨쩜이엑스이
HTML: 에이치티엠엘
SQL: 에스큐엘, 씨퀄
In URLs, leave out http://. Read the rest of the URL entirely.
http://www.microsoft.com/korea: 더블유더블유더블유 쩜 마이크로소프트 쩜 씨오엠 슬래시 코리아 or 더블유더블유더블유 쩜 마이크로소프트 쩜 씨오엠 슬래시 케이오알이에이
Most punctuation marks are implied by the sound of the voice: ?, !, :, ;, ,
En dash – emphasizes an isolated element. Pronounce it as a comma, a short pause.
Pronounce special characters such as /, \, ˘, <, >, +, - using the approved Korean translations.

Tone¶

Match the tone to the target audience: informal, playful and inspiring for most products and games; formal, informative and factual for technical texts.

Local usage¶

Use respectful, natural requests and check machine suggestions against context. Preserve brand spelling and variables; review particles after substituted text, and distinguish full-sentence messages from noun-phrase labels.

FontLab terminology decisions (2026-10-04)¶

Follow the canonical FontLab glossary, including its approval status and contextual notes. The current choices are:

Concept	Wording
OpenType lookup	프로시저
Fusion, using the fallback Welder	용접공
FontAudit, visible name	폰트오디트
Pin, a named point in an element	핀

For OpenType lookup, the default is the translation of procedure. Retain a different term only with strong OpenType-specific evidence; the explicit German, French, Polish and Russian decisions take precedence. Ordinary search, dictionary lookup and code keywords are separate senses. Preserve literal lookup, lookupflag, LookupList and identifiers in code. Keep individual rules distinct from the procedures that group them.

Use the FontAudit name above in visible interface text and prose; preserve FontAudit in code and identifiers. In non-Latin scripts it is a phonetic transliteration, including Chinese. A proposed glossary entry remains proposed; this table does not confer native-team approval.

Keep marked and unmarked menu labels consistent after accounting for Qt mnemonic & and appended shortcuts. In Dimensions and Glyph Window preferences, aim for labels no longer than 120% of the source; preserve meaning when that target is impractical. Omit redundant font or colour wording when context supplies it. TTH options may omit the verb “use” and abbreviate TrueType hinting as TTH. Help may be longer, but quoted interface labels must match the final UI.

FontLab Rapid tool¶

FontLab names this tool 래피드. The name stays recognizable in the interface and Quick Help; it does not mean an ordinary fast or quick action. Use the canonical TS spelling and translate the surrounding grammar, as in 래피드로 그리기. The contrast classifications containing English rapid use the ordinary adjective instead. See the localization guide for the current terminology and source-version checks.

Quick Help: action and property-bar contexts¶

Use the current control's label. ActionRemoveCorners has 잉크 트랩 제거, while prose elsewhere may use 잉크트랩. ActionLockMetrics and Bar_Metrics use 연결 for binding sidebearings. Preserve full sidebearing names in formula explanations; compact LSB and RSB labels need not replace them.

The processing dialog is 동작 (DlgActions). Do not borrow the ThePropertyPanel heading 작업 for its command path. The actual Variations panel title is 베리에이션; MainWindow's action tooltip is 변형 패널. The Measurements panel title is 측정값, while its menu tooltip is 측정 패널.

ActionSetMetrics fills its selectors at runtime. Use 동일한 값으로 설정, 자동 + 조정, 지정값만큼 증가, 지정값만큼 감소 and 아무 작업 안 함, from FontLabUI.action_setmetrics. The designer's sample text does not override these choices. ActionSetWidth uses 양쪽 조절, 왼쪽 조절 and 오른쪽 조절.

Bar_Ellipse uses 직사각형, 지우기 직사각형 and 곡선 장력이 있는 타원. Bar_Shape uses 앵커에 연결된 컴포넌트 and 위치 초기화. Keep these distinct from similar labels in other toolboxes. Bar_Glyph's Recipe field is 조합식, while controls in other contexts retain 레시피. The current thickness-editing tool is 줄기.

Bar_Pin's mark-feature option requires 글리프 구성에 사용. This is a construction setting, not the anchor-cloud view toggle. Preserve the shorter draft source where it omits that requirement.

Color names are context-specific. Green is 초록색 in ClassesPanel and 녹색 in ColorFlagsWidget. Aquamarine is 아쿠아마린색 in ColorFlagsWidget and 연한 청록색 in ColorGuideWidget.

Quick Help: inherited source errors and dialog labels¶

Scribble's actual control is 겹침 (Overlap), not Engraving's 들여쓰기 (Indent). Positive values expand the generation area and negative values inset it. Values use a 1000-UPM scale and are converted for the current font's UPM. The Warp section caption is 모양; its copied slant-right help does not describe the caption.

Miter limits are width-relative factors, not lengths in font units. Add Stroke uses the stroke thickness; Expand Contour uses the expansion distance and its visible 각진 연결 label. A logarithmic axis-map description should not promise a slow-then-fast curve. Ellipse tension changes handle length; increasing it throughout the allowed range does not continually approach a circle.

Use 위치 배율 조절 for the Axis Graph button and 비례 조정 for the range-change confirmation button. Keep English axis/style examples such as Bold when they identify runtime values.

DlgCreateGlyphs uses 글리프 만들기, 기존 글리프 다시 만들기, 새 글리프 편집용으로 열기 and 간단한(FLS5) 구문 사용. DlgComponentGlyphsDelete uses 조합 글리프 and 레시피 보존. In Find Outline, the section captions are 찾기 and 바꾸기; the control is 현재 선택 항목 사용. A preview description may still say that it is a preview.

Quick Help: dialogs and font naming¶

Use the visible titles 요소 참조 추가, 문맥 미리보기, 마스터 미리보기 and 이형 선택자 for the corresponding dialogs. Class-derived English headings can differ from their actual titles.

DlgImportMetrics uses 글자폭 교체, 사이드베어링 교체 and 메트릭스 표현식 교체. Advance-width import follows the chosen sidebearing option; it does not always preserve left/right balance. DlgRemapGlyphNames uses 이름 변경 테이블 and 인코딩에 따라 이름 바꾸기 / 테이블에 따라 이름 바꾸기.

Use 환경 설정 for DlgPreferences commands. Preferences files are INI, with native PLIST support on macOS; do not describe them as JSON or PREFS. The Workspaces dialog uses 작업 공간.

FontsPanel uses 스타일 이름 만들기, 스타일링 그룹 이름 만들기, 최적 스타일링, 이탤릭 스타일링 and 스타일링 분리. These commands modify selected fonts' naming and style-link metadata. Do not promise CSS compatibility or describe metadata changes as only visual grouping. FontInfoPanel populates slope choices with literal Plain, Italic and Oblique, despite translated designer samples. Use Italic for an italic font linked to another font.

FontWindow flags retain 파란색 라벨, 청록색 라벨 and 초록색 라벨. Do not borrow shorter color names from other contexts. FilterPanel's Preview is 미리 보기. Lowercase stem controls show lc; running explanations may spell out that this means lowercase.

Quick Help: glyph controls and layout editing¶

FontWindow uses 책갈피, 필터 조건에 맞지 않는 글리프 숨기기, 좁음, 넓음 and 매우 넓음. Recipe commands use 레시피 편집 / 초기화 and 레시피 초기화. GalleryPanel's size commands are 셀 크기 줄이기 and 셀 크기 늘리기, while FontWindow uses 셀 축소 / 셀 확대.

GlyphWindow uses 줄 간격, 줄 서식, 블록 서식 and 표 서식. GW_Text retains 행간 and its distinct case-conversion labels. GW_Component and GW_Shape use 변형 초기화. This resets the full transformation. Their offset, scale and angle help must not direct users to separate center, shift, scale or rotation reset buttons absent from those panels. GW_Delta's value is 진행률(0-100%); its section caption is 진행 상황.

GW_Pin's 마크 피처 생성 requires 글리프 구성에 사용. Preserve the shorter draft instructions where that requirement is absent. GW_Skin uses 가운데 정렬, 좌우 뒤집기 and 상하 뒤집기. GW_Transform uses 가로로 기울이기 / 세로로 기울이기. InspectorNode clones the node command 노드 조화; a handle command in another context can use 조화 조정.

InspectorGlyph uses 마스터에 RSB 및 글자폭 수식 복사 and 마스터에 LSB 수식 복사. Copy recipients share the source layer's master status and must be unlocked. Its OT choices are 단순, 합자 and 마크. Both Width and Advance width mean 글자폭 in this inspector; avoid a duplicate translated alias. Ordinary explanatory metric prose can use 수식.

InspectorGlyph's 변형 선택자 대화 상자 열기 action edits inline despite the label. Supplementary selector indices extend to 256. Skin-tone editing has five Unicode modifiers, U+1F3FB–U+1F3FF. Keep these distinct from DlgUnicodeVariations, whose title is 이형 선택자.

Use 안전 영역 위쪽, 안전 영역 아래쪽, BBox 위쪽 and BBox 아래쪽 in Info_Dimensions. Its button is 폰트 경계 상자 업데이트. Info_Zones uses 위쪽 영역 and 아래쪽 영역.

The Variations panel title is 베리에이션, while its list and map are 변형 목록 and 변형 지도. The preference page is 변형 and its Match edits section is 편집 맞추기. Keep the button label 편집 내용 맞추기 distinct from that section.

LookupsPanel uses 프로시저 추가 / 프로시저 제거 for lookup controls, 프로시저 컴파일, 피처 업데이트 and 선택한 피처 컴파일 및 업데이트. The panel title Lookups is 규칙, but an individual lookup is 프로시저. Positioning is 위치 조정, advance-width adjustment is 글자폭 조정, and Device corrections is 크기별 보정. A proposed Add feature label must not replace Add lookup.

Quick Help: main commands and destinations¶

MainWindow distinguishes 노드 조화 from 핸들 조화 조정. InspectorNode clones 노드 조화. Context-menu handle commands use 조화 조정 and 고급 조화 조정. Explain G2 as equal curvature at the join; avoid claiming constant curvature across an entire curve or whole-contour energy optimization.

The command 작업 영역 관리 opens the dialog 작업 공간. 글리프 빌드 opens 글리프 만들기. Commands can retain their own terminology while help identifies the actual destination title.

Match Edits is 편집 내용 맞추기. Its preference path is 환경설정 > 변형 > 편집 맞추기. Ordinary mathematical explanations can use 수식. Do not substitute another context's label for a valid description.

In the Actions dialog, Flatten glyph is 글리프 평면화; the MainWindow command is 글리프 병합. MainWindow stacking commands retain 뒤로 보내기, 맨 앞으로 가져오기 and 앞으로 가져오기. Add a one-step explanation where needed, while preserving the action name.

MainWindow uses 작업 내역, 되감기, 기록 and 빨리 감기. The GitHub command uses 이력. PreviewPanel uses 미리보기 and 텍스트 따라가기 / 사용자 정의 텍스트. Rectangle is 직사각형; the related erasing tool is 지우기 직사각형. Keep literal shortcuts, glyph names and formula syntax intact.

Quick Help: workspace and preference contexts¶

Use 작업 공간 for Workspace. The Variations panel is 베리에이션, while the Variations preference page is 변형. Follow the owning context: 노드 조화 is the contour/node command; 조화 조정 refers to handles. Use 영역 for Zones and 래피드 for the Rapid tool.

Use the preference choices 시각적, 좁게, 범용 모델 and 읽기 쉬운 이름 where those controls appear. The naming preferences use 알기 쉬운 이름 in their own context. Code-font reset uses 재설정; its named panels include TT 힌팅, 테이블 and 점수판.

폰트 창 최소 1개 selects a lifecycle policy: opening a font opens a Font window, and closing its last Font window closes that font. Do not describe it as a simple window on/off toggle.

For anchor copy buttons, distinguish expressions from numeric coordinates. When the separate X button is visible, the main button copies Y expressions; otherwise it copies both coordinates' expressions. A missing anchor is cloned. The all-item activation buttons act immediately. Enabling mark participation also requires glyph-construction participation.

For autohint center links, On links from both sidebearings toward the center; Off links from left to right. Retain 링크 in this TTH context.

Quick Help: repeated controls and dynamic fields¶

MainWindow's Workspaces menu is 작업 영역; the Workspace dialog and property panel use 작업 공간. Naming operations use 알기 쉬운 이름 / 제작용 이름, while font opening uses 읽기 쉬운 이름 / 배포용 이름. Pref_Texts uses 사전 정의 텍스트; the GlyphWindow and Preview chooser says 미리 정의된 텍스트 선택. The Variations map is 지도, distinct from AxisWidget's 매핑.

Use each panel's reset captions. ShapesPanel uses 라이브 이동 초기화, 라이브 크기 조절 초기화 and 라이브 회전 및 기울기 초기화. Nonspacing elements are 메트릭스 제외; this property does not imply zero advance width. Arrange controls change stacking order inside the owner group or layer. Distance and bounds suggestions use their actual actions, rather than copied guide-snapping instructions.

The stroke widget uses 시작점 캡 / 끝점 캡, 각진 연결 and 각진 연결 한계. Dynamic cap fields are 끝 모양, 끝 장력 and 끝 각도 고정. Flat, square and fixed cap shapes accept -100–100%; horizontal and vertical shapes accept -100–0%; round tension accepts 0–100%. The angle field also sets cap offset for flat, square and round caps. Preserve the linked-cap condition and distinguish resetting angle from offset.

Quick Help: labels and repeated descriptions¶

Runtime slope-class choices remain Plain, Italic and Oblique in the naming and master selectors. Translate their explanations; preserve the displayed choice values.

Follow the owning control: Bar_Brush uses 지우기 붓, WidgetBrush uses 지우개 붓. Bar_Ellipse uses 곡선 장력이 있는 타원, WidgetEllipse uses 곡선 장력이 적용된 타원. Panel titles use 베리에이션 and 미리보기; menu captions may use 변형 and 미리 보기. An instruction referring to a control inside another panel uses that control's label.

The hint-creation tool is 연결 (Attach); Magnet is its legacy internal name. Ordinary handle harmonization and 고급 조화 조정 are separate commands. Keep their behavior distinct when explaining curvature.

With inactive-pair editing off, clicking the second glyph activates that kerning pair. It does not make that glyph the current glyph. The OpenType tables limitation concerns availability of graphical editors, not whether FontLab can retain the table data. Translate double-click instructions as 2×클릭 and include degrees when explaining rotation or slant values.