Wikipedia talk:WikiProject Aviation

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Shortcuts:
STOP nuvola.svg WikiProject:Aviation exists to co-ordinate Wikipedia's aviation content. However, if you are here to ask a question or raise a concern about a particular article, it may be better directed to one of the following sub-projects:
Skip to Table of Contents Skip to Table of ContentsAdd new section
Aviation WikiProject
Articles for review




Ryanair Flight 296[edit]

Article has been blanked, now a redirect to the Ryanair Accidents and Incidents page RMS52 (talk) 12:50, 7 August 2015 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

The non-notable Ryanair Flight 296 was redirected per a decision at Wikipedia:Articles for deletion/Ryanair Flight 296 (2nd nomination) but continues to be restored by Ridland as an article, I doubt it has become notable in time so I have been changing it back to a redirect per the previous decision, any comments ? MilborneOne (talk) 16:53, 4 July 2015 (UTC)

Just to note that I have suggested to User:Ridland to take the original decisions for Ryanair Flight 296 and KLM Flight 1673 to Wikipedia:Deletion review, rather than continually restore them, thanks. MilborneOne (talk) 17:26, 4 July 2015 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

List of aircraft of X Air Force/Military table formats, especially as related to images[edit]

There is a discussion on List of aircraft of the Swiss Air Force regarding the use of images in tables listing the equipment used by various air forces. As it stands there is something of a mess with these pages - some air forces have images in the table, some alongside, some have no images at all, and some have straight lists with or without images. Some degree of uniformity should be carried out across all of these pages especially as they are likely to be compared to each other. In addition, some air forces have separate pages for current and historic, others combine them into a single page, but as separate lists, and others have them in a single table. So far the discussion has just been about the use of images.

The points I have laid out so far are thus:
  1. Many aircraft lack images or lack images for the appropriate air force leaving blanks or photos of inappropriate aircraft (wrong AF mostly).
  2. Images are of random sizes, messing up table formatting.
  3. The purpose of the table is to provide information, not be a gallery. Wikimedia is for galleries.
  4. They take up a lot of space, stretching even fairly short lists into unmanageable ones.
  5. Images in tables are too small to see properly on smaller screens such as cell phones.
  6. If someone is interested in what the aircraft looks like there is already a link to that aircraft's page.
  7. The tables that have images are almost all for current inventory, which covers a small number of types - historical listings rarely have images inline, not least because they are less likely to be the focus of nationalistic zealotry, and they have a lot more entries and would be unmanageable for even a medium sized air force. They should be consistent, and the likelihood of finding appropriate images for a majority of historical listings is low. Images should be used sparingly, and should add to the article beyond making it look pretty (which they don't) - in fact there is a wiki rule against that being the sole purpose for images.
  8. Of all the information one can put in a table, an image is a long way down the useful list - when it entered service is far more important but there is no room for that in many current tables, nor is there even room to give each entry a single line.
  9. Because other lists have them is no reason at all (another wiki rule). Many lists are not infected by useless clutter such as:
List of aircraft of the Royal Canadian Navy
List of historic aircraft of the People's Liberation Army Air Force
List of military aircraft of Japan
List of historical aircraft of the Indian Air Force
List of Regia Aeronautica aircraft used in World War II
List of aircraft of the Royal Air Force
List of military aircraft of Sweden
List of military aircraft of the Soviet Union and the CIS
List of Albanian Air Force aircraft
List of aircraft of Argentine Naval Aviation
Belize Defence Force Air Wing
List of active Brazilian military aircraft
List of aircraft of the Brazilian Navy
List of active Bulgarian military aircraft
List of former Bulgarian military aircraft
List of active People's Liberation Army aircraft
List of military aircraft of Denmark
List of active Egyptian military aircraft
List of aircraft of the Egyptian Air Force
List of military aircraft of Finland
List of aircraft of Canada's air forces

And on, and on... indeed more of these air force lists lack images than have them. NiD.29 (talk) 21:30, 5 July 2015 (UTC)

For the past several months I've been updating the tables (sourcing/ sub-headings etc) following the Aviation/Style guide/Lists and WP:IMAGEMOS (Don't overload articles with images) as per NiD.29 point and bring some uniformity to these tables - FOX 52 (talk) 23:12, 5 July 2015 (UTC)
The section on Sortable lists of aircraft types is not really suitable for national lists, as it includes a column for nationality. Some of the air force lists under discussion include additional columns, such as numbers in service, that people might want to keep. I'd suggest that we adapt the columns accordingly and add a new section to the style guide page for Lists of types in a given organisation" or similar heading. — Cheers, Steelpillow (Talk) 08:21, 6 July 2015 (UTC)

Hello all together Pictures make the chart more attractive to the reader. Images are information carriers and give the reader a first impression of the aircraft to the publically available information.For the active inventory it should be no problem to find the right picture (type& Nation), its more live in the page with a picture to every type in the list (type& Nation). As can be seen, this (pictures in the chart) is used inventory lists for other Air Force on Wikipedia.

So I am for having pictures in the inventory lists. I think in active inventory such a picture is a must have, and even by air forces (for eg.List of currently active Russian military aircraft) I see no problem. I would prefere to have the pictures in the active inventory and the one with retired aircraft. But I can see that by the historical aircraft not for any aircraft a picture can be found, so its not that important to me.FFA P-16 (talk) 20:48, 6 July 2015 (UTC) And a other "big fish" List of active United States military aircraftFFA P-16 (talk) 20:56, 6 July 2015 (UTC)

I agree with NiD.29 per his points - images in the table are unnecessary, and only clutter the page, causing formatting issues. The purpose of the table(s) is to provide information, not be a gallery. They take up a lot of space, stretching long lists into unmanageable ones. And Images in tables are too small to see properly on smaller screens such as smart phones. If someone is interested in what the aircraft looks like there is already a link to that aircraft's page - FOX 52 (talk) 21:18, 6 July 2015 (UTC)
Since were listing pages I've already overhauled 112 air force tables with 39 to go (following the basic Aviation guide/Lists with out images). I began this project back in December - FOX 52 (talk) 21:25, 6 July 2015 (UTC)
Aircraft Photo Origin Role Version Number
Comment/NOTES or whatever this box should be called
F-16 [[file:some photo.ext|100px]] USA etc etc etc
Place a all that supplementary information that makes all these tables odd looking with too much whitespace here, on a separate line below, like how episode lists handle episode summaries
Those have horrible formatting. I recommend using a two-line format, like how TV episode lists are formatted, so that the "notes" or whatever the long commentary section is called, appears as a table-wide box below the other boxes for the particular list entry. A picture can be standardized a 100px, and would not be intrusive, but, as to whether it's a good idea or not, I have no opinion. -- 67.70.32.20 (talk) 03:01, 7 July 2015 (UTC)
No that's still leading to the problem of images which will clutter the page, causing formatting issues. The purpose of the table(s) is to provide information, not be a gallery - TV episode are a little different than aircraft type list - FOX 52 (talk) 04:15, 7 July 2015 (UTC)
How about...
Name CAF
Designation
Place of
manufacture
Primary
role(s)
Service
Entry
Retired #
Used
Notes
Airbus Polaris CC-150 France transport/tanker 1992 current 5 [4][note 2]
Airco DH.4 n/a UK bomber 1920 1928 12 [5]
Active types are highlighted with an alternate colour, and there is lots of room for the full name of the aircraft. Because current use is small, it can be merged with the historical use, so those types that have been in use forever are not conspicuously absent from the historical listing which can not then be used to provide an idea of what equipment an air arm had at some particular point in time. A note can indicate if current inventory has been reduced.
No need for a version column, which again gets bloated easily, with the versions listed with the aircraft name. Versions associated with a different use (trainers for instance) can have their own entry. Instead an optional column can cover alternate designations where the particular air arm changed the designations at some point (US and RCAF for instance both changed designation systems)
Place of Manufacture is a better choice than Origin as not all aircraft are built where the design originated - for instance the Swiss historical list has to go through hoops with the Harvard II, which originated in the US but was built in Canada. Rather than the "North American (Noorduyn) Harvard IIB" it uses which isn't normal usage, it could have "North American Harvard IIB" (normal use) - with the Place of Manufacture being Canada.
Notes is for the references most of these pages lack, and it gets the supplementary notes (which often are long winded and full of trivia and cruft) out of the way and not messing up the formatting or providing distractions like how much a program cost, or what aircraft they traded where (for an example of this type of mess see the current Turkish list which needs severe trimming).
All columns MUST be sortable so the information can be put into context, which non-sortable tables with column spans cannot. The purpose of a table is to provide context. A table that can't be sorted is useless for most of the reasons anyone would put the information in a table in the first place.
CONTEXT! CONTEXT! CONTEXT! - cheers, :-) NiD.29 (talk) 05:21, 7 July 2015 (UTC)
Compare how clean and readable and useful List of aircraft of Canada's air forces is, compared with List of active aircraft of the Turkish Air Force whose format actively prevents comparisons between table entries, and whose pictures reduce the number of visible entries even on a large screen to a small number - how much is visible on a small screen? Part of one entry, maybe? Will the public come back to that page? Probably not - they will go elsewhere because they can't make sense of what it has.NiD.29 (talk) 05:27, 7 July 2015 (UTC)

Dear NiD.29, I think the List of active aircraft of the Turkish Air Force still looks good, on diffrend screens.. I have checked it out so far on 4 differend sizes of screens. i see no problem. Also I have to say that the List of aircraft of the Royal Canadian Air Force looks much more attractive to me to reading as List of aircraft of Canada's air forces ( Tow times Canada, one with pics one without).FFA P-16 (talk) 12:51, 7 July 2015 (UTC)

