2026-01-30

This section is empty…

scanning korean text: graphically or phonologically

native speakers on scanning hangeul: respect korean phonology, or graphical syllables?

do you find yourself "scanning" korean text in a particular way... i have been reading block-by-block because that's intuitive to me coming from the linear latin script. e.g. in the sentence

unimplemented! (center-block){:type "center-block", :affiliated {}, :contents-begin 685, :contents-end 707, :position {:start {:line 18, :column 1, :offset 670}, :end {:line 21, :column 1, :offset 720}}, :children ([:p ("점심을 먹은 다음에, 도서관에 갔어요.\n")])}

my eyes/brain scan one block at a time, like jeom-shim-eul meok-eun da-eum-e, ... (그림 1 참조 }:3) but that makes it difficult for me to speak as i read since it kinda works against liaison and batchim pronunciation rules. thus i've been trying to get myself to scan sorta phonologically, which would be more like jeom-shi-meul meo-geun da-eu-me, ... (그림 2 참조) if that makes sense? i am curious what your perspective on this is =​​w​=.

attachment:1.gif

attachment:2.gif

what native speakers say

yep! i totally do the second

for words i do not know anyway. i scan the whole word as a block if i know it i expect it to become more like [그림 1] the more you do [그림 2] though i don't read a lot in korean anymore haha.

---

faye's response

Ohhh interesting lwk I never thought of this before but like I think I was always taught to speak and read block by block

Ok I remember what my parents taught me. U shouldn’t be trying to pronounce the thing where it’s like 나는 가지고 있어. U shouldn’t be tryna pronounce it like It-suh. It only sounds like it since ur talking fast That’s a bad example tho lemme think of a better one.

Ok I think 같이 is a better one. It’s pronounce gat-chi only because when u say gatch-i fast enough it turns into gat-chi

---

bidoof's response