On the point of tonogenesis in Korean, that actually solves the tense consonant issue for English speakers!
Comment on Is Korean phonology difficult?
farmgineer@nord.pub 5 weeks ago
Korean due to it being an alphabe
Technically, it’s not; it’s a syllabary like Japanese katakana and hiragana.
Is it actually that hard while Japanese phonology is considered “easier” to pick up.
Japanese is dead easy for an English speaker so long as they remember that vowel length matters, and the R is not a standard General American R.
Korean has a couple of sounds/features (tense consonants) not in use in General American, but nothing insurmountable. I’d call it more difficult but only very slightly so.
Tone
Korean is actually considered to be undergoing tonogenesis, so that’s kinda neat.
Tone isn’t a huge deal; even if you get it wrong, there’s usually only one thing that makes sense in the context of the sentence. Not a worry in Korean at the moment. Japanese has pitch accent which can cause the same issue (If I’m running through the field plucking はな (hana), you’re not going to think it means ’nose’ here if I get the pitch accent wrong).
One can pick up reading Korean more quickly than Japanese (if no Kanji/Hanzi/Hanja experience otherwise), though I found bacchim to be annoying. In exchange, Korean tends to have some grammatical features lacking in Japanese, but I never got far enough to learn what those were (outside of some more forms of address/honorific).
otp@sh.itjust.works 5 weeks ago
farmgineer@nord.pub 5 weeks ago
Neat! I have a video on the topic in my to-watch list, but hadn’t looked into the details yet so far.
zaphod@sopuli.xyz 1 week ago
Hangeul is an alphabet, it has distinct symbols for vowels and consonants, you just write them in syllable blocks. Compare that to hiragana/katakana that has distinct symbols for all possible syllables. Theoretically you could write 한글 (hangeul) as ㅎㅏㄴㄱㅡㄹ, try doing that with hiragana/katakana. Linearised Hangeul was an idea that was actually proposed in the past (source).
farmgineer@nord.pub 1 week ago
I stand corrected. Thanks for this!