Wiktionary:Votes/2014-08/Migrating from Template:term to Template:m

Hello, you have come here looking for the meaning of the word Wiktionary:Votes/2014-08/Migrating from Template:term to Template:m. In DICTIOUS you will not only get to know all the dictionary meanings for the word Wiktionary:Votes/2014-08/Migrating from Template:term to Template:m, but we will also tell you about its etymology, its characteristics and you will know how to say Wiktionary:Votes/2014-08/Migrating from Template:term to Template:m in singular and plural. Everything you need to know about the word Wiktionary:Votes/2014-08/Migrating from Template:term to Template:m you have here. The definition of the word Wiktionary:Votes/2014-08/Migrating from Template:term to Template:m will help you to be more precise and correct when speaking or writing your texts. Knowing the definition ofWiktionary:Votes/2014-08/Migrating from Template:term to Template:m, as well as those of other words, enriches your vocabulary and provides you with more and better linguistic resources.

Migrating from Template:term to Template:m

Support

  1. Support --Vahag (talk) 18:23, 29 August 2014 (UTC)
  2. SupportCodeCat 19:28, 2 September 2014 (UTC)
  3. Support Mulder1982 (talk) 19:45, 12 September 2014 (UTC)
  4. Support, but I would like the final result to be {{term}} redirecting to {{m}} (or vice versa). --WikiTiki89 19:46, 12 September 2014 (UTC)
    To do that, we would first need to orphan {{term}}, as the parameters are not compatible. And at that point there is no need for a redirect anyway, is there? —CodeCat 20:03, 12 September 2014 (UTC)
    Yeah there is: so that people can start using {{term}} instead of {{m}} if they feel like it suits them better. --WikiTiki89 20:05, 12 September 2014 (UTC)
    We should aim at there being one template in the mainspace. We should aim at at least a semblance of professionalism. Keeping term with old parameter order to make old revision legible is fine. --Dan Polansky (talk) 20:13, 12 September 2014 (UTC)
    Actually, that's also a good idea. --WikiTiki89 20:31, 12 September 2014 (UTC)
  5. Support — It's better to have one term (whichever) than two - since the newbie suspects there's a subtle difference between them. Since most will look for an example (like me) either would do, but m is shorter — Saltmarshαπάντηση 19:30, 5 November 2014 (UTC)
  6. Weak support — I can agree that "term" is more descriptive than "m", which can be confusing. On the other hand, not needing a named language parameter makes things a lot easier. ObsequiousNewt (ἔβαζα|ἐτλέλεσα) 00:14, 25 November 2014 (UTC)
  7. Support "term" does not mean what it says, and it's NOT more descriptive; it's misleading, beside being longer. "m" would force the newbies to read the docs, which is eventually a good thing, because by seeing "term" they probably think that they already know what the template does, while they usually don't. --Z 10:07, 1 December 2014 (UTC)
  8. Support per Z. --Fsojic (talk) 10:53, 1 December 2014 (UTC)
  9. Support --Anatoli T. (обсудить/вклад) 02:05, 8 December 2014 (UTC)
  10. Support per Z. Keφr 08:02, 9 December 2014 (UTC)
  11. Support. {{m}} is much easier to use and should be the default. I agree with Wikitiki89, though, that it's best to leave {{term}} functional, since it's been in use for so long, and because we should go as easy as possible on casual editors. I think the best course of action is to swap out current uses of {{term}} to reduce confusion and encourage the use of {{m}}, but not to introduce any overt obstacles to use of {{term}} by those who want to use it (hidden tracking categories should be ok). I can understand the resentment of many here for the way the changes in behavior of some templates with respect to omitted language codes was handled, but, on balance, I think this is a better course of action. Chuck Entz (talk) 20:15, 3 January 2015 (UTC)
  12. Support embryomystic (talk) 05:25, 22 January 2015 (UTC)
  13. SupportUngoliant (falai) 05:29, 22 January 2015 (UTC)
  14. Support Vorziblix (talk) 01:25, 29 January 2015 (UTC)

Oppose

  1. Oppose No user will ever guess what {{m}} means, while the meaning of {{term}} is rather obvious. We need to think about non-regulars and casual contributors too. -- Liliana 18:05, 29 August 2014 (UTC)
    At least the name of {{m}} is intriguing while term is misleading - one may take it for only a decorating template (like I did until recently xD).--Dixtosa (talk) 19:07, 29 August 2014 (UTC)
    Just to note, {{m}} is now a shortcut for the more descriptive name {{mention}}, while {{l}} is likewise a shortcut to {{link}}. —CodeCat 21:10, 5 November 2014 (UTC)
    I always thought {{l}} stood for "list-item", not just "link". Keφr 09:05, 8 December 2014 (UTC)
    I also thought that. --WikiTiki89 09:33, 8 December 2014 (UTC)
  2. Oppose. It's a cryptic and unhelpful name. But I think the parameter order of {{m}} is better. Perhaps it would be nice to migrate all existing uses of {{term}} to that parameter order. This, that and the other (talk) 07:37, 31 August 2014 (UTC)
  3. Oppose deleting Template:term. No opinion regarding any other action. —Mr. Granger (talkcontribs) 19:32, 2 September 2014 (UTC)
  4. Oppose. The name term is more comprehensible. The old revision histories will be clearer (not that that's a strong argument in my opinion, but it's worth something). And even if all were equal (m and term were equally good), there'd be no reason to specifically change from one to the other. I have no opposition, however, to reordering the parameters of either template to match those of the other, provided that that's done without introducing errors.​—msh210 (talk) 16:35, 18 September 2014 (UTC)
    Changing {{term}}'s parameters to match {{m}} would break the old revision histories anyway. --WikiTiki89 20:45, 18 September 2014 (UTC)
  5. Oppose. As above - term means what is says; m will always mean masculine to me. SemperBlotto (talk) 08:51, 13 October 2014 (UTC)
  6. Oppose Per others, especially Liliana's argument. User: PalkiaX50 talk to meh 09:19, 13 October 2014 (UTC)
  7. Oppose --Dijan (talk) 19:33, 14 October 2014 (UTC)
  8. strong. Another unnecessary merge. Purplebackpack89 14:14, 2 November 2014 (UTC)
  9. Oppose – I read the ‘rationale’ but can't see any explanation…does this new template do something different? If not, why can't we just change how {{term}} works? And why ‘m’?! Basically, no. Ƿidsiþ 08:15, 17 November 2014 (UTC)
    If we change term to work like m... that's basically what the support camp is arguing for. That's basically support but under another name. Renard Migrant (talk) 18:54, 7 December 2014 (UTC)
    @Renard Migrant I don't think so. The disagreement seems to be about the template name. I don't see anyone insisting that term should be used like {{term|...|lang=en}} instead of {{term|en|...}}. --Dan Polansky (talk) 18:59, 7 December 2014 (UTC)
  10. Oppose This doesn't simplify anything. At all. --Neskaya sprecan? 05:02, 28 December 2014 (UTC)

Abstain

  1. Abstain I can't decide between the pros and the cons. --Dan Polansky (talk) 17:18, 26 September 2014 (UTC)
  2. Abstain, I prefer {{m}} but I see no reason to 'ban' {{term}}. Renard Migrant (talk) 18:50, 7 December 2014 (UTC)
    @Renard Migrant Would it be accurate to say you support "Replacing all uses of Template:term with Template:m" but not "subsequently discontinuing Template:term"? --Dan Polansky (talk) 18:56, 7 December 2014 (UTC)
    No it wouldn't. Renard Migrant (talk) 12:37, 21 January 2015 (UTC)

Decision