Tables should be void of mini images, (tables) are to provide concise information, not be a gallery, that's for Wikimedia - And a few examples other tables (no pictures needed) List of muscles of the human body, List of rulers of China, Timeline of deportations of French Jews to death camps, List of Metropolitan Statistical Areas, Cheers and Coach (TV series) and we should not be the exception, that's why we have Help:Links - FOX 52 (talk) 16:03, 7 July 2015 (UTC)

Hello Fox. yes if someone is interested in pictures he can go to wikimedia But we have the the possibility to use the pictures in many ways in wikipedia, and "a picture tells more than thousand words" Having a picture in every row of a type in this lists is far a way from beeing a gallery. We are here now discuss about Inventory chards / lists of Air Force/Military table formats. I think it is not a good idea to have one single rule for all these lists/charts/.. for all kinds of issues that exist in Wikipeda. if we already compare should be with a comparable theme, like for eg.

As a few exampels FFA P-16 (talk) 17:09, 7 July 2015 (UTC)

For the record, I'd like to say that - in my opinion - List of aircraft of the Royal Canadian Air Force is one of the clumsiest, ugliest tables in existence on Wikipedia. And you need to work on your wikilinking. GraemeLeggett (talk) 18:35, 7 July 2015 (UTC)
I dont have a strong view either way on images but as Graeme has said List of aircraft of the Royal Canadian Air Force is not the way to go, the load of text in a table cell is probably a worse thing than the image, but we do have worse at List of aircraft of the Pakistan Air Force. MilborneOne (talk) 19:34, 7 July 2015 (UTC)

Probably the reason why most tables don't have images, they take up a lot more space than needed and agree I with GraemeLeggett just "clumsiest, ugliest" looking table - FOX 52 (talk) 19:40, 7 July 2015 (UTC)

I would say by the List of aircraft of the Royal Canadian Air Force not the pictures make it to a clumsie table, i would say there is to much text in the "notes". Yes the List of aircraft of the Pakistan Air Force is ugly, but this is not because of the pictures it is in general a little chaotic and again to much text in the "Notes". I think on the other hand the List of currently active Russian military aircraft is a nice example for such a table . The pictures are good and make the list interesting and appealing as without pictures.FFA P-16 (talk) 18:07, 8 July 2015 (UTC)

Both the pictures and excessive text make it clumsy and ugly, but take away the notes and will still be clumsy and pointless - it may as well be just an article - lists (especially when made into tables) are not simply simply a cute formatting exercise - the whole point is that they facilitate the understanding of the information presented, which a table that is loaded with images and excessive text does not, and indeed cannot. A picture may tell a story of thousand words (although a picture of an aircraft almost never does), but it is not a story that belongs in the table - the table is telling a different story - of how that one aircraft relates to others used by the same organization - in numbers, dates, where it was purchased etc - the picture is a distraction from the other things we can learn - which often we can only learn from a sortable table. Can you tell me at a glance what the most numerous aircraft in the Swiss inventory has been? Without scrolling through the entire list? Or what types were merely tested rather than being widely used? One click on the clean, image-free sortable list and you have that information - information you could not easily see by scrolling through it, or even determine from the cluttered up list with the pictures. (It is the Morane-Saulnier 406 and variants btw). In addition, once images are added, the list becomes a magnet for useless trivia that doesn't belong there, as the Pakistan and Current RCAF tables clearly demonstrate.NiD.29 (talk) 18:32, 8 July 2015 (UTC)

Hello NiD29 A picture gives the reader much faster an information what general type of aircraft it is than text ( you see a 4 engine higwing T tail jet Transport AC). To understand me right i am not only for pictures iam for pictures AND of how that one aircraft relates to others used by the same organization - in numbers, dates, where it was purchased etc. "Without scrolling through the entire list? " ? If you look for some special information you have to scrol trough the list no mather if there are pictures or not. Also I have to say for me a list with pictures looks much more interesting, the pictures motivate to have a closer look at the list or a part of it. But having no pictures make a list looking (in german you say "trocken " =dry, dusty). Not every one knows how a A-50 look like so the can see it right on the list and have not to click to the pages woh decribe the aircraft type, then go back to the list and do this for every type. If we have the pictures in an aproped size and in a clear row they dont clutter up the list. As I sayd before i testet it on 4 differend screens of differend sitzes,I had no problem with the pictures, the list. And today we have the tools to crate nice lists with pictures so we should use this, for me lists without picture look also very oldfashion You have to remeber we humans taking on informations on the first priorety on the visual way, so pictures help us to get informations. FFA P-16 (talk) 19:38, 8 July 2015 (UTC)

And i find it much easyer to finde an aircaft type (for ge F/A-18, MiG-29) by his photo, than seach in a only text list for this aircraft.FFA P-16 (talk) 19:43, 8 July 2015 (UTC)

The Turkish list is horrid, due to the comments causing massive amounts of whitespace

Aircraft Origin Role something or other something or other something or other Notes
Comments
F-16 USA etc etc etc etc [a][b][c]
Place a all that supplementary information that makes all these tables odd looking with too much whitespace here, on a separate line below, like how episode lists handle episode summaries

Regardless of whether there are images in the table or not, all the tables with extended commentary per entry, should use a two-line format. -- 67.70.32.20 (talk) 06:18, 9 July 2015 (UTC)

For example, from the Turkish Air Force list, we have this horrible amount of vertical whitespace:

Aircraft Photo Origin Role Version Number Note
Lockheed Martin F-16 Fighting Falcon F-16C  USA
 Turkey
Multirole fighter F-16C
F-16D
185
57
Turkish Aerospace Industries manufactured 242 F-16C/D aircraft in Block 30 and 40. 163 Turkish F-16 have been modernised under the Common Configuration Implementation Program (CCIP) bringing them to Block 50+ configuration. TAI has commenced modernizing 30 of its F-16 Block 30 fleet with an indigenous package developed by ASELSAN as a test bed for the TAI TFX program. TuAF additionally operates 30 F-16 Block 50+ with Conformal Fuel Tanks.

But it could look like

Lockheed Martin F-16 Fighting Falcon Turkish Air Force F-16C Block 50 MOD 45157793.jpg  USA
 Turkey
Multirole fighter F-16C
F-16D
185
57
Turkish Aerospace Industries manufactured 242 F-16C/D aircraft in Block 30 and 40. 163 Turkish F-16 have been modernised under the Common Configuration Implementation Program (CCIP) bringing them to Block 50+ configuration. TAI has commenced modernizing 30 of its F-16 Block 30 fleet with an indigenous package developed by ASELSAN as a test bed for the TAI TFX program. TuAF additionally operates 30 F-16 Block 50+ with Conformal Fuel Tanks.

or without the picture

Lockheed Martin F-16 Fighting Falcon  USA
 Turkey
Multirole fighter F-16C
F-16D
185
57
Turkish Aerospace Industries manufactured 242 F-16C/D aircraft in Block 30 and 40. 163 Turkish F-16 have been modernised under the Common Configuration Implementation Program (CCIP) bringing them to Block 50+ configuration. TAI has commenced modernizing 30 of its F-16 Block 30 fleet with an indigenous package developed by ASELSAN as a test bed for the TAI TFX program. TuAF additionally operates 30 F-16 Block 50+ with Conformal Fuel Tanks.

which have much better presentation -- 67.70.32.20 (talk) 06:28, 9 July 2015 (UTC)

The issue then is the length of the comment. Table should be for pithy and to the point content. Further detail will (should be) in the aircraft of air force articles. GraemeLeggett (talk) 11:04, 9 July 2015 (UTC)
None of those are useful presentations - they all break table functionality, and are hideous to boot. Again the whole point of the table is to do something you cannot do with just text in a aparagraph - the layouts you have made may as well just be text and not be a list at all.
Name Place of
manufacture
Role(s) Service
Entry
Retired #
Used
Notes
Lockheed Martin F-16C Fighting Falcon  US/ Turkey Multirole fighter 19? n/a 185 [note 1]
Lockheed Martin F-16D Fighting Falcon  US/ Turkey Multirole fighter/trainer 19? n/a 57 [note 1]
There has yet to be a single rational argument provided to support leaving images in the table other than one person thinks they look pretty - which is a non-argument as that is already covered by wiki rules (ie no unnecessary images, and no excess images, and images should be pertinent to the page) - but lots to the contrary. An image adds nothing when there is already a link to the aircraft's page. Yet another broken format variation on the same theme is not helpful.NiD.29 (talk) 22:19, 9 July 2015 (UTC)
  • As it stands I think the debate has run it's course, and appears we should keep in place of what we currently use (image to remain out of the Table(s)) - FOX 52 (talk) 23:00, 9 July 2015 (UTC)
I think the result is that the photos have to go. The rules preclude them and I haven't seen a good reason to "ignore all rules" presented here. "It looks nice" is not a good enough reason. - Ahunt (talk) 23:20, 9 July 2015 (UTC)

The picture helps to recognize an aircraft than searching its name in the list. It is annoying if you then still have to switch between pages back and forth just turn around as certain types of aircraft at an Air Force look.Nowadays it is rather unusual that there are no pictures to support the text in a document of this kind.FFA P-16 (talk) 05:43, 10 July 2015 (UTC)

