Jump to content

Talk:Gijang County

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Population

[edit]

Just a note on the population; the Busan English-language website [1] currently gives a figure of 242,600 people and some 74,500 households. However, this is at variance with the county's own statistical yearbook, and all other sources. Where the figure on the Busan site came from I'm not sure; my guess would be that someone transposed a decimal point (easy to do when switching between East Asian and Western systems), and then assumed that now-inflated households figure must actually refer to the population... -- Visviva 12:50, 13 August 2006 (UTC)[reply]

[edit]

Hello fellow Wikipedians,

I have just added archive links to one external link on Gijang County. Please take a moment to review my edit. If necessary, add {{cbignore}} after the link to keep me from modifying it. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—cyberbot IITalk to my owner:Online 00:54, 19 February 2016 (UTC)[reply]