In T10217#2687245, @Liuxinyu970226 wrote:

In T10217#2687244, @HenryLi wrote:

In T10217#2687230, @Liuxinyu970226 wrote:

In T10217#2687167, @HenryLi wrote:

In T10217#2683465, @Liuxinyu970226 wrote:

In T10217#2175710, @Kaihsu wrote:

The earlier comments show that the users who raised this issue were ignored. Because of this bug, the users have not been able to take advantage of some advances in software. For example, this link does not go to the correct mobile version: https://nan.m.wikipedia.org/ cf. https://fr.m.wikipedia.org/

If you're asking who resulted in these issues, per https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikipedia_Cantonese_2, that said, @Hillgentleman, @Pathoschild, @Felix Wan, @Chamdarae, @Harvzsf, @HenryLi, @Taichi, @Ffaarr, and @Servien

If you prefer to dig into the history of Cantonese Wikipedia, I can give you some brief information.
The proposal of Cantonese Wikipedia started from 2004 and was finally approved at the end of 2006. At that time, the code of Cantonese was "zh-yue" under the proposal of ISO-639. This code pre-dated the final standard, ISO 639-3:2007, which gave the code "yue" to Cantonese. When "yue" became final and we requested for code change in align with ISO 639-3:2007. This kind of discrepancy causes many requests for language code change on various wikipedias.

Huh, isn't yue already avaliable at 2006? http://www-01.sil.org/iso639-3/chg_requests.asp?chg_status=past said nothing about yue.

ISO 639-3:2007 was published by ISO on 1st February 2007 which was after the creation of Cantonese wikipedia. And it is three letter code standard for languages. It was known as DIS/ISO 639-3 which was under-development between 2002 and 2007. The original suggestion was with a prefix "zh" of ISO 639-1/2 for the family of Chinese languages. Cantonese is not the only case, so as Hokkienese.

There were a lot of debates and changes during the formation of DIS/ISO 639-3. You might notice some old codes like roa-rup and bat-smg in some old wikipedias. This was the consensus for the wikipedia community at that time.

cbk-zam? map-bms? roa-tara? ru-sib (defunct)? simple? tokipona (defunct)? too?

In T10217#2687230, @Liuxinyu970226 wrote:

In T10217#2687167, @HenryLi wrote:

In T10217#2683465, @Liuxinyu970226 wrote:

In T10217#2175710, @Kaihsu wrote:

The earlier comments show that the users who raised this issue were ignored. Because of this bug, the users have not been able to take advantage of some advances in software. For example, this link does not go to the correct mobile version: https://nan.m.wikipedia.org/ cf. https://fr.m.wikipedia.org/

If you're asking who resulted in these issues, per https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikipedia_Cantonese_2, that said, @Hillgentleman, @Pathoschild, @Felix Wan, @Chamdarae, @Harvzsf, @HenryLi, @Taichi, @Ffaarr, and @Servien

If you prefer to dig into the history of Cantonese Wikipedia, I can give you some brief information.
The proposal of Cantonese Wikipedia started from 2004 and was finally approved at the end of 2006. At that time, the code of Cantonese was "zh-yue" under the proposal of ISO-639. This code pre-dated the final standard, ISO 639-3:2007, which gave the code "yue" to Cantonese. When "yue" became final and we requested for code change in align with ISO 639-3:2007. This kind of discrepancy causes many requests for language code change on various wikipedias.

Huh, isn't yue already avaliable at 2006? http://www-01.sil.org/iso639-3/chg_requests.asp?chg_status=past said nothing about yue.

In T10217#2683465, @Liuxinyu970226 wrote:

In T10217#2175710, @Kaihsu wrote:

The earlier comments show that the users who raised this issue were ignored. Because of this bug, the users have not been able to take advantage of some advances in software. For example, this link does not go to the correct mobile version: https://nan.m.wikipedia.org/ cf. https://fr.m.wikipedia.org/

If you're asking who resulted in these issues, per https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikipedia_Cantonese_2, that said, @Hillgentleman, @Pathoschild, @Felix Wan, @Chamdarae, @Harvzsf, @HenryLi, @Taichi, @Ffaarr, and @Servien

I am glad to hear some good progress. I read through all the related issues and come across with this document.

This ticket opened in 2009 and now it is 2016. Why does it take 7 years without anything done? While it is not urgent and not trivial, there is a date it must be done. Please raise its priority and start a project as soon as possible to streamline the renaming process. It affects the consistence of user interface and the alignment to language code standard.