I am against images in the lists, and they also go against policy (which has been made clear enough). Although there has not been a poll or vote, I count opinions now as:
For images: 1
No preference: 2
Against images: 4
No view expressed: 1
But more significantly, the arguments against are supported by policy while the arguments for are supported only by "why I like them" statements. As it happens, this is also the majority view so we have a very clear consensus to remove images from these lists.
I am also against long screeds of text, they also are not what list tables are for. I don't think the relevant policy has been explicitly brought up yet in this thread but I am sure it can be found. Do we need to dig it out or can we call this a wrap too?
Finally, I should like to raise the issue of national flags. Certainly, our guideline on sortable lists of aircraft in general forbids them and ISTR there is longstanding wider policy and consensus that they should not be used in this kind of list. Does anybody have a problem with this?
— Cheers, Steelpillow (Talk) 19:28, 10 July 2015 (UTC)
I believe by consensus the only place we use flags is in the operator section of aircraft articles and not anywhere else. MilborneOne (talk) 20:06, 10 July 2015 (UTC)
Question regarding Origin (or Place of manufacture) I've place the original producer of a type ei; Brazilian Air Force use of the EC-725 origin France and in notes stated "licensed manufactured by Helibras" as opposed to made Brazil as the Origin - thoughts - FOX 52 (talk) 20:00, 10 July 2015 (UTC)
The origin is normally where the aircraft are built so in the case you mention it should be just Brazil. MilborneOne (talk) 20:03, 10 July 2015 (UTC)
  • (E/C) For Origin as in national origin in Infobox WP:Air has used where it was originally designed and built. For license production we're have sometimes listed both like France/Brazil if the license manufacturer partnered with the original manufacturer for the local version, such as the TAI/AgustaWestland T129. Just depends on what reasonably fits the situation. -Fnlayson (talk) 20:12, 10 July 2015 (UTC)
OK then a note should be made perhaps stating the original creator of the type? - FOX 52 (talk) 20:09, 10 July 2015 (UTC)
Listing "Place of manufacture" like in Steelpillow's last table above seems to handle things best, imo. -Fnlayson (talk) 20:17, 10 July 2015 (UTC)

For the flags I see to possible ways 1. only the flag of the orginal creator of the type. 2. Flag of the creator of the type and flag of the place it was built but wit the note Built under license. Two flags with no such note like in the example here shown with the Turkish Air Force F-16 is not so good, I would use more than one flag without the not build under license only for multinational aircraft like the Jaguar, Tornado, Eurofighter,.. And if you are against photos in the list so please treated al this air force list equal. For eg.It's weird when an Australian forcible all photos from the Swiss Air Force list deletes, but in the list on the Australian Air Force All pictures can be in the list.FFA P-16 (talk) 20:57, 10 July 2015 (UTC)

Those articles mentioned will be rectified, with image pulled from the table(s) - FOX 52 (talk) 21:43, 10 July 2015 (UTC)

I'm for the use of images. In my opinion, such edits and removal of images should be done by consensus on the article talk page. Faraz (talk) 01:16, 15 July 2015 (UTC)

Like many WikiProjects, this Project seeks to apply consistent standards across articles. The whole point of this is to avoid repeating the same old blow-by-blow arguments on every darn talk page concerned. The use of images in lists of aircraft was discussed and rejected a long time ago. Consensus has just reaffirmed that rejection. — Cheers, Steelpillow (Talk) 09:47, 15 July 2015 (UTC)
If indeed that is the case, I do not understand why do the following articles still use the image format?
https://en.wikipedia.org/wiki/List_of_active_Indian_military_aircraft
https://en.wikipedia.org/wiki/List_of_active_United_States_military_aircraft
https://en.wikipedia.org/wiki/Royal_Saudi_Air_Force
on and on...
Why are they not being edited in a similar manner? Faraz (talk) 17:22, 15 July 2015 (UTC)
They will be. Just no-one has got to them yet. I'm going to look at the Indian one now but probably won't get as far as re-arranging columns this time. GraemeLeggett (talk) 19:35, 15 July 2015 (UTC)

Images alongside the list tables[edit]

We are still seeing columns of images alongside the list tables. This is terrible, as they rely on a wide browser window. On mobile devices or if you simply narrow your desktop browser it collapses into an unusable mess. For example try narrowing your browser window while viewing List of aircraft of the Swiss Air Force. These images are not intended to align with the table rows but just stack arbitrarily downwards. IMHO they serve no sensible purpose and should be summarily deleted. Or, do folks think they are worthwhile galleries and should be found another home as per WP:GALLERY? — Cheers, Steelpillow (Talk) 16:37, 12 July 2015 (UTC)

We dont want to encourage galleries as I believe the current thinking is that the link to the relevant category on commons is all that is needed. Some representive images of current aircraft in the air force articles do not do any harm but as you say not alongside the table as is makes the mobile view hard to comprehend, not sure they are needed in the stand-alone list articles which can use the commons category. MilborneOne (talk) 17:46, 12 July 2015 (UTC)
Just link to commons in these cases to avoid a formatting mess under narrow browser settings. - Ahunt (talk) 20:30, 12 July 2015 (UTC)
One image at the start should be sufficient - galleries are prone to accretion problems and any limit on their size would be arbitrary and prone to starting arguments. At the same time the tables should have the text wrap disabled as they make tables hard to read on narrow displays.NiD.29 (talk) 20:52, 12 July 2015 (UTC)
If you have an image or two that end up next to a table, then so be it. This whole brew ha-ha was regarding having images inside the tables - FOX 52 (talk) 17:48, 20 July 2015 (UTC)
  • Yes, only images inside the tables like some of the tables shown above. -Fnlayson (talk) 18:31, 20 July 2015 (UTC)
It is now over two weeks since this sub-topic was started. As I see it we have:
For these images: 1
No preference: 0
Against these images: 4
No view expressed: 1
The "for" vote is based on a "why not?" argument. The "against" votes are based on usability, especially for Mobile. This appears to me to offer a clear consensus. — Cheers, Steelpillow (Talk) 17:12, 27 July 2015 (UTC)

Are lists in main articles different from lists with their own article?[edit]

Just to clarify: all this applies to lists included in main articles as well as pages created just for the list. — Cheers, Steelpillow (Talk) 11:53, 18 July 2015 (UTC)

No, the main articles I believe should not be included. Were going to have change every article so the work with smart phones? Granted I don't to see a massive galleries, but a few images pertaining to the subject should be ok FOX 52 (talk) 17:52, 18 July 2015 (UTC)
This whole discussion has been about lists, location unspecified, i.e. whether or not they occupy a whole article or a section in more general article. Check out the title of this thread, it says nothing about location. And there has been nothing said which generally excludes the main articles as you suggest. And anyway, I don't see how a list in a section differs in any way from a list hogging a whole article. The mobile viewing issue is exactly the same and the eye candy issues inside the table are exactly the same. And we don't want people going, "I'll keep this list in the main article so I can justify its pretties." — Cheers, Steelpillow (Talk) 18:12, 18 July 2015 (UTC)
And you specified "regarding the use of images in tables listing" we use images in articles to illustrate to the subject matter, not because it's "eye candy" - FOX 52 (talk) 18:26, 18 July 2015 (UTC)
I fail to see how this is relevant to the distinction between lists tables in articles and list tables in sections. — Cheers, Steelpillow (Talk) 19:19, 18 July 2015 (UTC)
I too had assumed the discussion was treating these inventory tables the same whether a [relatively] short section of a general article on a nation's air force or a long standalone article. It might be different though if it was just a "stack" of images alongside a bulleted list of links. How does that come across in mobile view? GraemeLeggett (talk) 19:52, 18 July 2015 (UTC)
I notice on (at least on my smart phone) is every image whether in a paragraph or next to a table is they stack up no matter what, which seems to be an issue for smarts phones in general (and that seems to be the problem for smart phones on any website) - FOX 52 (talk) 20:58, 18 July 2015 (UTC)

So far we have 2:1 that all lists should have the same rules. The argument that "we will have to change a lot more pages" is not valid - Wikipedia is here for its readers' convenience not its editors'. But I am being repeatedly reverted, so I'd like a stronger consensus one way or the other. — Cheers, Steelpillow (Talk) 09:07, 20 July 2015 (UTC)

Not really sure what the problem here is - if a list is within an article it should follow the same rules for the same reasons, however any urge to add images can readily be taken care of elsewhere in the same article.NiD.29 (talk) 17:40, 20 July 2015 (UTC)
Theses list should have the same information and appearance it doesnt matter if they are still in the main article or have been moved into a sub-article. MilborneOne (talk) 11:19, 21 July 2015 (UTC)
It is now two weeks since I asked for further comment on whether we should treat lists in sections the same as lists with their own articles. Views now stand at:
  • Treat the same: 4
  • Treat differently: 1
I think this is a clear consensus to treat them the same. — Cheers, Steelpillow (Talk) 20:52, 3 August 2015 (UTC)

Table styling[edit]

In general, there is no reason to add styling, whether CSS or HTML, to tables. It can conflict with the skin/theme selected by the visitor and in turn this can affect accessibility. MOS:TABLES says that "Deviations from standard [styling] ... should not be used gratuitously." I have seen no justification for any such custom styling on any of the lists I have seen. Has anybody else? — Cheers, Steelpillow (Talk) 12:05, 18 July 2015 (UTC)

No - and the standard wikitables adds its own styling - centering and bolding column headers and giving those cells a coloured background. The only variation I have found useful is to highlight those aircraft still in service with another colour. Neither alignment (L-R or T-B) is usually needed, especially with the images gone, nor is any other colouring needed (as some lists have every second entry using a coloured background, but that in turn makes updates more difficult, and it usually results in a mishmash with skiped spacing and missing some of the coloured bars).NiD.29 (talk) 17:46, 20 July 2015 (UTC)

It is now two weeks since this sub-topic was broken out. Wikipedia's default is no added styling without a specific usage agreed by Project consensus. One proposal, for highlighting operational types, is under discussion below. No other specific usage has been put forward here. So I think it is clear that, with the possible exception of operational types (see ongoing discussion below), our Project consensus defaults to Wikipedia's and in-table styling should not be used. — Cheers, Steelpillow (Talk) 08:49, 2 August 2015 (UTC)

