Jump to content

Talk:Main Page

Page contents not supported in other languages.
Page semi-protected
From Wikipedia, the free encyclopedia
(Redirected from Wikipedia talk:Main Page/4)
Archives: Sections of this page older than three days are automatically relocated to the newest archive.

001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207

Main Page error reports

To report an error in content currently or imminently on the Main Page, use the appropriate section below.

  • Where is the error? An exact quotation of the text in question helps.
  • Offer a correction if possible.
  • References are helpful, especially when reporting an obscure factual or grammatical error.
  • Time zones. The Main Page runs on Coordinated Universal Time (UTC, currently 05:07 on 5 December 2024) and is not adjusted to your local time zone.
  • Can you resolve the problem yourself? If the error lies primarily in the content of an article linked from the Main Page, fix the problem there before reporting it here. Text on the Main Page generally defers to the articles with bolded links. Upcoming content on the Main Page is usually only protected from editing beginning 24 hours before its scheduled appearance. Before that period, you can be bold and fix any issues yourself.
  • Do not use {{edit fully-protected}} on this page, which will not get a faster response. It is unnecessary, because this page is not protected, and causes display problems. (See the bottom of this revision for an example.)
  • No chit-chat. Lengthy discussions should be moved to a suitable location elsewhere, such as the talk page of the relevant article or project.
  • Respect other editors. Another user wrote the text you want changed, or reported an issue they see in something you wrote. Everyone's goal should be producing the best Main Page possible. The compressed time frame of the Main Page means sometimes action must be taken before there has been time for everyone to comment. Be civil to fellow users.
  • Reports are removed when resolved. Once an error has been addressed or determined not to be an error, or the item has been rotated off the Main Page, the report will be removed from this page. Check the revision history for a record of any discussion or action taken; no archives are kept.

Errors in the summary of the featured article

Please do not remove this invisible timestamp. See WT:ERRORS and WP:SUBSCRIBE. - Dank (push to talk) 01:24, 29 September 2022 (UTC)[reply]
  • "In 2019, the researchers named the new genus and species Mimodactylus libanensis; referring to the MIM Museum, with the Greek word daktylos for 'digit', and the specific name refers to Lebanon." This is grammatically incorrect, as the text following the semicolon is not a complete sentence. I would recommend: "In 2019, the researchers named the new genus and species Mimodactylus libanensis, a reference to the MIM Museum combined with the Greek word daktylos for 'digit'; the specific name refers to Lebanon."

The text begins with "The École Polytechnique massacre". If you mouse over that link without clicking, either here or in the article, it says "French-language text". That is wrong. Mousing over normally tells you what article you will get if you click. But clicking the link doesn't give you an article about French-language text, nor does it give you an article written in French.

In edit mode, you'll see this is caused by template:lang, which is used 3 times. According to template:lang#Links, the lang template isn't even working when it's inside a wikilink like that, so you wouldn't lose anything by removing the lang links. The fix suggested at Template:Lang#Links doesn't seem to apply because the examples are entire links in another language, but here the word "massacre" is English. So unless someone has a better idea, I could just remove the lang templates that aren't working anyway. Art LaPella (talk) 07:03, 30 November 2024 (UTC)[reply]

