Hello, you have come here looking for the meaning of the word Template talk:de-noun. In DICTIOUS you will not only get to know all the dictionary meanings for the word Template talk:de-noun, but we will also tell you about its etymology, its characteristics and you will know how to say Template talk:de-noun in singular and plural. Everything you need to know about the word Template talk:de-noun you have here. The definition of the word Template talk:de-noun will help you to be more precise and correct when speaking or writing your texts. Knowing the definition ofTemplate talk:de-noun, as well as those of other words, enriches your vocabulary and provides you with more and better linguistic resources.
Diminutive
Latest comment: 15 years ago1 comment1 person in discussion
(Note to self or anyone who feels like doing this before I get to it because I'm lazy) must add option of "dim=?" to hide diminutive form stuff if unsure (like how en-noun has pl=?) — opiaterein — 01:27, 27 June 2009 (UTC)Reply
Only categorize entries, not other pages.
Latest comment: 14 years ago1 comment1 person in discussion
This template needs to be changed so that it only adds entries, not other kinds of pages, to {{de-noun}}. While I'm making that change, is there anything else that needs changing? —RuakhTALK12:26, 18 February 2010 (UTC)Reply
gen+gen2 doesn't work
Latest comment: 12 years ago6 comments6 people in discussion
I tried to use both parameters "gen" and "gen2" in an entry today, and it shows only the first genitive. Using "genitive" and "genitive2" works. --Zeitlupe07:30, 17 June 2010 (UTC)Reply
In the case where there are two genitives, you should probably use gen1 and gen2. If you just write gen, the template assumes there's only one genitive, and refuses to display the other. -- Prince Kassad08:20, 17 June 2010 (UTC)Reply
Latest comment: 12 years ago1 comment1 person in discussion
Hey, please edit the template in a way that it links to the German section of the target page. I know, this is a somewhat rare occurrence cos German nouns are capitalized, but anyway, better be safe as houses and make this dictionary flawless. :) -- Frous (talk) 03:53, 9 March 2012 (UTC)Reply
Fixing and rewriting the template
Latest comment: 12 years ago12 comments4 people in discussion
(taken from User talk:Mglovesfun)
I've added line breaks and indenting to the template code just so it's a little easier to understand. And wow... it's a really big mess! If no one else minds I can try to rewrite and simplify the code a little without breaking any existing entries (hopefully)? —CodeCat16:23, 30 June 2012 (UTC)Reply
Quite the opposite! Zeitlupe pointed out the problem in 2010 on the talk page. I merely tried to fix it, since nobody else had in the previous two years! Mglovesfun (talk) 16:24, 30 June 2012 (UTC)Reply
Well, the code in this template is similar to how {{nl-noun}} was before I completely rewrote it. I removed most of the duplicate parameters so that there was only one way to specify each parameter, which simplified the code a lot. More recently I also made the gender a numbered parameter, following the principle that 'numbered parameters are required, named parameters are optional' which seems to make sense in many cases (though not all). —CodeCat16:32, 30 June 2012 (UTC)Reply
After my question in 2010 was answered, I always used gen if there is only one genitive form and gen1+gen2 if there are two. As long as it is documented, I don't see a problem with that. --Zeitlupe (talk) 06:55, 1 July 2012 (UTC)Reply
I imagine the new template to work either like this {{de-noun|gender|genitive|plural|diminutive}} or like this {{de-noun|g=gender|genitive|plural|diminutive}}. If there is more than one possibility for each of those, they will use g2=, gen2=, pl2=, dim2= and so on, while the 'first' still uses the parameters I mentioned (in other words, adding a second possibility doesn't change how you specify the first). Is that ok? —CodeCat11:20, 1 July 2012 (UTC)Reply
@Zeitlupe, it contradicts other templates of the same nature, also the template contradicts itself as it doesn't (or didn't) have a pl1 parameter, only a pl parameter! So the parameters were gen or gen1 and gen2 but pl or pl and pl2, not pl1. Furthermore, documentation is good of course, but if ideally the template is simple enough that users can work out how to use it without documentation, it's better no? Mglovesfun (talk) 20:43, 6 July 2012 (UTC)Reply
I've made the changes now, and a script is currently running to update all old usages. I've added documentation as well. —CodeCat16:57, 2 January 2013 (UTC)Reply
OK, when the genitive singular is the same as the nominative (e.g. with feminines), no link is created and the word appears in bold instead. But when the plural is the same as the singular (e.g. Penner), the plural is a clickable link to the exact same section. Can that please be fixed? —Angr22:40, 2 January 2013 (UTC)Reply
Btw, there's a known issue where the auto-generated inflected forms of many feminine nouns are wrong due to human error (people added the wrong declension templates and/or set the wrong parameters to the declension or headword templates). So, accelerated creation of missing inflected forms would need to proceed cautiously. Most masculine and neuter nouns are OK, as far as I know. - -sche(discuss)01:05, 19 February 2015 (UTC)Reply
I don't know where to add it, or even if it is the correct code! But the plan to include something which categorises missing plurals is cool. --Type56op9 (talk) 13:45, 19 February 2015 (UTC)Reply
About some pluralia tantum
Latest comment: 9 years ago3 comments2 people in discussion
Well, I think that it is possible to write the code such that in the case "pl" does not exist, the last parametre is used. But before making changes to such a template that is used more than 1000 times, it is best to make a decision what and how to do it.--Sae1962 (talk) 05:38, 18 April 2015 (UTC)Reply
Unchanged genitive and plural in -en is often incorrect. So many entries in which no genitive or plural was entered (e.g. Duftanhänger) now mention incorrect forms. Thus all German entries which now mention incorrect forms have to be cleaned up. ... -84.161.6.2006:30, 20 November 2016 (UTC)Reply
New parameter
Latest comment: 6 years ago1 comment1 person in discussion
Please add an optional parameter for compound forms, so we can display that 'Forum' in a compound becomes 'Foren-', 'Hund' becomes 'Hunde-', 'Satan' becomes 'Satans-' and 'Haus' stays 'Haus-' etc. pp. This has been mused for Norwegian too. Korn (talk) 13:17, 3 August 2018 (UTC)Reply
Template reboot
Latest comment: 2 years ago4 comments3 people in discussion
Thanks @Benwing2 very much for updating this rather cumbersome template! I have a few requests for the documentation page, though. Could you explain the significance of the exclamation point in {{de-noun|m|f=!weiblicher Geschäftspartner,in}}? Also, since "weiblicher Geschäftspartner" would be SOP and should never be an entry, can you edit the module so that {{de-noun|m|f=!]er Geschäftspartner,in}} links weiblich separately? (Clearly there would be no need to link to Geschäftspartner when you're on the page Geschäftspartner. Thanks! —Mahāgaja · talk12:05, 8 February 2022 (UTC)Reply
@Mahagaja Yup, I am planning on adding support for embedded links like this. The significance of the exclamation point is to indicate that the term in question is the full form of the term rather than an ending. The module recognizes this automatically if the form begins with a capital letter, but if it begins with a lowercase letter, it assumes it's an ending unless told otherwise. There might be a smarter way of distinguishing them, but I don't want to do something that's hacky. Benwing2 (talk) 03:14, 9 February 2022 (UTC)Reply
@Mahagaja: I really don't think we should list "weiblicher Geschäftspartner" or other SOPs in the headword. Any person noun (of unspecified gender; the "default" form) can be preceded with männlich or weiblich, just like one can say "male driver" or "female driver", but of course we don't mention "female driver" in the article driver. Furthermore, what's meant with "feminine" (by my understanding) is the grammatically feminine form (-in) (which sometimes doesn't refer to entities of female natural gender (there was an annoying dispute not too long ago...)). — Fytcha〈 T | L | C 〉 15:25, 10 February 2022 (UTC)Reply
I'm not wild about listing "weiblicher Geschäftspartner" in the headword line either, but the template ought to be flexible enough for it to be possible. —Mahāgaja · talk16:13, 10 February 2022 (UTC)Reply
|n=+
Latest comment: 2 years ago5 comments2 people in discussion
@Benwing2 I've noticed that the template now supports |f=+ which is a phenomenal idea and simplifies a lot of work for German editors! Can we perhaps also get support for |n=+? The semantics are: der Erwachsene = the adult human (male or unspecified sex), die Erwachsene = the female adult human, das Erwachsene = the adult/mature thing (e.g. a personality, a deed, an aspect ...). See e.g.:
2018 June 11, Julianna Baggott, Harriet Wolfs siebtes Buch der Wunder: Roman, btb Verlag, →ISBN, →OCLC:
liebte diese Tätigkeit, die Effizienz, das Erwachsene daran.
@Fytcha Yup, I will add this. I am also adding various features to better support proper nouns, including surnames (which need their own table format that displays both masculine and feminine forms, which differ in the genitive), toponyms (mostly neuter) and terms that are normally used with the article. Next is to figure out how to properly handle given names. Benwing2 (talk) 05:36, 16 February 2022 (UTC)Reply
@Benwing2: In Invalider, I had to use f=+,Invalidin instead of the (expected) f=+:Invalidin. What do you think about offering both syntaxes? The colon is consistent with the rest of the template, the comma not so much. — Fytcha〈 T | L | C 〉 23:21, 18 February 2022 (UTC)Reply
Category:German terms with redundant head parameter
Latest comment: 1 year ago1 comment1 person in discussion
Latest comment: 1 year ago3 comments2 people in discussion
@Benwing2 The headword line does not generate any acceleration parameters for the genitive and plural forms. They are present in the declension table though. Looking at the code, it seems it's missing the accel_form parameter, line 473-474
@Jberkel This is intentional because I think it won't properly pick up and include other cases that are syncretic with the cases in question unless I do significant hacking on the code. It works if you click on the corresponding terms in the declension table. Benwing2 (talk) 20:05, 17 September 2023 (UTC)Reply
Ok, I don't actually need it for acceleration, I'm revisiting some parsing code I wrote a while ago which extracts the forms from the headword line (from the generated HTML), and I just noticed that it stopped working. I guess I could just change it to get the forms from the table instead. Jberkel20:15, 17 September 2023 (UTC)Reply