Hello, you have come here looking for the meaning of the word Template talk:cap. In DICTIOUS you will not only get to know all the dictionary meanings for the word Template talk:cap, but we will also tell you about its etymology, its characteristics and you will know how to say Template talk:cap in singular and plural. Everything you need to know about the word Template talk:cap you have here. The definition of the word Template talk:cap will help you to be more precise and correct when speaking or writing your texts. Knowing the definition ofTemplate talk:cap, as well as those of other words, enriches your vocabulary and provides you with more and better linguistic resources.
Hardly used. Where it is used it appears to be a hard to spot typo for {{l}}. If someone is actively using this for its intended purpose (substing) it should be moved to a better name. DTLHS (talk) 21:04, 21 December 2018 (UTC)Reply
Rename as suggested by -sche. Personally I’m not sure it saves much time, but the Grease Pit discussion suggests some editors would find it useful. — SGconlaw (talk) 02:37, 23 December 2018 (UTC)Reply
How can you tell, DTLHS, that it's "hardly used", when its documentation says it must be substed? Keep the useful template; note that the GP discussion linked above actually shows an editor seeking just this template! so it obviously is useful. That said, I wouldn't object to a change in name ({{subst:cap}}, I guess) if this one is confusing, so long as the deletion summary indicates the new name so people looking for it at the old page can find it.—msh210℠ (talk) 20:33, 28 May 2019 (UTC)Reply
It is obviously "hardly used" because it has a stupid name that nobody even knew existed as evidenced by the GP discussion. DTLHS (talk) 21:15, 28 May 2019 (UTC)Reply
Note this is {{1}} - not to be confused with {{l}}. This is a link template that capitalises the first letter. This has issues, however:
It assumes English by default if you don't enter a language code. This makes it highly prone to error.
It makes it easy for inexperienced users to use capitalisation in places where they shouldn't, such as in lists. For example, "Hellur" in this recent version of the page hello.
According to the documentation, it "must" always be substituted. This is very clearly not how it's been used, as it's currently transcluded over 500 times (and possibly many, many more). When this is combined with the fact that no langcode is required, it makes the template totally nonstandard (and therefore prone to error if bots happen across it).
I suggest we just get rid of it, as it's an obvious source of problems. If we keep it, then at the very least we should mandate a langcode and force substitution. Theknightwho (talk) 00:36, 17 February 2023 (UTC)Reply
Delete: wow, you’ve got to be super lazy to need this template. Plus, the instructions are rather involved; I can’t imagine an inexperienced editor bothering to read them. — Sgconlaw (talk) 12:21, 17 February 2023 (UTC)Reply
Keep. It's meant for definitions in English entries where we usually capitalise the first letter of the first word of the definition while linking to its entry which is on its non-capitalised spelling (unless it is a proper noun, etc. always beginning with a capital letter). This is its most common (if not only) usage in mainspace entries. The documentation can be updated to clearly instruct inexperienced users regarding its usage to avoid them using it where they shouldn't and the "must be substituted" part can be removed according to current practices. --Svartava (talk) 05:50, 18 February 2023 (UTC)Reply
@Sgconlaw: Yeah, I think it is totally fine to use it without substitution (as done mostly presently). It's a simple template anyway, and makes it quite convenient to capitalise the first letter without having to re-type the whole word. --Svartava (talk) 12:17, 18 February 2023 (UTC)Reply
I agree with @Sgconlaw - it adds needless confusion. We should be cutting down on the number of templates when they aren't actually needed. Plus, there are other disadvantages I've already listed, too. Theknightwho (talk) 12:25, 26 February 2023 (UTC)Reply
The name of this template is poor; it doesn't seem to refer to anything in particular and it's too easily confused with the {{{1}}} syntax for template parameters. Let's at least move the template to an alphabetical title. Maybe {{M}} or {{j}} for Majuscule?
There is no need for a language code in this template. It is intended to be used in glosses, which are written in English. The lang= parameter doesn't appear to be in use in any entries (other than IFA); let's just remove it to avoid confusion.
Keep, but I would suggest renaming it and perhaps removing the language code for the reasons This, that and the other mentions, especially given that 1 and l look particularly similar in the default font for the script editor. I would add a couple of points: small pieces of "laziness" can add up to significant time-saving in the context of anything that requires a large number of manual edits, and I don't personally see the reason for forcing substitution since it adds a fair number of keystrokes for not much benefit. —Al-Muqanna المقنع (talk) 13:36, 24 February 2023 (UTC)Reply
On one hand, it's useful to have a template that does this, and it even makes a decent amount of sense for it to expect itself to be used only in English sections since those are the main place we need to capitalize an initial link, since English definitions are typically capitalized, where other languages just have glosses. On the other hand, the name is poor and opaque, as I admitted in the last RFD (Template talk:1). But if we rename to something long, it reduces the advantage of this template, that it's easier than typing the whole headword again ({{l|en|uranium hexafluoride|Uranium hexafluoride}}). Meh. IMO keep but maybe rename (I suggested {{capitalize}} with a redirect from {{cap}} last time), and I have no objection to removing the language code so that it just functions like ]. - -sche(discuss)21:19, 2 March 2023 (UTC)Reply
Keep. I wasn't aware of its existence, but would like to use it when inserting long vernacular names of organisms at the beginning of definition sentences. I'd much rather not have to subst because of the extra keystrokes. I suppose we could instead just have a bot capitalize the first word of every definition in English L2s periodically. DCDuring (talk) 23:11, 2 March 2023 (UTC)Reply
Ooh, I forgot about this template. Thanks for reminding me. I'm gonna use it again :). This is a keep, of course. All the points made by Theknightwho are unconvincing arguments. It assumes English by default if you don't enter a language code. This makes it highly prone to error (WTF?) It makes it easy for inexperienced users to use capitalisation in places where they shouldn't, such as in lists - inexperienced users wouldn't even know it exists. Van Man Fan (talk) 23:35, 8 March 2023 (UTC)Reply
Renamed to {{cap}} and changed so that if no lang code is given, you get a bare piped link instead of linking to English through {{l}}. {{1}} is kept as a deprecated alias. Benwing2 (talk) 10:41, 2 March 2024 (UTC)Reply
Support "cap", but I believe credit goes to -sche for the idea (see Template talk:1). Ultimateria (talk) 04:21, 18 January 2024 (UTC)