You should: Sign up > Write articles > tell people about your articles > Monetize them > Earn money  > learn/do/earn more

Aksai Chin

From Wikiafripedia, the free afripedia (encyclopedia)
Jump to navigation Jump to search

Aksai Chin
Disputed territory
Tianshuihai army service station in Aksai Chin
Tianshuihai army service station in Aksai Chin
Aksai Chin
A map of the disputed Kashmir region showing the Chinese-administered region of Aksai Chin
Coordinates: 35°7′N 79°8′E / 35.117°N 79.133°E / 35.117; 79.133Coordinates: 35°7′N 79°8′E / 35.117°N 79.133°E / 35.117; 79.133
Administering CountryChina

Aksai Chin (Template:Lang-ug;[1] Chinese: 阿克赛钦[2]; pinyin: Ākèsài Qīn) is a region administered by China as part of its Xinjiang and Tibet autonomous regions (mostly as part of Hotan County, Hotan Prefecture in Xinjiang[2]), claimed by India as part of the union territory of Ladakh and constituting the eastern portion of the larger Kashmir region which has been the subject of a dispute[3][4][5][6][7][8] between India and China since 1962.[9]

Name[edit source | edit]

The etymology of both words in Aksai Chin is disputed.[citation needed]

Majority of the sources interpret Aksai to be a word of Turkic origin with the meaning "white stone desert", this includes British colonial sources,[10][11] modern Western sources,[12][13][14][15] Chinese sources,[2][6] and number of Indian sources.[16][17] Instead of a desert, some modern sources also interpret it to mean "white brook".[18][19] However, at least one source interpret Askai to mean "eastern" of Yarkandi dialect.[20]

The meaning regarding the word "Chin" is disputed.[19] It is taken to mean "China" by most Chinese sources[2][6][1] some Western sources,[10][14] and few Indian sources.[20] At least one source take it to mean "pass".[18] Most other sources simply leave it out of their interpretations.[11][12][13][15][16][17]

History[edit source | edit]

Kashmir map big.jpg

Because of its 5,000 metres (16,000 ft) elevation, the desolation of Aksai Chin meant that it had no human importance other than as an ancient trade route, which provided a temporary pass during summer for caravans of yaks between Xinjiang and Tibet.[21] For military campaigns, the region held great importance, as it was on the only route from Tarim Basin to Tibet that was passable all year round. The Dzungar Khanate used this route to enter Tibet in 1717.[22]

One of the earliest treaties regarding the boundaries in the western sector was signed in 1842. Ladakh was conquered a few years earlier by the armies of Raja Gulab Singh (Dogra) under the suzerainty of the Sikh Empire. Following an unsuccessful campaign into Tibet in 1840, Gulab Singh and the Tibetans signed a treaty, agreeing to stick to the "old, established frontiers", which were left unspecified.[23][24] The British defeat of the Sikhs in 1846 resulted in the transfer of the Jammu and Kashmir region including Ladakh to the British, who then installed Gulab Singh as the Maharaja under their suzerainty. British commissioners contacted Chinese officials to negotiate the border, who did not show any interest.[25] The British boundary commissioners fixed the southern end of the boundary at Pangong Lake, but regarded the area north of it as terra incognita.[26]

The Johnson Line[edit source | edit]

Map of Central Asia (1873) from T. Douglas Forsyth. Khotan is near top right corner. The border claimed by the British Indian Empire is shown in the two-toned purple and pink band with Shahidulla and the Kilik, Kilian and Sanju Passes north of the border.
The map shows the Indian and Chinese claims of the border in the Aksai Chin region, the Macartney-MacDonald line, the Foreign Office Line, as well as the progress of Chinese forces as they occupied areas during the Sino-Indian War.

