Content deleted Content added

Inline

Revision as of 15:12, 7 February 2006

Documentation

English
English
Pronunciation	/ˈɪŋɡlɪʃ/
Region	(see below)
Native speakers	360 million (cited 2010); L2: 375 million and 750 million EFL
Language family	Indo-European Germanic West Germanic Anglo–Frisian Anglic English; ; ; ; ;
Writing system	English alphabet (Latin script)
Signed forms	Manually coded English
Official status
Official language in	54 countries; 27 non-sovereign entities; United Nations; European Union; Commonwealth of Nations; Council of Europe; IOC; NATO; NAFTA; OAS; OECD; OIC; PIF; UKUSA Agreement;
Language codes
ISO 639-1	en
ISO 639-2	eng
ISO 639-3	eng
Glottolog	stan1293
Linguasphere	52-ABA
	Countries where English is the native language of the majority of the population Countries where English is an official but not primary language
	This article contains IPA phonetic symbols. Without proper rendering support, you may see question marks, boxes, or other symbols instead of Unicode characters. For an introductory guide on IPA symbols, see Help:IPA.

; Archives
	January 2005 — November 2005; November 2005 — December 2005; ; ;

This template is used on many pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them.

This template employs intricate features of template syntax.

You are encouraged to familiarise yourself with its setup and parser functions before editing the template. If your edit causes unexpected problems, please undo it quickly, as this template may appear on a large number of pages.
You can conduct experiments, and should test all major changes, in either , the general template sandbox, or your user space before changing anything here.

This template uses Lua:

This template is for use in articles about languages or dialects. It provides a common standard for displaying data about a language.

Usage

Syntax

Template:CompactDocToc purge

Documentation

Template loop detected: Template talk:Infobox Language/Usage

Move

the current Template:Infobox Language is a private version of User:Netoholic and should be moved to his user space or to Template:Infobox Language new. He has no right to abuse the standard name to (in the long run) delete the history of the original template.

If needed a bot can change all article references from Language to Language Infobox. As Commander Kean told me, asking at Wikipedia:Bot requests gives fast help in general. Netoholic pointed out no bot should be used to do this, because a redirect is sufficient. But this is a different matter. This voting is only about having the true language infobox at Template:Infobox Language. Tobias Conradi (Talk) 23:29, 5 January 2006 (UTC)[reply]

support - standard name for infobox Tobias Conradi (Talk) 23:29, 5 January 2006 (UTC)[reply]

result

not moved - please take destination template to WP:TfD if you wish to so, thanks WhiteNight ^{T | @ | C} 09:10, 11 January 2006 (UTC)[reply]

I don't think it should be deleted. Tobias Conradi (Talk) 21:14, 11 January 2006 (UTC)[reply]

moved to {{{Infobox Language}}} Tobias Conradi (Talk) 05:59, 7 February 2006 (UTC)[reply]

Discussion

Template:Infobox Language

Netoholic has created this template as a version that avoids conflict with WP:AUM. However, he has done this with no discussion, and I am not happy with the result. I am posting this here so that those who use this template might be aware of what he's doing. --Gareth Hughes 18:40, 31 December 2005 (UTC)[reply]

I warned users on this page (#Wikipedia:Avoid_using_meta-templates) weeks ago, and noone was forthcoming. I am beginning to convert the "simpler" language articles into this new infobox. I have started with a pilot group of a few articles, but everytime I try and make progress, Garzo rollbacks my edits. Garzo's displeasure is irrelevant, because WP:AUM trumps anything else that this template has been hacked into doing. I'm not sure how much functionality can be packed into the non-meta-template version, but if even half can be converted quickly, that is an improvement. -- Netoholic @ 08:59, 1 January 2006 (UTC)[reply]

Garzo! Thanks for informing us! What Netoholic is doing is realy bad. He warned us, lol. You have my full support of reverts. Furthermore I am not even sure if WP:AUM really applies here, I raised the question on a different issue [1] (a template that's not edited because it is protected) but nobody could tell a reference in WP:AUM that's states how this could harm the servers. So if our subtemplates are stable soon, they may get protected. Tobias Conradi (Talk) 16:06, 1 January 2006 (UTC)[reply]

No one can deny that meta-templates (templates that have other templates in them) are harmful to the servers. It's documented in Wikipedia:Avoid using meta-templates. The sooner the non-meta Infobox Language can be fully implemented the better.--Commander Keane 18:07, 1 January 2006 (UTC)[reply]

Why this arrogance and agressive wording? (no one can deny - arrogance because you don't seem to have read my previous posting, aggressive because you speak of 'no one can deny' - as if we others are idiots.) From WP:AUM _I_ could NOT learn that meta-templates are harmful to the servers. EDITING meta-templates is harmful. The non-meta Infobox is quite bad design as of now. Why could Netoholic not implement his "improvements" in the language template and by doing so keep the history ... of Garzo's and other peoples great work? and go with the other editors. Why did he need to work where is work could not be seen and switch the templates without informing here? Tobias Conradi (Talk) 07:19, 2 January 2006 (UTC)[reply]

Wikipedia:Request_for_Arbitration#User:Netoholic Tobias Conradi (Talk) 07:35, 2 January 2006 (UTC)[reply]

(Tobias got the following on his talk) bad form: Dude, poisoning the well is a shitty tactic. Please remove this comment, since it's only put there to take a cheap shot at me. -- Netoholic @ 17:49, 2 January 2006 (UTC)[reply]
Thanks for the link to "poisoning the well". I didn't want to descredit you here with the RfA. So I am sorry if this impression was left. I thought it might be related. Especially after you defended your reverts with the words that you warned users (and now have some right of replacing?) and that "Garzo rolls back your progresses".
Please come here and try to present some ideas. I think we are all quite open to reduce the serverload. AFAIK there are more than 7000 ISO 639-3 language codes, so the effect of this template may be huge if we have it on 7000 pages one day. Tobias Conradi (Talk) 20:51, 3 January 2006 (UTC)[reply]

Meta-templates require extra calls to render. This is independent of editing a meta-template. From WP:AUM...

Here's some technical background which may be of use. Jamesday 07:52, 13 Feb 2005 (UTC) and clarified by LarryLACa 00:22, 11 November 2005 (UTC) (Clarifications show in []'s).

[The impact of meta-templates is two fold. a) They are more expensive to render. b) editing them has an immediate database affect, regardless of whether the pages using them are currently being accessed.]

[Re: Rendering impact: The first time a page is viewed, i.e. after it has been removed from caches, the page request causes several steps:]

* Each item in the base page portion is requested from the database (images and CSS aren't in the main part). The page you edit, each template, each template included in the template and so on. Two templates, two database records to be retrieved. One template on its own, one read, one template including another, two. Plus the one for the base page.

* Once that and the rest of what is called the parsing is done, the page is saved in the parser cache. That's kept in RAM in memcached.

* Finally the skin is applied and the page is passed on to the Squids, which cache it in RAM and on disk (to get larger capacity but at slower access time) for all who aren't logged in (will only be useful if it's the normal skin) and send it on to the person who originally requested it.

[So meta-templates are more expensive to render, and the impact shows up when the page is requested.].

Maybe I'm the idiot, but this looks clear to me. Meta-templates (even when if they are protected against editing) are to be avoided. Am I wrong?--Commander Keane 10:37, 2 January 2006 (UTC)[reply]

Harmful effects -> Server load -> When a meta-template is edited, many pages need to be updated in a single instance
if it's not edited it is less harmful, I assume.
the two templates = two DB calls stuff is _not_ specific to meta templates. one could also say: don't use two templates in one page
it is WP:AUM, not WP:DUM (don't use meta templates) Tobias Conradi (Talk) 20:23, 3 January 2006 (UTC)[reply]

I believe that we should improve the technical aspect of this template by phasing out its reliance on other templates. I approve of any suggestions that could help here. However, we have built this template on consensus over a long time: we are linguists and understand something of the complexity of the world's languages and the need for a flexible template to serve them. We were made aware of WP:AUM, and have been watching the debate there. I would like proposals of how to make this template more serve friendly made here, and trialled in full view, not concocted and imposed in secret. I am in full agreement with WP:AUM: just in case anyone misreads my actions. However, I see that it mandates no one user to apply the policy, and believe that changes should be made in the usual Wikipedia way: user agree and developing the change together. This is the natural progression of things. I have implored Netoholic to work with others, but he seems only capable of imposing his own ideas. I have reverted the implementation of the new template in articles as it has not been agreed. Read this well: I am not talking about WP:AUM, but the unilateral implementation of this template. Thank you for quoting the policy again above; I understand it and wish to see it implemented. However, as one who has been deeply involved in the develoment of this template, I wish to remain so, and repeat the request that we work together. --Gareth Hughes 17:14, 2 January 2006 (UTC)[reply]

Hey guys, please stop arguing. Template:Infobox Language was nothing more than a place for me to demonstrate how much can be done without resorting to meta-templates. There is simply no way to make these changes to the present template since it is so intricate and over-thought, and in such wide use. Unfortunately, it was discovered by Garzo/Gareth before I could properly introduce it and he, failing to assume good faith, interpreted that page's existence as some "secret" effort. Geez, the template is still marked "Inuse" because it still needs work. -- Netoholic @ 17:51, 2 January 2006 (UTC)[reply]

You implemented in articles, and you havea history of being argumentative and disruptive. This page was not informed about your 'demonstration': it looks very much the opposite to what you say. --Gareth Hughes 17:54, 2 January 2006 (UTC)[reply]

I implemented in precisely four articles, and no information was lost in any of them. Though it worked on those, the template was still not ready to show off. Now, please stop with the personal remarks. -- Netoholic @ 18:09, 2 January 2006 (UTC)[reply]

I think other contributors to this page know who I am, and know my history: that speaks for itself. I find it difficult to understand the 'not ready to show off'/'only implemented in four articles' confusion: if it's not ready it should not be in any articles. The nature and future of the template is the business of this discussion page and Wikipedia talk:WikiProject Languages: that latter page has had no discussion of the issue. I am annoyed because you are unilaterally changing (adding the thing to articles without discussion) a WikiProject's template without letting the project know or being a prior member of that project. It is useful to enlighten us about our failure to live up to certain policies and guidelines and to help us keep them, but is not useful to impose your will thus on other users. --Gareth Hughes 20:58, 2 January 2006 (UTC)[reply]

Wikipedia's in sore need of some server relief, and this template was the grand-daddy of all offenders of WP:AUM. I've put in place my best attempt at this template, without using meta-templates. Improve away. Unless you need my help, I'm going to pretty much be done with this. Please put your energies into improving this non-meta-templated version rather than squabble about who-did-what. -- Netoholic @ 22:37, 3 January 2006 (UTC)[reply]

If you want to get rid of the meta-templates you don't need to make a new template. Why anyone would want to make a completely new template to fix this problem and push it through so aggressively is beyond me. If the problem was just server load, the reverts of the current template would obviously been just as effective. But this strikes me as just being as tactless as it is unilateral. I understand Garzo's frustration and I would like to Netoholic to calm down and have some patience about such a major undertaking before we get enbroiled in yet another drawn out dispute resolution.

Peter ^Isotalo 12:44, 7 January 2006 (UTC)[reply]

New template

Thanks to the new template, the Ido page no longer displays the symbol it used to contain. Please fix it, thanks. Mithridates 22:19, 3 January 2006 (UTC)[reply]

There were a handful of complaints about the template doing really stupid things in the last few minutes: you can post complaints to user talk:Netoholic. --Gareth Hughes 22:36, 3 January 2006 (UTC)[reply]

Netoholic tried out a new technique to avoid using meta-templates. This technique uses a CSS kludge that will not work on Wikipedia mirrors (unless they use Wikipedia CSS). It broke a great load of templates. We have already discussed that the family colour is not implemented. However, this is the least of the problems. Ido's infobox went really funny. There is a nice question on talk:Macedonian language about what a lawngreen language is: apparently the template ended up classifying Macedonian as such a language. All the multiple ISO 639-3 codes disappeared and were replaced with bare template code. When I've worked on this template, I've tested everything fully before altering the template itself. Not only must the server load from these bad edits by fairly high, but this must be considered vandalism: wrecking a few hundred articles. --Gareth Hughes 23:20, 3 January 2006 (UTC)[reply]

it was probably not WP:Vandalism.
some of the subtemplates could be put back in the main, reducing harm-effect serverload, but actually WP:AUM also mentions harm-effect editibility. I think meta-templates can increase editibility. Garzo, can you protect the colorfile? And change the file only once a month? Maybe all color request should be placed in the talk of that file? Tobias Conradi (Talk) 14:44, 4 January 2006 (UTC)[reply]

Over at Wikipedia talk:Avoid using meta-templates there is a growing consensus that we start using WeebleCode, a kind of parameter kludge, rather than hiddenStructure, a CSS kludge. This could deal with every template:qif call in this template. I have been working on a different way of including certain of the sub-templates in the body of the main template, but it makes more sense to use WeebleCode throughout. The only drawback to this approach is that the parameter |if= (an empty parameter) would have to be added to every article to make the kludge workable. This can be done by a bot if we can get one. All colour changes have been discussed over at Wikipedia talk:WikiProject Languages so far, and there has been no vandalism of the array. Actually, vandalism of this array isn't much fun: you can swap the colours around, but, if you add anything else, everything goes white. I don't think we want to protect it at the moment. --Gareth Hughes 15:23, 4 January 2006 (UTC)[reply]

It is disingenuous to say the "only drawback" is the |if= (empty parameter). I'm not going to re-hash the arguments here (discussion is better held on WT:AUM), but some significant other problems exists with that method. -- Netoholic @ 16:11, 4 January 2006 (UTC)[reply]

I just returned from the WP:AUM talk page. The WeebleCode did look kind of complicated. Where in the articles does the if need to be added? Protecting: Fun or not, we should be able to state to any AUM-reviewer that we did our best. No problem if you protect it, colors are not changed every day. Why not protect? Or should we add the colors to the main temp? Tobias Conradi (Talk) 16:08, 4 January 2006 (UTC)[reply]

Again: why not protect. It is also listed at WP:AUM#Alternatives. Tobias Conradi (Talk) 18:51, 5 January 2006 (UTC)[reply]

I didn't want to be accused of 'stonewalling' again, but I shall protect the sub-templates. The WeebleCode is just another kludge: the |if= parameter can be added anywhere in the template call, just like any other parameter. There are different drawbacks to all three proposals: using 'meta-templates', hiddenStructure and WeebleCode. There has been no real discussion or evidence about the weighted pros and cons of each, so it's still difficult to decide. I proposed WeebleCode because a few people with more expertise than I reckoned it a better option. I have a couple of little tweaks in draft that could be added to this template, and should simplify it and reduce the number of sub-templates needed. So, in the meantime, I'll work on those to see if they are viable, and let you know when I think they're ready for a trial. --Gareth Hughes 19:24, 5 January 2006 (UTC)[reply]

sometimes I like using mirros. Look to the stonewall argument throught the mirror and you may see the one who posted it, to be the stonewaller. ;-) Tobias Conradi (Talk) 20:27, 5 January 2006 (UTC)[reply]

