Jongseong
Similarities in pronunciation between languages spoken over the same region are part of a phenomenon well known to linguists and do not imply that the languages are related. For example in terms of a pronunciation feature called coda devoicing, Slovene dialects near the Austrian border will pattern with German, those near the Croatian border will pattern with Croatian, while Standard Slovene will have something in the middle. Slovene and German are only very distantly related.
There may be something there about closely related population groups ending up using similar sounds even if their languages are not closely related, but I doubt the researchers even thought about that and used phonemic distance as a shorthand for actual linguistic distance.
There is no reason for there to be a difference in English loanword usage in North Korea between the border area and the far far North. Remember, the DMZ is a tightly sealed border and there has been virtually zero cross-border exchange that would influence the language since the Korean War. If we were talking about normal national boundaries with some cross-border linguistic exchange then there would be a gradient of linguistic features taken from the neighbouring state near the border and diminishing as you move away from it, but with the DMZ there is no such thing.
찍개 is a recent South Korean neologism for 'stapler'. There is no reason that North Korea would use the same word. I don't know what they call staplers in North Korea, though.
Once again, the point is that English loanwords were being used in Korean before the division of the peninsula, and afterwards, North and South Korea followed completely separate paths of linguistic evolution. There was no way for people near the border regions to be influenced by what people were speaking on the other side. You might flip the question and ask whether South Koreans near the DMZ are more likely to use pure Korean words due to North Korean influence, and again the answer is no for the same reasons.
도꾜 is the traditionally common spelling for Tokyo that is based on maximum phonetic similarity. In South Korea, the spelling was reformed to 도쿄 to conform to standardized rules about how to write Japanese loanwords, where all non-initial "k" sounds were to be mapped to ㅋ. So this is more of a phonemic spelling. Roughly speaking, "phonetic" refers purely to the sounds, while "phonemic" goes into the more abstract level of grouping the sounds that are considered mere variations of a single sound to the speakers of that language. However, due to widespread resistance, the South Korean reform didn't go all the way in making it phonemically regular—otherwise, we would be writing 토쿄 instead, using ㅌ everywhere for "t" (in concession to the traditional practice, we write ㄷ for initial "t").
This reform took place in the 1980s in South Korea, and didn't affect North Korea, which still writes 도꾜 for Tokyo. It has nothing to do with Russian pronunciation. If we imitated Russian pronunciation, it would come up as something like 또끼오 or even 또끼워.
The situation in Korean is not qualitatively different, either. For instance, the Jeju "dialect" (now sadly moribund) is definitely not mutually intelligible with other dialects of Korean some authorities would insist on classifying it as a separate language. Even the mainland dialects (as they are traditionally considered as opposed to distinct languages) are considerably different from each other, not just in lexical items but in the existence of different grammatical categories (e.g. distinguishing between yes/no and wh-questions), morphology (the conjugation of verbs and adjectival verbs is all different), and phonology (different consonant and especially vowel inventories, different stress/pitch systems), to the degree that I wonder how much communication would be possible if it had not been for the imposition of standard Korean.
I used Italy as an example instead of the U.S., because it is a stretch to say that the U.S. has different dialects as the speech is quite uniform across the vast country compared to what you see in Korea; or the U.K., where the existence of Scots complicates the analogy. I did not intend to minimize the diversity of regional languages in Italy.
However, there are often differences in the spelling of such loanwords between the North and the South. So you have 프로그람 (p'ŭrogŭram) in the North but 프로그램 (p'ŭrogŭraem) in the South for "programme", 텔레비죤 (t'ellebijyon) in the North but 텔레비전 (t'ellebijŏn) in the South for "television", and 미싸일 (missail) in the North but 미사일 (misail) in the South for "missile". This is due to the fact that the standardized spelling of loanwords (a problematic and much debated area of Korean orthography) was frequently reformed in South Korea, and probably in the North as well, so the principles of spelling have turned out quite differently between the two. Also, as North Korea uses a lot of loanwords from Russian, even loanwords originally from English tend to be absorbed in the Russian pronunciation, such as 땅크 (ttangk'ŭ) for "tank" or 뜨락또르 (ttŭrakttorŭ) for "tractor" as opposed to SK 탱크 (t'aengk'ŭ) or 트랙터 (t'ŭraekt'ŏ) which is closer to the English pronunciation.
The official language policy in both the North and the South tends to discourage loanwords from English, but it seems a bit more successful in the North, especially when it comes to post-1945 loanwords. If you only focus on the differences between the North and the South, then you see many cases where North Korea uses native Korean words whereas South Korea uses loanwords from English. But you can't extrapolate from that and conclude that North Korea doesn't use loanwords from English at all. This would be a misconception, just like the false notion that North Korea doesn't use Sino-Korean words.
The notion that North Koreans say 얼음보숭이 (ŏrumbosung'i) for "ice cream" is a bit of a myth. The authorities in North Korea did indeed introduce this word as a part of a linguistic purification effort, but it doesn't really seem to have caught on. A 1962 North Korean dictionary only has 아이스크림 (aisŭk'ŭrim) "ice cream", just as in South Korea. A 1981 edition of another dictionary and a 1984 encyclopedia introduce 얼음보숭이 (ŏrumbosung'i), but the official dictionary that appeared in 1992 again has 아이스크림 (aisŭk'ŭrim) "ice cream" and not 얼음보숭이 (ŏrumbosung'i). The 1992 dictionary also has 에스키모 (esŭk'imo) "eskimo", which in North Korea is a popular everyday word for "ice cream" which comes from a name of a brand that was popular there.
You have plenty of examples of South Korean language authorities introducing "purified" (often pure Korean) words to replace loanwords, which don't necessarily catch on. For "stapler", the official South Korean dictionary has the pure Korean translation 찍개 (jjikgae), for instance. But I have never seen this term in the wild—instead, people say 스테이플러 (seuteipeulleo) "stapler", or more commonly, 호치키스 (hochikiseu) "Hotchkiss". There is a limit to how much official language policy can dictate actual usage, whether it is in North or South Korea.
Note that linguistic evidence doesn't come into this, just as one wouldn't usually be speculating about which English-speaking country a hacker was from simply based on the code.
More importantly, Italians will continue to write and be taught in Standard Italian, which was developed based on the Tuscan dialect long before our artificial division of the peninsula. It won't be as if they would start from scratch and create new standard languages based on the Milanese dialect in the North and the Roman dialect in the South. Even independent countries such as Germany, Austria and Switzerland find it useful to use the same standard German as each other, even if it's not necessarily based on a dialect spoken wothin their borders. There will inevitably be differences in vocabulary and spelling, but the differences will be far less than if we imagined a naïve model where each country creates its own standard (which is what basically happened in Scandinavia).
Also, as far as I know the codes didn't contain any Korean. Instead, what they found was that it seems to have used Korean text encoding, like EUC-KR. People have pointed out that this is a South Korean encoding, but North Koreans also use it since you hardly find any software that supports the official North Korean encoding. Again, if someone uses a British English locale, that isn't proof that it can't be an American. When it comes to text encoding and locale, you usually use whatever is available that lets you type in your own language.
"As a result of our investigation, and in close collaboration with other U.S. government departments and agencies, the FBI now has enough information to conclude that the North Korean government is responsible for these actions. While the need to protect sensitive sources and methods precludes us from sharing all of this information, our conclusion is based, in part, on the following:
* Technical analysis of the data deletion malware used in this attack revealed links to other malware that the FBI knows North Korean actors previously developed. For example, there were similarities in specific lines of code, encryption algorithms, data deletion methods, and compromised networks. * The FBI also observed significant overlap between the infrastructure used in this attack and other malicious cyber activity the U.S. government has previously linked directly to North Korea. For example, the FBI discovered that several Internet protocol (IP) addresses associated with known North Korean infrastructure communicated with IP addresses that were hardcoded into the data deletion malware used in this attack. * Separately, the tools used in the SPE attack have similarities to a cyber attack in March of last year against South Korean banks and media outlets, which was carried out by North Korea."
As you will note, all of these are circumstantial and none is conclusive. Hackers can reuse malware developed by others, and it is possible to fake identifying information to make it appear as if it is the work of North Koreans.
Many security experts are not convinced just from the publicly available information, but the feeling is that the conclusion must be based on unreleased info, perhaps human or signals intelligence.
So at this point, for Americans at least, it's based on how much you trust your government to tell the truth. It's telling to see the amount of scepticism here. I'm South Korean, and we may be more willing to blame North Koreans not because we have access to conclusive evidence but because we have been following related news more here. While the international audience seems surprised that such a supposedly technically backward country could be behind the hacking, South Korea has already experienced a couple of major attacks that were blamed on North Korean hacking units, later described by defectors who allegedly worked in such a unit based in China. We also have been reading about how unhappy North Korea was about The Interview long before the hacking. Again, this is all circumstantial evidence, but it makes it easier for us to accept the FBI's conclusion.
In the end, what you choose to believe is based on your worldview.
The Greenland Norse probably sent expeditions to the Canadian islands and coast to get timber for a few centuries at least. An Icelandic document records that in 1347, a ship that was returning from "Markland" came off course and ended up in Iceland. Markland along with Helluland and Vinland is one of the Norse names given to regions in the North American coast and islands. So there could well have been opportunities to encounter Inuits who expanded to Northwest Canada by the 13th or 14th centuries. But even the Norse themselves haven't left many records about such expeditions or encounters with other peoples.
Anyway, the Dorset disappearance is usually blamed on the Inuit (whose oral traditions recount driving off the Dorset people), although they seem to have already been in decline when the Inuit arrived. It could be that Inuit pathogens may have partly been to blame, though we may never know.
I don't know of any oral traditions about the Norse from Canadian Indians, though. Unlike the settlements in Greenland, L'Anse aux Meadows was just an exploration base that never developed into a permanent settlement. So unlike the prolonged periods of contact between the Norse and the Inuit, there might have been just a few isolated encounters between the Norse and the Canadian Indians that didn't leave enough of an impression to be preserved in oral tradition.
From the Wikipedia article on the Eastern Settlement (the largest of the Norse Greenland settlements): https://en.wikipedia.org/wiki/Eastern_Settlement
"In the Greenlandic Inuit tradition, there is a legend about Hvalsey. According to this legend, there was open war between the Norse chief Ungortoq and the Inuit leader K'aissape. The Inuit made a massive attack on Hvalsey and burned down the Norse inside their houses, but Ungortoq escaped with his family. K'aissape conquered him after a long pursuit, which ended near Kap Farvel. However, according to archaeological studies, there is no sign of a conflagration."
Also, try explaining how simple all this is to the self-employed women selling crafts online using PayPal.
Russia is by no means unique in this respect. This applies to most global and regional hegemons. There are many that do not like the U.S. or China. Britain and Germany in recent memory, or France earlier in early modern Europe, inspired similar fear. But what is particularly worrying about Russia now is that the narrative being privileged within the country only portrays Russia as the victim of recent history. This makes it difficult for Russians and their neighbours to come to a common historical understanding.
“In the file we had a line with broken characters. Those characters didn’t render right under any encoding, except EUC-CN [Chinese] and EUC-KR [Korean] … In this case, the readme.txt file could be read fine under either EUC-CN and EUC-KR, which means the file was most likely generated from a computer set in either Chinese or Korean – or the hacker deliberately converted the file (which seems unlikely),” Karpeles said.
I should add that EUC-KR is a South Korean legacy character encoding, but the corresponding North Korean encoding (EUC-KP?) is hardly ever supported so in practice North Koreans would be likely to use EUC-KR.
I have to say I find point 1 borderline offensive, that the English basically isn't bad enough to be authentic "Konglish". It can't have been written by North Koreans unless you see comprehension mistakes! Does the author know that perhaps counterintuitively, English is the most widely taught foreign language in North Korea? Or is he familiar with the barrage of English-language propaganda put out by the North Korean regime?
I wouldn't describe it as "broken English" either. Stilted and unlikely to have been produced by a complete native speaker, yes (e.g. old-fashioned English subjunctive in "our request be met"), but not ungrammatical. I have no particular trouble believing that it is an earnest attempt by a non-native speaker to write correct English.
Point 2 is the weakest. I have no idea where the author got the notion of North Koreans speaking their own dialects and traditional Korean being forbidden. Korean like any language has regional dialects in both North and South Korea, but the language itself was standardized before the division of the peninsula based on the Central dialect region around Seoul. This dialect region is split between the North and South so that for example the speech in Kaesong, North Korea is similar to the speech in Seoul, but Pyongyang falls outside this and falls into a different dialect region. Nevertheless, because Standard Korean was established before the division, the standard speech in North Korea is also based on the Central dialect. The Standard Korean spoken by someone from the North is not as different from what you would hear from someone from the South as one might imagine, as South Koreans may verify by watching a North Korean news broadcast. There are of course differences in orthography and vocabulary similar to what you would find between the UK and US in English (thus the "helicopter" example supplied by the author), but this has more to do with a natural divergence of the language after decades of forced separation than anything.
The closest thing I can think of to the notion of traditional Korean being forbidden is that North Korea banned Chinese characters from official writing right away, while South Korea didn't go as far but still eliminated Chinese characters from texts used in education. Korean has its own alphabet, but Classical Chinese was the traditional literary language, and Sino-Korean vocabulary (words derived from Classical Chinese) were often written in Chinese characters in a "mixed-script" style reminiscent of Japanese. In both Koreas, the end result was that Korean came to be written purely in the Korean alphabet. In South Korea this was gradual as the mixed-script style held on for a few decades, but by now most South Koreans have been educated writing only using the Korean alphabet. At any rate, Koreans wouldn't be using Chinese characters on computers anyway, North or South, so this is an irrelevant historical detail by now.
What does the author mean by saying that "the code was written on a PC with Korean locale & language"? That the actual coding was done in Korean? What kind of programming language used by hackers is in Korean? I am not familiar with the details of the Sony case so I would like to be enlightened on what the author actually means here.