Table of Content
Whoops this document contains no title
Reader Settings
Appearance
Side by side
Popup dict
Page Length
Page Max Width
Typography
Font Family
Font Size
18px
Line Height
27px
Word Break
오래된 시골 마을에 착한 농부가 살고 있었다. 그는 아직 결혼하지 않은 채 혼자 생활하고 있었다.
Header
Header 1 Font Size
28px
Header 2 Font Size
24px
Header 3 Font Size
22px
Behavior
Highlight block on hover/touch
1.

Subject Marker

Mark the subject of the sentence.
Example
  • 펑펑 내려요.
    The snow is falling heavily.
  • 머리 길다면 머리를 묶어야 해요.
    If your hair is long, you should tie it up.
Related to

Usage

  • The particle is used in front of words ending in a consonant.
  • The particle is used in front of words ending in a vowel.

Emphasis

The particle N+이/가 can also be used to emphasize the preceding subject.

  • 할게요.
    I will do it.

New topic

N+이/가 is used to introduce a new theme, change it or add new information.

  • 옛날 어느 마을에 착한 농부 살았다. 농부는 아직 결혼하지 않고 혼자 살았다.
    Once upon a time, in a village, there lived a kind farmer. The farmer was still unmarried and lived alone.

Phonetic transformation

When the particle is combined with , , , 누구 or 무엇 a phonetic transformation takes place.

  • + becomes 내가
  • + becomes 네가
  • + becomes 제가
  • 누구 + becomes 누가
  • 무엇 + becomes 뭐가

Honorific language

In honorific language, N+이/가 (Subject Marker) is replaced by N+께서 (Subject marker).

N+이/가 vs N+은/는 vs N+을/를

이/가 (Subject Marker)

Mark the subject, who or what is doing the action.

은/는 (Topic marker)

Mark the topic, what the sentence is about. The topic of the conversation.

을/를 (Object marker)

Mark the object, who or what is being acted upon.

Note that these particles can sometimes be dropped in practice and we assume the audience is smart enough to understand the context.


All the grammatical content on this page, excluding the computer-generated audio, is licensed under the permissive
CC BY 4.0
license. Contributions, corrections, and feedback are all highly welcomed.
Grammar settings
Audio playback rate
English translation
Failed to load the context :( This is a bug