Wikipedia talk:Manual of Style/India-related articles

Use of Slokas
Can we use slokas in articles. A on going debate is at Talk:Sritattvanidhi. I think this may be incorpoareted into this MOS. Amartyabag  TALK2ME  06:58, 12 August 2007 (UTC)

Scope of this project
So far the main development here is the incorporation of most of the content of Naming conventions (Indic). I suggest that that Naming convention article should remain separate and active, and that this Manual of Style should only make reference to the it for appropriate cases. Reasons;
 * that naming convention would also apply to articles that were not specific to India (the modern country); including articles about some of the neighbouring countries, and to the Pali language.
 * that article was always intended to deal with old Indian languages (for history, religion and so on). India has names that do not derive from Indic languages. These include Arabic, Persian, and English names.
 * the naming convention was not intended or written with modern names in mind. For a current example, the naming convention (or this manual of style) would be of little help in the recent dispute over Bengaluru / Bangalore, which is the sort of thing that should be addressed here. (According to the naming convention, Bangalore should be renamed Bengalūru, not Bengaluru, and I don't suppose anyone will support that). The existing, very sketchy 'Modern names' section should be expanded to deal with these.

Imc 15:44, 29 August 2007 (UTC)

Biographical naming conventions
Editors behind this proposal may wish to step in at Talk:Mohandas_Karamchand_Gandhi (see also the immediately preceding discussions) where there is a discussion about whether to change the article name of Mahatma Gandhi. Currently it is named 'Mohandas Gandhi' while others are in favour of 'Mohandas Karamchand Gandhi', while other prefer the original 'Mahatma Gandhi'. This MOS for India-related articles has been invoked at the current discussion but, despite saying so on the MOS articlespace that 'Mahatma Gandhi' is preferred, there is doubt as to whether this should be implemented on account of this MOS being a proposed guideline. So, in any case, editors may wish to step in over there and contribute their thoughts. Thanks, Ekantik talk 19:56, 1 December 2007 (UTC)

Resurrection of this MoS page
A recent decision on the use of indic scripts in the leads of India-related articles was made (see main discussion here and clarification here). This decision has not been properly communicated and User:DeltaQuad and I agree that it should be placed in the Manual of Style somewhere. The most appropriate place would be in this India-related articles subpage, but it is currently inactive. Surely there are now enough India-related article to warrant the resurrection of these guidelines. What are your thoughts? Bazonka (talk) 08:56, 24 February 2012 (UTC)
 * I did not realise that this section of MOS had ever existed. By all means, resurrect it after a period of review. I'll wander through the thing over the next few hours. - Sitush (talk) 09:04, 24 February 2012 (UTC)
 * One for a section on lead sections: WT:INB reached a consensus sometime mid/late 2011 that specific varna status should not be referred to in the lead section of caste/community articles. I'll try to find the link to the discussion. - Sitush (talk) 09:09, 24 February 2012 (UTC)
 * This may be that varna discussion, although it seemed to deteriorate into a "bash Sitush" type of thread. Nothing new, then! - Sitush (talk) 09:26, 24 February 2012 (UTC)
 * I can't be bothered to read all of that discussion now, but assumuing a decision was reached (which isn't clear from the little I've read), then that's exactly the sort of thing that should be in this MoS article. Bazonka (talk) 09:41, 24 February 2012 (UTC)

I'm no expert on India topics, so I will defer to the wider community: is there anything that's currently in this MoS article that shouldn't be there or needs to change? If not, I suggest taking the inactive template off the top, and relinking it into Category:Wikipedia Manual of Style (regional), etc. We can then start to improve it with stuff about varnas and indic scripts and so on. Bazonka (talk) 09:45, 24 February 2012 (UTC)
 * I think that it needs some discussion before the template is removed. For example, I can see that some people might have problems with the guideline preferring British English and Indian units (lakhs etc). If this is made active now then some pretty fundamental concepts are raised to the status of something that has current consensus when in fact the consensus may have changed. We need a structured discussion here of the various aspects. I emphasis structured because my experience is that discussion of such things tend to deteriorate pretty fast.- Sitush (talk) 09:59, 24 February 2012 (UTC)
 * I agree. One option would be to remove anything remotely controversial from the page, and make the uncontroversial stuff active (even if there isn't very much). Then separate discussions can be held about each controversial part, rather than one big amorphous bunfight of a discussion. The MoS page can then grow over time as (and if) consensus is reached for each discussion. Bazonka (talk) 10:05, 24 February 2012 (UTC)
 * I cannot really comment on the transliteration bit (I am monoglottal) but the section regarding district naming is also currently being discussed. Tbh, I do not think that there is much in the inactive version that does not require review. The only dead cert is probably the recent RfC regarding scripts in lead sections. - Sitush (talk) 11:28, 24 February 2012 (UTC)

I agree that this needs to be resurrected. IMO, the following are controversial: IMO, Naming conventions (Indic) (linked in here) also needs to be discussed and made a policy, rather than proposed one. -- Redtigerxyz Talk 16:16, 26 February 2012 (UTC)
 * Scope: "Religions originating in India, including Hinduism, Sikhism, Jainism. Articles on Buddhism may follow this convention, Mythology of India" All wikiProjects related to Indian Religions need to be consulted before imposing the MOS on articles related to them
 * "Use only British English spellings as per the guidelines for India related pages": change to Indian English??? Eg. the word cock is usually used in Indian English for "the adult male of the domestic chicken", however America (or Britain not sure) use the vulgar connotation. The word "rooster" can be used in American English in this context.
 * This is another proposed addition to the naming convention needs to be updated
 * "However, exceptions may apply to individuals who are widely known by an honorific name or with a title. Examples are Mahatma Gandhi where Mahatma is an honorific" The page is no more at the title Mahatma Gandhi. The honorifics are dropped. Need to update the honorific policy and form a consensus
 * "Naming and transliteration" is controversial. There are many written totally in IAST eg. Bhaṭṭikāvya, which are affected. Needs to be discussed.

MOS is now live
Since no-one objected to the resurrection of this page, I have made a few amendments and reinstated it under Category:Wikipedia Manual of Style (regional). The changes that I have made to it are: I have not included anything about the decision mentioned above not to use Indic scripts in the leads of articles. This seems like a controversial decision requiring further discussion and consensus. The points raised above by User:Redtigerxyz also require further discussion. Bazonka (talk) 09:04, 11 March 2012 (UTC)
 * 1) A few non-controversial spelling and punctuation fixes.
 * 2) Removal of the "Geographic articles" section because each of its subsections was disputed. I would recommend discussing and reinstating this as soon as possible.
 * 3) Change the spelling guideline from use of only British English to use of only Indian English. This seemed like an obvious change.
 * 4) Removal of text about religion and mythology as per User:Redtigerxyz's concern above.
 * 5) Removal of the "Naming and transliteration" section as per User:Redtigerxyz's concern above.
 * 6) Removal of text about people who are widely known by honorific titles, as per User:Redtigerxyz's concern above.

Conflicting policies
At, it says that Indic script is not to be used in the lede sentence of an article:
 * There is community consensus that the lead sentence of an article should not contain any regional or Indic language script. It is suggested that IPA be used for help with pronunciation. For details, refer to this RfC: Native languages in lead.

However, at, it says that Indic script is to be used in the lede and gives the example:
 * Sikhism is a ...
 * Sikhism is a ...

This is more consistent with article practice, too.

So, which is it? —&#91;  Alan M 1  (talk) &#93;— 06:37, 19 July 2013 (UTC)

Translations in Infoboxes
In Infoboxes for places, there are the parameters name, official_name, other_name, native_name, and native_name_lang (ignoring the tranlit* params for now). The first three are specified to be in English with Latin script.

The question is what to do with the others. The fact that native_name_lang exists says to me that the design is to support the predominant non-English language/non-Latin script name of the place, like:

or this, using the Lang-hi template wrapper around the script to prepend the Hindi link:

The notes say that if multiple names/languages are to be specified, to wrap the names in, but this doesn't specify which language the names are in like Lang-xx does. Example:

What about pronunciation guides, like ? —&#91;  Alan M 1  (talk) &#93;— 09:12, 19 July 2013 (UTC)

BTW, this came up because of a string of edits by User:101.0.38.163, adding Indic script names to native_name on various articles on places without moving what alternative names were already there or changing/adding the language to native_name_lang. —&#91;  Alan M 1  (talk) &#93;— 10:30, 19 July 2013 (UTC)


 * Are you familiar with WP:INDICSCRIPT and the various discussions that gave rise to it and that have subsequently taken place at WT:INB? - Sitush (talk) 10:32, 19 July 2013 (UTC)
 * Sorry, you've posted two queries in two sections, and I missed the one above. Clearly, you are aware to some extent. The quick solution that avoids all this mess and more is not to have the scripts anywhere. They cause a phenomenal number of problems, including outright vandalism that doesn't get picked up because insufficient contributors can understand the scripts. - Sitush (talk) 10:37, 19 July 2013 (UTC)

City names
Is there a convention for handling new/old city names, (Mumbai/Bombay), specifically in historical articles? Thanks for the help! Lfstevens (talk) 04:26, 3 July 2014 (UTC)


 * Use the name that was used at the time the event occurred. This can be especially important for some geographical entities; for example, British India was geographically very different to India as it is known today. - Sitush (talk) 17:14, 3 July 2014 (UTC)

Handling numbers
I have just amended the wording here. - Sitush (talk) 10:50, 6 September 2014 (UTC)

Alphabetical order for names
When a list of personal names in an India-related article is sorted alphabetically, which name order should be used for sorting? If the family name is usually placed last (western order) then a list of names should probably be sorted by the last name. I am looking at Sir Jamsetjee Jeejebhoy School of Art, which is currently sorted by the full name, so that Francis Newton Souza is listed before John Fernandes. In a European or a North-American article I would change this. What should be the convention for India-related articles? Verbcatcher (talk) 12:54, 27 July 2015 (UTC)