Template move to Infobox Language - blocked by Netoholics template

the folowing talk is copied from Tobias and Netohlics talk pages Tobias Conradi (Talk) 20:27, 5 January 2006 (UTC)[reply]

Hi Netoholic, I would like to move Template:Infobox Language to somewhere, maybe your user-space? Than we can move Template:Language -> Template:Infobox Language , what is a standard conform name for Infoboxes. I will ask for a bot than, to change the articles. Maybe we also find some other task the bot could in the same run. ... and yes, hopefully we can at least reduce some load made by the language. I think the language-project people don't want to be the bad guys that put unecessary server load. best regards Tobias Conradi (Talk) 18:45, 5 January 2006 (UTC)[reply]

I'd rather not move this. It will prove to be more useful for the coming conversion since we can migrate to Template:Infobox Language over time. -- Netoholic @ 18:50, 5 January 2006 (UTC)[reply]

That would destroy the whole history of the template. Lets bring the original box there and than look for changes. Please don't lock the improvement regarding naming, by your box, a box that currently almost nobody wants to implement. Let's seperate the issues on template-naming and on template-content. Tobias Conradi (Talk) 18:55, 5 January 2006 (UTC)[reply]

Please don't think naming is nearly as important as content. Doing a bot run to replace a single redirect is not critical or even desirable. What is important is the flagrant WP:AUM abuse taking place on Template:Language. -- Netoholic @ 18:59, 5 January 2006 (UTC)[reply]

I don't think the two issues have the same importance and never thought so. Take care of your usage of the word abuse. Why is it unwanted to have a bot help switch to using correct names? Tobias Conradi (Talk) 19:04, 5 January 2006 (UTC)[reply]

Single redirects are no big deal, and no one and no bot should find it necessary to replace them. It is just busywork with no gain. It just adds to the bandwidth and creates an unnecessary extra version in the page history, adding to database space needed. -- Netoholic @ 19:06, 5 January 2006 (UTC)[reply]

I thought to have read something diff for template redirects. Than we could switch to correct name without bot use? That would be very good. How about the css-version moved to Template:Infobox Language new? Tobias Conradi (Talk) 19:12, 5 January 2006 (UTC)[reply]

prepare RfC Netoholic

Netoholic wrong edits summary:

Tobias Conradi (Talk) 19:54, 6 January 2006 (UTC)[reply]

http://en.wikipedia.org/w/index.php?title=Template%3AInfobox_Language&diff=34198909&oldid=34192230

2005-01-15 basic change without talk http://en.wikipedia.org/w/index.php?title=Template%3ALanguage&diff=35241199&oldid=35175651

I am tearing my hair out: Netoholic has just re-added his conlang template to all these articles, and invented template:Infobox Sign language and added that to all the sign languages. There is enough evidence to show this user is disruptive and refuses to work with others. --Gareth Hughes 23:20, 16 January 2006 (UTC)[reply]

Conversion

I converted {{language/familycolor}} from a meta-template (it used to call {{switch}}) to a single template and made corresponding changes to how it is called in this template. Please let me know if this breaks any pages. If it works correctly that removes one level of meta'ing on this template. We can probably start removing these nested conditions one at a time. --CBD _☎ ^✉ 22:04, 6 January 2006 (UTC)[reply]

I installed this re-written {{Language/familycolor}} into the call for {{Infobox language}}. Since this is called and set as a parameter for the call to the language template it avoids the problems of meta-templating, but gives the same family colors functionality. An example can be seen at Template talk:Infobox Language. I also made some minor formatting adjustments to make the new box look more like the current one. Let me know what else should be adjusted. --CBD _☎ ^✉ 02:07, 7 January 2006 (UTC)[reply]

Since Netoholic reverted my changes and has slapped 'inuse' on the template again I have made a copy at User:CBDunkerson/Sandbox2. That page also shows samples of what the non-meta version looks like (on the left) against the current meta version (on the right). Currently my goal is to copy the existing Template:Language as closely as possible without using meta-templates at all. Still a work in progress, but please take a look and let me know what should be adjusted. If everyone agrees that the template has reached a usable state we can then move it into the proper location and make any adjustments to the articles calling it as needed. --CBD _☎ ^✉ 16:48, 7 January 2006 (UTC)[reply]

what changes are needed in the articles? Tobias Conradi (Talk) 19:37, 7 January 2006 (UTC)[reply]

Nothing specifically yet. What I'm saying is that if we implement a new template with parameter changes (such as changing the 'state' parameter to 'official' as you suggest) then all the calls to the template in the individual articles will need to be updated to reflect any and all such changes. --CBD _☎ ^✉ 20:38, 7 January 2006 (UTC)[reply]

What is going on?!?

Excuse me, but what is going on with this template? I think it's good as it is. Bomac 19:59, 7 January 2006 (UTC)[reply]

Short answer: WP:AUM says that the sort of meta-templating used to make this template work is bad for the servers and must be reduced. Netoholic has written a new Template:Infobox language template which doesn't use meta-templating, but also doesn't have the same capabilities. I'm trying to adjust a copy of his template at User:CBDunkerson/Sandbox2 to match the capabilities of the current template. Various edit wars and conflicting adjustments have gone on around all of this.

Longer answer: Read this page and associated links from here down. --CBD _☎ ^✉ 20:36, 7 January 2006 (UTC)[reply]

ISO 639 - none

Garzo / CBD, can we add "none" or so to the ISO 639 code fields? E.g. Montenegrin language has no code. But the reader would not know whether it is simply missing or does not exist. I think it is interesting for discussion whether something is considered language by ISO or not. Even if SIL/ISO is not _the_ authority to decide this (or any) it is interesting what they think. Tobias Conradi (Talk) 21:39, 11 January 2006 (UTC)[reply]

The current chaos really prohibits doing anything constructive with the template. We could change the default of the parameter to 'none' instead of '—'. Most languages don't have an ISO 639-1 code, many constructed languages don't have an ISO 639-3 code. Because ISO 639-2 has a comprehensive set of collective codes every language should be able to find an appropriate one. I thought about having ISO 639-1 optional for all languages, and ISO 639-3 optional for constructed languages. However, this AUM cult has scuppered those plans. ISO 639-3 is still in draft format, and there are a good number of cases for new codes pending. --Gareth Hughes 23:01, 11 January 2006 (UTC)[reply]

default should be '-'. 'None' would be explicit statement that there is none. Don't care about the new codes, they can be added. Hey and this clowny Neto can't stop us from improving the infobox? Cheers Tobias Conradi (Talk) 23:26, 11 January 2006 (UTC)[reply]

Two wishes: I would like the explicite 'none' statement. AFAICS for ISO 639 1 & 2 we could do so already. For 639-3 a link would be created, this should be avoided. the second gets an extra section Tobias Conradi (Talk) 03:34, 20 January 2006 (UTC)[reply]

Go ahead and make updates. It looks like WP:AUM is going to be severely downgraded/changed or scrapped altogether. Brion, the lead developer, has said that the server load problems aren't that big a deal and will be handled on the dev side if/when needed. Meta-templates are still considered 'ugly' and to be avoided when possible, but better that than all the problems which the CSS hack has been introducing. The '|if=' parameter trick can still be used, but only if it is an easier/nicer way to do things than meta-templates like 'qif' would be. --CBD _☎ ^✉ 12:16, 23 January 2006 (UTC)[reply]

