Jump to content

Template talk:Infobox military person/Archive 3

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 1Archive 2Archive 3

Propose specifying sentence case for "rank" values

I propose adding "sentence case" to the instructions for the "rank" parameter, to parallel the "occupation" parameter in the tl:infobox person template, which says "Please observe sentence case and capitalise only the first letter of the first item; e.g.: Musician • actor • singer-songwriter". In MOS:MILTERMS it is made clear that military ranks are to be treated the same as civilian job titles, that is, not capitalized except to begin a sentence or when used as part of a person's name. Chris the speller yack 11:04, 16 March 2017 (UTC)

  • Oppose as per MOS:JOBTITLES When an unhyphenated compound title ... is capitalized (unless this is simply because it begins a sentence), each word begins with a capital letter. The infobox entries are capitalized, as the proposal admits, but clearly are not part of a sentence. As per quoted MOS compound ranks outside of sentences, like "Brigadier General", should have both words capitalized. ...GELongstreet (talk) 12:15, 16 March 2017 (UTC)
Comment You have the MoS turned inside out. When an unhyphenated compound title ... is capitalized refers to cases where the compound is capitalized because it is "followed by a person's name to form a title" and "can be considered to have become part of the name: President Nixon" (better example: "Vice President Biden"); in the text "President Obama and Vice President Biden carried ...", both "Vice" and "President" are capitalized because they are considered part of Biden's name, but in "Vice presidents have exercised this latter power to varying extents ...", "presidents" is not capitalized because "vice presidents" is a common noun, and "Vice" is capitalized only because it begins a sentence. This is the exception that the MoS means by "When an unhyphenated compound title ... is capitalized (unless this is simply because it begins a sentence", so we do not begin each word with a capital letter. The MoS says nothing about whether a rank is used within a sentence or not, only that coming at the beginning of a sentence is cause for capitalizing the first word and no other. I cannot make this any clearer; you should avoid going off on a tangent of being inside/outside a sentence when the MoS does not state or imply anything like that. Chris the speller yack 13:49, 16 March 2017 (UTC)
I think in this case you´re the one turning it. The fact that it specifically says "(unless this is simply because it begins a sentence)" says that it is for all capitalization cases safe that one. And as it is not in a sentence the "lower case when used generically" doesn´t apply because it is not generic. So I can only repeat myself just as you do. We´ve already discussed and you´ve made your statement as have I; you started the proposal now let it run and give other editors time to speak up. ...GELongstreet (talk) 14:58, 16 March 2017 (UTC)

Support See my comments on this page (section above). Holy (talk) 20:32, 16 March 2017 (UTC)

GELongstreet is willfully misinterpreting the MoS wording. "When an unhyphenated compound title ... is capitalized (unless this is simply because it begins a sentence)" means, and only means, when it is followed by a name, to form a title and name, as in "Brigadier General Lethbridge-Stewart". WP uses exactly the same sentence case convention for actual sentences and for headings, article titles, image captions, table headers, and list entries (including infobox data). Everyone else on the system seem to have absorbed this, and it's why MOS:CAPS doesn't say "at the start of a sentence, a heading, an article title, an image caption, a table header, or a list entry (including infobox data)" over and over and over again. See WP:AJRULE and don't force us to add yet another AJ rule to prevent people making plays at WP:GAMING the short wording "begins a sentence".  — SMcCandlish ¢ >ʌⱷ҅ʌ<  02:25, 20 October 2017 (UTC)

Terms of separation

Shouldn't there be a field in this infobox for the terms of separation from the military, whether retired, honorably or dishonorably discharged, or whatever other such terms exist? – Athaenara 04:03, 7 November 2017 (UTC)

Children?

It seems the children param is not recognized. Any clue? Carlotm (talk) 01:16, 5 April 2017 (UTC)

I would support adding |children=. Edit request has been submitted. Gaia Octavia Agrippa Talk 22:15, 25 November 2017 (UTC)
Done Placed under Spouse. Please update the documentation. – Train2104 (t • c) 23:01, 25 November 2017 (UTC)

