Contents

Voting on: When any template has its behavior affected by a parameter that specifies a language, requiring this parameter to be the language code, never the language name.

Note:

The outcome of this vote will affect the templates that may be used for two or more languages individually: that is, {{term}}, {{infl}}, {{alternative spelling of}}, among various others. Some of them employ the parameter lang= to specify only one language, by their code or name, as in the following examples. Or, alternatively, they employ only the language code, not recognizing languages by their names.

Support Language names can change. On my memory {{os}} became 'Ossetian' from 'Ossetic'. I may one day change {{xcl}} to 'Classical Armenian' from 'Old Armenian'. Moreover, theoretically we may want to change {{el}} to 'Modern Greek', etc. --Vahag 18:20, 25 October 2010 (UTC)

Semi-weak support. These template changes would be reasonable and practical, but the real strength comes in consistency, not having to remember which is used for a particular template, certainly a bigger problem for foreign language editors than for those like me. I'm just not sure where in policy this should be coded, or how strongly. DAVilla 09:38, 27 October 2010 (UTC)

Oppose. I don't completely understand what we're voting on, but I'm pretty sure I don't agree with it, or at least, that I don't agree with it being a blanket policy. —RuakhTALK 17:49, 18 October 2010 (UTC)

OpposeǷidsiþ 15:37, 19 October 2010 (UTC) Ideally, you should be able to use either. Ƿidsiþ 15:37, 19 October 2010 (UTC)

Oppose I like consistency, but using the language name would be much easier for editors (and technically possibly). --Bequw→τ 20:45, 23 October 2010 (UTC)

OpposeMglovesfun (talk) 18:39, 25 October 2010 (UTC), per Ruakh. This vote isn't in a state where I can support it (see the talk page). Mglovesfun (talk) 18:39, 25 October 2010 (UTC)

Oppose – while consistency is good, requiring ISO codes add a barrier for new editors. I’d support a bot to change it (makes code more legible, ensuring consistent naming, and allowing name changing in future) and to flag misspellings, but it’s technically feasible to support language names (not just codes), so we should do so. —Nils von Barth (nbarth) (talk) 19:07, 8 November 2010 (UTC)

AbstainDan Polansky 07:53, 31 October 2010 (UTC) I was originally in favor of the proposal to forbid language names in template parameters (so only language codes could be used), but I have grown indecisive about it. I can no longer confirm that {{ttbc|French}} as compared {{ttbc|fr}} harms anything: this particular template sits nicely along with the non-templated "French" in translation tables. I would more readily support if this only concerned "lang=" parameters, that is those templates that have language as a named parameter. --Dan Polansky 07:53, 31 October 2010 (UTC)

Abstain It would effectively get rid of the xs= parameter {{t}} has. This causes problems for water. -- Prince Kassad 00:24, 6 November 2010 (UTC)