OK. I think Montenegrin language is a bad example as it is usually considered to be a Serbian dialect. However, it would be useful to look again at how we present the codes. I've suggested that we might look at incorporating the Linguasphere language code into the template (discussion here). The ISO 639-1 codes are only given to major world languages, so many languages simply will not have one. The default text is an em-dash, but we might want to change that to read none, as not having a part-one code is the most likely reason why it's not in the infobox. I have thought about making this row removable, so that languages without a part-one code could skip it. However, it is perhaps useful to state that these languages do not have any code assigned them under part one. In part two, every language should be able to find a suitable code, as part two provides 'collective' codes. If an infobox is lacking a part-two code, it is most likely that the authors cannot find the appropriate code. Part three does not allow such collective codes and is attempting to be comprehensive. The real problem with part-three codes is with constructed languages: most will not have any code assignment in this part of the standard. We could make this field optional for constructed languages. In the meantime, I'll move the to be added notice from the default for {{{iso3}}} to {{{iso2}}} (it was added before the ISO 639-3 codes were added to articles), and make none the default for {{{iso3}}} and {{{iso1}}}. --Gareth Hughes 14:55, 23 January 2006 (UTC)[reply]

Don't ! If someone adds a new article and cannot look up the code/ is lazy he will not add it. for iso3 the default should be "---". "none" should only be displayed if some looked for the code and there was none. That's an explicit none than. for iso1 default none is ok, because all the articles do allready exist, the code set does not change, is small, can easily be looked up. Tobias Conradi (Talk) 04:22, 24 January 2006 (UTC)[reply]

Yes, I see the logic in that. I've changed the default for {{{iso3}}} to an em-dash, but left the option that when the parameter is equal to none it returns the text none. I hope that looks right now. --Gareth Hughes 13:24, 24 January 2006 (UTC)[reply]

script / alphabet

can we include script? maybe it could be done by using an array like for the families. So we stay flexible as for where the link goes and how to analyze the script variable. Maybe the IPA notice can later on depend on the script and can be removed. I once read someone thinking about codes for scripts - does anyone know about it? what about alphabet? Tobias Conradi (Talk) 03:34, 20 January 2006 (UTC)[reply]

I think the neutral term would be writing system. The easiest implementation of this would be to have an optional row that can be added to the infobox that allows a blank field to be edited (e.g. |script=[[Latin alphabet]]). This would allow the maximum flexibility, but would make automatic changing of the footer notice more difficult. A code-based array might work, but would be more complicated to put together. --Gareth Hughes 12:14, 23 January 2006 (UTC)[reply]

I really prefer array, especially after WP:AUM seems to have been downgraded. if "script" is incorrect the variable should be IMO "write", "writing", "writingsystem". I tend to "write" because it is short. Tobias Conradi (Talk) 04:26, 24 January 2006 (UTC)[reply]

I was thinking of 'Writing system' as the text to be displayed in the left-hand column: {{{script}}} seems like a good name for the parameter. I just wonder whether a code based array would be flexible enough. There are many languages with two or three different writing systems, or a different system used in different eras or places. On the positive side, many such languages have a single page covering the various differen systems (e.g. Mongolian alphabet). Some languages use a well-known system, but have a separate page on that language's implementation of the system (e.g. Welsh alphabet). I wonder how to fit this amount of information into a parameter. --Gareth Hughes 13:35, 24 January 2006 (UTC)[reply]

ok, array seems not to be (easily) feasible. Before starting let's maybe analyze what will be put in. for param name: are the writing system all called scripts? if not i would prefer no to use script, or only use it for scripts. Tobias Conradi (Talk) 03:17, 25 January 2006 (UTC)[reply]

List, please improve:

Latin
Latin modified
Latin with diacritics
Latin with extra letters (azeri)
Russian cirillic
Serbian cirillic and Latin modified (serbian)
Katagana, Hiragana (japanese)
...

Template:Infobox Conlang

Please view discussion about this template on Wikipedia talk:WikiProject Languages#Template:Infobox Conlang. -- Netoholic @ 07:14, 12 January 2006 (UTC)[reply]

Moved thread replies. PLEASE keep the conversation on the WikiProject talk page. -- Netoholic @ 17:27, 12 January 2006 (UTC)[reply]

Announcement

I am kindly requesting all interested parties to review discussion regarding this template on my talk page: User talk:Ezhiki#Infobox:Language issues and User talk:Ezhiki#Infobox:Language proposed solution. I realize that I should have announced it a lot earlier than this, but I did not expect the discussion to take as long as it did. Your attention and comments will be much appreciated.—Ëzhiki (ërinacëus amurënsis) 16:32, 16 January 2006 (UTC)[reply]

maps

Image:Niger-Congo.png IMO we should upload an image with the project colors. Tobias Conradi (Talk) 03:46, 20 January 2006 (UTC)[reply]

I think the colors are fine, but here's the complete list of those maps anyways:

--Khoikhoi 01:29, 21 January 2006 (UTC)[reply]

I know when I was looking at this I was confused by the colour changes - probably indicates a bear of little brain, but there will be others like me out there. I like Tobias' suggestion if someone has time to do it. Gailtb 08:52, 21 January 2006 (UTC)[reply]

Interesting idea to highlight the main subject. Did not knew this feature before. Nevertheless I tend to prefer the project-color way. Is SVG format better? I am not an image professinal. And never did any SVG file. If we have a worldwide map with project colors in SVG we can then cut whatever regions / language groups we want. Tobias Conradi (Talk) 19:06, 21 January 2006 (UTC)[reply]

I created this series some time ago. I have been collecting comments over at the commons version. I have been meaning to update the series for some time now, so I might give the colors a shot. However, I must say I quite like the current coloring. As Tobias says, in the four individual maps, the main subject is highlighted. I think this is only confusing when one puts them next to each other, but normally they are seen in the context of their respective articles so then there's no problem. As for switching to the project colors, one of the problems would be that the distinction between Niger-Congo (A) and Niger-Congo (Bantu), which serves to show the extent of the massive Bantu family, would be lost. — mark ✎ 09:14, 27 January 2006 (UTC)[reply]

I might suggest using both methods. That is, use the 'highlight' method to make the language(s) being addressed more prominent, but leave the languages around it on the map in their project colors. This might require some adjustments to the color scheme to take visual presentation on a map into account (and remove the 'highlight' color from the normal scheme), but would help to standardize when looking at maps in different articles. Alternatively, you could use these 'highlight' maps as they are but then have an overall 'language distribution' map using the project colors when not highlighting any one language/group. --CBD _☎ ^✉ 12:01, 27 January 2006 (UTC)[reply]

Templates for Deletion

I am happy to announce the following polls:

As I'm not looking forward to the next time Netoholic decides to spread these all over the article space, I thought we might as well vote them out of use. --Gareth Hughes 14:25, 24 January 2006 (UTC)[reply]

Pronunciation

I've created Template:Language/pronunciation and modified Template:Language to optionally include the pronuncation of a particular language.

The syntax added in template:language is simply

 {{if defined
   |test={{{pronunciation|}}}
   |call=language/pronunciation
   |1=1={{{pronunciation|}}}}}

See the effect in English language, German language and French language. --Hello World! 04:49, 27 January 2006 (UTC)[reply]

This works well; thank you. --Gareth Hughes 13:57, 27 January 2006 (UTC)[reply]

I added the substed equivalent of {{IPA}} so it should display properly for everyone, too. --Angr 14:43, 27 January 2006 (UTC)[reply]

Since I previously argued for it, I'm very happy to see this parameter. I wonder about a couple of small improvements:

Would it be better to have the label as "Native name /pronunciation:" (ie move the native name down from its current position)? That way it would be absolutely clear what the pronunciation is of.
When using it on pages, shouldn't there be / / or [ ] around the IPA (cf Hungarian language)?

Gailtb 19:52, 27 January 2006 (UTC)[reply]

Yes, Gail, I think that we might want a more descriptive left-hand column than 'pronunciation'. However, I feel that moving the native name out of the header reduces its importance (somewhen there was a debate that concluded that we should try not to place the native name below the English name, but beside it). On the second point, you are quite correct about proper transcription of IPA (I often get so worried about the squiggles that I forget what goes round them). I suppose we should aim for a fully phonetic representation, but in practice this might be untidy and divisive (which dialect do we use?). --Gareth Hughes 20:38, 28 January 2006 (UTC)[reply]

Propose tweaks to template

It seems that the template is triggered into sign language mode in one of two ways: by assigning a value to the "signers=" parameter or by familycolor=sign. Oftentimes even an estimate of the number of signers is just not possible — but when familycolor=sign and no "signers=" value is assigned, it seems that the family is still given as "sign language" rather than "unknown" (see Turkish Sign Language). I'm not sure how to change this myself, sorry, but I would like to see the family as "unknown" in both cases.

Also, I don't know how easy it is to make a further change, but I would prefer the when the family is unknown to just have the text "unknown" in the infobox, not "unknown" followed by the language name. (see German Sign Language for example).

Thirdly, the bottom bar of the sign language template has two links - sign language and list of sign languages - very nice! But the sign language link is written as "sign languages" so unless there is a reason for this I'd like to remove the "s". Thanks! ntennis 00:10, 28 January 2006 (UTC)[reply]

Things would work much better if sign languages used their own infobox, tailored specifically for their needs. -- Netoholic @ 00:43, 28 January 2006 (UTC)[reply]

I'm happy to go with consensus either way on this. I don't think others are opposed in principle to a seperate sign language template either, but what are the pros and cons? IIRC we went with a single template for simplicity and unity, and it does work well as is. I guess if there was a seperate template, it would require less esoteric syntax, and i could make the changes myself without bothering the brainy coders like Garzo! ntennis 01:02, 28 January 2006 (UTC)[reply]

You're part of making the consensus. Unfortunately, using one language template gives "unity" but falls very short on simplicity/elegance. A separate template would not require any esoteric syntax. Like you said, you could make changes as needed. The main language template likewise becomes much simpler, as well. Keeping the "look" the same is no different than other infoboxs are handled (the WikiProject keeps Template:Infobox Arcade Game and Template:Infobox CVG in a common style). I had created a reasonable Template:Infobox Sign language, but that was prematurely nominated for deletion for somewhat emotional reasons. It's yours if you want to go ahead with it. -- Netoholic @ 03:07, 28 January 2006 (UTC)[reply]

The changes ntennis is requesting would be no more or less complex with multiple templates rather than a single one. He's asking for differences in the default presentation of sign languages. Easy enough to implement if people agree they make sense. --CBD _☎ ^✉ 16:02, 28 January 2006 (UTC)[reply]

The fact that he has to ask someone else to make the changes because this template's code is so complex is the problem. -- Netoholic @ 00:45, 29 January 2006 (UTC)[reply]

Maybe it's because it's protected too. You probably haven't noticed but conditionals have moved a lot of the formatting out of the template calls and into the template. That means it is easier to modify the template contents. --Gareth Hughes 00:51, 29 January 2006 (UTC)[reply]

It's only semi-protected, and even that doesn't seem to have any reason. And what are you talk about... my version of separate sing language template didn't require any special "formatting" on the article side. -- Netoholic @ 05:50, 29 January 2006 (UTC)[reply]

Protecting important stuff (here: "used a lot" stuff) isn't that bad. Some templates just shouldn't be treated like articles when editing. There is nothing wrong with doing the change work in a sandbox on the side, presenting it on the talk, gathering consenus for it and then asking an admin to apply it (in the case of full protection). Revert warring forth and back, as you prefer and in-situ surgery is just bad for the servers, something which you usually care a lot. --Adrian Buehlmann 10:14, 29 January 2006 (UTC)[reply]

