Template talk:Infobox language
Latest comment: 3 months ago by A455bcd9 in topic Edit request 26 April 2025
 | This template was considered for merging with Template:Infobox proto-language on 5 January 2025. The result of the discussion was "keep". |
 | Template:Infobox language is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
 | To help centralize discussions and keep related topics together, the talk pages for all subtemplates and submodules redirect here. |
 | This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
| |||||||||||||||
_-_The_Noun_Project.svg){kind=small}
| 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 11, 12 |
|
|
This page has archives. Sections older than 240 days may be auto-archived by Lowercase sigmabot III if there are more than 4. |
Edit request 5 January 2025
edit | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Could we change the text color for Pano-Tacanan and Macro-Je please? they are barely visible. — Preceding unsigned comment added by ZKevinTheCat (talk • contribs) 05:41, 5 January 2025 (UTC)
Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. Nardog (talk) 02:28, 7 January 2025 (UTC)
- I believe the change being referred to here is that the Pano-Tacanan and Macro-Je language colors should have white text like the color for conlangs, since the text is barely visible. 🪐Kepler-1229b | talk | contribs🪐 04:16, 12 February 2025 (UTC)
- Please make the exact edit you want made to the appropriate template sandbox for this and the below requests. * Pppery * it has begun... 20:44, 30 March 2025 (UTC)
- I believe the change being referred to here is that the Pano-Tacanan and Macro-Je language colors should have white text like the color for conlangs, since the text is barely visible. 🪐Kepler-1229b | talk | contribs🪐 04:16, 12 February 2025 (UTC)
Template-protected edit request on 5 January 2025
edit| | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Can someone please add the {{subst:tfm|Infobox proto-language}} tag to this template so I can nominate it for merging with {{Infobox proto-language}}. I've already added it to that template just now because it's not currently protected. PK2 (talk; contributions) 09:11, 5 January 2025 (UTC)
Edit request 13 February 2025
edit| | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Description of suggested change: I propose adding two new language family colors to this template; namely those for Chibchan languages and Tucanoan languages. Diff:
| − | + | CHANGED_TEXT |
🪐Kepler-1229b | talk | contribs🪐 05:26, 13 February 2025 (UTC)
Set `mapscale=1` by default?
editPresently by default maps tend to stretch out the infobox to fill up half the reading area unless one manually specifies a figure like |mapscale=1. I think 1 is a pretty reasonable default value. If there are any issues or objections please let me know. Remsense ‥ 论 15:17, 26 February 2025 (UTC)
- I feel a larger scale, like 1.35, might make it easier to see the images. The UNESCO endangerment images are notably hard to see. 🪐Kepler-1229b | talk | contribs🪐 🪐Kepler-1229b | talk | contribs🪐 16:02, 26 February 2025 (UTC)
- (Side note, we should not be putting the UNESCO rating images there at all—see the above discussion from a few months back. It's misusing the parameter for something it was very clearly not designed for, also. I would appreciate help in removing the rest that I haven't gotten around to yet.)
- Like I said, I think the solution here is generally cropping the map or just putting it in the article body instead. These are cramped confines, and a global political map is very often not a good medium at thumbnail size to begin with on Wikipedia. Remsense ‥ 论 16:05, 26 February 2025 (UTC)
- I feel that including visual information for a given language's endangerment (or extinction) would be helpful, but there should be information in the text that discusses the language's sociolinguistic situation. 🪐Kepler-1229b | talk | contribs🪐 20:02, 26 February 2025 (UTC)
- It is certainly something that can be mentioned with the article body, but to reemphasize: the categories are not universally accepted, the data is old, and the presentation purposefully draws a direct parallel between biological diversity and language vitality which I find personally to be particularly inappropriate. Remsense ‥ 论 20:06, 26 February 2025 (UTC)
- In the discussion above a suggestion was made to use Glottolog's evaluation. If SVG graphics can be made for this we could implement this and replace the current UNESCO atlas graphics, which are outdated anyway. 🪐Kepler-1229b | talk | contribs🪐 20:16, 26 February 2025 (UTC)
- I would be apprehensive about a graphic. If in the infobox, I would prefer we implement a parameter for listing it as plain text. Remsense ‥ 论 20:19, 26 February 2025 (UTC)
- Moving back to the issue of mapscale, I would prefer a scale of 1.35 to make certain maps larger, and most global maps are only used for large-scale discussions of languages/families, or large macrofamilies which are not gfenerally accepted. 🪐Kepler-1229b | talk | contribs🪐 22:12, 26 February 2025 (UTC)
- If a map can't comfortably fit in the infobox, the first impulse should be to move it out of the infobox, not bloat the layers width along its entire height. The parameter can always be specified manually when that is deemed best, but 1.35 is a terribly ill fitting default. Remsense ‥ 论 22:20, 26 February 2025 (UTC)
- Then what would you suggest, if 1 would be unsuitable? 🪐Kepler-1229b | talk | contribs🪐 01:14, 27 February 2025 (UTC)
- I think 1.1 or 1.15 may be alright for readers' default settings, as long as the map isn't stretching out the infobox by default. Remsense ‥ 论 01:17, 27 February 2025 (UTC)
- Agreed. I believe 1.15 is better that 1, mainly due to a lack of visibility for 1. 🪐Kepler-1229b | talk | contribs🪐 01:42, 27 February 2025 (UTC)
- A default of 1 seems to leave too much unused horizontal space with the default settings.
{{Infobox country}}has a default of 1.15. Anything more than 1.25 would make the box wider, which should be avoided. I agree that the invented graphics for endangerment should go. Kanguole 09:33, 27 February 2025 (UTC)- I believe that visual information on a language's endangerment would be helpful, so instead of outright removing the current graphics, we could perhaps replace them with graphics for a more updated endangerment classification. 🪐Kepler-1229b | talk | contribs🪐 19:50, 27 February 2025 (UTC)
- I'm now reading the 2018 paper by the authors.[1] Given it's not clear from the label what "Shifting" means, it probably needs to be visually presented in context of the other categories. I've started working on a SVG graphic for this purpose. Remsense ‥ 论 22:32, 27 February 2025 (UTC)
- I believe that visual information on a language's endangerment would be helpful, so instead of outright removing the current graphics, we could perhaps replace them with graphics for a more updated endangerment classification. 🪐Kepler-1229b | talk | contribs🪐 19:50, 27 February 2025 (UTC)
- A default of 1 seems to leave too much unused horizontal space with the default settings.
- Agreed. I believe 1.15 is better that 1, mainly due to a lack of visibility for 1. 🪐Kepler-1229b | talk | contribs🪐 01:42, 27 February 2025 (UTC)
- I think 1.1 or 1.15 may be alright for readers' default settings, as long as the map isn't stretching out the infobox by default. Remsense ‥ 论 01:17, 27 February 2025 (UTC)
- Then what would you suggest, if 1 would be unsuitable? 🪐Kepler-1229b | talk | contribs🪐 01:14, 27 February 2025 (UTC)
- If a map can't comfortably fit in the infobox, the first impulse should be to move it out of the infobox, not bloat the layers width along its entire height. The parameter can always be specified manually when that is deemed best, but 1.35 is a terribly ill fitting default. Remsense ‥ 论 22:20, 26 February 2025 (UTC)
- Moving back to the issue of mapscale, I would prefer a scale of 1.35 to make certain maps larger, and most global maps are only used for large-scale discussions of languages/families, or large macrofamilies which are not gfenerally accepted. 🪐Kepler-1229b | talk | contribs🪐 22:12, 26 February 2025 (UTC)
- I would be apprehensive about a graphic. If in the infobox, I would prefer we implement a parameter for listing it as plain text. Remsense ‥ 论 20:19, 26 February 2025 (UTC)
- In the discussion above a suggestion was made to use Glottolog's evaluation. If SVG graphics can be made for this we could implement this and replace the current UNESCO atlas graphics, which are outdated anyway. 🪐Kepler-1229b | talk | contribs🪐 20:16, 26 February 2025 (UTC)
- It is certainly something that can be mentioned with the article body, but to reemphasize: the categories are not universally accepted, the data is old, and the presentation purposefully draws a direct parallel between biological diversity and language vitality which I find personally to be particularly inappropriate. Remsense ‥ 论 20:06, 26 February 2025 (UTC)
- I feel that including visual information for a given language's endangerment (or extinction) would be helpful, but there should be information in the text that discusses the language's sociolinguistic situation. 🪐Kepler-1229b | talk | contribs🪐 20:02, 26 February 2025 (UTC)
References
- ^ * Hammarström, Harald; Castermans, Thom; Forkel, Robert; Verbeek, Kevin; Westenberg, Michel A.; Speckmann, Bettina (2018). "Simultaneous Visualization of Language Endangerment and Language Description". Language Documentation & Conservation. 12. University of Hawaiʻi Press. ISSN 1934-5275.
Glottolog ACE parameter graphic?
edit
Continuing above convo, I'm not sure this is going to work so far, for the sole reason that the abbreviations used by ACE aren't at all intuitive, so it's not clear what meaning SH should have in relation to MB or TH etc. Remsense ‥ 论 22:06, 28 February 2025 (UTC)
| EGIDS | 6b (Threatened) |
|---|
- That seems less accessible than just adding a field with a text value like
- Kanguole 22:52, 28 February 2025 (UTC)
- I think so too. @Kepler-1229b, what do you think? I would be on board with adopting EGIDS more readily even, as it is much more multidimensional and less teleological in its categories, while remaining useful.Remsense ‥ 论 00:41, 1 March 2025 (UTC)
- Pretty good so far. EGIDS should be good. 🪐Kepler-1229b | talk | contribs🪐 01:02, 1 March 2025 (UTC)
- @Kepler-1229b you mean regarding Kanguole's textual parameter? That is what I would prefer for the reasons stated.
- I also think we should consider excluding the parameter for both safe (0–6a) and extinct (10) languages, as those statuses are fairly obvious and do not require infobox placement imo. Remsense ‥ 论 00:35, 3 March 2025 (UTC)
- I was referring to the created graphic. A textual parameter would also work. I also agree that extinct and safe languages do not need to be included. 🪐Kepler-1229b | talk | contribs🪐 01:24, 3 March 2025 (UTC)
- Pretty good so far. EGIDS should be good. 🪐Kepler-1229b | talk | contribs🪐 01:02, 1 March 2025 (UTC)
Edit request 18 March 2025
edit| | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Add two new language family colors: Chibchan languages and Tucanoan languages. 🪐Kepler-1229b | talk | contribs🪐 22:54, 18 March 2025 (UTC)
- This is a duplicate of #Edit request 13 February 2025. * Pppery * it has begun... 20:43, 30 March 2025 (UTC)
Two invocations of AIATSIS create a problem
editWhen {{AIATSIS}} is used on the same page twice, an ugly red text appears in the references stating that there are two references named AIATSIS. Is it possible to fix it? See the Uradhi language as an example (the problem had appeared after the merge). Thank you in advance! Викидим (talk) 04:46, 21 March 2025 (UTC)
- I can think of 2 approaches -- [1] create a special AIATSIS param for a 2nd info box that will generate a ref with a different name, or [2] have each AIATSIS entry generate a separate reference
- With [2] we could just use 'aiatsis6' as the parameter for the second info box in the Uradhi article, and we'd also have 6 references to AIATSIS, one for each code we use — kwami (talk) 10:31, 21 March 2025 (UTC)
Edit request 26 April 2025
edit| | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
"e28" in "ref" does not work for {{e28}}.
Diff:
| − | + | CHANGED_TEXT |
a455bcd9 (Antoine) (talk) 14:57, 26 April 2025 (UTC)
- Fixed at {{Infobox language/ref}}. – Jonesey95 (talk) 15:35, 26 April 2025 (UTC)
- Thanks! a455bcd9 (Antoine) (talk) 06:43, 5 May 2025 (UTC)