Jump to content

Template talk:Infobox language/language family color table

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Caucasian languages

[edit]

Should Kartvelian languages and North Caucasian languages have the same colour? The language families are not related with each other. Jaqeli 19:40, 19 July 2014 (UTC)[reply]

In this case the colour code seems to refer to languages spoken in the same geographic area, even though they may not be related. Altaic and American languages use the same pattern in the color table. De728631 (talk) 22:31, 28 July 2014 (UTC)[reply]
And is it right to have them like that? All defined language families should have their own family color methinks. Do you think it can be changed or further discussion are possible for such changes? Jaqeli 11:16, 29 July 2014 (UTC)[reply]
[edit]

The Tidy bug affecting font tags wrapping links has crashed into this template. The problem is in the markup

|colspan="17" style="background-color:{{Infobox language/family-color|Conlang}}"|<font style="color:white; background-color:black">{{Infobox language/genetic|Conlang}}</font>

The old Tidy processor moved the font color (white) into the link. The new Remex processor keeps the font color outside the link, where the default link color overrides. The default link color (blue) is very hard to see against a black background. For a comparison on how this looked under the old Tidy processor vs the new Remex processor, see this comparison. To solve an obsolete HTML lint error, the markup

<font style="...">...</font>

should be replaced with

<span style="...">...</span>

but that would not solve the real problem of making the link color white. —Anomalocaris (talk) 16:28, 6 July 2018 (UTC)[reply]

Colors not on the table

[edit]

Andamanese, Algic and Uto-Aztecan languages have their own colors not shown in the table, could someone fix and check if this happens to any other language families/groups ? — Preceding unsigned comment added by 138.36.47.213 (talk) 13:13, 20 February 2020 (UTC)[reply]