Naming conventions
This article says "After the initial mention of any name, the person may be referred to by surname only." This is not always true. Many people use the personal name. For example, see R. K. Narayan, where he is known by his personal name (Narayanan) and not his surname (Rasipuram, actually village name). Anbumani Ramadoss is Anbumani, son of Dr. Ramadoss. Another example is V. Anand, sometimes wrongly expanded as Vishwanathan Anand. (Anand is his given name and the correct expansion is Anand Vishwanathan.) Also, "The last name or the family name is placed before the first name for Telugu people." This is also found in Kerala, as in V. S. Achuthanandan, where Velikkakathu is his surname, and Achuthanandan his given name. As far as I know, this style is restricted to South India. Jose Mathew (talk) 11:23, 6 February 2016 (UTC)

Merge WP:INDICSCRIPT to MOS:INDIA's "Lead and infobox" section
The rationale and consensus history (the links/diffs for which should be put into a footnote) at WP:WikiProject India belong in the MOS:INDIA page; they serve no purpose buried on the wikiproject page where no one will see them but active participants in the wikiproject. Without that material, the one-liner in the present guideline looks like arbitrary nonsense, and is easily dismissed as some consensus-free WP:CREEP someone added without discussion.

I did some cleanup work on the material to make it "MoS-styled" language, and actually guideline-worthy. It had a bunch of WP:OWNish wording (I don't mean that too critically, it's just a common problem in stuff written at wikiprojects), was very unclear in certain ways, and had some grammar problems).

After merging, the WP:INDICSCRIPT shortcut (and a MOS:INDICSCRIPT one) should redirect to what is presently the "Lead and infobox" section in MOS:INDIA, though this would be better named "Indic script in leads and infoboxes" since it does not cover anything else, and it doesn't stand out in the table of contents without "Indic" in it.

— SMcCandlish ☏ ¢ &gt;ʌⱷ҅ᴥⱷʌ&lt;  02:04, 11 November 2017 (UTC)
 * Support merge, and strong support MOS:INDICSCRIPT redirect, which I've been acting as if it is anyway. However, leave a meaningful stub in the current place as well, since this is one of the most common project guidelines newcomers will need to know, and the more places it is mentioned the better. --Muhandes (talk) 17:49, 11 November 2017 (UTC)
 * Support per nom. Let There Be Sunshine (talk) 09:51, 4 December 2017 (UTC)
 * Comment I may be too busy to implement this, should the idea gain consensus; I trust someone else can handle it.  — SMcCandlish ☏ ¢ &gt;ʌⱷ҅ᴥⱷʌ&lt;  11:20, 4 December 2017 (UTC)

Implementation
This is regarding the implementation per the above discussion.

I moved the relevant material and updated the links. There is, however, the matter of the "Preferred format for introducing the article subject" section and onwards, which now makes much less sense. The example given, Sikhism, is especially bad since it it can always be argued that it's not even predominantly within the scope of WikiProject India but more in the scope of WikiProject Religion. The entire point of the section was how to use Indic in the lead section, are we now recommending its use at all? --Muhandes (talk) 12:04, 21 December 2017 (UTC) I read it again and it is just too confusing to keep. I commented out the entire thing, here it is for further discussion

Preferred format for introducing the article subject
Ideally, when introducing an article that is covered by this guideline, IPA transcriptions (with audio files if possible) and transliterations of the Indic script should be included. The format is:


 * Simplified Transliteration ...

A special template has been made to take care of formatting issues.

Use this format when you have the original script text, transliteration, IPA and audio pronunciation file.




 * Example:


 * Sikhism is a...
 * Sikhism is a...

Without audio
Use this when you have the original script text, transliteration and IPA but do not have the audio pronunciation. This is likely to be the most used format.




 * Example:


 * Mumbai is a...
 * Mumbai is a...

Pinging User:SMcCandlish and User:Let There Be Sunshine --Muhandes (talk) 12:17, 21 December 2017 (UTC)
 * On a quick once-over, the problem appears to be that this is being written about leads when we don't want to use Indic in leads. If the material were rewritten to be about use of Indic in our text in general (with a reminder that we don't use it in the lead, "see above", then some of the material could be restored into "Non-English strings" somewhere, though Sikh stuff should just be an example. We would never do "Simplified Transliteration" which is against both MOS:BOLD and MOS:CAPS ("simplified transliteration" is just fine), and we would not normally include audio without a really good reason. The audio stuff is already covered, in a non-topic-specific manner, at MOS:AUDIO  MOS:PRON, so it need not be covered here at all except with short cross-references, like "For when to include a link to an audio pronunciation file, see WP:Manual of Style/Pronunciation."  — SMcCandlish ☏ ¢ &gt;ʌⱷ҅ᴥⱷʌ&lt;  22:03, 21 December 2017 (UTC)
 * I'm thinking what I did as first-aid (commenting out the entire section) might be the best solution. The entire thing is just an explanation of how to use Indic which does not seem to apply as a WP:MOS anyway and is covered elsewhere. --Muhandes (talk) 19:11, 23 December 2017 (UTC)

I suggest not to mention state/UT name because when reorganization of any state will occur, each assembly constituency state will need to be changed. Sid54126 (talk) 14:00, 12 February 2020 (UTC)
 * , I think you meant this to go elsewhere (probably three sections below). --Muhandes (talk) 14:10, 12 February 2020 (UTC)

Nonsense about wikiproject scope
Articles do not belong to wikiprojects. Someone added stuff about the "don't use Indic script in leads and infoboxes" somehow only applying to WikiProject India articles. I've objected to this, Corinne has as well, on another page, and it just doesn't make any sense. It's directly against WP:CONLEVEL and WP:OWN policy and the WP:ARBINFOBOX ruling against projects trying to assert authority over entire categories of articles. I've removed this twice and been reverted on the basis that there will allegedly be controversy if I"m not. Show us the controversy.

The wording of the contested material has now been changed to "This avoidance of Indic scripts only applies to articles that are predominantly India-related and is excluded from, among others, articles about Hinduism, Buddhism, Pakistan or any of India's neighbouring countries." What?! Articles about these religions are not magically disassociated from India as a topic. This result is literally under policy. If Indic script is a problem for readers in articles that pertain to India, it does not magically become a non-problem when the topic is Bangladesh. Wikiprojects on Pakistan and Jainism cannot declare "their" article immune to guidelines that are based on a practical consensus that our leads and infoboxes should not have indic script in them for well-articulated reasons. That's Indic script, not Indian script. This is a site-wide MoS guideline, not a wikiproject advice page essay. If projects on Hinduism and Bangladesh really want to assert that there is no consensus to apply this rule to any article they say is within their scope, then the Indic script rule actually does not have consensus. But I don't see any evidence of that. I see one editor trying very hard to shoe-horn wikilawyering language into this guideline for no clear reason.

PS: If we need to explain that there can be exceptions, e.g. where the very topic is an Indic word like Aum, familiar even in written form around the world, then we should do so. There is no exception for "this politician is Maldivian, so we can use Indic script as much as we want to." — SMcCandlish ☏ ¢ &gt;ʌⱷ҅ᴥⱷʌ&lt;  23:36, 5 January 2018 (UTC)
 * It's not about Indic scripts, and never has been, it's about "Indian" scripts. If an article is related to India, then the community has decided that it's not desirable to include native scripts in the lede or the infobox regardless of whether those native scripts are Indic or something else, e.g. Urdu. Clarifying the scope is kind of redundant: this is after all, the MOS page for India-related articles (and before this was moved here, it was within WP INDIA's internal project space). However, WP:INDICSRIPT is used and quoted so often that there was a history of incidents with editors missing that point and starting to remove e.g. Sanskrit names from Buddhism articles, or Urdu native names from Pakistan-related articles.
 * Anyway, if you'd like to change the guideline to have broader scope than it currently has, you can of course start and RfC, but unlike all the previous ones it will need to 1) be on a page different from the talk page of WP INDIA, and 2) be advertised to the projects concerned. However, this is unlikely to draw much support as the situation that led to the adoption of this guideline (= regular editors being sick of people edit-warring over which script(s) to include and in what order) doesn't hold for any of the related projects. – Uanfala (talk) 00:45, 6 January 2018 (UTC)
 * Really? I may be wrong but I thought the RfC etc said Indic? The underlying problem, though, does have history either on this page or some other. Something to do with local (ie: project) consensus cannot over-ride general community consensus. That's a big issue because all someone has to do is add another project banner to a talk page and an article instantly becomes exempt from the India project consensus. Whether it is a problematic issue is another matter. Personally, I'd rather see it applied site-wide for the reasons that have already been discussed to death in numerous past threads and because I feel that if a project can re-work general notability guidelines with local consensus - NSPORT, NPROF etc - then we're on the cusp of doing the same sort of thing with Indic scripts anyway. The fact is, they're pretty much unworkable and the value of retention is really of minimal (not zero, but minimal) utility for our readership: if you know it, you know it ... and if you do not then you probably couldn't care less. - Sitush (talk) 01:21, 6 January 2018 (UTC)
 * Sitush, do you suggest that any of the editors who opposed the inclusion of say Devanagari or Tamil scripts in the lede would have been happy with retaining Urdu? all someone has to do is add another project banner to a talk page and an article instantly becomes exempt from the India project consensus – that's why that bit in the text says "predominantly India-related". – Uanfala (talk) 01:38, 6 January 2018 (UTC)
 * Any script is a problem. Defining India is also a problem, eg: in theory most Pakistan-related tribe articles are also India-related: Pakistan has only been around for a few years and it was a part of India for much longer. We have to assume a bit of common sense here. - Sitush (talk) 15:00, 6 January 2018 (UTC)

blanket ban per WP:INDICSCRIPT
I understand the reasoning for WP:INDICSCRIPT, but the ban seems excessive. For example, gujarati film Dhh has a clear case of indic script in lead and/or infobox. There are no claims of multiple language to be added here, so why can't we refine policy to allow such cases? Coderzombie (talk) 13:10, 13 April 2018 (UTC)
 * There has been quite a number of discussions on the matter over the years, and I think the simplest way is to explain it is that there is no way to leave the door half-open. Since the alternative was worse, the community has chosen to leave the door tightly closed. Maybe one day consensus will change. --Muhandes (talk) 22:30, 14 April 2018 (UTC)

