Template talk:Infobox military person

(Redirected from Template talk:Infobox Military Person)
Latest comment: 10 days ago by Santiago Claudio in topic Edit request on 14 August 2024

Underscores

edit

Noticed that some parameters, including serviceyears and servicenumber, don't have underscores as required per INFOBOXNAME. Can that be corrected? QuietHere (talk | contributions) 09:03, 18 March 2024 (UTC)Reply

  Done. Feel free to update the documentation for consistency. – Jonesey95 (talk) 23:53, 18 March 2024 (UTC)Reply

"Commands held"

edit

Could this not be shortened to "Commands"? It would be concise, communicate the very same information, and decrease the width of the lefthand parameters column when displayed (thereby less frequently causing uncontrolled line breaking in both columns). — Fourthords | =Λ= | 22:44, 6 August 2024 (UTC)Reply

As mentioned above, reducing all instances "Commands held" to "Commands" for (a) concision, (b) reducing induction of visible unintended parameter & variable line-breaking, (c) equally communicating the exact same meaning, (d) and to match the infobox code itself. — Fourthords | =Λ= | 18:38, 11 August 2024 (UTC)Reply

  Done if anyone disagrees this can be reverted on request — Martin (MSGJ · talk) 21:06, 11 August 2024 (UTC)Reply
Thanks so much! — Fourthords | =Λ= | 21:44, 11 August 2024 (UTC)Reply

Rank

edit

There's been quite a bit of discussion on Talk:Tim Walz regarding the rank field here. The documentation used to say highest rank unless reduced, but that was changed three years ago. It's also been raised that if Tim Walz is listed as a Command Sergeant Major, because he held that rank until retirement, then Ronny Jackson should be listed as a RDML. Any thoughts about how this should properly work? Thanks. --SarekOfVulcan (talk) 15:08, 12 August 2024 (UTC)Reply

The discussions at those talk pages should not be forked to here. The discussion that led to the 2021 template documentation change was this one at WP Military history. If consensus cannot be reached at the article's talk page, you could post a note at the WikiProject page to ask people to visit. – Jonesey95 (talk) 21:07, 12 August 2024 (UTC)Reply
I'm not trying to fork the discussions - I'm looking for confirmation — or not — that the documentation still matches the larger consensus over the use of this field. I don't usually work in the MilHist realm, so I don't know the best practices. --SarekOfVulcan (talk) 15:33, 13 August 2024 (UTC)Reply

Edit request on 14 August 2024

edit

To any administrator, apply my edit to this infobox's sandbox: replace font-size: 125% in |abovestyle= with {{{abovestyle|}}}. Santiago Claudio (talk) 04:24, 14 August 2024 (UTC)Reply

Please explain the purpose of this edit. Also, I have removed the setting in the edit request saying that this is an edit request for Template:Infobox officeholder rather than Template:Infobox military person. SilverLocust 💬 10:26, 15 August 2024 (UTC)Reply
This edit request is for consistency with |abovestyle= in Template:Infobox person. Santiago Claudio (talk) 02:12, 16 August 2024 (UTC)Reply
I encourage the requester to test their new parameter on the testcases page. I expect that an error will appear in Preview mode; the new parameter needs to be added to the unknown parameter check. This advice goes for all three edit requests filed by the requester. – Jonesey95 (talk) 02:58, 16 August 2024 (UTC)Reply
  Not done pending a response to MSGJ's queries elsewhere * Pppery * it has begun... 22:07, 19 August 2024 (UTC)Reply
I synced the testcases; there were no errors. Santiago Claudio (talk) 02:46, 20 August 2024 (UTC)Reply
Which test case contains a demonstration of |abovestyle=? – Jonesey95 (talk) 13:33, 20 August 2024 (UTC)Reply
Parameter names! Santiago Claudio (talk) 00:48, 22 August 2024 (UTC)Reply

Military service

edit

Should this template be used on subject mandatory conscription?, or theres no need to input military service since it's not the subject main occupation ot what the subject is known for 27.125.250.21 (talk) 17:32, 15 August 2024 (UTC)Reply