Wikipedia:Requests for comment/Wikipedia style and naming
The following discussions are requested to have community-wide attention:
| Should the Infobox include Arabic with the ethnic languages, or follow examples like Assyrian people and Copts that exclude it? TahaKahi (talk) 22:12, 19 November 2024 (UTC) |
| For any proposed article title determined by the application of WP:CRITERIA the proposed title should nonetheless comply with WP:TITLEFORMAT (ie WP:TITLEFORMAT has primacy over WP:CRITERIA). Cinderella157 (talk) 00:03, 18 November 2024 (UTC) |
Wikipedia talk:Manual of Style/Dates and numbers
| I am revisiting an issue that was last brought up 6 years ago here and settled without a strong consensus.
I think we should avoid using Indian numbering conventions unless it is needed for context. For instance, if we want to list the box office take of an Indian movie, don't use "crore", use "millions". This isn't about disrespecting a culture, it's about using internationally favored notation and unit conventions. We should use "millions" instead of "crore" for the same reason we favor meters over feet. There is no reason that India-related articles should be an enclave of Indian conventions. People who are not Indian will struggle with these things, it will weaken Wikipedia's role as an information tool for everyone. This is not the same thing as currency. It is appropriate to list an Indian movie's box office take in rupees. Providing a US$ conversion is optional, but a good idea since the US dollar is widely used around the world as a reserve currency. But write it as "millions of rupees", not "crores of rupees". Kurzon (talk) 16:38, 16 November 2024 (UTC) |
Wikipedia talk:Short description
| I have asked this question multiple times and have received no complete consensus to change WP:SDNONE to apply article names such as History of Nottinghamshire and Watersheds of Illinois. When this is resolved, please update WP:SDNONE to comply with this ruling. This RfC is necessary since there are thousands of articles where this applies where there is no consensus for use of WP:SDNONE. Additionally, the guideline is extremely short and vague for something that applies to hundreds of thousands of articles.
Potential options:
|
Wikipedia talk:Requests for comment
| Should the words "or ~~~~~ (just the time and date)" be removed from statement 5 of Wikipedia:Requests for comment#Creating an RfC? |
Wikipedia talk:Manual of Style/Images
| Should MOS:LEADIMAGE include a subsection for selecting lead images in biographical articles (if there is more than one image of the subject)? ―Howard • 🌽33 18:15, 10 November 2024 (UTC) |
Wikipedia talk:Reliable sources/Perennial sources
| There has been an initiative to change the interface so that the gray header at the top of the table "follows around" as you scroll down. See: {{sticky header}}. Which of the choices below (A-E) do you prefer? What other ideas do you have?
The header is now 2 lines tall. What Timeshifter is now proposing (scroll down this example) is a narrow one-line sticky header with a link from the "Status" column head back to the "Legend" section of the article. And a link from the "Sources" column head back to the "Sources" section of the article. Notes explain this just above the table. He states this allows new users of the table to quickly return to the table TOC, or to quickly find the meaning of the legend icons. An issue in any skin other than the default Vector 2022: When you use the horizontal table TOC, or if you follow ("jump to") an anchored link within the table such as WP:FORBESCON, the top line of the note in the row you jump to would be covered by the narrow sticky header. 2 lines are covered by the 2-line header. Template discussions have not found a way to fix this. Timeshifter does not believe this is a serious problem. Others do. One solution (see E below) is to add a line's worth of blank padding at the top of each row. |