Diacritics, use or not?
This guideline is unclear on whether or not to use diacritics, and in what circumstances. Devanagari or Devanāgarī? Aryabhata or Āryabhaṭa?

Should diacritics be "extended?" (Brihadisvara, Brihadiśvara, or Brihadishvara?)

Should they be used for all terms that can be transcribed with IAST (this would be excessive, imo), or just technical Sanskrit terms/names for historical/religious topics? The latter is my preference, for words like parinirvāṇa.

Should they be used for article names? In leads? General text?

Overall diacritic usage is very inconsistent across the wiki, I hope a standard can be set. - A Morozov  &#9001;talk&#9002; 12:18, 9 May 2020 (UTC)
 * The question is not one of whether to use diacritics or not, but which transliteration standard to use. As the section on Non-English strings outlines, ISO 15919 should be used for all Indic languages except for Sanskrit, where IAST is used conventionally. I have proposed to switch to ISO for Sanskrit as well (see the section below), but that's the policy for the moment. By "without diacritics", I assume you mean using the Hunterian transliteration scheme, the official scheme used by the Indian government. In that scheme, it can be written as Brihadishvara. Brihadisvara is incorrect; it's not a matter of simply dropping the diacritics from the ISO/IAST transliteration to reach Hunterian transliteration. All in all, I'd say use ISO (preferably) or Hunterian for all Indic languages except for Sanskrit, for which you should be using IAST. Getsnoopy (talk) 01:52, 16 January 2021 (UTC)

Gandhi
In section "Indic scripts in leads and infoboxes", we are admonished not to use Indic scripts in the lede section. In the very next section, "Linking to other Indian Language Wikipedias", an example lede fragment is given which violates this rule. The article it refers to, Mahatma Gandhi, does not display the same lede. Elizium23 (talk) 11:03, 15 May 2020 (UTC)

Avoidance of Indic scripts makes no sense
The decision was made because there are too many Indian languages? This makes no sense, because there are only 2 official languages in India, English and Hindi. Adding Hindi can help millions of people who only know, speak and write in Hindi to find articles on wikipedia. Not all English wikipedia articles have a hindi translation. Such a decision only prevents wikipedia's accessibility. For people, companies, and organizations that operate mostly on the state level. State languages can be included as an when deemed necessary. It seems regressive to avoid the usage of Indic scripts when for every other country, a local language translation is offered — Preceding unsigned comment added by Debitpixie (talk • contribs) 11:50, 3 June 2020 (UTC)

Prefer BCE/CE
I propose a policy of preferring the secular BCE/CE as opposed to BC/AD for Indian articles being added under the "Basic India conventions". Many articles on Indian topics seem to follow this convention already (e.g., India, Karma, Hinduism), but my proposal is to codify it as a preference. Getsnoopy (talk) 04:37, 26 August 2020 (UTC)

Prefer ISO 15919 over IAST
I propose preferring ISO 15919 over IAST for all Indic-language transliterations, and adding this to the conventions page. IAST is essentially a subset of ISO 15919, barring a couple cases where it's different, and the latter allows for all Indic languages to be unambiguously represented. Along the same lines, the recommended template for transliterations should be changed to  instead of , as the former allow specifying the transliteration scheme used as well, which is important in many cases. Getsnoopy (talk) 17:17, 26 August 2020 (UTC)

Category:Government of Bangalore should be deleted since it is named after a an entity which never existed
Category:Government of Bangalore should be deleted since it is named after a an entity which never existed. Usage of terms Government of Karnataka and Government of India should be entertained but there is (or was) nothing by the name Government of Bangalore. If you want to categorize agencies associated with Bangalore, then we can use Category:Bruhat Bengaluru Mahanagara Palike for Pages dedicated to Agencies associated with Municipal Corporation. Similarly other Pages which are using Category:Government of Bangalore can use Category:Bangalore. Talk Page Talk. -Vijethnbharadwaj (talk) 17:14, 19 January 2021 (UTC)


 * This is the wrong forum for deleting or merging a category. Take it to WP:CFD where it will have wider attention. Timrollpickering (talk) 19:29, 19 January 2021 (UTC)
 * Agree with Timrollpickering. --Rsrikanth05 (talk) 21:31, 19 January 2021 (UTC)

Is this okay?
So if on an India-related geography article, can I put Indic script and then Latin script? It doesn't say you can't according to WP:INDICSCRIPT. For example, can I put in the "nativename" section the Hindi name for a place and then below that the Latin transliteration? 2001:8003:C829:E400:F091:1EFE:F47B:624B (talk) 07:03, 27 June 2021 (UTC)
 * That's requires a very imaginative reading of Avoid the use of Indic scripts in lead sections or infoboxes.. Avoid it. --Muhandes (talk) 09:15, 27 June 2021 (UTC)
 * Some geographical names in India have been used with multiple spellings in Roman. For example The name of the city in Hindi जबलपुर follows the exact native pronunciation and has not changed. In Roman it has been Jubbulpore, Jubbalpur, Jabalpur etc. In that case it is advantages to use the Indic text. One distinct advantage of using the Indic text is that the text string can be used to search publications in Indian languages (newspapers and books). For example see which will search for जबलपुर in Hindi newspapers.


 * Malaiya (talk) 02:01, 28 July 2021 (UTC)
 * I know what you mean. I have a lot of examples, for one being Guntur which was written as గుంటూరు which transliterates to Gunturu. Can't say about other languages in other countries, but this is common in Indic scripts. For this change, you'll need to achieve consensus in the WP:INDICSCRIPT context. -- DaxServer (talk) 08:59, 28 July 2021 (UTC)

All non-Sanskrit transliterations should use ISO 15919
This policy is already implied in the current policy and followed on most articles, but my proposal is to make it explicit. If no one objects to this in about a week's time, I will be amending the text accordingly in. Getsnoopy (talk) 19:42, 12 November 2021 (UTC)

Legislative Assembly constituency names
I am noticing some confusion about what are the correct and uniform names for the Indian state assembly constituencies. Articles are titled using Vidhan Sabha constituency, Vidhana Sabha constituency, Assembly constituency, Legislative Assembly, State Assembly constituency and Union Territory Assembly constituency etc.

I propose to name change of the all State and Union Territory assembly constituencies, for example, from Khanapur (Vidhan Sabha constituency) to Khanapur (Maharashtra State Legislative Assembly constituency), Khanapur (Assembly constituency) to Khanapur (Telangana State Legislative Assembly constituency), Khanapur (Vidhan Sabha constituency (Karnataka)) to Khanapur (Karnataka State Legislative Assembly constituency) and Islampur (Maharashtra) (Vidhan Sabha constituency) to Islampur (Maharashtra State Legislative Assembly constituency) etc. Italawar (talk) 14:49, 31 January 2020 (UTC)


 * The standard name should be "XYZ (Legislative Assembly constituency)". In the case of multiple constituencies in different states having the same name, the format should be "XYZ (ABC Legislative Assembly constituency)". Using "Vidhan Sabha" in the title will be a cause for conflicts. In the future, someone may argue that Karnataka constituencies should instead use the term "Vidhana Soudha". Better to go with the English term. Bharatiya  29  15:04, 1 February 2020 (UTC)
 * I support Bharatiya suggestion, there is no need to list the state if no further disambiguation is needed. Number 57's proposal below is more complete so I prefer it. --Muhandes (talk) 16:41, 1 February 2020 (UTC)
 * I too support Bharatiya's suggestion. TryKid (talk) 19:13, 5 February 2020 (UTC)
 * Bit of a late reply, but Karnataka's Legislative Assembly is called a Vidhan Sabha. It's only the building that's called the Vidhana Soudha. Wilhelm Tell DCCXLVI converse &#124; fings wot i hav dun 03:13, 20 April 2021 (UTC)


 * I propose the uniformed nomenclature "XYZ (ABC Assembly constituency)", where XYZ is the constituency name and ABC is the State/UT name. That way we wouldn't need to put the titles, "State Legislative Assembly constituency" or "Union Territory Assembly constituency" separately the for the states and union territories.


 * Also the "XYZ (Legislative Assembly constituency)" as proposed by Bharatiya29 is unusually long title and thus not desirable. For example, "Ghosi (Uttar Pradesh Legislative Assembly constituency)" can simply be titled "Ghosi (Uttar Pradesh Assembly constituency)" — Hemant DabralTalk  17:15, 1 February 2020 (UTC)
 * There are two issues here. You propose to use "Assembly constituency" instead of "Legislative Assembly constituency". To this I do not oppose. However, you also propose to always use the state, which I think makes the titles unnecessarily too long in 99% of the cases. If there is no disambiguation needed, don't disambiguate. --Muhandes (talk) 17:44, 1 February 2020 (UTC)


 * There is no need to put State/UT in the title irrespective of the fact ehther the State name is mentioned or not. The legislative body of a state is called the legislative assembly for both states and partial states (Delhi, Puducherry, J&K). Bharatiya  29  19:36, 1 February 2020 (UTC)


 * Keeping the name of a State/UT in titles will bring the uniformity in all of these constituency pages and at the same time it will rule out any chance of ambiguity. It'd look odd if some constituencies in a state (disambiguation pages) have the state name in titles and other constituencies don't have it. It's rather more practical to use State/UT name to achieve uniformity so we don't have to use different titles (one for disambigous pages and other for normal pages) for the various consistencies of a same State/UT. — Hemant DabralTalk  22:45, 1 February 2020 (UTC)
 * While I see why uniformity can be valued, it is no excuse to needlessly extend all titles, and is generally not the way disambiguators work. There are thousands of examples of this in Wikipedia, but just one, in how song disambiguators work, we have Hope (Jack Johnson song) because there are many songs with the title "Hope", but we have As Tears Go By (song), not As Tears Go By (Marianne Faithfull song), although that would be more uniform. 99% of the titles will not need the state/UT, uniformity is not a reason to make the other 99% longer. --Muhandes (talk) 11:13, 2 February 2020 (UTC)

