Template talk:Year nav

Years below 101

What about years BC? And what about the 1st century? Check those out and fix them, please! /Ludde23 ^{Talk Contrib} 14:38, 6 December 2006 (UTC)[reply]

02-Feb-2007: I have developed a new nav-box for 1st century (only): it is fairly complex and called "Template:Year nav 1st century CE" which can handle years 1-100 (and show years BC), such as for year "2":

The calculations are so complex that the template is dangerous to maintain, and is being purposely limited to years 1-100. An even more complex template could be created to handle any year, but perhaps, only 1 person in 1000 could understand the multiple nested calculations, making such an any-year template very dangerous to maintain. Wikitables do not yet use typical computer-language syntax, so an any-year template might use "#ifeq" nesting calculations to handle any specified year; however, even experienced computer programmers would see such a template as too arcane and obtuse to easily modify. Rule of programming: "If no one else could modify it, avoid writing it" (rule of thumb). I plan to create some less complex templates to handle only years BC. Later. -Wikid77 14:09, 2 February 2007 (UTC)[reply]

More centuries

01-February-2007: Perhaps the centuries listed were limited to a choice of 3 due to width-limitations; however, more century numbers could be displayed by dropping "century" from other choices, such as showing "18th" rather than "18th century" (omit "century" outside the center). -Wikid77 14:23, 1 February 2007 (UTC)[reply]

Narrowed

01-February-2007: The navigation template "Template:Year nav" had been too wide for commonplace 800x600 screens, when displayed in the yearly articles 1500-1999, so I narrowed the nav-box by using small-font for the choice of decades. Just a small narrowing allowed left-side text to format as 6-7 words per line, enough to avoid the peculiar appearance of 5 words-per-line wrapping which often produced very ragged lines because most words are 6-7 letters wide. -Wikid77 14:25, 1 February 2007 (UTC)[reply]

Political World Map

Can there be a political world map for each year embedded into the year nav? It benefit the study of temporal politics. Possible difficulties I know of:

African nations changes frequently in last century and annual map may not have sufficient granulity to reflect that
Disputed territories between peace treaties

3Laws 23:53, 7 April 2007 (UTC)[reply]

Current year

I've added some code that will automatically put {{Current-year}} on the current year page. --Philip Stevens 06:35, 23 June 2007 (UTC)[reply]

Year nav range

{{editprotected}} Please copy the code from {{Year nav range}} into the template, there is no need to have two templates that do the same thing. --Philip Stevens 06:06, 27 June 2007 (UTC)[reply]

Are you really asking to have one of these templates deleted or redirect to the other? If so, perhaps you should list this at WP:TFD. If you want help with that, or can't do a portion of the nomination due to the protection, let me know and I'll try to do the parts that you have trouble with. --After Midnight ⁰⁰⁰¹ 17:27, 27 June 2007 (UTC)[reply]

I'll do that thanks. --Philip Stevens 21:17, 27 June 2007 (UTC)[reply]

Since the other template has been nominated, I've disabled this edit protect. If anything else needs to be done here, feel free to leave a message on my talk page or After Midnight's. - auburnpilot talk 23:00, 27 June 2007 (UTC)[reply]

Protected erroneous change

{{editprotected}}
30-June-2007: That Template:Year_nav was hacked live, without full testing, and erroneous changes got protect-locked into the template on 23-June-2007.

The error message: "Unrecognised parameter 'year' " is caused by checking the keyword "PAGENAME" instead of "{{{1|888}}}" so the fix is to replace the top 2 if-statements with the following 2 code lines:

