Open ronaldtse opened 4 years ago
This was implemented as bgn-kor-Hang-Latn-1939
, based on "BGN/PCGN 1945 Agreement".
The only difference between the two documents that I could spot, is on how they handle the initial ㄹ
(rieut / r)
This letter is used to write out Sino-Korean words which was historically pronounced /r/. This initial ㄹ
had been dropped in the spoken language before it was removed from the orthography in 1933 [1]. Before this reform, this letter R used to be pronounced as /n/ or dropped in the word-initial position. After the reform, the written form would be consistent with the actual pronunciation. Any word-initial R, for decades after 1933, would have been either loanwords or old spelling.
In the 1962 guide, this sound is transcribed as n
or dropped, following the pre-reform convention. I suppose this is a way to handle pre-reform written work, i.e. if one sees this word-initial R, then follow the pre-reform phonological rule for transliteration.
In the latest guide, this rule has been removed, and R is always transliterated as is. This is because the traditional spelling was restored in DPRK in 1966, and since then all ㄹ
is supposed to be pronounced and transliterated as r under this DPRK standard.
A related note from the latest BGN/PCGN guide is quoted below:
As a result of 조선말규범집 (‘Standard Korean Language’ guidelines published in North Korea in 1966), unlike the Korean spoken in the Republic of Korea, the language spoken in the Democratic People’s Republic of Korea maintains and pronounces the word-initial ᆯ (‘r’). The use of the word- initial ᄅ ('r') can be seen in official news reports as well as native mapping. Since such examples exist, the word initial ᄅ ('r') is reflected as an option in the tables given above.
[1] Here is the original text from Wikisource
@ronaldtse I believe this 1962 guide is closer to the original bgn-kor-Hang-Latn-1939
. I can change the content of the file to match with this 1962 guide.
The current implementation, which is based on BGN/PCGN document, can be renamed to bgnpcgn-kor-kore-latn-kn-1945
.
I found this name in code.csv
, but I am not sure if the Script code Kore
should be used instead of Hang
. Written Korean is still occasionally mixed with Hanja.
bgnpcgn-kor-kore-latn-kn-1945,BGN/PCGN Romanization Agreement -- Korean (North Korea) (1945),bgnpcgn,iso-639-2,kor,Kore,Latn,kn-1945,BGN/PCGN Romanization Agreement -- Korean (North Korea) (1945),,"Date approved: 1945; Originator: McCune-Reischauer, 1939"
@chaaklau I found the source document of the McCune-Reischauer system from the Korea Branch of the Royal Asiatic Society. Volume XXIX (PDF), and in particular, the article:
I think we need to split into the following systems:
var-kor-hang-latn-mr-1939
: based on the original article (McCune-Reischauer)var-kor-kore-latn-mr-1939
: utilizes var-kor-hang-latn-mr-1939
but with Hanja character resolution via dictionary.bgn-kor-hang-latn-1943
: this is an inheritance from var-kor-hang-latn-mr-1939
. (the spec is this file BGN Romanization Guide for Koreanbgn-kor-kore-latn-1943
: would be the bgn-kor-hang-latn-1943
with Hanja resolution.bgnpcgn-kor-hang-latn-kn-1945
: is an inheritance from var-kor-kore-latn-mr-1939
but with the ᄅ rule replaced. The source is BGN/PCGN 1945 Agreement ROMANIZATION OF KOREAN FOR THE DEMOCRATIC PEOPLE’S REPUBLIC OF KOREAbgnpcgn-kor-kore-latn-kn-1945
: would be the bgnpcgn-kor-hang-latn-kn-1945
with Hanja resolution. But do we need this? Hanja is no longer used in DPRK.bgnpcgn-kor-hang-latn-rok-2011
: is an inheritance from moct-kor-hang-latn-2000
.bgnpcgn-kor-kore-latn-rok-2011
: is an inheritance from moct-kor-hang-latn-2000
with Hanja resolution?A list of words in Hanja with their pronunciation can be found here: Hanja Hangul Converter 0.0.7 (Public Domain)
Under the current implementation, all Hanja -> Hangul conversion rules can be added under map[rules]
. This will give the correct result but O(n) runtime with a big dictionary is undesirable.
I am going to modify interscript.rb
to add handle dictionary lookup using binary search. After this is done, the Hangul -> Jamo map can also be handled using dictionary.
Dictionary lookup and Hanja support have been implemented. cd238a1 Implement dictionary lookup f5bbd72 Restructure and add Hanja support to Korean Maps
The maps need some further review and updates. I will send a pull request when they are ready.
Original spec: BGN_Romanization_Guide_1962_korean.pdf
@chaaklau could you please help check this too? Thanks!