Wikipedia:Requests for comment/Wikipedia style and naming

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)

Potential options:

1. Yes, articles on subnational entities and municipalities in the title should have "none as a short description"
2. Only for cities and subnational entities that an "average reader would know" (which I have seen brought up in the past) should have "none" as a short description (most readers know about Delhi, Texas, and Moscow, not so much Kilgore, Texas, and Ncojane) (This has been brought up in the past by Remsense)
3. No, none of these apply for WP:SDNONE (a format will have to be provided for what should be recommended in the new guideline)

Thanks! -1ctinus📝🗨 22:06, 15 November 2024 (UTC)

RFCBefore Selfstudier (talk) 18:18, 13 November 2024 (UTC)

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.

• A: No sticky header, same style (2-line) header as before.
• B: Full size (2-line) header with sticky enabled.
• C: Narrow (1-line) header without sticky enabled.
• D: Narrow header with sticky header that follows you around.
• E: Same as D, but with padding at the top of each row.

Graywalls (talk) 15:04, 30 October 2024 (UTC)