My view is that we should always keep disambiguation to a minimum and unnecessarily long names are not helpful. Having a standard disambiguator, especially as long as that proposed by Italawar is unnecessary IMO. I would propose the following disambiguation hierarchy: I don't see having slightly different titles across a range of articles as a significant issue – having unnecessarily long titles is more of an issue than a lack of uniformity IMO. Cheers, Number   5  7  13:54, 12 February 2020 (UTC)
 * 1) No other geographical area or entity with the same name: Do not disambiguate (e.g. Gwalior East as opposed to Gwalior East (Vidhan Sabha constituency))
 * 2) Geographic entity with the same name, but not a constituency: Disambiguate with "(constituency)" (e.g. Alirajpur (constituency) as opposed to Alirajpur (Vidhan Sabha constituency))
 * 3) Lok Sabha constituency with the same name: Disambiguate with "(Legislative Assembly constituency)" (e.g. Betul (Legislative Assembly constituency) as opposed to Betul (Vidhan Sabha constituency))
 * 4) Legislative Assembly constituency with the same name in another state: Disambiguate with "(state name constituency)" (e.g. Islampur (Maharashtra constituency) rather than Islampur (Maharashtra) (Vidhan Sabha constituency))
 * 5) Legislative Assembly constituency with the same name in another state and a Lok Sabha constituency with the same name: Disambiguate with "(state name Legislative Assembly constituency)" (e.g. Footown (Maharashtra Legislative Assembly constituency)).
 * I fully support your proposal as it captures my thoughts about how disambiguation should be done. However, is #4 the furthest disambiguation needs to go? Is it not possible to have a constituency which is both the same name another state and a Lok Sabha constituency? There might not be such a case, but if there is, it may require the obnoxiously long Khanapur (Telangana Legislative Assembly constituency).--Muhandes (talk) 14:18, 12 February 2020 (UTC)
 * Yes, you're correct that it probably needs a #5 just in case such a situation did exist. I've added it above. Cheers, Number   5  7  14:22, 12 February 2020 (UTC)
 * Even better. care to comment? --Muhandes (talk) 18:51, 12 February 2020 (UTC)
 * 's proposal looks quite good to me. I think we should extend it to Lok Sabha constituencies as well. Chennai South (Lok Sabha constituency) can be moved to Chennai South as per point one. I am not entirely sure about how to manage Lok Sabha constituencies with the same name in different states. Should it be Aurangabad (Maharashtra Lok Sabha constituency) or Aurangabad, Maharashtra (Lok Sabha constituency)? Because the current title gives a feeling that there is a different Lok Sabha for each state. Bharatiya  29  21:05, 12 February 2020 (UTC)
 * Although I see your point about it making it look like there is a Maharashtra Lok Sabha, I think Aurangabad (Maharashtra Lok Sabha constituency) is still slightly preferable as it avoids a double disambiguation in the same title (using a comma and brackets). Number   5  7  21:13, 12 February 2020 (UTC)
 * Number 57's proposal looks quite obnoxious and odd to me. For example:

1. Aurangabad, Maharashtra (Lok Sabha constituency) serves as a much better disambiguator than using "double brackets" Aurangabad (Maharashtra) (Lok Sabha constituency). As an alternative, you can just use the official constituency number if you don't want double disambiguation. 34-Aurangabad (Lok Sabha constituency) for Bihar and 41-Aurangabad (Lok Sabha constituency) for Maharashtra. The constituency number is the part of official name of the constituency as it can be seen in the nomination papers filed by candidates.