Lack of involvement of other projects in discussion[edit]

I came here following recent edits to the Royal Australian Air Force article (which incidentally I have no opinion about). I was intrigued by the edit summary which stated "per Project consensus" and since I'd noticed no discussion at WP:MILHIST I assumed it must of been a WP:AVIATION initiative that was being referred to. Judging by the length of this thread I can see considerable effort has gone into attempting to develop agreement on some sort of standardization, which I accept does seem advantageous. That said I can't help but wonder why you didn't involve the regular MILHIST editors of many of these articles in the discussion, given that as near as I can tell that project was not notified of it. Of cse no one project "owns" any article and WP:AVIATION is as good a place as any to discuss this matter, but surely if you are attempting to develop consensus then all interested parties should at least be informed to give them the opportunity to participate. Anotherclown (talk) 12:21, 18 July 2015 (UTC)

I think that when this discussions started it was more about understanding and applying current consensus, not reforging it. If that seems to be changing then I guess you are right and we should be widening it. Bar the odd over-enthusiastic edit (and I don't rule myself out in that), do you think we have got to that point yet? — Cheers, Steelpillow (Talk) 19:27, 18 July 2015 (UTC)
Gday, unsure to be honest as its a very long thread (!) and I don't watchlist many air force pages (only a few that interest me and that I have some knowledge about). At any rate I can see how discussions tend to evolve over time etc and become more involved than they were originally intended to be. FWIW I posted a note at Wikipedia talk:WikiProject Military history last night in case any interested editors in that project were unaware of the discussion here (as I was) and wished to participate. All the best. Anotherclown (talk) 21:22, 18 July 2015 (UTC)
Thank you. — Cheers, Steelpillow (Talk) 14:02, 21 July 2015 (UTC)

Rows, columns and column headings[edit]

There is a fair variety of table layouts out there. I'd like to see them standardised so that when I visit a list the layout is familiar and I can quickly find what I want.

Firstly, as somebody else said it needs to be sortable. This means that all those clever subdivisions for different variants have to go: Either a variant gets its own row or it gets lumped in with the main entry. Also, long text boxes have to go, which I think has already been agreed is a good thing as they are just a sign that the text needs cutting back.

Next, here are some example sets of column headings:

Table 1. Wikipedia:WikiProject Aviation/Style guide/Lists specifies these for multinational lists in generic articles:

Type Country Date Role Status Description

Table 2. Several major nations' sites use this:

Aircraft Origin Role Version Number Notes

Table 3a. Other pages use variants of these labels and may include dates along the lines of:

Name Origin Role Variant Service entry Retired Quantity Note

Table 3b. Or, in similar vein:

Name Origin Role Variant Service period In service Comment

I think we should use the generic headings where possible. With no separate funnies for variants, this information can be included in the Type column. A single column is enough for service periods. So I'd suggest:

Table 4.

Type Origin Role Service Number Notes
Most forces are split into current and historical lists. For current craft the Service is the date of introduction, for historical craft it is the from-to dates.

Any views? — Cheers, Steelpillow (Talk) 18:43, 28 July 2015 (UTC)

Your Table 4 seems to include all that is required although the term "Service" may be confusing to some readers. MilborneOne (talk) 18:47, 28 July 2015 (UTC)
Yes, I wondered about "Service date" and "Service dates" respectively for current and historical lists. — Cheers, Steelpillow (Talk) 18:49, 28 July 2015 (UTC)
I agree on most points but I would also like to see (eventually) all the current and historic tables merged, with a retirement date set to n/a for those that are current, and a suitable highlighting to make them easy to distinguish from retired aircraft. For sortability, the dates should be in two columns. Origin is ambiguous when one country designed it, but another built it - better to choose where it was built or where it was designed, so multiple country names aren't needed - or have the country it was designed first, and where it was built in bracket afterwards. Variant info should be restricted to the broadest designation that covers all aircraft for a given role, so no block numbers and no hyphenated sub-variants so as to limit the number of entries for each type. To provide the number currently in service, the current number can follow the number used in brackets. Also all notes and references should be in the last column, aka...
Type (variant) Origin (built) Primary role Operational Retired Number used
(remaining)
References
and notes
Aircraft C-77B US (US) transport 1979 n/a 5 (4) [6]
Aircraft Mk.III UK (UK) bomber 1936 1943 70 [5][note 1]
Aircraft Mk.V UK (Canada) trainer 1942 1965 510 [5][note 2]
────────────────────────────────────────────────────────────────────────────────────────────────────
Ought to be "Number" not "#" though. To also include the right-pondian readers.GraemeLeggett (talk) 05:32, 29 July 2015 (UTC)
NP, Updated...NiD.29 (talk) 06:25, 29 July 2015 (UTC)
If the current and historic tables are merged, then I think they need to be sortable on their status rather than multi-coloured. There are also types which are neither operational nor retired, such as those currently being evaluated, or worked up to future operational status, or captured enemy types, and so on. This brings the opportunities of adding the retirement date to the status column and resolving the problem with "Service" discussed above.
On the matter of origin, having more than one country per entry makes sorting on the second nation impossible. I would suggest that the best country is that in which the airframe type was manufactured (or re-manufactured from a different type). There are many variations on manufacture, re-manufacture, modification, refit, licensing, etc. and attempting to write them all into a flexible format is not realistic. The more significant ones can be described in the Notes column and the rest left out.
I agree that variants should be kept to a minimum, using the broadest designation for the role.
For in-service types I think there should again be just one number, to make sense of sorting, and that for types in service it should be the number currently in service. Others can be left out of the list unless they are notable in some way.
On the general approach to headings, the fewer words used the broader the applicability and the less scope for argument. For example cites can just go in the Notes, there is no need to say so in the heading.
On that basis I'd like to suggest something more like:
Table 5.
Type Origin Role Adoption Status No. Notes
General Dynamics F-16 USA Multi-role 1988 Operational 24 Locally modified. 13 more now phased out.
Sukhoi SU-27 Russia Fighter 2012 Working up 7 9 more on order.
Supermarine Spitfire UK Fighter 1943 Retired 1952 197 Primarily Mks. V, VIII and XIV.
Workable? — Cheers, Steelpillow (Talk) 16:54, 30 July 2015 (UTC) [Clarifications added in italics 11:43, 31 July 2015 (UTC)]
Looking good, is it worthdoing an example table using real data just to see that it all works. MilborneOne (talk) 12:07, 31 July 2015 (UTC)
I just changed "Number" to "No." because it was wasting space. — Cheers, Steelpillow (Talk) 16:16, 31 July 2015 (UTC)
Don't like status as it is too open to random nonsense - adoption is fine, but it should be paired with withdrawn or some synonym, with either a date or n/a or current or similar. Notes should be as brief as possible and limited to information directly related to one of the columns or cruft will grow like a weed. Some indication needs to cover the difference between the number currently in service and the total that have been in service. In my above post I meant both sortable on status, and highlighted - which the table is, as n/a or current will sort ahead or behind all those with dates. Captured enemy types work best in a separate table I think as with rare exceptions they are not used operationally, and types being evaluated are either on strength with a serial from the organization in which they get included, or they are not, and their inclusion should start when the organization has taken the type onto its books - either purchased or leased. Just because France evaluated the F-15 is no reason to include that type in a listing of French Air Force types (despite carrying French markings), and finding references to every aircraft evaluated would be difficult if not impossible, and it would add confusion. For the number in service this creates a problem, in that the table then cannot show how many of the type have been used to date - this may be partly my bias toward historic listings, but the current number is rarely accurate anyway - most air forces have hangar queens that have been stripped of parts and won't ever fly again, but are still listed on the books as on strength, and it breaks the format for those smaller air forces where having two tables doesn't make any sense at all. Also the number field will probably need an {{nts|#}} tag otherwise it sorts one digit at a time, so 40 will precede 5 - your numbers only sort because the first digits are opposite to the sizes of the whole number. {{sort|value|display}} is also useful so the role column will sort in a meaningful way - for instance primary trainer, advanced trainer and operational trainer all sort separate - but by putting {{sort|trainer - advanced|Advanced trainer}} and {{sort|trainer - primary|Primary trainer}}, they will sort as a group, with all the trainers together. Also not mentioned are industry acronyms TOS and WFU (hover over text to see meaning) - too obscure maybe?
Type Origin Role Adoption Retired No. (active) Notes
Aircraft C-77B US transport 1979 n/a 5 (4) [6]
Aircraft Mk.III UK bomber 1936 1943 70 [5][note 1]
Aircraft Mk.V Canada trainer 1942 1965 510 [5][note 2]
NiD.29 (talk) 23:49, 31 July 2015 (UTC)
Sorry, I need your original table to make sense of the subsequent comments. I have restored it and moved your revised table to your associated post (there's a policy/guideline somewhere about not retrospectively changing posts without leaving a clear trail of the changes). — Cheers, Steelpillow (Talk) 12:26, 1 August 2015 (UTC)
────────────────────────────────────────────────────────────────────────────────────────────────────
The allowed content for a given column can be specified in the style guide. For example Trainer is an allowed role, but qualifiers such as Basic, Advanced, etc. are not. This should also tame any Status column, for example it could be restricted to; Working-up, Operational, Retired.
I agree about excluding types under evaluation. I am not sure it is tenable to argue that both operational and retired types must go in a common table but captured enemy types must have a separate one. Better to exclude captured types from lists unless they were used operationally, I do not see say "List of aircraft captured by the RAF in WWII" as notable, if only in a training aggressor role. The same goes for oddball types which appear in Air Force museums, such as the Avro 707 in Australia (although for an air museum, a "List of aircraft in the collection" might be appropriate). Nevertheless, significance can be attained for all kinds of oddball reason, and a "Status" column is flexible enough to allow the unpredictable. I see no reason to hard-code it out.
I am getting less and less happy about trying to accommodate the subtleties of numbering. For example do we count the number of Westland Sea Kings delivered to the RAF, the number at its operational peak, or the number officially still in operational service, or some combination of these? Hangar queens are seldom reliably sourced, they are just a distraction. And so on. To me, good cases can only be made for the number delivered to date and the number currently in service. One of these belongs in the "No." column, the other can go in the "Status" column, as in say "54 operational". This is nice for us because the No. delivered does not change when a type is withdrawn. The ordering issue is best resolved by adding data-sort-type="number" | to the column header or, in the case of mixed content, data-sort-value="number" to the individual cell.
We don't want trade acronyms. They are confusing, the templated display equally so, and we cannot rely on the client reader, especially accessibility readers, understanding how to handle the templated code.
Which all leads to:
Table 6
Type Origin Role Adoption Status Total Notes
Aircraft C-77B US transport 1979 4 in service 5 [6]
Aircraft Mk.III UK bomber 1936 Retired 1943 70 [5][note 1]
Aircraft Mk.V Canada trainer 1942 Retired 1965 510 [5][note 2]
General Dynamics F-16 USA Fighter 1988 24 in service 32 28 license-built. Remainder locally modified.
Sukhoi SU-27 Russia Multi-role 2012 Working up 7 9 more on order.
Supermarine Spitfire UK Fighter 1943 Retired 1952 197 Primarily Mks. V, VIII and XIV.
Progress? — Cheers, Steelpillow (Talk) 12:26, 1 August 2015 (UTC)
[Update] I changed the F-16 entry to illustrate some issues with local manufacture. Would there ever be a need to break out a given type into separate entries for multiple variants? Also changed "operational" to the slightly shorter and more accurate "in service". — Cheers, Steelpillow (Talk) 09:10, 2 August 2015 (UTC)
Given the change to "In service" I now think the "Working up" status should be rolled into it. Might we want an "In storage" status for types that are still on charge but have been "mothballed"? I'd prefer not, as the next thing will be the number in storage and that messes up the column sorting, but would In service or Retired come closer? — Cheers, Steelpillow (Talk) 09:26, 2 August 2015 (UTC)
The fewer different statuses the better - I see no need for "working up" as that is perfectly well covered by "In service". Likewise, stored airframes are no longer in service, until whatever time they are brought back into service (rarely) or sold off - particularly as these are nearly impossible to document, and prone to change, and endless argument that will require frequent updates to keep current.
Multiple variants are fine so long as the roles are significantly different - ie - trainers vs fighters vs (dedicated) reconnaissance. There should NOT be an entry for multiple fighter variants (for instance) unless they are so radically different as to be almost completely different aircraft (which is rare).NiD.29 (talk) 04:30, 3 August 2015 (UTC)
We currently have lists with different scope: some include only types in service, some only historical types and some include both. I see no reason to get rigid about this, I would expect that all three options will remain useful. It occurs to me that the "Status" column heading then seems a bit awkward where the only values will be respectively nos. in service or dates of retirement: I think it would be better to have "Number" or "Retired" accordingly where the list includes only one status. Does that seem reasonable? — Cheers, Steelpillow (Talk) 17:19, 4 August 2015 (UTC)
  • Yes it does, I think. -Fnlayson (talk) 17:39, 4 August 2015 (UTC)

Users reverting image/flag removals[edit]

At least 2 users have restored the image and flag removals here. One is a registered (but not a regular) user, so semi-protection won't stop them if they want to edit war. Thanks. - BilCat (talk) 02:49, 3 August 2015 (UTC)

Taking out images and flags is a HUGE mistake in my opinion. As soon as you open the article and see the images, it's much easier to understand it and read/browse through it. With out them, it's just looks plain and way too lame article.buccaneer (talk) 02:53, 3 August 2015 (UTC)

The images are a problem for viewing in smaller devices, are often inappropriate, and do not add anything significant to the list. Lists with images also tend to lose most of the functionality of the list, reducing their overall utility. If you want to know what one of the aircraft looks like, there is a link to that types pages that probably has a whole bunch of images. This has been discussed at length and all the arguments both ways covered in depth.NiD.29 (talk) 03:30, 3 August 2015 (UTC)
I would echo NiD.29's point that this has been discussed at length above and a consensus emerged to avoid images and flags in lists of aircraft. Please do not edit war, but if you feel the consensus is misplaced you are welcome to put new thoughts to us here (there is no point in you repeating what has already been said above here). If you want to build a gallery of images to browse, the WP:COMMONS is there for you. — Cheers, Steelpillow (Talk) 07:25, 3 August 2015 (UTC)

Proposed additions to WP:AVLIST[edit]

Based on the above discussions I have drafted some proposed additions to the Project style guide WP:AVLIST. The draft is currently at User:Steelpillow/Test. What it the best place to move it to for discussion/amendment/approval before merging it in, so that the associated discussion doesn't get lost? — Cheers, Steelpillow (Talk) 16:59, 13 August 2015 (UTC)

Perhaps as a sub-page of Wikipedia talk:WikiProject Aviation/Style guide. MilborneOne (talk) 17:39, 13 August 2015 (UTC)

Now moved to WP:WikiProject Aviation/Style guide/Lists/draft. Comments welcome, either here or on its talk page. — Cheers, Steelpillow (Talk) 11:23, 14 August 2015 (UTC)

Need comments for 2-month-old FL candidate[edit]

Timeline of Malaysia Airlines Flight 370 is currently the oldest Featured List candidate and at risk of the nomination being rejected for lack of comments/support. I've addressed concerns from one editor, but the FLC hasn't received much in the way of a review. Would some editors please take a few minutes to comment on its FLC page? Thanks! I'd like to turn MH370 into a good topic: Malaysia Airlines Flight 370 (GA), Timeline of Malaysia Airlines Flight 370 (current FL candidate), Analysis of Malaysia Airlines Flight 370 satellite communications (current GA nominee), Joint Agency Coordination Centre (current GA nominee), Search for Malaysia Airlines Flight 370 (75% of work done towards GA), & Malaysia Airlines Flight 370 unofficial disappearance theories (only article that needs lots of work). AHeneen (talk) 20:44, 13 July 2015 (UTC)

I'll take a look tomorrow if I get a chance. I guess the relatively controversial topic means it's turning people off... The Rambling Man (talk) 20:56, 13 July 2015 (UTC)

Accident reports from Embry Riddle site[edit]

I found a collection of accident reports at http://web.archive.org/web/*/http://avsaf.org/reports/* - Avsaf was at one time controlled by Embry Riddle Aeronautical University and this is its collection of accident reports.

I already added the Canadian ones but there may be others which aren't yet in Wikipedia articles WhisperToMe (talk) 20:50, 21 July 2015 (UTC)

Is this distinct from Embry Riddle's material which can be found here? --Colin Douglas Howell (talk) 22:53, 31 July 2015 (UTC)

Blackbushe Phenom Accident[edit]

A saudi-registered Phenom HZ-IBN has crashed today at Blackbushe Airport, England, already has an article 2015 Blackbushe Airport crash but no sign yet that it is notable. MilborneOne (talk) 16:44, 31 July 2015 (UTC)

No refs for the article so far. - Ahunt (talk) 16:49, 31 July 2015 (UTC)
I added the bbc article as a starter http://www.bbc.co.uk/news/uk-england-surrey-33736685 MilborneOne (talk) 16:53, 31 July 2015 (UTC)
I have removed an entry on the accident twice at Blackbushe Airport as we are not a news service and a provider of speculation, we still have no indication that it is notable. MilborneOne (talk) 17:19, 31 July 2015 (UTC)
I nominated it for deletion[1]....William 17:22, 31 July 2015 (UTC)
It was kept. Mjroots (talk) 06:36, 2 August 2015 (UTC)

Accessibility of lists[edit]

Many of the pages under the purview of this project use markup like:

;United Kingdom
*Bar
*RAF
**RAF Valley

which is not in accordance with our MoS & accessibility guidelines.

The markup should either be:

===United Kingdom===
*Bar
*RAF
**RAF Valley

with whatever level of subheading is appropriate) , or:

;United Kingdom
:Bar
:RAF
::RAF Valley

In addition to fixing the affected pages, are there any guidelines that need to be updated? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:11, 1 August 2015 (UTC)

Hi, thanks for pointing this out. These are just generic lists, there are no special guidelines. The semicolon format is intended for Q&A formatting (e.g. FAQs) and not for minor subheadings, so you are right, it should not be used here. I think editorial judgement needs to be made for each case whther it is better to change to the properly-headed
  ===United Kingdom===
   *Bar
   *RAF
   **RAF Valley
or to the plain
  And in the United Kingdom they include:
   *Bar
   *RAF
   **RAF Valley
For lists of aircraft types, they can - and probably should - be expanded to table format per WP:AVLIST. Note also the discussion above about lists of aircraft for individual air forces.
— Cheers, Steelpillow (Talk) 14:57, 1 August 2015 (UTC)
  • What is the specific Wikipedia policy/guidelines on this? And what are the errors or issues caused by semicolon in the list formatting? -Fnlayson (talk) 15:32, 1 August 2015 (UTC)
";" is part of a "definition list"; and WP:LISTGAP says "do not switch between list marker types". [[]] says "Do not make pseudo-headings using bold or semicolon markup. ". In both cases, these are accessibility issues, affecting people (for example whose with sight disabilities) who navigate pages by having them out loud by assistive software. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:20, 1 August 2015 (UTC)
And for where and how to use the semicolon system, see MOS:DEFLIST. See also MOS:BULLETLIST where it explains the optional use of section titles to head a bulleted list. MOS:LIST also includes the gerneral remark, "Use proper wikimarkup- or template-based list code" for bulleted lists, which by implication precludes the use of Definition List markup for them. — Cheers, Steelpillow (Talk) 18:01, 1 August 2015 (UTC)
I dont think that anybody has really paid much attention to the construction of these lists other than the recent aircraft list/table discussion. That said all we need is somebody to tell us what is best without having to read all the guff so we can help change and improve the articles, thanks. MilborneOne (talk) 19:25, 1 August 2015 (UTC)
That's kind of what I did, but then somebody asked why. Face-wink.svg — Cheers, Steelpillow (Talk) 20:25, 1 August 2015 (UTC)
  • Yea, saying something is all wrong and needs to be fixed should be explained better up front to get wide support, imo. -Fnlayson (talk) 22:53, 1 August 2015 (UTC)
Where is the consensus for removing flags from operators list as here, and delisting the list in the next edit? Flags in Operators list is a standard part of both WPAIR and MILHIST articles, and needs major discussion before wholesale changes are enacted. - BilCat (talk) 19:39, 2 August 2015 (UTC)
On the flags, I now realise that it was my bad. I had assumed something different (doesn't matter what). On the lists, it was a matter of removing the MOS:DEFLIST markup from bulleted lists as discussed here. It seemed silly to create a load of headings for lists with only one entry each, so I took the "plain text" option - also as discussed here. What do others think? — Cheers, Steelpillow (Talk)
  • I believe the consensus is only about omitting flags in Infoboxes, which I an in full agreement on. I agree on not creating excess section labels for one (or a few) entries. -Fnlayson (talk) 21:50, 2 August 2015 (UTC)

Island Air Charters[edit]

For those interested, the article Island Air Charters is under discussion at Wikipedia:Articles for deletion/Island Air Charters. YSSYguy (talk) 23:46, 1 August 2015 (UTC)

Changes to air crash infoboxes[edit]

G'day all; User:Hmdwgf has popped up in my watchlist several times today as he or she has made a fair few edits to air crash article infoboxes along the lines of this. Could we have some eyes on this person's edits please. YSSYguy (talk) 08:39, 3 August 2015 (UTC)

I have reverted a few more today and left a note on his/her talk page to come here if they want to change how the summary field is used, certainly not for listing every available factor in the accident, thanks. MilborneOne (talk) 19:48, 3 August 2015 (UTC)
Some of these descriptions are too simple, i.e. not descriptive enough. If I went overboard, I apologize, but a number of these summaries need to be changed. There has to be a simple conclusion in the description box as to why it happened. That may defeat the purpose of the article, but I still think it should be included. It can't just be something like "pilot error" or "controlled flight into terrain". I feel as though it looks incomplete and unprofessional. --Hmdwgf (talk) 20:32, 3 August 2015 (UTC)
It is only an infobox it should be simple thats the purpose, the detail should be in the article, thanks. MilborneOne (talk) 20:37, 3 August 2015 (UTC)
I don't agree. Again, the infoboxes should be simple, but some are so simple that it looks unprofessional. Also- deleting the above user's comment was an accident, he saved the page before I did, and I made a mistake in saving my comment and the page deleted his comment because it didn't exist while I was editing mine. --Hmdwgf (talk) 20:44, 3 August 2015 (UTC)
It should be something like "pilot error because of/aggravated by bad weather", not just "pilot error". --Hmdwgf (talk) 20:45, 3 August 2015 (UTC)
I think the infobox causes need to mirror the official investigation conclusions, but they also need to be brief and described on more depth in the text as required. - Ahunt (talk) 21:12, 3 August 2015 (UTC)
@Hmdwgf: - If you think that a change needs to be made, why not flag it up here for discussion. You're obviously making these edits in good faith, but consensus generally would seem to be against you. Not saying that all infoboxes are perfect. There may well be a case for altering some of them if consensus can be gained to do so. Mjroots (talk) 21:18, 3 August 2015 (UTC)
It's worth noting that infoboxes are labelled 'Quick facts' on the mobile version of Wikipedia, might help put into perspective what should be contained in them. Nimbus (Cumulus nimbus floats by) 23:07, 3 August 2015 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── As MilborneOne points out, infoboxes are just a summary of any article. Any other detail can be discussed in the corresponding sections.--Jetstreamer Talk 23:16, 3 August 2015 (UTC)

FWIW I agree with Jetstreamer and Milborne. The infoboxes are for a brief summary. Details go into the heart of the article....William 23:37, 3 August 2015 (UTC)

Disagreement over an appropriate aircraft image for an accident article.[edit]

It seems that I disagree with EditorASC over what image would be most appropriate for this article about the 1955 crash of a United Air Lines DC-6. Opinions of other project editors would be appreciated. --Colin Douglas Howell (talk) 08:30, 7 August 2015 (UTC)

What Image is it? RMS52 (talk) 12:36, 7 August 2015 (UTC)

If its a livery argument about the picture in the infobox, the livery that the plane was painted in at the time of the crash would be most suitable. RMS52 (talk) 12:39, 7 August 2015 (UTC)

I'd suggest try bringing the user here, so he/she can debate too. Also, even if another photo looks nicer. What does it have in relevant to the incident at the time? A photo of the livery at the time of the crash would be better, I agree with Colin. RMS52 (talk) 12:42, 7 August 2015 (UTC)

I think it might be better to keep the discussion on the original talk page thread; that's why I had linked to it above. --Colin Douglas Howell (talk) 17:56, 7 August 2015 (UTC)
I gave my reasons why I brought back the previous photo on that talk page, but I think they should be included here too:
I'm sorry but I have to disagree that your change in photos constitutes an improvement to this article:
a) While you claim that a livery design change was made in 1958, to all of UAL's planes, I see no citation to support that OR statement. You are aware that OR editing is against Wiki rules, aren't you?
b) When I compare the two livery designs, I cannot see much that makes them very different, in any significant way which would be relevant to the factual issues and purpose of this Wikipedia accident article. That is especially true, since the livery in your replaced photo is NOT in color, it is of a much lower resolution (FAR less pixels) AND it is a photoshoped picture that was uploaded by a Commons editor that has since been banned. We have no way of knowing how much that photo might have been altered, and in what way, from the original, un-retouched photo.
If you will check around you will find that Wikipedia generally favors color photos, AND ones with much higher resolutions, over B&W photos of lower resolution. If you could show how the very slight difference between the two liveries would change any of the important facts in this ACCIDENT article, then you might have a case for the change you made. However, this article is about that historical accident and WHY it happened. It is not an article about the history of UAL's different liveries.
While I think your edit was in good faith, I don't see that it improved the article at all, so for the reasons stated, I am going to restore the other photo. Thanks, EditorASC (talk) 03:57, 6 August 2015 (UTC)
I do not agree that a low-grade B & W photo displays a livery that the plane was "painted in at the time of the crash " The livery at the time of the crash was in COLOR, not in black and white. The difference between those two liveries, when compared in COLOR mode is rather slight and I see nothing in that difference which adds to the subject matter and issues presented in the article, namely that the crash happened and WHY it happened. EditorASC (talk) 02:21, 8 August 2015 (UTC)