William Johnson, a civil servant with the Survey of India proposed the "Johnson Line" in 1865, which put Aksai Chin in Kashmir.[27][unreliable source?] This was the time of the Dungan revolt, when China did not control most of Xinjiang, so this line was never presented to the Chinese.[27][unreliable source?] Johnson presented this line to the Maharaja of Kashmir, who then claimed the 18,000 square kilometres contained within,[27][unreliable source?] and by some accounts territory further north as far as the Sanju Pass in the Kun Lun Mountains. The Maharajah of Kashmir constructed a fort at Shahidulla (modern-day Xaidulla), and had troops stationed there for some years to protect caravans.[28] Eventually, most sources placed Shahidulla and the upper Karakash River firmly within the territory of Xinjiang (see accompanying map).[citation needed] According to Francis Younghusband, who explored the region in the late 1880s, there was only an abandoned fort and not one inhabited house at Shahidulla when he was there – it was just a convenient staging post and a convenient headquarters for the nomadic Kirghiz.[29]Template:Primary-source-inline The abandoned fort had apparently been built a few years earlier by the Kashmiris.[30]Template:Primary-source-inline In 1878 the Chinese had reconquered Xinjiang, and by 1890 they already had Shahidulla before the issue was decided.[27][unreliable source?] By 1892, China had erected boundary markers at Karakoram Pass.[31]

In 1897 a British military officer, Sir John Ardagh, proposed a boundary line along the crest of the Kun Lun Mountains north of the Yarkand River.[28] At the time Britain was concerned at the danger of Russian expansion as China weakened, and Ardagh argued that his line was more defensible. The Ardagh line was effectively a modification of the Johnson line, and became known as the "Johnson-Ardagh Line".

The Macartney–Macdonald Line[edit source | edit]

The map given by Hung Ta-chen to the British consul at Kashgar in 1893. The boundary, marked with a thin dot-dashed line, matches the Johnson line[32]:pp. 73, 78

In 1893, Hung Ta-chen, a senior Chinese official at St. Petersburg, gave maps of the region to George Macartney, the British consul general at Kashgar, which coincided in broad details.[32]:pp. 73, 78 In 1899, Britain proposed a revised boundary, initially suggested by Macartney and developed by the Governor General of India Lord Elgin. This boundary placed the Lingzi Tang plains, which are south of the Laktsang range, in India, and Aksai Chin proper, which is north of the Laktsang range, in China. This border, along the Karakoram Mountains, was proposed and supported by British officials for a number of reasons. The Karakoram Mountains formed a natural boundary, which would set the British borders up to the Indus River watershed while leaving the Tarim River watershed in Chinese control, and Chinese control of this tract would present a further obstacle to Russian advance in Central Asia.[33] The British presented this line, known as the Macartney–MacDonald Line, to the Chinese in 1899 in a note by Sir Claude MacDonald. The Qing government did not respond to the note.[34] According to some commentators, China believed that this had been the accepted boundary.[35][36]

1899 to 1947[edit source | edit]

Both the Johnson-Ardagh and the Macartney-MacDonald lines were used on British maps of India.[27][unreliable source?] Until at least 1908, the British took the Macdonald line to be the boundary,[37] but in 1911, the Xinhai Revolution resulted in the collapse of central power in China, and by the end of World War I, the British officially used the Johnson Line. However they took no steps to establish outposts or assert actual control on the ground.[31] In 1927, the line was adjusted again as the government of British India abandoned the Johnson line in favor of a line along the Karakoram range further south.[31] However, the maps were not updated and still showed the Johnson Line.[31]

Postal map of China published by the Republic of China in 1917. The boundary in Aksai Chin is as per the Johnson line.

From 1917 to 1933, the Postal Atlas of China, published by the Government of China in Peking had shown the boundary in Aksai Chin as per the Johnson line, which runs along the Kunlun mountains.[32][36] The Peking University Atlas, published in 1925, also put the Aksai Chin in India.[38] When British officials learned of Soviet officials surveying the Aksai Chin for Sheng Shicai, warlord of Xinjiang in 1940–1941, they again advocated the Johnson Line.[27][unreliable source?] At this point the British had still made no attempts to establish outposts or control over the Aksai Chin, nor was the issue ever discussed with the governments of China or Tibet, and the boundary remained undemarcated at India's independence.[31]

