This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 |
As can be seen on Category:2008–09 I-League, the template create 2009-010 instead of 2009-10 in the navigation. Can anyone take a look? Coderzombie ( talk) 05:20, 14 July 2016 (UTC)
This template is used over such a wide range of WikiProjects, so asking here.
Le Deluge (and anyone else), what would you think of using {{
LinkCatIfExists2}} so that redcats are instead greyed out (example via {{
Category in year}}
here), either as default, or as a parameter option using |linkcatifexists2=yes
, |grey=yes
, |gray=yes
, |blueonly=yes
, or the like. ~
Tom.Reding (
talk ⋅
dgaf) 13:48, 3 October 2018 (UTC)
|min=
parameter too, but its use is/was intermittent in the taxonomy area, so it could go either way. Personally, I wouldn't choose to enforce/use a |min=
param if it were available, after seeing the alternative (this template). Decade cats are
their own can of worms, arguably the worst being that YY00 cats would be duplicated/misplaced in their parent century container cats. I'm actually in the process of ridding the taxonomy area of decade cats after a recent
RfC. Also, just because one year doesn't exist doesn't mean adjacent years are sparse - some years adjacent to reds contain ~100 pages. ~
Tom.Reding (
talk ⋅
dgaf) 14:25, 4 October 2018 (UTC)This
edit request to
Template:Navseasoncats/var firsthalf has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please remove the line <noinclude>{{pp-template|small=yes}}</noinclude>
- protection templates are automatically handled by the documentation page. Thanks, --
DannyS712 (
talk) 07:14, 22 March 2019 (UTC)
I see that |min=
& |max=
currently only work for navyear
type cats, but not navdecade
& navhyphen
cats. Is there any desire to add this functionality to either of these other category types? ~
Tom.Reding (
talk ⋅
dgaf) 20:52, 14 April 2019 (UTC)
|min=
& |max=
parameters now work for all decade cats AD/BC (but not BCE yet - are there any BCE decades?). Under the
principle of least astonishment, they behave similarly as on year & ordinal categories, while navdecade behavior was otherwise left unchanged. Behavior can be changed in the future with the modification of a few constants. This was a relatively simple (other than two 0s decades situation) transfer of the min/max code from navyear/navordinal, but doing this for navseason I think would be even trickier, so that won't be done on a whim. There's also the question of whether to adopt decade's shifting behavior for seasons, or if they're to remain centered like years & ordinals.On a millennium category such as Category:3rd millennium in Egypt, there is no point showing future millennia, and it would be better to reach back to 4th millennium BC which exists in that case. I therefore suggest that all millennia categories display the range from 4th BC to 3rd after. – Fayenatic London 10:48, 4 May 2019 (UTC)
|min=
/|max=
would be made to override these defaults, of course. ~
Tom.Reding (
talk ⋅
dgaf) 12:26, 4 May 2019 (UTC)I first need to be able to go backwards and forwards from words/numbers to numbers/words. This is currently almost completely doable:
{{
Roman|2019}}
{{#invoke:ConvertNumeric|_roman_to_numeral|MMXIX}}
{{
Ordinal to word|1}}
{{#invoke:ConvertNumeric|_english_to_ordinal|First}}
(produced as a result of this discussion)I could not easily find a word-to-ordinal utility (it's possible I glossed over it), and Template:Word to *
& Module:Word to *
don't exist (yet).
Questions to Gonnym, Fayenatic london, and everyone else:
~ Tom.Reding ( talk ⋅ dgaf) 16:58, 8 June 2019 (UTC)
numeral_to_english_less_100()
. If you go above 100 then that is just a little more process that goes into with numeral_to_english_less_100()
. --
Gonnym (
talk) 09:47, 12 June 2019 (UTC)
p.find_var
and nav_wordinal
functionality can be extended. ~
Tom.Reding (
talk ⋅
dgaf) 02:15, 14 June 2019 (UTC)
The template works for e.g. 1999–2000 but does not currently link to 1999–2004, see Category:MEPs 2004–09. – Fayenatic London 08:36, 27 May 2019 (UTC)
navhyphen
|min=
& |max=
having the same simple behavior as the other category types (i.e. no offsetting). ~
Tom.Reding (
talk ⋅
dgaf) 20:19, 8 June 2019 (UTC)
@ Wikipedia:Categories for discussion/Log/2019 May 29#Category:MEPs 1952-58, posted here separately for visibility. ~ Tom.Reding ( talk ⋅ dgaf) 22:10, 29 May 2019 (UTC)
@ Oculi, Gonnym, Philip Stevens, Lugnuts, FoxyGrampa75, and Concus Cretus: pinging everyone involved with the above CfD. Of the ~821 term-categories, 31 of them (~4%) have term lengths of exactly 1 and follow the (optional) YYYY-YY format, so they stand out a little amongst the vast majority of 2+ year terms with the unabbreviated YYYY–YYYY format. Since I can see arguments both for and against, what's the sentiment for formatting all of these YYYY–YYYY, regardless of term length? ~ Tom.Reding ( talk ⋅ dgaf) 13:01, 8 June 2019 (UTC)
Special:WhatLinksHere/Category:MEPs_for_the_Republic_of_Ireland_2009–14 shows that the updated adjacent categories Category:MEPs for the Republic of Ireland 2004–2009 and 2014–2019 are in some way linking to the otherwise obsolete redirect at the 2-digit date. Is this a minor bug in the module? – Fayenatic London 09:20, 19 June 2019 (UTC)
mw.title.new
is used to check the existence of a category, it counts as a link to that page. I've updated the gap checking routine to check the most likely name first, so a multi-year range will first check an unabbreviated multi-year adjacent range, then, if not found, check the MOS-incorrect abbreviated multi-year adjacent range. Likewise, a single-year range first check an abbreviated adjacent range, then, if not found, will check the unabbreviated range (both MOS-acceptable). This should have been updated after
MOS:DATERANGE CfDs, but was overlooked. This should lower the number of attempts, on average, needed to find the nearest existing cat, and can be optimized even more to start with whatever format the parent category is using, then, if not found, try the other one. ~
Tom.Reding (
talk ⋅
dgaf) 16:14, 20 June 2019 (UTC)
No consensus to move, after extended time for discussion. Notably, even among those who supported a move, there was no clear determination of a move target. bd2412 T 19:14, 24 June 2019 (UTC)
– This template started as a category navigation tool for football seasons, but with the recent changes this has become a multi-style navigation tool, as can be seen by the doc at Template:Navseasoncats/doc#About. The name of the template should describe what it does and "navseasonscats" does not do that. Gonnym ( talk) 10:32, 25 May 2019 (UTC) --Relisting. Steel1943 ( talk) 13:48, 4 June 2019 (UTC)
describe what it does, and any alternative which actually describes its functionality is going to be much more verbose, e.g. Template:Category navigation by year, decade or season.
the nominator si clarly unfamiliar with the v wide range of category navigation templates already in use.(sic), you'd be surprised, but I know how to read. -- Gonnym ( talk) 17:58, 25 May 2019 (UTC)
But I accept your assurance that my good faith in your ability to spot the folly of a massively ambiguous title was misplaced.and I truly hope that in real life your attitude to others is much less vain. There is nothing wrong with an ambiguous title, as can be seen by WP:PRIMARYTOPIC, in this specific case, this template does indeed fit the criteria in that it's scope is already pretty large, while the other templates have a very specific and smaller scope. As such, the name I proposed works. That being said, and as I previously said at the very start of this thread, I was never against an alternative and better proposal. And while you can argue that "seasons" means that, it really doesn't, which is why "seasons" is not a good name and neither are your CamelCase proposals per WP:TPN and general recent practice. -- Gonnym ( talk) 21:08, 25 May 2019 (UTC)
The category (and similar ones) has been moved. Could somebody please update the description. Thanks.
Currently, multi-year/hyphenated cats can search for and follow {{ Category redirect}}s. 2 questions arise:
See Category:Navseasoncats range redirected (base change) for more. ~ Tom.Reding ( talk ⋅ dgaf) 14:43, 15 June 2019 (UTC)
|follow-redirects=yes
, or|follow-redirects=no
|follow-redirects=no
allowed ~
Tom.Reding (
talk ⋅
dgaf) 15:18, 22 June 2019 (UTC)I created {{ R from category navigation}} in an effort to keep these cat #Rs from being deleted. ~ Tom.Reding ( talk ⋅ dgaf) 23:14, 28 June 2019 (UTC)
See Category:2010s in Ohio, which uses {{ Navseasoncats}} with no parameters.
But the bolded non-link for the current page is displayed to the right, instead of in the centre. Category:2000s in Ohio in Category:2020s in Ohio both display correctly, so I dunno why 2010s is wrong. Please can it be fixed?
Having the current item consistently in the centre makes the navbar much easier to use. -- BrownHairedGirl (talk) • ( contribs) 21:35, 24 August 2019 (UTC)
|max=
parameter with any number, and show greyed text up to '2060s' by using |max=2060s
, or preferably a larger # like |max=9999
. ~
Tom.Reding (
talk ⋅
dgaf) 16:35, 25 August 2019 (UTC)
-->|{{Navseasoncats/navdecade|{{Navseasoncats/var firsthalf|{{{testcase|}}}}}|{{str left|{{Navseasoncats/var season|{{{testcase|}}}}}|4}}|{{Navseasoncats/var lasthalf|{{{testcase|}}}}}|{{str left|{{CURRENTYEAR}}|3}}0}}<br/><!--
{{str left|{{CURRENTYEAR}}|3}}0
at the end, which has been there
since March 2017.
1950s • | 1960s • | 1970s • | 1980s • | 1990s • | 2000s | • 2010s | • 2020s | • 2030s |
1950s • | 1960s • | 1970s • | 1980s • | 1990s • | 2000s • | 2010s | • 2020s | • 2030s |
1950s • | 1960s • | 1970s • | 1980s • | 1990s • | 2000s • | 2010s • | 2020s | • 2030s |
1950s • | 1960s • | 1970s • | 1980s • | 1990s • | 2000s • | 2010s • | 2020s | • 2030s |
@ BrownHairedGirl: then I think the solution is a compromise where the the show-1-decade-ahead style is maintained for 2 decades beyond the current, instead of just 1. That maintains the original behavior (even moreso), and limits jumpiness.
Note that it is not a coincidence that this 1-ahead style wasn't discussed until 2019, the end of the current decade. For prior years, the old 1-ahead style presented no problems. ~ Tom.Reding ( talk ⋅ dgaf) 23:44, 25 August 2019 (UTC)
The parameter |min=
has been implemented so that blank spaces appear where earlier dates would be. The range remains centred on the "current" category.
If the range is short, i.e. both min and max are used and they are not far apart, then I support the current outcome.
However, in other cases with just |min=
, I would prefer the displayed range to shift so that it starts with the min.
This can be achieved by using the testcase parameter to determine the category at the centre of the template, but then both the testcase date and the current category date are highlighted, e.g. [2]. – Fayenatic London 08:24, 11 June 2019 (UTC)
|min=
parameter. Anything else gets more complicated (but is still doable):|max=
param provides the user with an 'escape' from this default behavior, and will force the 'current' element to always be centered.|max=
this ability would lock-in this shifting behavior, giving the user fewer options, unless a new |max=current
value is accepted.|min=
simply hides elements lower than its value.|max=
destroy a 'right offset', while |min=
produces a 'left offset'. But, the alternative would be to remove the default right-offset, and require something like |max=current
to recover it.|min=
/|max=
behaviors also kinda makes sense (I might be biased here due to the original template's behavior).|min=
& |max=
the same behavior, that is, producing the appropriate left/right offset. No offsets will occur by default, only by min/max. In cases of automatically-updated right-offsets, |max=current decade
, |max=current millenia
, etc. can be used.|min=
the ability to induce a left offset, and keep |max=
behavior as-is.I'm thinking about using a default left-offset for category types which will only have positive integer elements, like TV seasons, numeric and word ordinals, and roman numerals. This will not/should not interfere with #Should min & max shorten, or shift, the range displayed?.
Currently, the |max=
parameter overrides any default right-offsets, forcing the current element into the center. The new left-offset behavior would interact similarly with the |min=
parameter.
Before (no left-offset):
|
After (left-offset):
Thoughts/questions/suggestions? ~ Tom.Reding ( talk ⋅ dgaf) 15:02, 21 August 2019 (UTC)
|min=
parameter would override any left-offsets and center the current element.|min=1921
would do what you want. You'd have to hardcode it into {{
Year in Northern Ireland category}} to send |min=1921
to {{
Year in country category}} and then to {{
Navseasoncats with decades below year}} and finally to
Module:Navseasoncats/navyear. Navyear is a {{
Navseasoncats}} fork, of course, but it looks like it should handle it correctly. ~
Tom.Reding (
talk ⋅
dgaf) 16:55, 25 August 2019 (UTC)
min=1921
[3]|min={{{min|}}}
[4]|min={{{min|}}}:
[5]I have just stumbled across a series of categories created by Vegaswikian in 2015 with a nav template but no parents, e.g. Category:Buildings and structures completed in 1210.
The template is {{ 10years}} which now redirects to Navseasoncats.
Ah, 10years previously built parent categories that we have overlooked in the updating work. The parameters on the above example are:
{{10years|13th|Buildings and structures completed in|1210|Buildings and structures by year of completion}}
10years used to include the line
[[Category:{{{2}}} the {{{1}}} century]]
Parameter 4 used to be a category as well, see old doc page
For the sake of buildings & structures, I have changed {{ 10years}} for now to transclude navseasoncats instead of redirecting, followed by
[[Category:{{{2}}} the {{{1}}} century]] [[Category:{{{3}}} establishments]] [[Category:{{{4}}}|{{{3}}}]]
However, the establishments category should be replaced by more specific categories in some cases.
@ Primefac: I'm not sure if you are watching this page. For info, it was your merge that broke it. [6] – Fayenatic London 22:09, 24 September 2019 (UTC)
[[Category:{{{3}}} establishments]]
categories, so I have now built a big switch to generate appropriate parents in each case where {{
10years}} is currently used.On category pages which are not every year, but have regular intervals such as Category:Candidates in the 2016 United States presidential election, this template displays fine with every fourth year shown and linked, the intervening three years being omitted. Now consider pages like Category:Nations at the 2015 World Championships in Athletics where every year is shown, even though the IAAF World Athletics Championships have never been an annual event; the years without championships are greyed out. The championships began in 1976 but were irregular ( 1976, 1980, 1983, 1987, 1991) until 1991, since when they have been held every two years. Is it possible to configure the template to omit the years without championships, since these outnumber the years with championships? Otherwise, there are just two links in the box for the 1980, 1983 and 1987 pages. -- Redrose64 🌹 ( talk) 11:43, 9 October 2019 (UTC)
World Championships in Athletics |
---|
Nations at the World Championships in Athletics |
---|
Events at the World Championships in Athletics |
---|
|irregular-interval=on
option that searches for existing categories in each direction on-the-fly until the navbox is filled up, and defaults to an increment/decrement of 1 if none are found 10 or fewer away from each element. ~
Tom.Reding (
talk ⋅
dgaf) 14:38, 9 October 2019 (UTC)
|interval=
parameter? I noticed on one of the cats (maybe the Olympics?) that it was doing as described above (skipping years), and an |interval=4
could help with that.
Primefac (
talk) 15:31, 9 October 2019 (UTC)
|irregular-interval=on
sounds good. It could also be used for completely regular non-annual events so if |interval=
is not implemented then maybe it should just be called |non-annual=on
.
PrimeHunter (
talk) 18:55, 9 October 2019 (UTC)
|non-annual=
could be misleading, and certainly less intuitive and wrong-looking for a passer-by when used on annual event cats which at some distance away from the parent turn into every-2-year events, or skipped a year, etc., so I think |irregular-interval=
or |irregular-gap=
(to match the existing convention used in the module, documentation, and other existing parameters, but it doesn't sound as good...) would be better as the more general & informative options. ~
Tom.Reding (
talk ⋅
dgaf) 19:45, 9 October 2019 (UTC)|irregular-gaps=yes
... Anyway, will start on this in the near future. ~
Tom.Reding (
talk ⋅
dgaf) 20:08, 9 October 2019 (UTC)@
Redrose64,
PrimeHunter, and
Primefac: the sandbox now has a working mechanism for skipping non-existing cat years - you can test it via {{Navseasoncats/sandbox|skip-gaps=yes}}
to make sure everything is as-expected. If a grey year is shown, that means no cats were found 10-15 cats away (10 away, if the grey element is at the ends of the nav, and 15 away if the grey element is right next to the parent in the center of the nav). Will make live in a day or so if minimal issues. ~
Tom.Reding (
talk ⋅
dgaf) 20:25, 10 October 2019 (UTC)
Can someone add support for three-digit years or otherwise fix Category:604 in Japan? -- Numberguy6 ( talk) 03:34, 17 October 2019 (UTC)
|year=604
to the category's template call (as it's a supported parameter of {{
Year in country category}}).
Primefac (
talk) 10:37, 17 October 2019 (UTC)Thanks to Tom for taking the template on and doing all the tweaks I never quite got round to doing! <g> One thing I've noticed is that skip-gaps doesn't work on decades eg Category:Mosques completed in the 1830s. Not a biggy, but I thought I'd mention it. Le Deluge ( talk) 14:15, 20 December 2019 (UTC)
Hi Tom.Reding
I have noticed a small glitch in {{ Navseasoncats with centuries below decade}}: it works only if the century cats are named "nth century foo" or "Foo in the nth century" ... but it doesn't work if the century category title uses the adjectival form with a dash before "century", e.g. "nth-century foo".
Examples:
Please can this be fixed, if you have time? -- BrownHairedGirl (talk) • ( contribs) 14:20, 4 March 2020 (UTC)
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 |
As can be seen on Category:2008–09 I-League, the template create 2009-010 instead of 2009-10 in the navigation. Can anyone take a look? Coderzombie ( talk) 05:20, 14 July 2016 (UTC)
This template is used over such a wide range of WikiProjects, so asking here.
Le Deluge (and anyone else), what would you think of using {{
LinkCatIfExists2}} so that redcats are instead greyed out (example via {{
Category in year}}
here), either as default, or as a parameter option using |linkcatifexists2=yes
, |grey=yes
, |gray=yes
, |blueonly=yes
, or the like. ~
Tom.Reding (
talk ⋅
dgaf) 13:48, 3 October 2018 (UTC)
|min=
parameter too, but its use is/was intermittent in the taxonomy area, so it could go either way. Personally, I wouldn't choose to enforce/use a |min=
param if it were available, after seeing the alternative (this template). Decade cats are
their own can of worms, arguably the worst being that YY00 cats would be duplicated/misplaced in their parent century container cats. I'm actually in the process of ridding the taxonomy area of decade cats after a recent
RfC. Also, just because one year doesn't exist doesn't mean adjacent years are sparse - some years adjacent to reds contain ~100 pages. ~
Tom.Reding (
talk ⋅
dgaf) 14:25, 4 October 2018 (UTC)This
edit request to
Template:Navseasoncats/var firsthalf has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please remove the line <noinclude>{{pp-template|small=yes}}</noinclude>
- protection templates are automatically handled by the documentation page. Thanks, --
DannyS712 (
talk) 07:14, 22 March 2019 (UTC)
I see that |min=
& |max=
currently only work for navyear
type cats, but not navdecade
& navhyphen
cats. Is there any desire to add this functionality to either of these other category types? ~
Tom.Reding (
talk ⋅
dgaf) 20:52, 14 April 2019 (UTC)
|min=
& |max=
parameters now work for all decade cats AD/BC (but not BCE yet - are there any BCE decades?). Under the
principle of least astonishment, they behave similarly as on year & ordinal categories, while navdecade behavior was otherwise left unchanged. Behavior can be changed in the future with the modification of a few constants. This was a relatively simple (other than two 0s decades situation) transfer of the min/max code from navyear/navordinal, but doing this for navseason I think would be even trickier, so that won't be done on a whim. There's also the question of whether to adopt decade's shifting behavior for seasons, or if they're to remain centered like years & ordinals.On a millennium category such as Category:3rd millennium in Egypt, there is no point showing future millennia, and it would be better to reach back to 4th millennium BC which exists in that case. I therefore suggest that all millennia categories display the range from 4th BC to 3rd after. – Fayenatic London 10:48, 4 May 2019 (UTC)
|min=
/|max=
would be made to override these defaults, of course. ~
Tom.Reding (
talk ⋅
dgaf) 12:26, 4 May 2019 (UTC)I first need to be able to go backwards and forwards from words/numbers to numbers/words. This is currently almost completely doable:
{{
Roman|2019}}
{{#invoke:ConvertNumeric|_roman_to_numeral|MMXIX}}
{{
Ordinal to word|1}}
{{#invoke:ConvertNumeric|_english_to_ordinal|First}}
(produced as a result of this discussion)I could not easily find a word-to-ordinal utility (it's possible I glossed over it), and Template:Word to *
& Module:Word to *
don't exist (yet).
Questions to Gonnym, Fayenatic london, and everyone else:
~ Tom.Reding ( talk ⋅ dgaf) 16:58, 8 June 2019 (UTC)
numeral_to_english_less_100()
. If you go above 100 then that is just a little more process that goes into with numeral_to_english_less_100()
. --
Gonnym (
talk) 09:47, 12 June 2019 (UTC)
p.find_var
and nav_wordinal
functionality can be extended. ~
Tom.Reding (
talk ⋅
dgaf) 02:15, 14 June 2019 (UTC)
The template works for e.g. 1999–2000 but does not currently link to 1999–2004, see Category:MEPs 2004–09. – Fayenatic London 08:36, 27 May 2019 (UTC)
navhyphen
|min=
& |max=
having the same simple behavior as the other category types (i.e. no offsetting). ~
Tom.Reding (
talk ⋅
dgaf) 20:19, 8 June 2019 (UTC)
@ Wikipedia:Categories for discussion/Log/2019 May 29#Category:MEPs 1952-58, posted here separately for visibility. ~ Tom.Reding ( talk ⋅ dgaf) 22:10, 29 May 2019 (UTC)
@ Oculi, Gonnym, Philip Stevens, Lugnuts, FoxyGrampa75, and Concus Cretus: pinging everyone involved with the above CfD. Of the ~821 term-categories, 31 of them (~4%) have term lengths of exactly 1 and follow the (optional) YYYY-YY format, so they stand out a little amongst the vast majority of 2+ year terms with the unabbreviated YYYY–YYYY format. Since I can see arguments both for and against, what's the sentiment for formatting all of these YYYY–YYYY, regardless of term length? ~ Tom.Reding ( talk ⋅ dgaf) 13:01, 8 June 2019 (UTC)
Special:WhatLinksHere/Category:MEPs_for_the_Republic_of_Ireland_2009–14 shows that the updated adjacent categories Category:MEPs for the Republic of Ireland 2004–2009 and 2014–2019 are in some way linking to the otherwise obsolete redirect at the 2-digit date. Is this a minor bug in the module? – Fayenatic London 09:20, 19 June 2019 (UTC)
mw.title.new
is used to check the existence of a category, it counts as a link to that page. I've updated the gap checking routine to check the most likely name first, so a multi-year range will first check an unabbreviated multi-year adjacent range, then, if not found, check the MOS-incorrect abbreviated multi-year adjacent range. Likewise, a single-year range first check an abbreviated adjacent range, then, if not found, will check the unabbreviated range (both MOS-acceptable). This should have been updated after
MOS:DATERANGE CfDs, but was overlooked. This should lower the number of attempts, on average, needed to find the nearest existing cat, and can be optimized even more to start with whatever format the parent category is using, then, if not found, try the other one. ~
Tom.Reding (
talk ⋅
dgaf) 16:14, 20 June 2019 (UTC)
No consensus to move, after extended time for discussion. Notably, even among those who supported a move, there was no clear determination of a move target. bd2412 T 19:14, 24 June 2019 (UTC)
– This template started as a category navigation tool for football seasons, but with the recent changes this has become a multi-style navigation tool, as can be seen by the doc at Template:Navseasoncats/doc#About. The name of the template should describe what it does and "navseasonscats" does not do that. Gonnym ( talk) 10:32, 25 May 2019 (UTC) --Relisting. Steel1943 ( talk) 13:48, 4 June 2019 (UTC)
describe what it does, and any alternative which actually describes its functionality is going to be much more verbose, e.g. Template:Category navigation by year, decade or season.
the nominator si clarly unfamiliar with the v wide range of category navigation templates already in use.(sic), you'd be surprised, but I know how to read. -- Gonnym ( talk) 17:58, 25 May 2019 (UTC)
But I accept your assurance that my good faith in your ability to spot the folly of a massively ambiguous title was misplaced.and I truly hope that in real life your attitude to others is much less vain. There is nothing wrong with an ambiguous title, as can be seen by WP:PRIMARYTOPIC, in this specific case, this template does indeed fit the criteria in that it's scope is already pretty large, while the other templates have a very specific and smaller scope. As such, the name I proposed works. That being said, and as I previously said at the very start of this thread, I was never against an alternative and better proposal. And while you can argue that "seasons" means that, it really doesn't, which is why "seasons" is not a good name and neither are your CamelCase proposals per WP:TPN and general recent practice. -- Gonnym ( talk) 21:08, 25 May 2019 (UTC)
The category (and similar ones) has been moved. Could somebody please update the description. Thanks.
Currently, multi-year/hyphenated cats can search for and follow {{ Category redirect}}s. 2 questions arise:
See Category:Navseasoncats range redirected (base change) for more. ~ Tom.Reding ( talk ⋅ dgaf) 14:43, 15 June 2019 (UTC)
|follow-redirects=yes
, or|follow-redirects=no
|follow-redirects=no
allowed ~
Tom.Reding (
talk ⋅
dgaf) 15:18, 22 June 2019 (UTC)I created {{ R from category navigation}} in an effort to keep these cat #Rs from being deleted. ~ Tom.Reding ( talk ⋅ dgaf) 23:14, 28 June 2019 (UTC)
See Category:2010s in Ohio, which uses {{ Navseasoncats}} with no parameters.
But the bolded non-link for the current page is displayed to the right, instead of in the centre. Category:2000s in Ohio in Category:2020s in Ohio both display correctly, so I dunno why 2010s is wrong. Please can it be fixed?
Having the current item consistently in the centre makes the navbar much easier to use. -- BrownHairedGirl (talk) • ( contribs) 21:35, 24 August 2019 (UTC)
|max=
parameter with any number, and show greyed text up to '2060s' by using |max=2060s
, or preferably a larger # like |max=9999
. ~
Tom.Reding (
talk ⋅
dgaf) 16:35, 25 August 2019 (UTC)
-->|{{Navseasoncats/navdecade|{{Navseasoncats/var firsthalf|{{{testcase|}}}}}|{{str left|{{Navseasoncats/var season|{{{testcase|}}}}}|4}}|{{Navseasoncats/var lasthalf|{{{testcase|}}}}}|{{str left|{{CURRENTYEAR}}|3}}0}}<br/><!--
{{str left|{{CURRENTYEAR}}|3}}0
at the end, which has been there
since March 2017.
1950s • | 1960s • | 1970s • | 1980s • | 1990s • | 2000s | • 2010s | • 2020s | • 2030s |
1950s • | 1960s • | 1970s • | 1980s • | 1990s • | 2000s • | 2010s | • 2020s | • 2030s |
1950s • | 1960s • | 1970s • | 1980s • | 1990s • | 2000s • | 2010s • | 2020s | • 2030s |
1950s • | 1960s • | 1970s • | 1980s • | 1990s • | 2000s • | 2010s • | 2020s | • 2030s |
@ BrownHairedGirl: then I think the solution is a compromise where the the show-1-decade-ahead style is maintained for 2 decades beyond the current, instead of just 1. That maintains the original behavior (even moreso), and limits jumpiness.
Note that it is not a coincidence that this 1-ahead style wasn't discussed until 2019, the end of the current decade. For prior years, the old 1-ahead style presented no problems. ~ Tom.Reding ( talk ⋅ dgaf) 23:44, 25 August 2019 (UTC)
The parameter |min=
has been implemented so that blank spaces appear where earlier dates would be. The range remains centred on the "current" category.
If the range is short, i.e. both min and max are used and they are not far apart, then I support the current outcome.
However, in other cases with just |min=
, I would prefer the displayed range to shift so that it starts with the min.
This can be achieved by using the testcase parameter to determine the category at the centre of the template, but then both the testcase date and the current category date are highlighted, e.g. [2]. – Fayenatic London 08:24, 11 June 2019 (UTC)
|min=
parameter. Anything else gets more complicated (but is still doable):|max=
param provides the user with an 'escape' from this default behavior, and will force the 'current' element to always be centered.|max=
this ability would lock-in this shifting behavior, giving the user fewer options, unless a new |max=current
value is accepted.|min=
simply hides elements lower than its value.|max=
destroy a 'right offset', while |min=
produces a 'left offset'. But, the alternative would be to remove the default right-offset, and require something like |max=current
to recover it.|min=
/|max=
behaviors also kinda makes sense (I might be biased here due to the original template's behavior).|min=
& |max=
the same behavior, that is, producing the appropriate left/right offset. No offsets will occur by default, only by min/max. In cases of automatically-updated right-offsets, |max=current decade
, |max=current millenia
, etc. can be used.|min=
the ability to induce a left offset, and keep |max=
behavior as-is.I'm thinking about using a default left-offset for category types which will only have positive integer elements, like TV seasons, numeric and word ordinals, and roman numerals. This will not/should not interfere with #Should min & max shorten, or shift, the range displayed?.
Currently, the |max=
parameter overrides any default right-offsets, forcing the current element into the center. The new left-offset behavior would interact similarly with the |min=
parameter.
Before (no left-offset):
|
After (left-offset):
Thoughts/questions/suggestions? ~ Tom.Reding ( talk ⋅ dgaf) 15:02, 21 August 2019 (UTC)
|min=
parameter would override any left-offsets and center the current element.|min=1921
would do what you want. You'd have to hardcode it into {{
Year in Northern Ireland category}} to send |min=1921
to {{
Year in country category}} and then to {{
Navseasoncats with decades below year}} and finally to
Module:Navseasoncats/navyear. Navyear is a {{
Navseasoncats}} fork, of course, but it looks like it should handle it correctly. ~
Tom.Reding (
talk ⋅
dgaf) 16:55, 25 August 2019 (UTC)
min=1921
[3]|min={{{min|}}}
[4]|min={{{min|}}}:
[5]I have just stumbled across a series of categories created by Vegaswikian in 2015 with a nav template but no parents, e.g. Category:Buildings and structures completed in 1210.
The template is {{ 10years}} which now redirects to Navseasoncats.
Ah, 10years previously built parent categories that we have overlooked in the updating work. The parameters on the above example are:
{{10years|13th|Buildings and structures completed in|1210|Buildings and structures by year of completion}}
10years used to include the line
[[Category:{{{2}}} the {{{1}}} century]]
Parameter 4 used to be a category as well, see old doc page
For the sake of buildings & structures, I have changed {{ 10years}} for now to transclude navseasoncats instead of redirecting, followed by
[[Category:{{{2}}} the {{{1}}} century]] [[Category:{{{3}}} establishments]] [[Category:{{{4}}}|{{{3}}}]]
However, the establishments category should be replaced by more specific categories in some cases.
@ Primefac: I'm not sure if you are watching this page. For info, it was your merge that broke it. [6] – Fayenatic London 22:09, 24 September 2019 (UTC)
[[Category:{{{3}}} establishments]]
categories, so I have now built a big switch to generate appropriate parents in each case where {{
10years}} is currently used.On category pages which are not every year, but have regular intervals such as Category:Candidates in the 2016 United States presidential election, this template displays fine with every fourth year shown and linked, the intervening three years being omitted. Now consider pages like Category:Nations at the 2015 World Championships in Athletics where every year is shown, even though the IAAF World Athletics Championships have never been an annual event; the years without championships are greyed out. The championships began in 1976 but were irregular ( 1976, 1980, 1983, 1987, 1991) until 1991, since when they have been held every two years. Is it possible to configure the template to omit the years without championships, since these outnumber the years with championships? Otherwise, there are just two links in the box for the 1980, 1983 and 1987 pages. -- Redrose64 🌹 ( talk) 11:43, 9 October 2019 (UTC)
World Championships in Athletics |
---|
Nations at the World Championships in Athletics |
---|
Events at the World Championships in Athletics |
---|
|irregular-interval=on
option that searches for existing categories in each direction on-the-fly until the navbox is filled up, and defaults to an increment/decrement of 1 if none are found 10 or fewer away from each element. ~
Tom.Reding (
talk ⋅
dgaf) 14:38, 9 October 2019 (UTC)
|interval=
parameter? I noticed on one of the cats (maybe the Olympics?) that it was doing as described above (skipping years), and an |interval=4
could help with that.
Primefac (
talk) 15:31, 9 October 2019 (UTC)
|irregular-interval=on
sounds good. It could also be used for completely regular non-annual events so if |interval=
is not implemented then maybe it should just be called |non-annual=on
.
PrimeHunter (
talk) 18:55, 9 October 2019 (UTC)
|non-annual=
could be misleading, and certainly less intuitive and wrong-looking for a passer-by when used on annual event cats which at some distance away from the parent turn into every-2-year events, or skipped a year, etc., so I think |irregular-interval=
or |irregular-gap=
(to match the existing convention used in the module, documentation, and other existing parameters, but it doesn't sound as good...) would be better as the more general & informative options. ~
Tom.Reding (
talk ⋅
dgaf) 19:45, 9 October 2019 (UTC)|irregular-gaps=yes
... Anyway, will start on this in the near future. ~
Tom.Reding (
talk ⋅
dgaf) 20:08, 9 October 2019 (UTC)@
Redrose64,
PrimeHunter, and
Primefac: the sandbox now has a working mechanism for skipping non-existing cat years - you can test it via {{Navseasoncats/sandbox|skip-gaps=yes}}
to make sure everything is as-expected. If a grey year is shown, that means no cats were found 10-15 cats away (10 away, if the grey element is at the ends of the nav, and 15 away if the grey element is right next to the parent in the center of the nav). Will make live in a day or so if minimal issues. ~
Tom.Reding (
talk ⋅
dgaf) 20:25, 10 October 2019 (UTC)
Can someone add support for three-digit years or otherwise fix Category:604 in Japan? -- Numberguy6 ( talk) 03:34, 17 October 2019 (UTC)
|year=604
to the category's template call (as it's a supported parameter of {{
Year in country category}}).
Primefac (
talk) 10:37, 17 October 2019 (UTC)Thanks to Tom for taking the template on and doing all the tweaks I never quite got round to doing! <g> One thing I've noticed is that skip-gaps doesn't work on decades eg Category:Mosques completed in the 1830s. Not a biggy, but I thought I'd mention it. Le Deluge ( talk) 14:15, 20 December 2019 (UTC)
Hi Tom.Reding
I have noticed a small glitch in {{ Navseasoncats with centuries below decade}}: it works only if the century cats are named "nth century foo" or "Foo in the nth century" ... but it doesn't work if the century category title uses the adjectival form with a dash before "century", e.g. "nth-century foo".
Examples:
Please can this be fixed, if you have time? -- BrownHairedGirl (talk) • ( contribs) 14:20, 4 March 2020 (UTC)