Of course the livery was in colour, but the image IS NOT in colour, I suggest any replies should be made to the talk page. Thus, I am going to close this disscussion. RMS52 (talk) 07:05, 8 August 2015 (UTC)

Two 'new' articles[edit]

Hello all, an IP has converted the redirects Boeing 747-100 and Boeing 747-200 into articles by copying-and-pasting the relevant material from the Boeing 747 article. Could we keep watch on these please. YSSYguy (talk) 11:18, 9 August 2015 (UTC)

Shenyang WS-10 thrust; Fisher, 27 May 2015[edit]

In ANALYSIS: Can China break the military aircraft engine bottleneck? by Richard Fisher (27 May 2015), it states:

In early May, it was revealed that the electronically-scanned array radar-equipped J-11D had made its first flight. At the same time, there were unconfirmed reports it featured a new variant of the Taihang, with improved reliability and thrust approaching that of the AL-31F-M1; or more than 13t.

Would it be accurate to say that, according to Fisher, the thrust of the WS-10 variant described is more than 13t and less than that of the AL-31F-M1?

If so, would it be fair to say exactly that in the WS-10 article? Or would WP:NEUTRAL require the information to be phrased like "the variant reportedly had improved reliability, and a thrust approaching the AL-31FM1" (avoiding the word "less", etc.)? - RovingPersonalityConstruct (talk, contribs) 04:46, 10 August 2015 (UTC)