Or yuo could not. @Art LaPella:, please do not change featured content unilaterally. Paging relevant parties: @FAC coordinators: and @TFA coordinators . SerialNumber54129 10:00, 30 November 2024 (UTC)[reply]
Just so everyone knows, I have often made minor unilateral changes to featured articles and blurbs without objection. Even when I ask for attention, I don't always get it. In this case I asked, and I'm happy to leave this issue for others. Art LaPella (talk) 18:40, 30 November 2024 (UTC)[reply]
  • I've changed from '''[[École Polytechnique massacre|{{Lang|fr|École Polytechnique|italic=no}} massacre]]''' to '''{{Lang|fr|[[École Polytechnique massacre]]|italic=no}}''' (thus École Polytechnique massacre to École Polytechnique massacre) which gets rid of the problem. This is possibly temporarily unless someone finds a better way; as "massacre" is a cognate from the French this isn't problematic, per se. - SchroCat (talk) 10:25, 30 November 2024 (UTC)[reply]
    This is a browser problem, not a content one, and that change has introduced an error. "massacre" should not be treated as a French word because, in this instance, it's English. The target article's lead has '''{{Lang|fr|École Polytechnique|italic=no}} massacre''' which, being syntactically and grammatically correct, should be used here: École Polytechnique massacre. Bazza 7 (talk) 10:52, 30 November 2024 (UTC)[reply]
    Read the opening comment and come up with something that doesn't cause the problems that began the thread. - SchroCat (talk) 11:14, 30 November 2024 (UTC)[reply]
    @SchroCat: I did read the comment, and have pointed out already that this is a problem with the reader's browser, not the content. The content generates
    <a href="/wiki/%C3%89cole_Polytechnique_massacre" title="École Polytechnique massacre"><span title="French-language text"><span lang="fr" style="font-style: normal;">École Polytechnique</span></span> massacre</a>
    The browser uses any inner-most "title" attribute to generate a tooltip; so for hovering over École Polytechnique that will be French-language text, and for hovering over massacre it will be École Polytechnique massacre.
    The tooltip functionality is not a part of the code generated. We must not be led into generating inaccurate content purely to overcome the behaviour of certain browsers.
    The simplest solution to satisfy this non-error is to remove the language tag from around the establishment's shortened name which was also its shortened name in Canadian English at the time of the event; so: '''[[École Polytechnique massacre]]''' giving École Polytechnique massacre. Bazza 7 (talk) 14:17, 30 November 2024 (UTC)[reply]
    This is not a “browser problem”. The WHATWG specification of the title attribute says that “The title attribute represents advisory information for the element, such as would be appropriate for a tooltip” and defines an order of precedence for advisory information such that any higher-level elements are ignored. If “French-language text” is not the most relevant advisory information for the text, it should not be in the title attribute. 216.147.127.204 (talk) 03:10, 1 December 2024 (UTC)[reply]
Art LaPella, that is Friday's (6 Dec) TFA not Wednesday's? JennyOz (talk) 13:21, 30 November 2024 (UTC)[reply]
Yes which is the correct date. Secretlondon (talk) 13:31, 30 November 2024 (UTC)[reply]
Friday 6 December. - SchroCat (talk) 14:16, 30 November 2024 (UTC)[reply]
Bazza_7 is correct about this being a browser issue. What should probably be done is to modify the template concerned so that it is possible to supress the title attribute, by writing, say, ''[[École Polytechnique massacre|{{Lang|fr|École Polytechnique|italic=no|title=no}} massacre]]''; or possibly better still by simply removing the title attribute completely. I have raised this on the template's talk page; see Template talk:Lang#Issue with use in links. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:27, 30 November 2024 (UTC)[reply]
Also noting that this is not an issue for users of the WP:Navigation popups tool, so the fix might be better done in whatever (Wikipedia) tool is failing to show the article preview popup. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:33, 30 November 2024 (UTC)[reply]
Your suggestion of ''[[École Polytechnique massacre|{{Lang|fr|École Polytechnique|italic=no|title=no}} massacre]]'' shows as the following error message for me:
[[École Polytechnique massacre|[École Polytechnique] Error: {{Lang}}: invalid parameter: |title= (help) massacre]]
(for those who few for who this renders properly, lucky you, but the rest of us are seeing the multi-coloured ''[[École Polytechnique massacre|[École Polytechnique] Error: {{Lang}}: invalid parameter: |title= (help) massacre]]'')
The template guidance specifically says not to use this format because it doesn't work on talk and some other pages (as seen above); it's not something you want to try out on TFA blurb on the main page. - SchroCat (talk) 09:08, 1 December 2024 (UTC)[reply]
@SchroCat: I suggested earlier that the language tag may not be needed for this establishment name, so a simple '''[[École Polytechnique massacre]]''', giving École Polytechnique massacre will do. Bazza 7 (talk) 13:32, 1 December 2024 (UTC)[reply]
I don't know who wrote the 'advice' at Template:Lang § Links but it is not very correct. This link:
[[École Polytechnique massacre|{{Lang|fr|École Polytechnique|italic=no}} massacre]]
works here in the Wikipedia namespace because {{lang}} does not categorize outside of mainspace. As written, the link will not work on main page because in mainspace, {{lang}} categorizes:
[[École Polytechnique massacre|<span title="French-language text"><span lang="fr" style="font-style: normal;">École Polytechnique</span></span>[[Category:Articles containing French-language text]] massacre]]
[[École Polytechnique massacre|École Polytechnique massacre]]
This is why {{lang}} has |nocat=yes. Use that parameter to suppress the category link in mainspace.
Trappist the monk (talk) 15:27, 1 December 2024 (UTC)[reply]
@Trappist the monk: The issue is not about categorisation, but tooltips vs. popups. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:37, 1 December 2024 (UTC)[reply]
Sigh. I was responding to Editor SchroCat's comment: The template guidance specifically says not to use this format because it doesn't work on talk and some other pages. In fact it does work on talk and ... other pages as evidenced in the OP. As I explained, it will not work if included as-is on main page. If the {{lang}} template is retained, |nocat=yes is your friend.
Trappist the monk (talk) 15:53, 1 December 2024 (UTC)[reply]
For what it's worth (I suck at writing documentation – it is known), I have rewritten Template:Lang § Links.
Trappist the monk (talk) 17:47, 1 December 2024 (UTC)[reply]
"Your suggestion ... shows as the following error message..." I suggested that "What should probably be done is to modify the template" to allow such usage; not that it is possible at the moment. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:34, 1 December 2024 (UTC)[reply]
Personally I think this is not an appropriate usage of the {{lang}} template in the first place. "École Polytechnique" is the English language common name for the institution, this is a proper name and not a foreign-language term that requires clarification. The fact that it originates from French is not really relevant, any more than Paris Saint-Germain FC or Notre-Dame de Paris. We should remove the template per Art LaPella's original suggestion, as that is the correct thing to do.  — Amakuru (talk) 11:23, 4 December 2024 (UTC)[reply]
I asked about the use a year ago, and was told that it doesn't matter if it is a proper name or not, the template should be used. It's not in English, despite the fact that it is the common name.
Either way, the point is moot: someone removed the template a couple of days ago, although it wasn't the "correct" thing to do. - SchroCat (talk) 12:33, 4 December 2024 (UTC)[reply]

Errors with "In the news"

Errors in "Did you know ..."

  • In the Lou Rash hook, it would be helpful for non-Americans if NFL were linked or even spelt out. I am also not really sure what "release" meant in this context: release from some contract, I guess. But on first reading the hook, I was supposing it was referring to a prisoner who had to return to jail. I'm never sure whether ambiguities like this are a deliberate ploy to garner more clicks, but to me they cheapen Wikipedia. JMCHutchinson (talk) 18:28, 4 December 2024 (UTC)[reply]
    I went and at least linked NFL, as the context is needed to understand release. I think the wording was just subject experts not realizing that non-experts might not understand the term here.—Bagumba (talk) 04:02, 5 December 2024 (UTC)[reply]

Errors in "On this day"

(December 6, tomorrow)
(December 9)

General discussion

Accessibility: We could so do much better

Of the five images currently in the home page only one has anything like suitable alt text.

The current alt texts are:

File:Bird notes and news (1912) (14562015579).jpg
Lord Curzon, winner of the election
File:2014 Rallye Deutschland by 2eight 8SC0443.jpg
Thierry Neuville in 2014
File:Presidente Nayib Bukele (cropped).jpg
Nayib Bukele
File:Shropshire Scotsman.jpg
The Flying Scotsman
File:Sir Winston Churchill - 19086236948.jpg
Black-and-white image of Winston Churchill standing with his left hand on his hip and his right hand resting on the back of a chair

Three of the first four simply repeat the image caption, which is redundant, while the fourth adds "in 2014", which cannot be determined from looking at the picture, and in any case belongs in the caption, if anywhere (why would a blind person need to know that, but not a sighted person?).

What needs to change for things to improve? Do we need to write clearer guidance (we have an MOS page on alt text already)? Do we need to add an explicit check to the criteria for inclusion? Something else?

I'm sure we wouldn't tolerate frequent breaches of other parts of the MOS on the home page, yet the impact of doing so for alt text is far greater, for a proportion of our users, than things like inconsistent capitalisation or curly apostrophes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:33, 30 November 2024 (UTC)[reply]

Note that even the Churchill alttext isn't alttext. It appears to sighted people as a tooltip, even though the description is helpful only to the blind and annoying to others. Sighted people vastly outnumber the blind, so one might think we'd fix it for sighted people first.
Previous discussion
Art LaPella (talk) 06:11, 1 December 2024 (UTC)[reply]
<img alt="Black-and-white image of Winston Churchill standing with his left hand on his hip and his right hand resting on the back of a chair" src="<img alt="Black-and-white image of Winston Churchill standing with his left hand on his hip and his right hand resting on the back of a chair" src="... It's alt text. And no, no one with any sense would think ableist nonsense like "we'd fix it for sighted people first". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:32, 1 December 2024 (UTC)[reply]
Just so you know, the redundant alt text wasn't manually set – {{main page image}} uses the caption for alt text whenever it's not given an |alt= parameter. If you think that default sn't helpful, you could propose removing it at Template talk:Main page image. jlwoodwa (talk) 04:47, 2 December 2024 (UTC)[reply]
It is indeed not helpful and I have made that point every time such use has been proposed (I will do so again for the template in question; thank you). However, in this case my point is that - if we are going to put images in our "shop window" - we should be extra careful about manually adding appropriate alt text. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:02, 2 December 2024 (UTC)[reply]
I suspect the main problem is the volatility of main page images rotating around ~24hr. Its one thing when the image is used "permanently" in an article, but we don't give the same thought to an image that is here today, gone tomorrow. Masem (t) 12:59, 2 December 2024 (UTC)[reply]
This also makes me wonder why we do not have a tech approach that would automatically draw an alt text from an image description file (whether here or commons) to use as the default alt text if one is not provided in the image tag. I can't see many cases where one appropriate alt text could be written for an image that would apply in any context 99% of the time. — Preceding unsigned comment added by Masem (talkcontribs) 14:10, 2 December 2024 (UTC)[reply]
Because alt text is often content dependent. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:26, 2 December 2024 (UTC)[reply]
People seem to mange to do it OK on ephemeral services like social media. It's not like we don't collectively spend 100s of hours debating transient DYK hooks, for example. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:26, 2 December 2024 (UTC)[reply]

 You are invited to join the discussion at Wikipedia:Village pump (idea lab) § New main page section: Wikipedia tips. Ca talk to me! 07:32, 1 December 2024 (UTC)[reply]

The redirect Mian Page has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2024 December 2 § Mian Page until a consensus is reached. Ca talk to me! 01:18, 2 December 2024 (UTC)[reply]

Issue with wide TFA images on mobile

Can someone try to figure out how to fix wide image formatting in the FA blurbs on mobile devices? This has become more and more apparent with recent FAs. Right now for the KARE article, the image has a width that is not quite 100% of the box it is in, but the text is still trying to wrap alongside it in the narrow space that remains. This results in a whopping 2 characters per line appearing for the first 4 lines of the blurb. It is incredibly frustrating as a reader and long-time contributor that mobile layouts can still look like this in 2024. Y2Kcrazyjoker4 (talkcontributions) 06:10, 4 December 2024 (UTC)[reply]

This is probably best as a general thread at Talk:Main Page unless there's an issue specific to the KARE image. -- Tamzin[cetacean needed] (they|xe|🤷) 06:15, 4 December 2024 (UTC)[reply]
Agree with T: this isn't an error in the blurb (which is what this section is for), but a flaw in the structure way beyond the capabilities of any editor to fix - it's something the WMF tech people need to fix. - SchroCat (talk) 08:52, 4 December 2024 (UTC)[reply]
Moved. Courtesy pings @Y2kcrazyjoker4 and SchroCat. -- Tamzin[cetacean needed] (they|xe|🤷) 08:59, 4 December 2024 (UTC)[reply]
I see the same problem on mobile. I seem to recall that when we've had this problem before, it was simply fixed by putting {{nowrap}} around the problematic text. So in this case, something like:
{{nowrap|'''[[KARE (TV)|KARE]]'''}} {{nowrap|(channel 11)}}
I haven't tested this though. Modest Genius talk 12:43, 4 December 2024 (UTC)[reply]