Yeah, this isn't really a problem. I've corrected template:language/signnotice so that it bypasses the redirect to sign language (that's point 3 dealt with). You are correct about the way the sign-language options are triggered. The initial idea was that these options would be turned on by having the parameter {{{signers}}} defined in the call. However, I then realised that there often isn't adequate data about the number of signers of a given language. That's where 'familycolor=Sign' comes in: it triggers the options without anything needed for {{{signers}}}. The 'genetic classification' box is designed to build itself out of available information. If it is given nothing else, it has text determined from unclassified with the text of {{{name}}} in bold below. The complete override for this is {{{family}}}. If that parameter is defined, its contents will be put into the box instead of the automatic stuff. The first line can be altered separately by using {{{fam1}}}. However, as we are looking at a global solution for sign languages, it seems a bit much to use these workarounds. As I understand it (correct me if I'm wrong), we want the automatic text in the 'genetic classification' box for sign languages to read simply "unknown" (and nothing else) as a default. I'll test it out, and if it works OK, I'll upload it. --Gareth Hughes 20:59, 28 January 2006 (UTC)[reply]

I didn't do the best job of it, but the infobox should now display as requested for sign languages. --Gareth Hughes 22:42, 28 January 2006 (UTC)[reply]

Brilliant! Thanks again. ntennis 23:22, 28 January 2006 (UTC)[reply]

Can I suggest getting rid of the term Genetic classification on this template? Guinnog 18:30, 5 February 2006 (UTC)[reply]

Can someone incorporate this change [2] (Alphabet) into the wiki machine? Ksenon 19:43, 5 February 2006 (UTC)[reply]

Guinnog, what do you suggest as an alternative?
- 'Language family' Guinnog 16:24, 6 February 2006 (UTC)[reply]
- On the grounds that we are not talking about genes but about language here. Guinnog 01:15, 7 February 2006 (UTC)[reply]

Ksenon, which change do you wish to see incorporated where (elaborate)? --Gareth Hughes 13:16, 6 February 2006 (UTC)[reply]

I believe Ksenon was referring to this change to add an alphabet line. Might make sense, though I'd suggest making it optional. Does get complicated with languages which have more than one alphabet used though. 'Moldovan' and Sindarin come to mind. It's somewhat similar to the recent change to show the name of the language in its natural script and might be combined with that. --CBD _☎ ^✉ 13:32, 6 February 2006 (UTC)[reply]

Bot

Could we get a bot to make the change from {{language}} to {{Infobox Language}}? — mark ✎ 13:20, 7 February 2006 (UTC)[reply]

There is no significant benefit in replacing that text, since the redirect leaves everything working fine. Update it late when there is some substantive change to the articles, or if a change is made to how this template is used. -- Netoholic @ 15:12, 7 February 2006 (UTC)[reply]

{{Infobox language
| name             =
| altname          =
| nativename       =
| acceptance       =
| image            =
| imagescale       =
| imagealt         =
| imagecaption     =
| pronunciation    =
| states           = <!-- or state -->
| region           =
| creator          =
| created          =
| setting          =
| ethnicity        =
| extinct          =
| era              =
| speakers         =
| date             =
| dateprefix       =
| ref              = <!-- up to e26 (or current edition) if reference is Ethnologue -->
| refname          =
| speakers2        =
| revived          =
| revived-category = <!-- or revived-cat -->
| familycolor      =
| family           =
| fam1             =
| fam2             =
| fam3             = <!-- up to fam15 -->
| protoname        =
| ancestor         =
| ancestor2        = <!-- up to ancestor8 -->
| standards        =
| stand1           =
| stand2           = <!-- up to stand6 -->
| dialects         =
| listclass        =
| dia1             =
| dia2             = <!-- up to dia20 -->
| script           =
| sign             =
| posteriori       =
| nation           =
| minority         =
| agency           =
| development_body =
| iso1             =
| iso1comment      =
| iso2             =
| iso2b            =
| iso2t            =
| iso2comment      =
| iso3             =
| iso3comment      =
| lc1              =
| ld1              =
| lc2              = <!-- up to lc30 -->
| ld2              = <!-- up to ld30 -->
| iso6             =
| isoexception     =
| linglist         =
| lingname         =
| linglist2        = <!-- up to linglist6 -->
| lingname2        = <!-- up to lingname6 -->
| glotto           =
| glottorefname    =
| glotto2          = <!-- up to glotto5 -->
| glottorefname2   = <!-- up to glottorefname5 -->
| aiatsis          =
| aiatsisname      =
| aiatsis2         = <!-- up to aiatsis6 -->
| aiatsisname2     = <!-- up to aiatsisname6 -->
| guthrie          =
| ELP              =
| ELPname          =
| ELP2             = <!-- up to ELP6 -->
| ELPname2         = <!-- up to ELPname6 -->
| glottopedia      =
| lingua           =
| lingua_ref       =
| ietf             =
| map              =
| mapscale         =
| mapalt           =
| mapcaption       =
| map2             =
| mapalt2          =
| mapcaption2      =
| pushpin_map      =
| pushpin_image    =
| pushpin_map_alt  =
| pushpin_map_caption =
| pushpin_mapsize  =
| pushpin_label    =
| pushpin_label_position  =
| coordinates      = <!-- use {{Coord}} -->
| module           =
| notice           = IPA
}}

References in infobox

Parameters

The required parameters are:

name: name of language
familycolor: appropriate language family. Possible values are listed in the colored chart to the right (or above, depending on your browser). Please do not use other names, because they will not be recognized, and the table will be colored grey.; In most cases, 'familycolor' will trigger a default entry for the 'fam1' field, so that field is not necessary (you can continue with 'fam2'), but you can override this by entering something under 'fam1'.; Areal colors (American, Khoisan, Altaic, etc.) represent areal codings, and are *not* claims that the language belongs to that family. When these are used, the fam1 parameter must be set to the widely accepted language family.; If 'isolate' or 'unclassified' is used, the fam1–xx tree will not display. In order to allow levels of classification, as with dialects of a language isolate, enter "grey"/"gray" instead.

Other parameters are listed below, they can be incorporated anywhere between the first and last lines, and in any order.

altname: additional name of the language [not every one, but one a reader would be likely to look for]
nativename: native name, or a second alternative name [most cases as of 2012 not actually the native name] (if nativename is to be used, and altname parameter MUST be defined)
pronunciation: pronunciation of the native name of the language in IPA → remember to enclose the transcription in an IPA template such as {{IPA}}
acceptance: questionable acceptance/status of the language: unattested, spurious, etc.
states: countries in which it is mainly spoken. You do not have to define both this and region. Do not use flag icons (WP:INFOBOXFLAG). Direct links to country articles are generally not useful, and distract from useful links. Consider 'Languages of [country]' or '[ethnicity] in [country]' links instead.
state: alias for states
region: geographic region in which it is mainly spoken. You do not have to define both this and states; use this parameter for a single statement about geographic distribution. It is not for the broader region where the states are located, but rather the regions within the country, or across countries, where it is spoken. (That is, do not add SE Asia if we state it's in Laos, or West Africa if we state it's in Mali.)
ethnicity: people for whom this is the ethnically native language; also good for the ethnic population if different from the number of speakers (although the names chosen for the articles on the people and on the language will generally be the same, it may be appropriate to pipe in the native name of the people here)
era: era of use of a historical language, such as one that developed into something else; 'speakers' will not display
extinct: date of extinction, or information about extinction; 'speakers' will not display
revived: Date and/or population of attempted revival of extinct language
revived-category: (or revived-cat) optional name (without "Category:") of appropriate subcategory of Category:Language revival (which is used by default if |revived= has a value); can be given as |revived-category=nocat to suppress the categorization entirely, when the language has a separate article about its revival that is already in the category (e.g. Cornish revival is in Category:Celtic language revival, so | is used in the infobox at Cornish language).

dia1

...
dia20: primary dialects
dialects: whatever you want to say; dia1–xx will not display
listclass: class for the dia1–xx list: plainlist (default), hlist (horizontal) or flatlist (bulleted)
stand1: a standardized register
stand2: a second standardized register; ...
stand6: sixth standardized register
standards: whatever you want to say
script: writing system(s) used for the language by literate speakers, in the form script (instantiation), such as "Latin (English alphabet)"
(Common variants of "Latin (alphabet)" redirect to Latin script. For the Latin alphabet itself, add an element such as  .)
sign: signed forms (manually coded language)
nation: list of countries in which it is an official language
minority: list of countries in which it is a recognized/protected minority language. This is intended for legal protection and similar de jure recognition, not simply being listed on a census and other de facto recognition.
agency: regulatory body or language academy for the language
development_body: development body for the language
boxsize: overrides default width of infobox, currently set at 22em. Format must include units ("12em" or "123px").; Useful when an article has various infoboxes aligned in a column. (Box will automatically expand to fix map wider than default box width.)
fontcolor: color of font against 'familycolor' ← the font color is usually black, use this to change it if it is difficult to read
module: Used for embedding other infoboxes into this one.

Number of speakers

