stux wrote:

This makes sense, since I've run into several improperly used template, but doing so will likely break other templates where users may have (inappropriately) taken advantage of case sensitivity:

{{template|par1=val1|PAR1=val2...}}

I think parameter case sensitivity should be treated as a "template standard" and so template "programmers" (i.e. users) should be informed of this issue (i.e. the information widely disseminated through as many channels as possible).

ayg wrote:

This might or might not have been a good idea to start with, but by now there's way too much legacy content. Also, case-sensitivity of template parameters matches case-sensitivity of the template names themselves. Given the relatively marginal benefit of allowing case-insensitive parameters to begin with (is it really hard to always use lowercase?), I would suggest WONTFIX.

I was considering doing this, but with a config variable to enable it (disabled by default), but if people think that's excessive, I'm not especially attached to the idea.

ayg wrote:

I don't think a config option would be useful here. It would potentially break copying content between wikis, e.g., Wikipedia.

(In reply to comment #4)

I don't think a config option would be useful here. It would potentially break
copying content between wikis, e.g., Wikipedia.

I agree completely. This should either be fixed or not fixed, introducing a variable here would just create incompatibilities between wikis and make Import/Export unreliable.

(In reply to comment #2)

This might or might not have been a good idea to start with, but by now there's
way too much legacy content. Also, case-sensitivity of template parameters
matches case-sensitivity of the template names themselves. Given the
relatively marginal benefit of allowing case-insensitive parameters to begin
with (is it really hard to always use lowercase?), I would suggest WONTFIX.

I'm inclined to agree here. This seems like it would've been a great idea when it was being designed, but it's too late now.

In T6964#3897917, @Iniquity wrote:

I think we need to discuss this anew.

Why?

It cannot really be my decision, but I'd decline it.

Evidently, this has been requested for many years, and people are still asking for it. However, it seems to me that the problems that such a change in templates syntax after so many years outweigh the possible benefits.

The problems currently caused by case-sensitivity of templates are minor in any case. A better way to address them is to write good TemplateData. This will help people use less manual and error-prone source editing and more visual editing, and it will also help wikis implement linting tools, such as https://he.wikipedia.org/wiki/Module:ParamValidator in the Hebrew Wikipedia.

Removing good first task project since this is evidently not "non-controversial", as required by bullet point 2 in the description.