Talk:2026 FIFA World Cup

From WikiProjectMed
Jump to navigation Jump to search
The word "soccer" is used in this article instead of "football", as per WP:TIES and WP:ENGVAR. Likewise, use the singular for teams; "France was defeated by Argentina", not "France were defeated".

Broadcasting

i have to suggest that Broadcasting Rights Panel have to align in


Broadcasting Rights Panel have to align in wikitable panel Nauman335 (talk) 07:33, 2 October 2023 (UTC)[reply]
Territory Rights Holder(s)

this is better Nauman335 (talk) 07:32, 2 October 2023 (UTC)[reply]

Small note, but YLE should be written Yle. The all-caps version hasn't officially been used in 12 years. This mistake is still often seen in Wikipedia, what would be the best way to get it fixed? Source in Finnish: [1] — Preceding unsigned comment added by 83.150.64.252 (talk) 07:19, 8 February 2024 (UTC)[reply]

References

  1. ^ https://yle.fi/aihe/s/ylen-brandi-ilme-ja-logot

"Canada-Mexico-United States 2026" listed at Redirects for discussion

The redirect Canada-Mexico-United States 2026 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 January 24 § Canada-Mexico-United States 2026 until a consensus is reached. Hey man im josh (talk) 20:35, 24 January 2024 (UTC)[reply]

. Support - I can see that it may be likely for readers to look that up, I support. Besides, there is no harm in this redirect. 🅲🅻🅴🆃🅴🆁 (a word) 02:46, 7 February 2024 (UTC)[reply]

2026 World Cup and 2026 Super Bowl

It has come to my attention that both the World Cup and the Super Bowl are taking place in Santa Clara. Should we mention? DeathCat36 (talk) 00:13, 4 February 2024 (UTC)[reply]

Personally, I think that is a non-issue, you could mention it in the Levi's Stadium page however. IntMaMis (talk) 18:12, 4 February 2024 (UTC)[reply]

Adding official FIFA stadium names to the venue format

I'd personally like for the venue information to mention the official FIFA stadium names for the 2026 World Cup. This is a procedure that is clearly lined out in FIFA's rules (Specifically that you can't have the name of the venue have a sponsor that isn't an official FIFA sponsor and if you do the stadium will be given a neutral name), so for example MetLife Stadium gets the name "NYNJ Stadium". This has been a common procedure throughout World Cup pages (See 2006 as a major example) on Wikipedia and this should be carried over to this page as well. IntMaMis (talk) 18:20, 4 February 2024 (UTC)[reply]

I suggest taking a look at the article for the 2015 Women's World Cup in Canada and following the format used there—at least two stadiums used temporary names for that tournament and the venue table showed both (the real name as the link, given that those are the articles' names, and the temporary FIFA name in parentheses). That seems like a useful way to handle it. 1995hoo (talk) 22:13, 4 February 2024 (UTC)[reply]
@1995hoo@IntMaMis
You can see the official stadium names at the FIFA tournament website. Now, my concern is that the table is going to get crowded if we start listing the host city, stadium name, stadium's sponsored name, and the stadium location. Adeletron 3030 (talk • edits) 21:12, 8 February 2024 (UTC)[reply]
After looking at that website, I think adding the FIFA names seems pointless because in effect it would just mean repeating the metropolitan areas' names over again. It would be redundant to the extreme—even if there is a city name that is used by another city somewhere else that could be confused (and I don't think the other Vancouver in Washington State qualifies!), the table provides the necessary context already. To the extent it's necessary to clarify, perhaps the way to do it is to drop a footnote along the lines of, "FIFA rules prohibit tournament organizers from referring to stadiums by corporate names that do not belong to FIFA sponsors. For purposes of the 2026 World Cup, stadiums with sponsored names will be referred to by their metropolitan area names, e.g., Boston Stadium." (I would avoid using the word "official" in the article because it doesn't really add anything in this context and because arguably the "official" names are the normal ones and the FIFA-imposed names are temporary names, regardless of whether FIFA considers them "official" for its purposes.) 1995hoo (talk) 21:42, 8 February 2024 (UTC)[reply]
Agreed - "Boston's Boston Stadium, also known as Gillette Field in Foxborough, Massachussets" is too many words saying very little. Adeletron 3030 (talk • edits) 02:16, 9 February 2024 (UTC)[reply]
We either need the sponsored names or the non-sponsored name being used, but not both. My preference would be for the non sponsored names, to match the FIFA documentation on the stadium names for this tournament. Joseph2302 (talk) 17:56, 9 February 2024 (UTC)[reply]