2. Suggesting the constituency title Alirajpur (constituency) is also incorrect as there are Legislative Council constituencies too in the some states of same name. (Not in Madhya Pradesh though but I'm using Alirajpur as a reference point here) For example: Saharanpur in U.P. has three kind of constituencies — Legislative Assembly, Legislative Council and Lok Sabha, So it's better to clarify what kind of constituency is it, Assembly or Council or Lok Sabha. Even within the Legislative Council, Saharanpur has three constituencies — Graduate's constituency, Teacher's constituency and Local Authority constituency.

3. The title Gwalior East denote a general locality or geographical area of that city. It doesn't have an article on Wikipedia as of today but in future there's a possibility that there might be an article related to this geographic area so it's better to use disambiguator instead of using just a generic title for a constituency article page.

4. It would be very inconvenient for a Wikipedia user to search for a specific constituency located in a specific state with all these non-uniform title names. For example: A person looking for Betul Assembly constituency would be expecting the same keywords for Alirajpur Assembly constituency and Gwalior East Assembly constituency to search for the articles, but all three of them having three different non-uniform titles would prove to be very inconvenient to a Wikipedia user to locate them.

— Hemant DabralTalk  02:26, 13 February 2020 (UTC)
 * Happy to have a constructive debate, but I feel your first three points are a wilful misrepresentation/misinterpretation of my suggestion; regarding #1, I did not suggest using double brackets. Regarding #2 and #3, the examples I gave were illustrations of how it would work; if the specific examples I gave do require further disambiguation, then they would move to the next level (for example, if there are other Legislative Assembly constituencies called Alirajpurr, then they would fall under #4).
 * The suggestion made to use 34-Aurangabad (Lok Sabha constituency) is worth consideration. However, I think adding the number would have to be applied to all Lok Sabha constituencies if it were adopted.
 * With regards to the final point, when editors search for a constituency, as they start typing its name in the search box, all the matches will come up. As a result, I don't see there being problems with locating articles, or that keywords are necessary in the title.  Number   5  7  11:18, 13 February 2020 (UTC)
 * I endorse all of Hemant Dabral's four points. HD clearly knows the set of articles very well, and is familiar with the degree of ambiguity involved.
 * HD's description of it reminds me of the discussions we had in relation to Ireland, where a broad stable adminsitrative geography (Ireland has had the same set of counties for ~400 years) means that their names (and those of towns and cities) have been used for constituencies of
 * The Parliament of Ireland (pre 1801)
 * The Parliament of the United Kingdom (since 1801 for Northern Ireland, and 1801–1922 for the Republic of Ireland)
 * The Parliament of Northern Ireland (1921–1972)
 * The Northern Ireland Forum (1996–1998)
 * The Northern Ireland Assembly (since 1999)
 * Dáil Éireann, since 1918
 * The European Parliament (since 1979)
 * .... and that's not even a definitive list.
 * For examples of the permutations of name, see e.g. Template:County Antrim constituencies or Template:County Cork constituencies. The Indian situation seems just as complex, and trying to impose a multi-level disambiguation hierarchy would create absurd complexity. --  Brown HairedGirl  (talk) • (contribs) 03:32, 13 February 2020 (UTC)


 * I strongly oppose 's suggestion. That creates a complex 5-level hierarchy of disambiguation, which means that editors and readers have to guess what the canonical name is, with an inevitably high rate of error.  The problem is simple:
 * every constituency is anmed after a pre-existing geographucal entity, so the bare name is always inherently ambiguous
 * the bare name such as "FooTown" or "FooTown East" may refer to any of
 * an informal geographical area
 * an administrative division
 * a state assembly constituency
 * a Lok Sabha constituency
 * With a consistent naming format, readers and editors can ascertain the name of the constituency article just by applying the convention.
 * But without it, the article's name can be determined only with extensive prior knowledge. In other words, the reader or can find the article only if they are already have info which most will need to learn from the article.  If Number 57's plan is implemented, the result will be that it is impossible to conduct a  rules-based check for the accuracy of links.  Every one of them will have to be checked by hand, and we simply don't have enough dedicated editors to sustain that level of manual checking of such huge variability across such a huge set of articles.
 * The same issues were debated at length in 2006/2007 in respect of constituencies in the UK and Ireland. Neither is a federal system, but both share the Indian characteristic have multiple types of constituency.   In each case, the consensus was to use a consistent dismabiguator in all cases, and that consensus has remained stable ever since then. Similarly, see Category:European Parliament constituencies+subcats: all articles use "Foo (European Parliament constituency)"
 * So please, disambiguate all the constituencies, at least to the level of "Foo (assembly constituency)"/"Foo (Lok Sabha constituency)", and much preferably use the always-unambiguous "XYZ (ABC Assembly constituency)" proposed by Hemant Dabral.
 * Maintainability is massively enhanced by consistency. Please please please don't undermine that maintainability. --  Brown HairedGirl  (talk) • (contribs) 02:44, 13 February 2020 (UTC)
 * PS Please note that the policy WP:NAMINGCRITERIA sets five criteria:
 * Recognizability
 * Naturalness
 * Precision
 * Conciseness
 * Consistency
 * The format "XYZ (ABC Assembly constituency)" is a clear winner on 3 criteria: Recognizability, Precision, and Consistency.
 * Number 57's provision wins only on conciseness, but fails on at least three of the other criteria.
 * Some editors seem to prioritise conciseness over all the other 4 criteria, but there is no policy reason to do so. -- Brown HairedGirl  (talk) • (contribs) 02:59, 13 February 2020 (UTC)
 * You have a point on consistency as I accepted above, but I disagree on the recognisability and precision criteria. We don't generally disambiguate where it's not necessary. I would imagine the vast, vast majority of readers would not know what the word Culpho refers to, but I doubt anyone would seriously suggest changing its name to Culpho (UK village) to make it recognisable or precise. This debate effectively boils down to a decision between consistency vs conciseness. Number   5  7  11:18, 13 February 2020 (UTC)


 * I agree with that this is primarily a consistency vs conciseness debate. But 's points are worth consideration. A lot of Lok Sabha constituency names can also refer to geographical entities. For example, Inner Manipur, Autonomous District, Paschim Champaran, etc. Terms like Gwalior East should mostly refer to the LS constituency, but that depends on one's perspective and hence we have to assume that all constituency names can also refer to the geographical location irrespective of the existence of a Wikipedia article about the same. The idea of hierarchical disambiguation is no longer practical due to legislative council constituencies. In light of all this, we have to sacrifice conciseness for practicality and consistency. I will like to propose a much simpler naming scheme:
 * All LS and legislative assembly constituencies should have "(Lok Sabha constituency)" and "(Legislative Assembly constituency)" in their title. Omitting the word "legislative" will not be appropriate IMO.
 * If two assembly constituencies in different states have the same name, the state name should be mentioned in the disambiguator: "ABC (XYZ Legislative Assembly constituency)".
 * If two LS constituencies in different states have the same name, the state name should be mentioned with a comma: "ABC, XYZ (Lok Sabha constituency)".
 * This proposal is mostly based on consistency, but also provides some conciseness by omitting the state name in most cases. As for mentioning the constituency name in the title, that would practically solve all of these issues. But it will look quite odd and will fail WP:NATURALNESS. Bharatiya  29  17:00, 13 February 2020 (UTC)
 * The use of titles like Rajinder Nagar (constituency) might lead to confusion for the reader as it can refer to either the Delhi legislative assembly constituency or the North Delhi Municipal Corporation ward. A constituency is defined as "a group of voters in a specified area who elect a representative to a legislative body", and since municipal corporations are not legislative bodies, wards are technically not constituencies. But they do satisfy the first part of the definition and that can lead to confusion. Bharatiya  29  17:20, 13 February 2020 (UTC)
 * no, this not a simple consistency vs conciseness debate. That stance is just denialism of the precision and recognisability criteria.
 * Every constituency name is derived from an existing geographical term, so it is inherently ambiguous. Every constituency name (e.f. "FooTown", "FooTown Central", "FooTown and BarTown", "South DistrictName" etc) could equally well refer to a formal or informal geographical entity. So the undisambiguated form fails the precision criterion.  Readers and editors are unlikely to know in advance whether we currently have an article on the informal area "South DistrictName", and the failure to disambiguate leaves them guessing.
 * Number47's comparison with Culpho is a red herring, because the name Culpho is not derived from an existing geographical entity. The constituency name is derivative, so it is almost never the primary topic for a geographical term, where as the village nearly always is primary (unless ambiguous with an other village of the same name).
 * Here's an example of the sort of absurdity which arises from the failure to disambiguate: Bhograi.  The article is about a constituency named after an administrative division ... but because the article on the division hasn't yet been created, the constituency is occupying the slot.
 * The undisambiguated term also fails the recognisability criterion, by failing to indicate that the article is about a primarily legal entity rather than a primarily geographical one.
 * And I'm sorry to see that Number57 pays no attention to maintainability. There are currently 4,227 articles on Indian constituencies, of which only 181 omit the word "constituency".  Number57 wants to introduce avoidable ambiguity to an unquantified number of the 4,046 articles which are already dismabiguated: why?  How does this help anyone?  Who benefits from this? Where is all the extra editorial effort going to come from to maintain this 5-level hierarchy of disambiguation? --  Brown HairedGirl  (talk) • (contribs) 23:53, 13 February 2020 (UTC)


 * There is no need to put State/UT in the title irrespective of the fact ehther the State name is mentioned or not. The legislative body of a state is called the legislative assembly for both states and partial states (Delhi, Puducherry, J&K). Bharatiya  29  19:36, 1 February 2020 (UTC)
 * I oppose for now Italawar (talk) 15:48, 15 February 2020 (UTC)


 * Keeping the name of a State/UT in titles will bring the uniformity in all of these constituency pages and at the same time it will rule out any chance of ambiguity. It'd look odd if some constituencies in a state (disambiguation pages) have the state name in titles and other constituencies don't have it. It's rather more practical to use State/UT name to achieve uniformity so we don't have to use different titles (one for disambigous pages and other for normal pages) for the various consistencies of a same State/UT. — Hemant DabralTalk  22:45, 1 February 2020 (UTC)
 * Isupport Italawar (talk) 15:48, 15 February 2020 (UTC)


 * All LS and legislative assembly constituencies should have "(Lok Sabha constituency)" and "(Legislative Assembly constituency)" in their title. Omitting the word "legislative" will not be appropriate IMO. Bharatiya  29  17:00, 13 February 2020 (UTC)
 * I support Italawar (talk) 15:48, 15 February 2020 (UTC)


 * Number 57's ...
 * I strongly oppose 's suggestion. Probably a good compromise could be to use the official name of the constituency without number. [1] [2] Italawar (talk) 05:28, 16 February 2020 (UTC)

Why the Karnataka Legislative Assembly constituencies pages were moved by Vijethnbharadwaj when the discussion about the correct title format of constituencies is still ongoing? — Hemant Dabral (📞 • ✒) 07:32, 13 July 2020 (UTC)
 * I see there is no clear outcome of this discussion. May be we should go for an RfC. What do you think? -- Ab207 (talk) 13:12, 29 July 2020 (UTC)
 * @Ab207: I agree.  An RFC is needed to clear this up.
 * But please, before launching the RFC, let's collaborate to make a neutral summary of the issues. That makes for a much better discussion at RFC. -- Brown HairedGirl  (talk) • (contribs) 13:21, 29 July 2020 (UTC)
 * Yeah, thats the ideal way to go. --Ab207 (talk) 13:59, 29 July 2020 (UTC)

Constituency names RFC drafting
(as with e.g. Category:New Zealand electorates and Category:Canadian federal electoral districts, which don't always disambiguate) (as with e.g. the various types of constituencies under Category:Parliamentary constituencies in Ireland, Category:Constituencies in the United Kingdom. Each set of constituencies for those countries has a standard disambiguator for each parliament/assembly. Category:Australian electorates uses a pair of consistent but unparethesised naming formats: "Division of Foo" for federal constituencies, "Electoral district of Foo" for state assembly constituencies)
 * There are two topics here: Should we go for consistency or conciseness? If consistency, then how?
 * Lok Sabha constituencies where there is already some consistency XYZ (Lok Sabha constituency) e.g. Chennai South (Lok Sabha constituency)
 * Legislative assembly constituencies where currently there is no consistency. Different proposals include:
 * Option 1: Disambiguation by generic name: Secunderabad (Assembly constituency) or Madurai East (state assembly constituency)
 * Option 2: Disambiguation by State/UT name: Khanapur (Telangana Legislative Assembly constituency) or Sultan Pur Majra (Delhi Assembly constituency)
 * Option 3: Disambiguation by Indian language: Bangalore South (Vidhana Sabha constituency) or Begusarai (Vidhan Sabha constituency)
 * I have tried to hit brief points, you may fill in your input--Ab207 (talk) 13:59, 29 July 2020 (UTC)
 * Thanks for that valuable start, @Ab207.
 * However, I think the the hierarchy of questions and options is little confusing. So I suggest this redraft:
 * Question 1: disambiguate selectively or always. Should constituency names in India be:
 * Option 1a) always as concise as possible, i.e. include a disambiguator only when needed?
 * Option 1b) consistent, i.e. include a standard disambiguator in all cases?
 * Note that the underlying debate here is about two ways of viewing these titles:
 * One view is that every constituency title as inherently ambiguous, because it is named after an existing geographical entity on which we may or may not have an article. Under this view "FooTown", "North FooTown", "West FooDistrict", "FooTown and BarTown" etc are all ambiguous because they describe a geographical area on which we could reasonably have an article.
 * the other view is to individually test the ambiguity of each constituency article only by whether another article already exists with that title.
 * Question 2: How should we disambiguate the Lok Sabha constituencies?. Note that:
 * this applies regardless of the answer to Q1, which decides whether we disambiguate in some cases or all cases.
 * Currently, all article on Lok Sabha constituencies are disambiguated either as "(Lok Sabha constituency)", except in five cases where that is ambiguous and the dab is ("StateName Lok Sabha constituency)".
 * Option 2a: disambiguate only as far as needed in this hierarchy: "constituency" / "Lok Sabha constituency" / "StateName Lok Sabha constituency"
 * Option 2b: (status quo) disambiguate only as far as needed in this hierarchy: "Lok Sabha constituency" / "StateName Lok Sabha constituency"
 * Question 3: How should we disambiguate the State Assembly constituencies?. Note that:
 * this applies regardless of the answer to Q1, which decides whether we disambiguate in some cases or all cases.
 * Currently, there is no consistency in the naming of State assembly constituencies
 * Options for Q3:
 * Option 3a disambiguation by generic name "Assembly constituency", e.g. Secunderabad (Assembly constituency)
 * Option 3b disambiguation by generic name "state assembly constituency", e.g. Madurai East (state assembly constituency)
 * Option 3c disambiguation by specific name "[name of state or union territory]' assembly constituency": e.g. Sultan Pur Majra (Delhi Assembly constituency)
 * Option 3d disambiguation by specific name "[name of state or union territory] Legislative Assembly constituency": e.g. Bishnupur (Manipur Legislative Assembly constituency)
 * Option 3e disambiguation by generic Indian-language name "Vidhan Sabha constituency": e.g. Bangalore South (Vidhana Sabha constituency)
 * Option 3f disambiguation by specific Indian-language name "[name of state or union territory] Vidhan Sabha constituency": e.g. Ramgarh (Jharkhand Vidhan Sabha constituency)
 * -- Brown HairedGirl  (talk) • (contribs) 19:23, 29 July 2020 (UTC)
 * , The draft looks good, there's one minor issue though. example for Option 3e is incorrect. Vidhana Sabha is Kannada-language term while generic Hindi-language term is Vidhan Sabha. There are other Indic language terms include, Sasana Sabha (Telugu), Niyamasabha (Malayalam) etc. which are not in use at this point.
 * It may also be worth mentioning that while there is no consistency for state assembly constituencies across India, there is consistency at state/UT level. "Assembly constituency" is used by Telangana and Andhra Pradesh; "state (or) Union Territory assembly constituency" by Tamil Nadu and Puducherry; "[name of state or union territory] assembly constituency" by Delhi; "Vidhana Sabha constituency" by Karnataka; "Vidhan Sabha constituency" used by several states, and so on. Hence, there is indeed an option of maintaining the status quo with consistency at State/UT level.-- Ab207 (talk) 19:58, 29 July 2020 (UTC)
 * Thanks, Ab207. How about an Option 3g for "retain existing format of consistency at State/UT level"? --  Brown HairedGirl  (talk) • (contribs) 20:06, 29 July 2020 (UTC)
 * Sounds good -- Ab207 (talk) 20:10, 29 July 2020 (UTC)
 * Pinging past participants who are currently active Do you have any inputs? -- Ab207 (talk) 05:45, 1 August 2020 (UTC)


 * Comment I don't think the state assembly options are precise enough for an RfC, as each of them gives two options. I would suggest only having one method for each option, which could potentially be:
 * Option 1: Use (state assembly constituency), e.g. Madurai East (state assembly constituency) (adding state where there are two with the same name in different states)
 * Option 2: Use (Assembly constituency), e.g. Secunderabad (Assembly constituency) (adding state where there are two with the same name in different states)
 * Option 3: Use (Vidhana Sabha constituency), e.g. Bangalore South (Vidhana Sabha constituency) (adding state where there are two with the same name in different states)
 * Option 4: Use the full name of the state assembly, e.g. Khanapur (Telangana Legislative Assembly constituency)
 * Cheers, Number   5  7  16:32, 29 July 2020 (UTC)
 * Yeah, this version is better. But I'm not sure if you have realized Vidhana Sabha (Kannada-language) and Vidhan Sabha (Hindi-language) are also different. This would open a pandora box as each Indian language has its own name e.g., Sasana Sabha (Telugu), Niyamasabha (Malayalam) etc. which are not in use at this point. -- Ab207 (talk) 17:30, 29 July 2020 (UTC)
 * We can add Indira Nagar (Union Territory Assembly constituency) in option 1 as an example for UTs. (Now there's an unaddressed issue of caps). Following options may also be added
 * Option 5 Use (State Legislative Assembly constituency), full official name, e.g. Tamenglong (State Legislative Assembly constituency)
 * Option 5.a Use ConstituencyName (StateName/UnionTerritoryaName State/Union Territory Legislative Assembly constituency), e.g. Gandhinagar (Rajasthan State Legislative Assembly constituency), Gandhi Nagar (Karnataka State Legislative Assembly constituency), Gandhi Nagar (Gujarat State Legislative Assembly constituency), Gandhi Nagar (Delhi National Capital Territory Legislative Assembly constituency) or (Delhi Union Territory Legislative Assembly constituency) etc. for assembly constituencies and Use ConstituencyName (StateName/UnionTerritoryaName State/Union Territory Lok Sabha constituency), e.g. Gandhinagar (Gujarat State Lok Sabha constituency), Gandhinagar (Jammu and Kashmir Union Territory Lok Sabha constituency) etc. for Lok Sabha constituencies.
 * Option 6 Use (Legislative Assembly constituency), concise official name, e.g. Uri (Legislative Assembly constituency) -- Ab207 (talk) 17:49, 29 July 2020 (UTC)
 * Does anyone actually advocate Foo (State Legislative Assembly constituency)? The word "state" seems redundant. -- Brown HairedGirl  (talk) • (contribs) 20:08, 29 July 2020 (UTC)
 * I think no one yet (including me). I was brainstorming all possible options. -- Ab207 (talk) 20:19, 29 July 2020 (UTC)
 * The word "state" or "union territory" may require to rename Gandhinagar (Jammu and Kashmir Assembly constituency) to Gandhinagar (Jammu and Kashmir State Legislative Assembly constituency) (Historic) and Gandhinagar (Jammu and Kashmir Union Territory Legislative Assembly constituency) (Future). 171.48.30.80 (talk) 14:18, 3 August 2020 (UTC)
 * @Ab207, fair enough. Probably best to put everything on the table at the outset. Options added later get confusing. --  Brown HairedGirl  (talk) • (contribs) 20:39, 29 July 2020 (UTC)
 * Ah, I didn't mean to write Vidhana – that was a typo... On a related note, is State Legislative Assembly (India) actually the right name for that article? Not State assembly (India)? Number   5  7  20:27, 29 July 2020 (UTC)
 * I think it uses official terminology. Alternatively it could be State Legislative Assemblies of India -- Ab207 (talk) 20:44, 29 July 2020 (UTC)
 * A user actually mass moved all the constituencies in Karnataka from Vidhan to Vidhana as recently as June. So we should be specific. -- Ab207 (talk) 20:54, 29 July 2020 (UTC)

I have a more fundamental note / question. Since this is in English and we're trying to be clear to typical readers, we should look at the common meaning / interpretation of the word "constituency":
 * 1) 98% I think that 98% of the time it means the group of supporters or group of people being represented, and so this is how the readers are going to read the word "constituency"
 * 2) 1% of the meanings are the geographic district being represented
 * 3) 1% of the meanings is that it is the assembly itself.

