Author | Message |
---|---|
◊ 2012-06-22 08:30 |
That's a 2008-2010 grille. |
◊ 2014-09-21 16:37 |
Not P473 in the least. It's P356. |
◊ 2014-09-25 07:29 |
Please correct this, as it is not P473. P356. Doing a simple search on Google shows the facelifted MY2011-16 version. |
◊ 2014-10-01 06:49 |
I already established the correct 2008-2010 Super Duty model code as P356 twice, so I'm not sure if or even why that is being dismissed, in favor of simply omitting the original incorrect P473 label. As an engineer I actually inform myself and do research on such specifics to the best of my ability. There is proof here, regarding Super Duty's built from December 2006-December 2009 as P356: http://abelconstruct.com/portfolio/ford-truck-plant/ & http://epubl.ltu.se/1402-1617/2007/023/index-en.html . If one still does not believe me, doing some further research will prove my suggestion as correct. -- Last edit: 2014-10-14 18:29:21 (DidierF) |
◊ 2014-10-01 08:29 |
(Second link is a '404 Not Found', Carmaker1.) |
◊ 2014-10-01 17:50 |
because of the "." at the end |
◊ 2014-10-13 07:40 |
I have already pointed this out and provided enough proof as to it being P356 for model years 2008-2010. That's all I can do here really in this case. |
◊ 2014-10-13 07:45 |
This site's "URL creator" chose to recognize the period at the end of the sentence, as part of the source URL. Copy-pasting the link remedies that. |
◊ 2014-10-14 18:15 |
Or just don't put a dot just after an URL (some day I'll try to improve the parsing of URLs) |
◊ 2014-10-14 18:30 |
En vertu des pouvoirs qui m'ont été conférés… fixed. |
◊ 2014-10-19 15:25 |
Tonguing? Just wow. I wouldn't be initially aware of periods invalidating URLs on this "lovely" site of yours as a user. I am not one for inaccuracy nor incompleteness, as I've provided enough evidence on this subject. It is P356 and that is that. Choosing to dismiss that fact, since I'm the source of the suggestion, only highlights hidden intentions. Signing off... |
◊ 2014-10-19 20:34 |
Well it was as a joke, since you noticed that the "." was causing the problem, you could then remove it when it directly follows an URL, it seemed more practical than copy/pasting the link -- Last edit: 2014-10-19 21:23:39 |
◊ 2022-04-16 19:54 |
2 stars |