Hello, you have come here looking for the meaning of the word Template talk:label. In DICTIOUS you will not only get to know all the dictionary meanings for the word Template talk:label, but we will also tell you about its etymology, its characteristics and you will know how to say Template talk:label in singular and plural. Everything you need to know about the word Template talk:label you have here. The definition of the word Template talk:label will help you to be more precise and correct when speaking or writing your texts. Knowing the definition ofTemplate talk:label, as well as those of other words, enriches your vocabulary and provides you with more and better linguistic resources.
Deletion debate
Note:The following refers to a previous, unrelated template that used the same name as this one.
Latest comment: 14 years ago3 comments2 people in discussion
It's unused. The template uses CSS try swap one type of content for another. This causes problems for some views (browsers, gateways, and applications). See related BP discussion. We should be able to use links or hover-text to get our message across. Note there's a related declaration in Mediawiki:Common.css. --Bequw→τ17:50, 25 July 2010 (UTC)Reply
For your information, the other on-line dictionaries (, ...) publish them, and as a native French speaker I can assure that it's fundamental at least in my language. JackPotte (talk) 21:29, 29 July 2013 (UTC)Reply
That debate was about French specifically, but changing the categories in this module would change it for every language on Wiktionary. It was also 5 years ago, so that can hardly be assumed to be current consensus. That's why I said, it's assuming we actually want all of those categories. Also, it appears that not all the verbs in the category are actually reflexive, only some of them are. Why is that? —CodeCat21:43, 29 July 2013 (UTC)Reply
Exactly. The practice is very different for some other languages. For Dutch for example, the label is treated as a sense-level context label (like it should!) and a verb can have reflexive and non-reflexive senses. So if you added a category to the labels, then none of the verbs in "Dutch reflexive verbs" would actually be reflexive. They would only have one or more reflexive senses. —CodeCat22:03, 29 July 2013 (UTC)Reply
Latest comment: 11 years ago2 comments2 people in discussion
Are they possible, or we are supposed to have language-specific context labels (like uds. for Spanish)? I'd like to have e.g. reflexive or Croatia with lang=sh link to Serbo-Croatian appendix (which there isn't one yet, but if this is possible I'd create it) where such terms are explained in more details. Also it would be useful to have support for this (links and categorization) in Module:headword, because often such labels are not meaning-specific (e.g. Ijekavian/Ekavian), but form-specific. --Ivan Štambuk (talk) 10:45, 3 September 2013 (UTC)Reply
Latest comment: 11 years ago1 comment1 person in discussion
I didn't notice that the list was segregated into "qualifier labels", etc, so I have just been adding labels without regard to that segregation. It may be necessary to check that each label is in the right "section" of the module, or just abandon the segregation and sort all the labels alphabetically. - -sche(discuss)00:37, 27 January 2014 (UTC)Reply
Old Latin data
Latest comment: 11 years ago6 comments2 people in discussion
Hello. Could someone change the text for Old Latin in Module:labels/data from:
I'd considered that, too; there are many striking differences between it and Classical Latin, and there's a respectable corpus to draw on. Currently, however, it's treated as just a chronolect of Latin, along with Classical Latin, Late Latin, Medieval Latin, etc. Whilst the chronolectical treatment persists, could the context label be changed as I suggest above, please? — I.S.M.E.T.A.15:50, 3 February 2014 (UTC)Reply
Latest comment: 11 years ago5 comments2 people in discussion
I think it would be best if we split the currently listed categorisation into two. pos_categories would become sense_pos_categories and term_pos_categories. That way we can categorise differently depending on what template is being used. We'd then also be able to decide that one of the two should not categorise at all, if we wanted to. —CodeCat19:03, 28 March 2014 (UTC)Reply
I suppose. But I prefer to keep things symmetrical. So maybe we could make it so the old names are the default for both, but if you want them to be different you have to use the separated names with "sense" and "term". We also probably don't want to use topical labels term-wide, because topics are inherently sense-specific generally. —CodeCat19:44, 28 March 2014 (UTC)Reply
Latest comment: 11 years ago2 comments2 people in discussion
They should categorise to "Beginning Mandarin", not "Beginning Chinese", even though the code used is 'zh'. Wyang (talk) 03:47, 8 May 2014 (UTC)Reply
OK, I'll do it a bit later, using "plain_categories". It's same as "Cantonese" and we need to add some more categories, e.g. "Min Nan Chinese", "Wu Chinese":
Latest comment: 11 years ago8 comments4 people in discussion
What's the best way to label e.g. "Min Dong, dialectal Wu" (context|Min Dong|dialectal Wu), so that terms get categorised as both Min Dong Chinese and Wu Chinese (both are plain categories? --Anatoli(обсудить/вклад)04:24, 22 May 2014 (UTC)Reply
That's not the same as cx|Min Dong|dialectal Wu|. That's equivalent to cx|dialectal|Min Dong|Wu. We should either keep those labels, or create another label "dial." which is defined as "{omit_postComma = true}". Wyang (talk) 05:14, 22 May 2014 (UTC)Reply
Thank you. "dialectal" actually belongs here to the language - "zh", in this case, so if "dialectal" cat exists, then it will be added to dialectal Chinese categories, which is okey. The visual effect is also achieved, it's Min Dong but dialectal Wu, is it right? --Anatoli(обсудить/вклад)05:20, 22 May 2014 (UTC)Reply
Visually it is the same, but it loses information about the association between "dialectal" and "Wu" and instead treats them as equal in level. If entries like 横顺 are created, they would be categorised as "Sichuanese Mandarin" < "Dialectal Mandarin", and this categorisation would not be possible. Wyang (talk) 05:29, 22 May 2014 (UTC)Reply
Hmm... I can see advantages to distinguishing things that are found "in the Wu and Gan dialects" from things that are found "in dialectal Wu". High German, the Low German varieties and English could also make distinctions of that nature. I'm not convinced that it's necessary to make such distinctions, but if we do, the best way would IMO be to have dedicated "dialectal Wu" and "dialectal Gan" labels in addition to the "dialectal" and "Wu" labels which are already present. I don't think a "dial." label would be used correctly vis-à-vis "dialectal" in practice; as DCDuring observed some few years ago, "a system that is too complicated will not be implemented correctly by anyone other than the developer of the system and perhaps an acolyte or two". (I'm not even convinced that people would correctly distinguish "dialectal Wu" from "dialectal: Wu" in practice, but meh.) - -sche(discuss)07:27, 22 May 2014 (UTC)Reply
I am undecided now. If it's OK with others, please re-add "dialectal Wu", etc. In any case, the data modules are for keeping data, even if it's large. --Anatoli(обсудить/вклад)07:50, 22 May 2014 (UTC)Reply
Vietnamese dialects
Latest comment: 9 years ago3 comments2 people in discussion
That would create lots of conflicts with existing entries that use the label "postpositive" already. We can't assume that all of them mean "postpositive modifier", not even in English. This is also one reason why I think we should actually move away from using labels to categorise things, rather than adding more categories to them. —CodeCat23:29, 8 July 2015 (UTC)Reply
Bug
Latest comment: 9 years ago2 comments1 person in discussion
Latest comment: 9 years ago1 comment1 person in discussion
What is the purpose of the language code?
If the label adds something to a category (e.g. transitive verbs), it ensures it is the correct language category (e.g. English transitive verbs). Equinox◑09:02, 26 February 2016 (UTC)Reply
So it should be the language code of the entry, right? If so, please update the documentation to clarify this.
Topic categories
Latest comment: 9 years ago7 comments3 people in discussion
Would it be possible or desirable to make labels like "animal" or "color" automatically include words in a language's Colors or Animals category (for instance, grc:Colors or grc:Animals)? There would be one benefit: you wouldn't have to specify the category in the headword template or at the bottom of the page. — Eru·tuon21:19, 10 March 2016 (UTC)Reply
Than specifying categories in the headword or at the bottom of the page: in Ζεύς(Zeús), {{grc-proper noun| ... |cat1=Greek mythology|cat2=Greek deities}}; in ἐρυθρός(eruthrós), ]. — Eru·tuon22:20, 10 March 2016 (UTC)Reply
Latest comment: 9 years ago4 comments2 people in discussion
I've been using {{label}} for tagging Ancient Greek words that are used in formulaic poetic descriptions (epithets) in the Iliad and Odyssey: for instance, the fairly famous οἶνοψ(oînops) in the phrase "wine-dark sea". For these cases, the following labels would be useful:
The commas before and after would be omitted because "epithet" should only occur in phrases such as "Homeric epithet of the sea and cattle".
This request assumes that the label "epithet" will only be used in Ancient Greek entries. If that's not correct, then I can offer a different version of the labels. — Eru·tuon23:18, 10 March 2016 (UTC)Reply
I think it would be confusing for a general word like "epithet" to link in a language-specific way. A few (not many) entries refer to things as epithets, but often in the definition rather than (currently) the context; other entries use labels which are sometimes (partially) synonymous, like "slur". - -sche(discuss)02:39, 11 March 2016 (UTC)Reply
In that case, here's a modified form. Would this work? (It might be nice to have Greek dialect labels, but not sure if it's actually necessary at the moment...) — Eru·tuon07:01, 12 March 2016 (UTC)Reply
Latest comment: 9 years ago2 comments1 person in discussion
It seems that {{label}} and {{term-label}} don't recognize the labels in Module:labels/data/subvarieties. This is a problem for me, since I'm labeling Ancient Greek words by what dialect they belong to. For instance, I'd like {{term-label|grc|Epic}} to reference the label Epic in the subvarieties module. Could the code be modified to do this, or is there a reason why it doesn't allow it? — Eru·tuon00:14, 23 March 2016 (UTC)Reply
Module:labels/datais protected with the "cascading" option turned on: Wiktionary:Main Page
Latest comment: 9 years ago11 comments4 people in discussion
The 3 April 2014 the labels list had been protected for the autoconfirmed users only. However, today a cascading protection blocks any non-admin account.
So, in order to work efficiently, that is to say without any redundancy into the articles and uncategorizing labels hazardous researches, I had to ask for some consensual and obvious modifications (because the categories already existed and were far from empty):
As a result, this maintenance inertia has slowed and prevented my projects here, and unfortunately might have provoked discouragement or frictions between contributors. That's why I propose to avoid {{lb}} into the main page, once for all. JackPotte (talk) 22:55, 19 April 2016 (UTC)Reply
I meant that I ignored the categorisation for the time that the label wasn't recognised, but I suppose that this doesn't work as well for busier pages like English entries, but I went fine with it with Japanese entries. The good days for the remainder of this month are the 25th, the 28th, the 29th, and the 30th, provided that the uncreated FWOTDs, when created, don't contain any transclusion (and they usually don't), but, for the other days, you can edit inactive WOTDs and FWOTDs to replace the transclusions, as they're allowed to be edited if they themselves are not transcluded in the main page. Nibiko (talk) 11:37, 22 May 2016 (UTC)Reply
Ideally, Words of the Day should not invoke {{label}}, but should use plain formatting like (''this'') or something equivalent instead, to avoid this issue. - -sche(discuss)21:04, 23 May 2016 (UTC)Reply
and
Latest comment: 9 years ago2 comments2 people in discussion
Latest comment: 8 years ago2 comments1 person in discussion
Excuse me. In polite section, I would like to add
pos_categories = {"polite terms"} }
and delete
display = "]"}
.
I'm working on the Javanese language and I find a category of polite terms (Javanese: tembung krama) is necessary for any lemma with the polite label. This is similar to categories of honorific terms (Javanese: tembung krama inggil) and humble terms (Javanese: tembung krama madya) that Javanese can have here. In every Javanese dictionary, those three categories always follow every lemma and knowing which category a lemma belongs is important.
I don't think the link to Glossary is needed since the term polite is not found there.
Thanks! Minor issue maybe, but probably just because there's some data cleaning/workaround deployed at *some* level in the stack. – Jberkel (talk) 22:27, 15 August 2016 (UTC)Reply
label for units of measure
Latest comment: 8 years ago5 comments3 people in discussion
Are there terms whose usage context is restricted to when units of measure are being discussed? I doubt it. So a label should not be used. If you want to categorize, simply add a category (as in ]), either by spelling it out or by using {{C}}. - -sche(discuss)22:36, 24 August 2016 (UTC)Reply
Isn't a label's purpose also to categorize? Maybe I misunderstood then. I find labels very helpful to get a quick idea of the scope. Categories are hidden at the bottom of the page and it's often not clear to which sense they belong. – Jberkel (talk) 00:46, 25 August 2016 (UTC)Reply
That's a secondary effect, but not the primary purpose. The primary purpose is to indicate per-sense grammatical information, and to indicate the context within which a sense is primarily used. Something like kilometer is not used primarily within a certain context, it's used generally and understood without context. As a rule, context-indicating labels are used with senses that exist along other, more general senses as well. —CodeCat00:59, 25 August 2016 (UTC)Reply
@D1gggg: That's because the display field is empty. It should either have content or not be given at all. However, I can make it so the module ignores an empty display field. — Eru·tuon19:58, 26 February 2017 (UTC)Reply
regarding "remove empty display" - I was asked at my user page not to display such specific label.
No, you are misunderstanding me. I am referring to the code display='' that you added to Module:labels/data. The stuff between the quotes is the display. It should not be empty. Between the quotes, add a link to a page that explains what a "hedge" is. — Eru·tuon20:35, 26 February 2017 (UTC)Reply
call senseid with "grammar" as parameter
Latest comment: 8 years ago2 comments2 people in discussion
Latest comment: 7 years ago1 comment1 person in discussion
This seems to be sorely lacking to me.. I don't understand this at all. I can link to Australia, slangs and transitive. Some pages seem to indicate I could link or have the category for things like accounting or acting, but that doesn't seem to work at all. It seems like this would be useful if you could just put any word in somehow, like {{lb|en|WP:money|slang}} (WP:money,slang) to have it link to the Wikipedia page for money but that doesn't work either. Am I missing something? W3ird N3rd (talk) 11:00, 4 August 2017 (UTC)Reply
labels = {pos_categories = { "pluralia tantum" },
= {pos_categories = { "pluralia tantum" },">edit]
Latest comment: 7 years ago2 comments2 people in discussion
I would suggest adding a label called "plural only verb", with whatever display text ("plural only"?) and categorization is desired, to use in those entries. If verbs and affixes need different categorization, a "plural only affix" label may also be needed. - -sche(discuss)20:02, 6 October 2017 (UTC)Reply
Categorization for the "outside" label
Latest comment: 7 years ago2 comments2 people in discussion
Currently, this template includes the entry in the regional category for every region mentioned, regardless of a preceding outside label. So, for example, the following code:
# {{lb|pt|except in|Brazil}} ]
…would include câmara in the Category:Brazilian Portuguese. I think such behavior is correct and, I assume, deliberate. Why should we restrict the regionalism category to additional senses, excluding absent senses ?? @Ungoliant MMDCCLXIV: thinks it "doesn’t make sense," though. So, how should this template behave?
As is; (ie., absent and additional senses get categorized together)
A better solution would be to tag the sense with the places where it is used (i.e. (Portugal, Africa) rather than (not in Brazil)). The current tag is better than no tag, but care should be taken so that sense isn’t added to Category:Brazilian Portuguese (which would indicate that the sense is only, or mostly, used in Brazil as opposed to all other non-tagged places).
You may want to propose the creation of categories for senses not used in a given place in the Beer Parlour. The existing regiolect categories are not a good place for that information as they stand. — Ungoliant(falai)17:27, 15 December 2017 (UTC)Reply
Add maritime to topical?
Latest comment: 5 years ago1 comment1 person in discussion
@Victar: Adding a prefix from part of the language code would be hard to implement. So what you are suggesting is to use etymology language codes in {{label}} and {{term-label}} and translate them to their canonical names and add a Wikipedia link if possible? I suppose that would save the work required to add labels to the appropriate label data module. — Eru·tuon02:25, 28 June 2018 (UTC)Reply
Latest comment: 5 years ago2 comments2 people in discussion
I noticed some terms when input like "offensive" automatically link to that word, while others do not. Is this a list of options for what can be input there? Ranze (talk) 19:46, 18 October 2018 (UTC)Reply
(This is followed by multiple "subsenses" all related to this overarching sense.)
I find this confusing. The word "heading" is presumably intended to signal that a collection of related senses is being introduced (see play#Verb for this example in context), but readers may be mislead into thinking that "heading" is trying to indicate some grammatical property of the word "play" itself (as are "transitive" and "intransitive"). I didn't find any other entries that did this, but cat#Noun contains such "collections of senses" without using this template. Is the usage I cite above nonstandard? Should it be changed? Could "heading" be replaced by, say, "multiple senses"? Has this issue been discussed before? <time passes> I see that this was introduced to the entry by User:ReidAA (contribs) on 21 January 2015. - dcljr (talk) 13:10, 26 November 2019 (UTC)Reply
That same edit by ReidAA I just linked to contains other changes I find weird (so experienced users might want to look it over carefully), but that's an issue for another talk page… - dcljr (talk) 13:18, 26 November 2019 (UTC)Reply
We should probably make "dialects" display "dialects", while still categorizing the same way, because this comes up in a number of places. Although, another way of doing this would be "dialectal, otherwise obsolete". - -sche(discuss)22:20, 11 January 2020 (UTC)Reply
I have re-separated the label "dialects" (which was the historical state of affairs, until it was changed recently by someone who meant well but didn't think the consequences all the way through) so that it categorizes the same as "dialectal" but displays "dialects" to address this not-infrequent situation. I will flip through entries using the label with AWB in a bit to check that they are still displaying sensibly. - -sche(discuss)21:02, 14 January 2020 (UTC)Reply
"social media" label
Latest comment: 5 years ago1 comment1 person in discussion
I think we should have a "social media" label. "Internet" seems to get used as catch-all for all sorts of things happening on the internet. Or maybe the internet has become so dominated by social media that it's now treated synonymously? – Jberkel07:57, 25 June 2020 (UTC)Reply
@Suzukaze-c: That would be the right module to put that sort of label, but what happened is that the label in Module:labels/data/subvarieties overrode it. Maybe what we'd need is for {{lb|en|South Korea}} to behave differently from {{lb|ko|South Korea}}, but at the moment the structure doesn't allow that; one or the other of the two labels would need a different key (South Korean something or other versus just plain South Korean). In a past discussion User:Rua suggested what I think was something like labels = { en = { ... }, ko = { ... } }. I've come to agree that's the best way to solve this sort of problem properly, but it'd require changing Module:labels to accept a new label data structure in addition to the current one. — Eru·tuon21:45, 14 December 2020 (UTC)Reply
Code for categorizing into "Category:English obsolete forms"
Latest comment: 4 years ago1 comment1 person in discussion
@Sgconlaw The issue is that e.g. sometimes I want to write something like {{lb|it|transitive|often|figurative|or|jocular}} and it comes out 'figuratively', which reads wrong. Originally 'figuratively' mapped to 'figurative' which would have made this read correctly, but then people who put 'literally' by the first sense of a term complained that they wrote 'figuratively' by the second sense and it came out 'figurative', which looked wrong, so they reversed the mapping. Although 'figurative' and 'figuratively' mean the same thing (and link to the same glossary entry), sometimes you want the adverbial form to display and sometimes the adjectival form, and we shouldn't force it one way or the other. It's similar to labels 'Tuscan' vs. 'Tuscany'; they mean the same thing but sometimes you want one to display, sometimes the other. Benwing2 (talk) 20:27, 20 February 2023 (UTC)Reply
To me, "often figuratively or jocular" seems fine ... Actually I don't know why we didn't just shift entirely to the adjectival form. "Literal" and "figurative" also seem fine to me. — Sgconlaw (talk) 20:33, 20 February 2023 (UTC)Reply
@Theknightwho I noticed you changed the label to figurative in all entries. Perhaps it would've been good to have a BP discussion about the display of these labels as they are used in thousands of entries. I don't have a strong opinion, but slightly prefer the adverbs over the adjectives as the default labels. In case we stick with the adjectival form, certain entries need to be corrected: "used figurative" (and perhaps others). (@Benwing2, Sgconlaw) Einstein2 (talk) 00:44, 1 September 2023 (UTC)Reply
@Einstein2 You make a good point - I hadn’t realised it was used with “used figuratively” et al in labels. I was merely changing it to match many of the other aliases we already have. Theknightwho (talk) 01:05, 1 September 2023 (UTC)Reply
Should we switch entirely over to adjectives? I don't have a strong feeling one way or another, but note that we have "attributively" and (until recently) "figuratively" which are adverbs, and then many adjectives which seem to predominate: "formal", "humorous", "poetic", and so on. ("Used figuratively" could just be replaced by "figurative" or "figuratively", in my view.) — Sgconlaw (talk) 10:22, 1 September 2023 (UTC)Reply
@Theknightwho It sounds like you undid my change to split 'figurative' and 'figuratively'. The whole reason I did this was for reasons like pointed out by User:Einstein2, sometimes one makes more sense and sometimes the other in particular label configurations. It is similar IMO to 'Tuscan' vs. 'Tuscany'; merging the two led to all sorts of solecisms so I split them. I would suggest a BP discussion to make sure we have consensus before going and changing/cleaning everything to a particular person's preferred standard. Benwing2 (talk) 19:36, 1 September 2023 (UTC)Reply
I changed "figurative" back to "figuratively" in order to bring it into line with "literally". If you would like to make further modifications with the display of the labels, please start a BP discussion. Einstein2 (talk) 18:43, 23 October 2023 (UTC)Reply
Latest comment: 2 years ago1 comment1 person in discussion
Could 'stenoscript' be added as a context label, with corresponding category? (All instances are tagged as lang=en, but that's redundant.) kwami (talk) 03:34, 4 March 2023 (UTC)Reply
Please add
Latest comment: 2 years ago1 comment1 person in discussion
This is weird and confusing, and shouldn't show up on mainspace entries. We should be showing an error instead for empty parameters. For example display on Template:label, can't we just manually pass "example"? (@Benwing2)
@Theknightwho This is a bug in parameter handling in Module:parameters. Can you take a look? When you specify required = true, list = true it needs to check to make sure there are no list values at all but it appears to be just checking the first value. Benwing2 (talk) 01:28, 15 March 2024 (UTC)Reply
Teesside/Hartlepool English redirecting to Smoggie
Latest comment: 11 months ago2 comments2 people in discussion
For whatever reason, the Teesside English (also aliased Hartlepool) links to the Wikipedia page of w:Smoggie, “a colloquial term used to refer to people from the Teesside area”. It's also mentioned there that “Originally, this was a term of abuse”. It does contain one section about the language (including some phonology changes and vocabulary), but wouldn't this dialect better fit redirecting to w:Teesside or some separate entry for the dialect?TheChilliPL (talk) 21:37, 12 July 2024 (UTC)Reply
@TheChilliPL No, it's better to link to a page that actually talks about the dialect, and not just a generic page for the place. Given that there is no page for Teesside English, the page for Smoggie is the best we have. Just like "Geordie" and "Mackem", "Smoggie" can also specifically refer to the dialect itself. Theknightwho (talk) 05:33, 13 July 2024 (UTC)Reply
"buzzword"
Latest comment: 6 months ago2 comments2 people in discussion
Latest comment: 7 months ago1 comment1 person in discussion
The label "by extension" is used quite often (more than 12,000 times). It always annoys me that it doesn't generate a link around the word "extension", and I think we should add one. And maybe even a category called "terms with senses derived by extension". What do you think? Tc14Hd (aka Marc) (talk) 18:46, 22 November 2024 (UTC)Reply