Korean QA: Practical Checks a Non-Speaker Can Actually Use
- Apr 20
- 7 min read
Korean QA is not only about finding mistakes. It is also about not “fixing” something that is already correct.
That matters a lot in project work. A PM or non-Korean reviewer may see punctuation, brackets, dots, or quote marks that look unfamiliar and assume they should be normalized. Sometimes that instinct helps. Sometimes it creates a new error. The safest approach is to focus on a few visible, rule-backed checks that a non-speaker can use, while leaving deeper grammar and style calls to a native reviewer. Korea’s official orthography says that words are normally spaced, particles attach to the word before them, and many punctuation rules are explicitly standardized. Microsoft’s Korean localization guidance also adds some software-specific rules that matter in UI review.
1. Numeric dates: the final dot matters
One of the easiest Korean QA checks is numeric date formatting.
The National Institute of Korean Language says that when you write a date with Arabic numerals, you can replace 년 / 월 / 일 with dots. Its official examples include:
1919. 3. 1.
10. 1.~10. 12.
The same guidance also says the final dot for 일 should not be omitted. In other words, 1919. 3. 1 is not the standard form in that system.
So this is a useful review check:
Correct official-style numeric date:1919. 3. 1.
Suspicious / nonstandard in that rule set:1919. 3. 1
There is another useful nuance here. For historically meaningful dates, both of these are accepted:
3.1 운동
3ㆍ1 운동
The official rule says the dot form is the principle and the centered dot form is also allowed. So this is exactly the kind of place where QA should be careful: do not “correct” one accepted form into the other just because it looks unfamiliar. Both can be valid.
2. Direct quotes: the final period is optional in some cases
This is one of the best examples of why QA should avoid over-correction.
Korea’s official orthography says that for a directly quoted sentence, writing the final period is the principle, but omitting it is also allowed. The official examples are:
그는 “지금 바로 떠나자.”라고 말하며 서둘러 짐을 챙겼다.
그는 “지금 바로 떠나자”라고 말하며 서둘러 짐을 챙겼다.
Both are accepted. The same rule also says that the same principle applies with single quotation marks.
This matters in QA because a non-speaker may see one version and think the other must be wrong. Not always. If you flag every Korean direct quote that omits the period inside the quotation marks, you may be flagging text that is already allowed by the official rule.
So the practical takeaway is simple:If you see
“지금 바로 떠나자.”라고
and
“지금 바로 떠나자”라고
do not assume one is automatically an error. Check the project style first.
3. Titles: Korean has standard title marks, but accepted alternatives exist
Korean does have standard marks for titles, and these are very visible to non-speakers.
For books and newspaper names, the official rule says the principle is to use:
『 』 or ≪ ≫
Examples given by the official rule include:
『훈민정음』
≪한성순보≫
But the same rule also says that double quotation marks can be used instead.
For subtitles, songs, works of art, business names, laws, and regulations, the official rule says the principle is to use:
「 」 or < >
Examples given include:
「국어 기본법 시행령」
<국어의 로마자 표기법>
And again, the rule allows an alternative: single quotation marks can also be used.
This creates a very practical QA lesson.
If you see a book title written as:
『훈민정음』
that matches the official principle.
If you see it written as:
“훈민정음”
that can still be allowed.
Likewise, if you see a law or song title written as:
「국어 기본법 시행령」
or
‘국어 기본법 시행령’
you should not automatically assume the single-quote version is wrong. The official rule allows it.
So for QA, the right question is not “Does this use the title mark I personally expected?” The right question is “Is this within the accepted Korean rule or within the project style?”
4. Parentheses: they usually attach, not float
Parentheses are another visible check.
The official Korean punctuation rules say that an opening parenthesis attaches to the following word, and a closing parenthesis attaches to the previous word. The rule’s examples include:
니체(독일의 철학자)
2014. 12. 19.(금)
That means you normally do not insert spaces like this:
니체 (독일의 철학자)
2014. 12. 19. (금)
There are special exceptions in numbered references such as article numbering, but in ordinary running text the no-space pattern around the parenthetical content is the standard visible form.
This is useful for non-speakers because it is easy to spot on screen. If Korean text repeatedly shows English-style floating parentheses with spaces around them, that is worth checking.
There is one more subtle point. When a sentence is followed by a parenthetical note, the general Korean guidance says sentence-final punctuation such as a period, question mark, or exclamation mark usually comes before the parenthesis, although there are cases where the punctuation may come after if the parenthetical is effectively part of the sentence. That means this area is rule-based, but not always mechanically simple. So if you are not a native reviewer, it is safer to flag only the clearly broken cases, not every punctuation-parenthesis combination that looks unfamiliar.
5. Ellipsis: don’t invent your own number of dots
This is one of the clearest QA checks of all.
Korea’s official punctuation rule uses the ellipsis form:
……
The National Institute of Korean Language also states in a 2024 answer that the principle is six dots, while three dots are permitted. It also says that forms like …………. are not the standard way to write it.
Official examples include:
그는 최선을 다했다. 그러나 성공할지는…….
“…….”
And the rule says that when the ellipsis ends the sentence, a sentence-ending mark follows it according to the sentence type.
So from a QA perspective:
Standard principle:
……
Allowed shorter form:
...
Not a safe “creative fix”:
………….
This is very practical because a non-speaker can spot dot count and consistency immediately. If a Korean subtitle file or UI string keeps mixing ..., ……, and long improvised strings of dots, that is worth checking. But again, do not over-correct a three-dot ellipsis if the project accepts the allowed shorter form.
6. Sentence-ending punctuation in software: product style can differ from literary expectations
This is where localization QA often goes wrong.
Microsoft’s Korean localization style guide says that in software localization, English strings ending with a colon or semicolon are often translated into Korean with a period if the Korean sentence ends in full sentence styles such as ~하세요 or ~합니다. At the same time, the guide warns that if changing the punctuation could cause functional problems, the team should check with the product group instead of changing it blindly.
That means a PM should not assume that a Korean UI must mechanically preserve English end punctuation. But they also should not assume every colon must be deleted. In software, punctuation can be tied to placeholders, parsing, or UI behavior. Microsoft’s own guide gives both patterns: some strings are converted to sentence-final periods, while others keep the colon because the colon is functionally tied to the placeholder or structure.
This is the broader QA lesson:
visible difference does not always mean error.
Sometimes it means style-guide choice.
The same Microsoft guide also says that if the source uses double quotation marks, the same double quotation marks can be used in the Korean target unless Microsoft has flagged an exception. So in software localization, do not automatically “correct” every pair of straight double quotes into Korean literary title marks. That may be the wrong fix for the product context.
7. Word spacing: useful clue, but handle with care
Korea’s official orthography says that the general principle is to separate words with spaces, and it specifically notes that particles attach to the word before them. Its example is:
동생이 밥을 먹는다
not
동생 이 밥 을 먹는다
This is useful, but it is also where non-speakers need humility.
Yes, visible spacing problems can sometimes be spotted. If a Korean UI repeatedly shows short one-syllable pieces detached in odd places, that can be a clue worth asking about. But Korean spacing is not something a non-speaker should “correct” aggressively from instinct alone. The official rule gives you a principle, not a license to rewrite everything you think looks crowded.
So treat spacing as a query area, not a casual cleanup area, unless you have a native reviewer or a project-specific style rule backing the change.
8. One of the most valuable QA skills: knowing when not to flag
If you want one lesson from Korean QA, it is this:
Do not equate “different from what I expected” with “wrong.”
These pairs are especially useful to remember:
3.1 운동 / 3ㆍ1 운동
Both accepted.
“지금 바로 떠나자.”라고 / “지금 바로 떠나자”라고
Both accepted in direct quotation contexts.
『훈민정음』 / “훈민정음”
The first is the official principle for book and newspaper titles in running text; the second is also allowed.
「국어 기본법 시행령」 / ‘국어 기본법 시행령’
The first is the official principle for laws, regulations, and similar titles; the second is also allowed.
That is not weakness in QA. That is good QA. It means you are checking against the rule, not against personal expectation.
What a non-speaker can realistically check
A non-Korean reviewer can still contribute a lot by watching for practical, visible issues.
You can check whether a numeric date dropped its final dot. You can check whether parenthetical text is floating with English-style spaces. You can check whether a title is using some accepted Korean title-mark pattern rather than random punctuation. You can check whether an ellipsis is consistent and not improvised. And you can avoid raising false alarms where the official rule already allows more than one form.
That is often more valuable than trying to sound authoritative about a language you do not speak.
If you speak Korean and something here looks off, unclear, or unnatural, please do tell us. We do our best to keep these articles accurate and useful, but native readers will always catch things others may miss. Please contact us and let us know what you spotted.
