XIV

Source 📝

Inconsistency with succeeding template

There is a lack of consistency between this template. And {{Ferrari road car timeline 1960-2009}}. Consider the models listed for 1968: this template lists 365 GTC, 275 GTB/4, 365 GTS and "365 GT," whereas {{Ferrari road car timeline 1960-2009}} lists 365 GTB/4 Daytona, "365GT and Dino 206." Also, is there any reason why this template ends at 1968 rather than 1969 (i.e. the end of the decade)? DH85868993 (talk) 02:44, 22 April 2008 (UTC)

Why not just have non-overlapping templates, "e."g. end this one in 1959, with the next one being the 1960's to 1990's, and the next one being the "modern" (as in "3rd millennium, plus 2000 :-)) cars? Guy Harris (talk) 06:37, 10 February 2017 (UTC)
I considered doing that more than once. But I didn't because I reckoned it would bring no benefit. Considering the "middle" template you'd basically just have to remove the 1960s, creating number of layout problems (see for example 365 GT 2+2, which straddles two decades) without any advantages since the template isn't overly wide. Or too cramped.
As for the "modern" template which I created, I decided to start in from 1996 to show the full modern V12 GT lineage (that year the Maranello replaced the 512) which I thought would be, nice and create no problems given the whole template only spans two decades. Of course if consensus/when the need arise (inevitably in a few years) it can be easily modified to start from the year 2000. Anyway the inconsistencies DH85868993 mentioned back in 2008 should be long gone by, now. —Cloverleaf II (talk) 13:13, 10 February 2017 (UTC)
No, the inconsistencies are still there: this template lists 4 models for 1968 and 1969, whereas {{Ferrari car timeline 1960s-1990s}} only lists 2. DH85868993 (talk) 22:39, 10 February 2017 (UTC)

Changed   to {{unicode| }}

The HTML character entity   does not display correctly in the Opera browser. I used {{unicode}} to workaround the problem. –droll  03:06, 29 September 2010 (UTC)

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.