Since 1947[edit source | edit]

Map including the Aksai Chin region (AMS, 1950)

Upon independence in 1947, the government of India used the Johnson Line as the basis for its official boundary in the west, which included the Aksai Chin.[31] From the Karakoram Pass (which is not under dispute), the Indian claim line extends northeast of the Karakoram Mountains through the salt flats of the Aksai Chin, to set a boundary at the Kunlun Mountains, and incorporating part of the Karakash River and Yarkand River watersheds. From there, it runs east along the Kunlun Mountains, before turning southwest through the Aksai Chin salt flats, through the Karakoram Mountains, and then to Panggong Lake.[21]

On 1 July 1954 Prime Minister Jawaharlal Nehru wrote a memo directing that the maps of India be revised to show definite boundaries on all frontiers. Up to this point, the boundary in the Aksai Chin sector, based on the Johnson Line, had been described as "undemarcated."[33]

During the 1950s, the People's Republic of China built a 1,200 km (750 mi) road connecting Xinjiang and western Tibet, of which 179 km (112 mi) ran south of the Johnson Line through the Aksai Chin region claimed by India.[21][31] Aksai Chin was easily accessible to the Chinese, but was more difficult for the Indians on the other side of the Karakorams to reach.[21] The Indians did not learn of the existence of the road until 1957, which was confirmed when the road was shown in Chinese maps published in 1958.[39]

The Indian position, as stated by Prime Minister Nehru, was that the Aksai Chin was "part of the Ladakh region of India for centuries" and that this northern border was a "firm and definite one which was not open to discussion with anybody".[21]

The Chinese minister Zhou Enlai argued that the western border had never been delimited, that the Macartney-MacDonald Line, which left the Aksai Chin within Chinese borders was the only line ever proposed to a Chinese government, and that the Aksai Chin was already under Chinese jurisdiction, and that negotiations should take into account the status quo.[21]

Despite this region being nearly uninhabitable and having no resources, it remains strategically important for China as it connects Tibet and Xinjiang. Construction started in 1951 and the road was completed in 1957. The construction of this highway was one of the triggers for the Sino-Indian War of 1962.[40] The resurfacing of the highway taken up for first time in about 50 years was completed in 2013.[41]

In June 2006, satellite imagery on the Google Earth service revealed a 1:500[42] scale terrain model[43] of eastern Aksai Chin and adjacent Tibet, built near the town of Huangyangtan, about 35 kilometres (22 mi) southwest of Yinchuan, the capital of the autonomous region of Ningxia in China.[44] A visual side-by-side comparison shows a very detailed duplication of Aksai Chin in the camp.[45] The 900 m × 700 m (3,000 ft × 2,300 ft)[citation needed] model was surrounded by a substantial facility, with rows of red-roofed buildings, scores of olive-colored trucks and a large compound with elevated lookout posts and a large communications tower. Such terrain models are known to be used in military training and simulation, although usually on a much smaller scale.

Local authorities in Ningxia claim that their model of Aksai Chin is part of a tank training ground, built in 1998 or 1999.[42]

In August 2017, Indian and Chinese forces near Pangong Tso threw rocks at each other.[46][47][48]

On September 11, 2019, People's Liberation Army troops confronted Indian troops on the northern bank of Pangong Lake.[49][50]

On May 5-6, 2020, there was a face-off between about 250 Indian and Chinese troops near Pangong Tso lake.[51][47][52][53][54][55]

Geography[edit source | edit]

Aksai Chin area
The Tarim River Basin, 2008
Northern plains of Aksai Chin looking towards Qitai Daban (Khitai Dawan)

Aksai Chin is one of the two large disputed border areas between India and China. India claims Aksai Chin as the easternmost part of the union territory of Ladakh. China claims that Aksai Chin is part of the Xinjiang Uyghur Autonomous Region. The line that separates Indian-administered areas of Ladakh from Aksai Chin is known as the Line of Actual Control (LAC) and is concurrent with the Chinese Aksai Chin claim line.

