User:KYPark/Korean Romanization

Definition from Wiktionary, the free dictionary
Jump to: navigation, search

Comparison Chart[edit]

Jamo IPA Yale M-R. Luk. 1959 J.G. R.R. Nemo
k k k/g k g k g/k g/kg
kk kk kk gg kk kk 'k,q
n n n n n n n n
t t t/d t d t d/t d/td
tt tt tt dd tt tt 't
l l l/r l l/r r r/l r/lr
m m m m m m m m
p p p/b p b p b/p b/pb
pp pp pp bb pp pp 'p
s s s s s s s s/ts
ss ss ss ss ss ss 's,x
ŋ ng ng ng ng ng ng '/ng
ʨ c ch/j j j ts j z
ʨ̤ cc tch jj jj tss jj 'c
ʨʰ ch ch' jh ch tsh ch c/tc
kh k' kh k kh k k
th t' th t th t t
ph p' ph p ph p p
h h h h h h h h
z 'z
a a a a a a a a
ɛ ay ae ä ae ai ae ay
ja ya ya ya ya ya ya ja
yay yae yae yai yae jay
ʌ e ŏ ø eo ŏ eo e
e ey e e e e e ey
ye yeo yeo je
je yey ye ye ye ye ye jey
o o o o o o o o
wa wa wa wa wa wa wa wa
way wae wae wai wae way
ø oy oe ö oe oi oe oy
jo yo yo yo yo yo yo jo
u wu u u u u u wu
we weo wo wo we
we wey we we we we we wey
wi wi wi wi wi wi wi wi
ju yu yu yu yu yu yu ju
ɰ u ŭ ʉ eu ŭ eu u
ɰi uy ŭi ʉi eui ŭi ui uy
i i i i i i i i
ə wo
əi wy
  • Adapted from Korean Romanization Chart of Glossika Inc.
  • Put the mouse pointer on the headline cell (outide of the link!) to read the fuller denotation than the abbreviation.

Toward Roman orthography of no ambiguity[edit]

Words in isolation or out of context are not only semantically but also phonetically unstable and anomalous by nature.

The Revised Romanization of Korean requires that the name of the Republic of Korea 한국 for example be transliterated to /hanguk/. The point here lies in the use of /k/ rather than /g/ as the final consonant. Such final endings would sound more real or realistic, if truly, only in isolation or in foreign context. In Korean context, however, they link up with such particles as (-eun), (-i), (-ui), (-e), 에게 (-ege), 에서 (-eseo), 으로 (-euro), (-eul), etc., and sound /g/ rather than /k/ for example. Such agglutinations are equivalent to Eurpean inflections. In most of, so to speak, Korean inflections, the final consonant of Korean nouns sounds /b/, /d/, /g/ rather than /p/, /t/, /k/, respectively. From the Korean perspective, therefore, the Romanization /hanguk/ preferred to /hangug/ is most unlikely or groundless in practice.

All the past Korean Romanization systems greatly suffer from ambiguity, and shy away from orthography. These vital linguistic considerations are not taken seriously.

Men and machines of low intelligence may not discriminate such identical pairs of Yale Romanization as follows:

토끼 thokki cf. to'ki
톡기 thokki cf, toggi

코끼리 khokkiri cf. ko'kiri
콕기리 khokkiri cf. koggiri

깎기 kkakkki  cf. 'ka'kgi
깍끼 kkakkki  cf. 'kag'ki

있습니다 isssuphnita cf. i'ssubnida
잇씁니다 isssuphnita cf. is'subnida

Orthography and orthoepy[edit]

Orthography is one hare; orthoepy is another. So it may be unwise to chase the two. Then which should be the right choice? It depends, but would better be orthography in principle.

Pronunciation anomaly[edit]

1.0 말 못하는 사람 
1.1 mal mothaneun saram - Phonocentric RRoK   
1.2 mal moshaneun saram - Orthographic RRoK 
1.3 [ma:l motʰanɯn sa:ɾam] 

2.0 말 못타는 사람
2.1 mal mottaneun saram - Phonocentric RRoK   
2.2 mal mostaneun saram - Orthographic RRoK 
2.3 [mal motʰanɯn sa:ɾam] 

3.0 말 모타는 사람 - "Phonetic Hangul" for (1) & (2)
3.1 mal motaneun saram - Phonocentric RRoK   
3.2 mal motaneun saram - Orthographic RRoK 
3.3 [mal motʰanɯn sa:ɾam] 

The ambiguity and anomaly imvolved in the, so to speak, phonocentric RRoK may be shown up by (2.1) that is definitely confused with "말 모따는 사람" that should sound different! Hence, such an idea should be given up as soon as possible. In contrast, the orthographic RRoK is less ambiguous and less variant, hence definitely worth the orthography while the orthoepy is attributed to IPA, Phonetic Hangul and its RR.

Doubled consonants[edit]

된소리
IPA          ʨ̤

Hangul Romanization JavaScript[edit]

var arrayC = "g kk n d tt r m b pp s ss ^ j jj ch k t p h".split(" ") ; arrayC[11]="" ;
var arrayV = "a ae ya yae eo e yeo ye o wa wae oe yo u wo we wi yu eu ui i".split(" ") ;  
function doRR(x) {
  n = parseInt(escape(x).substring(2), 16) - 44032 ;
  c = parseInt(n/588) ; 
  v = parseInt((n-588*c)/28) ; 
  return arrayC[c] + arrayV[v] ; 
}
First presented @ User_talk:AutoFormat#Korean characters in computing --KYPark 03:58, 12 April 2007 (UTC)