speakers: the number of native speakers of the language. If unknown, enter ⟨?⟩ and do not enter NA for the date (this causes the article to be listed in the Category:Language articles with speakers set to 'unknown', a hidden maintenance category). If no native speakers, enter ⟨none⟩. Otherwise, if no date is supplied, missing date will be displayed. Use {{sigfig|...|2}} to round to 2 significant figures while retaining the exact figure from the reference.
date: the date of publication of the estimate of the number of speakers.; Used for calculations for obsolete data, so needs to start with a 4-digit year (see next parameter). Exception: If ⟨NA⟩ is entered, nothing will display. If ⟨no date⟩ is entered, "no date" will display. Do not enter a date parameter at all if speakers is set to ⟨none⟩.; Articles with old dates (currently ≥ 30 years) appear in Category:Language articles with old speaker data.
dateprefix: any text wanted inside the parentheses before the date; a space ( ) must be explicitly included at the end
ref: reference for the speaker data; placed after the date, if any. This can be any inline citation or a predefined code such as e19, linglist, ne2010, etc. For more details, see the documentation at Template:Infobox language/ref.; If ⟨e26⟩ is entered, this will automatically generate a reference to the Ethnologue 26 article that bears the ISO 639-3 code entered at 'iso3'.; To link to the auto-generated reference from elsewhere in the article, use <ref name=e26/>.; ⟨e25⟩ and <ref name=e25/> or ⟨e24⟩ and <ref name=e24/> etc. can be used to reference earlier editions, for example for languages which are no longer supported by Ethnologue, or to give an idea of how old undated population figures are.; ⟨linglist⟩ and <ref name=linglist/> can be used to ref the MultiTree entry at the Linguist List.; ⟨ne2007/ne2010⟩ and <ref name=NE100/> can be used to ref the Swedish national encyclopedia, which we use for many of the world's top 100 languages; ⟨inali⟩ and <ref name=INALI/> can be used to ref Mexico's Instituto Nacional de Lenguas Indígenas; Similarly, aiatsis can be used to link to the <ref name=AIATSIS/> ref generated by the infobox for the AIATSIS entry for Australian languages. (For Maho's edition of the Guthrie list for Bantu languages, <ref name=Guthrie/> needs to be added manually, as they do not provide population data.)
refname: Name used in reference generated by certain 'ref' parameter values such as e19. It defaults to the value of the 'name' parameter or PAGENAME.
speakers2: a 2nd line for speaker data, such as 2nd estimate, 2nd country, L2 speakers, etc, appearing after the date.; If this is a second line of L1 speakers, it should be arranged so that, if there are two dates cited, the oldest appears in the date parameter, for automated update calculations. Data from different countries should not be added together if they are not comparable: say if one is from 1973 and another from 2006, or if one is rounded to the nearest million and another is on the order of 10,000.
speakers_label: The infobox label for the number of speakers is "Native speakers" by default. Set this parameter to |speakers_label = Speakers to change it to "Speakers" or |speakers_label = Signers to change it to "Signers" for sign languages.

Genetic classification

You can use the language template to show the genetic classification of a language as a descending staircase of language families, from the broadest to the most specific.

fam1: the broadest possible widely accepted language family of which the language is a part. If this would be exactly the same as you have defined for familycolor, it may be omitted.
fam2: a more specific sub-family; ...
fam15: most specific sub group

If you would prefer to enter some other information in this box (for example, disputed), use this parameter instead:

family: whatever you want to say; fam1–xx will not display. This can be set to "na" to avoid specifying a family relationship at all, an for a geographical group that has no single origin.

The template can also display a staircase of ancestral forms:

ancestor: ancestral or reconstructed form, if it has an article or has been assigned an ISO code
ancestor2: ...
ancestor8: intermediate ancestral forms
protoname: alias for ancestor

ISO language codes

iso1

the ISO 639-1 code for the language

iso1comment

for comments to not interfere with the link

iso2

the ISO 639-2 code for the language (not for its family); creates a link to the ISO page. If a language has two ISO 639-2 codes, use the following two separate fields instead.

iso2b

the ISO 639-2 bibliographic code (for languages with two ISO 639-2 codes)

iso2t

the ISO 639-2 terminological code (for languages with two ISO 639-2 codes)

iso2comment

for comments to not interfere with the link(s)

iso3

the ISO 639-3 code for the language; creates a link to the ISO page. See below for the situation where multiple ISO 639-3 codes apply.

Field will display even if left empty, unless 'lc1' etc. is used.

If there is no ISO 639-3 code, set |iso3=none to return the text none and add the article to Category:Languages without iso3 codes (if iso3comment is also used, that will display in place of none)

Leave empty for a dialect that has no iso3 code, but the language it belongs to does; in this case, also use |isoexception=dialect.

Leave empty for a historical variety that has no iso3 code, but its modern version does; in this case, also use |isoexception=historical.

Leave blank for a protolanguage, and use |isoexception=protolanguage.

Use 'linglist' if the language has an iso3 code, but this is maintained at Linguist List instead of at SIL. Add the code itself under |linglist=. (This is not necessary if the SIL page provides its own link to the Linguist List page.)

iso3comment

allows a comment in the ISO field that will not interfere with the link

isoexception

a maintenance field to organize cleanup categories for missing ISO codes. Excludes article from the Category:Language articles without language codes if set to any of the following values:

dialect (used for a dialect that does not itself have an ISO code, although the language it belongs to does; adds article to the Category:Dialects of languages with ISO 639-3 code)

historical (used for a historical language that does not itself have an ISO code, although its modern version does; adds article to the Category:Historical forms of languages with ISO codes)

protolanguage (used for protolanguages without ISO codes; adds article to the Category:Protolanguages without ISO codes)

talkpage (used on talk pages and in archives so that they don't show up in tracking categories)

Some languages have a number of ISO 639-3 codes, one for each dialect of that language. If you try putting all of these codes in the usual iso3 = parameter, it will get quite messy. Instead, use the following parameters:

lc1: ISO code of the first dialect (the 'iso3' field will not display if empty and this is included)
ld1: name of the first language dialect; plain text only; do not include references in this field
lc2: ISO code of the second dialect
ld2: name of the second language dialect; ...
lc30: ISO code of the 30–th dialect
ld30: name of the 30–th dialect
iso6: the ISO 639-6 code for the language.

Lc entries will be automatically linked to the Ethnologue site. Wikipedia articles on the dialects may be linked from the ld entries.

For languages with an ISO 639-3 macrolanguage code and several individual codes, use iso3 for the macrolanguage and lcn, ldn for the individual codes.

Other language codes

linglist: this parameter is deprecated due to unreliable data, with the exception of some long-extinct languages. For ISO 639-3 codes of extinct languages whose descriptions are maintained at Linguist List, enter the code under 'iso3' and the reader will be redirected from the ISO page.
lingua: the Linguasphere code for the language

glotto
glotto2

...
glotto5: the Glottolog code for the language. Enter "none" if Glottolog does not have a code for the language, "spurious" if Glottolog uses that term. [future: also "unattested"]
glottorefname
glottorefname2: ...
glottorefname5: the Glottolog name(s) for the language (optional). Substitute glottoname etc. if the name needs to be displayed in the info box.
guthrie: the Guthrie code for Bantu languages. Generates a reference which can be accessed via name="Guthrie".
aiatsis: the AIATSIS code for Australian languages. Generates a reference which can be accessed via name="AIATSIS". Site includes population data we can use.

aiatsis2

...
aiatsis6: additional AIATSIS codes

aiatsisname2

...
aiatsisname6: the AIATSIS name, if different from the entry at |name=, or note to appear after code
ELP: URL suffix of the language article on the Endangered Languages Project site. Manual override of a default module linking to the ELP article per WikiData settings. Either way generates a reference that can be accessed via name="ELP". Entering "none" prevents the default link (e.g. when there is more than one info box in the WP article). The ELP site includes population data we can use.
ELPname: name that will display for the ELP link and ref.; ...
ELP4: additional ELP links, or manual addition (rather than replacement) to the automated module link. Useful when changing WikiData might corrupt articles on other-language wikis (e.g. when the two wikis don't define the language with the same scope).

ELPname4

glottopedia: Glottopedia. Generates a reference which can be accessed via name="Glottopedia".
ietf: IETF language tag

Constructed languages

This template is appropriate to use for constructed languages. The following parameters can be used:

creator: name of language creator
created: year of first creation
setting: the use or setting for the language
posteriori: natural-language sources

Using these parameters, or setting familycolor=Conlang, automatically sets the colored bars of the infobox to /**/#114057 background with white fonts, and removes the states and region parameters from use (nation is also disabled). If the iso2 parameter is left undefined, it is treated as being iso2=art. For conlangs, the family or famn parameters are used to describe the hierarchy of purpose of the language, whereas posteriori is used to describe the a posteriori sources on which the conlang draws.

Maps and images

You should not put large images at the top of the language template: they just make it very messy. You can place a small image at the top of the template using the following parameters:

image: image at top of info box. Use format "image name.png", without "File:/Image:" or brackets.
imagescale: override default size of image display (currently set to "upright=0.9", producing 200px display in a non-customized account). Use fractions or multiples: "2" for twice user-default, "0.5" for half. "1.45" will cause the image to fill the width of the infobox.
imagealt: alt text for the image
imagecaption: caption to appear under the image
imageheader: brief header for the image ('logo', 'map', 'script', etc). This is placed in the left-hand column, and so needs to be short.

If you have a larger image or two, such as a map, you can place them at the bottom of the template, spanning both columns, with the following parameter:

map: image at bottom of info box. Use format "image name.png", without "File:/Image:" or brackets.
mapscale: override default size of map display (currently set to "upright=1.45", producing 320px and filling the width of the infobox in a non-customized account). Use fractions or multiples: "2" for twice user-default, "0.5" for half. Affects both maps.
mapalt: alt text for the map
mapcaption: caption to appear under map
map2: a second map
mapalt2: alt text for the second map
mapcaption2: caption to appear under both maps

The usual image markup applies for both images. Alt text is for visually impaired readers, and the caption is for all readers; typically they should have little in common (see WP:ALT).

For languages spoken in smaller areas, where the location of the language can be reasonably approximated by a point on the map, then a pushpin map can be added:

coordinates: latitude and longitude; use {{coord}}
pushpin_map: The name of a location map as per Template:Location map (e.g. Indonesia or Russia). The coordinate fields (from |coordinates=) position a pushpin coordinate marker and label on the map automatically. To show multiple pushpin maps, provide a list of maps separated by #, e.g., California#USA
pushpin_image: (optional) Allows the use of an alternative map; the image must have the same edge coordinates as the location map template.
Equivalent to AlternativeMap parameter in Template:Location map.
pushpin_mapsize: (optional) Must be entered as only a number—do not use px. The default value is 250. Equivalent to width parameter in Template:Location map.
pushpin_map_alt: (optional) Alt text for pushpin map; used by screen readers, see WP:ALT. Equivalent to alt parameter in Template:Location map.
pushpin_map_caption: (optional) Fill out if a different caption from map_caption is desired. Equivalent to caption parameter in Template:Location map.
pushpin_label: (optional) The text of the label to display next to the identifying mark; a wikilink can be used. If not specified, the label will be the text assigned to the name parameter, and if the name parameter is not specified, the article title. (if |pushpin_label_position=none, no label is displayed).
Equivalent to label parameter in Template:Location map.
pushpin_label_position: (optional) The position of the label on the pushpin map relative to the pushpin coordinate marker. Valid options are {left, right, top, bottom, none}. If this field is not specified, the default value is right.
Equivalent to position parameter in Template:Location map.

Footer notice

A notice or notices may be placed at the bottom of the infobox:

notice=ipa: places a notice about the Unicode fonts used for displaying IPA

Examples

Example 1

{{Infobox language
| name = English
| pronunciation = {{IPAc-en|ˈ|ɪ|ŋ|ɡ|l|ɪ|ʃ}}<ref>[http://www.oxfordadvancedlearnersdictionary.com/dictionary/english_2 English Adjective] – Oxford Advanced Learner's Dictionary – Oxford University Press ©2010.</ref>
| region = (see [[#Geographical distribution|below]])
| speakers = 360&nbsp;million
| date = 2010
| dateprefix = cited&nbsp;
| ref = <ref name=NE>[[Nationalencyklopedin]] "Världens 100 största språk 2010" The World's 100 Largest Languages in 2010</ref>
| speakers2 = [[Second language|L2]]: 375&nbsp;million and 750 million [[English as a foreign or second language|EFL]]<ref name=BritishCouncilEnglish>{{cite web |url=http://www.britishcouncil.org/learning-elt-future.pdf |title=Future of English|accessdate=24 August 2011 |publisher=The British Council}} (page 10)</ref>
| familycolor = Indo-European
| fam2 = [[Germanic languages|Germanic]]
| fam3 = [[West Germanic languages|West Germanic]]
| fam4 = [[Anglo-Frisian languages|Anglo–Frisian]]
| fam5 = [[Anglic languages|Anglic]]
| script = [[English alphabet]] ([[Latin script]])
| sign = [[Manually coded English]]
| nation = {{plainlist|
* [[List of countries where English is an official language#Sovereign states|54 countries]]
* [[List of countries where English is an official language#Non-sovereign entities|27 non-sovereign entities]]
* [[United Nations]]
* [[European Union]]
* [[Commonwealth of Nations]]
* [[Council of Europe]]
* [[International Olympic Committee|IOC]]
* [[NATO]]
* [[North American Free Trade Agreement|NAFTA]]
* [[Organization of American States|OAS]]
* [[Organisation for Economic Co-operation and Development|OECD]]
* [[Organisation of Islamic Cooperation|OIC]]
* [[Pacific Islands Forum|PIF]]
* [[UKUSA Agreement]]}}
| iso1 = en
| iso2 = eng
| iso3 = eng
| glotto = stan1293
| lingua = 52-ABA
| map = Anglospeak.svg
| mapcaption = {{legend|#0000ff|Countries where English is the native language of the majority of the population}} {{legend|#8ddada|Countries where English is an official but not primary language}}
| notice = IPA
}}

References in infobox

^ English Adjective – Oxford Advanced Learner's Dictionary – Oxford University Press ©2010.
^ Nationalencyklopedin "Världens 100 största språk 2010" The World's 100 Largest Languages in 2010
^ "Future of English" (PDF). The British Council. Retrieved 24 August 2011. (page 10)

Example 2

Persian
Fārsi
فارسی
Fārsi written in Persian (Nastaʿlīq script)
Pronunciation	[fyɒːɾˈsiː]
Native to	Iran Afghanistan (as Dari) Tajikistan (as Tajik) Uzbekistan (as Tajik) Iraq Russia
Native speakers	45 million (2007) – 60 million (2009) (110 million total speakers)
Language family	Indo-European Indo-Iranian Iranian Western Iranian Southwestern Iranian Persian
Early forms	Old Persian Middle Persian
Standard forms	Western Persian Dari Tajik
Dialects	Western Persian Dari Central Asian Persian (Tajik) Bukhori Pahlavani Hazaragi Aimaq Judeo-Persian Dehwari Judeo-Tat Caucasian Tat Armeno-Tat
Writing system	Persian alphabet (Iran and Afghanistan) Tajik alphabet (Tajikistan) Hebrew Persian Braille
Official status
Official language in	Iran (as Persian) Afghanistan (as Dari) Tajikistan (as Tajik)
Regulated by	Academy of Persian Language and Literature (Iran)
Language codes
ISO 639-1	`fa`
ISO 639-2	`per (B)` `fas (T)`
ISO 639-3	`fas` – inclusive code Individual codes: `pes` – Western Persian `prs` – Dari language (Afghan Persian) `tgk` – Tajiki `aiq` – Aimaq dialect `bhh` – Bukhori dialect `haz` – Hazaragi dialect `jpr` – Judeo-Persian `phv` – Pahlavani `deh` – Dehwari `jdt` – Judeo-Tat `ttt` – Caucasian Tat
Glottolog	`fars1254` Farsic – Caucasian Tat
Linguasphere	58-AAC (Wider Persian) > 58-AAC-c (Central Persian)
Areas with significant numbers of Persian speakers (including dialects)
Countries where Persian is an official language
This article contains IPA phonetic symbols. Without proper rendering support, you may see question marks, boxes, or other symbols instead of Unicode characters. For an introductory guide on IPA symbols, see Help:IPA.

{{Infobox language
| name             = Persian
| altname          = Fārsi
| nativename       = {{lang|fa|فارسی}}
| image            = Farsi.svg
| imagescale       = 0.5
| imagecaption     = ''Fārsi'' written in Persian ([[Nastaʿlīq script]])
| pronunciation    = {{IPA|fa|fyɒːɾˈsiː|}}
| states           = {{hlist|style=line-height:1.3em;
 | [[Languages of Iran|Iran]]
 | [[Languages of Afghanistan|Afghanistan]]&nbsp;(as [[Dari language|Dari]])
 | [[Languages of Tajikistan|Tajikistan]]&nbsp;(as [[Tajik language|Tajik]])
 | [[Languages of Uzbekistan|Uzbekistan]] (as Tajik)
 | [[Languages of Iraq|Iraq]]
 | [[Languages of Russia|Russia]]
 }}
| speakers         = 45 million (2007) – 60 million
| date             = 2009
| ref              =
| speakers2        = (110 million total speakers)
| familycolor      = Indo-European
| fam2             = [[Indo-Iranian languages|Indo-Iranian]]
| fam3             = [[Iranian languages|Iranian]]
| fam4             = [[Western Iranian languages|Western Iranian]]
| fam5             = Southwestern Iranian
| ancestor         = [[Old Persian]]
| ancestor2        = [[Middle Persian]]
| stand1           = [[Western Persian]]
| stand2           = [[Dari language|Dari]]
| stand3           = [[Tajik language|Tajik]]
| listclass        = hlist
| dia1             = [[Western Persian]]
| dia2             = [[Dari language|Dari]]
| dia3             = [[Tajik language|Central Asian Persian (Tajik)]]
| dia4             = [[Bukhori dialect|Bukhori]]
| dia5             = [[Pahlavani dialect|Pahlavani]]
| dia6             = [[Hazaragi dialect|Hazaragi]]
| dia7             = [[Aimaq dialect|Aimaq]]
| dia8             = [[Judeo-Persian]]
| dia9             = [[Dehwari dialect|Dehwari]]
| dia10            = [[Judeo-Tat]]
| dia11            = [[Tat language (Caucasus)|Caucasian Tat]]
| dia12            = [[Armeno-Tat]]
| script           = {{startplainlist}}
* [[Persian alphabet]] ([[Iran]] and [[Afghanistan]])
* [[Tajik alphabet]] ([[Tajikistan]])
* {{hlist |[[Hebrew alphabet|Hebrew]] | [[Persian Braille]]}}
{{endplainlist}}
| nation           = [[Iran]] (as Persian)<br />[[Afghanistan]] (as [[Dari language|Dari]])<br />[[Tajikistan]] (as [[Tajik language|Tajik]])
| agency           = {{longlink|[[Academy of Persian Language and Literature]]&nbsp;([[Iran]])}}
| iso1             = fa
| iso2b            = per
| iso2t            = fas
| iso3             = fas
| lc1              = pes
| ld1              = [[Western Persian]]
| lc2              = prs
| ld2              = [[Dari language]] (Afghan Persian)
| lc3              = tgk
| ld3              = [[Tajik language|Tajiki]]<!--This and the following codes aren't part of the macrolanguage per SIL-->
| lc4              = aiq
| ld4              = [[Aimaq dialect]]
| lc5              = bhh
| ld5              = [[Bukhori dialect]]
| lc7              = haz
| ld7              = [[Hazaragi dialect]]
| lc8              = jpr
| ld8              = [[Judeo-Persian]]
| lc9              = phv
| ld9              = [[Pahlavani language|Pahlavani]]
| lc10             = deh
| ld10             = [[Dehwari language|Dehwari]]
| lc11             = jdt
| ld11             = [[Judeo-Tat]]
| lc12             = ttt
| ld12             = [[Tat language (Caucasus)|Caucasian Tat]]
| glotto           = fars1254
| glottoname       = Farsic – Caucasian Tat
| lingua           = {{longitem|58-AAC (Wider Persian)<br />&nbsp;> 58-AAC-c (Central Persian)}}
| map              = Persian Language Location Map.svg{{!}}border
| mapcaption       = Areas with significant numbers of Persian speakers (including dialects)
| map2             = Iran, Afghanistan and Tajikistan.svg{{!}}border
| mapcaption2      = {{legend|red|Countries where Persian is an official language}}
| notice           = IPA
}}

References in infobox

Error-tracking categories

With 8,000 articles, manual review is insufficient. The following automating tracking categories should catch some of the more common errors. They also produce lists of articles that should be reviewed occasionally, because they lack population data or the data is dated.

ISO support

Category:Languages without ISO 639-3 code (53) – [iso3=] is set to 'none', as it is not (yet) included in ISO. May have other codes.
- Category:Conlangs without ISO 639-3 code (57) – subcat: most conlangs do not qualify for ISO
- Category:Nonexistent E17 links (0) – setting [iso3=none] and [ref=e17] generates an invalid reference
Category:Language articles without language codes (211) – no language code listed, but not specifically excluded from ISO with [iso3=none]
- Category:Languages without ISO 639-3 code but with Linguist List code (163)
  - subcat Category:Dialects with Linguist List code (60) – LingList codes some dialects with sub-ISO codes as "xxx-yyy"
- Category:Languages without ISO 639-3 code but with Linguasphere code (165)
- Category:Languages without ISO 639-3 code but with AIATSIS code (51)
- Category:Languages without ISO 639-3 code but with Guthrie code (57)
- Category:Dialects of languages with ISO 639-3 code (844) – a normal exception, triggered by isoexception=dialect
- Category:Historical forms of languages with ISO codes (53) – a normal exception, triggered by isoexception=historical
- Category:Protolanguages without ISO codes (0) – a normal exception, triggered by isoexception=protolanguage
Category:Languages which need ISO 639-3 comment (73) – triggered by [lc1=] without [lc2=] (once used as a way to provide comments; occasionally still appropriate with [iso3=] when a second but redundant ISO code is included)
Category:Languages with ISO 639-2 code (500) – sometimes the 639-3 code is mistakenly copied into the iso2 field
Category:Languages with ISO 639-1 code (247)

Speaker and date issues

Category:Language articles without speaker estimate (620) – no entry under [speakers=], and not extinct, a sign language, or a conlang
Category:Language articles with invalid population dates (5) – entry error at [date=] (anything other than a 4-digit number at start)
Category:Language articles with speaker number undated (156) – no entry at [date=]
- Category:Language articles with 'no date' set (166) – [date=no date], used when the source lacks a date
- Category:Language articles with NA population dates (5) – [date=NA], used when a date does not apply
Category:Language articles with old speaker data (420) – currently set to > 25 years
Category:Language articles without reference field (260)

Classification

Category:Language articles with spurious family (0) – generally because [fam1=] is autofilled from [familycolor] to 'American', 'Australian', 'Papuan', 'Khoisan', 'Caucasian', 'Andamanese', or 'Paleosiberian'
Category:Languages without family color codes (1) – no or invalid familycolor
Category:Languages without classification (0) – family displayed as 'unknown' (sometimes triggered by SLs or conlangs)

Other

Category:Language articles needing infoboxes (25) – manual cat: switch off (to "no") if you judge the article does not need one
Category:Ill-formatted infobox-language images (54) – images need to be stripped of external file formatting
Category:Language articles with unsupported infobox fields (63) – detects any parameter not in the list, incl. for now anything over dia20
Category:Articles citing AIATSIS (38)
Category:Articles citing INALI (11)
Category:Articles citing Linguist List (31)
Category:Articles citing Maho/Guthrie (0) – category exists in template but has not been created
Category:Articles citing Nationalencyklopedin (11)
Category:Articles opting out of population reference (1)
Category:Articles with unnamed Glottolog code (233)
Category:Dialect articles with speakers set to 'unknown' (239)
Category:Extinct ISO language articles citing sources other than Ethnologue (101)
Category:ISO language articles citing sources other than Ethnologue (1,020)
Category:Language articles missing Glottolog code (472)
Category:Language articles with IETF language tag (410)
Category:Language articles with old Ethnologue 18 speaker data (1,140)
Category:Language articles with speakers set to 'none' (37)
Category:Language articles with speakers set to 'unknown' (253)
Category:Language articles with unknown extinction date (225)
Category:Language articles with unknown population not citing Ethnologue 18 (50)
Category:Language articles with unreferenced extinction date (736)
Category:Languages rejected by Glottolog (15)
Category:Languages with neither ISO nor Glottolog code (356)
Category:Languages without Glottolog code (853)
Category:Languages without ISO 639-3 code but with Glottolog code (550)
Category:Nonexistent E18 links (0)

Sub-templates

TemplateData

TemplateData documentation used by VisualEditor and other tools

See a monthly parameter usage report for Template:Infobox language in articles based on its TemplateData.

TemplateData for Infobox language

Display data about a language in a standard format

Template parameters
This template has custom formatting.
Parameter		Description	Type	Status
Name	`name`	The English name of the language	String	required
Alternative name	`altname`	An alternative or additional English name of the language	String	optional
Native name	`nativename`	The native name of the language	String	optional
Acceptance	`acceptance`	The acceptance of the language among linguists	String	optional
Pronunciation	`pronunciation`	The IPA pronunciation of the native name of the language	String	optional
States	`states` `state`	States or countries in which the language is mainly spoken	String	optional
Region	`region`	The geographic region(s) in which the language is mainly spoken	String	optional
Ethnicity	`ethnicity`	The ethnic group(s) whose native language this is	String	optional
Speakers	`speakers`	The number of native speakers/signers of the language (will be rounded to 2 significant figures)	Number	optional
Extinction	`extinct`	The date of the language's extinction or other information about extinction	String	optional
Revival	`revived`	Date and/or population of attempted revival of extinct language	String	optional
revived-category	`revived-category`	optional name of appropriate subcategory of [[:Category:Language revival]] (which is used by default if {{para\|revived}} has a value); or <code>nocat</code> to suppress categorization	String	optional
Era	`era`	The era of a historical language's use	String	optional
Date	`date`	The date of the stated estimate of the number of speakers, starting with a 4-digit year	String	optional
Date prefix	`dateprefix`	Additional information about the date of estimation of the number of speakers, placed in parentheses before the date	String	optional
Reference	`ref`	A reference for the number of speakers, placed after the date, if any. This can be any inline citation or a predefined code such as e19, linglist, ne2010, etc. For more details, see the documentation at Template:Infobox language/ref.	String	optional
Reference name	`refname`	Name used in reference generated by certain 'ref' parameter values such as e19. It defaults to the value of the 'name' parameter or PAGENAME.	String	optional
Speakers 2	`speakers2`	A second line giving more information about the number of speakers, such as a second estimate	String	optional
Label for the 'speakers' field	`speakers_label`	A label which can overwrite the 'Native speakers' label	String	optional
Language Family Color	`familycolor`	The appropriate language family for the purposes of determining the background color, chosen from a fixed set given in the documentation	String	required
Language Family	`fam1`	The broadest accepted language family the language belongs to	String	optional
Language Family 2	`fam2`	A more specific sub-language family that the language belongs to	String	optional
Language Family 3	`fam3`	A more specific sub-language family that the language belongs to	String	optional
Language Family 4	`fam4`	A more specific sub-language family that the language belongs to	String	optional
Language Family 5	`fam5`	A more specific sub-language family that the language belongs to	String	optional
Language Family 6	`fam6`	A more specific sub-language family that the language belongs to	String	optional
Language Family 7	`fam7`	A more specific sub-language family that the language belongs to	String	optional
Language Family 8	`fam8`	A more specific sub-language family that the language belongs to	String	optional
Language Family 9	`fam9`	A more specific sub-language family that the language belongs to	String	optional
Language Family 10	`fam10`	A more specific sub-language family that the language belongs to	String	optional
Language Family 11	`fam11`	A more specific sub-language family that the language belongs to	String	optional
Language Family 12	`fam12`	A more specific sub-language family that the language belongs to	String	optional
Language Family 13	`fam13`	A more specific sub-language family that the language belongs to	String	optional
Language Family 14	`fam14`	A more specific sub-language family that the language belongs to	String	optional
Language Family 15	`fam15`	A more specific sub-language family that the language belongs to	String	optional
Family	`family`	Overrides all other family parameters, displays whatever you want	String	optional
Ancestor	`ancestor`	An ancestral or reconstructed form of the language	String	optional
Ancestor 2	`ancestor2`	An ancestral or reconstructed form of the language	String	optional
Ancestor 3	`ancestor3`	An ancestral or reconstructed form of the language	String	optional
Creator	`creator`	For constructed languages, the name of the creator	String	optional
Creation date	`created`	Creation date for constructed languages	String	optional
Setting	`setting`	The fictional setting or other usage of a constructed language	String	optional
Posteriori	`posteriori`	Natural languages used as sources for a constructed language	String	optional
Dialect	`dia1`	A primary dialect of the language	String	optional
Dialect 2	`dia2`	Another primary dialect of the language	String	optional
Dialect 3	`dia3`	Another primary dialect of the language	String	optional
Dialect 4	`dia4`	Another primary dialect of the language	String	optional
Dialect 5	`dia5`	Another primary dialect of the language	String	optional
Dialect 6	`dia6`	Another primary dialect of the language	String	optional
Dialect 7	`dia7`	Another primary dialect of the language	String	optional
Dialect 8	`dia8`	Another primary dialect of the language	String	optional
Dialect 9	`dia9`	Another primary dialect of the language	String	optional
Dialect 10	`dia10`	Another primary dialect of the language	String	optional
Dialect 11	`dia11`	Another primary dialect of the language	String	optional
Dialect 12	`dia12`	Another primary dialect of the language	String	optional
Dialect 13	`dia13`	Another primary dialect of the language	String	optional
Dialect 14	`dia14`	Another primary dialect of the language	String	optional
Dialect 15	`dia15`	Another primary dialect of the language	String	optional
Dialect 16	`dia16`	Another primary dialect of the language	String	optional
Dialect 17	`dia17`	Another primary dialect of the language	String	optional
Dialect 18	`dia18`	Another primary dialect of the language	String	optional
Dialect 19	`dia19`	Another primary dialect of the language	String	optional
Dialect 20	`dia20`	Another primary dialect of the language	String	optional
Dialects	`dialects`	Overrides all other dialect parameters, just displays the argument	String	optional
Standardized Register	`stand1`	A standardized register of the language	String	optional
Standardized Register 2	`stand2`	Another standardized register of the language	String	optional
Standardized Register 3	`stand3`	Another standardized register of the language	String	optional
Standardized Register 4	`stand4`	Another standardized register of the language	String	optional
Standardized Register 5	`stand5`	Another standardized register of the language	String	optional
Standardized Register 6	`stand6`	Another standardized register of the language	String	optional
Standardized Registers	`standards`	Overrides all other standardized register parameters, displays the argument	String	optional
Script	`script`	The writing system(s) that literate speakers use for the language	String	optional
Nations	`nation`	A list of countries in which it is an official language	String	optional
Minority Status	`minority`	A list of countries in which it is a recognized minority language	String	optional
Agency	`agency`	The regulatory body or language academy for the language	String	optional
ISO 639-1	`iso1`	The ISO 639-1 code for the language	String	optional
ISO 639-1 Comment	`iso1comment`	Any comments about the ISO 639-1 code, so as not to interfere with the link	String	optional
ISO 639-2	`iso2`	The ISO 639-2 code for the language (but not the language family)	String	optional
ISO 639-2 Bibliographic	`iso2b`	The ISO 639-2 bibliographic code for the language	String	optional
ISO 639-2 Terminological	`iso2t`	The ISO 639-2 terminological code for the language	String	optional
ISO 639-2 Comment	`iso2comment`	Any comments about the ISO 639-2 code(s), so as not to interfere with the link(s)	String	optional
ISO 639-3	`iso3`	The ISO 639-3 code for the language, can be 'none' or 'linglist'	String	optional
ISO 639-3 Comment	`iso3comment`	Any comments about the ISO 639-3 code, so as not to interfere with the link	String	optional
ISO Exception	`isoexception`	Used for cleanup categories, excludes from the general 'missing language code' category if set to 'dialect', 'historical', 'protolanguage', or 'talkpage'	String	optional
Dialect ISO 639	`lc1`	The ISO 639 code of the first dialect	String	optional
Dialect Name	`ld1`	The name of the first dialect	String	optional
Dialect ISO 639 2	`lc2`	The ISO 639 code of another dialect	String	optional
Dialect Name 2	`ld2`	The name of another dialect	String	optional
Dialect ISO 639 3	`lc3`	The ISO 639 code of another dialect	String	optional
Dialect Name 3	`ld3`	The name of another dialect	String	optional
Dialect ISO 639 4	`lc4`	The ISO 639 code of another dialect	String	optional
Dialect Name 4	`ld4`	The name of another dialect	String	optional
Dialect ISO 639 5	`lc5`	The ISO 639 code of another dialect	String	optional
Dialect Name 5	`ld5`	The name of another dialect	String	optional
Dialect ISO 639 6	`lc6`	The ISO 639 code of another dialect	String	optional
Dialect Name 6	`ld6`	The name of another dialect	String	optional
Dialect ISO 639 7	`lc7`	The ISO 639 code of another dialect	String	optional
Dialect Name 7	`ld7`	The name of another dialect	String	optional
Dialect ISO 639 8	`lc8`	The ISO 639 code of another dialect	String	optional
Dialect Name 8	`ld8`	The name of another dialect	String	optional
Dialect ISO 639 9	`lc9`	The ISO 639 code of another dialect	String	optional
Dialect Name 9	`ld9`	The name of another dialect	String	optional
Dialect ISO 639 10	`lc10`	The ISO 639 code of another dialect	String	optional
Dialect Name 10	`ld10`	The name of another dialect	String	optional
Dialect ISO 639 11	`lc11`	The ISO 639 code of another dialect	String	optional
Dialect Name 11	`ld11`	The name of another dialect	String	optional
Dialect ISO 639 12	`lc12`	The ISO 639 code of another dialect	String	optional
Dialect Name 12	`ld12`	The name of another dialect	String	optional
Dialect ISO 639 13	`lc13`	The ISO 639 code of another dialect	String	optional
Dialect Name 13	`ld13`	The name of another dialect	String	optional
Dialect ISO 639 14	`lc14`	The ISO 639 code of another dialect	String	optional
Dialect Name 14	`ld14`	The name of another dialect	String	optional
Dialect ISO 639 15	`lc15`	The ISO 639 code of another dialect	String	optional
Dialect Name 15	`ld15`	The name of another dialect	String	optional
Dialect ISO 639 16	`lc16`	The ISO 639 code of another dialect	String	optional
Dialect Name 16	`ld16`	The name of another dialect	String	optional
Dialect ISO 639 17	`lc17`	The ISO 639 code of another dialect	String	optional
Dialect Name 17	`ld17`	The name of another dialect	String	optional
Dialect ISO 639 18	`lc18`	The ISO 639 code of another dialect	String	optional
Dialect Name 18	`ld18`	The name of another dialect	String	optional
Dialect ISO 639 19	`lc19`	The ISO 639 code of another dialect	String	optional
Dialect Name 19	`ld19`	The name of another dialect	String	optional
Dialect ISO 639 20	`lc20`	The ISO 639 code of another dialect	String	optional
Dialect Name 20	`ld20`	The name of another dialect	String	optional
Dialect ISO 639 21	`lc21`	The ISO 639 code of another dialect	String	optional
Dialect Name 21	`ld21`	The name of another dialect	String	optional
Dialect ISO 639 22	`lc22`	The ISO 639 code of another dialect	String	optional
Dialect Name 22	`ld22`	The name of another dialect	String	optional
Dialect ISO 639 23	`lc23`	The ISO 639 code of another dialect	String	optional
Dialect Name 23	`ld23`	The name of another dialect	String	optional
Dialect ISO 639 24	`lc24`	The ISO 639 code of another dialect	String	optional
Dialect Name 24	`ld24`	The name of another dialect	String	optional
Dialect ISO 639 25	`lc25`	The ISO 639 code of another dialect	String	optional
Dialect Name 25	`ld25`	The name of another dialect	String	optional
Dialect ISO 639 26	`lc26`	The ISO 639 code of another dialect	String	optional
Dialect Name 26	`ld26`	The name of another dialect	String	optional
Dialect ISO 639 27	`lc27`	The ISO 639 code of another dialect	String	optional
Dialect Name 27	`ld27`	The name of another dialect	String	optional
Dialect ISO 639 28	`lc28`	The ISO 639 code of another dialect	String	optional
Dialect Name 28	`ld28`	The name of another dialect	String	optional
Dialect ISO 639 29	`lc29`	The ISO 639 code of another dialect	String	optional
Dialect Name 29	`ld29`	The name of another dialect	String	optional
Dialect ISO 639 30	`lc30`	The ISO 639 code of another dialect	String	optional
Dialect Name 30	`ld30`	The name of another dialect	String	optional
ISO 639-6	`iso6`	The ISO 639-6 code for the language	String	optional
Glottolog	`glotto`	The Glottolog code for the language	String	optional
Glottolog name	`glottoname`	The name to be used in the Glottolog reference (can be cross-ref'd as name=Glottolog etc.) Example Romance	String	suggested
Glottolog reference name	`glottorefname`	The reference used by Glottolog Example Indo-European	String	suggested
Glottolog code 2	`glotto2`	A Glottolog code for a branch of the language family. Example sout3147	String	optional
Glottolog name 2	`glottoname2`	The name to be used in the 2nd Glottolog reference	String	optional
Glottolog reference name 2	`glottorefname2`	The second reference used by Glottolog Example Indo-European	String	optional
Glottolog code 3	`glotto3`	A Glottolog code for a branch of the language family. Example bwil1246	String	optional
Glottolog name 3	`glottoname3`	The name to be used in the third Glottolog reference	String	optional
Glottolog reference name 3	`glottorefname3`	The third reference used by Glottolog Example Indo-European	String	optional
Glottolog code 4	`glotto4`	A Glottolog code for a branch of the language family. Example bota1239	String	optional
Glottolog name 4	`glottoname4`	The name to be used in the fourth Glottolog reference	String	optional
Glottolog reference name 4	`glottorefname4`	The fourth reference used by Glottolog Example Indo-European	String	optional
Glottolog code 5	`glotto5`	A Glottolog code for a branch of the language family. Example sabi1248	String	optional
Glottolog name 5	`glottoname5`	The name to be used in the fifth Glottolog reference	String	optional
Glottolog reference name 5	`glottorefname5`	The fifth reference used by Glottolog Example Indo-European	String	optional
Linguist List	`linglist`	The Linguist List ISO 639-3 private or local code or other substitute, range qaa-qtz or numerals only	String	optional
Linguist List Comment	`lingname`	Any comments on the Linguist List code	String	optional
Linguist List 2	`linglist2`	An additional Linguist List code	String	optional
Linguist List Comment 2	`lingname2`	An additional comment on the Linguist List code	String	optional
Linguist List 3	`linglist3`	An additional Linguist List code	String	optional
Linguist List Comment 3	`lingname3`	An additional comment on the Linguist List code	String	optional
Linguasphere	`lingua`	The Linguasphere code for the language	String	optional
Guthrie	`guthrie`	The Guthrie code for Bantu languages	String	optional
AIATSIS	`aiatsis`	The AIATSIS code for Australian languages	String	optional
AIATSIS Comment	`aiatsisname`	Any comments on the AIATSIS code	String	optional
AIATSIS 2	`aiatsis2`	An additional AIATSIS code	String	optional
AIATSIS Comment 2	`aiatsisname2`	An additional comment on the AIATSIS code	String	optional
AIATSIS 3	`aiatsis3`	An additional AIATSIS code	String	optional
AIATSIS Comment 3	`aiatsisname3`	An additional comment on the AIATSIS code	String	optional
AIATSIS 4	`aiatsis4`	An additional AIATSIS code	String	optional
AIATSIS Comment 4	`aiatsisname4`	An additional comment on the AIATSIS code	String	optional
AIATSIS 5	`aiatsis5`	An additional AIATSIS code	String	optional
AIATSIS Comment 5	`aiatsisname5`	An additional comment on the AIATSIS code	String	optional
AIATSIS 6	`aiatsis6`	An additional AIATSIS code	String	optional
AIATSIS Comment 6	`aiatsisname6`	An additional comment on the AIATSIS code	String	optional
IETF	`ietf`	IETF language tag	String	optional
ELP	`ELP`	The Endangered Languages Project code for the language	String	optional
Image	`image`	The image to display at the top of the infobox, in the format 'image name.png' without 'File:' or brackets	String	optional
Image Size	`imagesize`	Overrides the default image size, using units of 'px' or 'em'	String	optional
Image Alt Text	`imagealt`	The alt (hover) text for the image	String	optional
Image Caption	`imagecaption`	A caption to display under the image	String	optional
Image Header	`imageheader`	A brief header for the image to display in the left hand column	String	optional
Map	`map`	The image to display at the bottom of the infobox, in the format 'image name.png' without 'File:' or brackets	String	optional
Map Size	`mapsize`	Overrides the default image size for the map, using units of 'px' or 'em'	String	optional
Map Alt Text	`mapalt`	The alt (hover) text for the map	String	optional
Map Caption	`mapcaption`	A caption to display under the map	String	optional
Map 2	`map2`	A second map to display at the bottom of the infobox, in the format 'image name.png' without 'File:' or brackets	String	optional
Map Alt Text 2	`mapalt2`	The alt (hover) text the second map	String	optional
Map Caption 2	`mapcaption2`	A caption to display under both maps	String	optional
Pushpin map	`pushpin_map`	The name of a location map (e.g. 'Indonesia' or 'Russia'). The coordinates information (from the coordinates parameter) position a pushpin coordinate marker and label on the map 'automatically'. Example see: Padang, Indonesia Example Indonesia	String	optional
Pushpin image	`pushpin_image`	Image to use for the pushpin map	File	optional
Pushpin map size	`pushpin_mapsize`	Must be entered as only a number—do not use px. The default value is 250. Example 200	Number	optional
Pushpin map alt text	`pushpin_map_alt`	Alt (hover) text for the pushpin map	String	optional
Pushpin map caption	`pushpin_map_caption`	Fill out if a different caption from ''map_caption'' is desired. Example Map showing the location of Biak language in Indonesia	String	optional
Pushpin label	`pushpin_label`	Label of the pushpin	Line	optional
Pushpin label position	`pushpin_label_position`	The position of the label on the pushpin map relative to the pushpin coordinate marker. Valid options are {left, right, top, bottom, none}. If this field is not specified, the default value is ''right''. Default right Example left	String	optional
Coordinates	`coordinates`	Latitude and longitude. Use {{Coord}}. See the documentation for {{Coord}} for more details on usage. Example {{coord\|41\|50\|15\|N\|87\|40\|55\|W}}	Template	optional
Infobox Size	`boxsize`	Overrides the default width of the infobox, using units of 'px' or 'em' (it automatically expands to fit images wider than the default width)	String	optional
IPA Notice	`notice`	Set to 'IPA' or 'ipa' to display a notice that the article contains special IPA phonetic symbols	String	optional
Signed form	`sign`	The name of the sign language used for this language Example Signed Arabic (national forms)	String	optional
Protolanguage name	`protoname`	Name of the proto-language of the language Example [[Proto-Arabic language]]	Line	optional

Move

the current Template:Infobox Language is a private version of User:Netoholic and should be moved to his user space or to Template:Infobox Language new. He has no right to abuse the standard name to (in the long run) delete the history of the original template.

If needed a bot can change all article references from Language to Language Infobox. As Commander Kean told me, asking at Wikipedia:Bot requests gives fast help in general. Netoholic pointed out no bot should be used to do this, because a redirect is sufficient. But this is a different matter. This voting is only about having the true language infobox at Template:Infobox Language. Tobias Conradi (Talk) 23:29, 5 January 2006 (UTC)[reply]

support - standard name for infobox Tobias Conradi (Talk) 23:29, 5 January 2006 (UTC)[reply]

result

not moved - please take destination template to WP:TfD if you wish to so, thanks WhiteNight ^{T | @ | C} 09:10, 11 January 2006 (UTC)[reply]

I don't think it should be deleted. Tobias Conradi (Talk) 21:14, 11 January 2006 (UTC)[reply]

moved to {{{Infobox Language}}} Tobias Conradi (Talk) 05:59, 7 February 2006 (UTC)[reply]

Discussion

Archives
January 2005 — November 2005 November 2005 — December 2005

Template:Infobox Language

Netoholic has created this template as a version that avoids conflict with WP:AUM. However, he has done this with no discussion, and I am not happy with the result. I am posting this here so that those who use this template might be aware of what he's doing. --Gareth Hughes 18:40, 31 December 2005 (UTC)[reply]

I warned users on this page (#Wikipedia:Avoid_using_meta-templates) weeks ago, and noone was forthcoming. I am beginning to convert the "simpler" language articles into this new infobox. I have started with a pilot group of a few articles, but everytime I try and make progress, Garzo rollbacks my edits. Garzo's displeasure is irrelevant, because WP:AUM trumps anything else that this template has been hacked into doing. I'm not sure how much functionality can be packed into the non-meta-template version, but if even half can be converted quickly, that is an improvement. -- Netoholic @ 08:59, 1 January 2006 (UTC)[reply]

Garzo! Thanks for informing us! What Netoholic is doing is realy bad. He warned us, lol. You have my full support of reverts. Furthermore I am not even sure if WP:AUM really applies here, I raised the question on a different issue [3] (a template that's not edited because it is protected) but nobody could tell a reference in WP:AUM that's states how this could harm the servers. So if our subtemplates are stable soon, they may get protected. Tobias Conradi (Talk) 16:06, 1 January 2006 (UTC)[reply]

No one can deny that meta-templates (templates that have other templates in them) are harmful to the servers. It's documented in Wikipedia:Avoid using meta-templates. The sooner the non-meta Infobox Language can be fully implemented the better.--Commander Keane 18:07, 1 January 2006 (UTC)[reply]

Why this arrogance and agressive wording? (no one can deny - arrogance because you don't seem to have read my previous posting, aggressive because you speak of 'no one can deny' - as if we others are idiots.) From WP:AUM _I_ could NOT learn that meta-templates are harmful to the servers. EDITING meta-templates is harmful. The non-meta Infobox is quite bad design as of now. Why could Netoholic not implement his "improvements" in the language template and by doing so keep the history ... of Garzo's and other peoples great work? and go with the other editors. Why did he need to work where is work could not be seen and switch the templates without informing here? Tobias Conradi (Talk) 07:19, 2 January 2006 (UTC)[reply]

Wikipedia:Request_for_Arbitration#User:Netoholic Tobias Conradi (Talk) 07:35, 2 January 2006 (UTC)[reply]

(Tobias got the following on his talk) bad form: Dude, poisoning the well is a shitty tactic. Please remove this comment, since it's only put there to take a cheap shot at me. -- Netoholic @ 17:49, 2 January 2006 (UTC)[reply]
Thanks for the link to "poisoning the well". I didn't want to descredit you here with the RfA. So I am sorry if this impression was left. I thought it might be related. Especially after you defended your reverts with the words that you warned users (and now have some right of replacing?) and that "Garzo rolls back your progresses".
Please come here and try to present some ideas. I think we are all quite open to reduce the serverload. AFAIK there are more than 7000 ISO 639-3 language codes, so the effect of this template may be huge if we have it on 7000 pages one day. Tobias Conradi (Talk) 20:51, 3 January 2006 (UTC)[reply]