Keeping this in mind, IMO the above possibilities are confusing to the typical reader and/ or sometimes redundant. It appears that the "98%" meaning is not intended under any of the above. My suggestion is: Sincerely, North8000 (talk) 16:16, 7 August 2020 (UTC)
 * Don't even use the word "constituency" in the title.
 * Call a "district" simply a "district"
 * Call an "assembly" simply an "assembly"


 * Comment: The Page names should always give an idea on the content of the Page. Hence it is also necessary to retain the names as used in local terminologies. (Assembly constituency) was the early used suffix for Legislative Assembly Constituency Pages (Example: Ayodhya (Assembly constituency)). There were other forms of usage as well (mentioned and listed by many, above). The use of Indic terminology started with using (Vidhan Sabha constituency) as a suffix (Example: Chhindwara (Vidhan Sabha constituency)). So if more usage is considered, what we call popular usage or most Commonly used name in Wikipedia, (Vidhana Sabha constituency) suffix gets justified (Example: Bangalore South (Vidhana Sabha constituency). So, if title Vidhan Sabha Constituency stands valid, Vidhana can also co-exist.... If consistency is the key, I would suggest using (Assembly constituency) as suffix for all pages across India without mentioning State name or the word State / Union Territory or even mentioning the words Legislative, since these characters makes the title lengthy. However, in case of disambiguation, we should use state name in the title. (Example: Shivajinagar (Maharashtra Assembly constituency) and Shivajinagar (Karnataka Assembly constituency) Since we have multiple seats in different states with same name. Whereas, Lucknow East (Assembly constituency) page title can continue without modification since no page exist with the given name else where in India. Vijeth N Bharadwaj 18:57, 24 August 2020 (UTC)
 * I agree with "The Page names should always give an idea on the content of the Page." IMHO, for the majority of English readers, using "constituency" would violate that concept. North8000 (talk) 19:45, 24 August 2020 (UTC)

===Discussion at Wikipedia talk:WikiProject Indian politics § Proposal : Wikipedia:Naming conventions Indian constituencies=== You are invited to join the discussion at Wikipedia talk:WikiProject Indian politics § Proposal : Wikipedia:Naming conventions Indian constituencies. Venkat TL (talk) 12:54, 27 March 2022 (UTC)

Cleanup Indic script
FYI has been nominated for deletion -- 65.92.246.142 (talk) 06:54, 28 March 2022 (UTC)

Solution to the Indic script debate
Obviously I think banning all Indic scripts in the lead section of India-related articles is not a very good solution, so I came up with another: using a template like Template:Infobox Chinese to list the names of places in Indian languages. I have therefore created Template:Infobox Indian. It's currently a work-in-progress and please feel free to (and please do) help me fix it. I have used it on the page Indian Australians as an example. Thanks! Thiscouldbeauser (talk) 07:55, 17 November 2022 (UTC)

Why just not use indonesia alone?
Where is the indonesia related articles for applying the manual of style in editing pages? 2404:8000:1027:85F6:4D2C:4F6E:D2A6:F16F (talk) 15:36, 25 March 2023 (UTC)

Revisiting exceptions to INDICSCRIPT: proper titles of creative works?
Would there be any appetite for an RfC to codify an exception to INDICSCRIPT for proper titles of published works in those languages (film, books, etc.) in articles? It seems like it should be relatively straightforward to determine/enforce. It doesn't appear to have been considered in the close for the original discussion, and I'm not aware of further revision discussions. The current implementation of INDICSCRIPT makes it very difficult to search for non-English sources. I note that FA-class Pather Panchali does include its Bengali name, although my impression is that for better or for worse, most articles about published works diligently toe the INDICSCRIPT line. signed,Rosguill talk 22:59, 4 June 2023 (UTC)


 * While craving an exception from WP:INDICSCRIPTS for some literary works and films, will be relatively straightforward, that won't be the case in general. For example, prior to adoption of this guideline, there have been numerous wiki-battles about whether classic Bollywood films and songs are in Hindi/Urdu/Hindustani and which script(s) should be included and in what order. And several high-profile South Indian films nowadays are simultaneously filmed in multiple languages, which makes determining their "actual" language(s) a target for wiki-fights too. Even the language of Indian national anthem has been subject to on and off-wiki-dispute. So while I personally support inclusion of পথের পাঁচালী at Pather Panchali and tacitly follow the practice of not removing Indic-scripts from articles about written literary works whose language/script is not subject of any dispute, don't expect formulating or enforcing a general exception to be easy! Abecedare (talk) 17:19, 5 June 2023 (UTC)
 * I know it's common for films in India to be produced in multiple languages but am less familiar with how many languages are a common upper limit for simultaneous filming. If it's less than say, 5, I think it should be straightforward enough to include all of the languages of production. If films are commonly produced in more than 5 languages at once it becomes truly unwieldy. I think we could come up with a similar workaround for Hindi vs. Urdu or other languages (e.g. do not include Hindi or Urdu if at all ambiguous) that are similarly paired. signed,Rosguill talk 17:23, 5 June 2023 (UTC)
 * Alright, absent anyone jumping out of the woodwork to identify major problems with this idea, I'm going to start an RfC shortly. signed,Rosguill talk 04:36, 12 June 2023 (UTC)

INDICSCRIPT RfC
Should we add the following exception to MOS:INDICSCRIPT (changes highlighted in bold)?

Exceptions are articles on the script itself, articles on a language that uses the script, articles on creative works originally produced in Indic languages. This exception does not apply to dubs or translations of original works, but does apply to works produced and released in multiple languages simultaneously (e.g. Radhe Shyam). For works whose spoken language is ambiguous (i.e. languages in the Hindustani continuum), defer to the spelling/language(s) provided in the earliest publication of the work itself.

Note that the status quo text already provides for exceptions for articles on texts originally written in a particular script.; the proposed change would expand this exception to include films, music, video games, and other creative works with specific, identifiable languages of production; text in the guideline related to written works was changed purely for copyediting purposes. signed,Rosguill talk 15:33, 12 June 2023 (UTC)

Discussion

 * Support As I noted in the above discussion, the current implementation of MOS:INDICSCRIPT makes it very difficult to search for non-English sources for these topics, and there already appears to be a tacit lack of application of INDICSCRIPT's restrictions in high-quality film articles such as Pather Panchali. In prior discussions of INDICSCRIPT, suggestions to include carveouts for films and other creative works were suggested but not discussed in depth, and ultimately not included as part of the consensus results (despite not receiving direct opposition). I think that the nature of a creative work's original language of production is such that this exception would cause little additional disruption, and could provide significant benefit to both to readers in itself, and to editors searching for more sources to expand or establish the notability of articles. While multilingual productions are relatively common, the list of original languages of production rarely goes higher than a handful and should not present a significant obstacle. I am also open to further workshopping of how to handle Hindustani languages or other areas of potential confusion that I have not been able to anticipate. signed,Rosguill talk 15:33, 12 June 2023 (UTC)
 * Support That seems perfectly reasonable. I have pondered and can't think of any downsides - but if anyone has cogent arguments against......now is the time. Lukewarmbeer (talk) 16:35, 12 June 2023 (UTC)
 * BTW It seems premature to have an RfC now but as this is a dark corner of WP I understand why you have. Lukewarmbeer (talk) 16:37, 12 June 2023 (UTC)
 * I initiated a discussion a week ago to test the waters and attempt to do an RFCBEFORE, and got a limited response. Given that this is a very wide-ranging guideline, an RfC seems more appropriate to me than boldly making the change--even if I took the perspective that this change was totally uncontroversial, the lack of publicity associated with a bold change would mean that we'd end up with confusion and inconsistent application of the guideline. (As a side note, I think you could even wikilawyer a case that the original RfC from a decade ago should have been closed with the inclusion of carveouts for creative works, as it was raised in that discussion as a reasonable exception by editors primarily arguing for wholesale removal--but I'd rather get community buy-in and a new consensus than legalistically challenging a decade-old, widely-applied decision). signed,Rosguill talk 16:41, 12 June 2023 (UTC)
 * Oppose The guideline has stood for a long time and for a good reason; the language battles are too frequent (Hindi-Urdu-Bengali, Tamil-Sanskrit-Devanagri etc.) and the script clutter too high whether it be for any topic including the arts, creating very specific exceptions while leaving other topics out will not work. Similar proposals were there in the RfCs back then (e.g. of allowing only local official languages on geographic articles) which were rightly shut down as they had not worked in the past as well. There are already not enough users to enforce the existing guideline (e.g. the Pather Panchali script you cite was only [incorrectly] added about a week ago) and creating further loophopes will deter anyone from further enforcing them (you can also expect a rollover effect where drive by editors will be adding scripts all over place [scripts in popular film etc. articles only serving to encourage them]). The guideline is already limited to India-specific topics and articles, the result being that you find the same script clutter for which this guideline was created playing out in broader topics (e.g. interboundary rivers, religious topics etc. where they have lead to the same language wars and in cases their removal entirely), we do not need to further weaken the guideline by creating a large exception that too for the most popular topic area. And "articles on texts originally written in a particular script" was incorporated for religious/older texts in a language not covering popular culture areas of literature et al.
 * As for the comment about scripts being needed for non-English sources, that is easily resolvable by going to the apt language wiki for the same or Wikidata itself.
 * I have consistently and strugglingly enforced the previous guideline for years now and will be heavily discouraged to enforce a guideline if such a gaping hole is brought forth. Gotitbro (talk) 20:11, 12 June 2023 (UTC)
 * The Wikidata method you suggest is not really workable, as typically new articles are not already linked on there, if an article even exists on the relevant projects. I'm a little confused by the logical jump from "this is already near-impossible to enforce" to "another exception will make it harder to enforce". If anything, our ability to enforce the current wording is undermined by the absence of these common-sense adjustments that people unfamiliar with our guidelines are going to continually make in perpetuity. I am also skeptical that names of Indian topics is really so much more of an intractable problem than anything else we face on Wikipedia, or that CTOP remedies are not sufficient for addressing disruption related to the region (case in point: we don't appear to need similar provisions for Pakistan topics, despite the presence of multiple sizable minority languages that use both Persian and Devanagari scripts, and plenty of ethno-politico-linguistc tensions both within the country and in relation to its neighbors). I can understand the wisdom of the guideline for matters such as people's personal names or the names of geographic locations, where the correct spelling/language is genuinely ambiguous much of the time, but the same is simply not true for creative works that have an unambiguous language of production. signed,Rosguill talk 20:29, 12 June 2023 (UTC)
 * Google Translate would be your friend then, also finding sources for Indian films etc. topics has never been an issue as most of them are in English. The script sclutter has always been an intractable problem, the reason this guideline exists in the first place. And the reasoning is perfectly justifiable, language warriors always pop-up now and then and no-one is willing to put in the work to cleanup after they are done. Those who do (such as ) know how laborious it is and would not really be impressed by this proposal. Gotitbro (talk) 20:41, 12 June 2023 (UTC)
 * I'd appreciate Fylindfotberserk's opinion, but am still mystified by the logical gap in your argument as to what creates more work for us to do. I'm no stranger to article cleanup, or dealing with intractable nationalist editors across a variety of regions (including naming disputes in particular) and can't say that your comments speak to my experience in this field of editing at all. signed,Rosguill talk 20:47, 12 June 2023 (UTC)
 * The case of Pakistan is also not really applicable to India, Devanagari is not used in Pakistan at all Perso-Arabic is the standard (the language writing in Devanagari, i.e. Sindhi, Kashmiri, Punjabi (Gurmukhi) is not done in Pakistan but on the Indian side where these language are also spoken) and Urdu is universal. And unlike the multiple-language cinema of India, the cinema in Pakistan is also mostly in Urdu (Punjabi, Sindhi, Pashto cinemas existed but are mostly extinct nowadays and anyhow they all use the same script). Gotitbro (talk) 20:53, 12 June 2023 (UTC)
 * Is that true of Pakistan-administered Kashmir as well? At any rate, while there may not be a single country that perfectly lines up to India's particularities, I'm still left a little skeptical that there's something inherently more problematic about linguistic rivalry in India as compared to Kurdish regions, the Caucasus, or Israel/Palestine, to name a few linguistically contentious regions. signed,Rosguill talk 20:58, 12 June 2023 (UTC)
 * Yes, and Kashmiri is barely spoken in the Pakistani-administered region in any case. The fact that the other mentioned regions don't have a similar policy would be a testament to that, the maximum scripts in any of them would at most be three (Cyrillic/Perso-Arabic/Latin), simply not the case with India. Gotitbro (talk) 21:10, 12 June 2023 (UTC)
 * Friend, you vastly underestimate the diversity of language in the Caucasus and Syria. Kurdish-adjacent conflicts can involve Kurmanji (written in Latin or Arabic), Arabic, Syriac (written in Aramaic, which looks a lot like but is distinct from Arabic) or Turkish (Latin-derived, but with a different character set than Kurmanji that intentionally excludes letters important for Kurmanji), Circassian (which can use Arabic, Cyrillic-derived, or Latin scripts) and Armenian, among other smaller minority languages. The Caucasus meanwhile, is home to about 30 different languages across seven entirely distinct families of languages, using (often heavily expanded, unique) variations of Cyrillic, Latin, Georgian, Armenian and Arabic scripts signed,Rosguill talk 21:24, 12 June 2023 (UTC)
 * I was talking from the perspective of single country applicability. I doubt all of the languages mentioned above would be applicable to a single article. In an Indian film article say for a film simultaneously filmed in three languages (Tamil, Telugu, Hindi) and released in dubs (such as Malayalam, Kannada, Punjabi, Bhojpuri, Marathi, Bengali, Odia) the avenues for shenanigans become significantly higher. Gotitbro (talk) 21:38, 12 June 2023 (UTC)
 * Turkish-Arabic-Kurmanji edit wars, with the occasional addition of Syriac, Circassian or Armenian for relevant villages, are frequent for northern Syrian topics; linguistic disputes in southern Russia and Georgia can easily include upwards of four languages, although you would be correct that Azerbaijan-Armenia disputes tend to be mercifully simple in their linguistic dimension. signed,Rosguill talk 21:46, 12 June 2023 (UTC)


 * Oppose Gotibro has expressed my misgivings with this very well. The bottom line is that our INDICSCRIPTS policy has put an end to the plague of script wars and I would much prefer to keep it that way. Additionally, carving out an exception for film articles is unnecessary since, almost always, a serviceable transliteration into English for a film title already exists. I don't see much point in including a polyglot set of non-Latin scripts (e.g., the Telegu and Hindi for Radhe Shyam - OP's example above) when a perfectly acceptable transliteration already exists (e.g., the poster image in that article). What purpose does it serve the English language reader of Wikipedia to see the Telegu, Tamil, Malayalam, Kannada, and Devnagri scripts for RRR (film) stuck in the infobox or the lead sentence of the article, interrupting the textual flow? RegentsPark (comment) 20:46, 12 June 2023 (UTC)
 * Maybe I'm missing something but it looks like RRR (film) was only produced in Telugu? Where would consideration of other scripts come in? signed,Rosguill talk 20:48, 12 June 2023 (UTC)
 * It was dubbed in the other languages. --RegentsPark (comment) 20:52, 12 June 2023 (UTC)
 * The current proposal is to explicitly only include primary languages of production and to exclude dubs. signed,Rosguill talk 20:53, 12 June 2023 (UTC)
 * Ah. The exception to the exception! I think you're getting stuck on trees and are missing seeing the forest. When you build an exception, we're going to see endless discussions on where the exception applies and where it doesn't. For example, if the dubbed Malayalam verion was advertised in Malayalam, does that mean we should include the Malayalam script as well? Since it does exist. Regardless, I'm not seeing any purpose in including any indic script for Indian films when they are also heavily advertised in using English. Or, to put it another way, if we think indic scripts are useful for films, why exclude other areas and not just toss the whole policy out? RegentsPark (comment) 21:13, 12 June 2023 (UTC)
 * It's not an exception to the exception, it's a boundary, no more unenforceable than delimiting it to the country of India, or providing an exception for textual works but not films. My reasoning for the proposed scope is that I believe that the parameters are unambiguous (for the Malayalam-dub-and-ad example the answer would be "no"), that the titles are of some use to readers and editors (if not necessarily every reader and editor) and that the genuine confusion at the root of guessing the correct spelling/language the names of Indian people and places (or the languages notable enough to merit listing) is not present for creative works that typically have objectively-verifiable primary languages. signed,Rosguill talk 21:30, 12 June 2023 (UTC)
 * Also, has it put an end to the plague of naming disputes or not? Gotitbro above implies that such disputes and enforcing the existing guideline are a constant battle, hardly something resolved by the guideline. signed,Rosguill talk 20:54, 12 June 2023 (UTC)
 * That was put an outlay of how these problems will be exacerbated not a rebuke of the guidelines as a whole. Atleast with the current guideline you don't have multiple users vying for a place for their language when all can be removed in single swoop without the need of debating on what original language script needs to be there. The latter gets tricky as films in India a lot of times carry mutiple strands of lects, take Nadiya Ke Paar (1982 film) for example and see a back and forth of language wars, with scripts its all the more tiring. Gotitbro (talk) 21:04, 12 June 2023 (UTC)
 * I would imagine that any conflict that would occur would be identical to the existing conflict or lack thereof over the listing of Hindi, Bhojpuri and Awadhi in English in the infobox. signed,Rosguill talk 21:10, 12 June 2023 (UTC)
 * Ib conflicts much easier to handle, but if you give prominence to one script in the lead there most definitely would be a significantly higher increase in drive-by script inserters (speaking with experience). Gotitbro (talk) 21:14, 12 June 2023 (UTC)


 * Oppose I may have been here too long, but I well remember the chaos before WP:NOINDICSCRIPT was first introduced in 2012, and then the repeated need to tighten it up over the next 5 years, as people kept trying to find/force loopholes in it. I find it difficult to explain how bad this was to any editors who did not experience it. This proposal seems a very retrograde step to a system that is currently working reasonably well, partially because of its simplicity. If the average reader, sees Indic script in one article, they will assume this is acceptable, and add it to others, without reading any guidelines, thus creating far more work for us WikiGnomes who clear the mess up. The suggested "benefits" of the proposal seem insignificant compared to the drawbacks. Indian films are a battleground as it is, including arguments over releases in multiple languages and dubs, we don't need more chaos and language-warring. - Arjayay (talk) 21:19, 12 June 2023 (UTC)
 * Comment I see a lot of oppositions based on script fighting but I think I have a potential solution. What if we create a collapsible template which has fields for a variety of Indic scripts (ordered alphabetically to be as neutral as possible)? It can be implemented on Indic script allowed pages and users can populate the fields with the Indic script they want to include (perhaps we have start off with all the officially recognized scripts of India as default fields and expand as needed). Since it would be collapsible (with its default state being closed and not expanded until users click “show”), it wouldn’t hug too much space in the article and it’ll keep Indic scripts out of the text of the article, where I assume most of the script fighting occurs. It can be titled “Template:Infobox Indic scripts” or something along those lines. I have no idea if an idea like this has been suggested in the past. What do you all think? ThethPunjabi (talk) 21:57, 12 June 2023 (UTC)
 * Would not really serve any purpose for disparate language really. Pages where Indic scripts are allowed either do not really suffer language wars or are better off without any scripts. The issue is not the relegation of scripts but their removal, even if you include all official languages in such a template, users will still find a way for disruption. All manner of solutions for not removing scripts entirely were proposed in varied ways in the RfC for the guideline, they were not implemented for good reason. Gotitbro (talk) 22:12, 12 June 2023 (UTC)
 * Having read through the prior discussions, while "lack of consensus" is in a sense a good reason to not implement something, I think it's an overstatement to imply that all alternatives were decisively rejected. The original discussion was closed as There is ultimately no consensus about which language to use... defaulting to the encouragement of IPA by the closer as an attempt to resolve the impasse. The various discussions listed in the guideline itself since then are a rather confusing list of primarily one-off challenges by an editor unsatisfied with the status quo and which led to minimal further discussion, and a much more relevant 2017 discussion to expand the lead-ban to an infobox-ban. I'm not aware of any past discussion that has really taken up the question of exceptions to the rule. signed,Rosguill talk 22:32, 12 June 2023 (UTC)
 * Yes, I had gone through each one of them thoroughly before I set off in implementation of the guideline on enwiki. The 2017 discussion's conclusion was pretty conclusive in not wanting any scripts in any manner whatsoever in India-specific articles. Localized solutions did not work, Infobox solutions did not work, expansion of exceptional areas was not done and templates are not going to work - keeping in line with the spirit that this guidelines set was put forth for, that of reduction and elimination of script clutter. Gotitbro (talk) 23:03, 12 June 2023 (UTC)


 * Oppose: Yes it is problematic for the very reasons discussed in the previous RfC and here. Another thing, I don't know people have noticed it or not, it is even problematic in articles that are exempt from the policy, e.g. language and religion-related ones that are relevant for more than one script. Bhojpuri language is one such article, that has faced POV additions and rearrangements of scripts. Durga is another one I used to patrol before, see these versions, this one with two scripts, only Devanagri, and the current version with a list of scripts in the infobox. - Fylindfotberserk (talk) 09:40, 13 June 2023 (UTC)
 * I feel Indic scripts should be in the infobox under the param "infobox name module". When Chinese and Japanese scripts are allowed, why disallow Indic ones? Kailash29792 (talk)  09:47, 13 June 2023 (UTC)
 * Oppose I won't repeat the oppose reasons already stated above, which I agree with, but emphasize that it is not trivial to determine the language of Indic creative works or assign a script, even if a a language is determined. With regards to the former, consider, List of multilingual Indian films; Carnatic and Hindustani classical music; all Hindi/Urdu/Hindustani films, plays and songs, etc. For the latter, consider works in Hindustani, Konkani, Kokborok etc. While referring to the "earliest publication of the work itself" as prescribed by the proposed amendment may work for written literature, i don't see how that is supposed to help with oral, visual and performance arts. The ambiguity and complexity is best handled in the article body with appropriate sources rather than by adding clutter in the lede sentence, which more than a decade of experience has shown becomes a focal point for linguistic warriors to express their pride and mark ownership over the article's subject. Abecedare (talk) 16:38, 13 June 2023 (UTC)
 * Oppose for the reasons noted above. Enough discussions that got extremely contentious, too much drama and not enough return.  Ravensfire  (talk) 14:54, 14 June 2023 (UTC)