-->{{#ifeq:{{{1|888}}}|{{CURRENTYEAR}}|{{Current-year}}}}
-->{{#ifexpr:{{{1|888}}}>{{CURRENTYEAR}}|{{future}}}}

That fix replaces PAGENAME with parameter 1: "{{{1|888}}}" (note the triple-braces "{{{_}}}").

I have fixed the related "Template:Year_nav_range" which is intended for experimental changes, because it is used in only a handful of years, while "Template:Year_nav" is used by hundreds of WP articles (intended for thousands). Thanks. -Wikid77 11:23, 30 June 2007 (UTC)[reply]

Done. By the way, the code above would have broken the template; you forgot to use a new <!-- . Cheers. --MZMcBride 14:43, 30 June 2007 (UTC)[reply]

Thanks, it tested OK. Glad you caught the unopened comment; these primitive computer languages are still a syntactical nightmare: there was a joke many moons ago that proposed using a comment token "$##%%&@$$" to gig the ad-nauseum language tokens. Wow, it's way into the 21 century now, and much software is still uncommented to avoid runaway comment tokens: "what's new is old [tech] again." -Wikid77 03:33, 1 July 2007 (UTC)[reply]

Remove {{future}} tag

{{editprotected}}

The {{future}} tag should be removed from this template. It looks rather silly to inform readers that things may change as the year 2054 approaches. See also discussions on WP:CAFET and {{future}}. --Kildor (talk) 07:01, 28 March 2008 (UTC)[reply]

No comments or objections have been made to this proposal after almost a week. So I request the following change to this template:

Replace the following two rows (row 4 and 5 in the template):

 -->{{#ifexpr:{{{1|888}}}>{{CURRENTYEAR}}|{{future}}}}
  {| class="infobox" style="text-align: center;"

...with the following row:

 -->{| class="infobox" style="text-align: center;"

Thanks. --Kildor (talk) 14:08, 3 April 2008 (UTC)[reply]

Done Happy‑melon 15:46, 5 April 2008 (UTC)[reply]

Decade links

The decades denoted nn00s have been moved to nn00–nn09. We need to change the template accordingly, possibly using {{DecadeLink}}. (This might break the spacing, though, so I hesitate to ask for a specific change at this time.) {{year nav 1st century CE}} also needs to be changed, and {{year nav BC}} will need to be changed. — Arthur Rubin (talk) 02:02, 3 October 2008 (UTC)[reply]

I propose changing the section <code> :--> [[{{#expr: ({{{1|888}}} - ({{{1|888}}} mod 10)) - 30}}s]]  [[{{#expr: ({{{1|888}}} - ({{{1|888}}} mod 10)) - 20}}s]]  [[{{#expr: ({{{1|888}}} - ({{{1|888}}} mod 10)) - 10}}s]]  - [[{{#expr: ({{{1|888}}} - ({{{1|888}}} mod 10))}}s]] - [[{{#expr: ({{{1|888}}} - ({{{1|888}}} mod 10)) + 10}}s]] [[{{#expr: ({{{1|888}}} - ({{{1|888}}} mod 10)) + 20}}s]] [[{{#expr: ({{{1|888}}} - ({{{1|888}}} mod 10)) + 30}}s]] </code>

by

<code> :--> {{DecadeLink|{{#expr: (({{{1|888}}} - ({{{1|888}}} mod 10)) - 30)/10}}}}  {{DecadeLink|{{#expr: (({{{1|888}}} - ({{{1|888}}} mod 10)) - 20)/10}}}}  {{DecadeLink|{{#expr: (({{{1|888}}} - ({{{1|888}}} mod 10)) - 10)/10}}}}  - {{DecadeLink|{{#expr: (({{{1|888}}} - ({{{1|888}}} mod 10)))/10}}}} - {{DecadeLink|{{#expr: (({{{1|888}}} - ({{{1|888}}} mod 10)) + 10)/10}}}} {{DecadeLink|{{#expr: (({{{1|888}}} - ({{{1|888}}} mod 10)) + 20)/10}}}} {{DecadeLink|{{#expr: (({{{1|888}}} - ({{{1|888}}} mod 10)) + 30)/10}}}} </code>

(That's a literal substitution; the expressions could probably be simplified.) — Arthur Rubin (talk) 02:09, 3 October 2008 (UTC)[reply]