Template talk:Football squad player

Latest comment: 3 years ago by Wbm1058 in topic High node counts coming from this template

Add postion Field Player (FP)

edit

Hey! Can the position FP be added to the template, as I was using this template for a futsal squad and players other than goalkeepers are usually referred as field players in futsal.--Anbans 585 (talk) 17:16, 30 July 2018 (UTC)Reply

Anbans 585, from looking at Futsal positions it seems like field player isn't listed there. Is there an article that I could link to describing the position of field player, as there is for the four positions currently in the template? It would look slightly weird if the link to Field player were a redirect.
Actually, since the template would link to the football definition of goalkeeper, do you think it might also be advisable to create a separate {{Futsal squad player}}? Enterprisey (talk!) 04:35, 4 September 2018 (UTC)Reply
Enterprisey, no I don't think we require to create a separate template for it. Actually the template {{nat fs start no caps}} contains a parameter 'Field Player' which now redirects to Futsal positions. Though you are right that futsal has outfield positions like defender, forward etc, but in futsal terms they are usually known as ala, pivot, etc. Though when any futsal squad is announced for a competition, if the position of the player is unknown (the player is not a goalkeeper) then he is usually referred as a 'Field Player', that is why I wanted that if possible a 'FP' parameter can also be added to this template, as this template is usually used for displaying a club squad.--Anbans 585 (talk) 10:49, 4 September 2018 (UTC)Reply

Can the above request be completed?--Anbans 585 (talk) 14:18, 5 August 2019 (UTC)Reply

See Association football positions. Is the correct term outfield player? By this terminology, even the GK is a "field player", i.e. football player. Unless futsal uses different terminology than football. – wbm1058 (talk) 18:11, 7 March 2021 (UTC)Reply
@Wbm1058: Yep, in futsal it's common to use GK and FP. This match report sees two teams using different positions: Japan uses GK and FP, Lebanon uses GK, DF, MF, FW. Nehme1499 19:24, 7 March 2021 (UTC)Reply

Multiple issues

edit

Why have we truncated the template? Also, I don't like the deviation on the background colour from plain page to a different background, having issues with that. Also, the alternative code is gone for the flag icons and that needs to be reinstated. Govvy (talk) 12:45, 17 August 2020 (UTC)Reply

@Govvy: Do you mean the alternative text? It is already present for the flag icons. S.A. Julio (talk) 14:22, 17 August 2020 (UTC)Reply
@S.A. Julio: I can't see any alt text when I hover over the flags (e.g. here). I'm not sure what Govvy means by 'truncated' though? If anything the new version is slightly larger as it now includes the trigrammes. Number 57 14:29, 17 August 2020 (UTC)Reply
I think the nationality isn't being read out because the idea is that it's not the nationality being displayed, rather the nation's football federation. Nehme1499 (talk) 14:45, 17 August 2020 (UTC)Reply
@Number 57: The alt attribute is present for the flag icons (you can view this in the source code). However, the flag icons themselves are not linked (the accompanying FIFA trigramme instead is). Normally you see the text "England" when hovering over   because it links to England (done by the software), while no mouseover text displays over the flag icons for   ENG or   England. However, if desired I can add mouseover text using the title attribute (though I have not usually noticed this used in flag templates). S.A. Julio (talk) 15:15, 17 August 2020 (UTC)Reply
On my 15" screen it looks, I don't know, truncated to me, I find the hover over text really very helpful, especially when I am not sure of the flag colours, and the three letter's afterwards, I am not really sure about that, it should be a whole name or not at all in my opinion, the three letters might be confusing to certain readers. Govvy (talk) 16:01, 17 August 2020 (UTC)Reply
I am in agreement with that, the three letters doesn't tell you which country the player comes from does it? REDMAN 2019 (talk) 16:56, 17 August 2020 (UTC)Reply
If it's the full name, the template will be a mess when you have players from countries with long names. The idea behind using the trigrammes was that they are consistently three letters. Number 57 17:29, 17 August 2020 (UTC)Reply
I don't know about other people, but I am not a fan of the three letters, nor the over-linked squad positions. Govvy (talk) 18:13, 17 August 2020 (UTC)Reply
I don't think it's possible to automatically de-link multiple instances of positions. As for the trigram, it's the only aesthetically pleasing solution because, as N57 pointed out, some countries (such as Trinidad and Tobago) would mess up the table width. Nehme1499 (talk) 19:26, 17 August 2020 (UTC)Reply
I didn't think there was anything wrong before the changes. I would say if it ain't broke don't fix it!! :/ Govvy (talk) 19:43, 17 August 2020 (UTC)Reply
I would also prefer for there to only be a flag, without text. However, it apparently violates MOS:ACCESS, so we needed to add some text. As for the positions, I don't think it's different than before? Nehme1499 (talk) 19:50, 17 August 2020 (UTC)Reply
Yes, the positions were linked on every line in the previous version. Number 57 20:36, 17 August 2020 (UTC)Reply
The flags and the country codes seems like massive overkill and just makes the template look crowded and clunky. Do we really need country codes? NouveauSarfas (Talk page) 00:33, 18 August 2020 (UTC)Reply
Per the RfC above, we can't put only the flag without the country's name (or code) next to it, per MOS:ACCESS. Nehme1499 (talk) 00:38, 18 August 2020 (UTC)Reply

Oh, bugger is all I can say. Can we at least change the background back to normal? Govvy (talk) 21:04, 17 August 2020 (UTC)Reply

I wouldn't necessarily have a problem with this, but the outcome of the section RfC on this was to use MediaWiki default (albeit not with a terrible amount of consensus). I'm also not sure how to change this. It looks like the code is looking at something that defines "wikitable football-squad", but I have no idea where this is. I assume Tholme knows where it is? Number 57 21:25, 17 August 2020 (UTC)Reply
The real problem is that this template is not suited for this to start with. The cramped layout when accessibility was correctly considered was a primary motivator when {{Fs player2 sort}} was created 12 years ago. It is wider and longer, but does not look cramped, and you get the full nation name not a TLA. While the other template still needs to be fixed so it links to the association, not nation, it's a better fit for accessibility. I'll also remind readers here that the trigram with a tool tip is still a minor issue as tablets cannot hover easily to get the tool tip.
I suppose, you could make each side of this template a wider to avoid this cramping. Walter Görlitz (talk) 02:19, 18 August 2020 (UTC)Reply
What I don't understand is, why was {{Fs player2 sort}} created 12 years ago? Why weren't changes made directly to {{Football squad player}}? I'm not saying one is better than the other, but I really don't see why we now have Saudi, American, and a handful of other countries only using Fs player2, while 99% of other leagues use Fs player. Nehme1499 (talk) 12:11, 18 August 2020 (UTC)Reply
From memory, fs start/player/end2 was initially created as a form of a sandbox version to showcase a potential change, but there was insufficient support to change the main template to that format. However, rather than it being left as a dead end, some editors began using v2 instead. It's a mess that should never have been allowed to happen, but there is a bit of a history of North American editors doing things their own way (I recall at least one threat to start a breakaway WikiProject after a dispute over wording in {{Infobox football club}}), and lower profile leagues are often prone to a single editor implementing changes across a wide number of articles without discussion (I guess this may have happened with the Saudi ones). Number 57 14:03, 18 August 2020 (UTC)Reply
Maybe it should just be one table like the fs player2 sort, and in one column. I think being able to sort the table is very useful. There will then also be space to use the full name for nations.

The background is set in Commons.css for wikitable, but it is possible to overwrite with css styling on the individual rows. I belive the best would to use a more normal wikitable with standard grid lines and backgrounds. Tholme (talk) 16:49, 18 August 2020 (UTC)Reply

Yes, the second template was made in an effort to address accessibility. The consensus us one large table is not preferred by most, and ideally a responsive table should be used if possible so that mobile viewers can see it better. I can't recall what the effect of having the "two column" view is on screen readers—the tool that those who have difficulty seeing text use to read the page to them—but if I recall, they read across the table, not down numerically. This is avoided with a single-column table. Walter Görlitz (talk) 20:25, 18 August 2020 (UTC)Reply

Merge with {{Football squad player2}}

edit

So, what is missing to merge the two? Nehme1499 (talk) 21:27, 22 September 2020 (UTC)Reply

