z-logo
open-access-imgOpen Access
Tibet in World War II
Author(s) -
Anatoly Sergeyevich Klinov
Publication year - 2022
Publication title -
naučnyĭ dialog/naučnyj dialog
Language(s) - English
Resource type - Journals
eISSN - 2227-1295
pISSN - 2225-756X
DOI - 10.24224/2227-1295-2022-11-3-415-438
Subject(s) - neutrality , china , politics , independence (probability theory) , memoir , regent , state (computer science) , empire , ancient history , convention , law , economic history , political science , autonomy , world war ii , sovereignty , independent state , history , ecology , statistics , mathematics , algorithm , computer science , biology
The author explores the causes and manifestations of Tibetan neutrality in World War II, based on reference materials, diplomatic documents and correspondence, program documents, memoirs, journalism. Evidence is given that Tibet, which was an autonomous state (with the status of political autonomy) under the suzerainty of China (according to the Simla Convention of 1914), aspired to independence. Lhasa aimed at the international recognition of the sovereign status of Tibet and its separation from China. It was revealed that the adoption of strict neutrality by Tibet in 1941 was due to the fact that the anti-Chinese abbot of the Taktra monastery Agvan Sungra took the post of regent under the young Dalai Lama. It is noted that the position of strict neutrality of Tibet was contrary to the Simla Convention of 1914, according to which Tibet recognized China’s suzerainty over itself. It is shown that Tibet’s refusal to let US and British Empire military supplies to China through India was a serious help to Japan, since in 1942 the Japanese army captured Burma, and Tibet became the only military supply route for China. It has been proven that Tibetan neutrality significantly limited the possibilities of China, the British Empire and the United States in the war against Japan.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here