Talk:US Airways Flight 1549[edit]

We could use some experienced eyes, especially in dealing with aircraft incidents, at Talk:US Airways Flight 1549#Too much unrevealing content about the aircraft. The issue should be self-explanatory. Thanks. - BilCat (talk) 07:05, 12 August 2015 (UTC)

MH370 images being translated into Chinese[edit]

Many maps related to Malaysia Airlines Flight 370 are being translated into Chinese. User:Cerevisae is doing an excellent job preparing the translations for these maps. He, along with User:李4, User:CFSO6459, and User:Antigng also translated the commons image gallery: Commons:Malaysia Airlines Flight 370. (Cerevisae also added Malay translations for the gallery) - They are all helping our Mainland Chinese friends better understand the MH370 accident.

In the future when accidents and incidents happen we can help ensure Wikimedia content is translated into the relevant local languages. It may mean outreach to other Wikipedias or other persons. WhisperToMe (talk) 01:40, 13 August 2015 (UTC)

Draft additions to WP:AVLIST[edit]

You are invited to comment on Wikipedia:WikiProject Aviation/Style guide/Lists/draft. — Cheers, Steelpillow (Talk) 11:33, 14 August 2015 (UTC)

Now merged in. I did a fair amount of jiggling and copyediting, so more eyes are welcome. — Cheers, Steelpillow (Talk)