MOS:ACCESS had to be met and ideally, WP:OVERLINK. Walter Görlitz (talk) 04:53, 23 September 2020 (UTC)Reply
Didn't we already meed ACCESS? And OVERLINK doesn't apply to tables. Nehme1499 (talk) 14:15, 23 September 2020 (UTC)Reply
You're confusing may be linked in tables with must be linked. If a reader of the roster would be helped by the link is the question. If we had used full names rather than the three-letter acronyms, is there any benefit to the links here Arsenal F.C.#First-team squad? Gabon is the only uncommon nation in the list. I can see millions of readers thinking, "I wonder if there's a Wikipedia article about the football association in Germany? Oh I know how to find it: Arsenal's keeper is German, I'll click through to the roster to get to it." Granted, the better squad listing also links it so it's not any better, but easier to solve. Walter Görlitz (talk) 16:26, 23 September 2020 (UTC)Reply
The positions and countries are linked for every player both versions of the squad template, so this is not an issue that is preventing a merger of the two.
A constructive answer is that there are two options to resolve this:
  1. Manually change every article using fs player2 to the main template
  2. Make fs squad player backwards compatible with {{fs player2}} and {{Fs player2 sort}} (e.g. enable {{fs player}} to process with firstname/lastname input) and deal with any article that is using a non-standard heading for the squad (you may be able to create a list of every article that uses. Once that's resolved, the template can simply be redirected.
Number 57 17:32, 23 September 2020 (UTC)Reply
That won't work since it uses a single column and is preferable. Use the better template and ditch this one. It's really a lot easier, especially when you can just ignore the mid. Walter Görlitz (talk) 06:04, 24 September 2020 (UTC)Reply
@Trialpears: Any update? Nehme1499 (talk) 02:34, 18 December 2020 (UTC)Reply
No, because of the problems that remain. Walter Görlitz (talk) 04:39, 18 December 2020 (UTC)Reply

After seeing that several "football transfers" articles had landed in Category:Pages where node count is exceeded using many football squad player tables, I somehow fell into this rabbit hole, where I've been for the past two days. I've just noticed that Template:Football team 1 redirects to Template:Football squad start and Template:Football team 2 redirects to Template:Football squad mid and these templates are used in articles such as FA Youth Cup Finals of the 2000s, where each column in a 2-column table is for a different team. This throws a little monkey wrench at the idea that tables could be auto-split into two columns at the midway point on screens large enough to support two columns. – wbm1058 (talk) 23:41, 14 February 2021 (UTC)Reply

@Wbm1058: This template shouldn't be used in that page. It should be formatted as such, using tables for the players. Nehme1499 (talk) 23:59, 14 February 2021 (UTC)Reply
It shouldn't be too much work to change the usage of those. Just 1816 pages use {{Football team 1}} 16 pages use {{Football team 2}}. – wbm1058 (talk) 00:16, 15 February 2021 (UTC)Reply
@Wbm1058: Yep, agreed. Regarding the merge of Fs player and Fs player2, do you think it's going to be complicated? Are there other things that have to be taken care of before they can be merged? Nehme1499 (talk) 00:26, 15 February 2021 (UTC)Reply
I've made several edits which bring the two into closer alignment, and so far nobody has reverted me or objected to any of my edits. See the next subsection. wbm1058 (talk) 04:37, 15 February 2021 (UTC)Reply
It was bound to happen. One of my edits to Template:Football squad start was reverted, so I have made a corresponding edit to Template:Football squad start2. See WT:FOOTBALL#Fs start - template update question. – wbm1058 (talk) 15:06, 15 February 2021 (UTC)Reply
{{{team}}} was added on 25 August 2012 to allow for some merging Template:Football team 1 & Template:Football team 2 (they had actually been merged on 7 June 2012‎ but support for the {{{team}}} parameter had been neglected). The February monthly TemplateData usage report shows {{{team}}} only used on 15 pages, which seem to be the same pages that use Template:Football team 1 & Template:Football team 2. So if we substitute those templates on these pages I think we'll just have the wikitable source code on those pages without the tables being generated by templates, and we can drop support for {{{team}}} as an unused parameter rather than merge that parameter into Template:Football squad start2. – wbm1058 (talk) 20:09, 15 February 2021 (UTC)Reply
I haven't seen any discussions about the matter, but I suppose the reason for using templates to build a squad's roster is that membership is under constant flux, and it's easier for editors unfamiliar with wikitable syntax to add or remove team members when the implementation uses templates. But for matches the opposing squads for the match are what they were, and will never change, so it's better to just use wikitables as these will never need to be edited except to correct any errors. – wbm1058 (talk) 20:50, 15 February 2021 (UTC)Reply
Hmm, Template:Football line-up. – wbm1058 (talk) 04:28, 26 February 2021 (UTC)Reply

Responsive template

edit

The consensus was to make the table responsive to window width (if possible) or two-column (if not), but I can see from the discussion above that making it responsive is important to Walter Görlitz, so we should try again for that. I see that earlier attempts didn't find an acceptable solution. Below are transcluded discussions relevant to that from Number 57 talk. – wbm1058 (talk) 04:37, 15 February 2021 (UTC) Reply

Sidebar discussions

Template:Football squad player

edit

Hi, two things. Firstly, there is a rogue "|}" at the end of the template. Secondly, can you make it so that Template:Football squad player2 becomes a redirect to Template:Football squad player? Thanks, Nehme1499 (talk) 16:21, 15 August 2020 (UTC)Reply

@Nehme1499: I think I've fixed the |}. Not sure about redirecting yet. Number 57 16:22, 15 August 2020 (UTC)Reply
Not sure in the sense that you don't know how to do it, or not sure if we should even do it? Nehme1499 (talk) 16:23, 15 August 2020 (UTC)Reply
@Nehme1499: I have not checked the compatibility of the code yet. Number 57 16:24, 15 August 2020 (UTC)Reply
Ok makes sense. It seems that Fs player2 doesn't use a "Fs player2 start", "mid", or "end", rather a wikitable, which complicates things. How do you think it can be solved? Nehme1499 (talk) 16:27, 15 August 2020 (UTC)Reply
@Nehme1499: It does use start and end in some cases (see e.g. Toronto FC). The main issue I can see is the use of {{Fs player2 sort}}. If we redirected fs start and end2 to the main ones, the table would work, but the headings would be out of order (e.g. the nationality of the players appears in the last column). {{fs player}} needs to be reworked to able to accept both the normal input and the parameters used in {{Fs player2 sort}} before a wholescale transfer over could be done. In the meantime, to enable this, someone should go round and introduce fs start2 and fs end2 to all the articles missing it, as this will enable the transition once it's ready. Number 57 16:34, 15 August 2020 (UTC)Reply
Can you highlight this in WT:FOOTY? This way, it's more likely to find an editor (or more) who would help us out in this. Nehme1499 (talk) 16:37, 15 August 2020 (UTC)Reply
@Nehme1499: Will leave a message there later (I'm about to go off to do something for a bit). I'd imagine there may be some comments about the change made to the squadlist, so worth keeping an eye out for that and referring people to the RfC outcome if they aren't happy with the changes. Cheers, Number 57 16:45, 15 August 2020 (UTC)Reply
Ok thanks. I'll do that. Also, could you also explain the situation to Frietjes? She's pretty good with templates, so she should be able to give us a hand. Nehme1499 (talk) 16:58, 15 August 2020 (UTC)Reply

Change to Template:Football squad player

edit

Hello,

In the change that you made to {{Football squad player}} template the two columns that were side by side are now appearing one below the other when there is a wide entry that used to wrap. Thus extending the squad listing and having a middle set of headings at the {{fs mid}} point. You can see the effect on this article. Keith D (talk) 22:38, 15 August 2020 (UTC)Reply

@Keith D: The two columns remain side by side on the PC version. They only become one below the other on mobile view. Nehme1499 (talk) 22:45, 15 August 2020 (UTC)Reply
@Nehme1499: I have the problem on a laptop not on a mobile. Keith D (talk) 22:47, 15 August 2020 (UTC)Reply
@Keith D: Ah strange. I suppose you see two columns side by side when there isn't a "wide entry" (like here)? Nehme1499 (talk) 22:52, 15 August 2020 (UTC)Reply
This is a change that wasn't apparent in the testcases. I think it is something to do with what Tholme did in Template:Football squad start/sandbox and/or Template:Football squad mid/sandbox, but I can't work out what. It was a requested change as a result of the RfC, but I'm not sure this implementation really works, as it leaves a gap in the middle of the table when it switches to a single column. Cheers, Number 57 22:59, 15 August 2020 (UTC)Reply
@Keith D and Nehme1499: I think I've fixed it in the sandbox. Does it look ok the in testcases? Number 57 23:13, 15 August 2020 (UTC)Reply
The test cases look OK. Keith D (talk) 23:16, 15 August 2020 (UTC)Reply
@Keith D: Do you want me to make the change? Or was the narrowing to a single column actually helpful? It was a requested outcome of the RfC, but I am unsure whether this is a satisfactory implementation of it due to the gap and repeated heading. Number 57 23:18, 15 August 2020 (UTC)Reply
Ah no, now it shows two columns side-by-side on mobile view. I think the idea was for it to be dynamic (side-by-side on PC, one above the other on mobile). Nehme1499 (talk) 23:20, 15 August 2020 (UTC)Reply
As far as I am aware, there is no way to differentiate between mobile and PC views. It's either always side-by-side on both, or one-below-the-other on both. Number 57 23:22, 15 August 2020 (UTC)Reply
It was working on my end. On my phone, the columns were one below the other. On my laptop, they were next to each other. Nehme1499 (talk) 23:32, 15 August 2020 (UTC)Reply
You can make the change. The single column is not very helpful as it doubles the length of the squad list. Keith D (talk) 23:23, 15 August 2020 (UTC)Reply
@Keith D: Done. Number 57 23:26, 15 August 2020 (UTC)Reply
Thanks. That solves the problem on the article that I found it on. Keith D (talk) 23:28, 15 August 2020 (UTC)Reply
I think this last change should be reverted. The whole point was to use two tables that when there are enough width will be shown side by side. When there is not enough width (on narrow screens like mobiles), the tables will be shown one over the other. This was done by using two tables with display:inline-table set. Tholme (talk) 16:38, 18 August 2020 (UTC)Reply
@Tholme: The problem is that it didn't work properly. The second column of players didn't merge into the first, it just appeared beneath it, with a gap between the two tables and the header repeated. This wasn't a satisfactory solution as far as I can see. Number 57 19:55, 18 August 2020 (UTC)Reply
I agree that having it merged would be the best, but I think it is very difficult to make it work like that. The header is repeated in both cases, but you do not have to scroll sideways and having the tables squished. Repeating the header also have the added benefit that on small screens you can see the header when scrolling. Have you looked at the result for both cases on a mobile? Tholme (talk) 20:26, 18 August 2020 (UTC)Reply
To be honest, I am less bothered about the header than the large gap, which makes it look like a new table starting again. Number 57 20:27, 18 August 2020 (UTC)Reply
Hmm, I think the gap should be fixable. I will try in the sandbox and see if I can make this work. See also the comments on Template talk:Football squad player. Maybe we should continue the discussing there? Tholme (talk) 20:32, 18 August 2020 (UTC)Reply
Managed to get rid of the gap, but as it is two different tables they don't match up. This probarbly looks even worse... One table in one column is probably the best. Tholme (talk) 21:18, 18 August 2020 (UTC)Reply
@Tholme: The result of the RfC was to have a responsive template (which could adjust to a single column on narrow screens), and if this was not possible, to retain the two column system. I wonder whether it might be possible to build a more agile table using a Lua module? Number 57 21:21, 18 August 2020 (UTC)Reply
Actually, I don't think what you've done is too bad. The 'not matching up' issue could effectively be hidden by removing the background to the table – then all you'd see was that the 'player' heading was a different length (as everything else is a set width, the other columns all align. Number 57 21:23, 18 August 2020 (UTC)Reply
Also, I wonder whether it's possible to resolve by making the 'player' column heading fill whatever the remaining width of the table is (if the two columns are nested inside another hidden table. Ages ago I made a version where this heading width issue is solved, but I couldn't fix the problem of the columns being too far apart when they were side-by-side. Perhaps you could look at that as a potential solution? It is here. Cheers, Number 57 21:28, 18 August 2020 (UTC)Reply
@Tholme: Just pinging you again in case you didn't see my last two comments. Cheers, Number 57 21:31, 18 August 2020 (UTC)Reply
I have changed the background to be transparent, getting it to fill the remaining width I do not know how to achieve. Tholme (talk) 20:13, 20 August 2020 (UTC)Reply

Country name

edit

With regards to the recent change (which I reverted), I don't believe the discussion above is definitive on requiring the full country name (the closer refers to MOS:Icons#Accompany flags with country names, which gives {{flag|JPN}}(which produces   JPN) as an example of appropriate use). Using the full names makes the template look a mess – compare the two options here. Having the trigramme means the country name is a reasonably consistent width all the way through the table. When you start using full names, it starts looking quite disjointed. The full name works better on fs player 2 because the country is in the final column rather than in the middle, and also because that template has gridlines, making it easier to follow the row. As this version has no gridlines (confirmed in the RfC above), placing the full country name in the middle of the columns makes it noticeably harder to follow IMO. Cheers, Number 57 22:17, 24 February 2021 (UTC)Reply

While MOS:FLAG does advocate for the use of the full name "adjacent to the first use of the flag", the "Accompany flags with country names" section also states "However, some editors feel that some tables such as those containing sports statistics (example) are easier to read if {{flag}} is used throughout". Nehme1499 22:26, 24 February 2021 (UTC)Reply

There was an earlier, decade-old TL;DR discussion on this:

Template talk:Football squad player/Archive 1 §Country names

I think that the name of the country need to be placed next to the flag of the players' nationalities, i.e. use the {{flag}} template instead of {{flagicon}}. Using just the flag without the name of the country assumes the reader has the knowledge and the ability to recognise the flag, which may not necessarily be the case, and even if a reader does know their flags they can be difficult to distinguish at the size they are displayed here. The various blue ensigns in use around the world can cause particular difficulty, not to mention pairs of countries like Indonesia/Monaco which have identical flags, or the various combinations of the pan-african colours.

There needs to be some sort of clever wizardry to make sure that the output is   Central African Republic, rather than   CAF, when the three-letter ISO code has been used with the 'nat=' parameter instead of the full country name. — Gasheadsteve Talk to me 13:27, 25 March 2010 (UTC)Reply

That would indeed adress an abuse of WP:FLAG perpetuated in this template, but there are many other issues about the inclusion of flags that are not well resolved at present, like why are they considered relevant at all, especially for the vast majority of players who are nowhere near consideration for a national team; the false impression given about players who have played under what is not much more than a flag of convenience; presentation of incomplete information about players of multiple nationality or otherwise eligible for more than one team; and lack of verification. I would suggest holding fire until some or all of those have been resolved. Kevin McE (talk) 16:05, 30 March 2010 (UTC)Reply
@Gasheadsteve: No clever wizardry required; use {{flagcountry|CAF}} to get   Central African Republic. — Andrwsc (talk · contribs) 20:28, 30 March 2010 (UTC)Reply

Per above and Wikipedia:Manual of Style (icons)#Accompany flags with country names, {{editprotect}}

For {{fs player}}, change

| style="text-align: right;" |{{flagicon|{{{nat}}}|variant={{{natvar|}}}}}

to

| style="text-align: left;" |{{#if: {{{icononly|}}} | {{#ifeq: {{{icononly|}}} | yes | {{flagicon|{{{nat}}}|variant={{{natvar|}}}}} | {{flagcountry|{{{nat}}}|variant={{{natvar|}}}}} }} | {{flagcountry|{{{nat}}}|variant={{{natvar|}}}}} }}

(Per discussion below) also change for {{fs start}}

!width=1%|No.

!width=1%|

!width=1%|Position

to

!width=1%|No.

!width=22%|Nationality

!width=1%|Position

This incoporates a new parameter—"icononly". If "icononly" is empty (default) or not "yes", the country name will be shown. To show only the flag icon, simply add the parameter "icononly=yes". The default case complies with Wikipedia:Manual of Style (icons)#Accompany flags with country names, and having lists with names besides all the flags is still compliant with the guidelines. Any other sort of scheme as default goes against MOSFLAG. Jappalang (talk) 22:05, 19 July 2010 (UTC) :I request that this is declined until discussion has taken place at WT:FOOTY. Regards, --WFC (talk) 22:10, 19 July 2010 (UTC)Reply

Sorry, I think I may have misunderstood what is being requested. Could you expand on what this would do? --WFC (talk) 22:12, 19 July 2010 (UTC)Reply
  1. MOS is clear on one thing; when you first use a flag, put the name next to it.
  2. This change will make it such that the use of {{fs player}} will have the country name displayed next to the flag on default.
  3. To disable the name (for subsequent repetition of the flag), just use "icononly=yes".
The change will make display of a country name next to the flag a default. A new parameter is added to allow users to turn off the display of a country name next to the flag. The flags are always there in either case. Jappalang (talk) 22:48, 19 July 2010 (UTC)Reply
I'm not against following MOS:ICON in this regard. It's long overdue. But I think mandating a key would be a better solution. Otherwise all we are doing is taking an aspect of football squad lists that has consensus but is controversial (a player's nationality), and emphasising it further. By mandating a key (perhaps even encoding one into {{Fs start}} or {{Fs end}}) we could communicate the information without it dominating the table itself. Regards--WFC (talk) 23:04, 19 July 2010 (UTC)Reply
I am not certain putting the name is further emphasis when the graphic draws attention to itself like a candle in the dark (somewhat like "Ooo, a pretty flag... not sure which country it is? There is no name... do I click it to find out? Here goes.") A key (legend) is indeed an alternative, but it does not need to be implemented in the templates (it can be implemented as a separate table before the other lists and such). No article, however, has taken the initiative to (or perhaps is prohibited from) do so. Jappalang (talk) 23:20, 19 July 2010 (UTC)Reply
With regards to removing flags altogether, it's been tried, failed, and I doubt the outcome of any future attempt would be any different.   is against the MoS, I accept that. But   England is more prominent. Similarly, the large spaces left by only expanding a country on first use would also be more prominent than a uniform width.
In my defence, I did try to take the initiative with Watford (and another article, can't remember where but it will be in my contribution history). Neither stood the test of time. --WFC (talk) 23:34, 19 July 2010 (UTC)Reply
How about keeping a format very similar to the current style; having columns "Number", "Nationality", "Position", "Player", "Notes". Instead of a flag for nationality, have a flag and the full country name. And to amend for the obvious extended width this would create, have the list run in just one column, rather than the two it currently uses. 91.106.96.171 (talk) 23:49, 19 July 2010 (UTC)Reply
I agree that a column is needed. Beyond a slight preference for a key on whitespace grounds (USA vs Democratic Republic of Congo) I'd be happy with either solution. If the second method were used, a bot would need to remove {{Football squad mid}} from every article before the change were implemented. --WFC (talk) 00:02, 20 July 2010 (UTC)Reply
I hear ye, WFCforLife; my point is what you experienced: you were "prohibited from" doing so. You had implemented your key on 21 December 2009, but was later undone a month later by a User:JoeA2580, who removed the key without even an edit summary.[1] There is a faction that insists on having "pretty" layouts without care for others with visual disabilities (colour-blindness or such) or unfamiliarity with flags. Regardless, to make it clear, this proposal has naught to do with removal of flags.
User:91.106.96.171, this proposal does what you ask, it will place a country name next to the flag (by default). So can I take it that you and WFCforLife are agreeable to my suggested change to this template? Jappalang (talk) 05:11, 20 July 2010 (UTC)Reply
If accompanied by an edit to {{Football squad start}} to add a nationality column, I'm happy with that. We can always consider the possibility of changing to a key later, if desired. Thanks for your patience. --WFC-- 05:20, 20 July 2010 (UTC)Reply
No problems. The Nationality column has always been there; it just does not have a column title. If this change goes through, I will proceed to {{fs start}} to ask for the title to be implemented and the column's width extended from 1% to at least 22%. Jappalang (talk) 05:32, 20 July 2010 (UTC)Reply
Thats cool. Might be worth asking the admin to do them simultaneously though. A width of 1% might render strangely combined with expanded country names. --WFC-- 05:53, 20 July 2010 (UTC)Reply
Okay, I put up the suggestion above. I also changed the suggested "icon" parameter to "icononly" to make it less confusing to users. Let us see if an admin is willing to do this. Jappalang (talk) 20:20, 20 July 2010 (UTC)Reply
Looks good. Nice work! --WFC-- 20:42, 20 July 2010 (UTC)Reply
This looks hideously complicated, but that's just me. Has this been tested to ensure that it works? If so, could you copy the code to the template's sandbox so I can just copy and paste it, then stick the template back up. Thanks, HJ Mitchell | Penny for your thoughts? 01:54, 21 July 2010 (UTC)Reply

This will get even more complicated, as an edit will also need to be made to {{fs mid}}, unless a bot is going to mass-remove it. I've done some work, and the current state of play can be seen here. The player name field might prove to be a bit narrow (particularly for Eastern Europe), and we need to figure out a way to get Northern Ireland to render properly without compromising any further on player names. Once that conundrum is sorted I'll let you know. --WFC-- 02:33, 21 July 2010 (UTC)Reply

Right, we've cracked it

edit

{{editprotected}}

I'm filing this request on one page for the conveniece of the admin, but for procedural reasons will place {{editprotected}} on the other pages. I recommend making the edits in the order I have specified. In particular, it is vital that {{Football squad player}} is edited last.

These changes achieve two major things:

1. Ensuring that the template can comply with MOS:FLAG, by displaying the country name alongside the flag by default.
2. If country names have been spelt out in a previous table or a key, it is possible for the user to display flag icons only by using the new |icononly parameter.

Please:

  1. Replace the code in {{Football squad start}} with the code from {{Football squad start/sandbox}}
  2. Replace the code from {{Football squad mid}} with the code from {{Football squad mid/sandbox}}
  3. Replace the code from {{Football squad player}} with the code from {{Football squad player/sandbox}}

The combined effect of these changes can be seen at Template:Football squad player/testcases

Please credit User:Jappalang in the edit summary, as he has done much of the work. He indicated his approval for me to proceed with this request here. I now consider myself to have a very good understanding of the source code, so feel free to contact me with any queries. I also have this page watchlisted if you'd prefer to keep the discussion in one place. Regards, --WFC-- 01:10, 22 July 2010 (UTC)Reply

Wish I had been aware that this conversation was going on, but I guess that's my fault for having not put it on my watchlist after I had contributed in the early discussion.
I'd support it, but I would suspect mass revolt when it is rolled out: large amounts of white space won't go down well. Many team articles still list players on loan as an "other" section in fs mid: what would happen to such notes, and will it make very wide columns even more common?
My other reservation is that it might be seen to confirm the current header. FIFA eligibility rules do not allocate one nationality to every player in the workd, they simply indicate what will, and therefore what will not, be permitted if a national association wishes to name a player to its team. If Brazil were to decide that their World Cup campiagn would have gone better had they had a short-sighted overweight 47 year old with experience of playing at right back in the heights of inter-seminary football tournaments among their squad, FIFA would have told Dunga that I was not available to them, but FIFA has no opinion as to whether I am English, Irish or Northern Irish, nor does it have eligibiilty rules that would create any default position or order of preference between my potential eligibilities. The current header is factually wrong in that regard. Kevin McE (talk) 08:13, 22 July 2010 (UTC) (struck: WFC has introduced this under another heading below)Reply
I haven't changed the header. I request that you move that comment to another section so as not to complicate the matter. --WFC-- 09:02, 22 July 2010 (UTC)Reply

I hope you don't mind. I've moved the sandboxes and testcases to their proper places. I've also made a couple of other tweaks as well. Can you check if all is in order and I will make the changes. — Martin (MSGJ · talk) 12:47, 22 July 2010 (UTC)Reply

For the life of me I can't figure out what the extra |} you removed was for, but I've tested at length and everything seems fine. We look good to go. --WFC-- 20:52, 22 July 2010 (UTC)Reply
  all done. Let me know if they are any problems. — Martin (MSGJ · talk) 22:38, 22 July 2010 (UTC)Reply
Thanks. I've checked all the featured articles (and my own club), and haven't come across any problems. Aston Villa F.C. and Watford F.C. have images alongside them, but they still render well at 800x600. Aesthetically the template doesn't look fantastic for clubs without a squad numbering system, but that was already the case, and can be fixed with a new opt-in parameter if desired. I'll update the template's documentation accordingly. I'm having problems with wikipedia at the moment, but as soon as I get the opportunity I'll update the documentation. Regards, --WFC-- 23:13, 22 July 2010 (UTC)Reply

Looks appalling

edit

I just found out about this entire discussion today. It would have been nice if the proposed changes to the template were announced at WP:FOOTY prior to it going live, but that's a different matter. I appreciate that changing the template was done so that the flag icons comply with WP:MOSFLAG, but adding entire country name to the table makes the layout look utterly horrific. There has to be a better way. Wouldn't simply using the recognized FIFA Trigramme - ENG instead of England, USA instead of United States, COD instead of Democratic Republic of the Congo - make more sense? That way you can control column widths so they don't split across multiple lines and you're ensuring the spirit of MOSFLAG is retained without it looking like someone threw up on the screen. --JonBroxton (talk) 23:04, 22 July 2010 (UTC)Reply

I haven't updated the documentation yet, but it's possible to opt out of this change by using |icononly=yes in each {{Football squad player}} template. You would still have to find a way of complying with MOS:FLAG though (possibly your own key, such as the one that once existed in Watford, mentioned above). Regards, --WFC-- 23:15, 22 July 2010 (UTC)Reply
Each football squad player template?!?!? I maintain pages on over 200 US minor league teams, with over 5,000 players in the squad lists. Asking editors to do that is totally unrealistic. --JonBroxton (talk) 23:26, 22 July 2010 (UTC)Reply
Sorry, I didn't see this before. This change was the most convenient way of achieving MoS compliance, given that over 5,000 articles use this template.
The decision to use |icononly is made on the grounds that you are either going to knowingly ignore the manual of style, or that you'll comply with it in another way (for instance a key). Assuming the latter, you would still need to manually add a key in order to comply with it, which would involve a lot more work than copy-pasting "|icononly=yes" 25 times. Unless an article has Congolese players (that would be what, 5 or so US ones?) I really don't see why anyone would want to go to that trouble for the sake of avoiding a few characters' worth of whitespace. I'm not saying this is the finished product, but it was the most efficient solution to the problem of MoS compliance. I'm completely open-minded about superior alternatives. --WFC-- 01:18, 23 July 2010 (UTC)Reply
As for not mentioning this at WP:FOOTY, the "decision making process" has grown increasingly... how shall I put it diplomatically... shite in recent months, to the extent that I know of at least one user who has retired over the matter, and another that no longer has anything to do with the wikiproject. In any case, the meat of this change can easily be opted out of, and I'll be happy to solve (or provide code to solve) any substantive problems. --WFC-- 23:19, 22 July 2010 (UTC)Reply
I honestly think the matter could be resolved by displaying the country name as a three-letter FIFA trigramme rather than the entire country name. I'm not saying to remove the name entirely, because I understand that is a violation of WP:MOSFLAG; just display it as the widely-recognized 3-letter code, and shrink the nationality column so that the integrity of the squad template isn't compromised by forced row-splits. --JonBroxton (talk) 23:26, 22 July 2010 (UTC)Reply
That idea has been discussed at WP:FOOTY before, and always rejected. The Democratic Republic of Congo is a case in point. I sure as hell wouldn't know what "COD" means unless I was told.
In any case, the icononly parameter ensures that users who disagree with this change are not forced to put up with it. If preferred, articles can use the |icononly parameter, and come up with their own key. However, now that it is possible to use this template and comply with the manual of style, it's a reasonable expectation that articles meet it one way or another. --WFC-- 23:32, 22 July 2010 (UTC)Reply
WFCForLife speaks true. I initiated the change because when the non-compliance with MOS ("country names on first flag use") is pointed out, most editors are at a loss on how to comply with the MOS or defend the non-compliance. WP:FOOTY and certain partisans enforce the use of the Football squad templates on the football articles; however, most editors are unfamiliar with template markups, and any discussion about MOSFLAG somehow gets derailed into "remove the flags.... hell no!" rants irrelevant to the topic at hand. It is all easily solved with the above change. Whatever it is, the project is supposed to present information accessible to all and flags-only displays can confuse those with lesser knowledge of flags (we are not expected to be vexillologists) or have issues with visual abilities (e.g. color blindness); even the flags of Northern Ireland and England are too close in appearance to confuse. Initials are also discouraged for the same reasons (unfamiliarity with the ISO country codes). "Prettiness" has less place than clarity and accessibility. Jappalang (talk) 06:21, 23 July 2010 (UTC)Reply

I have updated the documentation to explain the change, and also to more widely publicise the fact that it is possible to hide the note. Please can an admin action the following request:

{{editprotected}} Please:

  1. Replace the code in {{Football squad start}} with the code from {{Football squad start/sandbox}}
  2. Replace the code from {{Football squad mid}} with the code from {{Football squad mid/sandbox}}
  3. Replace the code from {{Football squad player}} with the code from {{Football squad player/sandbox}}

The combined effect of these changes can be seen at Template:Football squad player/testcases.

Changes:

  • To shorten the header from "nationality" to "nation". Discussion needs to be had on the longer-term heading, but nationality is intolerably long if the |icononly parameter is used.
  • If icononly is used, the nationality parameter is centered, to reduce the increased whitespace between the flag and a player's position.
  • If icononly is not used, the nationality parameter remains left aligned, because the manual of style correctly stipulates that where flags are used in a table, they should all line up. Unless every player is from the same country, this cannot be guaranteed with centre alignment

Regards, --WFC-- 00:38, 23 July 2010 (UTC)Reply

This is one of the most absurd things I've ever seen done on Wikipedia. I don't see any reason to continue contributing here if you people think shit like this improves anything. I don't even know what to say. It's unbelievable. Eightball (talk) 05:47, 23 July 2010 (UTC)Reply

Care to expand on that? --WFC-- 06:16, 23 July 2010 (UTC)Reply
I think what he's trying to say is "this change to the Fs template makes every single page about every single soccer team across all of Wikipedia look like complete and utter crap, and we should go against WP:MOSFLAG in this instance because sticking to the letter of the guideline renders squad templates almost entirely unreadable". This is a prime example of an instance where WP:IGNORE applies, for the good of the WP:FOOTY wikiproject as a whole. Does that about cover it? --JonBroxton (talk) 07:07, 23 July 2010 (UTC)Reply
I know from experience that you are a reasonable person. Please consider rephrasing the above (and feel free to delete this paragraph if you do). You have legitimate points, but the forcefulness of that post only serves to strengthen the position of those who disagree with you. --WFC-- 07:31, 23 July 2010 (UTC)Reply
I am a reasonable person, but I'm not going to rephrase anything because I feel very, very strongly about this and my words were very carefully chosen to properly capture my feelings about this. I honestly think that this is one of the most misguided blanket changes I have seen here in years. Firstly, the fact that you intentionally kept this from the wider WP:FOOTY community and discussed it between yourself, Jappalang and a couple of others here and on your talk pages indicates to me that you were trying do to this "on the sly" without the participation of the wider wikiproject for whom you seem to have quite a bit of distain. I, and many of the others who would have wanted to contribute to this discussion had we known about it, work VERY hard on producing pages here which are accurate, informative, useful, aesthetically pleasing, and conform as best they can to the spirit of the Wiki guidelines. The latter os the most important thing; WP:MOSFLAG is a GUIDELINE, not a CARVED IN STONE RULE, and as such can be manipulated to best suit the needs of an article when said article is genuinely attempting to be accurate, informative, useful, and aesthetically pleasing. This is one of those occasions. There was absolutely nothing wrong with the FS template as it stood; certainly nothing that required such a drastic change to its layout. The bottom line is this: I for one don't want all the pages I maintain looking like crap as a result of a discussion in which I was not involved, and I'm sure a LOT of editors will agree with me. --JonBroxton (talk) 07:47, 23 July 2010 (UTC)Reply

I think what Eightball is trying to say is that there is really no need for a nationality header when you can simply hover above the flag which reveals the players nationality. Moreover, inclusion of the "Nationality" header has made the template look awkard and unorganized, in where nations with long names like "Azerbaijan" overshadow and skew the alligement of smaller nations such as "Iran". Overall, this edit seems like a hurried and unorthodox attempt to solve a problem which never existed. As such, i beleive more creative ideas, such as hyperlinking the flags to the country's wikipedia page, seem like simpler ideas to solve the nationality problem, if there ever were one.. Kasperone (talk) -- 12:04, 23 July 2010 (UTC)Reply

In answer to the accusation that this was hurried, discussion started four months ago, work started several days ago, and complaints started today. That said, I cocked up with the "Nationality" header. That looks bad in several circumstances, most notably in conjunction with "|icononly". This second set of changes will address that.
Even if you remain opposed to the initial change, it is imperative that the second set of edits to go through. They fix the above problem, and undeniably improve on what is currently in place, even if you think what was in place was better. I recommend that the admin dealing with this does so while explicitly expressing no prejudice to whether or not the previous changes should remain. Given that the first set of edits happened, this latest request is necessary maintenance, and that maintenance is entirely separate from the discussion on whether we should keep these changes. --WFC-- 07:31, 23 July 2010 (UTC)Reply
I agree completely with Kasperone, JonBroxton and Eightball. The new design is horrible to look at and absolutely nothing is gained by speling out the entire name of the country. And if you really want to be a bureaucratic pain in the ass about it, WP:MOSFLAG states that "the name of a flag's country should appear adjacent to the first use of the flag icon", meaning the current layout is also against its rules for any club which has more than one player from the same country (e.g. around 100 percent of them). Well done. The four months which have allegedly been spent discussing this must have been very fruitful. Timbouctou (talk) 07:53, 23 July 2010 (UTC)Reply
I disagree entirely with the notion that a second set of changes will fix everything. You're working under the assumption that the Fs template needed "fixing" in the first place, which I don't think it did. Any fix you make will simply make it a little less awful than it is now, not actually make it better. For the benefit of the project you should restore the original Fs template and take the discussion on whether it needs changing to WP:FOOTY, where veteran editors and others who care about soccer articles on Wikipedia can actually have a chance to air their views on the matter. --JonBroxton (talk) 07:56, 23 July 2010 (UTC)Reply
Fine. I've disabled my edit request, meaning that the "Nationality" header in its entirety will stay for a longer period of time than it otherwise would have. Congratulations.
All I did was enhance Jappalang's work,, make the edit request, and then promptly make a second edit request when I realised that there were teething problems. Criticise the process by all means. But if the remark that I deliberately acted in bad faith isn't retracted, I will take the matter further. --WF C-- 08:14, 23 July 2010 (UTC)Reply
No-one is saying you acted in bad faith (I'm not even sure what that means). I'm saying that a decision was made, and that decision was apparently made after intentionally excluding the majority of the members of WP:FOOTY from the discussion process, as you yourself insinuated above. I'm absolutely sure you all absolutely had the right intentions (WP:GOODFAITH) and thought the changes were making the template better. My opinion is that the template was made immeasurably worse by the change; that's not a statement that you "acted in bad faith" - it's a statement that IMHO the good faith change was misguided. And so we discuss it further and hopefully we can all come to a mutually acceptable way forward. --JonBroxton (talk) 15:45, 23 July 2010 (UTC)Reply

Reverted

edit

I've reverted the changes until this issue has been discussed by a wider group from WP:FOOTY. I think it's clear that there are several issues with this, not least the fact that it severely disturbs the layout of player squads. пﮟოьεԻ 57 08:55, 23 July 2010 (UTC)Reply

As someone who has previously expressed opinions on the matter, I suggest that you re-revert (or implement the interim solutions I proposed), until an uninvolved administrator has had a look. Regards, --WFC-- 09:07, 23 July 2010 (UTC)Reply
I think you are confused - I have not commented on this issue, and was only drawn here after seeing several comments expressing surprise about a decision made away from most members of WP:FOOTY, and which is not liked by most people commenting there (currently two in favour and six against). If you are referring to the 2008 discussion that I participated in, that was regarding the removal of flags from the template, rather than the issue of adding country names alongside. пﮟოьεԻ 57 09:20, 23 July 2010 (UTC)Reply
I am the admin who made the changes to this template. At the time consensus appeared to support the changes. However it is now clear that this change is controversial and needs further discussion to find the best way forward. WFC: thanks for your work with this template; please do not lose heart that this has met with opposition but continue to discuss the issue in a constructive way. — Martin (MSGJ · talk) 09:40, 23 July 2010 (UTC)Reply

RFC: Changes to Football squad templates to comply with WP:MOSFLAG

edit

The Manual of Style (MOS) specifically instructs that on the first time a flag icon is used, we should name the country (WP:MOSFLAG#Accompany flags with country names). The reasons are for clarity and accessibility. The Football squad templates ({{fs start}}, {{fs player}}, {{fs mid}}, and {{fs end}}) are used in association football (soccer, hereby referred to as football) articles. The project enforces the use of the templates; no article is to be without it. The templates do not allow the naming of flags. A proposal was tabled to modify the templates to name the flags on default with an option to disable the name.[2] It was implemented two days later after discussions and tests.[3] Three WP:FOOTY members arrived to protest after implementation, leading to a reversion of the change[4]. This RFC is to ask for community opinions on whether the initial change to the templates (naming the flags on first use) should be reinstalled or for any alternative methods to ensure compliance with MOS. Jappalang (talk) 21:36, 23 July 2010 (UTC)Reply

To see the proposed version (that was reverted), see Template:Football squad player/testcases.

Starting the motion, I have read the discussion above and found the reasons for opposition lacking.
Against the guidelines? It is not, read Accompany flags with country names again.
The guideline stated "The name of a flag's country (or province, etc.) should appear adjacent to the first use of the flag icon, as not all readers are familiar with all flags. Nearby uses of the flag need not repeat the name."
It does not state in any way that you can name only the first use and not subsequent ones ("need not" is not the same as "must not" or "should not"). The current (reverted to) scheme (icons only) violates the MOS (it did not name the first use), whereas the proposed scheme is in compliance, coming with an option to render subsequent uses of the flags nameless.
We can have the country name beside every flag icon, but we should not have flag icons in an article without naming them at least once (on each first use).
Why text is necessary:
  • Not everyone is well versed with flags, and some of us are impaired in our vision, notably color-blindness. These lead to confusions when confronted with the issues below.
  • Some "nations" use very similar flags, e.g. Monaco and Indonesia (  , Vietnam and Morocco (  ).
  • The flags of Ivory Coast, Ireland, and Italy use the same design with similar colors and can confuse those with lesser knowledgable of flags or under certain lighting conditions (   ).
  • When reduced to icon size, thus reducing details to little dots and smudges, one flag can be easily mistaken for another similar one: e.g. flag of Northern Ireland to the flag of England (  ), New Zealand to St. Helena to the Virgin Islands (   ), Singapore to Indonesia (  , Soviet Union to China (  ), Niger to India  ), Jordan to Palestine (  ). Readers should not be expected to pause and study intently the flags to identify them.
Tooltip-like implementation
A reader who mistakes a flag of one body for another for the above reasons would not bother to hover over the flag (very few would have a reading habit of moving their cursor over every word/object they read if ever). Full names in text clearly identifies the flags to their nations without confusion.
Conclusion
By making readers mistake one flag for another (and consequently one player's nationality or representation), the project is certainly causing them a disservice. The displays have become inaccurate and useless in their purpose.
From what I see so far, advocating for icons boils down to an appeal for aesthetics at the cost of accuracy and usefulness. I do not believe we should allow the call of "Looks pretty. Flags only please." to trump "Present information with greater clarity to everyone. Identify the flags." when it comes to building an encyclopaedia. The assumption of bad faith above rankles; when one brings a change to the table, it is directly at the talk page of the article concerned first. I had not expected a valued template to be not even watched at all by the project that is heavily enforcing its use on involved articles. This involves the MOS and as such, the RFC is started to gather wider community opinion instead of a single Wikiproject. Jappalang (talk) 21:41, 23 July 2010 (UTC)Reply
  • There was opposition to the first attempt to implement this, as the unwieldy "Nationality" header distorted the table for any club without Bosnian, Congolese or Northern Irish players. I quickly realised the problem, and quickly moved to deal with it. I deliberately made the requests at a time when European editors were least likely to be effected, on the grounds that many American editors edit between 0:00 and 4:00 UTC, and therefore that any teething problems could be swiftly remedied. Sadly, this did not happen. Opposition was needlessly exacerbated by the fact that while I was trying to correct it, our crats and admins were busy discussing how underworked they are. In six hours nobody had bothered to look at it, and as a result I was public enemy number one. As far as I'm concerned, editors there who claim to be committed to the smooth running of the project cocked up and hung me out to dry yesterday, and should be admonished for that. --WFC-- 22:10, 23 July 2010 (UTC)Reply
  • While I've been here a relatively short amount of time, discussion on the rights and wrongs of whether we should have flags, and if so, whether they should be expanded, has been going on for years at WT:FOOTY. The consensus has always been that we must represent nationality somehow. Apart from those whose attitude is "to hell with flag policy", there was also broad acknowledgement that ideally we needed to try to address the problem of non-MoS compliance. Therefore, that is exactly what we have tried to do here. There was no need to consult WP:FOOTY again; the correct process was to find a solution, see if it worked, and then discuss the way forward if for some reason it didn't. As an aside, the only legitimate aesthetic complaint about this template is its implementation. On the concept of expanding on country names there is simply no case to answer. --WFC-- 22:10, 23 July 2010 (UTC)Reply
  • Despite the level of hostility I've received over the matter, I have continued to work on trying to iron out the problems, and the current state of affairs can be seen here. --WFC-- 22:10, 23 July 2010 (UTC)Reply
I've created a simple wikitable that might work just as well as a squad list. You can find it here. If anyone has any ideas for other columns that could be added or any way that the table could be streamlined, do let me know! – PeeJay 22:48, 23 July 2010 (UTC)Reply
PeeJay, can you do a version of that where we have ENG instead of England, and GK instead Goalkeeper etc., just to see what it looks like? --JonBroxton (talk) 22:52, 23 July 2010 (UTC)Reply
How's this? – PeeJay 23:03, 23 July 2010 (UTC)Reply
  • I honestly think the most sensible way around this is what I mentioned before; to use the internationally recognized FIFA trigramme in place of the country name. That way, you keep the flag image that so many people want, you have an abbreviated country name next to the flag to maintain compliance with WP:MOSFLAG, and you have fixed column widths that don't cause any of the brain-melting row misalignments that the original changes gave us. Adding three capital letters to a row of text will not cause any undue problems, and will fix all the MOS issues that seem to be driving this whole discussion. (Although, again, I feel compelled to point out that MOSFLAG is a *guideline*, not a *rule*, and as such can be ignored if doing so will be more beneficial to the article(s) in question than following it). --JonBroxton (talk) 22:50, 23 July 2010 (UTC)Reply
USA is informative enough, and the likes of ENG and WAL would be tolerable. But the problem with that is that there are ambiguous ones such as ISL and NIG, and outright bizzare ones such as COD being used for a practically landlocked nation. --WFC-- 23:02, 23 July 2010 (UTC)Reply
True, I always thought that one was a bit fishy ;) I think the obvious ones do outweigh the few that are peculiar though: I mean, ENG, SCO, WAL, USA, FRA, ITA, GER, RUS, JAP, BEL, NED, DEN, SWE, NOR, AUS, CAN... I don't see much potential for confusion there. --JonBroxton (talk) 23:05, 23 July 2010 (UTC)Reply
Actually, it's JPN, not JAP. — Andrwsc (talk · contribs) 23:08, 23 July 2010 (UTC)Reply
  • I agree that using country codes and flags is a straightforward solution that will work for most articles. Most of the affected pages use wiki markup like {{flagicon|XYZ}} now, which would simply change to {{flag|XYZ}}. The end result would eliminate any confusion between   IDN and   MCO, but not require a significant amount of additional space for this table column, and would obviate the need for an awkward legend table. I do not see why   ISL or   NIG are ambiguous, because of the generated wikilink to the country article, nor do I see why   COD is any more awkward than some more well-known codes. — Andrwsc (talk · contribs) 23:06, 23 July 2010 (UTC)Reply
    • I quite agree. Using country codes seems like a reasonable compromise. – PeeJay 23:08, 23 July 2010 (UTC)Reply
      • I don't want to be seen as averse to compromise here. But the issue with triagrammes is that they're no use to someone reading plain text. When you pipe a link, you are usually doing so to get rid of unwanted precision (e.g. Don Cowie (footballer)Don Cowie). If you print off a page, and on that page there is a flag that you don't recognise with "COD" next to it, are you any the wiser for the triagramme? --WFC-- 23:14, 23 July 2010 (UTC)Reply
So what happens when I'm looking up a squad list on my iPhone or printed out, and I can't roll over the flags I don't recognise and can't click on the trigrammes which aren't obvious. You show   COD to someone in the street. Do you think they would know what country it was? 91.106.116.29 (talk) 23:16, 23 July 2010 (UTC)Reply
Exactly. The vast majority of readers gain nothing from seeing that, whereas the vast majority of readers can read "Democratic Republic of Congo". Knepflerle (talk) 10:13, 24 July 2010 (UTC)Reply
Thanks for your opinions. I'm asking this openly because the combination of the last two comments looks extremely bad. Are you a registered user? If so, would you consider using that account? Regards, --WFC-- 23:20, 23 July 2010 (UTC)Reply
No, I'm not a registered user. I came across this discussion a few days ago via the previous links originally at the Manchester United FAC and then the Football project page. 91.106.116.29 (talk) 23:24, 23 July 2010 (UTC)Reply
I'll briefly repeat the points I made at WT:FOOTY: Stand alone flags are absolutely a bad idea, as the ability to rollover for further information is not always available. I do however believe that FIFA trigrammes are not a bad option. MOSFLAG indicates that a country name should appear, but does not state limits on how the name should be rendered, so an established abbreviation is not explicitly forbidden. In a footballing context the FIFA trigrammes are well established and standard abbreviations, so to my mind would not be in violation of MOSFLAG and should be permissable. AJCham 00:44, 24 July 2010 (UTC)Reply
  • To tell you the honest truth, nothing good will come from this discussion. I don't believe for one second that having only flagicons is confusing readers, and I think quite a few people share this same view. Furthermore, I don't believe the motion to change the squad template was as a result of editors reading pages and saying, "wow, these flagicons are really ambiguous." I think someone discovered that the pages conflicted with the Manual of Style and set about try fixing this. The problem is, there's nothing to fix. There's no perfect solution to the problem we have. First off, I'd like to address those who say nationality is not important. They are quite spectacularly in the wrong. They simply do not understand how important nationality is in football, especially in leagues that restrict how many non-native players can be on a team, but also because football is notably a worldwide game. I'd also like to touch on the perceived ambiguity of flags. I don't believe that this is anywhere near as widespread of a problem as some of you think it is. The situations in which you could not easily discover the country an unknown flag represents are shockingly rare, and possibly even nonexistent. At worse you'd need to click on a player's name and view their page. And while trigrammes are a decent compromise, they really only help in situations where flags are quite similar, i.e. Monaco vs Indonesia. In most of these cases, both the team context and player's name should almost always end any confusion. A situation like the Democratic Republic of the Congo, where the trigramme is COD, including that abbreviation is almost entirely pointless.

    And finally, the original edit: full country names. This is simply unacceptable to me. You people get so caught up with adhering to your made up policies that you forget to take into account that aesthetics really do matter, and it is much much nicer to read a well-formatted list than a giant block of text (another problem with Wikipedia: the unwarranted war against tables. but that's for later). I've tried to lay down a well-reasoned argument for keeping the squad list as it currently stands, and while I've done the best I can without wasting my life away on a internet argument, obviously there are points that I've missed. Feel free to address these. However, if you simply reply with something to the extent of "BUT MOSFLAG SAYS," you just don't get it. In a discussion like this one, try to stop blindly quoting wikipolicy and actually support your stance once. And finally, WP:IGNORE. Use it. Eightball (talk) 06:49, 24 July 2010 (UTC)Reply
"In a discussion like this one, try to stop blindly quoting wikipolicy and actually support your stance once." - read Jappalang and AJCham's for a full and correct explanation of why MOSFLAG is used. Knepflerle (talk) 10:13, 24 July 2010 (UTC)Reply
"First off, I'd like to address those who say nationality is not important. They are quite spectacularly in the wrong. They simply do not understand how important nationality is in football, especially in leagues that restrict how many non-native players can be on a team, but also because football is notably a worldwide game. " So please explain why it is relevant to an article on Macclesfield Town whether their reserve left back is English or Welsh? What is the relevance to a player's membership of his squad that, despite having lived in England all his life, he once played for the U18 team of the country that his grandmother was from? Why should Wikipedia take a position on the nationality of a player who has a complex background, especially if he has no real likelihood of ever representing any of the national teams for which he might be eligible? Why should we include a field that invites vast numbers of unsourced claims for personal information? By all means have your opinion on the relevance of nationality in this template, but have enough respect for those who think differently to avoid phrases like "They are quite spectacularly in the wrong". Kevin McE (talk) 09:20, 24 July 2010 (UTC)Reply
Yes, those who think nationality is not important ARE in fact spectacularly wrong. There is virtually NO website out there dealing with fooball and football players which DOES NOT list their nationalities, and they are almost always indicated by flags or combinaton of flags and country names. Saying that "Wikipedia is taking position on this" is very misleading. It's not as if we're insisting on a parameter which is otherwise irrelevant in the world of football (as would be the case if we insisted on including the color of each players' eyes or his penis size). On the other hand, wheher a club has players who have been capped at international level IS relevant information for that club's article and excluding it would hardly help any reader. Claming that it should be excluded just because there is a very small number of players who are eligible for more than one national team would be a extreme overreaction. Once again, Wikipedia is NOT "taking position" by reiterating a well known fact which can be referenced and checked against a plethora of secondary sources. Wikipeda IS taking position when an editor says that "he has no real likelihood of ever representing any of the national teams for which he might be eligible". Who do you think you are exactly and why do you think anyone should care about your opinion? Wikipedia is here to present facts, and international careers of professional footballers, as well as ther eligibility fr a particular national team, is a pretty relevant fact in the world of this particular sport. Whoever thinks otherwise knows nothing about football. Period. I know some of you can and will accuse me of not being tolerant, but hey, democracy and tolerance DOES NOT include allowing the decision-making process to be dumbed down like this, and I refuse to "tolerate" such ignorance in the very place whose purpose of existence is to reduce it. Timbouctou (talk) 20:03, 24 July 2010 (UTC)Reply
" Who do you think you are exactly and why do you think anyone should care about your opinion?" Anyone who asks a question like that in serious discussion loses all right to be taken seriously. Kevin McE (talk) 10:31, 25 July 2010 (UTC)Reply
What I meant was why should our readers be constrained by anonymous editors' opinions when the purpose of Wiki is to present facts. I, as a reader of articles, couldn't give a toss about any editors opinion whether player X is talentd or not or whether he plays for Wales just because his grandmother hails from Cardiff. The fact that a player had appeared in international football is not something we can present or not depending on our (and who are we if not a group of anonymous amateurs with varying degrees of interest in the topic) understanding whether this piece of information should be omitted or not. I'd be hard pressed to find a website dealing with this topic which DOES NOT list players' nationalities and it seems Wikipedia is the ONLY place on the internet which is so perplexed with the notion of national teams in world football. So yeah, anonymous amateur editors (who more often then not tend to think that being constructive is second to being polite) have no place deciding about this for our readers. As for things to take seriously, I would hardly put idiotic debates about WP:MOS which go on for several months in my top 1,000 Things to Take Seriously list. Hundreds of "discussions" such as these are precisely the reason why people refuse to take Wikipedia seriously. Timbouctou (talk) 11:53, 25 July 2010 (UTC)Reply
While I disagree with your last two sentences, you otherwise make some very good points.
Strangely we agree on quite a lot. I completely agree with you that nationality is important. That's a long established principle on WP:FOOTY, and one that I am certain will never change. I'm 95% sure that we will never achieve consensus among editors to remove flags altogether. I'm at least the third editor to say this now, but going there again will achieve nothing. I also agree with you that the triagrammes are not helpful, except I'll go further and say that they are Euro-US centric. On that point, we disagree over whether   alone is enough, but clearly we do agree that IF there's a problem with the flag alone,   COD is not a solution.
We'll have to agree to disagree on whether we need the full country names or not. But for the reasons I have outlined above, I believe that there are three feasible outcomes to this discussion:
  1. 1. We keep the flags as they always were, on the basis that it's worth ignoring the MoS.
    2. We introduce a change that introduces the full country names, on the basis that it isn't.
    3. We start to encourage the use of a key, because we need to abide by the MoS but altering the table looks rubbish.
If consensus is for the first option, at least this RfC will give football editors something concrete to cite when challenged on the MoS in future. --WFC-- 07:55, 24 July 2010 (UTC)Reply
Out of those three options, I think only #1 is viable. #2 would cause a lot of problems, due to the lack of lines between columns possibly making it look like the country name is part of the player's name. Especially long country names would also be a problem. As for #3, I don't think using a key would be a good idea; with multi-national squads these days, the key could end up being as long as the squad list itself. I definitely think using the FIFA trigrammes is the best idea, but out of the three WFC has posited, #1 is the best IMO. – PeeJay 08:52, 24 July 2010 (UTC)Reply
I think my opinion on option #1 is clear. That said, I genuinely think that flags alone are more useful than flags plus triagrammes. --WFC-- 09:11, 24 July 2010 (UTC)Reply
Option 1 is simply not viable. The major reason for this are the information accessibility reasons laid out in detail here, but there is also the minor problem, of interest to some editors, that the people who choose which articles reach FA status may decide that they cannot promote an article which contain tables of information which isn't readily accessible to many users (especially when it could be made universally accessible so easily). I would guess that all editors on WP:FOOTY would hate to see an otherwise excellent article fail FAC just for this rather insignificant aesthetic issue, but as long as the tables stay as they are we're just hoping none of the judges notices and objects. Jappalang noticed and raised the issue atWikipedia:Featured_article_candidates/Manchester_United_F.C./archive5, so I think we can assume that other reviewers will spot this in future. If we work on a change now, then the FAC judges will have no reason to object and the articles will get the status they deserve.
I'd like to add that we should be making this change for the benefit of the readers who currently can't access the information in these tables, rather than for the reasons of FA criteria, but working towards meeting the criteria normally benefits the reader - and in this particular case it is clear that it will. Knepflerle (talk) significantly redacted and expanded, 12:01, 25 July 2010 (UTC)Reply
I agree with everything what Eightball said, including his feelings about the futility of this discussion. An earlier decision at WP:FOOTY about lists of notable footballers had already made me semi-retire from the project and I see this as just another continuaton of the longstanding tradition of fixing non-existent problems. Having said that, I might add that I too think trigrammes would be a good compromise, probably in conjuction with a short note explaining what they were embedded in the template with a link to the entire list. If country codes are good enough for FIFA, the sport's top governing body on planet Earth, I don't see why they're not good enough for our articles. As for the statement that they are "Euro-US centric", I don't understand what that means actually. Do trigrammes have ideological inclinations? Are symbols of chemical elements euro-centric too? Should we care even if they were? I think not. If one doesn't know what COD means perhaps it's a good opportunity for one to learn by clicking on those three letters to find out. Also, the current note on nationality should be re-phrased, as "non-FIFA" nationality is a pretty vague concept. The note should simply state that flags represent players' primary national team as defined by FIFA eligibility rules, not their actual citizenship(s). Timbouctou (talk) 08:45, 24 July 2010 (UTC)Reply
Trigrammes with an auto-generated key really wouldn't be so bad an option, but the inclusion of the key would have to be mandatory in this case. Knepflerle (talk) 10:13, 24 July 2010 (UTC)Reply
"Euro-US centric": nearly all of the European Union ones are useful, as are the US, Canada and Mexico. On the other hand, a reasonable proportion of African, Middle Eastern, Carribean, Asian and Oceanic countries are completely useless. I'm sure it isn't intentional, but it's an issue nonetheless. Given that these countries have fewer players, it's if anything more important to be able to communicate their nationalities, because a high proportion of players from these nations playing overseas will be international footballers. --WFC-- 09:11, 24 July 2010 (UTC)Reply
So you're saying trigrammes are not Euro-centric, but readers of the English Wikipedia are as little Johnny from 3rd grade may assume that ENG stands for England but has no clue that CIV sands for Ivory Coast? (I think we can safely assume that Ivorians reading Wikipedia probably are aware of their own country's trigramme, as I'm pretty sure every Serbian knows what SRB means.) The Euro-centricity of Wikipedias readers always was and always will be an issue present in any article about any topic. And that is the very reason why we SHOULD use standardised country codes if such exist. And hey - they actually do exist and are listed here. On first glance, I'd say some 80 percent of those codes consist of first three letters of the country's name in English. Assuming English Wikipedia is intended to be used by speakers of English, most of these codes should be pretty intuitive for a reader to decypher (yeah, somebody may mistake NGA for NIG, but it's not a problem a click on the trigramme won't fix). Even bloody Panini albums sold to children all over the world use FIFA trigrammes for at least the past 30 years. Timbouctou (talk) 20:18, 24 July 2010 (UTC)Reply
Why use SRB and hope that 95%, 98% or 99% of readers understand it, when we know 100% of readers can read the word "Serbia"? Even if it is a matter of only a few readers who don't understand it (and for some of the countries, I doubt it will just be a few), what are we gaining by using the trigramme that really justifies not using the word? Knepflerle (talk) 21:48, 24 July 2010 (UTC)Reply

I can't add anything that User:Jappalang and User:AJCham haven't already said, but something needs to be done.

WP:MOSFLAG may be annoying to some, but it exists for very good reasons - it's there to make sure that all readers have access to the information in articles, including those who don't use the same method of browsing as you are used to. Aesthetics will always be secondary to conveying information: editors prioritising the former over the latter must be strongly reminded that they are editing an encyclopedia, not a series of wallcharts. Encyclopedia articles are there primarily to hold and convey blocks of information, not to be stapled to the wall as interior décor. And making nice wallcharts is an extremely poor excuse for excluding information from article to people who don't know the flags of hundreds of countries, who don't use a mouse, who access the information from a phone, who use text-only browsing, who are colour blind, who don't know their STP from the MNE.

The only acceptable solution in the long run is including the country names; however, this can be done much more elegantly than it was in the first attempt. As Glamorgan_County_Cricket_Club#Current_squad shows, judicious use of column lines can improve matters significantly. We can also consider abbreviating some of the particularly long country names: Dem. Rep. Congo is still more evocative than COD, but takes up half the space. Knepflerle (talk) 10:13, 24 July 2010 (UTC)Reply

Hey, I've got a great idea. How about using DR Congo instead of conjuring up stuff which is "more evocative" than codes designed to be evocative in the first place? And btw how would you solve Bosnia and Herzegovina? Is "Bos. & Herz." more evocative than "BIH" for the idiot that we perceive our average reader to be? How about Trinidad and Tobago? "Trin. and Tob." or "TRI"? What about United Arab Emirates? Would you rather opt for "Un. Arab. Emr." or UAE? What about Saint Vincent and the Grenadines? Do you honestly think someting like "St. Vin. & the Gren." is "more evocative" than simply "VIN"? Timbouctou (talk) 20:28, 24 July 2010 (UTC)Reply
DR Congo would be fine too, and is more likely to be understood than COD. UAE is widely used in English anyway, and yes I belive that Bosnia and St. Vincent are far more recognisable to far more readers than BIH and VIN. I still expect there's a way to format the table so that the full country names can be used, and if not, we can then discuss suitable short forms that are still more recognisable than these trigrammes. Knepflerle (talk) redacted 22:03, 24 July 2010 (UTC)Reply
I think the whole problem is in the ordering of columns. I wouldn't mind having full country names next to flags if they were in the far right column of the squad list, provided that we scrap the Fs Mid parameter for good. That should be more aesthetically pleasing while at the same time conforming to MOS. Why couldn't we have columns ordered so that (from left to right) player numbers come first, followed by position abbreviation, then player name, then flag and country name. I still think FIFA trigrammes would be a better choice even in that kind of layout as I still don't see the point in inventing new shortnames when there are already three-letter codes devised and used exactly for situations like these by the sports top governing body, exactly the same way symbols for SI units are used. As long as there is a note on top of the template saying what those codes mean and why we chose to use them it should be fine. Also, date of birth or at least current age would be a useful addition to the template. Timbouctou (talk) 12:20, 25 July 2010 (UTC)Reply
Looks good to me. The "Position" column could be narrower, it seems like a waste of space this way. Perhaps naming it "Pos." could fix this. Also, a parameter for shading every other line could be useful to facilitate reading squad lists with large number of players. Also, an "age" column would be a nice addition, preferably inserted between name and nation columns, but I suppose this would have to be debated more and it would require additional input parameters. As for captaincy, icons or abbreviations would be a happier solution (let's say something like "(c)" for captains and "(vc)" for vice-captains). These should also be added to the table key. I think we're moving towards a solution here. Thanks for helping out Oranje.Timbouctou (talk) 12:28, 26 July 2010 (UTC)Reply
Timbouctou's suggested ordering sounds sensible to me and will display better, and Club Oranje's tables which include the country names are a really good start. Both the single and double column variants are already better than what we currently use. I've got a few comments:
  • Captaincy should be marked with text rather than icons (same issue as with the flags really; icons aren't always displayed, don't work in text-only etc.). Using (C) and a key would suffice, but I think in the current layout we probably have room to use the full word "Captain" (with link to the relevant article), seeing as we also allow comments like (on loan from Amazing FC) which are much longer. Might it be worth creating a new column for these notes about captaincy and loans, however?
  • If we're going to include the age, this should probably be automatically calculated from a template which contains the date of birth for each player otherwise it will become quite a maintenance effort, but that's certainly feasible. It should ideally be toggleable though so that it doesn't display on tables where the players' birthdates haven't been entered.
  • As I've mentioned in the section below, the header about "FIFA nationality" should also be changed to a more accurate wording but we should discuss that separately there (but now is a good time to discuss it).
  • How do people feel about grouping the players by position then squad number, instead of just squad number?
Thanks and best wishes, Knepflerle (talk) 13:52, 26 July 2010 (UTC)Reply
I think, if we are moving the columns around, we should move the "Position" column to the right of the "Name" column. I don't think we should add any more columns though, as the table is already wide enough as it is and may not display very well on non-PC browsers. I'm not really a fan of an "Age" column anyway, since it's not particularly relevant to the club. Finally, I prefer sorting by squad number rather than sorting by position. It's a more natural sorting method, IMO. – PeeJay 16:32, 26 July 2010 (UTC)Reply
The re-ordering columns make the template similar to the "National football squad" series templates (no doubt next month's MOSFLAGS target) used on national team and tournament squad pages - and on that basis I'd quite happily accept the addition of age (or DOB/age) as calculating template. On that basis I'd also support a proposal to make the list full width single column, and would leave the position field after the number as an abbreviation so as to not distract from the most important information in any squad list... namely, who is in it!. As for ordering of players, what people may prefer would depend on whether they are looking to see who wears number 17, or who are the clubs midfielders. Personally I think positions are a little arbitrary. Gareth Bale was in my Fantasy side as a defender last year, this year he is a midfielder and gets me less points if he scores, even if he is playing at left back.--ClubOranjeT 00:56, 27 July 2010 (UTC)Reply
Reading a few of the answers above suggests that this change is only being done to adhere to WP:MOS. I seriously disagree. Using Marseille as an example, do you think most readers will look at the squad and know straight away what nationality all the players are. They have players from Senegal, Burkina Faso, Ghana, Cameroon all with similar looking and similarly coloured flags, add Gabon and Togo whose flags I wouldn't have much conviction of knowing. Why is Wikipedia expecting readers to know all the flags. The squad list at the moment does not show nationality, instead shows what flag might be flying over a ground when a player plays internationally. It's alright if I'm browsing on the web to try get some fairly quick guidance on what nationalities the players are, but I mostly browse on my iPhone and I don't have that ability to check there. The current system appears to be style over substance to me. 91.106.115.244 (talk) 11:27, 24 July 2010 (UTC)Reply
Exactly, and there will be many, many other readers in the same position. The primary objective is to make sure everybody gets the relevant information easily; after we've achieved that we can tweak it to make it look more aesthetically pleasing - but that is the order of priorities. The MOSFLAG guidance exists to try and prevent this sort of discussion from being rehashed time and time again, by highlighting the problems icon-only data can cause. That it is part of MOS is by-the-by: the issues would still exist and be the same.
I firmly believe that a squad list with delineated columns and country names (with abbreviations for longer names) can be a suitable solution for these articles. Knepflerle (talk) 12:26, 24 July 2010 (UTC)Reply
Just a note that the call for WP:IAR is misguided in its thinking. IAR is applied sparingly and exists for cases when such a move will improve the project as an encyclopaedia. Making readers confused over flags for the sake of aesthetics does not make this a better font of information. If we should IAR, it should be to circumvent all this discussion (for the sake of building a consensus) and to re-install the proposed change (or some other form with full names of flags on first call). As has been said, aesthetic improvement can come later, and a pretty table/list of players with national team representations can be made with descriptive names of the nations the flag icons represent. The MOS guideline referenced in this case is not simply a rule on styling, it is a call for us to ensure that we can present legible and clear information to the readers, respecting certain visual difficulties as well. Jappalang (talk) 06:18, 26 July 2010 (UTC)Reply
  • I believe that adding the country names would be benficial, since the small icons are not helping to distinguish between similar flags (I just mistook a New Zealand player for an Australian player on one soccer team page I looked at to make up my mind about this). I also understand that having the full name of the countries is just too long to be easily achievable in a smallish template and is not aesthetically pleasing either, so I can live with adding the three-letter-codes, which are clear for most countries and at leat make it obvious that flag + NZL isn't the same as flag + AUS. On an unrelated to this RfC but quite fundamental note, I firmly oppose any use of the "current squad" template at all, since encyclopedias shouldn't be dealing with "current" anythings, and the current squad has no more encyclopedic value than previous years' squads. This is a bad case of recentism and undue weight, and should be removed from all articles instead of being enforced by the project. Squads belong on season articles, tournament articles, but not on general team articles. Fram (talk) 14:40, 26 July 2010 (UTC)Reply

I've updated my local testcases with an attempt at colouring every second line and a couple of other tweaks. Unfortunately I can't make it dynamic on non-supplied parameters, so used squad numbers even/odd for colouring. This will of course produce oddities if the numbers are not consecutively odd/even. I also modified Fs mid to put not make a new column, idea being we could 'bot that out if a changeover to new format occurs. Possible look at width factors for columns - I had it 1000%, but have dropped that out in favour of width-to-suit-per-squadlist. I wasn't that keen on full country names myself initially, particularly when they were in the front distracting from the important information, but with them tacked discreetly on the end I don't mind them.--ClubOranjeT 11:43, 29 July 2010 (UTC)Reply

I was just about to edit the squad list at Arsenal F.C. because I saw that the Flags didn't have names/codes by them as per MOS:FLAG. I thought I'd look into the template and discovered this mess! So here is my tuppence:
As it stands the squad lists break accessibility guidelines and the very reasonable guidelines concerning odd flags at MOSFLAG. I take the point that putting the entire country name looks a bit undesirable, so I would agree with the proposal that the three-letter-codes be used instead. For the argument that COD looks odd, it is no less odd than some of the obscure flags. For that argument that tried to interpret "only put the name on the first instance", they neglect to consider "every row in a table should stand on it's own" (WP:REPEATLINK. Therefore I would advocate the 3 letter code.—User:MDCollins (talk) 14:15, 29 July 2010 (UTC)Reply
I can accept that either   or COD might be enough, should the community reach that conclusion. But the argument that   is insufficient, yet COD or   COD solves everything is inconsistent and utterly unconvincing. --WFC-- 08:24, 30 July 2010 (UTC)Reply

Moving forward

edit

I thought long and hard about whether to start a new heading, but I firmly believe that this is a separate strand of discussion. The above discussion focuses on the merits and otherwise of expanding on flags. Although there has been little discussion in the last 24 hours, I believe that it still has some mileage. In contrast this section focuses on whether or not there is any scope for progress (obviously, what might be considered progress depends on one's point of view).

At the moment there is somewhat of a deadlock, which is understandable given the poor execution of the previous attempt. So let's put it this way. If a prototype is designed that attempts to deal with the concerns over accessibility, while at the same time ensuring that there is no compromise on aesthetics, will all editors agree to compare the two on their merits? It is unlikely that anyone is going to change their view on whether full names are necessary, but my question is whether all editors would be willing to reserve judgement until they see what is on the table?

For the record I will not be involved in that template's development. I feel that I have a lot to offer in the template development department, but I recognise that my involvement in this issue must now be an external one. However, I know of at least one editor who has stated a keen interest in working on a possible solution, if the community demonstrates a willingness to consider his work on its merits. Would people be willing to give it the time of day? Even if we keep flags as they are, I firmly believe that the current template is in need of an aesthetic revamp, and that it is worth doing so while there is a lot of attention on it, so that we can get maximum feedback. --WFC-- 02:06, 26 July 2010 (UTC)Reply

Your RfC has been open for only 3 days. That is simply not long enough to form a consensus decision. Not all users spend half the day every day on WP. An important wide reaching change such as this needs to be given an appropriate amount of time for others to consider and contribute - therwise a change will be made and THEN a whole lot of other users will want to re-discuss it.--ClubOranjeT 05:40, 26 July 2010 (UTC)}}Reply
We can't implement another change until there has been thorough, medium-term discussion. That's crystal clear. But getting a rough idea of whether it's worth trying to reform the template (with or without a change in flags) is a different matter, and needn't take anywhere near as long. Regards, --WFC-- 06:49, 26 July 2010 (UTC)Reply

My hat in the ring

edit

There's been a fair bit of convo here (and if I missed any points I apologise). Just thought I'd offer an alternative solution. Working off this mock template ([User:Rambo's Revenge/fsp2|testcases]]) I believe I've utilised the existing {{flagathlete}} and kept all current functions. It handles flag variations and, taken from code conversation, could use codes where repetitive or very common but for less common flags full names can be used. I believe it is fairly unobtrusive too. I have moved the other attributes to an extra column but I don't believe there is any problem with this. Would be interest in thoughts, or any other probles this might be bring that I could hopefully work around. Rambo's Revenge (talk) 14:55, 26 July 2010 (UTC)Reply

I've never been a fan of {{flagathlete}}. In my opinion, it should be reserved for when athletes are representing their country in an individual sport, whereas in a football squad the flags are merely there to indicate the national make-up of the squad. – PeeJay 16:24, 26 July 2010 (UTC)Reply
I think {{flagathlete}} is useful for simple lists (bullets or numbered) because the leading flags remain vertically aligned, but for tables, I think it's better to keep the flag adjacent to the (wikilinked) country code in a separate table column, rather than with the player name between the flag and the code. I prefer the use of {{flag|XYZ}} for that. — Andrwsc (talk · contribs) 16:30, 26 July 2010 (UTC)Reply
Not wanting to throw yet a other spanner in the works but the a lot of these flags in cases of unclear nationality are decided as far as I can tell on a whim with out regard for WP:RS. I've discussed this before at length and don't want to bog down this process so with that being said I prefer to see the country name and flags than flags alone Gnevin (talk) 17:54, 27 July 2010 (UTC)Reply
Also this has been mentioned a few times but I think an entire new layout like Glamorgan_County_Cricket_Club#Current_squad is the way to go Gnevin (talk) 18:25, 27 July 2010 (UTC)Reply

Status

edit

What's the status of this proposal. Something needs to happen Gnevin (talk) 10:02, 13 August 2010 (UTC)Reply

The fact is that there appears to be no consensus on the core issue, but that there are small positives to take from the discussion. I have attempted to "summarise" this RfC below:
  1. Consensus among most football editors is that nationality is relevant.
  2. There is consensus to continue using this template while this matter is under discussion. Although it is possible for individual articles to use customised squad templates, that would be bad for longer-term maintenance and internal consistency, and should therefore not be done.
  3. There is no consensus to keep or change the implementation of the template. The RfC should close as a no consensus, while encouraging further discussion.
  4. No changes should be made to this template without prior notification at WT:FOOTY.
  5. No changes should be made to this template without either consensus at WT:FOOTY, or from a wider cross-section of the community at WP:CENT.
  6. For as long as there is activity on this matter, it should be assumed that the template will eventualy either be amended to comply with the Manual of Style, or achieve a wider consensus that there are grounds to ignore the Manual of Style.
  7. Imposing deadlines is unlikely to be constructive. Equally, prolonging this discussion indefinitely is not desirable. Editors should attempt to find a compromise between these conflicting factors.
  8. From both sides of the flag divide, there is a feeling from several editors that it's worth exploring a redesign to the template. After exploring the options, it may be that we decide to stick with the current design.
  9. Acceptance or rejection of a possible redesign should be treated entirely separately to the discussion of how we communicate nationality.
  10. A redesign might be a good opportunity to consider whether there is any other information worth including in a squad template, and how to make the introductory note look better.
  11. Any redesign should be done without prejudice to the flag issue. It should be designed to potentially accomodate flags, triagrammes, flags + triagrammes, or flags + country names.
  12. WikiProject Football is one of the most active projects on Wikipedia. That does not give it a divine right to do as it pleases. However, its level of participation is such that, if it reaches a consensus at odds with a fairly specific subpage of the MoS, only a centralized decision could conceivably overturn that consensus.
My intention is to get feedback on potential pitfalls in the above statements, before putting them to a poll. Obviously polls are no substitute for consensus, but in the absence of consensus, does a poll on (roughly) the above statements seem like a good idea? --WFC-- 00:57, 14 August 2010 (UTC)Reply
Seems like the way to go. I agree the design issue is separate Gnevin (talk) 13:12, 16 August 2010 (UTC)Reply

Ping

edit

Are we getting any nearer, here? Chris Cunningham (user:thumperward: not at work) - talk 10:36, 22 August 2010 (UTC)Reply

Well, I gave the matter what I would consider to be adequate exposure. Given that last time changes were made people cried about not being told, I find the lack of interest surprising. Although assuming silence = consensus would be a bad idea in this instance, I believe my summary was an accurate reflection of the RfC. Might be worth contacting an admin who has absolutely nothing to do with football or flags to judge whether that's the case. As for the next step, I would suggest that this is considered for central discussion, but that it must not go up there until neutral phrasing has been agreed, and both sides have the opportunity to put forward their respective views. --WFC-- 22:35, 22 August 2010 (UTC)Reply
As noted above, I think the answer is to put forward the suggested solutions to a support/oppose opinion finder on the WT:FOOTY page rather than here. пﮟოьεԻ 57 08:08, 23 August 2010 (UTC)Reply
I find WT:FOOTY as a project is terrible for ignoring discussion like this and then get upset when the change is made and throwing their toys out of the pram Gnevin (talk) 14:40, 23 August 2010 (UTC)Reply
In my opinion, the consensus (the arguments against fall into an aesthetic category) is that the templates should abide the MOS in naming flags on first use. The problem among those who agree is the degree of implementation (whether country names should be in full or in ISO code). In light of this, the implementation of naming flags should be enacted. Refinement of this scheme (whether full-name or ISO, or other layouts) should follow later. Jappalang (talk) 06:21, 24 August 2010 (UTC)Reply
You may well be right. Although using ISO/FIFA codes alongside flags would be a change to abide by the letter of guidelines (flags should be accompanied on first use) rather than the spirit (article content should be understandable by all readers). All the likes of   COD would do is add to the clutter to the page, without being unambiguous. For that reason, what at a glance appears to be the logical compromise would in fact be worse than no change at all. If we're going the whole way with names, it's clear from the initial furore that the redesign needs to come first. --WFC-- 06:38, 24 August 2010 (UTC)Reply
Unlikely we will ever please everyone, but I am reasonably comfortable with the current sandbox sortable table format with full country names moved the end. As I once stated I wasn't a big fan of the initial proposal so quietly avoided the discussion until the emotive rejections had passed. My initial objection was largely around how it made it look like a list of nationalities that were in the squad, not a list of players, and could sympathise with some of the other reactive comments that it looked awful. On the other hand, arguments regarding MOSFLAG and ACCESSIBILITY were well presented. I figure the sandbox format as of 24 August has the following benefits:
  1. MOSFLAG compliant
  2. Reasonably smart and tidy aesthetically
  3. Sortable - can easily group by position or nationality, or revert to squad number order
  4. Nationality moved to back end of table is better has it is less important than player name
  5. Order of information matches "National football squad" series templates for consistency
  6. Position key is a no-brainer inclusion which also complies with WP:ACCESS while allowing reduced clutter
Additional comments I would have are:
  1. I prefer the FIFA nationality note at the top as it was before.
  2. Looks better with a single column generally, and if that is consensus it would be a simple matter for a bot to remove {{fs mid}}. I'd be happy then in this instance to have 100% width or maybe a minimum column width for name such that most names are shorter than the column-width, and if you have a longer name it just gives more whitespace on other rows, which would negate my next point.
  3. I'd also like to see a little space between name column and nationality column - purely aesthetic ease of reading.
  4. An earlier suggestion on this page suggested a DOB column. I didn't like the look of that as full DOB (more clutter) but agree it would be useful information to see at a glance the rough age band of a squad. Could accommodated with use of the {{age}} template rather than {{birth date and age}}. A bot could easily add the blank parameter into pages and wikignomes would soon populate most of numbers.:::--ClubOranjeT 09:56, 24 August 2010 (UTC)Reply
  • All of which means I support WFCforLife's earlier suggestion of presenting a fixed format for acceptance discussion and inviting interested parties such as WP:FOOTY to participate. Possibly worthwhile making a Template:Football squad player2 and applying it to a select series of low profile articles so people could see it in the real world.
I agree the flag issue and the change of design should be done separately . Change on design then flags Gnevin (talk) 10:53, 24 August 2010 (UTC)Reply
Errrm...yeah...sorry! Nothing on TV, I got BOLD and did the 8 New Zealand Football Championship teams with a {{Template:Football squad player2}}. I do think, however, that the answer to the flag question ultimately affects the layout design anyway.--ClubOranjeT 11:10, 24 August 2010 (UTC)Reply
Should we have [[England national football team|England]] rather than [[England]] Gnevin (talk) 11:18, 24 August 2010 (UTC)Reply
General consensus is against doing so unless specifically referring to involvement with the national team. For instance I should probably convert this list over to the sort of practise you describe, but not this one (at least, not until I get around to converting it to match its little sister). --WFC-- 11:28, 24 August 2010 (UTC)Reply
(EC) Know what? I'd never clicked through on those links before! Given the note states it is showing FIFA eligibility I'd suggest it does relate to the national team. However, all I did so far for the FS player2 set was copy the current sandbox and do a couple of minor tweaks. Live testing already found a couple of potential issues with the coding that would need to be sorted for the table format. The sorting function also lends itself to a single column, as if there are two, you only sort each side which is kinda pointless--ClubOranjeT 11:34, 24 August 2010 (UTC)Reply
Frankly, no progress will be made unless something is put into action. I do not favour ISO codes as well, but if we have to move forward, then let those who want it have the option and defend it later. In this case, have a look at the tweaks I made to Template:Football squad player/sandbox, on display at Template:Football squad player/testcases. The default is full country names; setting flagname to "iso" sets up the triagrammes. I believe those who claim it is easier to recognise triagrammes surely can input Turkmenistan's iso code with ease themselves (a full name will still appear as a full name no matter what, thanks to the way {{flag}} is coded). Jappalang (talk) 08:13, 26 August 2010 (UTC)Reply
Progress is being made. The redesign is live on nine articles. Eight use identical syntax to {{football squad player}}, while the somewhat amended transclusion in Watford F.C. shows roughly what the finished redesign might look like (albeit sortname might have to be done manually by those who want to sort by surname). My assumption is that once we have worked out how to deal with {{fs mid}} and sorting matters, the new template will be rolled out after discussion.
By default the new template shows the fully expanded countries, and deals with the aesthetic problem. There are legitimate, MOS compliant reasons why a user might want to just display the flags, and therefore that should be the alternative to full names. For instance, bigger clubs tend to include one or both of the reserves and youth team. In almost all cases these teams will have fewer nationalities than the first team, and in most of these cases all of the nationalities will be covered by the fully expanded first team. A parameter to shorten countries hasn't been created yet AFAIK, but if it is, and articles use the parameter in an MOS-incompliant way, it will then be possible and acceptible to remove it. --WFC-- 10:30, 26 August 2010 (UTC)Reply
I notice you used {{sort|##|#}} on the single digit Watford numbers; any particular reason? it doesn't seem to need it to sort the numbers properly - at least not in my browser. The {{sortname}} makes perfect logical sense to me for a sortable table, so the NZFC teams have also been updated with that.
I would be suitably impressed with the wizardry if someone manages to sort a split table across both columns.--ClubOranjeT 12:48, 26 August 2010 (UTC)Reply
When I was previewing there were sorting issues. I'll create an example in a little while. --WFC-- 13:12, 26 August 2010 (UTC)Reply
Sorting the numbers a few times here demonstrates the problem. Given that there are only nine possible cases where {{sort}} is necessary (numbers 1-9), I'm sure it will be possible to code the template to receive |no=1 and output {{sort|01|1}}. --WFC-- 13:21, 26 August 2010 (UTC)Reply
How bizarre! What have you done? Doesn't do that on _MY_ pages! ;-) it seems to go through a repeating cycle.--ClubOranjeT 01:36, 27 August 2010 (UTC)Reply
As far as I can tell it's because I used an emdash (&mdash) instead of a hyphen (-). Given that emdashes are widely used, it would probably be a good idea to hard-code a solution into the template. I made an attempt at it the other day, but I'm not really familiar with the syntax. --WFC-- 06:25, 27 August 2010 (UTC)Reply
The changes I made to the sandbox allow no names, ISO names, or full names, so I fail to see the point of "that should be the alternative to full names." The testcases are functional and at least compliant (on default) with the MOS. I fail to understand what is the hold up now; no policy- or guideline-backed opposition has been given (or even a valid point that MOS-compliance leads to a deterioration of encyclopaedic quality). Instead, valid opinion point to implementing a template that can be compliant. Aesthetics (including whatever issue {{fs mid}}, sorting, and such) can be improved later. I believe the impetus to improve the template, making it compliant with the MOS, has been railroaded into some complicated project that will see no light while allowing the current violation to persist further. Jappalang (talk) 13:02, 26 August 2010 (UTC)Reply
The holdup is that countries do look bad in the old template, and that the new one isn't quite ready. Relax, it will happen. After last time, it's clear that rushing the change is only going to be counterproductive in the long run. --WFC-- 13:12, 26 August 2010 (UTC)Reply
What's still to do with the new template? If I can do anything template-wise to expedite this then I'm happy to take requests. Chris Cunningham (user:thumperward: not at work) - talk 09:45, 27 August 2010 (UTC)Reply
Coding wise, the only thing I can see on the to-do list is ensuring that numbers 1-9 sort properly when emdashes are present. In my opinion the next step would be to protect the templates, roll them out to featured articles, leave it a few days to get some feedback, and assuming that the overall reception is positive, merge the templates. --WFC-- 09:54, 27 August 2010 (UTC)Reply
I think a good thing to do would be to change the position codes for full names, i.e. change "GK" for "Goalkeeper", "DF" for "Defender", etc. I would also suggest moving the "other" parameter to a new column, entitled "Notes" or something. – PeeJay 09:59, 27 August 2010 (UTC)Reply
Oh yeah, I agree that now is a good time to do that consider moving "other" to its own column. Almost forgot that "other" was a parameter- I usually find out that a player has joined us on loan by checking my watchlist. --WFC-- 10:51, 27 August 2010 (UTC)Reply
"Other" can easily be moved to a "notes" column if there's consensus for it. Let me know if there's consensus for that and I'll get it changed in sixty seconds. Chris Cunningham (user:thumperward: not at work) - talk 11:33, 27 August 2010 (UTC)Reply
We should probably leave the positions as they are for the time being. I see no point in stalling this process over a relatively unimportant point. Positions are now in the key, so it's really more a matter of taste than anything else. --WFC-- 11:28, 27 August 2010 (UTC)Reply
Ok Chris, get it so it will sort across twin table (i.e. using fs mid)- then I will truly shout your name as a Wiki Template God;-). That would make it the bees knees. I disagree with expanding positions to full descriptions, I'd rather see a key. The main purpose or a squad list is to see who is in the squad. Secondary would be the make up of the squad, a) as far as nationalities go, and b) the relative age of the squad. Every squad has goalkeepers, defenders and strikers, expanding that to full descriptions only detracts from the real important information.--ClubOranjeT 11:09, 27 August 2010 (UTC)Reply
Sorting across both tables at once isn't possible using the current sortable javascript. Fixing that is beyond my capabilities and will probably have to be punted to MediaWiki development, though I'd be surprised if it were possible at all as the columns are really two independent tables. WFC: the test case here sorts properly with emdashes already, so fas as I can see; it has a quirk where there are four sortable orders (as the squad numbers can be interpreted either digit-by-digit or as a whole), but that's nothing to do with the table header AFAIK. Anything else? Chris Cunningham (user:thumperward: not at work) - talk 11:31, 27 August 2010 (UTC)Reply
If {{football squad player2}} were able to read |no=1 as {{sort|01|1}}, |no=2 as {{sort|02|2}}, and so on up to 9, would that reduce the number of sortable orders to two? --WFC-- 11:44, 27 August 2010 (UTC)Reply
I'd think so. That might be an elegant solution. I would note that I'd really rather there weren't a dogfood version of the present code being deployed on high-profile articles for the time being, by the way. Chris Cunningham (user:thumperward: not at work) - talk 11:56, 27 August 2010 (UTC)Reply
Oh I agree, and WFC must also as he only put it on the Watford article.. ;-) --ClubOranjeT 12:06, 27 August 2010 (UTC)Reply
Yeah, I agree. The template as implemented on the Watford page is roughly how I think the template should look when rolled out. It shouldn't be put onto FAs until we're satisfied that it's robust, but I see putting it onto FAs when ready as a good stepping stone to full rollout. --WFC-- 12:37, 27 August 2010 (UTC)Reply
Right, got a fix for the dashes. Anyone else fancy a go at hairy string parsing code for the player lines sort key, or is that my job? Chris Cunningham (user:thumperward: not at work) - talk 12:17, 27 August 2010 (UTC)Reply
Just to clarify, are you talking about player names? --WFC-- 13:36, 27 August 2010 (UTC)Reply
Numbers. Chris Cunningham (user:thumperward: not at work) - talk 13:39, 27 August 2010 (UTC)Reply

I'm guessing the following switch statement will do the trick. --WFC-- 13:56, 27 August 2010 (UTC)Reply

{{#switch:{{{no}}}
|1={{sort|01|1}}
|2={{sort|02|2}}
|3={{sort|03|3}}
|4={{sort|04|4}}
|5={{sort|05|5}}
|6={{sort|06|6}}
|7={{sort|07|7}}
|8={{sort|08|8}}
|9={{sort|09|9}}
|#default={{{no}}}
}}

Aha. Fancy testing that to make sure? If so, we're about done for technical problems, right? Chris Cunningham (user:thumperward: not at work) - talk 15:00, 27 August 2010 (UTC)Reply
Given the kind of sorting I've successfully pulled off in the very recent past I'm almost embarrassed to say this, but I can't seem to get it to work. I'm sure the above switch statement is the way to go, I'm just struggling with the syntax. --WFC-- 15:46, 27 August 2010 (UTC)Reply
Try it now. Switch works perfectly for me. Chris Cunningham (user:thumperward: not at work) - talk 16:22, 27 August 2010 (UTC)Reply
Looks good. Thanks! --WFC-- 16:31, 27 August 2010 (UTC)Reply
My opinion is that the new template seems ready for serious consideration at WT:FOOTY (and I accept Number 57's suggestion that the discussion itself should go there). But the one concern I can see coming up is the rollout of {{sortname}}. It's simple enough to use, but is it remotely conceivable that a bot would be able to assist with rolling it out? Working through the problem logically I'm convinced that it's technically possible (I'll write out a word-based version of the process if anyone's interested). If it is possible, maybe a bot already exists to do it? --WFC-- 18:21, 31 August 2010 (UTC)Reply
Random break
edit

Has this process stalled again ? Gnevin (talk) 00:50, 22 September 2010 (UTC)Reply

I think it's ready to go. But after the early controversy I promised not to take the lead on this. --WFC-- 23:00, 22 September 2010 (UTC)Reply

ROI flags

edit

Got another problem. Why does nat=Republic of Ireland give Republic of Ireland, while nat=ROI gives Ireland? (note that I just created Template:Country data ROI as an alias to Template:Country data Republic of Ireland, and so this might be my fault.) Chris Cunningham (user:thumperward: not at work) - talk 12:23, 27 August 2010 (UTC)Reply

Ack, only just realised that you changed this. As I'm sure you're hinting Chris, we really should be using Republic, given that "Ireland" can literally mean the island in other sports, and that the IFA ran the pre-1922 team. {{flagcountry}} uses ISO 3166-1 alpha-3, so ROI should point to "Ireland", but I can't for the life of me see how it's doing it. --WFC-- 22:28, 31 August 2010 (UTC)Reply
Nope, I'm lost. Any suggestions for who to ping on this? Chris Cunningham (user:thumperward: not at work) - talk 12:32, 1 September 2010 (UTC)Reply
The first two people to edit the template have edited in the last month, but User:Andrwsc seems the best bet if we're looking for a quick response. --WFC-- 13:36, 1 September 2010 (UTC)Reply
I don't see any problem with this template; it just calls {{flagicon}}, so the tricolour is a clickable-link to Republic of Ireland as expected. Where are you seeing a link to Ireland? Any why did you create a new country code when IRL is a widely recognized standard code? — Andrwsc (talk · contribs) 03:24, 2 September 2010 (UTC)Reply
Sorry, I hadn't previously read the wall of text above this section, but I see now you are working on a sandbox version. The "problem" is that {{flagcountry}} will always use the shortname alias value inside the country_data template, and that is "Ireland" for Template:Country data Republic of Ireland. Note that the link is still to Republic of Ireland; it's only the display text that is shortened. Basically you get [[Republic of Ireland|Ireland]]. Is that a problem? My understanding is that "Republic of Ireland" (shown in full) is appropriate for the national team (e.g. output of {{fb|IRL}} is   Republic of Ireland) but we're referring to nations here, not national teams, so is it such a problem that the {{flagcountry}} output is what it is? — Andrwsc (talk · contribs) 03:38, 2 September 2010 (UTC)Reply
The issue is that in the past there was a Ireland team that has been superceded by the Northern Irish and Republic teams, hence it is a good idea to avoid using "Ireland" as a nationality for modern-day players. пﮟოьεԻ 57 08:20, 2 September 2010 (UTC)Reply
Yes, I know. I am the editor who coded the Ireland flag templates to work the way they do. But my point is that the nationality for these players isn't simply "Ireland" as you state, it is [[Republic of Ireland|Ireland]], and I'm asking what's wrong with that? — Andrwsc (talk · contribs) 21:11, 2 September 2010 (UTC)Reply
Because FIFA recognises Northern Ireland as the successor to the initial Ireland team. FIFA would never call Northern Ireland "Ireland", but by the same token they go out of their way to use the entire phrase "Republic of Ireland". --WFC-- 16:42, 13 September 2010 (UTC)Reply

nat parameter optional

edit

Could the nat=XXX please be optional so I dont have to worry about MOSFLAG. I would like to simply remove it from the player squad list. Sandman888 (talk) 11:46, 2 September 2010 (UTC)Reply

As in, remove the entire column? --WFC-- 13:16, 2 September 2010 (UTC)Reply
Yes Sandman888 (talk) 13:20, 2 September 2010 (UTC)Reply
For the hassle the debate that debate would entailGiven the hassle a debate on the matter would cause if we introduced it, it would make more sense to simply create a wikitable for that article. It would have the added advantage of simpler source code as well. --WFC-- 13:31, 2 September 2010 (UTC)Reply
But the present scheme doesnt comply with MOSFLAGS? It could be an optional parameter, as indicated. Sandman888 (talk) 14:03, 2 September 2010 (UTC)Reply
The scheme here does (which is what I thought we were talking about). --WFC-- 16:38, 13 September 2010 (UTC)Reply

I found this discussion when researching the history of the {{{icononly}}} parameter. {{{icononly}}} was briefly added, but quickly reverted from {{Football squad player}} in July 2010, but this parameter has been part of {{Football squad player2}} since its creation. I don't know whether or how much this parameter is used in that template. |name=code and {{{icononly}}}are two of the template differences remaining to be resolved. – wbm1058 (talk) 23:13, 24 February 2021 (UTC)Reply

Finding that {{{icononly}}} is apparently unused, I've removed it. – wbm1058 (talk) 15:43, 25 February 2021 (UTC)Reply

Birthdates?

edit

In working the invalid parameters list I've seen many cases of editors adding an unnamed parameter with a date which I assume is the player's date of birth. For example, see ESAE FC. Any idea why this is happening, and any better option for fixing this other than simply removing the date from the template? wbm1058 (talk) 03:25, 27 February 2021 (UTC)Reply

Such a parameter exists for national team squadlists (e.g.) so maybe they are confused by that. I can't really see any solution other than removing it where it exists for club squadlists. Number 57 15:50, 27 February 2021 (UTC)Reply
Done. I'm trying to get these cleaned up before the March report is generated. – wbm1058 (talk) 17:19, 27 February 2021 (UTC)Reply

nonat

edit

The little-used {{{nonat}}} parameter was added to {{Football squad start2}} in August 2012 as a way to remove the Nation column and was first used on Ayr United F.C.. However the current version of Ayr United F.C. does show the nation. Indeed the March TemplateData report found that this parameter wasn't being used anywhere. However I found that Southampton Women's F.C. wasn't specifying the nation in its table so I added |nonat=yes there. If we continue supporting this parameter, it needs to be merged/added to {{Football squad start}}. I can do that. wbm1058 (talk) 22:11, 7 March 2021 (UTC)Reply

I'm having second thoughts on supporting the option to remove the nation column. While it works fine on Southampton Women's F.C. where none of the players have their nation specified, it's more problematic on articles like Haringey Borough F.C. where just a couple players have their nation specified or Kansas City Comets (1979–91) where all but one have their nation specified. The implementation should be more robust to handle these better. I'm thinking of just removing support for this parameter rather than going to more effort to make it work better. – wbm1058 (talk) 02:04, 19 March 2021 (UTC)Reply
I think the best route to go down would be to follow the nonumber option – i.e. the nationality column is included unless turned off via a nonat parameter. I don't recall the mess that is the Haringey Borough squad being possible previously – is it a recent change that has caused this? Number 57 09:11, 19 March 2021 (UTC)Reply
Yes, a recent change I made, now reverted, caused that. I've reached a sort of impasse. The increased template complexity required to support these new options is causing some pages that have a lot of football squad tables to exceed template-include byte limits. So I'm stuck in my efforts to merge {{Football squad player}} and {{Football squad player2}}. I think this can be solved by coding the decision logic in a Lua module, but I'm still not particularly proficient in Lua. Perhaps this project is the push I've needed to take a crash course in Lua coding, so I can finish what I've started. – wbm1058 (talk) 14:50, 21 March 2021 (UTC)Reply

natlast

edit

And there was no consensus on #Should the nation be displayed after the number or in the last row? so I suppose the solution is to implement a new optional parameter to move the nation to the last rowcolumn. {{Football squad player2}} could simply be a shell that transcludes {{Football squad player}} which specifies this new parameter |natlast=yes. – wbm1058 (talk) 17:13, 10 March 2021 (UTC)Reply

@Wbm1058: Keep in mind that if we were to move it to the last row, it would create a huge white space in this case: say one player has "on loan from team" as the "other=" parameter. This means that, in order for the nations to be all aligned, the players that don't have an other parameter would have a lot of space between the player's name and their nationality. Nehme1499 17:33, 10 March 2021 (UTC)Reply
Agree with Nehme on this – as it looks like we're sticking with trigrammes, I don't see any benefits to moving the nationality to the last column, only problems. Number 57 17:59, 10 March 2021 (UTC)Reply
For the record, rows are horizontal and columns are vertical, so the request is for nationality to be placed in the column on the right. The real problem is that you all want two columns of complete player data for the roster.
Compare New York Red Bulls#Roster and RB Leipzig#Squad. In the first, the last column lines up quite nicely and meets both MOS:ACCESS and the nation is clear, with the nation being out of the way of the actual useful information about the player: name, position and number. To see what it would look like with players on loan, look at the players out on loan sections. Reducing either to a small monitor, and everything wraps and you end up with a horrible mess with the double-wide. Either drop the nation (which is a source for edit wars on occasion) or put it on the right where it belongs. Walter Görlitz (talk) 01:45, 11 March 2021 (UTC)Reply

ref location

edit

Can we shift the ref field to go after the |other= field, as we use that field for loans information also, is seems smarter to have the ref run after that maybe? At the end of the string line. I've used the feature on Tottenham Hotspur F.C.#Players for Out on loan players. Thought it would help, thoughts? Govvy (talk) 12:39, 2 February 2021 (UTC)Reply

Just put the ref outside the template at the end of the line as at Manchester United F.C. No need to put it in its own parameter of the template. – PeeJay 16:46, 2 February 2021 (UTC)Reply

Positions

edit

Association football positions describes more specialized positions. See #Add postion Field Player (FP) for a less-specialized position. From the archives:

Player positions abbreviation?

edit

After putting the wrong letter in whilst editing, I noticed that things such as 'MC' and 'ML' link to 'Midfielder' and 'DC' and 'DL' to 'Defender' (although 'DR' doesn't). Is this a deliberate decision? As it's not mentioned in the parameters above. My personal preference is to include the chance to be more accurate with players' positions than simple 'midfielder', although if you can't signify someone's a right-back then it's kinda pointless. CharlieT 00:02, 6 October 2007 (UTC)Reply

The only expected links are GK, DF, MF and FW. Any other link was not provided by the original creator, i.e., me. And I would not agree with any of them. --Angelo 00:40, 6 October 2007 (UTC)Reply

Multiple positions

edit

How can one handle multiple positions a player can play? For example Hapoel Ashkelon F.C. has pos=GK|pos=MF for Galil Ben Shanan, but only one (MF) is displayed. --CiaPan (talk) 06:17, 22 May 2015 (UTC)Reply

Only the second one is displayed because that's how Wikipedia's code handles duplicate parameters in the same instance of a template. To answer your question, though, there's no way to put in multiple positions. You'll just have to decide (using reliable sources) which is the player's primary position. – PeeJay 09:06, 22 May 2015 (UTC)Reply
How about adding a pos2 parameter? I could do that, but don't dare... ;) And honestly do not know if it's actually needed. --CiaPan (talk) 12:15, 22 May 2015 (UTC)Reply

Should any other valid positions be added to the template? I've run across several malformed attempts to add a second position. For example, see this diff.

Is THIS an acceptable way to show players who play two positions? wbm1058 (talk) 20:00, 7 March 2021 (UTC)Reply

No, we should stick to one position between GK, DF, MF, FW. Nehme1499 20:03, 7 March 2021 (UTC)Reply

High node counts coming from this template

edit

After seeing that several "football transfers" articles had landed in Category:Pages where node count is exceeded using many football squad player tables, I somehow fell into this rabbit hole, where I've been for the past two days... – wbm1058 (talk) 23:41, 14 February 2021 (UTC) (higher up on this page)

And now I've been here on and off for over a month, I'm just now looking deeper into this. Each {{Football squad player}} transclusion uses roughly 1,000 nodes. I ran a test on one example use and found that without |nat= the node count was just 146, but with |nat= the node count was 1158, thus |nat= uses (1158-146)=1012 nodes! So that's where to look to make efficiency improvements.

List of Iranian football transfers summer 2013 has 1,172 {{Football squad player}} transclusions and that put its node count at 1,008,338 which is > 1,000,000.

I saw that this 20 August 2020 edit by Frietjes attempted to solve the issue. I don't have any experience with working on other instances of this rarely-occurring problem, but will take a stab at further investigation to figure it out. I'd like to fix this before completing the merge with {{Football squad player2}} so as not to risk making this problem worse. – wbm1058 (talk) 17:09, 14 March 2021 (UTC)Reply

I've traced it down to:

{{ fba/core
| alias = Iran
| flag alias = Flag of Iran.svg
| name = code
}}

That still has a preprocessor visited node count = 1,028 but removing |name=code cuts it down to 630 as it saves a table lookup. In other words   IRN is too inefficient to do on a mass scale and I believe changing that to   Iran will get the Category:Pages where node count is exceeded pages inside the limit. I can make that happen by creating a new parameter that lets the user override the |name=code default on selected pages. Note that my recent edit to do this for everyone was reverted. – wbm1058 (talk) 18:30, 14 March 2021 (UTC)Reply

The primary issue here is that those articles shouldn't be using this template, as it's not what it is designed for. They should look like List of English football transfers summer 2020. Number 57 19:25, 14 March 2021 (UTC)Reply
It's not always easy to get all editors on the same page, and have Iranian and Serbian and Romanian and Japanese editors to all follow standards established by British editors. In the meantime, I've implemented the easier patch, and cleared Category:Pages where node count is exceeded, but for four user pages. wbm1058 (talk) 02:36, 15 March 2021 (UTC)Reply
Related discussion and analysis at Talk:List of Serbian football transfers summer 2018#Too many templates. – wbm1058 (talk) 16:14, 6 April 2021 (UTC)Reply