Marketing

There are three new logos that were unveiled during the schedule release. They have stylized elements of their flag (Canada red and with a maple leaf, Mexico green with an eagle, and the United States blue with stars and stripes) Can we try and include them? 47.153.148.108 (talk) 23:34, 4 February 2024 (UTC)[reply]

I don't see any need to do that. We already have a representative logo in the infobox and we don't include any of the other logos. — Jkudlick ⚓ (talk) 02:16, 6 February 2024 (UTC)[reply]
One logo is fine, using all of them would violate WP:NFCC#3- minimal use of non free media. Joseph2302 (talk) 17:58, 9 February 2024 (UTC)[reply]

Lint errors in map caption

@Jonesey95: You mentioned in a recent edit summary that the previous version of the map caption contained lint errors. Could you explain in layman's terms what this means, and perhaps suggest an alternative solution? I dislike how the "Central Region" column takes up space that the other two columns could have instead to fit "San Francisco Bay Area" and "New York/New Jersey" on a single line. — AFC Vixen 🦊 08:46, 22 February 2024 (UTC)[reply]

The {{nobreak}} template uses <span>...</span> tags to mark an in-line piece of content, like a few words, as "do not wrap this text". In HTML, span tags are not allowed to wrap around "block" content, which is content that extends across multiple lines or that contains div tags. In my edit, I removed the nobreak template where it was wrapping div-tag-based content. If you want to use nobreak/nowrap, it needs to wrap only a short piece of text. – Jonesey95 (talk) 15:32, 22 February 2024 (UTC)[reply]
I also removed the font-size specification, per MOS:FONTSIZE. Fonts can't be rendered at less than 85% of the default text size for the page. – Jonesey95 (talk) 15:34, 22 February 2024 (UTC)[reply]
Map
About OpenStreetMaps
Maps: terms of use
5000km
3,100miles
none
.
I've been toying around with the {{Div col}} that was added, and this was the best replica of the previous {{col-begin}}-based caption I could make for now (right). I made use of a single {{Ubl}} instead of three, and strategically placed non-breaking spaces to produce blank rows that help populate the columns in the exact same way they were before. Does this produce any errors? If not, is there any way to customise the width of one particular column? If there isn't, is there any alternate way "2 San Francisco Bay Area" and "14 New York/New Jersey" can be forced to appear on one line without using {{nobreak}} and producing an error? — AFC Vixen 🦊 19:24, 22 February 2024 (UTC)[reply]
@Jonesey95: When you removed the <div>...</div> tags, would that not have solved the problem with the {{nobreak}}? Or does the Linter error still exist with {{col-begin}}/{{col-break}}/{{col-end}} or {{Div col}}/{{Div col end}}? — Jkudlick ⚓ (talk) 17:34, 23 February 2024 (UTC)[reply]
The problem was that {{nobreak}} was wrapping Module:overlay, which uses div tags. – Jonesey95 (talk) 07:04, 24 February 2024 (UTC)[reply]
Do you have any answers to the questions I had, or no? — AFC Vixen 🦊 11:56, 24 February 2024 (UTC)[reply]
I will answer this. {{div col}} also uses div tags, as does {{col begin}}. I suspect the usage of these templates will produce the same errors Jonesey had mentioned. Jalen Folf (talk) 15:10, 24 February 2024 (UTC)[reply]
For the time being then, if there really isn't a way to customise the widths of individual columns in {{Div col}}, then I'll simply truncate "San Francisco Bay Area" to simply "San Francisco" and "New York/New Jersey" to "New York". — AFC Vixen 🦊 15:19, 24 February 2024 (UTC)[reply]
If I understand Jonesey correctly, <span/> can exist within <div/> without any errors, but the issue is templates and modules that use <div/> can't exist within <span/> without throwing errors. I wonder if using Module:Overlay is required in the map legend, or if we can use {{bgcolor}} (which uses <span/> tags), e.g. {{nobreak|'''{{bgcolor|#b2decf| 2 }}''' [[San Francisco Bay Area]]}} to produce  2  San Francisco Bay Area. — Jkudlick ⚓ (talk) 17:45, 24 February 2024 (UTC)[reply]
UPDATE: I have created a map legend at my sandbox that may work, but it requires widening the map to at least 400px. I have legends of 400px, 410px, and 420px there. — Jkudlick ⚓ (talk) 18:32, 24 February 2024 (UTC)[reply]

I think the current setup with the truncated names is fine, especially if it means we can keep the map as small as reasonably possible at its 340px width. — AFC Vixen 🦊 18:38, 24 February 2024 (UTC)[reply]

Map
About OpenStreetMaps
Maps: terms of use
5000km
3,100miles
none
.
340px wide
I understand the concerns about map size. Reducing font size to 85% allows for 340px. See over there. → — Jkudlick ⚓ (talk) 17:17, 25 February 2024 (UTC)[reply]
I'd be somewhat okay with this. However, Jonesey, you implied in one of your edit summaries how use of templates like {{col-3}} in Jkudlick's example on the right are "generally not recommended". I'd like to know what informed this opinion. — AFC Vixen 🦊 17:29, 25 February 2024 (UTC)[reply]
Pinging Jonesey95. — Jkudlick ⚓ (talk) 17:45, 25 February 2024 (UTC)[reply]
My recollection is that using a fixed number of columns is less compatible with accessibility, varying screen widths and font sizes, or both, but I am unable to locate that guidance now. I could be misremembering, or something might have changed. Meanwhile, reducing the font size as shown immediately above is not allowed per MOS:SMALLFONT; it reduces the font size to 76% of the default font size for the page. – Jonesey95 (talk) 00:17, 26 February 2024 (UTC)[reply]
@Jonesey95: I would think three explicit columns would be acceptable in this particular scenario, as the venues are split into three geographical regions. However, I misunderstood SMALLFONT and understand the resulting text in my revision here is not allowed in an article. I have to concur with AFC Vixen that what we currently have in the article is the best compromise that is in compliance with MOS and other guidelines. — Jkudlick ⚓ (talk) 02:53, 26 February 2024 (UTC)[reply]
The text looks good on my screen as of this time stamp. The font size is 88% of the default, and none of the text is wrapping or extending past the boundary of the box. I think we've got it resolved. – Jonesey95 (talk) 04:10, 26 February 2024 (UTC)[reply]

Distribution of third place teams in knockout round

Has there been any announcement from FIFA how the third place teams who qualify for the knockout round will be distributed? There are 495 different combinations of teams who could qualify (), which would make for an extremely complicated or lengthy distribution matrix. — Jkudlick ⚓ (talk) 16:25, 10 March 2024 (UTC)[reply]

French language in infobox

I attempted to remove the French translation from the infobox, as the event will only be held in Anglophone regions of Canada (namely Toronto and Vancouver) only to be reverted by @Jkudlick: under the reasoning that "French is one of the official languages of Canada". It is not standard for English Wikipedia to provide French translations of the names of sporting events in Anglophone regions of Canada- e.g. Quebec City Marathon contains a French translation but Vancouver Marathon does not contain a French translation. For this reason I don't see any reason why the French language should be included here. Chessrat (talk, contributions) 20:32, 31 March 2024 (UTC)[reply]

It is standard for the WP:FOOTY project to provide translations of major tournament names in English and in all official languages of the host nation(s). Your argument that Vancouver Marathon does not include a French translation does not take into consideration that WP:Some stuff exists for a reason. In other words, where there is precedent, it should be followed unless there is a convincing reason to do so. Not including French ignores that a significant portion of the Canadian population not only speaks French, but does not speak English. — Jkudlick ⚓ (talk) 02:36, 1 April 2024 (UTC)[reply]
Yeah, not sure what the problem could be here. Canada is officially bi-lingual and the bid for the competition was done at the country level (United 2026 FIFA World Cup bid), not at the province level. --McSly (talk) 03:23, 1 April 2024 (UTC)[reply]
All Canadian soccer competitions have French even if Quebec and New Brunswick do not host matches. 159.115.9.43 (talk) 18:52, 2 April 2024 (UTC)[reply]
Retrieved from "https://mdwiki.org/wiki/Talk:2026_FIFA_World_Cup"