Trigana Air ATR72 missing[edit]

Just for information at the moment "Indonesian plane missing over Papua region" http://www.bbc.co.uk/news/world-asia-33951718 MilborneOne (talk) 10:17, 16 August 2015 (UTC)

Trigana Air Service Flight 267 has appeared. MilborneOne (talk) 11:35, 16 August 2015 (UTC)

Scott Cody Gallego[edit]

  • Edit wars are never OK (removing vandalism is not edit warring, btw). I see no real edit warring there, except some back & forth edits over the categories. -Fnlayson (talk) 12:49, 17 August 2015 (UTC)
Bullshit indicator has been set off, doesnt appear particularly notable or realistic, reads like something the subject would write, are we sure its not a hoax or at least self-promotion. The creater has not made any other contributions, and the subject doesnt actually appear in any of the references. MilborneOne (talk) 16:17, 17 August 2015 (UTC)

Belfast International Airport[edit]

I have started a discussion re the inclusion of a non-aviation incident in the Belfast International airport article. Comments welcome at talk:Belfast International Airport#The bomb. Mjroots (talk) 15:35, 19 August 2015 (UTC)

Note that their is a disscussion at WT:AIRPORTS regarding this. RMS52 (talk) 09:00, 21 August 2015 (UTC)

Egyptian Air Force[edit]

My cleanup of the list tables at Egyptian Air Force is being reverted. help wanted. — Cheers, Steelpillow (Talk) 08:23, 22 August 2015 (UTC)

With all due respect, The list looks better with images in the table. The reason for the appearance of vertical whitespace is because of the large amount of information present in the "Comment" column. The vertical whitespace and table styling aren't actually a big deal. And what consensus? and by whom? did you vote for it? I see no consensus, All I see are personal decisions. The way Information is shown is different from one page to another, Every page is free to show its information in the way it likes. You are allowed to remove these images only if a license to distribute is not found. I here request not to change the way the information is shown in The Egyptian Air Force page. Cheers, AHMED XIV
The addition of flags to the tables is contrary to MOS guidance, and there is clear consensus above that the photos are not an improvement to lists of aircraft. In addition, most of the photos that are being edit-warred into the article are not of Egyptian Air Force aircraft, and don't belong, while you also appear to be adding significant unsourced text to the tables.Nigel Ish (talk) 11:52, 22 August 2015 (UTC)
Please, provide a link to the MOS guidance, and don't talk about a consensus unless you make a voting for it. I can make a page saying that it is important to add images in tables, In the end these are just personal decisions. the photos that are being edit-warred into the article are not of Egyptian Air Force aircraft, and we never said they belonged to the Egyptian Air Force. The purpose of the image is just to show the shape of the aircraft to the people , There are some unsourced text to the tables, but these are old ones that need citations, and we are working hard on providing them. Any recent information added to the page is added with a source, and we make sure that no information is added without a reliable source.AHMED XIV 12:52, 22 August 2015 (UTC)
Wikipedia:Manual_of_Style/Icons#Inappropriate_use. The use of flags is these tables is purely decorative.Nigel Ish (talk) 12:56, 22 August 2015 (UTC)
MOS guidance may be found by following the appropriate links from WP:MOS. Additional Project guidance may be found by following the appropriate links from Wikipedia:WikiProject Aviation/Style guide. These are supplemented by recent consensus on this talk page, between the majority of experienced and responsible participants who have as you can see offered views based on Wikipedia's policy and guidelines, along with further considered views on issues local to aviation topics. That's what consensus is, you don't need a vote unless informal discussion such as this has broken down. Simple "I don't like it" or "I want to be different" comments are not acceptable alternatives to such a consensus. If you want lots of images for other reasons, you can find out more at WP:GALLERY. Meanwhile, I must warn you that your continued disruptive reversion of multiple editors constitutes an WP:EDITWAR and you may face sanctions if you do not stop. — Cheers, Steelpillow (Talk) 12:59, 22 August 2015 (UTC)
According to the "Encyclopedic purpose" found in the Wikipedia:Manual_of_Style/Icons#Inappropriate_use page, Icons should serve an encyclopaedic purpose and not merely be decorative. The images that we provide are not to be decorative but are information carriers that give the reader a first impression of the aircraft to the publically available information. You must believe that this isn't an "I don't like it" issue, All editors for the Egyptian Air Force agree on this. Your continued change to the article must be stopped. AHMED XIV 13:23, 22 August 2015 (UTC)
  • The flag is redundant with the nation listed & linked next to it. That makes the use of flag icons decorative there. -Fnlayson (talk) 14:02, 22 August 2015 (UTC)
  • You are right about the flags Fnlayson, but we are talking about the images of each aircraft. They are definitely important. -AHMED XIV 02:25, 22 August 2015 (UTC)
This has all been hashed over before - images are NOT important as there is already a link to a page which has images of the aircraft, and serve to do little more than clutter the list, not to mention they tend to result in broken lists that cannot use most of the functionality of the list format - might as well not have the information in a list at all. Many of the images aren't even from the Air Force that they are supposed to be illustrating.NiD.29 16:20, 22 August 2015 (UTC)

Hawker Hunter crash at Shoreham[edit]

A Hawker Hunter crashed today at Shoreham, West Sussex. Initial reports are of "several killed" although the pilot is not amongst the casualties. Suggest we hang fire on an article for the moment, but 2015 Shoreham Hawker Hunter crash would be a suitable title for such an article. Mjroots (talk) 15:25, 22 August 2015 (UTC)

BBC reporting seven fatalities, one seriously injured. As the deadliest airshow accident in the UK for decades, this has just been pushed firmly up the notability ladder. Mjroots (talk) 15:55, 22 August 2015 (UTC)
Not sure the current title "disaster" is appropriate, sad but nobody in the press has used the term, perhaps move it to Mjroots suggestion. I was there yesterday watching aircraft arrive! MilborneOne (talk) 16:28, 22 August 2015 (UTC)
Move it. No-one seems to be naming it as a "disaster". Watching BBC news right now, they call it a "crash" GraemeLeggett (talk) 20:14, 22 August 2015 (UTC)
There's a serious talkpage move discussion going on there, which is better placed than here. The Rambling Man (talk) 20:18, 22 August 2015 (UTC)

User:FOX 52[edit]

FOX 52 (talk · contribs) is still applying styling and flag icons to lists of aircraft, despite having been involved in the consensus-building discussion above. See for example here. Please can folks keep an eye on this. — Cheers, Steelpillow (Talk) 17:34, 22 August 2015 (UTC)

Let me point out that I stated early on in this debate that I had already started a massive overhaul of all air force aircraft lists. I began this endeavor back in December 2014, putting in several hundred hours work and have (currently) revamped 122 articles following this format, and basically had no opposition (expect having images removed from the tables – which started this whole brew ha-ha). And even had input from others 1 2, with no complaints on style. - So the real question, is that format so bad that my work must be reverted? FOX 52 (talk) 19:54, 22 August 2015 (UTC)
The consensus in the relevant discussion above says, yes it really is that bad. If you want to impose your personal style on dozens of Wikipedia articles, it might prove wiser in future to obtain consensus before doing so. — Cheers, Steelpillow (Talk) 21:19, 22 August 2015 (UTC)
FYI this was what I went off of, so it's not my "personal style" that is being imposed. Hopefully some kind of compromise can be reached -Cheers FOX 52 (talk) 22:34, 22 August 2015 (UTC)
Perhaps you mean this edit? YSSYguy (talk) 06:14, 23 August 2015 (UTC)
The edit link appears scrambled. But what compromise do you propose, that does not overturn a consensus already discussed and agreed on? — Cheers, Steelpillow (Talk) 08:45, 23 August 2015 (UTC)
Obviously anything I propose will go counter to your discussion, since I began this project months before your debate. Having invested time in these lists, and bit more to lose, than some (overhauled 122 pages, over a 9 month period). I’d suggest the easiest and fairest fix, would be to remove the color styling, but keep the flag icons, as they give the reader quick ID of the origin and does NOT go against WP:MOSFLAG guidelines. Furthermore it would be a painstaking task, and I’d like to see some of work, wasn't for nothing. - FOX 52 (talk) 18:34, 24 August 2015 (UTC)
Sorry, no. To quote from MOS:FLAGS; "In lists or tables, flag icons may be relevant when such representation of different subjects is pertinent to the purpose of the list or table itself." In a list of aircraft types belonging to a given organisation, the flags are not pertinent to the purpose of the list. This is made abundantly clear in the section on Inappropriate use, where the very first subsection is Do not emphasize nationality without good reason. You have continued making these edits after participating in the main discussion and even while claiming that they conform to this Project's consensus or that they conform to MOS:FLAGS. Both claims are manifestly false and on occasion have led another editor into bad edits (e.g. see here). I have no more time for this mess of untruths and disruption. — Cheers, Steelpillow (Talk) 19:04, 24 August 2015 (UTC)
No my involvement was only pertaining to the images inside the table nothing more beyond that. And leaving the flag icon's is not a some silly nationalistic tactic for a table and doesn't refer to an organization only the origin (country). - FOX 52 (talk) 20:04, 24 August 2015 (UTC)
None of which - even if credited as more than spin and half-truth - is relevant to MOS:FLAG or to the consensus agreed above. — Cheers, Steelpillow (Talk) 20:24, 24 August 2015 (UTC)
I don't see the logic in wanting the removal the icons, except it seems to be a personal preference and your so-called consensus appears to have omitted these opinions [3] [4]. WP:MOSFLAG leaves the door open to either rout. It's one thing if it's a tech issue, but another if it's a "I just don't like it" deal. Finally my nine months of work on these articles are more than just "untruths and disruption" - FOX 52 (talk) 21:45, 26 August 2015 (UTC)
The following reasons mitigate against using icons:
  1. they take up space better used for information, as laid out in the format agreed upon here.
  2. they cause columns to wrap, which makes the table look ugly and inconsistent. It is worse if the table is viewed on a cell phone.
  3. they massively increase load times as each flag's template gets loaded - this is a problem for people on slow connections.
  4. they do not add additional info. The name of the country is there. The flag is nothing but decoration.
  5. how long you've been working on lists is irrelevant - I have been working on lists far longer, and others longer still. We are not talking content, but formatting. I used to like flags, but the problems they cause are not worth it.
  6. Wikipedia works by consensus - not by fiat, not by people going their own way, but by working together, and deciding to ignore an agreed upon formatting standard because you don't like it is behaviour that is likely to get you banned.NiD.29 03:14, 27 August 2015 (UTC)
  1. Takes up space? 3 letter spaces, is not gonna break the bank
  2. Massively increase load times, doubtful in the age of high speed internet
  3. Viewed on my phone and desk top looks fine, so not sure what issue you having there.
  4. At a glance the flagicon is a way better visual cue than the text for quick reference
  5. The concerted effort I've made trying to bring conformity to these lists (updating numbers, wikilinking variants & adding pertinent info) is very relevant.