Aksai Chin covers an area of about 37,244 square kilometres (14,380 sq mi). The area is largely a vast high-altitude desert with a low point (on the Karakash River) at about 4,300 m (14,100 ft) above sea level. In the southwest, mountains up to 7,000 m (23,000 ft) extending southeast from the Depsang Plains form the de facto border (Line of Actual Control) between Aksai Chin and Indian-controlled Kashmir.

In the north, the Kunlun Range separates Aksai Chin from the Tarim Basin, where the rest of Hotan County is situated. According to a recent detailed Chinese map, no roads cross the Kunlun Range within Hotan Prefecture, and only one track does so, over the Hindutash Pass.[56]

Aksai Chin area has number of endorheic basins with many salt or soda lakes. The major salt lakes are Surigh Yil Ganning Kol, Tso Tang, Aksai Chin Lake, Hongshan Hu, etc. Much of the northern part of Aksai Chin is referred to as the Soda Plains, located near Aksai Chin's largest river, the Karakash, which receives meltwater from a number of glaciers, crosses the Kunlun farther northwest, in Pishan County and enters the Tarim Basin, where it serves as one of the main sources of water for Karakax and Hotan Counties.

The western part of Aksai Chin region is drained by the Tarim River. The eastern part of the region contains several small endorheic basins. The largest of them is that of the Aksai Chin Lake, which is fed by the river of the same name. The region as a whole receives little precipitation as the Himalayas and the Karakoram block the rains from the Indian monsoon.

The nearby Trans-Karakoram Tract is also the subject of ongoing dispute between China and India in the Kashmir dispute.[57][21]

Demographics and Economics[edit source | edit]

Prior to 1940s, the inhabitants of Aksai Chin are, for the most part, the occasional explorers, hunters, and nomads from India who pass through the area.[58][59][60]

Prior to European exploration in 1860s, there were some jade mining operations on the Xinjiang side of Aksai Chin.[60][61] They were abandoned by the time European explorers reached the area.[61] In the 1860s to 1870s, in order to facilitate trade between the Indian subcontinent and Tarim Basin, the British attempted to promote a caravan route via the western side of Aksai Chin as an alternative to the difficult and tariffed Karakoram Pass.[62] The route, referred to as the Chang Chenmo line after the starting point in Chang Chenmo River valley, was discussed in the House of Commons in 1874.[63] Unfortunately, in addition of being longer and higher elevation than Karakoram Pass, it also goes through the desolate desert of Aksai Chin.[62][63] By 1890s, traders have mostly given up on this route.[64]

In the 1950s, India collected salt from various lakes in Aksai Chin to study the economic feasibility of salt mining operations in the area.[65][66]

By the end of 1950s, in addition to have constructed a road, numerous PLA Ground Force outposts were constructed in a few locations, including at Tianwendian,[67] Kongka Pass,[68] Heweitan[69] and Tianshuihai.[70] The road was later upgraded to the China National Highway 219. Modern day, there are a few businesses along the highway serving motorists.[71]

In the 2010s, geological surveys were conducted in Western Kunlun region, which Aksai Chin is part of.[72] Huoshaoyun, a major lead-zinc deposit, and numerous smaller deposits were discovered in the region.[72] Huoshaoyun is a mountain located in Aksai Chin near the Tibetan border.[73] The mining development for Huoshaoyun started in 2017.[74][75]

Transportation[edit source | edit]

China National Highway 219 runs through Aksai Chin connecting Lhatse County (Lhazê, Lazi) and Xinjiang in the Tibet Autonomous Region.

See also[edit source | edit]

