Template talk:Infobox language

Edit request 13 February 2025

Description of suggested change: I propose adding two new language family colors to this template; namely those for   Chibchan languages and   Tucanoan languages. 🪐Kepler-1229b | talk | contribs🪐 05:26, 13 February 2025 (UTC)

I have unarchived this edit request. This appears to be a follow-up to Wikipedia talk:WikiProject Languages/Archive 18#Addition of family colors to Template:Infobox language/family-color, if I'm not mistaken? It looks reasonable, although given the lack of input here I suggest asking on Wikipedia talk:WikiProject Languages, depending on how much specificity editors want in labeling small families vs larger areal groupings. Chaotic Enby (talk · contribs) 16:23, 11 October 2025 (UTC)

Since this edit request is a subgroup of the indigenous American languages edit request, building upon Kepler-1229b's original proposal I would like to further propose changing   Quechuan languages to   Quechumaran languages, bringing Aymara out of the "American (areal)" grouping. After all, if   Hokan languages gets theirs while being disputed, why shouldn't Quechumaran? Frank_{(has DemoCracy DeprivaTion)} 06:32, 19 November 2025 (UTC)

@DemocracyDeprivationDisorder This is very late, but the main difference between these groupings is that Hokan is very commonly cited in groupings of Native American languages, even if there is little to no support (Campbell 2024). Quechumaran is much less visible in classification schemes for South American languages and is mostly listed in a "proposed families" section, if even at all. 🪐Kepler-1229b | talk | contribs🪐 16:11, 8 April 2026 (UTC)

 Done though this was long pending. Santiago Claudio (talk) 08:23, 18 April 2026 (UTC)

Only the original proposals, I'm guessing? Or is Quechumaran also fine by you? Frank_{(has DemoCracy DeprivaTion)} 11:37, 18 April 2026 (UTC)

I think Quechumaran should not be expanded for now, per my above reasons. 🪐Kepler-1229b | talk | contribs🪐 16:45, 18 April 2026 (UTC)

Template-protected edit request on 18 January 2026

Add version and year parameter based on sandbox. Arctic Circle System (talk) 17:39, 18 January 2026 (UTC)

 Not done: the page's protection level has changed since this request was placed. You should now be able to edit the page yourself. If you still seem to be unable to, please reopen the request with further details. Zackmann (^{Talk to me}/_{What I been doing}) 20:55, 18 January 2026 (UTC)

Template-protected edit request on 4 February 2026

At the altname parameter, change "used, and altname parameter" to "used, an altname parameter".

this typo is pissing me off so badly —It's Okkirae.temp ^('Sup?)! 19:27, 4 February 2026 (UTC)

 Done but Okkirae.temp, that's Template:Infobox language/doc which isn't under any protection. I made the same mistake... HurricaneZeta^C 19:34, 4 February 2026 (UTC)

ah—I forget that the documentation pages are meta-separate from the main page. thanks for humoring me anyway —It's Okkirae.temp ^('Sup?)! 20:34, 4 February 2026 (UTC)

Edit request 11 February 2026

Add a parameter to use a css class for the image: Currently, a large number of the uses of this infobox use an image of text in the language for the image parameter. As is, these images render correctly in light mode, but they render with an unsightly white box in dark mode. In general, The fix for this is to add the css class skin-invert-image to the image. However it does not seem like there is currently a way to provide this parameter. Thus I am proposing the ability to add a css class to the image via an imageclass parameter. Then dark mode can be fixed for individual pages by adding the correct parameter.

Diff:

−

