Cited 0 time in
카자흐스탄의 지명 변화를 둘러싼 문제 연구
| DC Field | Value | Language |
|---|---|---|
| dc.contributor.author | 정경택 | - |
| dc.date.accessioned | 2022-12-26T23:32:37Z | - |
| dc.date.available | 2022-12-26T23:32:37Z | - |
| dc.date.issued | 2014-12 | - |
| dc.identifier.issn | 1598-3692 | - |
| dc.identifier.uri | https://scholarworks.gnu.ac.kr/handle/sw.gnu/19464 | - |
| dc.description.abstract | Kazakhstan has implemented a change of Russian place names (toponyms) into Kazah after its independence in 1991. At that time, a large number of Russian speakers expressed their concerns and criticism, but Kazakh government adopted a law (Zakon "Ob adminictrativno- territorial'nom ustrojstve Respubliki Kazakhstan 1993) to justify replacing places of residence of the administrative areas. Thus from 1991 to 2005, 12 cities, 53 provinces(rajon), 7 city boroughs(rajon v gorode), 43 train stations, and 957 residences have been renamed, and also other 890 different physical-geographical objects and public names have been changed or created. Until now Kazakh nationalist-patriots argue that Kazakh names are placed on a restricted status when they still see the presence of Russian place names. For example, Petropavlovsk, Pavlodar, Semipalatinsk, and Ust'-Kamenogorsk survived during the massive renaming process in the 1990s. These cities are the symbol of the colonial period of the Soviet dictatorship to Kazakh people. The renaming policy temporarily ceased because the government was afraid of severe resistance and migration outflow of Russians in Kazakhstan. However, after the deadline for the moratorium of rename, Kazakhstan Parliament raised the issue of renaming Petropavlovsk, in order to reduce the use of Russian language and to exclude the Russian speakers. Although the majority of the Russian population in Petropavlovsk and some state legislators and city council (городский совет) opposed the renaming, but if a special law in which the opinions of inhabitants do not need be reflected in the renaming process, is adopted, the process will be inevitable. Now the status of Russian language in Kazakhstan is extremely complex. The concept of Kazakhization(Казахизация) has been publicized throughout the society. Furthermore, the claim of changing their writing system from Cyrillic to Latin came to the fore and thus it is more likely to be forced to comply with Kazakh language norms. | - |
| dc.format.extent | 18 | - |
| dc.language | 한국어 | - |
| dc.language.iso | KOR | - |
| dc.publisher | 동북아시아문화학회 | - |
| dc.title | 카자흐스탄의 지명 변화를 둘러싼 문제 연구 | - |
| dc.title.alternative | A Study on Renaming of Toponyms in Kazakhstan | - |
| dc.type | Article | - |
| dc.publisher.location | 대한민국 | - |
| dc.identifier.doi | 10.17949/jneac.1.41.201412.029 | - |
| dc.identifier.bibliographicCitation | 동북아 문화연구, v.1, no.41, pp 519 - 536 | - |
| dc.citation.title | 동북아 문화연구 | - |
| dc.citation.volume | 1 | - |
| dc.citation.number | 41 | - |
| dc.citation.startPage | 519 | - |
| dc.citation.endPage | 536 | - |
| dc.identifier.kciid | ART001953256 | - |
| dc.description.isOpenAccess | Y | - |
| dc.description.journalRegisteredClass | kci | - |
| dc.subject.keywordAuthor | Kazakhstan | - |
| dc.subject.keywordAuthor | Law on Languages | - |
| dc.subject.keywordAuthor | Changes of administrative-territorial | - |
| dc.subject.keywordAuthor | Kazakh language | - |
| dc.subject.keywordAuthor | Russian language | - |
| dc.subject.keywordAuthor | 카자흐스탄 | - |
| dc.subject.keywordAuthor | 언어법 | - |
| dc.subject.keywordAuthor | 행정구역개편 | - |
| dc.subject.keywordAuthor | 카자흐어 | - |
| dc.subject.keywordAuthor | 러시아어 | - |
Items in ScholarWorks are protected by copyright, with all rights reserved, unless otherwise indicated.
Gyeongsang National University Central Library, 501, Jinju-daero, Jinju-si, Gyeongsangnam-do, 52828, Republic of Korea+82-55-772-0532
COPYRIGHT 2022 GYEONGSANG NATIONAL UNIVERSITY LIBRARY. ALL RIGHTS RESERVED.
Certain data included herein are derived from the © Web of Science of Clarivate Analytics. All rights reserved.
You may not copy or re-distribute this material in whole or in part without the prior written consent of Clarivate Analytics.