Template-protected edit request on 29 December 2017

For the image parameter, remove "upright=1" so that individual articles can use the upright parameter instead of setting the size of the image. - Mnnlaxer | talk | stalk 03:48, 29 December 2017 (UTC)

|image_upright= added. — JJMC89(T·C) 04:34, 29 December 2017 (UTC)
Thanks. - Mnnlaxer | talk | stalk 06:29, 29 December 2017 (UTC)

Template-protected edit request on 1 January 2018

The tag <wbr/> should be added following the slash in label9 per WP:LINEBREAK and WP:SHY. Thanks, 142.161.81.20 (talk) 04:41, 1 January 2018 (UTC)

Done Cabayi (talk) 09:56, 1 January 2018 (UTC)

Honorifics

Please change to match {{Infobox person}}:

  • <span class="honorific-prefix" style="font-size: small">
  • <span class="honorific-suffix" style="font-size: small">

To this:

  • <span class="honorific-prefix" style="font-size: 77%; font-weight: normal;">
  • <span class="honorific-suffix" style="font-size: 77%; font-weight: normal;">

Thank-you.--Nevéselbert 11:06, 24 December 2017 (UTC)

MOS:FONTSIZE requires 85%. Perhaps change both to 85%? Cabayi (talk) 11:39, 24 December 2017 (UTC)
Cabayi, that section is inside a "font-size:125%" and 77% of 125% is sufficiently above 85%. I will make the change. Frietjes (talk) 13:30, 25 December 2017 (UTC)
Neve-selbert, done. Frietjes (talk) 13:32, 25 December 2017 (UTC)

Honorifics (again)

Could |honorific_prefix= and |honorific_suffix= be un-bolded please? The above edits made the text smaller but it missed off removing the bolding to truly match the formatting at Infobox person. Thanks, Gaia Octavia Agrippa Talk 23:59, 14 January 2018 (UTC)

Done — Martin (MSGJ · talk) 09:47, 15 January 2018 (UTC)
Thank you, Gaia Octavia Agrippa Talk 13:17, 15 January 2018 (UTC)

Education

Could |education= and |alma_mater= please be added? Thanks, Gaia Octavia Agrippa Talk 18:17, 16 January 2018 (UTC)

Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. — JJMC89(T·C) 02:48, 17 January 2018 (UTC)
Okay. Does anyone object to having the above parameters added? This must be one of the only biographical inboxes that doesn't have these two parameters. Gaia Octavia Agrippa Talk 15:20, 17 January 2018 (UTC)
I support the addition of those parameters as they would be of some relevance quite often. However if you want more opinions or input to reach a concensus I´d suggest you drop a word at Wikipedia talk:WikiProject Military history ...GELongstreet (talk) 22:20, 23 January 2018 (UTC)

What to do if serviced in more than one branch of the military?

How should it be handled if a person started their career in one branch of service, and subsequently serviced in another branch of service? — ERcheck (talk) 03:02, 3 February 2018 (UTC)

T. E. Lawrence -- Cabayi (talk) 09:02, 3 February 2018 (UTC)
Thank you. — ERcheck (talk) 22:40, 3 February 2018 (UTC)

Template-protected edit request on 29 March 2018

Replace
| label19 = Children
| data19 = {{{children|}}}

