Jump to content

Wikipedia:Templates for discussion/Log/2021 May 24: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
→‎Template:Thinspace: Reply answers my original inquiry, which received no respondents before listing here. Thank you :)
Line 108: Line 108:
::::Fair enough. It was also an illustration of where the logic leads. But since I anyway have no problem with having {{tl|constlk}} moved to {{tl|Parliament of the United Kingdom constituency link}} leaving a redirect, could you tell me what your problem with that is? In terms of [[WP:TFD#Reasons]]. [[User:Charles Matthews|Charles Matthews]] ([[User talk:Charles Matthews|talk]]) 15:35, 24 May 2021 (UTC)
::::Fair enough. It was also an illustration of where the logic leads. But since I anyway have no problem with having {{tl|constlk}} moved to {{tl|Parliament of the United Kingdom constituency link}} leaving a redirect, could you tell me what your problem with that is? In terms of [[WP:TFD#Reasons]]. [[User:Charles Matthews|Charles Matthews]] ([[User talk:Charles Matthews|talk]]) 15:35, 24 May 2021 (UTC)
:::::@[[User:Charles Matthews|Charles Matthews]], do I really need to explain to you that an ambiguously-titled redirect breaches [[WP:RFD#DELETE]] #2?
:::::@[[User:Charles Matthews|Charles Matthews]], do I really need to explain to you that an ambiguously-titled redirect breaches [[WP:RFD#DELETE]] #2?
::::::Well, yes, you are clearly assuming the scope of that guideline extends to template space. A new one to me. [[User:Charles Matthews|Charles Matthews]] ([[User talk:Charles Matthews|talk]]) 17:05, 24 May 2021 (UTC)
:::::Also, your insistence on [[WP:TFD#Reasons]] is misplaced. That guidance explicitly says {{t|Templates for which none of these apply may be deleted by consensus here|q=y}}. So TFD will allow deletion on the basis of a consensus here that each of these templates cannot avoid being either 1) named ambiguously, or 2) so verbosely-named that its raison d'etre is destroyed. So far, that seems to be the emerging consensus, and if he closer determines that's the outcome, it is a valid reason to delete.
:::::Also, your insistence on [[WP:TFD#Reasons]] is misplaced. That guidance explicitly says {{t|Templates for which none of these apply may be deleted by consensus here|q=y}}. So TFD will allow deletion on the basis of a consensus here that each of these templates cannot avoid being either 1) named ambiguously, or 2) so verbosely-named that its raison d'etre is destroyed. So far, that seems to be the emerging consensus, and if he closer determines that's the outcome, it is a valid reason to delete.
::::::Well, yes, but, but. You do need the rationale for the first point to delete the redirect, and I don't see that, and if the redirect has standing then the ''raison d'être'' is good in my view. That is simply for moving the template to a verbose name. Anyway we'd have a cleaner process if the template was moved, and then the deletion of the redirect could be at RfD.
:::::And I am very surprised that you are making such a stand on your personal macro when a simple alternative is available to you. --[[User:BrownHairedGirl|<span style="font-variant:small-caps"><span style="color:#663200;">Brown</span>HairedGirl</span>]] <small>[[User talk:BrownHairedGirl|(talk)]] • ([[Special:Contributions/BrownHairedGirl|contribs]])</small> 16:33, 24 May 2021 (UTC)
::::::But the compromise has always been that substing is required. As you pointed out, it is not something I opposed, though it was in tension with the ''raison d'être''. It does not undermine the ''raison d'être''. [[User:Charles Matthews|Charles Matthews]] ([[User talk:Charles Matthews|talk]]) 17:05, 24 May 2021 (UTC)
:::::And I am very surprised that you are making such a stand on your personal macro when a simple alternative is available to you. --[[User:BrownHairedGirl|<span style="font-variant:small-caps"><span style="color:#663200;">Brown</span>HairedGirl</span>]] <small>[[User talk:BrownHairedGirl|(talk)]] • ([[Special:Contributions/BrownHairedGirl|contribs]])</small> 16:33, 24 May 2021 (UTC)
::::::There are many surprising things about this whole discussion, frankly. You could have had my view on {{tl|constlk}} for the asking. If you rely on consensus here, I hope there will be sounder process and logic than we have had so far. If you really think "ambiguous" template redirections are to be deprecated, across the board, that it a major can of worms in my view. [[User:Charles Matthews|Charles Matthews]] ([[User talk:Charles Matthews|talk]]) 17:05, 24 May 2021 (UTC)
*Dudes, the Brown Haired Girl is going to be right here... She just is. And I can't and wouldn't disagree with her. [[User:A loose necktie|A loose necktie]] ([[User talk:A loose necktie|talk]]) 14:35, 24 May 2021 (UTC)
*Dudes, the Brown Haired Girl is going to be right here... She just is. And I can't and wouldn't disagree with her. [[User:A loose necktie|A loose necktie]] ([[User talk:A loose necktie|talk]]) 14:35, 24 May 2021 (UTC)
* '''Comment''': to offer a more peaceful solution for Charles Matthews, make the template a subst always template and move it to your user space. There you can name it whatever you like and still keep the functionality you want for editing. --[[User:Gonnym|Gonnym]] ([[User talk:Gonnym|talk]]) 16:52, 24 May 2021 (UTC)
* '''Comment''': to offer a more peaceful solution for Charles Matthews, make the template a subst always template and move it to your user space. There you can name it whatever you like and still keep the functionality you want for editing. --[[User:Gonnym|Gonnym]] ([[User talk:Gonnym|talk]]) 16:52, 24 May 2021 (UTC)

Revision as of 17:06, 24 May 2021

Propose merging Template:Thinspace with Template:Thin space.
Template:Thinspace does not appear to do anything special that Template:Thin space does not already handle. I opened a discussion nearly 3 weeks ago at the proposed merge destination Talk page, pinging each template creator, with no reply as yet. — Christopher, Sheridan, OR (talk) 16:33, 24 May 2021 (UTC)[reply]

  • Keep. Their functionality is quite different.
{{Thinspace}} is for formatting a list of items separated by &thinsp;. It takes multiple parameters.
{{Thin space}} just emits a single &thinsp;, set to not wrap. It takes no parameters.
The /docs should be updated to explain the difference. --BrownHairedGirl (talk) • (contribs) 16:51, 24 May 2021 (UTC)[reply]
Thank you; I had asked that very question, but with no reply. My alternate suggestion was to add a notation somewhere near the top of each template, so as to avoid future confusion. — Christopher, Sheridan, OR (talk) 17:03, 24 May 2021 (UTC)[reply]

I do not understand why this template was ever even created. Its existence makes it more difficult for readers to edit the article on lunar eclipses, and I have now transferred the information within it to that article and removed the template from it. I've never seen this in a Wikipedia article before. A loose necktie (talk) 14:21, 24 May 2021 (UTC)[reply]

Coca-Cola Red Sparks team was disbanded at the end of the 2021 season, so the current squad template is no longer needed. Rugbyfan22 (talk) 11:54, 24 May 2021 (UTC)[reply]

The team is certainly notable, it's played in the top tier or second tier of Japanese rugby for the entirety of its history. There's plenty of coverage of the team online. Large numbers of the Japanese rugby teams are company teams (see Panasonic Wild Knights or Suntory Sungoliath this years finalists for example), they have professional players playing for them not just company staff playing muck about stuff. Rugbyfan22 (talk) 14:37, 24 May 2021 (UTC)[reply]

per WP:NENAN's "rule of five": these templates have fewer than five navigable links in addition to the main article. {{August 2020 Scottish Conservative Party leadership election}} has main+2, and {{Scottish Conservative Party leadership election, 2020}} has main+3. BrownHairedGirl (talk) • (contribs) 11:11, 24 May 2021 (UTC)[reply]

This is a simple template, used to create links to constituencies of the House of Commons of the United Kingdom. It is transcluded on about 300 pages.

Every constituency article uses a standard disambiguator "(UK Parliament constituency)", so the template just adds the dab and pipes the link:

e.g. {{Constlk|Moray}}Moray

These article titles have been stable since 2006, so there is no need to keep them wrapped in a template. All current uses should be substed, which in the example above will expand {{Constlk|Moray}} to [[Moray (UK Parliament constituency)|Moray]]

I have no strong view on whether the template should be kept, or tagged as always-substitute. It is not widely used, but if somebody finds it useful then it seem to me to be a bit of tossup whether to keep it. --BrownHairedGirl (talk) • (contribs) 00:59, 24 May 2021 (UTC) (Preceding two sentences struck because discussion revealed how the ambiguity of these titles can be resolved only by destroying the brevity which is their raison d'etre. I now see no alternative to deletion. --BrownHairedGirl (talk) • (contribs) 14:49, 24 May 2021 (UTC))[reply]

  • Very good point, but {{UKconstlk}} is insufficient disambiguation. Within the United Kingdom, there have been in the last 100 years constituencies for at least eight different parliamentary chambers or Assemblies:
  1. The House of Commons of the United Kingdom, at Westminster
  2. The House of Commons of Northern Ireland, at Stormont 1921–1973
  3. The House of Commons of Southern Ireland, in Dublin 1921–1922
  4. The Scottish Parliament, in Edinburgh 1999–present
  5. The Senedd, in Cardiff 1999–present
  6. The European Parliament, 1979–2020
  7. The Northern Ireland Assembly, 1973–1974, 1982–1986, and 1999–present
  8. The London Assembly, 2000–present
This template serves only the first item on that list, i.e. House of Commons of the United Kingdom at Westminster ... but its massively ambiguous name could apply to any of them. So if kept, it should be renamed to unambiguously describe its actual function: Template:Parliament of the United Kingdom constituency link or Template:House of Commons of the United Kingdom constituency link.
However, the verbosity of an unambiguous title destroys the brevity which is the sole source of the convenience sought by its creator @Charles Matthews. Since there is no way of squaring that circle, the remedy is deletion. --BrownHairedGirl (talk) • (contribs) 09:24, 24 May 2021 (UTC)[reply]
OK, the creation of the template dates from 2013, and as far as I know none of the other corresponding templates has been set up. This is more like a pre-emptive strike, than a "very good point" (from an IP editor who has been here a week). Charles Matthews (talk) 09:34, 24 May 2021 (UTC)[reply]
@Charles Matthews, you're a clever man. So why does your reply raise the red herring of the comment being by an IP, but evade the problem I identified: that removing the ambiguity in the title creates verbosity which destroys the brevity that prompted you to create the template in the first place? --BrownHairedGirl (talk) • (contribs) 09:48, 24 May 2021 (UTC)[reply]
On the naming of the template, it could be {{westconstlk}} (concise form) at need. Charles Matthews (talk) 09:53, 24 May 2021 (UTC)[reply]
Do I really need to point out how "west" is an ambiguous abbreviation, so {{westconstlk}} remains ambiguous as well as deeply obscure? --BrownHairedGirl (talk) • (contribs) 10:00, 24 May 2021 (UTC)[reply]
  • Comments: Nothing is clear. I have nominated this discussion at WP:CR because we'd do better with a fresh start.
  1. If the template is substituted, the disambiguation issue as formulated by Gonnym goes away.
  2. If 67.70.27.180 was unaware of that, which seems possible, my comment was scarcely irrelevant.
  3. If BHG says "But thank you for not opposing substing it", why does she also say "the remedy is deletion"?
So far we have my keep vote. If this is a deletion discussion, can we please have a rationale based on WP:TFD#REASONS? Preferably on a fresh page.
My attitude to subst is that "subst:" is six more keystrokes. wikt:half a loaf is better than none. It might be better to discuss that, than treat Charles to a tech interview 1990s-style based on a trick question. As the OP wrote "if somebody finds it useful then it seem to me to be a bit of tossup whether to keep it". Charles Matthews (talk) 13:23, 24 May 2021 (UTC)[reply]
1) and 2) Substing does not resolve the ambiguity problem. Substing current uses leaves us with the problem that the ambiguous name invites misuse.
3) I find it hard to avoid the conclusion that you are being intentionally disingenuous when you write If BHG says "But thank you for not opposing substing it", why does she also say "the remedy is deletion"?. I thanked you for not opposing substitution because that is at least some improvement, by removing the existing uses. I still prefer deletion, because after replying to you I considered the IP's point about ambiguity, and I realised that resolving the ambiguity would destroy the brevity which is the template's raison d'etre. That made me shift my view away from the ambivalence about deletion which I had expressed in the nomination. My reasoning is clearly set out above in my comment of 09:24, 24 May, which you chose to ignore in favour of moaning that an IP had identified the ambiguity. It is particularly disingenuous of you to quote from a part of the nomination where my reasoning has explicitly been superseded due to do things I learned in discussion. I will now strike that part of the nom. --BrownHairedGirl (talk) • (contribs) 14:45, 24 May 2021 (UTC)[reply]
And why do you say that? I use Template:Person categories all the time as {{l}} substituted. My point #1 was that subst would make that whole line of argument go away. I think you will have a bad time if you extend your reasoning to Template:HMS, another abbreviated "typing shortcut", by the way. Charles Matthews (talk) 14:23, 24 May 2021 (UTC)[reply]
@Charles Matthews, that pointer to another ambiguously-named template is a classic "other crap exists" argument. It's the daft notion that one unfixed problem justifies not fixing every other similar problem. --BrownHairedGirl (talk) • (contribs) 14:56, 24 May 2021 (UTC)[reply]
Fair enough. It was also an illustration of where the logic leads. But since I anyway have no problem with having {{constlk}} moved to {{Parliament of the United Kingdom constituency link}} leaving a redirect, could you tell me what your problem with that is? In terms of WP:TFD#Reasons. Charles Matthews (talk) 15:35, 24 May 2021 (UTC)[reply]
@Charles Matthews, do I really need to explain to you that an ambiguously-titled redirect breaches WP:RFD#DELETE #2?
Well, yes, you are clearly assuming the scope of that guideline extends to template space. A new one to me. Charles Matthews (talk) 17:05, 24 May 2021 (UTC)[reply]
Also, your insistence on WP:TFD#Reasons is misplaced. That guidance explicitly says {{Templates for which none of these apply may be deleted by consensus here}}. So TFD will allow deletion on the basis of a consensus here that each of these templates cannot avoid being either 1) named ambiguously, or 2) so verbosely-named that its raison d'etre is destroyed. So far, that seems to be the emerging consensus, and if he closer determines that's the outcome, it is a valid reason to delete.
Well, yes, but, but. You do need the rationale for the first point to delete the redirect, and I don't see that, and if the redirect has standing then the raison d'être is good in my view. That is simply for moving the template to a verbose name. Anyway we'd have a cleaner process if the template was moved, and then the deletion of the redirect could be at RfD.
But the compromise has always been that substing is required. As you pointed out, it is not something I opposed, though it was in tension with the raison d'être. It does not undermine the raison d'être. Charles Matthews (talk) 17:05, 24 May 2021 (UTC)[reply]
And I am very surprised that you are making such a stand on your personal macro when a simple alternative is available to you. --BrownHairedGirl (talk) • (contribs) 16:33, 24 May 2021 (UTC)[reply]
There are many surprising things about this whole discussion, frankly. You could have had my view on {{constlk}} for the asking. If you rely on consensus here, I hope there will be sounder process and logic than we have had so far. If you really think "ambiguous" template redirections are to be deprecated, across the board, that it a major can of worms in my view. Charles Matthews (talk) 17:05, 24 May 2021 (UTC)[reply]
  • Dudes, the Brown Haired Girl is going to be right here... She just is. And I can't and wouldn't disagree with her. A loose necktie (talk) 14:35, 24 May 2021 (UTC)[reply]
  • Comment: to offer a more peaceful solution for Charles Matthews, make the template a subst always template and move it to your user space. There you can name it whatever you like and still keep the functionality you want for editing. --Gonnym (talk) 16:52, 24 May 2021 (UTC)[reply]

Mvcg66b3r was removing both Templates from many Network affiliate articles, and I can see why, since TV Fool and TVQ are considered Inactive sites just like TV.com. Because of all this, and me removing the Templates too, both templates needs to automatically deleted by SporkBot on many Other Network affiliate articles that still has this template. LooneyTraceYT commenttreats 16:07, 24 May 2021 (UTC)[reply]