Rupee formatting
I've noticed that most articles mentioning the Indian rupee appear to use the old Rs[.] symbol or the lakh crore system, rather than the new (as of 2010) ₹ symbol. Is there a standard around which symbol to use, and should instances of "Rs" when referring to the Indian rupee be changed to the new symbol? Exobiotic 💬 ✒️ 13:29, 8 June 2023 (UTC)


 * @Exobiotic You can use Template:INR and Template:INRConvert — DaxServer (t · m · e · c) 15:18, 8 June 2023 (UTC)

MOS:INDICSCRIPT
Can someone provide an update for the MOS:INDICSCRIPT? Is the guideline still applicable or are there any exceptions to the guideline, especially in Wikiproject Hinduism? I'm seeing multiple articles with notes suggesting so. Thanks. The Herald (Benison) (talk) 16:36, 8 October 2023 (UTC)
 * What multiple articles with what notes suggesting "so" what?  — SMcCandlish ☏ ¢ 😼  20:17, 8 October 2023 (UTC)
 * Ashwatthama is one such article with a nowiki note. Is there such a guideline proposed and accepted? Thanks. The Herald (Benison) (talk) 20:40, 8 October 2023 (UTC)
 * What is a "nonwiki note"? Note about what, where on the page, saying what? Please try to be clearer about what issue you are raising and what you expect to be done about it. No one here is a mind-reader.  — SMcCandlish ☏ ¢ 😼  22:34, 8 October 2023 (UTC)
 * Hidden note on the lead about the MOS:INDICSCRIPT is what I'm talking about. Sorry for the confusion. The Herald (Benison) (talk) 02:34, 9 October 2023 (UTC)
 * I see an HTML comment there that reads   That's a nonsensical statement, since there is no such thing as a wikiproject that is magically immune to guidelines and policies applying to it.  This may be a mangled attempt at referring to some consensus discussion that came to a conclusion that certain Indic script renditions might be particularly relevant at certain topical articles, but we'll need to see what that discussion might be, if there has actually been one.  — SMcCandlish ☏ ¢ 😼  19:45, 9 October 2023 (UTC)
 * Yes, the same. I've been searching all the pages on MOS for something of the sort, but couldn't find any such guideline. Thanks.