This redirect is within the scope of the Aviation WikiProject. If you would like to participate, please visit the project page, where you can join the project and see lists of open tasks and task forces. To use this banner, please see the full instructions.AviationWikipedia:WikiProject AviationTemplate:WikiProject Aviationaviation articles
This redirect is within the scope of the Military history WikiProject. If you would like to participate, please visit the project page, where you can join the project and see a list of open tasks. To use this banner, please see the full instructions.Military historyWikipedia:WikiProject Military historyTemplate:WikiProject Military historymilitary history articles
This redirect is within the scope of WikiProject Germany, a collaborative effort to improve the coverage of Germany on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.GermanyWikipedia:WikiProject GermanyTemplate:WikiProject GermanyGermany articles
The contents of the Dornier P 256 page were merged into Dornier Do 335 on 31 January 2021 and it now redirects there. For the contribution history and old versions of the merged article please see its history.
Latest comment: 14 years ago8 comments2 people in discussion
Every single sentence doesn't need to be cited. Once per paragraph is enough if the same source is being referenced throughout. I'm a bit concerned about the copyright of this text. I couldn't find any policy where text from http://plane.spottingworld.com/ is copyright-free. Is this the case?--Sturmvogel 66 (talk) 21:52, 20 December 2009 (UTC)Reply
Since I've had {{fact}} tags attached where I've cited at the end of sentences, I tend to fn every detail, now. Overkill? Maybe. It does avoid ill-informed tagging.
If you feel more comfortable footnoting every sentence, that's your call, but at least consolidate the footnotes with a name to prevent unnecessary duplication.--Sturmvogel 66 (talk) 22:49, 20 December 2009 (UTC)Reply