You might have a different tune, if you had work on one specific project over the past year, achieving 80% of the goal only to find out it needs to be changed. Were working together? After trying to make a suggestion, the response I got started with "Sorry, no" - WP:TALKEDABOUTIT - FOX 52 (talk) 05:09, 27 August 2015 (UTC)
The claim that MOS:FLAGS allows such usage is false. Nothing could be clearer. Allow me to draw it to your attention once more to the section on Inappropriate use and specifically the subsection on Do not emphasize nationality without good reason:

'Flags are visually striking, and placing a national flag next to something can make its nationality or location seem to be of greater significance than other things. For example, with an English flag next to him, Paul McCartney looks like an "English singer-songwriter from Liverpool who was in the Beatles"; without the flag next to him, he looks like an "English singer-songwriter from Liverpool who was in the Beatles". Emphasizing the importance of a person's citizenship or nationality above their other qualities risks violating Wikipedia's "Neutral point of view" policy.'

We are identifying the country that built the plane, we are not identfying the country that built the plane. It really is that plain and unarguable, there is absolutely no wriggle room for you, so will you please stop pushing untruths about WP:MOS. — Cheers, Steelpillow (Talk) 07:02, 27 August 2015 (UTC)
@Steelpillow: "Focus on improvements, not rules" WP:NOTFATRAT I think it helped, but you seem to have your personal preference so I'll let it be - FOX 52 (talk) 17:38, 27 August 2015 (UTC)
Didn't we just settle this issue? And as long as Steel isn't asking Fox to undo Fox's own work, why cry about all the hard work being undone? If all that's being removed is the flags, what's the big deal? - BilCat (talk) 07:38, 27 August 2015 (UTC)
Bill your right, I just fear in 6 months from now these sections may still be in disarray, (sometimes editors lose interest, etc..with no follow through) so in the end I will probably be undoing my own work to please the community - FOX 52 (talk) 17:14, 27 August 2015 (UTC)
Fox, I appreciate the work that you do on WP, especially in fighting trivial additions to Operators sections, which is something I also worm on, so I notice it. I think we've all had times when we worked on something that later turned out to be unwanted, but perhaps not to the degree of your case with the aircraft lists. As a whole, WPAIR and WPAVIATION has been facing opposition from certain guideline-wonk factions, such as the one that lead to the deletion of the {{aviation lists}} navbox, that try to undo much of the work the project has done in standardization of aircraft and aviation articles. So we're familiar with what you're going through now. There clearly isn't a consensus for using country flags in the lists, but honestly, it's not that difficult to remove them. As to the rest of your style changes to the lists, I haven't looked at them in detail to see which is better, but to be honest, I don't work well with list tables, so I don't usually edit them at all. But if you honestly believe your style has merits, then make a case for it, minus the flags of course. But I don't see that harping on the fact that all your work is being undone will help your case at this point. - BilCat (talk) 17:41, 27 August 2015 (UTC)
@BilCat: Thanks I very much appreciate encouragement - just want the user experience on WP to be the best it can be (as am sure we all do) - Cheers FOX 52 (talk) 17:52, 27 August 2015 (UTC)
  1. Takes up space? 3 letter spaces, is not gonna break the bank - it is often more than three spaces due to the way the country name is presented, which requires a lot of extra text to change.
  2. Massively increase load times, doubtful in the age of high speed internet - not everyone has high speed internet, and not everyone has it all the time. Every flag that is included requires the full data from that template to be loaded. On a list with dozens of different flags, this can triple the page size easily, and for larger pages, this can be a problem. Before I completely revamped it, List of fighter aircraft used to have flags, but their removal not only provided more space for things like the full aircraft name, it also reduced load times dramatically, even on a high speed connection. While it won't change much for some piddly little lists, consistency demands we go with what works for all the lists.
  3. Viewed on my phone and desk top looks fine, so not sure what issue you having there. - according to your ideas as to what looks good - others have different opinions, and since it is nothing more than useless beautification, it is against
  4. At a glance the flagicon is a way better visual cue than the text for quick reference - it isn't required - that is why there is a sort option - so you can sort all the aircraft from one country together. Unless someone has gone and broken it with crossbars and photos and excessive notes.
  5. The concerted effort I've made trying to bring conformity to these lists (updating numbers, wikilinking variants & adding pertinent info) is very relevant. - and you think you are the only one who has done so? Or continues to do so? The reason there was a discussion here was about the need for a consistent format, and one was decided upon. Which you then chose to ignore.NiD.29 19:52, 27 August 2015 (UTC)

"Aircraft accidents and incidents" cats...[edit]

This seems overly broad to me, as it includes in 2011, for example, commercial accidents, commercial incidents, military accidents, and military shootdowns. Now, the alternative is really small categories (especially for the military side), but being shot down is not the same as an accidental crash, or a part falling off. The category title leads one to think commercial side anyway. Has this come up for discussion previously? MSJapan (talk) 05:02, 25 August 2015 (UTC)

It is meant to be broad to include everything in the year, other categories deal with causes and the type of aircraft so breaking it down further will probably just make it useless as a finding aid. MilborneOne (talk) 11:00, 25 August 2015 (UTC)
Basically per MilborneOne, but noting that the "Maritime incidents in (year)" and "Railway accidents in (year)" categories are similarly broad in their coverage. No need to change these IMHO. Mjroots (talk) 12:28, 25 August 2015 (UTC)

Orbital airship[edit]

The orbital airship article looks to me like a single commercial company pushing an impossible scam. I have started a discussion on its talk page at Is this for real?. Contributions gratefully received. — Cheers, Steelpillow (Talk) 12:54, 25 August 2015 (UTC)

I PRODded it. — Cheers, Steelpillow (Talk) 16:52, 27 August 2015 (UTC)
you WHAT? Jan olieslagers (talk) 17:07, 27 August 2015 (UTC)
WP:PROD. Remove the template if you disagree. — Cheers, Steelpillow (Talk) 17:44, 27 August 2015 (UTC)
Not disagreeing, not at all - merely wondering. Unexplained/non-documented acronyms go down badly, here. All clear now, thanks. Jan olieslagers (talk) 19:20, 27 August 2015 (UTC)
You're right, I should have linked first time round. My bad. Sorry. — Cheers, Steelpillow (Talk) 19:49, 27 August 2015 (UTC)

Wiki Books[edit]

Wikipedia:Book says you can compile selected articles into a book for either online reading as a pdf or even to buy a printed copy. So I had a play and came up with a draft on Aircraft wing configurations.

It is making me think more about the presentation of articles: overuse of bulleted lists soon gets tedious while tables tend to disappear altogether, and it gets very obvious who has been adding either too few or too many images. Closer inspection reveals how tedious it is to read the same thing several times over in different articles, I think that is an important lesson.

As example I have started tinkering in Category:Wing configurations space to see where this leads. Please feel free to download a copy: A4 and Letter formats are available. It will feed you the current version of each article, so it can take a minute or so to build the file. — Cheers, Steelpillow (Talk) 18:15, 25 August 2015 (UTC)

I wonder whether we should try to design our articles more with such books in mind. Please share any thoughts. — Cheers, Steelpillow (Talk) 18:17, 25 August 2015 (UTC)

Although the primary viewing is the webpage it would do no harm to have a list of good practices that improves the printed experience. MilborneOne (talk) 18:19, 25 August 2015 (UTC)
Interesting idea; there is a book on sale here in Australia about aircraft disappearances, published in the wake of MH370 but with many lesser-known disappearances in its pages. It is clearly based on Wikpedia articles. I have also seen an article in an Australian aviation magazine about the history of Piper Aircraft, lifted from the WP article almost verbatim - without attribution of course. Someone is making money from the work of WP editors. YSSYguy (talk) 22:31, 25 August 2015 (UTC)
I have seen a few around too. The book the system built for me has pages and pages of attributions at the end, presumably to conform with its Creative Commons license. If you told the Wiki foundation about the offending magazine article they might well set their legal team on it. — Cheers, Steelpillow (Talk) 09:47, 26 August 2015 (UTC)

Aircraft roles in lists[edit]

I think the list of roles in WP:AVLIST could do with an overhaul. I have started a discussion at Wikipedia_talk:WikiProject_Aviation/Style_guide/Lists#Roles. All comments welcome. — Cheers, Steelpillow (Talk) 10:59, 27 August 2015 (UTC)