This template is within the scope of WikiProject Infoboxes, a collaborative effort to improve the coverage of Infoboxes on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InfoboxesWikipedia:WikiProject InfoboxesTemplate:WikiProject InfoboxesInfoboxes
This template is within the scope of WikiProject Languages, a collaborative effort to improve the coverage of languages on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.LanguagesWikipedia:WikiProject LanguagesTemplate:WikiProject Languageslanguage
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)[reply]
This template must be followed by a complete and specific description of the request, so that an editor unfamiliar with the subject matter could complete the requested edit immediately.
Edit requests to template-protected pages should only be used for edits that are either uncontroversial or supported by consensus. If the proposed edit might be controversial, discuss it on the protected page's talk page before using this template. Consider making changes first to the template's sandbox and test them thoroughly here before submitting an edit request. To request that a page be protected or unprotected, make a protection request. When the request has been completed or denied, please add the |answered=yes parameter to deactivate the template.
Presently 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)[reply]
(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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
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. Kanguole09:33, 27 February 2025 (UTC)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
@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)[reply]
When {{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)[reply]
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)[reply]
Edit request 26 April 2025
This edit request has been answered. Set the |answered= parameter to no to reactivate your request.
This template must be followed by a complete and specific description of the request, so that an editor unfamiliar with the subject matter could complete the requested edit immediately.
Edit requests to template-protected pages should only be used for edits that are either uncontroversial or supported by consensus. If the proposed edit might be controversial, discuss it on the protected page's talk page before using this template. Consider making changes first to the template's sandbox and test them thoroughly here before submitting an edit request. To request that a page be protected or unprotected, make a protection request. When the request has been completed or denied, please add the |answered=yes parameter to deactivate the template.
_-_The_Noun_Project.svg){kind=small}
