Revision as of 17:16, 7 October 2019 editTrialpears (talk | contribs)Administrators33,082 edits →Geography, politics and governance: Reopened← Previous edit | Latest revision as of 00:11, 4 January 2025 edit undoFrietjes (talk | contribs)Autopatrolled, Extended confirmed users, Template editors1,001,183 edits →To orphan: redirected, so now merged | ||
Line 1: | Line 1: | ||
<includeonly>{{Transcluded section|source=Misplaced Pages:Templates for discussion/Holding cell}} | <includeonly>{{Transcluded section|source=Misplaced Pages:Templates for discussion/Holding cell}} | ||
</includeonly><noinclude>{{bots|deny=SineBot}}{{ |
</includeonly><noinclude>{{bots|deny=SineBot}}{{Backlog}}{{Shortcut|WP:TFD/H}}{{Deletion debates}}</noinclude> | ||
{{backlog}} | |||
'''If''' process guidelines are met, move templates to the appropriate subsection '''here''' to prepare to delete. Before deleting a template, ensure that it is not in use on any pages (other than talk pages where eliminating the link would change the meaning of a prior discussion), by checking ] for '(transclusion)'. Consider placing {{t1|Being deleted}} on the template page. | '''If''' process guidelines are met, move templates to the appropriate subsection '''here''' to prepare to delete. Before deleting a template, ensure that it is not in use on any pages (other than talk pages where eliminating the link would change the meaning of a prior discussion), by checking ] for '(transclusion)'. Consider placing {{t1|Being deleted}} on the template page. | ||
===Tools=== | |||
There are several tools that can help when implementing TfDs. Some of these are listed below. | |||
* – Toolforge tool to see which pages are transcluded but not linked from or to a template | |||
* ] – user script that allows for template use to be viewed from the ] page | |||
* ] – semi-automatic editor that can replace or modify templates using ] | |||
* ] – robots editing automatically. All tasks have to be ] before operating. There are currently five bots with general approval to assist with implementing TfD outcomes: | |||
** ] – substituting templates via ] | |||
** ] – general TfD implementation run by ] | |||
** ] – general TfD implementation run by ] | |||
** ] – general TfD implementation run by ] | |||
** ] – general TfD implementation run by ] | |||
===Closing discussions=== | ===Closing discussions=== | ||
Line 16: | Line 27: | ||
* {{tfdl|template name|log date (YYYY Month DD)}} | * {{tfdl|template name|log date (YYYY Month DD)}} | ||
If empty, add * ''None currently'' below this comment. --> | If empty, add * ''None currently'' below this comment. --> | ||
*{{tfdl| |
*{{tfdl|Infobox_tropical_cyclone|2024 March 10|section=Weather infoboxes}} | ||
*{{tfdl| |
*{{tfdl|Infobox_storm|2024 March 10|section=Weather infoboxes}} | ||
*{{tfdl| |
*{{tfdl|WikiProject_Glass|2024 November 5|section=Template:WikiProject Glass}} | ||
*{{tfdl| |
*{{tfdl|PIE|2024 December 3|section=Template:PIE}} | ||
**Instances should be replaced with <code><nowiki>{{lang|ine-x-proto}}</nowiki></code>. If the instance contains a phrase or sentence, <code>|proto=no</code> should be added to suppress the asterisk. <span style="white-space: nowrap;">—] <sup>(]·])</sup></span> 14:17, 16 December 2024 (UTC) | |||
*{{tfdl|Fb_r_footer|2018 April 28|section=Template:Fb r}} | |||
*{{tfdl|Fb_r|2018 April 28|section=Template:Fb r}} | |||
*{{tfdl|Fb_cl2_team|2018 April 19|section=Mass Fb cl templates}} | |||
*{{tfdl|Fb_cl2_header_navbar|2018 April 19|section=Mass Fb cl templates}} | |||
*{{tfdl|Fb_cl_header|2018 April 19|section=Mass Fb cl templates}} | |||
*:Would it be possible for a bot to convert the transclusions of these templates to ]? ] (]) 23:50, 28 April 2018 (UTC) | |||
*::Should be doable, yes. ] (]) 00:22, 29 April 2018 (UTC) | |||
*:::I could probably do something while I am converting all the {{tld|Fb team}} templates. But, I will have to see how complicated the code is. Thanks! ] ] 00:36, 29 April 2018 (UTC) | |||
*::::{{ping|Plastikspork|Primefac}} Can your bots using ] instead in this case, such as ? ] (]) 04:14, 29 April 2018 (UTC) | |||
*:::::], sure. That particular template only had one use, and that use was in userspace, and the title of the page was "concept", so I didn't bother to fully convert it. But in general, the plan is to convert the various table/cl header/cl footer/cl team templates to use sports table. Thanks! ] ] 12:41, 29 April 2018 (UTC) | |||
*:::::: I am replacing all of these fb templates ] (]) 15:08, 20 February 2019 (UTC) | |||
*Merge into {{t|Aircraft specs}}: | |||
**{{tfdl|Aerospecs|2019 March 20|section=Template:Aerospecs}} | |||
**{{tfdl|Aircraft_specifications|2019 March 20|section=Template:Aerospecs}} | |||
*::There's a discussion about this merger at ] --] (]) 15:52, 8 August 2019 (UTC) | |||
*For merging into {{t|Yesno}} - will need heavy sandboxing: | |||
**{{tfdl|If_affirmed|2019 March 19|section=Template:If affirmed}} | |||
*::{{u|Primefac}} You indicated that you had some kind of idea how this merger may be done while closing this discussion with the first step being making a If affirmed/declined a yesno wrapper. I've done that in the sandboxes, but as you can see in the testcases it does change the value for a not insignificant amount of values. Are we supposed to go through each and every template that uses if affirmed/declined to see if it breaks anything and if it doesn't substitute it in? Do anyone have a better plan? -- ] (]) 21:38, 18 July 2019 (UTC) | |||
*:::I don't see your changes to {{tl|Yesno/sandbox}}. If you don't change the source, then the template won't know what the "yes" and "no" values are. --] (]) 21:53, 18 July 2019 (UTC) | |||
*::::Sorry if I were unclear, I meant ] and ] is where I've made a simple wrapper version. This will inevitably lead to some output differences if we don't change YesNo directly but I don't believe we have consensus to do so. Several people in the TfD thought we shouldn't touch YesNo and last time a RfC was required before they added on and off. -- ] (]) 22:28, 18 July 2019 (UTC) | |||
*:{{tl|if affirmed}} is basically done, just 750ish transclusions from broken substitutuion of {{tl|welcome cookie}}. Could someone with a TfD bot go through these replacing <syntaxhighlight>{{ {{{\|safesubst:}}}if affirmed\|{{{notalk\|}}} \| \| ask me on {{ {{{\|safesubst:}}}ifsubst \| \] \| my talk page }} or }}(*\*)</syntaxhighlight> with <syntaxhighlight>{{subst:if affirmed|{{{notalk|}}} | | ask me on {{subst:ifsubst | ] | my talk page }} or }}$1$2</syntaxhighlight>. There seems to be a few more cases left, but this should be the vast majority. Regex is tested and there is no way this will cause false positives. --] (]) 10:00, 30 September 2019 (UTC) | |||
*::Will get to this in the next few days. ] (]) 19:24, 30 September 2019 (UTC) | |||
*{{tfdl|Ctime:06|2019 March 8}} - see ] | |||
*{{t|link language}} wrappers - listed at ], see ] for full close. In short - wrappers should be orphaned; first from template use (see §4 of LLWRAP) then article space. | |||
*:Wouldn't this be solved by just making all of them auto-substitute? The templates are so simple that they're already substituable. --] (]) 16:02, 4 August 2019 (UTC) | |||
*::That is certainly possible for most of them. I do highly suggest you actually read through the discussion before just slapping a one-size-fits-all solution to almost 300 templates; some of them are not direct wrappers and some of them have extra content that may need to be considered. Additionally, ''all'' of them have a commented-out section giving the language - this should not be subst'ed. ] (]) 16:15, 4 August 2019 (UTC) | |||
*:::I have read it and will check that they actually are only a direct wrapper (using regex). before adding auto substitute, but if that is enough for 90% of them that's what I'll do after dealing with the unprotected templates. I also wonder what I should replace them with. I feel like In lang would be the best choice, but since this wasn't even a redirect an hour ago and there were so many opinions about it I thought it would be best asking you. --] (]) 17:50, 4 August 2019 (UTC) | |||
*::::Sorry if I implied that you were going to rashly jump into this; thanks for being cautious. I would say that for anything that isn't protected and/or has <50 uses, {{t|language link}} would be fine to use in the wrapper (i.e. they can pretty much stay unchanged). I'll have to have a think about the higher-use ones, though; in particular, I'm going to look at the {{t|ill}} merger and how we dealt with combining multiple templates with very long names. ] (]) 18:16, 4 August 2019 (UTC) | |||
*:{{tlx|in lang}} with rudimentary documentation created. | |||
*:—] (]) 13:58, 6 August 2019 (UTC) | |||
*: | |||
*:I don't know what a {{tq|substitution forcer file}} is, but I would suggest that if the list at {{slink|Misplaced Pages:Templates_for_discussion/Log/2019_June_9/Link_language_wrappers#Templates_with_above_100_transclusions}} is intended to identify templates that should be substed from one template to another template, then that list is flawed. There are templates listed there that are also listed at {{slink|Misplaced Pages:Templates_for_discussion/Log/2019_June_9/Link_language_wrappers#Non-standard_templates}}. | |||
*:—] (]) 15:46, 6 August 2019 (UTC) | |||
*:: AnomieBOT require templates with over 100 transclusions to be added to ] for them to be auto substituted. I thought it would be useful having a list when that time comes. The first step will of course be fixing the unusual templates before starting substituting them. --] (]) 15:55, 6 August 2019 (UTC) | |||
*:::Is that even the right tool to use? Substing {{tlx|de icon}} templates will return <code><nowiki>{{link language|de}}<!--German--></nowiki></code> (I'm not sure how categories are handled in these kinds of cases). But, if the intent of this whole thing was to replace the icon templates with a more appropriately named template (which {{tlx|link language}} is not) then how is the AnomieBot task the correct task? One task to troll through and subst all of the various icon templates and then another to subst all of the {{tld|link language}} templates? Is that safe? Are there cases where {{tld|link language}} is used natively where changing those transclusions to {{tld|in lang}} would be the wrong thing? | |||
*:::—] (]) 16:28, 6 August 2019 (UTC) | |||
*::::I was planning on doing an AWB run to make sure all templates are only transcluding {{tlp|link language|langcode}} or whatever redirect we decide on using and then let AnomieBOT substitute it, which I think would do the job. The categories are handled by the template and removing the comments would not affect them. I'm not sure what's happening with {{tl|in lang}}. It was only a redirect to link language a couple of days ago and I thought that was the intent based on the closing comment. Why do we have two templates doing the same thing now? Updating the original template would be better if you want to implement new features. --] (]) 16:53, 6 August 2019 (UTC) | |||
*:::::The only consensus reached is for removal of the wrapper templates: the various {{tld|<{{var|xx}}> icon}} templates change to something. The close doesn't say to what those templates are to be changed. One might infer that they are to be 'unwrapped' to reveal the inner template which may not necessarily be {{tlx|link language}}; I suspect that to be the most common (and likely only) template that has been wrapped for this application. The use of {{tlx|LL}} as a redirect is addressed to the extent that a ] is required to do anything about it (an implicit no consensus). As a result of this RFC, {{tlx|in lang}} was created as a redirect to {{tld|link language}} but never used for that purpose (redirect because no consensus to rename {{tld|link language}}). I converted that redirect to a template as a way out of the mire that the fourth bullet item and definitive no-consensus declaration leaves us in: | |||
*::::::explicit consensus to remove (from article space) {{tld|<{{var|xx}}> icon}} wrapper templates (first bullet point in the close) | |||
*::::::explicit no consensus to delete the wrapper templates (fourth bullet point in the close) | |||
*::::::consensus / no consensus not stated with regard to deprecation of the wrapper templates (implicit no consensus) | |||
*:::::What point is there to removing the wrapper templates from article space if we don't have a consensus to do anything with the wrapper templates themselves once the transclusions are removed from article space? We don't have a consensus for deletion yet the wrapper templates are marked with {{tlx|being deleted}} templates which contradicts the fourth bullet item in the close; both conditions cannot simultaneously exist (deleting something that we don't have consensus to delete). The close is mute on deprecation so apparently we don't have consensus for that either. | |||
*:::: | |||
*:::::So, a new template with enhanced features and different categories to replace any-and-all uses of the wrapper templates. This, I think, meets the single consensus we do have, to remove the wrapper templates from article space. A new template is not constrained by the contradictions of the close. The wrapper templates are left to be deleted in dribs and drabs as anticipated in the close. | |||
*:::: | |||
*:::::To answer your question: {{tq|Why do we have two templates doing the same thing now?}} Yeah, there are two templates doing similar things; the original is constrained by the decisions (and lack of decisions) of an inconclusive RFC. The new is not constrained by that RFC and can be used to replace the wrapper templates in article space in compliance with the one consensus decision achieved by the RFC; the new template has features that the original does not: {{para|link}}, {{para|cap}}, multiple language support; the new template fills different categories; the new template name is consistent with what it does (preceding text – may or may not be a link – refers to something that is written in <{{var|language name}}>); the new template does {{em|not}} support {{para|cat-lang}} for the reasons stated at {{slink|Template_talk:Link_language#the_cat-lang_parameter}}. | |||
*:::::—] (]) 22:31, 6 August 2019 (UTC) | |||
*:Since there has been no further comment I have done these things: | |||
*:#written ] | |||
*:#created as a test bed: | |||
*:##{{cl|Articles with non-English-language sources}} – parent category for sub-cats: | |||
*:##:{{cl|Articles with Abkhazian-language sources (ab)}} et al; | |||
*:##] – documentation template for sub-cats; | |||
*:without objection I shall: | |||
*:#start a ] for Monkbot/task 15 | |||
*:#create additional sub-categories in Category:Articles with non-English-language sources according to those categories in {{cl|Articles with non-English-language external links}} that are not empty | |||
*:#when approved, run Monkbot/task 15 to replace {{tld|<{{var|xx}}> icon}} and redirects with {{tlx|in lang|<{{var|xx}}>}} | |||
*:—] (]) 14:18, 12 August 2019 (UTC) | |||
*::I don't approve of having both {{tl|link language}} and {{tl|in lang}} doing the same thing. {{tl|link language}} should be updated and then {{tl|in lang}} be redirected. Other than that I think it sounds good. --] (]) 14:28, 12 August 2019 (UTC) | |||
*:::Nor do I approve, however, they are not doing the same thing. It is true they are doing similar things but {{tl|in lang}} is about sources and allows multiple languages to be references whereas {{tl|link language}} is for only external links (which "sources" might be considered to include) and does not allow multiple languages. The latter also has a few issues with some extra parameters allowing strange categorizations. So in shorts {{tl|in lang}} was resigned without the historic constraints imposed upon {{tl|link language}} allowing it to be more flexible and potentially more things (if it is ever widely deployed to so such). If anything, after most of these transclusions have been updated to use {{tl|in lang}}, {{tl|link language}} could be updated to use/redirect to {{tl|in lang}} (or just be deleted outright with the rest of the templates targeted by this RFC decision). ] (]) 02:39, 30 August 2019 (UTC) | |||
*::::I'm confused. You start out by saying {{tq|Nor do I approve}} but then appear to talk yourself around to suggesting that the {{tlx|in lang}} should be deployed as I have outlined above. So which is it? | |||
*::::—] (]) 11:48, 30 August 2019 (UTC) | |||
*{{u|Trappist the monk}} There are now four templates using cat-lang after I fixed the easy ones a while ago: {{tl|bal icon}}, {{tl|ilo icon}}, {{tl|nan icon}} and {{tl|ksh icon}}. I think there are really two ways to handle this, either starting a CfD to change the names of these categories or modify ]. When this situation is dealt with we should sync with your improved link language template and then make sure all templates subsitute properly and then finally use AnomieBOT to mass subsitute these and then delete them. --] (]) 20:21, 30 September 2019 (UTC) | |||
*:Your posting above is merely pro forma since you have already set AnomieBOT to work? | |||
*: | |||
*:I think that you meant {{tlx|bla icon}} not {{tlx|bal icon}}. | |||
*:—] (]) 22:49, 30 September 2019 (UTC) | |||
*::I set it up for a few templates all with few transclusions. It was mearly for testing and if there's consensus to do it some other way it can be reverted. Based on those tests it worked exactly as expected. I'm ready to do the rest if you think my course of action is suitable. --] (]) 22:55, 30 September 2019 (UTC) | |||
*:::Apparently we are at deadlock because you object to {{tlx|link language}} (which, it appears, you wish to retain) and {{tlx|in lang}} existing simultaneously. I object to continued support of {{tld|link language}} (which I want to go away) because the text that {{tld|link language}} associates with in article text is often not a link. You think that all of the wrapper templates should be subst'd to {{tld|link language}} and I think that the wrapper templates should be replaced with {{tld|in lang}}. You did write above when discussing this topic with Editor ]: {{tq|I also wonder what I should replace them with. I feel like In lang would be the best choice, but since this wasn't even a redirect an hour ago and there were so many opinions about it I thought it would be best asking you}} so perhaps we aren't at deadlock and are talking past each other. | |||
*:: | |||
*:::Still, at the moment, I don't see any consensus here to do anything there being only two of us participating. | |||
*:::—] (]) 13:57, 1 October 2019 (UTC) | |||
*::::Why is it a problem that not all uses of link language are associated with a link? How would that problem be solved by using in lang? Since they have the same output I don't see any reason to keep them separate. I intend on starting another deletion discussion exclusively dealing with very low transclusion wrappers to gain consensus to delete wrappers under 50 transclusions. The arguments for keeping the wrappers don't apply to these and would be helpful for getting rid of a significant chunk of them. --] (]) 15:45, 1 October 2019 (UTC) | |||
*:::::The problem is one of semantics. These are taken from ]: | |||
*::::::<code><nowiki>* A. Klugmann, '''' (1875) {{de icon}}</nowiki></code> | |||
*::::::<code><nowiki>* H.L. Krause, ''Die Amazonensage'' (1893) {{de icon}}</nowiki></code> | |||
*::::::* A. Klugmann, '''' (1875) {{de icon}} | |||
*::::::* H.L. Krause, ''Die Amazonensage'' (1893) {{de icon}} | |||
*:::::These sort-of-work for both cases because {{tlx|de icon}} isn't specific about what kind of text precedes the template. Change {{tld|de icon}} to {{tlx|link language|de}} and the first example works because there is a link to a German-language source. The same cannot be said for the second example because there is no link. | |||
*:::: | |||
*:::::Change {{tld|de icon}} to {{tlx|in lang|de}} and both examples work because {{tld|in lang|de}} does not refer to links but does refer to the language of the sources. Editors are often 'literal' and are confused by template names that do not accurately reflect what the template does (one of the reasons that {{tld|de icon}} and similar are not well named – template doesn't produce an 'icon', this is the sort-of-works that I mentioned above) so an editor reading the wikitext of the second example where {{tld|de icon}} has been changed to {{tlx|link language|de}} may be confused by that because the second example does not have a link. | |||
*:::: | |||
*:::::Isn't it first necessary to decide what those {{tq|wrappers under 50 transclusions}} are to be replaced with before you charge off and delete them? Why are you in such a rush? | |||
*:::::—] (]) 16:43, 1 October 2019 (UTC) | |||
*::::::I am fine with using in lang as the template name. If we turned {{tl|in lang}} into a redirect that would indeed be my optimal outcome. Can we start working on removing the last few cat-lang uses so we can redirect it now? Regarding the TfD: The main reason is that I kind of messed up yesterday CSDing 4 unused templates thinking there was an exception to the deletion no consensus for unused templates. A TfD would be a solution to this, but I guess they would also fall under ]. I will discuss with the deleting admin ({{u|Justlettersandnumbers}}) to see what they think I should do. --] (]) 17:02, 1 October 2019 (UTC) | |||
*:::::::OK, I was pinged. Were those mistaken nominations, {{u|Trialpears}}? If so, they can easily be restored – just say the word! (oh, and give me the page titles if you have them handy). ] (]) 19:41, 1 October 2019 (UTC) | |||
*::::::::{{u|Justlettersandnumbers}} Yep they were mistaken, the discussion didn't actually reach a consensus to delete any of the templates, not even these unused ones. I think they would fall under ] and will probably tag them so they can be deleted after the 7 day hold. Please undelete {{tl|Av icon}}, {{tl|Arn icon}}, {{tl|Ak icon}}, {{tl|Als icon}} and {{tl|Ajt icon}}. --] (]) 21:42, 1 October 2019 (UTC) | |||
*:::::::::{{done}}. ] (]) 10:00, 2 October 2019 (UTC) | |||
*:::::::If you are {{tq|fine with using in lang as the template name}}, what is the point of redirecting it? If we are settled that the template name shall be {{tlx|in lang}}, then the task ahead is to replace all instances of {{tlx|link language}} (and all of its redirects) with {{tld|in lang}}. Deletion of {{tld|link language}} (and all of its redirects) as unused to follow. What then, is the point of a making {{tld|in lang}} into a redirect? | |||
*:::::::—] (]) 11:49, 2 October 2019 (UTC) | |||
*::::::::If you prefer to redirect in the opposite directions that's by all means fine by me. As long as the end result is one template. --] (]) 12:20, 2 October 2019 (UTC) | |||
*:Just to move this along, I support Trappist's proposal of replacing the icon templates with the new one. --] (]) 14:31, 2 October 2019 (UTC) | |||
*::I still think that Trappist's solution is more complicated than necessary, leaving the inevitable merger of these identical templates for later will cause more work overall and replacing it with another template is a bit dubious when the consensus was "Merge to Link Language". I'm however confident that the end result will be basically the same either way and won't block the proposed implementation. --] (]) 16:11, 2 October 2019 (UTC) | |||
*:With regard to: | |||
*::{{tlx|bla icon}} see {{slink|Talk:Blackfoot_language#language_naming_inconsistencies}} | |||
*::{{tlx|ilo icon}} see {{slink|Talk:Ilocano_language#language_naming_inconsistencies}} | |||
*::{{tlx|ksh icon}} see {{slink|Talk:Ripuarian_language#language_naming_inconsistencies}} | |||
*::{{tlx|nan icon}} see {{slink|Talk:Taiwanese_Hokkien#language_naming_inconsistencies}} | |||
*:—] (]) <s>16:01, 4 October 2019 (UTC)</s> (bla) <s>18:34, 4 October 2019 (UTC)</s> (ilo) <s>17:16, 5 October 2019 (UTC)</s> (ksh) 14:56, 6 October 2019 (UTC) (nan) | |||
*::{{slink|Wikipedia_talk:WikiProject_Languages#language_naming_inconsistencies}} | |||
*::—] (]) 15:02, 6 October 2019 (UTC) | |||
===To merge=== | ===To merge=== | ||
{{anchor|m}} | {{anchor|m}} | ||
Templates to be merged into another template. | Templates to be merged into another template. | ||
<!-- list begin (leave this here); please link to the per-day page that has the discussion on it. | <!-- list begin (leave this here); please link to the per-day page that has the discussion on it. | ||
Use the format: | Use the format: | ||
* {{tfdl| |
* {{tfdl|bad template|log date (YYYY Month DD)|section=Template:bad template}} - merge into {{tl|good template}} | ||
or | or | ||
* log date (YYYY Month DD) – explanation | * log date (YYYY Month DD) – explanation | ||
or | |||
* {{tl|template name}} merger: | |||
** {{tfdl|template 1|YYYY Month DD|section=Template:bad template}} | |||
** {{tfdl|template 2|YYYY Month DD|section=Template:bad template}} | |||
--> | --> | ||
====Arts==== | |||
* ''None currently'' | |||
====Geography, politics and governance==== | |||
*{{tfdl|WikiProject_Oregon_government|2019 September 16|section=Template:WikiProject Oregon government}} | |||
*{{tfdl|WikiProject_Oregon|2019 September 16|section=Template:WikiProject Oregon government}} | |||
==== |
====Infoboxes==== | ||
*Merge into the singular {{t|infobox ship}} (currently a redirect): | |||
*{{tfdl|Antipopes|2019 August 13|section=Template:Antipopes}} | |||
*{{tfdl| |
**{{tfdl|Infobox_ship_begin|2022 April 30|section=Template:Infobox ship begin}} | ||
*{{tfdl| |
**{{tfdl|Infobox_ship_career|2022 April 30|section=Template:Infobox ship begin}} | ||
*{{tfdl| |
**{{tfdl|Infobox_ship_characteristics|2022 April 30|section=Template:Infobox ship begin}} | ||
**{{tfdl|Infobox_ship_class_overview|2022 April 30|section=Template:Infobox ship begin}} | |||
**{{tfdl|Infobox_ship_image|2022 April 30|section=Template:Infobox ship begin}} | |||
**{{tfdl|Infobox_service_record|2022 April 30|section=Template:Infobox ship begin}} | |||
**:I have hacked ] which implements ship infoboxen without the external wikitable that the above templates require. Uses ]; {{tlx|infobox ship begin}} is no longer required; parameter names are changed from sentence- to snake-case; section header height for career, characteristics, service record sections is normalized; ] are supported. I chose to retain the individual section templates as subtemplates: | |||
**:*{{tlx|Infobox ship/image}} | |||
**:*{{tlx|Infobox ship/career}} | |||
**:*{{tlx|Infobox ship/characteristic}} | |||
**:*{{tlx|Infobox ship/class}} | |||
**:*{{tlx|Infobox ship/service record}} – Module:Infobox ship implements only the 'ship' portion of {{tlx|Infobox service record}} | |||
**:In the main infobox these subtemplates are called with the {{para|section<{{var|n}}>}} parameters (aliases of {{para|data<{{var|n}}>}}). | |||
**: | |||
**:Comparisons between wikitable infoboxen and Module:Infobox ship infoboxen can bee seen at ]. | |||
**:—] (]) 14:57, 21 May 2022 (UTC) | |||
**::Since the intent is to use ] directly, why is ] being used to generate the infobox? I can understand if there is need for a backend module to validate a value or something, but is there really a reason to have this unique code? ] (]) 17:50, 21 May 2022 (UTC) | |||
**:::The original complaint was that the ship infoboxen templates are {{tq|table templates masquerading as infobox templates}}. None of those templates use ]. ] answers that complaint. Yeah, we still have subtemplates, but, in my opinion, that is a good thing because the appropriate parameters and their data are contained in each particular subtemplate. The container subtemplates make it relatively easy for an editor reading an article's wikitext to understand. The current ship infobox system allows sections in any order (except for the position of {{tlx|infobox ship begin}} – not needed with Module:Infobox ship); whatever the final outcome of this mess, that facility must not be lost. | |||
**::: | |||
**:::Module:Infobox ship does do some error checking (synonymous parameters {{para|ship_armor}} / {{para|ship_armour}}, {{para|ship_draft}} / {{para|ship_draught}}, {{para|ship_honors}} / {{para|ship_honours}}, and {{para|ship_stricken}} / {{para|ship_struck}}). Whether {{tld|infobox ship}} directly calls Module:Infobox or whether {{tld|infobox ship}} calls Module:Infobox ship which then calls Module:Infobox is really immaterial so long as the final rendered result is a correctly formatted infobox. | |||
**:::—] (]) 19:06, 22 May 2022 (UTC) | |||
**::::@] are you still interested in working on this Module? If not, I'd like to try to get it finished myself. The massive deviation I had in mind was to make one invocation of the module do everything. Each page will require individual attention to complete the merge into a proper infobox anyway, so I reason to go the extra mile to make it nicer in general. Repeatable parameters will have the normal ''n'' number appended to the end of the parameter. An alternative would be to have subboxes for repeating sections, which would be easier in general to replace and implement. ] (]) 20:26, 20 August 2022 (UTC) | |||
**:::::Sure, but I don't think that this page is the proper place to discuss. Choose some place more proper and let me know where that is? | |||
**:::::—] (]) 22:58, 20 August 2022 (UTC) | |||
*Replacement with {{t|Infobox aircraft}}: | |||
**{{tfdl|Infobox_aircraft_type|2023 January 22|section=Template:Infobox aircraft begin}} | |||
**{{tfdl|Infobox_aircraft_career|2023 January 22|section=Template:Infobox aircraft begin}} | |||
**{{tfdl|Infobox_aircraft_program|2023 January 22|section=Template:Infobox aircraft begin}} | |||
**{{tfdl|Infobox_aircraft_begin|2023 January 22|section=Template:Infobox aircraft begin}} → {{tl|Infobox aircraft}} | |||
**{{tfdl|Infobox_aircraft_engine|2023 January 22|section=Template:Infobox aircraft begin}} → {{tl|Infobox aircraft}} | |||
***For {{t|Infobox aircraft engine}}, There is an ] about whether the aircraft engine Infobox should be merged with the Infobox aircraft or not. Except for the engine Infobox, other Infoboxes can be orphaned and there are no objection for that. ] (]) 22:39, 22 May 2023 (UTC) | |||
****This discussion is still ongoing, so I have moved it back to the "to merge" list with the others. ] (]) 10:09, 1 June 2023 (UTC) | |||
****The discussion has now ended (), with the consensus '''NOT TO MERGE''' {{tl|Infobox aircraft engine}} with the others. However {{tl|infobox aircraft begin}} may or may not end up being merged into {{tl|Infobox aircraft engine}}. The template pages should be updated accordingly. — Cheers, ] (]) 10:07, 6 August 2023 (UTC) | |||
*{{tfdl|Infobox_climber|2024 June 29|section=Template:Infobox climber}} | |||
*{{tfdl|Infobox_mountaineer|2024 June 29|section=Template:Infobox climber}} | |||
*Merge into {{tl|Infobox NFL biography}} and rename to {{tl|Infobox gridiron football biography}} | |||
**{{tfdl|Infobox_Canadian_Football_League_biography|2024 November 18|section=Template:Infobox Canadian Football League biography}} | |||
**{{tfdl|Infobox_NFL_biography|2024 November 18|section=Template:Infobox Canadian Football League biography}} | |||
**{{tfdl|Infobox_gridiron_football_person|2024 November 18|section=Template:Infobox Canadian Football League biography}} | |||
==== |
====Navigation templates==== | ||
* ''None currently'' | * ''None currently'' | ||
==== |
====Link templates==== | ||
*{{tfdl|Lx|2023 October 1|section=Template:Lx}} | |||
* ''None currently'' | |||
*{{tfdl|Pagelinks|2023 October 1|section=Template:Lx}} | |||
**Because Lx has the option to hide certain links and PageLinks itself doesn't, a direct merge is impossible. The next best thing would be to convert the transclusions to invocations of ]. Doesn't look too impossible at first glance. ] (] '''·''' ] '''·''' ]) 00:20, 14 January 2024 (UTC) | |||
**:Problem: Lx's 20,000 transclusions are kinda fake, because almost all of them are transclusions of transclusions. <br/>Even if we restrict it to the template namespace, most of {{em|those}} are transclusions of transclusions of transclusions in the doc subpage. ] (] '''·''' ] '''·''' ]) 00:38, 14 January 2024 (UTC) | |||
**::The more I look at this, the more it appears technically infeasible. Lx has some really bizarre arguments like tag and label which can't be replicated by Module:PageLinks. When Lx was used to link to a normal page, namespace is usually Talk and label is usually talk, but when it's used to link to a talk page, either could be anything. Also, the recursive transclusion issue means the only way to get our pages would be an insource search, which means we'd also have to deal with ].{{pb}}Replacing all uses of the format <code><nowiki>\{\{x\|1=\|2=(.*)\|3=Talk\|4=talk\}\}</nowiki></code> with <code><nowiki>{{Pagelinks|$1}}</nowiki></code> could be a start. From there, I'm totally lost. ] (] '''·''' ] '''·''' ]) 16:23, 14 January 2024 (UTC) | |||
**:::What if we only replaced , and then substed everything else? ] (] '''·''' ] '''·''' ]) 19:53, 15 January 2024 (UTC) | |||
**::::I have officially responded in less than a year. First, which only cares about direct uses of {{t|Lx}}, not other things like {{t|Lxg}}. To your question, what if we make those replacements and see where we are at, transclusion-wise? Once those transclusions of transclusions of translcusions of transclusioons are at least reduced, we can see what else needs evaluation. It will take a while for the ] to catch up and give us an accurate picture of where we are left, so I might do that sooner rather than later... <b>]]</b> (] • he/they) 06:07, 1 January 2025 (UTC) | |||
*{{tfdl|See_also_if_exists|2024 December 13|section=Template:See also if exists}} | |||
*{{tfdl|See_also|2024 December 13|section=Template:See also if exists}} | |||
**Requires an admin for ] ] (]) 15:30, 3 January 2025 (UTC) | |||
====Other==== | ====Other==== | ||
*{{tfdl|Football_squad_player2|2020 February 1|section=Template:Football squad player2}} and {{tfdl|Football_squad_player|2020 February 1|section=Template:Football squad player2}} | |||
*{{tfdl|Rfam_box|2019 April 5|section=Template:Rfam box}} | |||
** '''Note''' Pending ] ] (]) 18:51, 11 April 2020 (UTC) | |||
**{{tfdl|Infobox_rfam|2019 April 5|section=Template:Rfam box}} | |||
*** I've closed the RfC. ] (]) 15:15, 3 May 2020 (UTC) | |||
***{{tl|Rfam_box}} is now a wrapper, needing ''subst''ing and cleanup. <span class="vcard"><span class="fn">]</span> (<span class="nickname">Pigsonthewing</span>); ]; ]</span> 11:28, 23 September 2019 (UTC) | |||
** |
**At this point this is ready for large scale replacement. I said a while ago that I could do it but due to me being quite busy IRL this seems unlikely to get done in a timely manner. If you feel like doing a large scale replacement job feel free to take this one. --] (]) 17:34, 2 February 2021 (UTC) | ||
***], what large-scale replacement? I (foolishly?) jumped into this rabbit hole, and have been in it for over a day now. This is a very complex merge; I've got to show fewer differences, but there's still more to be done. – ] (]) 15:04, 14 February 2021 (UTC) | |||
*{{tfdl|Infobox_time_zone_UTC|2019 June 29|section=Template:Infobox time zone UTC}} | |||
*{{tfdl| |
*{{tfdl|Auto_compact_TOC|2023 March 6|section=Template:Auto compact TOC}} | ||
*{{tfdl|Compact_TOC|2023 March 6|section=Template:Auto compact TOC}} | |||
*: Note that while no one objected ''in principle'' to the merging of these two "time zone" templates, it is also true that no one has demonstrated how the merge would actually be accomplished ''in practice''. One user has ] to perform the merge. Personally, I looked at ] before the merge nomination was made, and eventually gave up on the idea since it looked like it was going to be too time consuming to actually do. It is not clear at this point who will be willing and able to successfully complete this merge. - ] (]) 23:08, 16 July 2019 (UTC) | |||
*{{tfdl|Wikisource author|2023 July 5|section=Template:Wikisource author}} | |||
*::I'll take care of it if no one else gets to it first. I've done a lot of these over the years. ] (]) 13:20, 17 July 2019 (UTC) | |||
*{{tfdl|Wikisourcelang|2023 July 5|section=Template:Wikisource author}} | |||
*:::], I think something went wrong here. There are fundamental differences between IANA time zones, UTC offset zones, and what is commonly known as "time zone". Please reconsider your nomination. ] (]) 12:57, 28 July 2019 (UTC) | |||
**Hi now that {{t|Wikisourcelang}} is being merged, how do I use the merge target template to point to sister language Wikisources? All the links keep incorrectly pointing to the English version and the documentation of {{t|Wikisource}} has not been updated about this. ] (]) 20:16, 11 August 2023 (UTC) | |||
***{{u|Folly Mox}}, the merge has not yet been completed, so you should use the appropriate currently-existing template to do whatever it is you are planning until the merge is complete. The existing uses will be converted appropriately at that time. ] (]) 09:00, 14 August 2023 (UTC) | |||
****Oops, I forgot I had posted here. My assertion was incorrectly based on the first instance I had tested, which had been misusing parameters in such a way that it worked prior to the start of the merge process but not afterwards. The links to en.s/lang:page do properly redirect if the parameters are used correctly, but I didn't initially follow the links to check. It was quite an embarrassing hour or so of my contribution history. ] (]) 13:00, 14 August 2023 (UTC) | |||
*{{tfdl|Wikisourcehas|2023 July 5|section=Template:Wikisource author}} | |||
**I see I am not supposed to use {{tl|Wikisourcehas}} on "additional padverages" so I have had to move to using {{tl|Sister project}} because {{tl|Wikisource}} does not have the required functionality. I shall look out for further developments because some very clever coding will be needed. ] (]) 13:13, 17 August 2023 (UTC) | |||
**For over a year now we have been instructed not to use {{t|Wikisource author}}, {{t|Wikisourcelang}} and {{t|Wikisourcehas}} and this is a nuisance because avoiding their use is not at all trivial. Can we have a report on progress with the merge, please, or permission to again use these templates? ] (]) 16:55, 12 July 2024 (UTC) | |||
***See Primefac's note above. Just keep using the existing templates. They will be converted for you during the merge process, whenever it happens (these merges sometimes take a while, as you can see above). When the conversion is done, the merged template will support the features that you need. That's how it's supposed to work, anyway. – ] (]) 19:01, 12 July 2024 (UTC) | |||
***:Thank you. That's helpful. Is there a change that could be usefully made to the display text in {{tl|being deleted}}? Or maybe the assumption is that no one reads beyond the first line anyway. ] (]) 20:41, 12 July 2024 (UTC) | |||
*{{tfdl|Facebook_page|2024 February 21|section=Template:Facebook page}} | |||
*{{tfdl|Facebook|2024 February 21|section=Template:Facebook page}} | |||
** While the result was "merge" it seems that this should be moved to "convert" as looking at ], the ID used there is "The-Kilborn-File/107748632605752", while the new one is at <code>https://www.facebook.com/profile.php?id=100082874612029</code>. The number is different. Unless I'm missing something else there is nothing here to merge. --] (]) 10:00, 15 March 2024 (UTC) | |||
*Merge into {{t|R_protected}}: | |||
**{{tfdl|R_fully_protected|2024 September 17|section=Template:R fully protected}} | |||
**{{tfdl|R_template-protected|2024 September 17|section=Template:R fully protected}} | |||
**{{tfdl|R_extended-protected|2024 September 17|section=Template:R fully protected}} | |||
**{{tfdl|R_semi-protected|2024 September 17|section=Template:R fully protected}} | |||
***In progress. ] (]) 11:11, 3 January 2025 (UTC) | |||
*{{tfdl|STN|2024 December 6|section=Template:STN}} | |||
*{{tfdl|Station|2024 December 6|section=Template:STN}} | |||
*{{tfdl|WPBASEBALL_assessment_level_category|2024 December 8|section=Template:WPBASEBALL assessment level category}} | |||
*{{tfdl|WPANIMATION_assessment_quality_work_group_level|2024 December 8|section=Template:WPBASEBALL assessment level category}} | |||
*{{tfdl|WikiProject_Television_task_force_assessment_category|2024 December 8|section=Template:WPBASEBALL assessment level category}} | |||
*{{tfdl|WPANIMATION_assessment_quality_work_group_level|2024 December 8|section=Template:WPBASEBALL assessment level category}} | |||
* {{tfdl|Articles by Quality|2024 December 20}} | |||
* {{tfdl|Category class|2024 December 20}} | |||
====Meta==== | ====Meta==== | ||
* ''None currently'' | |||
* Merge with ] | |||
**{{tfdl|Infobox name module|2017 April 7|section=Template:Infobox name module}} | |||
**{{tfdl|Infobox East Asian name|2017 May 26}} | |||
* Merge with ] | |||
**{{tfdl|Array_length|2019 February 20|section=Module:Array length|ns=Module}} | |||
*** Merged module written in sandbox (weeks ago). ] ] 03:01, 19 June 2019 (UTC) | |||
*{{tfdl|Vandal-m|2019 March 7|section=Module:Vandal-m|ns=Module}} | |||
*: Merged module written in sandbox (although much of the coded I added to ] should probably be in ] instead. ] (]) 15:13, 16 March 2019 (UTC) | |||
*::I've set up some {{oldid2|908855084|testcases}} and it outputs the same thing as the old one except for the autoblock thing which I assume was intentionl since it doesn't work. I think it could be completed now. --] (]) 13:37, 1 August 2019 (UTC) | |||
*::: Yes, removal of the broken autoblock link was intentional. ] ] 14:04, 1 August 2019 (UTC) | |||
*Merge into {{t|Copied}} | |||
**{{tfdl|Copied_multi|2019 August 10|section=Template:Copied multi}} | |||
**{{tfdl|Copied_multi/Merged-from|2019 August 10|section=Template:Copied multi}} | |||
**{{tfdl|Copied_multi/Copied|2019 August 10|section=Template:Copied multi}} | |||
**{{tfdl|Copied_multi/Afd-merged-from|2019 August 10|section=Template:Copied multi}} | |||
:::Could I claim this merger? I would like to convert this into my first module. It may take some time though since I have zero lua experience. --] (]) 18:53, 4 September 2019 (UTC) | |||
::::Go for it. Just makes sure you sandbox heavily and maybe have one of us check it before you go live. ] (]) 19:09, 4 September 2019 (UTC) | |||
*{{tfdl|Infobox_Italian_wine|2019 September 19|section=Template:Infobox Italian wine}} | |||
*{{tfdl|Infobox_wine_region|2019 September 19|section=Template:Infobox Italian wine}} | |||
*{{tfdl|WikiProject_Arabic_names|2019 September 16|section=Template:WikiProject Arabic names}} | |||
*{{tfdl|WikiProject_Anthroponymy|2019 September 16|section=Template:WikiProject Arabic names}} | |||
===To convert=== | ===To convert=== | ||
Line 193: | Line 151: | ||
* {{tfdl|template name|log date (YYYY Month DD)}} | * {{tfdl|template name|log date (YYYY Month DD)}} | ||
If empty, add * ''None currently'' below this comment. --> | If empty, add * ''None currently'' below this comment. --> | ||
* ] | |||
*{{tfdl|10years|2019 September 26|section=Template:10years}} | |||
** {{tfdl|R to related|2023 October 25}} - convert to {{t|R from related word}} or {{t|R to related topic}} as appropriate | |||
** Adding this from RfD as it's template related. --] (]) 21:45, 17 February 2024 (UTC) | |||
**: Started toying with this and came to the conclusion that I was very the wrong person because there are definitely cases where the appropriate template is neither of the two of interest. We need to leave this refinement on the user talk pages of some people who know what they're doing. ] (]) 22:20, 26 August 2024 (UTC) | |||
*{{tfdl|S-line/IT-Eurostar_left/Frecciabianca|2024 April 25|section=Frecciabianca s-line templates}} | |||
*{{tfdl|S-line/IT-Eurostar_right/Frecciabianca|2024 April 25|section=Frecciabianca s-line templates}} | |||
*{{tfdl|Adjacent_stations/Trenitalia|2024 April 25|section=Frecciabianca s-line templates|ns=Module}} | |||
===To ]=== | ===To ]=== | ||
{{anchor|s}} | {{anchor|s}} | ||
Templates for which the consensus is that all instances should be substituted ( |
Templates for which the consensus is that all instances should be substituted (e.g. the template should be merged with the article or is a wrapper for a preferred template) are put here until the substitutions are completed. After this is done, the template is deleted from template space. | ||
<!-- list begin (leave this here); please link to the per-day page that has the discussion on it. | <!-- list begin (leave this here); please link to the per-day page that has the discussion on it. | ||
Use the format: | Use the format: | ||
Line 207: | Line 171: | ||
{{anchor|o}} | {{anchor|o}} | ||
These templates are to be deleted, but may still be in use on some pages. Somebody (it doesn't need to be an administrator, anyone can do it) should fix and/or remove significant usages from pages so that the templates can be deleted. Note that simple references to them from Talk: pages should not be removed. Add on bottom and remove from top of list (oldest is on top). | These templates are to be deleted, but may still be in use on some pages. Somebody (it doesn't need to be an administrator, anyone can do it) should fix and/or remove significant usages from pages so that the templates can be deleted. Note that simple references to them from Talk: pages should not be removed. Add on bottom and remove from top of list (oldest is on top). | ||
<!-- list begin (leave this here); please link to the per-day page that has the discussion on it. | <!-- list begin (leave this here); please link to the per-day page that has the discussion on it. | ||
Use the format: | Use the format: | ||
Line 217: | Line 180: | ||
===Ready for deletion=== | ===Ready for deletion=== | ||
{{anchor|d}} | {{anchor|d}} | ||
Templates for which consensus to delete has been reached, and for which orphaning has been completed, can be listed here for an administrator to delete. Remove from this list when an item has been deleted |
Templates for which consensus to delete has been reached, and for which orphaning has been completed, can be listed here for an administrator to delete. Remove from this list when an item has been deleted. | ||
<!-- list begin (leave this here); use the format: | <!-- list begin (leave this here); use the format: | ||
* {{tfdl|template name|log date (YYYY Month D)|delete=1}} | * {{tfdl|template name|log date (YYYY Month D)|delete=1}} |
Latest revision as of 00:11, 4 January 2025
This page has a backlog that requires the attention of willing editors. Please remove this notice when the backlog is cleared. |
Deletion discussions |
---|
Articles |
Templates and modules |
Files |
Categories |
Redirects |
Miscellany |
Speedy deletion |
Proposed deletion |
If process guidelines are met, move templates to the appropriate subsection here to prepare to delete. Before deleting a template, ensure that it is not in use on any pages (other than talk pages where eliminating the link would change the meaning of a prior discussion), by checking Special:Whatlinkshere for '(transclusion)'. Consider placing {{Being deleted}} on the template page.
Tools
There are several tools that can help when implementing TfDs. Some of these are listed below.
- Template linking and transclusion check – Toolforge tool to see which pages are transcluded but not linked from or to a template
- WhatLinksHereSnippets.js – user script that allows for template use to be viewed from the Special:WhatLinksHere page
- AutoWikiBrowser – semi-automatic editor that can replace or modify templates using regular expressions
- Bots – robots editing automatically. All tasks have to be approved before operating. There are currently five bots with general approval to assist with implementing TfD outcomes:
- AnomieBOT – substituting templates via User:AnomieBOT/TFDTemplateSubster
- SporkBot – general TfD implementation run by Plastikspork
- PrimeBOT – general TfD implementation run by Primefac
- BsherrAWBBOT – general TfD implementation run by Bsherr
- PearBOT II – general TfD implementation run by Trialpears
Closing discussions
The closing procedures are outlined at Misplaced Pages:Templates for discussion/Closing instructions.
To review
Templates for which each transclusion requires individual attention and analysis before the template is deleted.
- Template:Infobox_tropical_cyclone2024 March 10 – Infobox_tropical_cyclone ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_storm2024 March 10 – Infobox_storm ( links | transclusions | talk | doc | sandbox | testcases )
- Template:WikiProject_Glass2024 November 5 – WikiProject_Glass ( links | transclusions | talk | doc | sandbox | testcases )
- Template:PIE2024 December 3 – PIE ( links | transclusions | talk | doc | sandbox | testcases )
- Instances should be replaced with
{{lang|ine-x-proto}}
. If the instance contains a phrase or sentence,|proto=no
should be added to suppress the asterisk. —Compassionate727 14:17, 16 December 2024 (UTC)
- Instances should be replaced with
To merge
Templates to be merged into another template.
Infoboxes
- Merge into the singular {{infobox ship}} (currently a redirect):
- Template:Infobox_ship_begin2022 April 30 – Infobox_ship_begin ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_ship_career2022 April 30 – Infobox_ship_career ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_ship_characteristics2022 April 30 – Infobox_ship_characteristics ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_ship_class_overview2022 April 30 – Infobox_ship_class_overview ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_ship_image2022 April 30 – Infobox_ship_image ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_service_record2022 April 30 – Infobox_service_record ( links | transclusions | talk | doc | sandbox | testcases )
- I have hacked Module:Infobox ship which implements ship infoboxen without the external wikitable that the above templates require. Uses Module:Infobox;
{{infobox ship begin}}
is no longer required; parameter names are changed from sentence- to snake-case; section header height for career, characteristics, service record sections is normalized; custom fields are supported. I chose to retain the individual section templates as subtemplates:{{Infobox ship/image}}
{{Infobox ship/career}}
{{Infobox ship/characteristic}}
{{Infobox ship/class}}
{{Infobox ship/service record}}
– Module:Infobox ship implements only the 'ship' portion of{{Infobox service record}}
- In the main infobox these subtemplates are called with the
|section<n>=
parameters (aliases of|data<n>=
). - Comparisons between wikitable infoboxen and Module:Infobox ship infoboxen can bee seen at my sandbox (permalink).
- —Trappist the monk (talk) 14:57, 21 May 2022 (UTC)
- Since the intent is to use Module:Infobox directly, why is Module:Infobox ship being used to generate the infobox? I can understand if there is need for a backend module to validate a value or something, but is there really a reason to have this unique code? Gonnym (talk) 17:50, 21 May 2022 (UTC)
- The original complaint was that the ship infoboxen templates are
table templates masquerading as infobox templates
. None of those templates use Module:Infobox. Module:Infobox ship answers that complaint. Yeah, we still have subtemplates, but, in my opinion, that is a good thing because the appropriate parameters and their data are contained in each particular subtemplate. The container subtemplates make it relatively easy for an editor reading an article's wikitext to understand. The current ship infobox system allows sections in any order (except for the position of{{infobox ship begin}}
– not needed with Module:Infobox ship); whatever the final outcome of this mess, that facility must not be lost. - Module:Infobox ship does do some error checking (synonymous parameters
|ship_armor=
/|ship_armour=
,|ship_draft=
/|ship_draught=
,|ship_honors=
/|ship_honours=
, and|ship_stricken=
/|ship_struck=
). Whether{{infobox ship}}
directly calls Module:Infobox or whether{{infobox ship}}
calls Module:Infobox ship which then calls Module:Infobox is really immaterial so long as the final rendered result is a correctly formatted infobox. - —Trappist the monk (talk) 19:06, 22 May 2022 (UTC)
- @Trappist the monk are you still interested in working on this Module? If not, I'd like to try to get it finished myself. The massive deviation I had in mind was to make one invocation of the module do everything. Each page will require individual attention to complete the merge into a proper infobox anyway, so I reason to go the extra mile to make it nicer in general. Repeatable parameters will have the normal n number appended to the end of the parameter. An alternative would be to have subboxes for repeating sections, which would be easier in general to replace and implement. SWinxy (talk) 20:26, 20 August 2022 (UTC)
- Sure, but I don't think that this page is the proper place to discuss. Choose some place more proper and let me know where that is?
- —Trappist the monk (talk) 22:58, 20 August 2022 (UTC)
- @Trappist the monk are you still interested in working on this Module? If not, I'd like to try to get it finished myself. The massive deviation I had in mind was to make one invocation of the module do everything. Each page will require individual attention to complete the merge into a proper infobox anyway, so I reason to go the extra mile to make it nicer in general. Repeatable parameters will have the normal n number appended to the end of the parameter. An alternative would be to have subboxes for repeating sections, which would be easier in general to replace and implement. SWinxy (talk) 20:26, 20 August 2022 (UTC)
- The original complaint was that the ship infoboxen templates are
- Since the intent is to use Module:Infobox directly, why is Module:Infobox ship being used to generate the infobox? I can understand if there is need for a backend module to validate a value or something, but is there really a reason to have this unique code? Gonnym (talk) 17:50, 21 May 2022 (UTC)
- I have hacked Module:Infobox ship which implements ship infoboxen without the external wikitable that the above templates require. Uses Module:Infobox;
- Replacement with {{Infobox aircraft}}:
- Template:Infobox_aircraft_type2023 January 22 – Infobox_aircraft_type ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_aircraft_career2023 January 22 – Infobox_aircraft_career ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_aircraft_program2023 January 22 – Infobox_aircraft_program ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_aircraft_begin2023 January 22 – Infobox_aircraft_begin ( links | transclusions | talk | doc | sandbox | testcases ) → {{Infobox aircraft}}
- Template:Infobox_aircraft_engine2023 January 22 – Infobox_aircraft_engine ( links | transclusions | talk | doc | sandbox | testcases ) → {{Infobox aircraft}}
- For {{Infobox aircraft engine}}, There is an ongoing discussion about whether the aircraft engine Infobox should be merged with the Infobox aircraft or not. Except for the engine Infobox, other Infoboxes can be orphaned and there are no objection for that. Prarambh20 (talk) 22:39, 22 May 2023 (UTC)
- This discussion is still ongoing, so I have moved it back to the "to merge" list with the others. Primefac (talk) 10:09, 1 June 2023 (UTC)
- The discussion has now ended (diff), with the consensus NOT TO MERGE {{Infobox aircraft engine}} with the others. However {{infobox aircraft begin}} may or may not end up being merged into {{Infobox aircraft engine}}. The template pages should be updated accordingly. — Cheers, Steelpillow (Talk) 10:07, 6 August 2023 (UTC)
- For {{Infobox aircraft engine}}, There is an ongoing discussion about whether the aircraft engine Infobox should be merged with the Infobox aircraft or not. Except for the engine Infobox, other Infoboxes can be orphaned and there are no objection for that. Prarambh20 (talk) 22:39, 22 May 2023 (UTC)
- Template:Infobox_climber2024 June 29 – Infobox_climber ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_mountaineer2024 June 29 – Infobox_mountaineer ( links | transclusions | talk | doc | sandbox | testcases )
- Merge into {{Infobox NFL biography}} and rename to {{Infobox gridiron football biography}}
- Template:Infobox_Canadian_Football_League_biography2024 November 18 – Infobox_Canadian_Football_League_biography ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_NFL_biography2024 November 18 – Infobox_NFL_biography ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Infobox_gridiron_football_person2024 November 18 – Infobox_gridiron_football_person ( links | transclusions | talk | doc | sandbox | testcases )
Navigation templates
- None currently
Link templates
- Template:Lx2023 October 1 – Lx ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Pagelinks2023 October 1 – Pagelinks ( links | transclusions | talk | doc | sandbox | testcases )
- Because Lx has the option to hide certain links and PageLinks itself doesn't, a direct merge is impossible. The next best thing would be to convert the transclusions to invocations of Module:PageLinks. Doesn't look too impossible at first glance. Snowmanonahoe (talk · contribs · typos) 00:20, 14 January 2024 (UTC)
- Problem: Lx's 20,000 transclusions are kinda fake, because almost all of them are transclusions of transclusions.
Even if we restrict it to the template namespace, most of those are transclusions of transclusions of transclusions in the doc subpage. Snowmanonahoe (talk · contribs · typos) 00:38, 14 January 2024 (UTC)- The more I look at this, the more it appears technically infeasible. Lx has some really bizarre arguments like tag and label which can't be replicated by Module:PageLinks. When Lx was used to link to a normal page, namespace is usually Talk and label is usually talk, but when it's used to link to a talk page, either could be anything. Also, the recursive transclusion issue means the only way to get our pages would be an insource search, which means we'd also have to deal with pages like this.Replacing all uses of the format
\{\{x\|1=\|2=(.*)\|3=Talk\|4=talk\}\}
with{{Pagelinks|$1}}
could be a start. From there, I'm totally lost. Snowmanonahoe (talk · contribs · typos) 16:23, 14 January 2024 (UTC)- What if we only replaced uses matching an insource search in the template namespace, and then substed everything else? Snowmanonahoe (talk · contribs · typos) 19:53, 15 January 2024 (UTC)
- I have officially responded in less than a year. First, better insource search which only cares about direct uses of {{Lx}}, not other things like {{Lxg}}. To your question, what if we make those replacements and see where we are at, transclusion-wise? Once those transclusions of transclusions of translcusions of transclusioons are at least reduced, we can see what else needs evaluation. It will take a while for the jobqueue to catch up and give us an accurate picture of where we are left, so I might do that sooner rather than later... HouseBlaster (talk • he/they) 06:07, 1 January 2025 (UTC)
- What if we only replaced uses matching an insource search in the template namespace, and then substed everything else? Snowmanonahoe (talk · contribs · typos) 19:53, 15 January 2024 (UTC)
- The more I look at this, the more it appears technically infeasible. Lx has some really bizarre arguments like tag and label which can't be replicated by Module:PageLinks. When Lx was used to link to a normal page, namespace is usually Talk and label is usually talk, but when it's used to link to a talk page, either could be anything. Also, the recursive transclusion issue means the only way to get our pages would be an insource search, which means we'd also have to deal with pages like this.Replacing all uses of the format
- Problem: Lx's 20,000 transclusions are kinda fake, because almost all of them are transclusions of transclusions.
- Because Lx has the option to hide certain links and PageLinks itself doesn't, a direct merge is impossible. The next best thing would be to convert the transclusions to invocations of Module:PageLinks. Doesn't look too impossible at first glance. Snowmanonahoe (talk · contribs · typos) 00:20, 14 January 2024 (UTC)
- Template:See_also_if_exists2024 December 13 – See_also_if_exists ( links | transclusions | talk | doc | sandbox | testcases )
- Template:See_also2024 December 13 – See_also ( links | transclusions | talk | doc | sandbox | testcases )
- Requires an admin for Template:Fooers at the YYYY Winter Olympics category/core NotAG on AWB (talk) 15:30, 3 January 2025 (UTC)
Other
- Template:Football_squad_player22020 February 1 – Football_squad_player2 ( links | transclusions | talk | doc | sandbox | testcases ) and Template:Football_squad_player2020 February 1 – Football_squad_player ( links | transclusions | talk | doc | sandbox | testcases )
- Note Pending Redesign RfC robertsky (talk) 18:51, 11 April 2020 (UTC)
- I've closed the RfC. Mdaniels5757 (talk) 15:15, 3 May 2020 (UTC)
- At this point this is ready for large scale replacement. I said a while ago that I could do it but due to me being quite busy IRL this seems unlikely to get done in a timely manner. If you feel like doing a large scale replacement job feel free to take this one. --Trialpears (talk) 17:34, 2 February 2021 (UTC)
- Trialpears, what large-scale replacement? I (foolishly?) jumped into this rabbit hole, and have been in it for over a day now. This is a very complex merge; I've got the documentation diff to show fewer differences, but there's still more to be done. – wbm1058 (talk) 15:04, 14 February 2021 (UTC)
- Note Pending Redesign RfC robertsky (talk) 18:51, 11 April 2020 (UTC)
- Template:Auto_compact_TOC2023 March 6 – Auto_compact_TOC ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Compact_TOC2023 March 6 – Compact_TOC ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Wikisource author2023 July 5 – Wikisource author ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Wikisourcelang2023 July 5 – Wikisourcelang ( links | transclusions | talk | doc | sandbox | testcases )
- Hi now that {{Wikisourcelang}} is being merged, how do I use the merge target template to point to sister language Wikisources? All the links keep incorrectly pointing to the English version and the documentation of {{Wikisource}} has not been updated about this. Folly Mox (talk) 20:16, 11 August 2023 (UTC)
- Folly Mox, the merge has not yet been completed, so you should use the appropriate currently-existing template to do whatever it is you are planning until the merge is complete. The existing uses will be converted appropriately at that time. Primefac (talk) 09:00, 14 August 2023 (UTC)
- Oops, I forgot I had posted here. My assertion was incorrectly based on the first instance I had tested, which had been misusing parameters in such a way that it worked prior to the start of the merge process but not afterwards. The links to en.s/lang:page do properly redirect if the parameters are used correctly, but I didn't initially follow the links to check. It was quite an embarrassing hour or so of my contribution history. Folly Mox (talk) 13:00, 14 August 2023 (UTC)
- Folly Mox, the merge has not yet been completed, so you should use the appropriate currently-existing template to do whatever it is you are planning until the merge is complete. The existing uses will be converted appropriately at that time. Primefac (talk) 09:00, 14 August 2023 (UTC)
- Hi now that {{Wikisourcelang}} is being merged, how do I use the merge target template to point to sister language Wikisources? All the links keep incorrectly pointing to the English version and the documentation of {{Wikisource}} has not been updated about this. Folly Mox (talk) 20:16, 11 August 2023 (UTC)
- Template:Wikisourcehas2023 July 5 – Wikisourcehas ( links | transclusions | talk | doc | sandbox | testcases )
- I see I am not supposed to use {{Wikisourcehas}} on "additional padverages" so I have had to move to using {{Sister project}} because {{Wikisource}} does not have the required functionality. I shall look out for further developments because some very clever coding will be needed. Thincat (talk) 13:13, 17 August 2023 (UTC)
- For over a year now we have been instructed not to use {{Wikisource author}}, {{Wikisourcelang}} and {{Wikisourcehas}} and this is a nuisance because avoiding their use is not at all trivial. Can we have a report on progress with the merge, please, or permission to again use these templates? Thincat (talk) 16:55, 12 July 2024 (UTC)
- See Primefac's note above. Just keep using the existing templates. They will be converted for you during the merge process, whenever it happens (these merges sometimes take a while, as you can see above). When the conversion is done, the merged template will support the features that you need. That's how it's supposed to work, anyway. – Jonesey95 (talk) 19:01, 12 July 2024 (UTC)
- Thank you. That's helpful. Is there a change that could be usefully made to the display text in {{being deleted}}? Or maybe the assumption is that no one reads beyond the first line anyway. Thincat (talk) 20:41, 12 July 2024 (UTC)
- See Primefac's note above. Just keep using the existing templates. They will be converted for you during the merge process, whenever it happens (these merges sometimes take a while, as you can see above). When the conversion is done, the merged template will support the features that you need. That's how it's supposed to work, anyway. – Jonesey95 (talk) 19:01, 12 July 2024 (UTC)
- Template:Facebook_page2024 February 21 – Facebook_page ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Facebook2024 February 21 – Facebook ( links | transclusions | talk | doc | sandbox | testcases )
- While the result was "merge" it seems that this should be moved to "convert" as looking at Craig Kilborn, the ID used there is "The-Kilborn-File/107748632605752", while the new one is at
https://www.facebook.com/profile.php?id=100082874612029
. The number is different. Unless I'm missing something else there is nothing here to merge. --Gonnym (talk) 10:00, 15 March 2024 (UTC)
- While the result was "merge" it seems that this should be moved to "convert" as looking at Craig Kilborn, the ID used there is "The-Kilborn-File/107748632605752", while the new one is at
- Merge into {{R_protected}}:
- Template:R_fully_protected2024 September 17 – R_fully_protected ( links | transclusions | talk | doc | sandbox | testcases )
- Template:R_template-protected2024 September 17 – R_template-protected ( links | transclusions | talk | doc | sandbox | testcases )
- Template:R_extended-protected2024 September 17 – R_extended-protected ( links | transclusions | talk | doc | sandbox | testcases )
- Template:R_semi-protected2024 September 17 – R_semi-protected ( links | transclusions | talk | doc | sandbox | testcases )
- In progress. Primefac (talk) 11:11, 3 January 2025 (UTC)
- Template:STN2024 December 6 – STN ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Station2024 December 6 – Station ( links | transclusions | talk | doc | sandbox | testcases )
- Template:WPBASEBALL_assessment_level_category2024 December 8 – WPBASEBALL_assessment_level_category ( links | transclusions | talk | doc | sandbox | testcases )
- Template:WPANIMATION_assessment_quality_work_group_level2024 December 8 – WPANIMATION_assessment_quality_work_group_level ( links | transclusions | talk | doc | sandbox | testcases )
- Template:WikiProject_Television_task_force_assessment_category2024 December 8 – WikiProject_Television_task_force_assessment_category ( links | transclusions | talk | doc | sandbox | testcases )
- Template:WPANIMATION_assessment_quality_work_group_level2024 December 8 – WPANIMATION_assessment_quality_work_group_level ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Articles by Quality2024 December 20 – Articles by Quality ( links | transclusions | talk | doc | sandbox | testcases )
- Template:Category class2024 December 20 – Category class ( links | transclusions | talk | doc | sandbox | testcases )
Meta
- None currently
To convert
Templates for which the consensus is that they ought to be converted to some other format are put here until the conversion is completed.
- 2023 October 25
- Template:R to related2023 October 25 – R to related ( links | transclusions | talk | doc | sandbox | testcases ) - convert to {{R from related word}} or {{R to related topic}} as appropriate
- Adding this from RfD as it's template related. --Gonnym (talk) 21:45, 17 February 2024 (UTC)
- Started toying with this and came to the conclusion that I was very the wrong person because there are definitely cases where the appropriate template is neither of the two of interest. We need to leave this refinement on the user talk pages of some people who know what they're doing. Izno (talk) 22:20, 26 August 2024 (UTC)
- Template:S-line/IT-Eurostar_left/Frecciabianca2024 April 25 – S-line/IT-Eurostar_left/Frecciabianca ( links | transclusions | talk | doc | sandbox | testcases )
- Template:S-line/IT-Eurostar_right/Frecciabianca2024 April 25 – S-line/IT-Eurostar_right/Frecciabianca ( links | transclusions | talk | doc | sandbox | testcases )
- Module:Adjacent_stations/Trenitalia2024 April 25 – Module:Adjacent_stations/Trenitalia ( links | transclusions | talk | doc | sandbox | testcases )
To substitute
Templates for which the consensus is that all instances should be substituted (e.g. the template should be merged with the article or is a wrapper for a preferred template) are put here until the substitutions are completed. After this is done, the template is deleted from template space.
- None currently
To orphan
These templates are to be deleted, but may still be in use on some pages. Somebody (it doesn't need to be an administrator, anyone can do it) should fix and/or remove significant usages from pages so that the templates can be deleted. Note that simple references to them from Talk: pages should not be removed. Add on bottom and remove from top of list (oldest is on top).
- None currently
Ready for deletion
Templates for which consensus to delete has been reached, and for which orphaning has been completed, can be listed here for an administrator to delete. Remove from this list when an item has been deleted.
- None currently