References[edit source | edit]

  1. 1.0 1.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  2. 2.0 2.1 2.2 2.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  3. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  4. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  5. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).(In the map, the Aksai Chin region is shown in grey whereas most of the territory of Xinjiang Uygur Autonomous Region is shown in blue-green.)
  6. 6.0 6.1 6.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  7. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  8. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  9. The application of the term "administered" to the various regions of Kashmir and a mention of the Kashmir dispute is supported by the tertiary sources (a) and (b), reflecting due weight in the coverage:
    (a) Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). (subscription required) Quote: "Kashmir, region of the northwestern Indian subcontinent ... has been the subject of dispute between India and Pakistan since the partition of the Indian subcontinent in 1947. The northern and western portions are administered by Pakistan and comprise three areas: Azad Kashmir, Gilgit, and Baltistan, the last two being part of a territory called the Northern Areas. Administered by India are the southern and southeastern portions, which constitute the state of Jammu and Kashmir but are slated to be split into two union territories. China became active in the eastern area of Kashmir in the 1950s and has controlled the northeastern part of Ladakh (the easternmost portion of the region) since 1962.";
    (b) Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil). C. E Bosworth, University of Manchester Quote: "KASHMIR, kash'mer, the northernmost region of the Indian subcontinent, administered partlv by India, partly by Pakistan, and partly by China. The region has been the subject of a bitter dispute between India and Pakistan since they became independent in 1947";
  10. 10.0 10.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  11. 11.0 11.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  12. 12.0 12.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  13. 13.0 13.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  14. 14.0 14.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  15. 15.0 15.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  16. 16.0 16.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  17. 17.0 17.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  18. 18.0 18.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  19. 19.0 19.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  20. 20.0 20.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  21. 21.0 21.1 21.2 21.3 21.4 21.5 21.6 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  22. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  23. Maxwell, India's China War 1970, p. 24.
  24. The Sino-Indian Border Disputes, by Alfred P. Rubin, The International and Comparative Law Quarterly, Vol. 9, No. 1. (Jan. 1960), pp. 96–125, JSTOR 756256.
  25. Maxwell, India's China War 1970, p. 25–26.
  26. Maxwell, India's China War 1970, p. 26.
  27. 27.0 27.1 27.2 27.3 27.4 27.5 Mohan Guruswamy, Mohan, "The Great India-China Game" Archived 30 September 2016 at the Wayback Machine, Rediff, 23 June 2003.
  28. 28.0 28.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  29. Younghusband, Francis E. (1896). The Heart of a Continent. John Murray, London. Facsimile reprint: (2005) Elbiron Classics, pp. 223–224.
  30. Grenard, Fernand (1904). Tibet: The Country and its Inhabitants. Fernand Grenard. Translated by A. Teixeira de Mattos. Originally published by Hutchison and Co., London. 1904. Reprint: Cosmo Publications. Delhi. 1974, pp. 28–30.
  31. 31.0 31.1 31.2 31.3 31.4 31.5 31.6 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  32. 32.0 32.1 32.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  33. 33.0 33.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  34. Woodman, Himalayan Frontiers (1970), pp. 102: "The proposed boundary seems never to have been considered in the same form again until Alastair Lamb revived it in 1964".
  35. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  36. 36.0 36.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  37. Woodman (1969), p.79
  38. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  39. China's Decision for War with India in 1962 by John W. Garver Archived 26 March 2009 at the Wayback Machine
  40. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  41. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  42. 42.0 42.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  43. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  44. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  45. Google Earth Community posting Archived 8 December 2008 at the Wayback Machine, 10 April 2007
  46. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  47. 47.0 47.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  48. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  49. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  50. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  51. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  52. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  53. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  54. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  55. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  56. Xinjiang Uyghur Autonomous Region Road Atlas (中国分省公路丛书:新疆维吾尔自治区), published by 星球地图出版社 Xingqiu Ditu Chubanshe, 2008, ISBN 978-7-80212-469-1. Map of Hotan Prefecture, pp. 18–19.
  57. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  58. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  59. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  60. 60.0 60.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  61. 61.0 61.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  62. 62.0 62.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  63. 63.0 63.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  64. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  65. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  66. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  67. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  68. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  69. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  70. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  71. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  72. 72.0 72.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  73. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  74. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  75. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).

Bibliography[edit source | edit]

External links[edit source | edit]

Template:Territorial disputes in East and South Asia