with
| label19 = {{#switch:{{{children}}}|1=Child|Children}}
| data19 = {{{children|}}}

so that if there is only one child, the label will display Child instead of Children. Thanks, L293D () 12:10, 29 March 2018 (UTC)

 Not done @L293D: I'm going to decline the request for now, based on that there has not been a discussion on the matter and such a change could be seen as controversial. Feel free to activate the request again once there is a demonstrated consensus for the change. Jon Kolbert (talk) 22:24, 29 March 2018 (UTC)

image parameter

I was looking at Category:Infobox military person image param needs updating which lists articles that use this template with the {{{image}}}=[[File:example.jpg]] instead of {{{image}}}=example.jpg, mainly to be consistent with other infoboxes. However, the majority of these articles have an two images (a photo of the person and a medal), as in Ralph E. Dias. Can the template be changed to more formally support this usage with additional fields for the medal image. MB 03:30, 11 June 2018 (UTC)

Frietjes, perhaps you can help? MB 13:51, 21 June 2018 (UTC)
MB, this works now. make sure you watch out for any old 'image_size' parameters that were being ignored before. the new parameters are |medal=, |medal_size=, |medal_alt=. Frietjes (talk) 15:25, 21 June 2018 (UTC)
generally, you should not need to set any of the size parameters. the medal image is scaled to be smaller, and the primary image is scaled if there is a medal image next to it. Frietjes (talk) 15:40, 21 June 2018 (UTC)

Parents

Why does this template not accept father/mother/parents parameters? {{Infobox person}} accepts those. Alexis Jazz (talk) 02:53, 29 June 2018 (UTC)

Need variation for multi-branch service

The "Template:Infobox military person" has been used in nearly 33,000 pages, so I think we need a closely related infobox to display multiple service branches, especially for different nations as with U.S. versus the Confederacy, in the case of General Robert E. Lee and others. I plan to create related infobox "Template:Infobox military person multi" for optional use when 2 branches or more, and we can further expand that co-template for use in a few hundred pages without risking upset to the current 33,000 pages using the single-branch variation. Because a minimum of 2 branches would be listed, then banner headers would appear inside the infobox, somewhat like multiple political offices. I also think listing battles separately for each service branch would be a great benefit, to reduce confusion. However, the "spouse=" could continue to list all spouses under a single entry regardless of the various nation "allegiance2=" banners. Should the awards be listed separately for each service branch? -Wikid77 (talk) 22:08, 22 July 2018 (UTC)

Currently the service of those who changed countries is listed by bullets or a plainlist, for example Stonewall Jackson. I don't see why a separate parameter is necessary. Kges1901 (talk) 01:44, 24 July 2018 (UTC)

Army flag, seal or neither?

There are three different ways that I've seen the "branch" parameter completed for U.S. Army personnel. There are those that include the Army flag before the name (like William F. Dean), those that include the Department of the Army seal (e.g. George Juskalian) and those that include neither (e.g. Powhatan Beaty). Is one of these styles correct? Is one even preferred? All three of the articles which I linked here are WP:Good articles despite the discrepancy. --Dennis C. Abrams (talk) 01:26, 13 April 2018 (UTC)

@Denniscabrams: MOS:FLAG specifically says that flags should not be used in biography infoboxes. Can't quite get why the GA review didn't pick up on this. Dom from Paris (talk) 07:42, 19 August 2018 (UTC)

branch_label

Would it be possible to add |branch_label= as a new parameter, same as how we already have |serviceyears_label= and |battles_label=? For one it'll allow us to chose either "service" or "branch", which I think might be beneficial for wrapping. Thank you. Jay D'Easy (talk) 15:37, 22 September 2018 (UTC)

 Done Enterprisey (talk!) 03:23, 24 September 2018 (UTC)

Unit parameter: customizable? Alternatively: a "ships" parameter?

Hello, me again. Thanks for the last edit, by the way. It's much appreciated (by me, at least).

I came across George Nares' article and noticed how awkward it looks when all ships he's served on before he took his first command are included; given the fact that the |unit= parameter is used. On the one hand I think it might be useful to be able to customize the parameter with |unit_label= (especially for naval personnel), on the other hand I can see how too many customizable labels may lead to misuse (or abuse). In case of the latter, maybe a new parameter would be better afforded? |ships= perhaps?

Last minute edit: on the last (spooky ghost) hand, maybe do nothing and instead I should remove this parameter from Nares' infobox altogether?

At the very least I hope this request inspires a discussion. Thanks. Jay D. Easy (talk) 13:04, 18 November 2018 (UTC)

 Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. I'd recommend (neutrally) soliciting input to this discussion by linking to it on the talk pages of the relevant projects tagged at the top of this page. Cabayi (talk) 13:12, 18 November 2018 (UTC)
Jay D. Easy, given that there is |branch_label=, |rank_label=, |battles_label=, it seems fairly uncontroversial to add |unit_label=. so, now added. if this is controversial, someone can revert my edit. Frietjes (talk) 14:17, 19 November 2018 (UTC)

Set width_style to person by default?

Hello. Please forgive my continued suggestions, but this is one of the templates I use most frequently.

There's a parameter a lot of people presumably aren't aware of: |width_style=; since it's not mentioned on the documentation page. It controls the infobox's width, naturally. By default, it's set to main_box_raw, which makes the infobox as wide as a military conflict infobox. This by itself is fine because a wider infobox doesn't create as many text wrapping issues as it otherwise may have. On the other hand, I have always felt this infobox's default width looks weird in comparison to other biography/person infoboxes, and frequently apply |width_style=person when opportunity permits.

I'm not that well versed in template coding, but the code pertaining to the width is found at the top of the template's source code:

| bodystyle    = {{WPMILHIST Infobox style|{{#switch:{{{width_style|}}}|narrow|person|auto=main_box_raw_auto_width|wide|military|#default=main_box_raw}}}}

I did a little research beforehand, but did not manage to find any previous discussion on this subject. Forgive my ignorance if the current default width was previously agreed upon. Thank you. Jay D. Easy (talk) 23:14, 21 December 2018 (UTC)

The documentation is not protected. You are welcome to edit it. What the code above says, as far as I can tell, is that if |width_style= is set to "narrow" or "person" or "auto", the width is set to "main_box_raw_auto_width". Otherwise, it is set to "main_box_raw". – Jonesey95 (talk) 23:25, 21 December 2018 (UTC)
That is actually what I was already doing before I canceled my edit and figured I could just as well put in this request. Jay D. Easy (talk) 07:10, 22 December 2018 (UTC)

image/medal

Frietjes, I asked for this change last year as a non-controversial (because it made no actual change to rendered version) way to fix over 400 articles in Category:Infobox military person image param needs updating. It appears that project editors feel an infobox should not contain both images, per this discussion and a prior one I saw on the same page. So |medal= can either be deprecated, or perhaps displayed only if |image= has no value. MB 15:41, 20 January 2019 (UTC)

MB, okay, I made two edits: (1) added a tracking category Category:Pages using infobox military person with both image and medal which will take time to fill up, and (2) modified the logic so only of the two will show, with image taking precedence. if suppressing the medal is controversial, someone can revert the second edit. Frietjes (talk) 15:58, 20 January 2019 (UTC)

Discussion regarding the use of infobox criminal for military personnel

There is a discussion regarding the use of infobox criminal for military personnel here in case anyone is interested. Cheers, Peacemaker67 (click to talk to me) 02:46, 8 February 2019 (UTC)

Informal spies?

What about people who are not part of the military per se, but agreed to spy for some cause such as Victor Martin for the Belgian resistance during World War II? On his Talk page, the military task force was involved from the Biography WikiProject, but he was also an academic. Thanks to anybody who can follow up on this, both on his page and in the guidelines on this template's documentation page if firm guidelines can be set. Unfortunately, my real life limitations force me to just leave this here. —Geekdiva (talk) 12:19, 18 July 2019 (UTC)

Something is wrong here

Does anyone know why |Children= is outputing a lablel of "Spouse(s)". There doesn't seem to be an obvious issue with the syntax. Ergo Sum 03:19, 2 December 2019 (UTC)

I found the problem. It wasn't with the template code, but with the TemplateData. Fixed now. Ergo Sum 03:21, 2 December 2019 (UTC)

When the 'obvious' assumptions go wrong

See my comments at Talk:Heinz_Guderian#Allegiance. Nothing wrong, it's just that what's right looks wrong. (sigh) Perhaps documentation to relate allegiance dates with dates of service could be added? I mean, *you* know how the template is to be used, but others may not... Shenme (talk) 03:18, 6 December 2019 (UTC)

Proposed additional parameters

I propose adding |alma_mater= and |education= to this infobox. There are other "personal" parameters in this infobox (eg |spouse=), so two more wouldn't be out of place. Gaia Octavia Agrippa Talk 00:17, 15 March 2019 (UTC)

Convert to wrapper

Parameter Infobox military person Infobox person
1 No Yes
2 No Yes
3 No Yes
4 No Yes
5 No Yes
abovestyle No Yes
agent No Yes
alias No Yes
allegiance Yes No
alma mater No Yes
alma_mater Yes Yes
alt Yes Yes
awards Yes Yes
baptised No Yes
baptized No Yes
battles Yes No
battles_label Yes No
birth_date Yes Yes
birth_name Yes Yes
birth_place Yes Yes
birthname No Yes
boards No Yes
body discovered No Yes
body_discovered No Yes
box_width No Yes
branch Yes No
branch_label Yes No
burial_coordinates No Yes
burial_place No Yes
callsign No Yes
caption Yes Yes
child No Yes
children Yes Yes
citizenship No Yes
commands Yes No
credits No Yes
criminal charge No Yes
criminal penalty No Yes
criminal status No Yes
criminal_charge No Yes
criminal_charges No Yes
criminal_penalty No Yes
criminal_status No Yes
death cause No Yes
death_cause No Yes
death_date Yes Yes
death_place Yes Yes
denomination No Yes
disappeared_date No Yes
disappeared_place No Yes
disappeared_status No Yes
domestic_partner No Yes
domesticpartner No Yes
education No Yes
embed Yes Yes
embed_title Yes No
employer No Yes
era No Yes
ethnicity No Yes
family No Yes
father No Yes
footnotes No Yes
height No Yes
height_cm No Yes
height_ft No Yes
height_in No Yes
height_m No Yes
home town No Yes
home_town No Yes
homepage Yes Yes
honorific prefix Yes Yes
honorific suffix Yes Yes
honorific_prefix Yes Yes
honorific_suffix Yes Yes
honorific-prefix No Yes
honorific-suffix No Yes
honors No Yes
honours No Yes
image Yes Yes
image caption No Yes
image size No Yes
image_caption No Yes
image_size Yes Yes
image_upright Yes Yes
imagesize No Yes
influenced No Yes
influences No Yes
judicial status No Yes
judicial_status No Yes
known No Yes
known for No Yes
known_for No Yes
label_name No Yes
landscape No Yes
laterwork Yes No
medal Yes No
medal_alt Yes No
medal_size Yes No
medal_upright Yes No
memorials Yes No
misc No Yes
misc2 No Yes
misc3 No Yes
misc4 No Yes
misc5 No Yes
misc6 No Yes
module Yes Yes
module2 No Yes
module3 No Yes
module4 No Yes
module5 No Yes
module6 No Yes
monuments No Yes
mother No Yes
movement No Yes
name Yes Yes
nationality No Yes
native_name Yes Yes
native_name_lang Yes Yes
net worth No Yes
net_worth No Yes
networth No Yes
nickname Yes Yes
nocat_wdimage No Yes
notable works No Yes
notable_works No Yes
occupation No Yes
office No Yes
opponents No Yes
organisation No Yes
organization No Yes
organizations No Yes
other names No Yes
other_name Yes No
other_names No Yes
othername No Yes
otherwork Yes No
parents No Yes
partner No Yes
partner(s) No Yes
partners No Yes
party No Yes
placeofburial Yes No
placeofburial_coordinates Yes No
placeofburial_label Yes No
post-nominals No Yes
pre-nominals No Yes
predecessor No Yes
pronunciation No Yes
rank Yes No
rank_label Yes No
relations Yes Yes
relatives No Yes
religion No Yes
residence No Yes
resting place No Yes
resting place coordinates No Yes
resting_place No Yes
resting_place_coordinates No Yes
restingplace No Yes
restingplacecoordinates No Yes
servicenumber Yes No
serviceyears Yes No
serviceyears_label Yes No
siglum No Yes
signature Yes Yes
signature alt Yes Yes
signature_alt Yes Yes
signature_size Yes Yes
spouse Yes Yes
spouse(s) No Yes
spouses No Yes
status No Yes
style No Yes
successor No Yes
television No Yes
term No Yes
title No Yes
unit Yes No
unit_label Yes No
URL Yes Yes
url No Yes
website Yes Yes
width_style Yes No
works No Yes
years active No Yes
years_active No Yes
yearsactive No Yes

This should be converted to wrapper of {{Infobox person}} per WP:INFOCOL Capankajsmilyo(Talk | Infobox assistance) 00:28, 25 March 2020 (UTC)

Please stop this disruptive spamming. Just take a look at the table above. There are major differences in the parameters supported by each template. Also, as I have already told you at one of the far too many pages on which you have spammed tables like this, your parameter list for {{Infobox person}} is incorrect. |1=, for example, is not supported by Infobox person. The documentation page for the tool you are using has a caveat explaining that you need to validate its output. – Jonesey95 (talk) 01:46, 25 March 2020 (UTC)

criteria for notable awards

At Template:Infobox military person/doc it says with regard to |awards=, "notable awards or decorations the person received; exhaustive lists should be worked into the prose. Separate multiple entries using {{Plainlist}}." To define "notable" in this context, I've taken the tack that if an award doesn't have a "recipients of…" category (e.g. the Silver Star), then it isn't notable enough to warrant infobox inclusion. Might this be suitable enough to lay out as recommended SOP? — Fourthords | =Λ= | 00:08, 9 November 2020 (UTC)

Alignment bug

In Charles Sweeny, if the branch_label field is present (even if empty), the branches are centered and the heading "Service/branch" is missing, but if the empty field is removed, it becomes left aligned and the heading appears (which is what I wanted). Clarityfiend (talk) 20:58, 4 March 2021 (UTC)

 Fixed. Good catch! – Jonesey95 (talk) 21:26, 4 March 2021 (UTC)

Icons in infobox

I don't usually edit military-related articles, but as I edit biographies I sometimes see this infobox included on a page. Some, like James Arness, have an array of icons within the military infobox. It seems to me that using icons in parameters such as Rank, Unit, and Awards goes against MOS:ICONDECORATION, and I noticed that the example on Template:Infobox military person contains only one icon -- the American flag.

Would I be wrong if I removed icons from infoboxes on pages like James Arness? I would like to have the opinions of editors who are familiar with this topic. Eddie Blick (talk) 01:51, 24 June 2021 (UTC)

It it ok to use this infobox for fictional people?

Erwin König is a fictional German soldier but his article has a military person infobox. 119.74.177.38 (talk) 04:17, 6 September 2021 (UTC)

Template:Infobox character. --Renat 01:54, 7 September 2021 (UTC)

Boolean handling

For |embed=, this template uses only {{lc}}, not {{yesno}}. Is there a reason for that? Using yesno would allow improved boolean handling, e.g. if someone accidentally writes |embed=y. {{u|Sdkb}}talk 22:18, 4 November 2021 (UTC)

"Known_for" parameter

Please add "known_for" parameter, in the same way as is now present in the Template:Infobox person. Besides their military ranks, battles, etc., many of the subjects have other areas of notability, such as war crimes or notable orders. For example, Walter von Reichenau is known for his Severity Order, but there's no current way to reflect this in the infobox. The best placement to render this in the infobox as displayed to the reader would be in between Commands held (above) and Battles/wars (below). --K.e.coffman (talk) 01:55, 29 January 2022 (UTC)

 Done. P.I. Ellsworth - ed. put'r there 02:58, 1 February 2022 (UTC)

"reported_death" parameter

Please add a "reported_death" parameter for individuals that have reportedly died but it has not been officially confirmed. This is important for military persons who are reported to have been killed in conflict but their nation has declined confirm that they have been killed. It could be years or even decades before official confirmation acknowledges their death. GravisZro (talk) 13:59, 24 March 2022 (UTC)

This can be handled in other ways without a separate parameter: just add "(reported)" after the date, or use {{efn}} and add a more detailed footnote. MB 14:17, 24 March 2022 (UTC)
 Not done as there is ongoing discussion about this above still, once a consensus emerges please reactivate the request if needed. — xaosflux Talk 15:17, 24 March 2022 (UTC)

Help requested: New parameters needed for Prisoner of War status

Parameters might include:

prisoner of war = yes

missing in action = yes (if the case, instead of prisoner of war) (many POWs are listed as "missing in action" [MIA] because their captors won't confirm that they have them)

conflict = (war or military operation or peacekeeping action) (leave open for any text)

captors = (nation or paramilitary group or terrorist group holding the military person captive) (allow parameter to recieve any text)

date of capture =

date of disappearance (If MIA) =

circumstances of capture = ("specific battle", or "shot down in fighter jet", or "special forces operation" or "captured while on patrol" etc...) (In other words, leave parameter open to recieve any text).

location of imprisonment = (leave open for any text, might be "Lubyanka prison in Russia" [for Ukrainian POWs] or a 'specific prison in Syria', etc...)

circumstances of captivity = (leave open for any text, might include "harsh" or "torture" or "no medical treatment" or "solitary confinement" or even "unknown" etc....)

negotiating parties = (Nations or NGOs / humanitarian organizations involved with release negotiations)

status of release negotiations = ("stalled" or "in progress" or "none") (perhaps allow any text)

released = (yes or no)

escaped = (yes or no)

died in captivity = (yes or no)

still in captivity = (yes or no)

date of release =

date of escape =

date of death in captivity =

1) (Automatically calculates and posts [from capture / disappearance / date to release / escape date] number of years, months (and days?) in captivity)

Or 2) (Automatically counts years, months (and days?) [to todays date from date of capture / disappearance], if still in captivity or still MIA)

resulting health problems = (leave open for any text, might include "PTSD", or "injuries from torture" or "neuropathy" [very common in cold places like Korea [Korean War ex-POWs], essentially permanent loss of feeling in feet or hands due to (repeated) frostbite] etc. Any text might be added).

special honors = (honors or medals or rank-promotion conferred related to POW experience) (leave open text input)

IMHO, these new parameters should be added into the existing "military person" type infobox (not be a seperate infobox) because the POW experience is a part of some people's military career.

So these should be optional added parameters for the military person infobox, not a seperate infobox

  • I am from a military family and we were close to an organization for families of US POWs / MIAs so I can tell you there are thousands of such former POWs and MIAs (and some current ones) in the USA (alone) not to mention other countries. My father was also a Korean War POW (although he is not notable by Wikipedia standards). There are many who were / are notable however.

Note: Boldface is only used here to emphasize key points.

Sincere thanks in advance to anyone who might be able to make something like this work.

Chesapeake77 (talk) 07:11, 14 May 2022 (UTC)

Putting military rank in honorific_prefix parameter

I've seen cases where the "honorific_prefix" is filled with the subject's military rank. I think it is redundant to the "rank" parameter that is always filled. Should "honorific_prefix" be filled with military rank or not? Aithus (talk) 05:05, 14 April 2023 (UTC)

Edit request 25 August 2023

Description of suggested change: Addition of disappearance parameters to the template when death date is uncertain. This request comes specifically for the article Hans Kammler, whose death date is widely debated, however his disappearance date is more certain.

Diff:

ORIGINAL_TEXT
+
CHANGED_TEXT

A y d o h 8 ( t a l k ) 01:02, 25 August 2023 (UTC)

 Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. To editor A y d o h 8: hopefully it will help that the [sandbox] has been synchronized with the live template, and a test case for [Hans Kammler] has been added to the testcases page. P.I. Ellsworth , ed. put'er there 10:27, 25 August 2023 (UTC)

Edit request 20 October 2023

Add death_cause parameter that was added to documentation several months ago (and then removed after I pointed it out at the help desk) but not actually added to the template until now. See the sandbox edit I made here. Thank you (if I did this incorrectly, sorry my bad I'm new to this) I also tried to do the above person's request. :) PARAKANYAA (talk) 08:38, 20 October 2023 (UTC)

We would normally ask for evidence of consensus for any new parameters in infoboxes. Has this new parameter been discussed anywhere? — Martin (MSGJ · talk) 10:25, 20 October 2023 (UTC)
It's alright to include. These specialized infoboxes extend Template:Infobox person, and it's reasonable that any parameters there should carry over. SWinxy (talk) 21:44, 20 October 2023 (UTC)
As SWinxy said, they're in infobox person as well, and I don't think it makes sense for a specialized version of that template to lack a basic field that one has. It's new to this template but not to other people infoboxes on wiki PARAKANYAA (talk) 23:07, 20 October 2023 (UTC)
 Done * Pppery * it has begun... 00:05, 27 October 2023 (UTC)

Texas State Guard?

I’m looking at the Robert Willis (hacker) page and as he has received an medal in his Infobox, I am not sure if it is appropriate to add this infobox below. His award came from his service in the Texas State Guard and there are other articles of their members without the military person infobox. If these qualify, I’d appreciate militia’s being acceptable in the documentation (the infobox documentation mentions government officials qualifying). Twillisjr (talk) 16:45, 6 January 2024 (UTC)

Discussion regarding the placement of "Sir"

There is a discussion regarding the placement of "Sir" here in case anyone is interested. Cheers, --Omnipaedista (talk) 15:34, 23 January 2024 (UTC)

Edit request 29 January 2024 - parent parameters

Description of suggested change: I went to add Winfield W. Scott Jr. to the infobox of Winfield W. Scott III and noticed that this template doesn't have mother/father/parents parameters like Template:Infobox person. If anyone could help out by adding it, I think it would be a really useful addition. Thanks! Rockhead126 (talk) 01:40, 29 January 2024 (UTC)

You could use the |relations= parameter. Or you could add this line to the infobox:
|module={{infobox person |embed=yes |father=[[Winfield W. Scott Jr.]]}}
The downside to either of these is that "relations" and "parent" are displayed at the bottom below all of the military carerr details.
Alternatively, you could switch from using {{Infobox military person}} as the main infobox to using {{Infobox person}} with the |module= parameter set to display {{Infobox military person}} with all of the associated parameters unique to that infobox. The look/style of the infobox will change slightly, but this approach has the benefit of having all of the "personal" details grouped together at the top and then everything else for the military career below.  — Archer1234 (t·c) 03:33, 29 January 2024 (UTC)

Rockhead126 I'm going to mark this as declined and suggest you try one of the suggestions in Archer's comment. Alternately, it may not be the case that the family relation is a defining characteristic that should be mentioned in the infobox. Keep in mind MOS:INFOBOXPURPOSE: "The less information it contains, the more effectively it serves [its] purpose, allowing readers to identify key facts at a glance." (t · c) buidhe 22:55, 5 February 2024 (UTC)

buidhe It seems reasonable to me to have the parameter carry over from Template:Infobox person in this case. Obviously not every parameter is relevant for the average military person, but this is a key piece of biographical information, and there are a heck of a lot of notable military figures whose parentages are undoubtedly notable characteristics. Especially considering that there are already spouse and children parameters, I'd argue that including parent parameters makes more sense than just having the information go under relations or requiring editors to embed a module. Rockhead126 (talk) 23:45, 5 February 2024 (UTC)

Underscores

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)

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

"Commands held"

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)

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)

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