| image = {{#invoke:InfoboxImage|InfoboxImage|image={{{image|}}}|upright={{if empty|{{{imagescale|}}}|0.9}}|alt={{{imagealt|}}}}}

+

| image = {{#invoke:InfoboxImage|InfoboxImage|image={{{image|}}}|upright={{if empty|{{{imagescale|}}}|0.9}}|alt={{{imagealt|}}}|class={{{imageclass|}}}}}

AquitaneHungerForce (talk) 14:27, 11 February 2026 (UTC)

Hey Aquitane, good to see you. As someone who both edits a lot of language pages and has been mass applying skinverts wherever necessary and possible, +1! This would be of great use. ~ oklopfer (💬) 06:29, 12 February 2026 (UTC)

 Done phuzion (talk) 13:12, 12 February 2026 (UTC)

Thank you. I forgot that a new parameter would need to be added to the parameter list. Using the imageclass parameter creates an erroneous unknown parameter warning. The fix for this would be:

−

|preview=Page using [[Template:Infobox language]] with unknown parameter "_VALUE_"|ignoreblank=y| acceptance | agency | aiatsis | aiatsis2 | aiatsis3 | aiatsis4 | aiatsis5 | aiatsis6 | aiatsisname | aiatsisname2 | aiatsisname3 | aiatsisname4 | aiatsisname5 | aiatsisname6 | altname | ancestor | ancestor2 | ancestor3 | ancestor4 | ancestor5 | ancestor6 | ancestor7 | ancestor8 | ancestor9 | ancestor10 | ancestor11 | ancestor12 | ancestor13 | ancestor14 | ancestor15 | boxsize | coordinates | coords | created | creator | date | dateprefix | development_body | dia1 | dia2 | dia3 | dia4 | dia5 | dia6 | dia7 | dia8 | dia9 | dia10 | dia11 | dia12 | dia13 | dia14 | dia15 | dia16 | dia17 | dia18 | dia19 | dia20 | dia21 | dia22 | dia23 | dia24 | dia25 | dia26 | dia27 | dia28 | dia29 | dia30 | dia31 | dia32 | dia33 | dia34 | dia35 | dia36 | dia37 | dia38 | dia39 | dia40 | dialect_label | dialects | ELP | ELP2 | ELP3 | ELP4 | ELP5 | ELP6 | ELPname | ELPname2 | ELPname3 | ELPname4 | ELPname5 | ELPname6 | era | ethnicity | extinct | fam1 | fam2 | fam3 | fam4 | fam5 | fam6 | fam7 | fam8 | fam9 | fam10 | fam11 | fam12 | fam13 | fam14 | fam15 | family | familycolor | fontcolor | glotto | glotto2 | glotto3 | glotto4 | glotto5 | glottoname | glottoname2 | glottoname3 | glottoname4 | glottoname5 | glottopedia | glottorefname | glottorefname2 | glottorefname3 | glottorefname4 | glottorefname5 | guthrie | ietf | image | imagealt | imagecaption | imagescale | iso1 | iso1comment | iso2 | iso2b | iso2comment | iso2t | iso3 | iso3comment | iso6 | isoexception | lc1 | lc2 | lc3 | lc4 | lc5 | lc6 | lc7 | lc8 | lc9 | lc10 | lc11 | lc12 | lc13 | lc14 | lc15 | lc16 | lc17 | lc18 | lc19 | lc20 | lc21 | lc22 | lc23 | lc24 | lc25 | lc26 | lc27 | lc28 | lc29 | lc30 | lc31 | lc32 | lc33 | lc34 | lc35 | lc36 | lc37 | lc38 | lc39 | lc40 | ld1 | ld2 | ld3 | ld4 | ld5 | ld6 | ld7 | ld8 | ld9 | ld10 | ld11 | ld12 | ld13 | ld14 | ld15 | ld16 | ld17 | ld18 | ld19 | ld20 | ld21 | ld22 | ld23 | ld24 | ld25 | ld26 | ld27 | ld28 | ld29 | ld30 | ld31 | ld32 | ld33 | ld34 | ld35 | ld36 | ld37 | ld38 | ld39 | ld40 | linglist | linglist2 | linglist3 | linglist4 | linglist5 | linglist6 | lingname | lingname2 | lingname3 | lingname4 | lingname5 | lingname6 | lingua | lingua2 | lingua3 | lingua4 | lingua5 | lingua6 | lingua7 | lingua8 | lingua9 | lingua10 | linguaname | linguaname2 | linguaname3 | linguaname4 | linguaname5 | linguaname6 | linguaname7 | linguaname8 | linguaname9 | linguaname10 | listclass | liststyle | map | map2 | mapalt | mapalt2 | mapcaption | mapcaption2 | mapscale | minority | module | name | nation | nativename | notice | notice2 | official | posteriori | pronunciation | protoname | pushpin_image | pushpin_label | pushpin_label_position | pushpin_map | pushpin_map_alt | pushpin_map_caption | pushpin_mapsize | qid | ref | refname | region | revived | revived-cat | revived-category | script | setting | sign | signers | speakers | speakers_label | speakers2 | stand1 | stand2 | stand3 | stand4 | stand5 | stand6 | standards | state | states }}<templatestyles src="Template:Infobox/styles-images.css" />{{#invoke:Check for conflicting parameters|check

+

|preview=Page using [[Template:Infobox language]] with unknown parameter "_VALUE_"|ignoreblank=y| acceptance | agency | aiatsis | aiatsis2 | aiatsis3 | aiatsis4 | aiatsis5 | aiatsis6 | aiatsisname | aiatsisname2 | aiatsisname3 | aiatsisname4 | aiatsisname5 | aiatsisname6 | altname | ancestor | ancestor2 | ancestor3 | ancestor4 | ancestor5 | ancestor6 | ancestor7 | ancestor8 | ancestor9 | ancestor10 | ancestor11 | ancestor12 | ancestor13 | ancestor14 | ancestor15 | boxsize | coordinates | coords | created | creator | date | dateprefix | development_body | dia1 | dia2 | dia3 | dia4 | dia5 | dia6 | dia7 | dia8 | dia9 | dia10 | dia11 | dia12 | dia13 | dia14 | dia15 | dia16 | dia17 | dia18 | dia19 | dia20 | dia21 | dia22 | dia23 | dia24 | dia25 | dia26 | dia27 | dia28 | dia29 | dia30 | dia31 | dia32 | dia33 | dia34 | dia35 | dia36 | dia37 | dia38 | dia39 | dia40 | dialect_label | dialects | ELP | ELP2 | ELP3 | ELP4 | ELP5 | ELP6 | ELPname | ELPname2 | ELPname3 | ELPname4 | ELPname5 | ELPname6 | era | ethnicity | extinct | fam1 | fam2 | fam3 | fam4 | fam5 | fam6 | fam7 | fam8 | fam9 | fam10 | fam11 | fam12 | fam13 | fam14 | fam15 | family | familycolor | fontcolor | glotto | glotto2 | glotto3 | glotto4 | glotto5 | glottoname | glottoname2 | glottoname3 | glottoname4 | glottoname5 | glottopedia | glottorefname | glottorefname2 | glottorefname3 | glottorefname4 | glottorefname5 | guthrie | ietf | image | imagealt | imagecaption | imagescale | imageclass | iso1 | iso1comment | iso2 | iso2b | iso2comment | iso2t | iso3 | iso3comment | iso6 | isoexception | lc1 | lc2 | lc3 | lc4 | lc5 | lc6 | lc7 | lc8 | lc9 | lc10 | lc11 | lc12 | lc13 | lc14 | lc15 | lc16 | lc17 | lc18 | lc19 | lc20 | lc21 | lc22 | lc23 | lc24 | lc25 | lc26 | lc27 | lc28 | lc29 | lc30 | lc31 | lc32 | lc33 | lc34 | lc35 | lc36 | lc37 | lc38 | lc39 | lc40 | ld1 | ld2 | ld3 | ld4 | ld5 | ld6 | ld7 | ld8 | ld9 | ld10 | ld11 | ld12 | ld13 | ld14 | ld15 | ld16 | ld17 | ld18 | ld19 | ld20 | ld21 | ld22 | ld23 | ld24 | ld25 | ld26 | ld27 | ld28 | ld29 | ld30 | ld31 | ld32 | ld33 | ld34 | ld35 | ld36 | ld37 | ld38 | ld39 | ld40 | linglist | linglist2 | linglist3 | linglist4 | linglist5 | linglist6 | lingname | lingname2 | lingname3 | lingname4 | lingname5 | lingname6 | lingua | lingua2 | lingua3 | lingua4 | lingua5 | lingua6 | lingua7 | lingua8 | lingua9 | lingua10 | linguaname | linguaname2 | linguaname3 | linguaname4 | linguaname5 | linguaname6 | linguaname7 | linguaname8 | linguaname9 | linguaname10 | listclass | liststyle | map | map2 | mapalt | mapalt2 | mapcaption | mapcaption2 | mapscale | minority | module | name | nation | nativename | notice | notice2 | official | posteriori | pronunciation | protoname | pushpin_image | pushpin_label | pushpin_label_position | pushpin_map | pushpin_map_alt | pushpin_map_caption | pushpin_mapsize | qid | ref | refname | region | revived | revived-cat | revived-category | script | setting | sign | signers | speakers | speakers_label | speakers2 | stand1 | stand2 | stand3 | stand4 | stand5 | stand6 | standards | state | states }}<templatestyles src="Template:Infobox/styles-images.css" />{{#invoke:Check for conflicting parameters|check

Apologies. AquitaneHungerForce (talk) 15:19, 12 February 2026 (UTC)

Fixed. I also fixed the new parameter name to use the standard underscore between words; this template needs an overhaul to conform to the template parameter naming guidelines. – Jonesey95 (talk) 04:07, 15 February 2026 (UTC)

@Jonesey95 There are many more templates that would need fixing in that regard:

https://en.wikipedia.org/wiki/Special:Search?search=insource%3Aimageclass&fulltext=1&ns10=1

Of those, over half are infobox ones: https://en.wikipedia.org/wiki/Special:Search?search=insource%3Aimageclass+intitle%3AInfobox&fulltext=1&ns10=1

Anyways, I fixed all of the pages using imageclass for this template to image_class ~ oklopfer (💬) 04:57, 15 February 2026 (UTC)

Yes, there are many infobox templates that need their code adjusted to comply with standards that were developed after the templates' initial creation. There is no deadline, but it's nice to not dig the whole deeper. Thanks for adjusting the sandbox. – Jonesey95 (talk) 22:56, 21 February 2026 (UTC)

Template-protected edit request on 12 February 2026

Similar to the previous request regarding |image_class=, it would be helpful for there to be |map_class= and |map_class2= parameters to apply dark mode (I have confirmed these work with {{Infobox language/sandbox}}):

−

| data53 = {{#if:{{{map|}}} |{{#invoke:InfoboxImage|InfoboxImage|image={{{map}}}|upright={{if empty|{{{mapscale|}}}|1.15}}|alt={{{mapalt|}}}}}{{#if:{{{mapcaption|}}}|<div style="text-align:left;">{{{mapcaption}}}</div>}}| }} | data54 = {{#if:{{{map2|}}} | {{#invoke:InfoboxImage|InfoboxImage|image={{{map2}}}|upright={{if empty|{{{mapscale|}}}|1.45}}|alt={{{mapalt2|}}}}}{{#if:{{{mapcaption2|}}}|<div style="text-align:left;">{{{mapcaption2}}}</div>}} }}

+

| data53 = {{#if:{{{map|}}} |{{#invoke:InfoboxImage|InfoboxImage|image={{{map}}}|upright={{if empty|{{{mapscale|}}}|1.15}}|alt={{{mapalt|}}}|class={{{map_class|}}}}}{{#if:{{{mapcaption|}}}|<div style="text-align:left;">{{{mapcaption}}}</div>}}| }} | data54 = {{#if:{{{map2|}}} | {{#invoke:InfoboxImage|InfoboxImage|image={{{map2}}}|upright={{if empty|{{{mapscale|}}}|1.45}}|alt={{{mapalt2|}}}|class={{{map_class2|}}}}}{{#if:{{{mapcaption2|}}}|<div style="text-align:left;">{{{mapcaption2}}}</div>}} }}

−

... | map | map2 | mapalt | mapalt2 | mapcaption | mapcaption2 | mapscale ...

+

... | map | map2 | mapalt | mapalt2 | mapcaption | mapcaption2 | map_class | map_class2 | mapscale ...

Thank you! ~ oklopfer (💬) 15:49, 12 February 2026 (UTC)

 Done * Pppery * _{it has begun...} 23:35, 19 February 2026 (UTC)

ISO 639-1 lookup not working?

I was reading Old Church Slavonic and clicked the ISO 639-1 link, cu, but it brings up a bunch of irrelevant languages from Achinese to Standard Moroccan Tamazight, and no Old Church Slavonic or any Slavonic. I tried English language too, en, and the same thing happens (same languages and no modern English listed). Is it a problem with this template? — W.andrea (talk) 12:30, 7 April 2026 (UTC)

@W.andrea I think it's a problem with the LOC website. If you go to the search page, cu and en both show up under the Alpha-2 code search dropdown, yet when hitting the Go button, it brings you to the same page that has only Alpha-3s listed. They clearly used to work (cu en), but it looks like the database went down in February, and was giving the same results we see now a few weeks ago. They are still shown on the full list, but it doesn't seem like the same parameters can be passed to the link to get specific code entries. ~ oklopfer (💬) 14:46, 7 April 2026 (UTC)

I just made this change to {{ISO 639-1}} which seems to make it work again. Not sure if/when the original search function will ever be fixed, the website is just plainly broken with it, even when done from their GUI. ~ oklopfer (💬) 19:31, 4 May 2026 (UTC)

Edit request 25 April 2026

Description of suggested change: The image and image2 parameters currently use inconsistent scaling for {{{mapscale}}}. It is best to use a consistent scaling for the two parameters. I propose using a scale of 1.35, as this maximizes image visibility without being too large and taking up too much space.

Diff:

−

| data53 = {{#if:{{{map|}}} |{{#invoke:InfoboxImage|InfoboxImage|image={{{map}}}|upright={{if empty|{{{mapscale|}}}|1.15}}|alt={{{mapalt|}}}|class={{{map_class|}}}}}{{#if:{{{mapcaption|}}}|<div style="text-align:left;">{{{mapcaption}}}</div>}}| }} | data54 = {{#if:{{{map2|}}} | {{#invoke:InfoboxImage|InfoboxImage|image={{{map2}}}|upright={{if empty|{{{mapscale|}}}|1.45}}|alt={{{mapalt2|}}}|class={{{map_class2|}}}}}{{#if:{{{mapcaption2|}}}|<div style="text-align:left;">{{{mapcaption2}}}</div>}} }}

+

| data53 = {{#if:{{{map|}}} |{{#invoke:InfoboxImage|InfoboxImage|image={{{map}}}|upright={{if empty|{{{mapscale|}}}|1.35}}|alt={{{mapalt|}}}|class={{{map_class|}}}}}{{#if:{{{mapcaption|}}}|<div style="text-align:left;">{{{mapcaption}}}</div>}}| }} | data54 = {{#if:{{{map2|}}} | {{#invoke:InfoboxImage|InfoboxImage|image={{{map2}}}|upright={{if empty|{{{mapscale|}}}|1.35}}|alt={{{mapalt2|}}}|class={{{map_class2|}}}}}{{#if:{{{mapcaption2|}}}|<div style="text-align:left;">{{{mapcaption2}}}</div>}} }}

🪐Kepler-1229b | talk | contribs🪐 05:25, 25 April 2026 (UTC)

FYI seems like you might be using an older version of the template? This is what it looks like now:

| data53 = {{#if:{{{map|}}}
  |{{#invoke:InfoboxImage|InfoboxImage|image={{{map}}}|upright={{if empty|{{{mapscale|}}}|1.15}}|alt={{{mapalt|}}}|class={{{map_class|}}}}}{{#if:{{{mapcaption|}}}|<div style="text-align:left;">{{{mapcaption}}}</div>}}|
  }}

| data54 = {{#if:{{{map2|}}}
  | {{#invoke:InfoboxImage|InfoboxImage|image={{{map2}}}|upright={{if empty|{{{mapscale|}}}|1.45}}|alt={{{mapalt2|}}}|class={{{map_class2|}}}}}{{#if:{{{mapcaption2|}}}|<div style="text-align:left;">{{{mapcaption2}}}</div>}}
  }}

~ oklopfer (💬) 19:37, 4 May 2026 (UTC)

@Kepler-1229b whoops, forgot to ping. ~ oklopfer (💬) 19:38, 4 May 2026 (UTC)

Possibly. The {{if empty|{{{mapscale|}}}|1.15}} and {{if empty|{{{mapscale|}}}|1.45}} need to be changed to 1.35 for both. 🪐Kepler-1229b | talk | contribs🪐 19:42, 4 May 2026 (UTC)

Split the Altaic language family

I am proposing a split in the Atlaic language family colour into 5 different groups (Turkic, Mongolic, Tungusic, Japonic and Koreanic). I think it should be split due to Altaic being a sprachbund of language that aren't connected to each other as a language family. I want to discuss this before I propose an edit request. I have a proposal of the colours that I will show below, which I could change it if anyone else has problems with it, but I do believe Turkic should be red. Thank You.

•   Mongolic languages
•   Turkic languages
•   Tungusic languages
•   Japonic languages
•   Koreanic languages

Spino-Soar-Us (talk) 10:36, 11 May 2026 (UTC)

While we're on the subject of language family colo(u)rs, I think we should change the conlang family colour to a shade of gra/ey to avoid confusion with Macro-Jê languages. 🪐Kepler-1229b | talk | contribs🪐 19:44, 14 May 2026 (UTC)

I'm okay with that colour change, but I think we should focus on the Altaic languages first and figure out the right colouring for each language family. Spino-Soar-Us (talk) 06:30, 16 May 2026 (UTC)

@Spino-Soar-Us The French Wikipedia uses blue for Koreanic and Japonic, and green for the other three, so I think that something like that should be used, though optimally blue should be changed to something else to aviod cunfusion with American language families, not to mention the fact that both of these language families have hardly any languages in them, so a distinct colour is useless in that regard. 🪐Kepler-1229b | talk | contribs🪐 06:43, 16 May 2026 (UTC)

I tried making the colours above similar to each other above as much as I could, but I do believe that Turkic should be red as there aren't any red colours currently being used for language families. As for the amount of languages inside specific language families, there currently are other language families with less languages than any of the Altaic language families, so I don't think that's a huge problem. Spino-Soar-Us (talk) 07:28, 16 May 2026 (UTC)

If Turkic and Tungusic are red, it would make sens for Mongoic to be red as well. As for your second point, which ones? It would make more sense for Koreanic/Japonic to use the "isolate" colours as they are composed of one to two known languages. 🪐Kepler-1229b | talk | contribs🪐 19:43, 16 May 2026 (UTC)

I do agree with you that the Mongolic colour should be changed to a red colour now, but I don't know which type of red it should be. As for my second point, I was thinking about the Andamanese languages, but that is an extreme exception so I concede my point. Finally, I would be fine with a Koreanic-Japonic colour instead too. Spino-Soar-Us (talk) 08:15, 17 May 2026 (UTC)

Really, any shade of red different enough from preexisting colo(u)rs is fine, though prefereably a darker shade. For Koreanic/Japonic, I was thinking of the Tyrsenian languages. 🪐Kepler-1229b | talk | contribs🪐 17:58, 17 May 2026 (UTC)

Could you clalify what you mean by Tyrsenian languages, since they don't have a specific colour right now and I believe that's what you meant. Spino-Soar-Us (talk) 00:53, 18 May 2026 (UTC)

They used to use the "isolate: colo(u)r, but was changed for some reason. 🪐Kepler-1229b | talk | contribs🪐 01:06, 18 May 2026 (UTC)

I wouldn't put the Koreanic/Japonic languages as isolates as Koreanic includes the Jeju language and could incude the Han and Puyo languages, while Japonic includes the Ryukyuan languages. Spino-Soar-Us (talk) 03:25, 18 May 2026 (UTC)

I'd agree in that aspect. 🪐Kepler-1229b | talk | contribs🪐 03:26, 18 May 2026 (UTC)

The colors are basically to tell you when in the world you are, not to have a color for every family. Should we also have a distinct color for every family in PNG, or in Nilo-Saharan? Also, with American we already have a problem with colors so dark that you can't read the name of the language. That's been how long now, and we still haven't fixed it? — kwami (talk) 20:13, 16 May 2026 (UTC)

That's always been a problem with the conlang colo(u)r. 🪐Kepler-1229b | talk | contribs🪐 20:15, 16 May 2026 (UTC)

I just want to first mention that there is a problem with Hmong–Mien and Kra–Dai having colours that look closer to Austronesian and the language families in the bottom column that Sino-Tibetan and Austroasiatic. I said that to propose either making the Japonic-Koreanic family colour redish colour and the northern languages a green-ish colour or all of the language families redish colours and pushing down Hmong–Mien and Kra–Dai into the next column. I also think that Altaic is different from the Papuan languages and the Nilo-Saharan languages as it is easier to separate as there are less languages that need to be separated and the fact that Japonic and Koreanic aren't classified as a part of Altaic language group in the Altaic languages article. Spino-Soar-Us (talk) 08:36, 17 May 2026 (UTC)

There absolutely is a problem with Austroasiatic. It needs to be changes ASAP. 🪐Kepler-1229b | talk | contribs🪐 17:56, 17 May 2026 (UTC)

Why not keep Altaic various khaki/green? Instead of changing Mongolic, change Turkic and Tungusic? That would fit trans-Eurasian better. — kwami (talk) 20:13, 17 May 2026 (UTC)

I wouldn't make it Khaki since it would be too similar to tan, which is already the creole colour. Honestly, I don't 100% know what you're telling me for your second point, but if you are saying that Mongolic should remain the yellowgreen colour of the current Altaic languages colour, I am fine with it. Spino-Soar-Us (talk) 01:02, 18 May 2026 (UTC)

Edit request to complete TfD nomination

Template:Infobox language has been listed at Templates for discussion (nomination), but it was protected, so it could not be tagged. Please add:

{{subst:tfm|help=off|type=sidebar|1=Infobox language family}}

to the top of the page to complete the nomination. Thank you. PPEMES (talk) 14:47, 5 June 2026 (UTC)

Proposed new variables

• Proto-language (or possibly add this as one variable being (Ancestor?) Language family/Proto-language
• Descendant languages (alternative termed Daughter languages)
• Linguistic homeland
• Language changes
• Dialects and/or Dialect continuum

PPEMES (talk) 16:04, 5 June 2026 (UTC)

Oppose per TfD nom. 🪐Kepler-1229b | talk | contribs🪐 04:10, 7 June 2026 (UTC)

"Dialects" and "descendant languages" are all already present; dialect continuua can be applied using the "dialect" parameter. "Linguistic homeland" and "language changes" are not exactly appropriate for living languages; language changes is too broad and best explained in the body of the article. "Proto-language" can be used with the "ancestor" parameter. 🪐Kepler-1229b | talk | contribs🪐 04:15, 7 June 2026 (UTC)