I think it would be vastly better not to subst this template, nor to use it directly in most cases; it would make the most sense to use it as a meta template for more specific templates like {{-ity}}
and {{-ize}}
. -- Visviva 10:54, 7 October 2007 (UTC)
Are templates {{prefix}}
and {{suffix}}
supposed to be English-only, and that's the reason why they don't accept lang= parameter (AND use {{en-term}}
which seems to be aware only of English POS)?
Same question applies for those inside Category:Suffix templates and Category:Prefix templates, although I see some French stuff there but still without lang parameter and support for alternate text (so that one could link to lemma entry and display a stem). --Ivan Štambuk 00:37, 4 November 2007 (UTC)
{{en-term}}
and replaced it with the result of {{term}}
, because it is a general template. perhaps a third (or named) parameter can be added if people are desperate to have the {{en-term}}
styling. Conrad.Irwin 00:16, 9 November 2007 (UTC){{term}}
with |lang={{{lang|}}|sc={{{sc|}}} ? Then you can use either or both as desired and get whatever customization that term gets you (including section links).{{term}}
, so most of this should be possible. H. (talk) 14:09, 30 October 2008 (UTC)I've replaced {{{{{lang}}}}} call with {{t-sect|{{{lang}}}}}. For non-top-40 languages {{{ISO 639}}} code gets expanded into wikified version which screws up linking to language sections (compare {{cu}}
with {{lang:cu}}
). It took me a while to figure this out (Special:ExpandTemplates is a great tool!).
Hopefully nothing is broken.. --Ivan Štambuk 20:15, 14 November 2007 (UTC)
I would like to categorize pages that use this template with ] but I'm not sure if that's the best category name and I don't know how {{t-sect}}
is supposed to be used. DAVilla 00:11, 25 November 2007 (UTC)
Could there be an extra parameters for instances where the original word changes when suffix is attached (i.e. instead of big + -er one could write big(g)- + -er, or more suitably for agglutinative languages which may have very different roots: mennä + -minen → mene- + -minen)? --Jyril 22:01, 23 March 2008 (UTC)
If arguments 1 or 2 refer to long English entries, the user can miss the relevant etymology or PoS. Would it be possible to allow the arguments to be of the form ] to allow for links to the right PoS or at least the right etymology. The same would apply to prefix, of course. DCDuring TALK 15:19, 4 September 2008 (UTC)
I added the word ‘From ’ in front of the template. This reflects the majority of the uses of it, namely plainly in the etymology section with not context. But that is too concise in my POV. This will break some pages, but I did some random tests on referring pages and most of them are fine. Maybe we could add an optional nofrom= parameter which would indicate the from should not be there, if people think it is needed, although I like the uniformity. H. (talk) 09:22, 23 September 2008 (UTC)
The above parameters don't work. See ծանրություն or учитель, for example. I don't have much experience in template editing, so can someone fix this please? --Vahagn Petrosyan 05:57, 1 April 2009 (UTC)
{{prefix}}
and {{compound}}
? It must be analogous, right? In {{prefix}}
gloss1= doesn't work and sc=, tr1=, tr2= do not exist. In {{compound}}
sc=, tr1=, tr2= do not exist. --Vahagn Petrosyan 07:46, 3 April 2009 (UTC)Trying to use this for things like Hebrew, the page displays properly, but the category comes up "Hebrew words suffixed with -י" with the hyphen on the wrong end of the suffix. I tried to fix this once, but got impatient pretty quickly. Could there be a way to fix it? — opiaterein — 11:38, 5 July 2009 (UTC)
I added parameters t1, t2 as alternatives to gloss1, gloss2 for the sake of "consistency" with {{compound}}
. AugPi 13:08, 20 September 2009 (UTC)
If a suffix is sandwiched between two hyphens, e.g. -ad-, then use parameter infix=yes as in vojaĝado. The alternative is to include the right hyphen in parameter 2. AugPi 21:26, 8 November 2009 (UTC)
Could there be an option to indicate multiple suffixes, if no intermediate one-suffix form exists? Nesting this template does not seem to work. --Tropylium 09:15, 11 February 2010 (UTC)
{{suffix||...|lang=eo}}
s gets rather ridiculous when etymologizing a word like homaranismo. It would be much preferable if suffix could handle three or four suffixes at once. - Robin 12:12, 22 September 2010 (UTC)
Since apparently "words" isn't specific enough (see Category:Portuguese adverbs suffixed with -mente) could someone add a pos= option to this bad boy? — opiaterein — 22:53, 3 May 2010 (UTC)
A while ago we decided not to use hyphens with Japanese and Korean (except when in Roman letters), both kana and kanji, at the BP. Is it possible to edit this template so that it reflects this change? I can take a look at it myself but I thought somebody else knows how the template works and could make the edit easily. TIA Haplology 13:28, 11 November 2011 (UTC)
{{suffixcat}}
will have to be changed accordingly. And you'll probably want to make the same change to {{prefix}}
and {{prefixcat}}
and prefix-categories. The smoothest way to do it is probably:
{{suffix}}
and {{suffixcat}}
. (I've created {{suffix/temp}}
and {{suffixcat/temp}}
, which you can steal. I haven't tested them, but I think they're good.)suffix
and suffixcat
, and all seems to be well except that the new categories still throw up an error message, for example Category:Japanese_words_suffixed_with_界. I'm deleting the old categories now. Thanks for helping me through this! Haplology 18:20, 12 November 2011 (UTC)
How it is supposed to be used? It generates weird category name. --Ivan Štambuk (talk)
Why does this template often fail to give me the font that I expect (for English) when {{term}}
, on the same line, does? Is term that much simpler? In what way? Can this defect be remedied by making if function more directly. DCDuring TALK 16:06, 18 September 2013 (UTC)
{{term}}
, so that is not the problem. —CodeCat 17:32, 18 September 2013 (UTC)
{{term}}
; they both ultimately call the same Lua function, of course, but there's also a good chunk of duplicated/unshared code in setting up the arguments to that function, and hence opportunity for discrepancies and {{suffix}}
-specific problems. —RuakhTALK 23:49, 18 September 2013 (UTC)
{{suffix}}
and {{term}}
both use Lua. (BTW, if you're asking CodeCat/me/anyone to investigate, I think you should link to an example, and/or give steps to reproduce. Otherwise this discussion won't really go anywhere.) —RuakhTALK 00:59, 19 September 2013 (UTC)Sphinx + -idae - result of {{suffix|Sphinx|idae}}
- this time with sans serif font
Sphinx - result of {{term|Sphinx}}
- this time with serif font
suffix - result of {{taxoninfl}}
- this time, as always, with sans-serif font
suffix - result of {{mul-proper noun}}
- this time, as usual, with serif font.
Is the result pattern similar for others? DCDuring TALK 01:10, 19 September 2013 (UTC)
{{term|Sphinx}}
has the "sans-serif" style from Latn-mention, while {{suffix|Sphinx|idae}}
has no such declaration. Either way I can see no difference between your examples. DTLHS (talk) 01:27, 19 September 2013 (UTC)
{{suffix}}
automatically assumes English (lang="en") while {{term}}
has no such assumption (lang="und"). DTLHS (talk) 01:36, 19 September 2013 (UTC)
{{taxoninfl}}
does not use any font or language templates or modules. {{mul-proper noun}}
uses just {{sc}}
, AFAICT. DCDuring TALK 01:43, 19 September 2013 (UTC)I have a slight issue with this template. The problem is that I cannot appropriately describe adding a suffix to a transcription of a foreign word. What I'm talking about is something like larpurlartizam. "Larpurlart" doesn't exist as a word itself in Serbo-Croatian, it is a respelling of the French "l'art pour l'art" and the suffix -izam is appended onto that. However, if I add the "lang=sh" option to the template, the link to l'art pour l'art (art for art's sake) includes the index code for Serbo-Croatian (https://en.wiktionary.orghttps://dictious.com/en/art_for_art%27s_sake#Serbo-Croatian).
Is there a way to address this issue while still having the word "larpurlartizam" automatically added to the category "Serbo-Croatian words suffixed with -izam"? 141.138.54.48 14:26, 27 October 2013 (UTC)
Sometimes you don't want the plus sign, e.g. when there's some explanation and you write "suffixed with -xy" or the like, then "suffixed with + -xy" is awkward. Could we add a parameter "noplus=1"? Or is there already a way to suppress it? 2.201.0.20 18:31, 2 April 2021 (UTC)
Is there a way to make the template link to a specific sense of the root word? Zacwill (talk) 04:34, 22 September 2024 (UTC)