text:
Wikipedia talk:Historical archive/Template:Substub

 This Template talk page is presently inactive and kept primarily for historical interest. If you want to revive discussion regarding the subject, you may try starting a discussion at the Village pump.

Introduction to substubs
I created this type of stub because I saw a reference to it on Find or fix a stub and thought that it needed to become official. Mike Storm 02:37, 21 Jul 2004 (UTC)

I don't think that this should include deletion in the message. If they qualify for deletion, the speedy deletion tag seems more appropriate. This seems to be for things which could be deletable but which are about topics which merit expansion rather than deletion. Jamesday 11:32, 23 Jul 2004 (UTC)

The message about the "quality of information" in Wikipedia was added because someone brought up a very good point in Wikipedia talk:substub about how people who found a substub with a search engine (very likely) would see unworthwhile information and therefore form a bad opinion of Wikipedia. Please don't let this turn into an edit war.Mike Storm (Talk) 14:47, 29 Jul 2004 (UTC)

 * Your threat of edit war is an inappropriate first step in a dispute over wording. If you are going to put official sounding notices on pages, you should achieve consensus on their wording and necessity. If necessary, we can put up a request for comments. I ask you to consider the response of a contributor, new to Wikipedia, who gets this "substub" notice slapped onto his first contribution. Is it welcoming? Is it kind, or is it rude? Is it necessary? Next I ask you to consider the response of someone who comes to Wikipedia to look up information and encounters this current notice: "This article is a substub. A substub is even smaller than a normal stub, and does not reflect well on the quality of information in Wikipedia. You can help Wikipedia by expanding it". Does the message itself reflect well on Wikipedia? I think not. Is it useful to someone not already familiar with Wikipedia jargon? I think not. The message also presents your point of view ("does not reflect well on the quality of information in Wikipedia") without attributing it, and without consideration of other points of view (e.g. "a short article is one step on the way to a fuller article, and is the way by which Wikipedia becomes more complete.)" Neither point of view needs to be there. And while you may find utility in having a category for both stubs and substubs (probably because "stub" is dreadfully overused that it has no residual utility, I see little need for a different message for the two: anyone who needs to distinguish between them can do so by looking at the category.- Nunh-huh 02:53, 31 Jul 2004 (UTC)

 * I don't believe in stubs much. They are too easy to create and are too often created by people who don't know anything about the topic (or they would produce a longer article). Accordingly they are quite often inaccurate. Very short stubs not needed at all. Better the user find no reference and search in Google than be annoyed by finding one of these. I've again and again made redirects out of short stubs which sometimes give information on a name found once only in one single work in all of human literature (other than a few references in comments on that work). Presumably the person who created them actually didn't know anything about the name, was just rushing through some handbook and adding reworded information, too often wrongly reworded. Such stubs are worse than nothing.

 * Don't encourage stubs of any kind. Blow them away. Yes ... they can become good articles. But it is just as easy for someone who knows something about a topic to start fresh than to use many stubs. If there is some concern about politeness, which Nunh-huh makes a good point about, then have a standard and polite template put on the user's talk page when short-short items are removed.

 * Perhaps what is needed instead is a template for very short articles that supplies no message but which counteracts a stub message. Some users stick stub notices on articles which are no shorter than many articles in standard paper encyclopedias and can stand quite well at their current size. Expanding such an article may be possible and even desirable, as with any article, but is often not at all necessary. Such a template could be placed by people who know something about the substance of the article to indicate that a short article as it stands is fine and should not display a stub message, including any stub message that someone adds without checking that it was marked as a short no-stub article. See for example Shamgar, which essentially relates everything known about the character mentioned in two verses in the Bible. One could expand this with bits of scholarly speculation, discussions of the etymology of the name, and so forth. Someone who has access to further information would be quite welcome to add that information, as with any article, regardless of size. But as it stands, the article requires no expansion. I could remove the stub notice, but someone would be likely to add it again.

 * My POV is that people should not be encouraged to create stubs. I could create a hundreds stubs a day based on individual POV books.

 * Stubs themselves are somewhat controversial. I don't believe there is any consensus on use of a sub-stub template. A sub-stub article should be deleted. That is my POV.

 * Jallan 17:15, 31 Jul 2004 (UTC)

 * In reply to Nunh-huh's message: First: "threat of edit war"? I was trying to guard against one. Maybe it was a little presumptuous, but I really don't feel like having one right now. Second: you should check out Wikipedia talk:substub if you feel that I am not doing this without consensus. The "quality of information" message was not my idea, and nor is it my opinion, I assure you. The "official-sounding" notices were just my efforts to make sure that I got the word out about substubs in a timely manner. Heck, substubs weren't even my idea. Please don't accuse me of being POV without doing your research in the other discussion forums. Third: your alternate message, "a short article is one step..." is certainly a great idea, and a much better wording, but a little long for a template message. I'll try to incorporate it into the template, unless you do it first. Fourth: if you want to discuss the existence of substubs, then please do it on Wikipedia talk:substub. This talk page is about the template message. Fifth: must you be so rude in your posts? Have I personally attacked you in some way as to provoke you into posting what some would call a flame? [[User:Mike Storm|Mike ∞ Storm]] 19:23, 31 Jul 2004 (UTC)

 * My concern was for the offputting wording of the template message. The current one seems fine. I have no strong feelings on the existence of substubs; I don't think the classification very useful, but that's fine. And if others don't object to the injection of self-referential meta-content into the content area of the wikipedia, I'm surprised, but that's ok, too. As for "fifth": I see nothing "rude" in my message, though it is certainly "cool" in tone, mostly because of your perceived edit war threat. If you didn't mean the threat, that's nice. - Nunh-huh 19:54, 31 Jul 2004 (UTC)

 * In reply to Jallan's message: If you don't support stubs at all, then I suggest that you try to delete the message and see what kind of reaction you get. Furthermore, as I explained to Nunh-huh, this talk page is about the template message. If you want to talk about substubs themselves, then do that on Wikipedia talk:substub. I believe that I have refuted all of your main arguments against substubs there, and I have no desire to repeat myself. [[User:Mike Storm|Mike ∞ Storm]] 19:23, 31 Jul 2004 (UTC)

 * "If you don't support stubs at all ..." Why the conditional? If I were totally opposed to any stubs at all, I would have said so. And even if that were my position, which it is not, I would not be so silly as to unilaterally remove a commonly used template without consensus. I believe stubs should be generally discouraged, which is not the same thing as being prohibited, far more useful would be a distinction between a poor stub and a good but short article.
 * You have not refuted my arguments on any page that I can see. Nor do I see a consensus. I see arguments for and against and a complaint that you skewed the discussion by not including an oppose section. I see a suggestion that you should not be surprised if articles marked as substubs are speedily deleted. I also recognize that adding a feature doesn't require as much consensus as removing or changing a feature. No-one is compelled to use added features.
 * As to posting here, I suggest adding to Nunh-huh's note at the pump the suggestion that all discussion should appear at Wikipedia talk:substub or indicating that template formatting alone should be discusssed here and anything else at Wikipedia talk:substub, whichever you prefer.
 * Jallan 21:08, 31 Jul 2004 (UTC)

Categories
Oughtn't the category name be plural? That's the standard form for categories. The category contains "articles which are substubs", not "articles which are substub". The latter is ungrammatical. --Eequor 16:34, 3 Aug 2004 (UTC)

NPOV
The message is not POV, do you really think that there's a substub anywhere that reflects well on the info in Wikipedia? [[User:Mike Storm|Mike ∞ Storm]] 18:29, 4 Aug 2004 (UTC)

 * Making a statement about how something appears is POV. Saying these articles reflect poorly upon Wikipedia is an open invitation for speedy deletion.  --Eequor 18:39, 4 Aug 2004 (UTC)

 * Hmm... good point. You're right. [[User:Mike Storm|Mike ∞ Storm]] 23:43, 4 Aug 2004 (UTC)

Backgrounds
I made the substub boilerplate message have an orange background because substubs need that extra attention and loving care, and this gets them noticed. [[User:Mike Storm|Mike ∞ Storm]] 18:53, 5 Aug 2004 (UTC)

 * I changed it to a color that's a bit easier on the eyes. [[User:Mike Storm|Mike ∞ Storm]] 19:18, 5 Aug 2004 (UTC)

 * Orange was an ugly color, as it clashes with blue and purple. Teal isn't much better, it makes the external link difficult to see.  How do the following look to you?

 ''This article is a substub, but may eventually become a full article. You can help Wikipedia by [ expanding it].

 ''This article is a substub, but may eventually become a full article. You can help Wikipedia by [ expanding it].

 ''This article is a substub, but may eventually become a full article. You can help Wikipedia by [ expanding it].

 * My preference would be for something close to the first two. The external link is difficult to see against pink as well.  --Eequor 19:28, 5 Aug 2004 (UTC)

 * A nice effect of the un- 'd message (for me, at least) was that it all fit on one line. With the narrower space given to it, it now takes two.  Minor, but something to consider.  --Eequor 19:38, 5 Aug 2004 (UTC)

 * Thanks for the suggestions. I like the first one, the orange color, best. I changed my mind - I like the bottom one, the reddish-pink color, best. I have no problem seeing the external link on that one. By the way, what do you mean, "un-  'd"? As far as I can tell, the message is still a div, and it's all on one line. If it's on two lines, then you can edit the width: thingy until it displays properly on your computer. [[User:Mike Storm|Mike ∞ Storm]] 20:25, 5 Aug 2004 (UTC)

 * Er, I guess it always was a , wasn't it?  I meant before the width was specified.  But it's not really important anyway.  =)  --Eequor 20:57, 5 Aug 2004 (UTC)

No background color, please. So-called substubs are already so small it's hard to see the article; no need to overwhelm it with a message so overdramatic that you never notice the article at all. --Michael Snow 22:03, 5 Aug 2004 (UTC)

 * I second what Michael Snow said. The stub message should be small as to not be larger than the article it marks, and not be quite so blazingly obnoxious as these hot colors.  I'd rather post it on speedy delete than put this kind of ugly banner on it. --ssd 05:21, 6 Aug 2004 (UTC)

 * Agreed, no background color is needed. In fact, the message should not even be bold because it is so easy to see on such short pages.  —siro χ o  00:37, Aug 7, 2004 (UTC)

Since the idea of categorizing substubs separately from stubs is controversial (see Wikipedia talk:Substub), I think we need to see how people feel about the continued use of this template. I'm constructing a survey below. --Michael Snow 19:46, 9 Aug 2004 (UTC)

Notes on wording
"The first step to becoming a full article" doesn't seem quite right to me. This isn't the first step for most other articles, so, in particular, the first step isn't really correct. Also, in my opinion, the reader oughtn't be reminded that the article can't get any worse. --Eequor 22:22, 9 Aug 2004 (UTC)

 * That sounds fine to me. The first step is to create a beginning which can attract the attention of others, notably ia search engines finding the article. It's a small beginning but still a beginning. Jamesday 09:33, 10 Aug 2004 (UTC)

Why is this template so long? The text wraps on my display, which doesn't make a very visually appealing endnote. This template shouldn't be longer than the stub template. ✏ Sverdrup 13:48, 16 Oct 2004 (UTC)

Survey
Is it worthwhile to keep the template? Or should we redirect it to the template?

''It is debatable whether this has been decided already. Please see Wikipedia talk:Substub (and Wikipedia talk:Substub below).''

Arguments for keeping
(In response to the arguments for redirecting):
 * Substubs need extra attention that can be generated by using the template.
 * Substubs need a unique notice indicating that somebody has interest in the article, despite its poor quality (discouraging speedy deletions).
 * By similarity with categories, substubs should use the most specific classification appropriate.
 * You can use the stub message, but isn't it better to be more specific and draw more attention to the fact that this particular stub is really small?
 * When using the substub message, it adds more characters than the stub template. This actually makes it useful, because then in lists such as Shortpages, we can differentiate the substubs which have template message from the ones that don't.
 * Category:Stub isn't too large to be useful -- I, for one, use it frequently.
 * The substub template message tempts people to expand upon it because (eventually, if substubs become an accepted policy) they will realize that while stubs are in need of attention, substubs are in need of extreme attention.
 * Of course there is a way to differentiate between a stub and a substub, which becomes quite clear after reading a few articles on Shortpages: stubs are short articles, and substubs are so short that they are no longer than a dictionary definition.
 * Substubs are indeed a type of stub. However, the argument that we would need both templates for one article is ridiculous, because we can do one or both of these things: 1) include both Category:Stub and Category:Substubs in the template message, and/or 2) make Category:Substubs a subcategory of Category:Stub.
 * How would a substub message make people want to delete an article? Not having the message would tempt them to delete it.
 * It's quite obvious what a substub is, even to newbies. They see sub-, which means small, and then they see -stub, which also means small. What's the conclusion? Substubs are really small. Newbies will want an explanation before their articles are redirected, and not doing so might drive new users away.

Arguments for redirecting

 * Substubs are just a type of stub. The stub template can be used on substubs just like all other stubs.
 * Adding a substub template adds more characters than the stub template. Therefore, it makes it harder to pick out the shortest stubs when organizing by character count, as is done in Offline reports/This is one of the shortest articles.
 * Category:Stub is already too large to be useful. With continued use Category:Substubs will be too.
 * A substub message does not make people any more likely to expand and improve an article than the existing stub message.
 * There is no sensible way to differentiate a substub from a "normal" stub.
 * Since substubs are a type of stub, shouldn't they be included in both categories? But to do that, we would need to use both templates on all substubs.
 * Using a substub message may tempt some people to speedily delete articles when this would not be appropriate.
 * Newbies have a good chance of intuitively understanding what a "stub" is. They are much less likely to immediately understand when they see something called a "substub".
 * We already have too many different messages in the article namespace.
 * The whole purpose of labelling something 'substub' is already covered by labelling it 'stub'.
 * Subsubstub?

Voting
See also Wikipedia talk:Substub

Keep
Substubs should continue to be distinct from stubs.
 * 1) Eequor 20:52, 9 Aug 2004 (UTC)
 * 2) [[User:Mike Storm|Mike ∞ Storm]] 21:58, 9 Aug 2004 (UTC)
 * 3)  —  Ilγαηερ  (Tαlκ)  23:38, 9 Aug 2004 (UTC)
 * 4) Dmn 23:55, 9 Aug 2004 (UTC)
 * 5)  —siro χ o  02:09, Aug 10, 2004 (UTC) (even if the categories are merged, I like the idea of differing messages)
 * 6) Neutrality 02:52, 10 Aug 2004 (UTC)
 * 7) Pjacobi 07:59, 10 Aug 2004 (UTC)
 * 8) Jamesday 09:31, 10 Aug 2004 (UTC) They are a type of stub which is deserving of highlighting for more rapid attention than the few tens of thousands of larger stubs.
 * 9) Everyking 16:44, 10 Aug 2004 (UTC)
 * 10) Timwi 21:48, 10 Aug 2004 (UTC)
 * 11) Dieter Simon 22:09, 10 Aug 2004 (UTC) . If a substantial amount of relevant info has been given in two or three lines of substub, there is no less reason to expand a substub than there is to expand a stub. Keep it distinct.
 * 12) ··gracefool |☺ 01:52, 14 Aug 2004 (UTC)
 * 13) Rossumcapek 23:50, 14 Aug 2004 (UTC)
 * 14) Frazzydee 19:31, 16 Aug 2004 (UTC): Substubs can be swiftly made into stubs, and the template is useful to those who don't have the time to make the article a bit bigger.  It discourages speedy deletions, and allow users to differentiate between small articles and unnervingly miniscules ones.
 * 15) Lvr 11:29, 17 Aug 2004 (UTC)
 * 16) Slowking Man 19:00, Aug 18, 2004 (UTC)
 * 17) Skyler 23:19, Aug 22, 2004 (UTC) - Though I believe the use of stubs and substubs should be clarified.
 * 18) rhyax 05:08, 31 Aug 2004 (UTC) - I agree with Skyler, and i would add clarified in the template.
 * 19)    — Tasty Sandwich | Talk 15:50, 2 Sep 2004 (UTC) Agree with Skyler.
 * 20) Andre 21:58, 13 Sep 2004 (UTC)

Redirect
Substubs should not be distinct from stubs.
 * 1) Michael Snow 21:10, 9 Aug 2004 (UTC)
 * 2) older ≠ wiser 21:32, 9 Aug 2004 (UTC)
 * 3) —Kate | Talk 21:38, 2004 Aug 9 (UTC)
 * 4) Jallan 22:42, 9 Aug 2004 (UTC)
 * 5) Netoholic 23:03, 9 Aug 2004 (UTC)
 * 6) Cyrius|✎ 00:37, 10 Aug 2004 (UTC)
 * 7) Cribcage 02:26, 10 Aug 2004 (UTC)
 * 8) Sean Curtin 06:43, 10 Aug 2004 (UTC)
 * 9) Johnleemk | Talk 09:23, 10 Aug 2004 (UTC)
 * 10) Jwrosenzweig 20:58, 10 Aug 2004 (UTC)
 * 11) User:Krik 21:17, 10 Aug 2004 (UTC)
 * 12) Noisy 12:06, 11 Aug 2004 (UTC)
 * 13) Zoney 17:15, 11 Aug 2004 (UTC)
 * 14) anthony (see warning) 21:09, 11 Aug 2004 (UTC) Not in terms of the message.
 * 15) pstudier 00:21, 12 Aug 2004 (UTC)
 * 16) Cookiecaper 16:42, 16 Aug 2004 (UTC)
 * 17) Sam [Spade] 20:17, 17 Aug 2004 (UTC)
 * 18) Zarggg 02:18, 21 Aug 2004 (UTC) (Stubs are useful, but there's really no need to differentiate.)
 * 19) squash 03:25, Aug 21, 2004 (UTC) There is no need for another stub thing, one is sufficent and only makes a person guessing about if a article should be substub or stub...
 * 20) Dyl 14:36, Aug 21, 2004 (UTC) (meaning of stub is easy to figure out for new users, substub is not)
 * 21) john k 19:40, 11 Sep 2004 (UTC)
 * 22) --Viki 16:36, 15 Sep 2004 (UTC)
 * 23) Yath 08:48, 19 Sep 2004 (UTC) substubs are the work of Hastur
 * 24) Mysteronald 12:27, 25 Sep 2004 (UTC) Substubs are stubs.
 * 25)  Grutness|hello? [[Image:Grutness.jpg|25px|]] 07:59, 15 Apr 2005 (UTC) no need to differentiate
 * 26) -- ericl234  talk  08:06, May 9, 2005 (UTC)

Comments
It should be noted that Category:Substubs organizes substubs. --Eequor 21:02, 9 Aug 2004 (UTC)

 * Since substubs are a type of stub, shouldn't they be included in both categories? But to do that, we would need to use both templates on all substubs.
 * This statement contains its own refutation. --Eequor 21:02, 9 Aug 2004 (UTC)

 * I vote against everything stubstub because Eequor seems to think articles longer than 500 characters can qualify as stubstubs. --ssd 01:12, 10 Aug 2004 (UTC)

 * Some longer articles do. Naming something a stub or a substub isn't so much a reflection on an article's size, as on its content (or rather, its lack of content).  A longwinded essay which fails to establish context necessary to the reader's understanding is no less a substub than a meaningless one-line article.  --Eequor 00:04, 15 Aug 2004 (UTC)

 * Newbies have a good chance of intuitively understanding what a "stub" is. They are less likely to immediately understand when they see something called a "substub".
 * However, both Template:Stub and Template:Substub link to informative descriptions. --Eequor 21:02, 9 Aug 2004 (UTC)

 * Yes, but can you count on people to click to read those descriptions? --Michael Snow 21:10, 9 Aug 2004 (UTC)

 * It also can't be counted on that they will do anything to help, regardless of what we call the article. At worst they'll take no interest and just move on without contributing.

 * To me, the substub message shows more hopefulness than the stub message. Maybe newbies will be encouraged by that.  --Eequor 21:26, 9 Aug 2004 (UTC)

 * Yay! More debate! Just so everyone notices, I posted a few responses to the arguments in the Arguments for redirecting section in the Arguments for keeping section. [[User:Mike Storm|Mike ∞ Storm]] 21:58, 9 Aug 2004 (UTC)
 * Personaly, when i first started, i thought that a substub was longer than a stub, eg, only just a stub, but then i was confused as to why we have ether, they should all be propper articals! I can wish... tooto 01:23, 23 Aug 2004 (UTC)

Michael Snow, I find it somewhat curious that, with the exception of Mike Storm, you seem not to have contacted anyone who indicated their support for substubs. In fact, all the users whom you contacted with a "form letter" on their talk pages (Cyrius, Duncharris, Jallan, John Kenney, Kate, Maximus Rex, and MyRedDice) have indicated, in some way, their opposition to substubs.

While such a beginning is possibly deserved given the beginnings of the poll on Wikipedia talk:Substub, it's rather hypocritical behavior in light of your comment at Wikipedia talk:Substub. --Eequor 22:04, 9 Aug 2004 (UTC)

 * I don't see why I should be obligated to rally support for a position I oppose. The survey is designed to give both sides a fair hearing. Note that I also posted a general announcement to the Village Pump. Supporters of substubs can recruit like-minded people just like I did. --Michael Snow 22:36, 9 Aug 2004 (UTC)

 * Yes. That was also done somewhat later.  --Eequor 23:10, 9 Aug 2004 (UTC)

 * I wasn't attempting to "retaliate" for the way the cited poll was conducted. In fact, I hadn't intended for this survey to start quite so soon, but you went ahead and started voting in it, so I figured I would work with what you did in the wiki spirit. I had left a message for Mike on his talk page asking him to contribute to the arguments for keeping the template, because I felt I wouldn't be able to do his case justice. My plan was to get both sets of arguments ready before actually starting, which is why I didn't vote yet myself while I was designing the survey. --Michael Snow 22:36, 9 Aug 2004 (UTC)

<dd>

Substubs
Since you participated in the discussion on this subject, could you express your opinion on what to do with the substub template at Template talk:Substub? Thanks. --Michael Snow 21:23, 9 Aug 2004 (UTC) </dd></dl></dd></dl>

 * Presumably this notice would have sufficed for everyone else as well. It seems to have done well enough for the others who agree with you, even without making a case for your position.  The message was neutral, but the delivery was not.  --Eequor 23:22, 9 Aug 2004 (UTC)

 * So the way I see it, I am trying to contribute to a process that can treat both points of view fairly. I would have liked a little more preparation, as suggested by Survey guidelines, but I still think we can have a fair survey. Naturally, that requires that both sides promote their positions as best they know how.

 * May I also suggest that accusations of "hypocritical behavior" are fairly strong language, and many people might take offense at such things? Please remember to assume good faith. --Michael Snow 22:36, 9 Aug 2004 (UTC)

 * I had been assuming good faith on your part until you posted an identical notice to seven people who seemed likely to support your position and none who opposed you except for the author. It would have been fairly easy to send the message to everyone else as well, but you did not.  --Eequor 23:10, 9 Aug 2004 (UTC)

Regarding your change to the intro: first, from appearances, the majority is in favor of substubs. Second, your actions have voided any justification you might have had for arguing the merits of the previous survey. --Eequor 22:12, 9 Aug 2004 (UTC)

 * Perhaps you could indicate why there is anything at all wrong with the version: Some related discussion is at Wikipedia talk:Substub, but did not reach a consensus. Are you seriously contending that a consensus was reached? Unless that really is your position, I see no reason to state that It is debatable whether this has been decided already, which is the language I changed. I will readily concede that a small majority favored substubs in the previous survey, but as I've noted, all but one of those were added while the option to oppose was not offered at all. And since the way I see it, the supporters of substubs have in both cases started these surveys on their way prematurely, I feel perfectly justified in arguing the merits of the previous survey. --Michael Snow 22:49, 9 Aug 2004 (UTC)

 * Should a new survey be started, then, giving equal time and voice to both parties? I've personally decided to be neutral in regards to substubs. supadawg 22:54, 9 Aug 2004 (UTC)

 * Hopefully not; I still think this one is quite fair, in spite of the premature start. I would like a more neutrally oriented introduction, however. --Michael Snow 22:57, 9 Aug 2004 (UTC)

 * You did have a chance for neutrality. --Eequor 23:10, 9 Aug 2004 (UTC)

 * I did say it was debatable whether a decision had been reached. Majority support seems a sufficient indication that it had been, however.

 * As the creator of the survey, you had the responsibility to see that it was undertaken in a proper manner. You might have set a starting time, or asked others not to vote yet, or removed my vote, or any number of things.  Instead you contacted everyone who agreed with you.  You have no justifications.  --Eequor 23:10, 9 Aug 2004 (UTC)

 * As I've tried to illustrate, I was trying to construct the survey in a collaborative process. I can now see that I should have put up an obvious notice that it was not open yet. I figured removing a vote would be taken as offensive. I did not contact anyone (except Mike Storm) until after you had voted and listed the survey at Current surveys. If you think simple majority support justifies saying a decision had been reached, I disagree, but I'll leave your version of the introduction. The standard way in which decisions are made on Wikipedia is by consensus, not by majority rule. --Michael Snow 23:32, 9 Aug 2004 (UTC)

Woah, woah, woah! Let's not get into another heated discussion like the one I had with Duncharris. The poll has been started, people are voting, and that's all that matters. Let's just cool it. [[User:Mike Storm|Mike ∞ Storm]] 23:22, 9 Aug 2004 (UTC)

 * Thanks, Mike. You learn well. --Michael Snow 23:32, 9 Aug 2004 (UTC)

 * Was that sarcasm? [[User:Mike Storm|Mike ∞ Storm]] 02:37, 10 Aug 2004 (UTC)

 * Not in the slightest. It was meant to be a compliment. --Michael Snow 05:36, 10 Aug 2004 (UTC)

 * Oh. Thanks, then. [[User:Mike Storm|Mike ∞ Storm]] 16:37, 10 Aug 2004 (UTC)

E8 is a, Adventure Games is a. I can see the difference. Pjacobi 08:02, 10 Aug 2004 (UTC)

Isn't it about time this vote got wrapped up? Can we just post a set time for the vote to end, say, 00:00, 11 Aug, and then take whatever action necessary? 00:28, 15 Aug 2004 (UTC)

 * Since there isn't a consensus, it's not clear what action should be taken. Leaving the survey open does little harm in the meantime, I think. --Michael Snow 16:42, 16 Aug 2004 (UTC)

Misuse of "Stub"
Jamesday's comment was: "They are a type of stub which is deserving of highlighting for more rapid attention than the few tens of thousands of larger stubs."

It think this is the wrong approach.

First, the word "stub" suggests that the article in question is somehow deficient, that it should be expanded to become a larger article. Yet many stubs here are already longer than a corresponding article in Encyclopædia Britannica or other encyclopedias. They are marked as stubs because some editors tend to mark every short article as a stub, no  matter how complete it might be. Indeed, often it is the originator who so marks it, sometimes seemingly unaware how little information is available on the person or place or thing in question. (I've seen stub articles on names of persons and places and even things mentioned which are mentioned once in all of world literature, with a plea for expansion!)

To get rid of the "few tens of thousands of larger stubs" that don't especially need attention, it seems to me a better solution is to unmark them as stubs.

Wikipedia policy should make clear that an article should be put into the stub category only when someone who knows something about the topic feels that it is not just a short article, but an especially difficient short article. There should not be special encouragement to expand a short article particularly over improving a long article.

A large number of articles marked as stubs don't need special attention compared to articles that are inaccurate, badly written, strongly POV and so on, whether they are stubs or not. It is not good when people who don't know much about a topic go to the web and quickly pull out whatever misinformation they find there to supposedly improve a short article because by someone's criteria, it is too short. I've seen too many articles that have grown from being short but accurate into a monstronsity of misinformation, sometimes one piece of misinformation at a time.

A short article that is accurate is preferrable to a longer article which misinforms.

Perhaps we should to get rid of the "stub" category altogether and replace it by a category of "Needs expansion" which might not so encourage every article that happened to be short being so marked. Not every short article especially needs expansion. Many longer articles are far more in need of expansion in respect to what they puport to cover than are many so-called stubs which are fine as they are.

I believe the real problem is this misuse of the stub category.

Jallan 14:41, 10 Aug 2004 (UTC)

 * I agree. Marking something "stub" has lost all meaning, and needs to be fixed. supadawg 15:47, 10 Aug 2004 (UTC)

 * "Stub" has lost quite a bit of meaning, but we already have Requests for page expansion, although it's not used nearly as often as the stub message. However, every short article that's no longer than a dictionary definition is in need of expansion (unless it's a disambig or something), which is why the substub marking is necessary. [[User:Mike Storm|Mike ∞ Storm]]

 * IMHO a good starting point would be, to have the right editors look into stubs in their field. There is some initial attempt to differentiate stubs, and perhaps will help, but e.g.  is still very broad. Perhaps one of our brilliant developers can make it work, that stubs show separately in all categories. So that every category has three lists: "subcategories", "articles in this category" and "stubs in this category". -- Pjacobi 16:58, 10 Aug 2004 (UTC)

 * Separating out stubs within categories is an interesting idea. Substubs in the category "Birmingham, England" would be huge. --Michael Snow 17:15, 10 Aug 2004 (UTC)

 * See []. This kind of thing has been done. You don't need to mark pages as substubs or subs when such lists exist. I don't need a message on a page to tell me that the page is short. I can see that. And I don't need or want someone who knows nothing about the topic telling me that it needs expansion, when other longer articles in the same field are, in my opinon, far more in need of improvement that I can give them.

 * But perhaps one answer is to generate such pages of short articles regularly and provide an easy tool by which anyone can generate similar pages of aricles by categories. Then there would be no need of flagging articles as stubs or substubs by people who know nothing about their topics.

 * An example: substub articles are created on Dromi, Loding, and Gleipnir in February 22, 2002. They should have been blown away. What happens instead. They sit around until July 30 of this year when Eequor comes upon them and marks them as stubs, asking that users expand them and adds links. How are they to be expanded? What did the template accomplish? Jallan 01:47, 11 Aug 2004 (UTC)

 * Considering that Dromi and Loding are now redirects to Fenris, whereas for two years there had been no significant changes, I think it's fairly clear what the templates accomplished. --Eequor 15:49, 11 Aug 2004 (UTC)

 * Nothing? At least according to the person who actually changed them into redirects.   — Kate | Talk 15:56, 2004 Aug 11 (UTC)

 * It sounds as though for Jallan, the stub message contained an implicit question (whether subconscious or conscious): "How could these articles be expanded?", Jallan's answer being "they cannot; they should not even exist". A subtle effect, but still a sort of accomplishment.  --Eequor 16:43, 11 Aug 2004 (UTC)
 * If it sounds like that to you, Eequor, then you aren't listening. You are hearing what you want to hear instead of what I wrote. It's so easy to mark something as a stub. We could even have it done automatically by software. Eequor (and others) write on article after article that people can help Wikipedia by expanding it even though they may know nothing about the article, without bothering check whether the information is duplicated, or is accurate. When you think about, that's almost vandalism. But, like a lot of advertising, people have become so used to those empty, meaningless stub messages that they tune them out. I can see that an article is short without a stub message. If I don't know anything about the subject of the article, I don't know whether it might or might not be especially useful to try to expand or whether it is accurate or not. If I do know something about it, I don't need a spam message telling that it should be expanded, especially when it often it shouldn't be. Stop stub spamming. And this is not directed particularly against Eequor. He's only doing exactly what many, many others are doing. It is coincidence, if there is such a thing, that those articles were marked by Eequor rather than someone else as stubs that needed expanding. There are thousands of other articles equally improperly marked, mindless stub spamming, put a spam message on every article that happens to be short, which software could do as well if there were any real value in it.

Jallan 23:16, 11 Aug 2004 (UTC)

 * I came upon them by chance when the Fenris article appeared on the cleanup list as there were links to them in that article. I simply blew away their useless content and made them redirects to Fenris. The name of the articles are just the names of the three chains used to bind Fenris. The chains are mentioned in all of world literature only in Snorri Sturluson's Edda in his story of Fenris (and then in modern retellings and commentaries on Snorri's tale). We don't want an article on everthing named in every piece of literature. Every stub does not need expansion and every substub, despite what Mike Storm claims above, does not need expansion.
 * Marking them as stubs did not help me. I came upon them as part of working on the article Fenris which appeared on Cleanup when I checked the links. If those articles had been blown away when created, there would have been no loss whatsoever. But if they had been left, there would have been no great damage either. At least those short articles were accurate. The Fenris article was a mess and needed help more than did the substubs. Cleaning up the linked substubs by making them redirects was just part of the Fenris cleanup. I deal with substubs when I can, but Wikipedia is such a mess that I don't see substubs as particularly important to look at over many other tasks. They don't need special treatment. Stubs don't need special treatment. Bad articles need special treatment, whether stubs, stubstub, medium length articles, or long articles.
 * Jallan 01:47, 11 Aug 2004 (UTC)

 * Shortpages isn't that much help. Of course the pages listed there should get some attention, but the judgemnet whether an article has sufficent content to escape being a stub, isn't a question of bytes alone. The is a very basic, but established QC mechanism.  is an attempt to get some more differentiation, but more ambitous projects on this are in preparation, see.
 * But all this doesn't addresses the point which would greatly benefit by separate listings of stubs in all categories: The sheer number of (marked or unmarked) stubs. This workload has to be distributed in a sensible way, and using the existing category system seems to be the easiest method.
 * Pjacobi 12:44, 11 Aug 2004 (UTC)

What was wrong with the articles on Dromi, Loding, and Gleipnir. If I click Gleipnir and then am redirected to an article on the Fenris Wolf, then I have to scroll through and read that entire article to learn what Gleipnir, the thing I was looking up, actually is. What's wrong with a short article on a subject about which there is little information? john k 19:47, 11 Sep 2004 (UTC)

 * The little information on these chains is all in one very short account by Snorri Sturluson that is reduced in size in the Fenrisulfr article. There is not much reading involved. And one can always use one's browser to search within the page. Links to these names remain in other articles only because a full cleanup and rationalization of the Norse mythology articles is taking time. The links should be gradually eliminated. There is no reason that the names of these chains should be mentioned in any other article except the one on Fenrir, whatever it is eventually called, except possibly in some kind of list of names from Norse mythology. And that list should be a useful annotated list rather than a straight list, one that for each name would contain a short single sentence summary with a link to an appropriate article or to appropriate articles for further information.
 * It is annoying to jump from connected article to connected article in an encyclopedia only to come across the same information repeated again and again. One should attempt to have information structured, that is try to have the full information on any topic in one place only. (There are exceptions, such as when combining information from two entirely different viewpoints.)
 * But there is a lot right about a separate aricle on a subject about which there is little information when that little information is compiled from multiple sources or is connected equally to a number of other other topics or not connected logically to any other topic, even if the resultant article is a very short one.
 * Jallan 19:09, 15 Sep 2004 (UTC)

Vandalism protection
The substub has been protected for the purpose against vandalism, since many pages use this stub, it should not be changed frequently anyway. If you feel that the template message needs to be corrected, please indicate so on this talk page or leave a note on my talk page. -- AllyUnion (talk) 02:37, 30 Dec 2004 (UTC)
 * In line with suggestions at WP:WSS, I was going to reduce the size of the text on the template by using the "small" function . It's a minor change, but it would affect a template that's currently on about 4100 articles... Grutness|hello? [[Image:Grutness.jpg|25px|]] 08:03, 15 Apr 2005 (UTC)

Survey again
I'd like to suggest re-opening the survey on retention or deletion of the substub template and category. All the arguments listed above still hold true, but there has been one significant change since the survey was first held - the number of substubs. When the (inconclusive) first voite was taken, there were 4000 substubs. since then, I and other members of Wikiproject stub sorting have been moving them to their respective stub subcategories, where they are far more likely to see actuion by editors, or merging or vfd'ing them, whichever seemed most fitting. There are now fewer than 200 substubs, and the number of un-subcategorised stubs has dropped considerably, probably from about 25,000 to under 4,000 - a drop of nearly 85% (exact figures are not easy to ascertain). As such, this is probably the most appropriate time to assess whether there is any need to have two separate types of stub template, stub and substub, or whether it is better to merge them into one group. Grutness|hello? 07:57, 6 May 2005 (UTC)
 * Update there are currently no substubs. Grutness|hello? [[Image:Grutness.jpg|25px|]] 12:46, 7 May 2005 (UTC)

Vote for deletion
<div class="boilerplate" class="metadata" id="tfd" style="background-color: #F3F9FF; margin: 0 auto; padding: 0 10px 0 10px; border: 1px solid #AAAAAA; "> This is an archive of the discussion about the proposed deletion of this template. There were 20 votes for deletion, 8 votes for keep and 3 votes to redirect to stub. Joe D (t) 19:24, 16 May 2005 (UTC)

Thanks to the hard work at WikiProject Stub sorting, there are no longer any substubs, so the category and template can be deprecated. Radiant_* 14:57, May 10, 2005 (UTC)
 * Rest in peace -- Netoholic @ 16:47, 2005 May 10 (UTC)
 * I find it hard to believe that there are no substubs. I saw one just 5 minutes ago. BrokenSegue 19:15, 10 May 2005 (UTC)
 * Note that the following have been tagged with this template today: Analog filter, Forum invasion, Jnes, Doily, Non-linear filter, Lukanka, Kawaks. Uncle G 19:39, 2005 May 10 (UTC)
 * Note that all have since been re-tagged with more appropriate stub subcategories. Grutness...  wha?  01:21, 11 May 2005 (UTC)
 * Non-linear filter was created with a more appropriate stub tag alongside the substub tag. Uncle G 18:32, 2005 May 11 (UTC)
 * Uncle G -> Yes, but they should have been tagged with instead. The two templates serve the same purpose, hence one should go (or be a redir). Radiant_* 07:56, May 11, 2005 (UTC)
 * I agree that they were wrongly tagged. I was merely noting that a scant 5 hours after your saying that there weren't any articles tagged as substubs, which was true at the time that you wrote it, 7 articles had been tagged. Uncle G 18:32, 2005 May 11 (UTC)
 * I think what Radiant means is that all substubs have been categorized as something-else-stubs. I think the template should be kept because it links to substub which tells people not to make them. Kappa 19:41, 10 May 2005 (UTC)
 * Delete. The concept of substubs has been tried and found not to work. The only proper use for this template is for tagging the junk that does not deserve the honor of being called a stub, but does not qualify as a speedy delete canidate.  These articles are better handled by the various cleanup templates. --Allen3 talk 21:01, May 10, 2005 (UTC)
 * Keep. See my comments at the substub category deletion voting. Courtland 23:33, 2005 May 10 (UTC)
 * Delete. No longer in much serious use, and redundant since the inception of stub subcategories. The original intention of substub was to mark articles that were too short to stand alone and should have had several thins happen to them (1) vfd; (2) merge; (3) hurried expansion. Now, the same articles are placed in categories where editors who know about such topics can find them more easily (who ever waded through 3000 substubs?). And those editors will know far better than the average Wikipedian whether something should be saved or not - as well as being able to expand those that could. I must say that from a philosophical point of view I like Kappa's argument that substub should exist to tell people that substubs shouldn't exist, but I still say rest in peace. Given that substubs are simply short stubs, and are being sorted by the same people who sort stubs, redirecting to stub would be a viable alternative. Grutness...  wha?  02:29, 11 May 2005 (UTC)
 *  Strong Keep The concept of a substub is essential to Wikipedia. Substubs are shorter articles which may offer some, if little, information; they can become valuable articles if worked on. I have also noticed some users at WikiProject Stub sorting are incorrectly reclassifing substubs as stubs. The abolition of substubs would most likely have a negative impact on Wikipedia, just as it would if the stub template was abolished. <FONT COLOR="#00AA00">тə</FONT><FONT COLOR="#00CC00">zє</FONT><FONT COLOR="#00FF00">ті</FONT> 01:25, May 11, 2005 (UTC)
 * care to explain how? The work that has previously been done by substub is now being done far more effectively by the separate stub subcategories. It is far easier for editors to tell what should be kept and what shouldn't. Before there were, at one point, several thousand substubs languishing bcause no-one had the energy to sort out what should stay and what should go. Now, in the vast majority of cases, those articles are somewhere where specialist editors can assess them readily. As for "incorrectly reclassifing substubs as stubs", many people at WP:WSS do not believe that substubs exist as a separate entity, and that there is no purpose for the separate distinction between a short article fragment and a slightly shorter article fragment. If it had been otherwise, substub would not now be empty. Grutness...  wha?  02:27, 11 May 2005 (UTC)
 * Comment If articles are classified as substubs, editors who wish to expand very short articles can easily identify them. A stub can sometimes be longer than a full paragraph, causing me to believe that these articles should be separated from others consisting of only one sentence. I am a member of WikiProject Stub sorting, however I believe that articles should only be sorted as stubs when they would not fit better under any other category. <FONT COLOR="#00AA00">тə</FONT><FONT COLOR="#00CC00">zє</FONT><FONT COLOR="#00FF00">ті</FONT> 03:20, May 11, 2005 (UTC)
 * But most of the things that were in substubs were well over a sentence in length! The last few I've re-sorted from there have, for the most part, been a paragraph in length. And as for "better suiting another category - that's exactly what I explained earlier. They far better suit the subcategories of stub than they do substub. Say, for example, you know a bit about French geography and want to expand some articles. Where would you look first - Category: Substubs or Category: France geography stubs? Perhaps it would illustrate my point further by saying that of the ten or so substubs that I have re-categorised in the last 24 hours, three (Interpellation, The Miracle Maker, and Mount Wuyi) have already been expanded further - presumably by the specialist editors working on the stub subcategories they are now in. One of them is no longer a stub, the other two are still short, but better articles than they were. Grutness...  wha?  04:34, 11 May 2005 (UTC)
 * Substub Categories would allow for this problem to be fixed, or using multiple templates so an article could both be considered a categorized stub and a substub. Also, making the template into a category could offer another solution. <FONT COLOR="#00AA00">тə</FONT><FONT COLOR="#00CC00">zє</FONT><FONT COLOR="#00FF00">ті</FONT> 22:44, May 11, 2005 (UTC)
 * Strong Keep - Consensus in previous TFD was to keep. Andros 1337 03:09, 11 May 2005 (UTC)
 * ...which was before the subcategory system was properly set up, and when there were about 3000 substubs. I voted keep at that time, ISTR. Grutness...  wha?  04:43, 11 May 2005 (UTC)
 * Redirect to Template:Stub, and delete Category:Substubs. People still use the template, but the stub sorting project has made it redundant and less than useful.  -Sean Curtin 03:14, May 11, 2005 (UTC)
 * Delete - this template has always been superfluous. --Yath 04:13, 11 May 2005 (UTC)
 * Delete, putting into specific stub categories is much much more effective. Bluemoose 09:00, 11 May 2005 (UTC)
 * Delete. Useless. Substubs ahould be transwiki'd, merged, deleted or expanded to stubs (if they aren't already stubs). -- grm_wnr Esc  09:11, 11 May 2005 (UTC)
 * Keep and NOOB -- this is within the domain of WikiProject Stub sorting. We have no business fooling with it. If they wish to delete it, they don't need to ask for our help or permission. Any user who wishes to comment on this should do so at Wikipedia talk:WikiProject Stub sorting. — Xiong<font color="#997749">熊 talk<font color="#009900">* 10:16, 2005 May 11 (UTC)
 * If you consider it none of your business, don't vote on it. WP:NOT a bureaucracy. Also, you are probably unaware that most people voting against it ARE from the WPSS. Radiant_* 11:11, May 11, 2005 (UTC)
 * In practice the level of debate tends to be higher away from the *fD pages, because the *fD frequently pages lack the domain-specific knowledge. I see no problem with the stub sorting projecting figuring out the best use of templates for their needs (whilst remaining in the general guidelines). Pcb21| Pete 11:59, 11 May 2005 (UTC)
 * ...and this template would never have been brought to tfd without a considerable amount of debate raging backwards and forwards between several WP:WSS talk pages. It is only because the comments by and large favoured deletion of the template that it was ever brought here for vote. Have a look at Wikipedia_talk:WikiProject_Stub_sorting/Criteria, for example, or Wikipedia_talk:WikiProject_Stub_sorting. That will give you some idea of the discussions on this subject at WP:WSS - and also of the feeling of at least part of the project on whether substubs should stay or go. Grutness...  wha?  06:15, 12 May 2005 (UTC)
 * Very Strong Delete (1st choice), or Redirect (2nd choice). Substubs are an idea whose time has come and gone. Blank <font color= 	#F88017>Verse <font color=#2554C7> <font color=#F660AB>∅  12:18, 11 May 2005 (UTC)
 * Keep' until the project decide what to do with it. Filiocht | Blarneyman 12:54, May 11, 2005 (UTC)
 * The project will decide whether to keep it or delete it right here, right now (This TfD is linked from the WP:WSS pages multiple times), so I suggest that if you're indifferent or want to leave the decision up to the project you should change your vote to "undecided". -- grm_wnr Esc  13:52, 11 May 2005 (UTC)
 * Delete as redundant. Susvolans (pigs can fly) 14:24, 11 May 2005 (UTC)
 * Delete. I wonder what will be the faith of the Substub
 * Delete. James F. (talk) 16:51, 11 May 2005 (UTC)
 * Redirect to Stub - SoM 18:09, 11 May 2005 (UTC)
 * Delete or redirect to {stub} (or {delete} - heh). CDC   (talk)  23:51, 11 May 2005 (UTC)
 * Strong Delete. I have not seen a single unrefuted argument for substubs, other than that we have a page about them. So far, as strongly as <FONT COLOR="#00AA00">тə</FONT><FONT COLOR="#00CC00">zє</FONT><FONT COLOR="#00FF00">ті</FONT> purports to feel, he has not even provided a reason why his two model cases (on Wikipedia_talk:Substub) should be substubs. — Sebastian (talk) 00:16, 2005 May 12 (UTC)
 * Delete I've sorted lots of stubs and substubs; there is a tremendous amount of overlap. It's a distinction without a difference, anything substubs can do stubs can do better. By sorting stubs into categories editors can find articles they have expertise in and expand them. There are no substub categories that offer the same function. If editors don't want to categorize a stub they can still use the generic and someone will sort it, though it's preferable to sort it out of the gate of course. After a transition period while we spread the word and update pages that refer to it, it should be deleted. The substub template is redundant and eliminating it will streamline the process of expanding very short articles. Rx StrangeLove 01:14, 12 May 2005 (UTC)
 * Delete: organisation by topic is far more useful than organisation by length. Joe D (t) 02:32, 12 May 2005 (UTC)
 * Delete. Redundant. Stub categories are much more useful, for all the reasons already stated above. --TheParanoidOne 15:04, 12 May 2005 (UTC)
 * Delete, redundant with now that stub categories exist and are in full use. --Nabla 15:31, 2005 May 12 (UTC)
 * Delete as redundant. Martg76 19:42, 12 May 2005 (UTC)
 * Keep, people are tagging articles as substubs whether we like it or not. It doesn't really matter what their reasons are...maybe they just don't know what to prefix the stub message with to put it into the proper category; or maybe they just think that there's so little information that it should be made note of.  Regardless of the reasons why, deleting this template would cause a lot of "wtf?" reactions when people try to put this in.  Don't delete this, just put a big red box saying deprecated or something so that people know what should be used.  I've seen substubs appear, although they are sorted amazingly fast nowadays.  Still, this template shouldn't be completely deleted, just deprecated. -Frazzydee|✍ 03:04, 13 May 2005 (UTC)
 * might you support a redirect? It would solve a lot of the poits you raise but also help get rid of the category... Grutness...  wha?  03:37, 13 May 2005 (UTC)
 * Delete; this has always been useless. — Dan | Talk 03:04, 13 May 2005 (UTC)
 * Keep the template - the substubs with only a few words should be (after a few days) deleted! Yopohari 08:58, 14 May 2005 (UTC)
 * Delete, not needed and redundant. Stub categories are far more useful.  --Canderson7 13:15, May 16, 2005 (UTC)

Post-TFD discussion
This template was protected because many articles used it. Now almost no articles use it, so protection is no longer necessary. Kappa 07:48, 17 May 2005 (UTC)
 * I agree - and given that it's in the queue to be deleted, turning it into a redirect to stub for the remaining time it's here would make sense - to get people used to it not being around. Grutness...  wha?  11:23, 17 May 2005 (UTC)
 * The category has now also gone through CfD, and the template has been delisted from the WP:TM pages. I have no opinion on whether it should remain protected, but it should at least be redirected to stub.  Joe D (t) 11:59, 17 May 2005 (UTC)
 * It's been delisted from everywhere I could find it listed, with a note saying "currently awaiting deletion", or similar. As an admin I could de-protect it and redirect it myself, but as a courtesy I've contacted AllyUnion as protector of it (1) and I'm waiting to hear back from him before doign anything about it. With any luck it'll only be a few hours. (1: "Protector of the Template" - no there's a fine title if every I heard one!) Grutness...  wha?  13:27, 17 May 2005 (UTC)

We should delete it, not redirect. Deleting it is the only way to ween people off its use. -- Netoholic @ 16:20, 2005 May 17 (UTC)
 * I agree with deleting instead of redirecting. No matter when the delete occurs some portion of the Wikipedia community will still be using substub.  All a redirect does is hide any article tagged as such by placing it into Category:Stub.  When the redirect goes away we are left with the problem of going back and finding all such articles that are still tagged.  --Allen3 talk 23:30, May 17, 2005 (UTC)
 * Precisely. At this point in time, a lot of people are watching for substub tagging, and taking care of them, so now is a great time to quit cold turkey. -- Netoholic @ 01:00, 2005 May 18 (UTC)
 * Mmm. Good points. The template is now the only thing in the category and nothing links to it (other than talk pages and the like), and is ready for deletion, but I take it the talk page should be archived somehow first. Anyone know what to do as far as that is concerned? Grutness...  wha?  01:50, 18 May 2005 (UTC)
 * I've documented the template's last content on Substub. Talk page's aren't archived anywhere special, but if you're asking about the TFD discussion, it's already logged per the TFD process. -- Netoholic @ 02:11, 2005 May 18 (UTC)

Unintended consequence of current appearance
If you're searching histories of articles that once were marked, it appears that the article has been deleted, rather than the template. Very confusing; took me a long time to figure out what was going on at Projective set, especially given that immediately after the template is removed, the article turns into a redirect. I was looking through old VfD logs to see what had happened and coming up blank. Any way to change the content of the template to make the situation clear? --Trovatore 06:34, 27 September 2005 (UTC)
 * Think I've fixed it now; hope it's OK with everybody. --Trovatore 06:52, 27 September 2005 (UTC)

 * I've used "noinclude", which means that it won't appear in the articles when you view them. I reckon that'll be the best solution.  violet/riga (t) 21:30, 27 September 2005 (UTC)

Apologies. It was my fault for adding the template without thinking about the appearance (I figured that substub wouldn't be on any new articles, but forgot about page histories. The main problem is that deletedpage is not really designed for use on templates (and as far as I know there is no equivalent for templates). Grutness...  wha?  00:26, 28 September 2005 (UTC)
 * This template is still getting added to pages occasionally. Should we put a note in the template that appears in the article saying to not include it or remove it or something? --ssd 16:33, 25 December 2005 (UTC)


text:
Electro-Shock Blues

Electro-Shock Blues is the second studio album by American rock band Eels. It was released in the United Kingdom on September 21, 1998, and October 20 in the United States by record label DreamWorks.

Background and content
Electro-Shock Blues was written largely in response to frontman Mark Oliver "E" Everett's sister Elizabeth's suicide and his mother's terminal lung cancer. The title refers to the electroconvulsive therapy received by Elizabeth Everett when she was institutionalized. Many of the songs deal with their decline, his response to loss and coming to terms with suddenly becoming the only living member of his family (his father, Dr. Hugh Everett III, having died of a heart attack in 1982; Everett, then 19 years old, was the first to discover his body).

Though much of the album is, on its surface, bleak, its underlying message is that of coping with tragedy. The record begins with "Elizabeth on the Bathroom Floor", a sparse piece composed of one of Elizabeth Everett's final diary entries. Later, the album's emotional climax is reached in two tracks: "Climbing to the Moon", which draws upon Everett's experiences visiting his sister at a mental health facility shortly before her death; and "Dead of Winter", a song about his mother's painful radiation treatment and slow death. The album's last song, "P.S. You Rock My World", is a hopeful bookend to "Elizabeth", containing subtly humorous lyrics that describe, among other things, an elderly woman at a gas station honking her car at Everett, incorrectly assuming he is the attendant, and his decision that "maybe it's time to live".

According to the Eels official website, the song "Baby Genius" is about Everett's father, a quantum physicist who authored the Many Worlds Theory, although Jim Lang, who helped with the song, believed it was about Eels former bassist, Tommy Walter.

Recording
At the time of the album's recording, the only official Eels members were E himself and drummer Butch Norton, as Tommy Walter had left the band.

Electro-Shock Blues features guest appearances by T-Bone Burnett, Lisa Germano, Grant Lee Phillips and Jon Brion.

Release
Electro-Shock Blues was released September 21, 1998, by record label DreamWorks. In addition to CD and cassette releases, it was also released on vinyl. This version included two 10-inch 33 RPM discs on see-through blue vinyl, limited to a small pressing.

Commercially the album didn't fare well, selling considerably less than the band's debut album, Beautiful Freak.

Critical reception
Electro-Shock Blues was well received by critics. Robert Hilburn of the Los Angeles Times called it "a brilliant work that combines often conflicting emotions so skillfully that you are reminded at times of the childhood innocence of Brian Wilson, the wicked satire of Randy Newman and the soul-baring intensity of John Lennon." Marc Weingarten of Entertainment Weekly wrote that while the album "lays bare the horrors of terminal illness in songs that shift from clinical to disconsolate", its "real feat is in making death life-affirming".

Colin Cooper of Stylus Magazine, in a retrospective write-up of Electro-Shock Blues, described it as "an album that reeks of classic on all levels: scene is set, tone established, problem arisen, grappled, fought (nearly lost) and eventually—joyously—overcome." Sputnikmusic reviewer Robin called it "deeper than some ironic indie pop record: it's E's honest smack of tough love, and he is his own recipient."

Tour
The Daniel Johnston song "Living Life" was played often on the Electro-Shock Blues tour, eventually seeing a studio release in 2004 on the tribute compilation The Late Great Daniel Johnston: Discovered Covered.

Personnel
Eels

 * E – vocals, guitar, bass, piano, keyboards, lyrics
 * Butch – drums, percussion, backing vocals

Additional musicians

 * Jon Brion – Chamberlin and Hammond organ on "Climbing to the Moon"
 * T-Bone Burnett – bass on "Climbing to the Moon"
 * Lisa Germano – violin on "Ant Farm"
 * Parthenon Huxley – guitar on "Going to Your Funeral Part I"
 * Jim Jacobsen – bass and keyboards on "Going to Your Funeral Part I", clarinet on "Going to Your Funeral Part II", arrangements
 * John Leftwich – upright bass on "Ant Farm" and "Dead of Winter", bowed bass on "Dead of Winter"
 * Elton Jones – backing vocals on "Last Stop: This Town"
 * Bill Liston – saxophone on "Hospital Food"
 * Volker Masthoff – vocals on "My Descent into Madness"
 * Cynthia Merrill – backwards cello on "Efils' God"
 * Grant-Lee Phillips – electric guitar, banjo, backing vocals on "Climbing to the Moon"
 * Stuart Wylen – ½ Rhodes, guitar, alto and bass flutes on "The Medication Is Wearing Off"

Technical

 * E – production
 * Michael Simpson – production
 * Mickey Petralia – production, mixing
 * Greg Collins – mixing
 * Jim Lang – mixing, conduction
 * Stephen Marcussen – mastering
 * Chester Brown – sleeve illustration
 * Debbie Dreschler – sleeve illustration
 * Hugh Everett III – sleeve illustration
 * Joe Matt – sleeve illustration
 * Francesca Restrepo – art direction, sleeve design
 * H. Scott Rusch – illustration
 * Seth – sleeve illustration
 * Adrian Tomine – sleeve illustration

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Electro-Shock Blues


text: User talk:167.206.231.97

title: User talk:167.206.231.97


text:
Wikipedia:Articles for deletion/Marrana

 This page is an archive of the discussion about the proposed deletion of the article below. This page is no longer live. Further comments should be made on the article's talk page rather than here so that this page is preserved as an historic record. The result of the debate was I speedy deleted this as nonsense. Zzyzx11 (Talk) 20:31, 14 Jun 2005 (UTC)

Marrana
Nonsense. - Possible candidate for speedy deletion? --Ian Pitchford 16:32, 14 Jun 2005 (UTC)
 * Speedy delete, patent nonsense. KFP 17:07, 14 Jun 2005 (UTC)
 * This page is now preserved as an archive of the debate and, like some other VfD subpages, is no longer 'live'. Subsequent comments on the issue, the deletion, or the decision-making process should be placed on the relevant 'live' pages. Please do not edit this page.

title: Wikipedia:Articles for deletion/Marrana


text:
User:John Z

Wikipedia is an endless wild party, where no editor is not a vandal, but because as each article is edited it is immediately revised, it is equally clearly "the right version."

title: User:John Z


text:
Beechcraft Model 18

The Beechcraft Model 18 (or "Twin Beech", as it is also known) is a 6- to 11-seat, twin-engined, low-wing, tailwheel light aircraft manufactured by the Beech Aircraft Corporation of Wichita, Kansas. Continuously produced from 1937 to November 1969 (over 32 years, a world record at the time), over 9,000 were built, making it one of the world's most widely used light aircraft. Sold worldwide as a civilian executive, utility, cargo aircraft, and passenger airliner on tailwheels, nosewheels, skis, or floats, it was also used as a military aircraft.

During and after World War II, over 4,500 Beech 18s were used in military service—as light transport, light bomber (for China), aircrew trainer (for bombing, navigation, and gunnery), photo-reconnaissance, and "mother ship" for target drones—including United States Army Air Forces (USAAF) C-45 Expeditor, AT-7 Navigator, and AT-11 Kansan; and United States Navy (USN) UC-45J Navigator, SNB-1 Kansan, and others. In World War II, over 90% of USAAF bombardiers and navigators trained in these aircraft.

In the early postwar era, the Beech 18 was the pre-eminent "business aircraft" and "feeder airliner". Besides carrying passengers, its civilian uses have included aerial spraying, sterile insect release, fish stocking, dry-ice cloud seeding, aerial firefighting, air-mail delivery, ambulance service, numerous movie productions, skydiving, freight, weapon- and drug-smuggling, engine testbed, skywriting, banner towing, and stunt aircraft. Many are privately owned, around the world, with 240 in the U.S. still on the FAA Aircraft Registry in August 2017.

Design and development

By the late 1930s, Beechcraft management speculated that a demand would exist for a new design dubbed the Model 18, which would have a military application, and increased the main production facilities. The design was mainly conventional for the time, including twin radial engines, all-metal semimonocoque construction with fabric-covered control surfaces, and tailwheel undercarriage. Less conventional was the twin-tailfin configuration. The Model 18 can be mistaken for the larger Lockheed Electra series of airliners, which closely resemble it. Early production aircraft were powered either by two 330-hp (250-kW) Jacobs L-6s or 350-hp (260-kW) Wright R-760Es. The 450-hp (336-kW) Pratt & Whitney R-985 became the definitive engine from the prewar C18S onwards. The Beech 18 prototype first flew on January 15, 1937.

The aircraft has used a variety of engines and has had a number of airframe modifications to increase gross weight and speed. At least one aircraft was modified to a 600-hp (447-kW) Pratt & Whitney R-1340 powerplant configuration. With the added weight of about 200 lb (91 kg) per engine, the concept of a Model 18 fitted with R-1340 engines was deemed unsatisfactory due to the weakest structural area of the aircraft being the engine mounts. Nearly every airframe component has been modified.

In 1955, deliveries of the Model E18S commenced; the E18S featured a fuselage that was extended 6 in higher for more headroom in the passenger cabin. All later Beech 18s (sometimes called Super 18s) featured this taller fuselage, and some earlier models (including one AT-11) have been modified to this larger fuselage. The Model H18, introduced in 1963, featured optional tricycle undercarriage. Unusually, the undercarriage was developed for earlier-model aircraft under an STC by Volpar, and installed in H18s at the factory during manufacture. A total of 109 H18s was built with tricycle undercarriage, and another 240 earlier-model aircraft were modified with this.

Construction of the Beechcraft Model 18 ended in 1970 with a final Model H18 going to Miyazaki Aviation College, Japan. Through the years, 32 variations of the basic design had flown, over 200 improvement modification kits were developed, and almost 8,000 aircraft were built. In one case, the aircraft was modified to a triple tail, trigear, humpbacked configuration and appeared similar to a miniature Lockheed Constellation. Another distinctive conversion was carried out by Pacific Airmotive as the PacAero Tradewind. This featured a lengthened nose to accommodate the tricycle nosewheel, and the Model 18's twin tailfins were replaced by a single fin.

Operational history

Production got an early boost when Nationalist China paid the company US$750,000 for six M18R light bombers, but by the time of the U.S. entry into World War II, only 39 Model 18s had been sold, of which 29 were for civilian customers. Work began in earnest on a variant specifically for training United States Army Air Forces (USAAF) military pilots, bombardiers, and navigators. The effort resulted in the Army AT-7. Further development led to the AT-11 navigation trainer, C-45 military transport, and F-2 (the "F" standing for "Fotorecon", short for "photographic reconnaissance"). The United States Navy first adopted the Beech 18 as the JRB-1, equivalent to the F-2, followed by the JRB-2 transport; the JRB was initially named the Voyager, but this name did not enter common use, and JRBs were generally called Expeditors like their USAAF counterparts. The first JRB-1 obtained by the Navy, bureau number (BuNo) 09771, was converted from the last civil Model 18 built before production was earmarked solely for the military for the duration of the war. The Navy subsequently obtained more Model 18s as the JRB-3 (C-45B), JRB-4 (UC-45F), SNB-1 Kansan (AT-11), SNB-2 (AT-7), and SNB-2C (AT-7C). Existing naval Twin Beeches were subsequently modified into the SNB-2H air ambulance, SNB-2P reconnaissance trainer, and SNB-3Q electronic countermeasures trainer. The United States Coast Guard acquired seven JRB-4 and JRB-5 aircraft from the Navy between 1943 and 1947; they were primarily used as utility transports, with one aircraft later converted for aerial mapping, and another used for proficiency flying.

After the war, the USAAF became the United States Air Force (USAF), and the USAF Strategic Air Command had Model 18 variants (AT-11 Kansans, C-45 Expeditors, F-2 Expeditors, and UC-45 Expeditors) from 1946 until 1951. In 1950, the Navy still had around 1,200 JRB and SNB aircraft in inventory. From 1951 to 1955, the USAF had many of its aircraft remanufactured with new fuselages, wing center sections, and undercarriages to take advantage of the improvements to the civil models since the end of World War II. Eventually, 900 aircraft were remanufactured to be similar to the then-current Model D18S and given new designations, constructor's numbers, and Air Force serial numbers. The USN had many of its surviving aircraft remanufactured as well, resulting in the JRB-6, the SNB-5, and SNB-5P. The Coast Guard retired its JRBs in 1956 and sold most of them as surplus in 1959, but one was retained by the United States Coast Guard Reserve until at least 1972. With the adoption of the 1962 United States Tri-Service aircraft designation system, the Navy's SNB-5 and SNB-5P became the TC-45J and RC-45J respectively, later becoming the UC-45J as their primary mission shifted from aircrew training to utility transport work. The C-45 flew in USAF service until 1963, the USN retired its last UC-45J in 1972, while the U.S. Army flew its C-45s until 1976. In later years, the military called these aircraft "bug smashers" in reference to their extensive use supplying mandatory flight hours for desk-bound aviators in the Pentagon.

Beech 18s were used extensively by Air America during the Vietnam War; initially more-or-less standard ex-military C-45 examples were used, but then the airline had 12 aircraft modified by Conrad Conversions in 1963 and 1964 to increase performance and load-carrying capacity. The modified aircraft were known as Conrad Ten-Twos, as the maximum takeoff weight (MTOW) was increased to 10200 lb. The increase was achieved by several airframe modifications, including increased horizontal stabilizer angle-of-incidence, redesigned undercarriage doors, and aerodynamically improved wingtips. Air America then had Volpar convert 14 aircraft to turboprop power, fitted with Garrett AiResearch TPE-331 engines; modified aircraft were called Volpar Turbo Beeches, and also had a further increase in MTOW to 10286 lb.

Spar problems
The wing spar of the Model 18 was fabricated by welding an assembly of tubular steel. The configuration of the tubes in combination with drilled holes from aftermarket STC modifications on some of these aircraft have allowed the spar to become susceptible to corrosion and cracking while in service. This prompted the FAA to issue an Airworthiness Directive in 1975, mandating the fitting of a spar strap to some Model 18s. This led, in turn, to the retirement of a large number of STC-modified Model 18s when owners determined the aircraft were worth less than the cost of the modifications. The corrosion on unmodified spars was not a problem; it occurred due to the additional exposed surface area created through the STC hole-drilling process. Further requirements have been mandated by the FAA and other national airworthiness authorities, including regular removal of the spar strap to allow the strap to be checked for cracks and corrosion and the spar to be X-rayed. In Australia, the airworthiness authority has placed a life limit on the airframe, beyond which aircraft are not allowed to fly.

Manufacturer models
Unless otherwise noted, the engines fitted are Pratt & Whitney R-985 radials.

 * Model 18A
 * First production model with seating for two pilots and seven or eight passengers, fitted with Wright R-760E-2 engines of 350 hp, MTOW: 6700 lb Four built.

 * Model S18A
 * Version of Model 18A capable of being fitted with skis or Edo 55-7170 floats; MTOW: 7200 lb

 * Model A18A
 * Version fitted with Wright R-760E-2 engines, MTOW: 7500 lb

 * Model SA18A
 * Seaplane version of Model A18A, MTOW: 7170 lb

 * Model 18B
 * Version powered with 285 hp Jacobs L-5 engines. Four built.

 * Model S18B
 * Version of Model 18B capable of being fitted with skis or floats.

 * Model 18D
 * Variant with seating for two pilots and nine passengers, fitted with Jacobs L-6 engines of 330 hp, MTOW: 7200 lb. Twelve aircraft built.

 * Model S18D
 * Version of Model 18D capable of being fitted with skis or, MTOW: 7170 lb

 * Model A18D
 * Variant of 18D with MTOW increased by 300 lb to 7500 lb.

 * Model SA18D
 * Seaplane version of Model A18D, but same MTOW as S18D.

 * Model 18R
 * Model with Pratt and Whitney R-985, 420 hp, seven built, one to Sweden as an air ambulance, six to Nationalist China as M18R light bombers

 * Model 18S
 * Nine-passenger pre-World War II civil variant, powered by 450 hp served as basis for USAAF C-45C

 * Model B18S
 * Nine-passenger pre-World War II civil variant, served as basis for USAAF F-2

 * Model C18S
 * Variant of B18S with seating for eight passengers, and equipment and minor structural changes

 * Model D18S
 * First post-World War II variant introduced in 1945, with seating for eight passengers and MTOW of 8750 lb, 1,035 built

 * Model D18C
 * Variant with Continental R9-A engines of 525 hp and MTOW of 9000 lb, introduced in 1947, 31 built.

 * Model E18S
 * Variant with redesigned wing and MTOW of 9300 lb; 403 built

 * Model E18S-9700
 * Variant of E18S with MTOW of 9700 lb; 57 built

 * Model G18S
 * Superseded E18S, MTOW of 9700 lb; 155 built

 * Model G18S-9150
 * Lightweight version of G18, MTOW of 9150 lb; one built

 * Model H18
 * Last production version, fitted with optional tricycle undercarriage developed by Volpar and MTOW of 9900 lb; 149 built, of which 109 were manufactured with tricycle undercarriage

USAAC/USAAF designations

 * C-45
 * Six-seat staff transport based on C18S; 11 built

 * C-45A
 * Eight-seat utility transport based on C18S; 20 built

 * RC-45A
 * Redesignation of all surviving F-2, F-2A, and F-2B aircraft by the USAF in 1948

 * C-45B
 * Based on C18S, but with modified internal layout; 223 ordered, redesignated UC-45B in 1943 Equipped with a hatch in the cabin door for aerial photography.

 * C-45C
 * Two Model 18S aircraft impressed into the USAAF, redesignated UC-45C in January 1943

 * C-45D
 * Designation given to two AT-7 aircraft converted as passenger transports during manufacture, redesignated UC-45D in January 1943

 * C-45E
 * Designation given to two AT-7 and four AT-7B aircraft converted as passenger transports during manufacture, redesignated UC-45E in January 1943

 * C-45F
 * Standardized seven-seat version based on C18S, with longer nose than preceding models; 1,137 ordered, redesignated UC-45F

 * C-45G
 * AT-7s and AT-11s remanufactured in the early 1950s for the USAF to similar standard as civil D18S with autopilot and R-985-AN-3 engines; 372 aircraft rebuilt

 * TC-45G
 * Multiengine crew trainer variant of C-45G; AT-7s and AT-11s remanufactured in the early 1950s for the USAF to similar standard as civil D18S, 96 aircraft rebuilt

 * C-45H
 * AT-7s and AT-11s remanufactured in the early 1950s for the USAF to similar standard as civil D18S, with no autopilot and R-985-AN-14B engines; 432 aircraft rebuilt

 * TC-45H

 * RC-45J
 * In 1962, all surviving U.S. Navy SNB-5Ps were redesignated RC-45J

 * TC-45J
 * In 1962 all surviving U.S. Navy SNB-5s were redesignated TC-45J

 * UC-45J
 * Subsequent redesignation of RC-45J and TC-45J

 * AT-7 Navigator
 * Navigation trainer based on C18S, with an astrodome and positions for three students, powered by 450-hp Pratt & Whitney R-985-25 engines; 577 built

 * AT-7A
 * Floatplane version of AT-7; six built

 * AT-7B
 * Winterised AT-7; nine built

 * AT-7C
 * Based on C18S with R-985-AN3 engines; 549 built

 * AT-11 Kansan
 * Bombing and gunnery trainer for USAAF derived from AT-7, fuselage had small, circular cabin windows, bombardier position in nose, and bomb bay; gunnery trainers were also fitted with two or three .30-caliber machine guns, early models (the first 150 built) had a single .30-cal AN-M2 in a Beechcraft-manufactured top turret, later models used a Crocker Wheeler twin .30-cal top turret, a bottom tunnel gun was used for tail gunner training, 1,582 built for USAAF orders, with 24 ordered by Netherlands repossessed by USAAF and used by the Royal Netherlands Military Flying School at Jackson, Mississippi.

 * AT-11A
 * Conversion of AT-11 as navigation trainer; 36 converted

 * CQ-3
 * Conversion of UC-45F, modified to act as drone control aircraft, redesignated as DC-45F in June 1948

 * F-2
 * Photo-reconnaissance version based on B18

 * F-2A
 * Improved version

 * F-2B

US Navy designations

 * JRB-1
 * Photographic aircraft, based on the C18S, fitted with fairing over cockpit for improved visibility, 11 obtained, at least one conversion from impressed civil B18S

 * JRB-2
 * Light transport, based on the C18S; 15 obtained, at least one conversion from JRB-1, some transferred from USAAF C-45A stocks

 * JRB-3
 * Photographic version, similar to C-45B; 23 obtained, some transferred from USAAF C-45B stocks

 * JRB-4
 * Utility transport version, equivalent to UC-45F; 328 obtained from USAAF

 * JRB-6
 * Remanufactured JRB

 * SNB-1
 * Similar to AT-11; 110 built

 * SNB-2
 * Navigation trainer similar to AT-7, 299 built

 * SNB-2C
 * Navigation trainer similar to AT-7C, 375 built

 * SNB-2H
 * Ambulance conversion

 * SNB-2P
 * Photo-reconnaissance trainer conversion

 * SNB-3Q
 * Electronic countermeasures trainer conversion

 * SNB-5
 * Remanufactured SNB or JRB

 * SNB-5P
 * Remanufactured SNB-2P

RAF/RCAF Lend-lease designations

 * Expeditor I: C-45Bs supplied to the RAF under Lend-Lease
 * Expeditor II: C-45Fs supplied to the RAF and Royal Navy under Lend-Lease
 * Expeditor III: C-45Fs supplied to the RCAF under Lend-Lease

Post-war RCAF designations
C-45Ds delivered between 1951 and 1952
 * Expeditor 3N: navigation trainer - 88 built
 * Expeditor 3NM: navigational trainer that could be converted to a transport - 59 built
 * Expeditor 3NMT: 3NM converted to a transport aircraft - 67 built
 * Expeditor 3NMT(Special): navigation trainer/personnel transport - 19 built
 * Expeditor 3TM: transport with fittings so it could be converted to a navigation trainer - 44 built
 * Expeditor 3TM(Special): modified RCAF Expeditors used overseas in conjunction with Project WPB6 - three built

Canadian Armed Forces

 * CT-128 Expeditor: 1968 redesignation of existing RCAF aircraft upon unification of the Canadian Armed Forces

Conversions

 * Conrad 9800
 * Modification increasing the gross weight to 9,800 pounds with a single piece windshield

 * Dumod I
 * Executive conversion with Volpar tricycle landing gear, new wing tips, enlarged fight deck and refurbished 6–7 seat cabin with larger windows. Originally named Infinité I. 37 converted by 1966.

 * Dumod Liner
 * Stretched airliner conversion. Similar to Dumod I but with forward fuselage stretched by 6 ft, allowing up to 15 passengers to be carried. Originally named Infinité II.

 * Hamilton HA-1
 * conversion of a TC-45J aircraft

 * Hamilton Little Liner
 * Modification of D18S with aerodynamic improvements and new, retractable tailwheel, capable of carrying 11 seats

 * Hamilton Westwind
 * Turboprop conversions with various engines

 * Hamilton Westwind II STD: Stretched conversion powered by two 840-hp PT6As, and with accommodation for up to 17 passengers
 * Hamilton Westwind III:two 579-hp PT6A-20s or 630-hp  PT6A-27s or 630-hp Lycoming LTS101s.
 * Hamilton Westwind IV:two 570-hp Lycoming LTP101s or 680-hp PT6A-28s or 750-hp PT6A-34s or 1020-hp PT6A-45s
 * PacAero Tradewind
 * Conversion of Beech D18S/C-45 to five- to 11-seat executive transport with single fin by Pacific Airmotive

 * Rausch Star 250
 * Built as C-45F 44-47231, this aircraft was re-manufactured at Wichita by Beech in 1952, to become TC-45G 51-11544. From 1959 Rausch Engineering Inc. of South San Francisco, California, converted N8186H to tricycle undercarriage, using forward retracting main gear from a P-51 and rearward-retracting nose-leg from a T-28, adding a 3 ft nose extension, 4 ft rear fuselage extension, re-roofed fuselage for increased headroom and enlarged cabin windows. The modifications did not obtain FAA certification despite 58 hours of flight testing, with the aircraft eventually being broken up at Antioch, CA, in 1978.

 * SFERMA-Beechcraft PD.18S
 * Modification of Beech 18S powered by two Turboméca Bastan turboprops

 * Volpar (Beechcraft) Model 18
 * Conversion of Model 18 with nosewheel undercarriage

 * Volpar (Beechcraft) Super 18:
 * Volpar (Beechcraft) Turbo 18:Beech Model 18s fitted with the Volpar MkIV tricycle undercarriage and powered by two 705-hp Garrett TPE331-1-101B turboprop engines, flat-rated to 605 hp, driving Hartzell HC-B3TN-5 three-bladed, reversible-pitch, constant-speed feathering propellers
 * Volpar (Beechcraft) Super Turbo 18
 * 2x 705 hp Garrett TPE331

 * Volpar (Beechcraft) C-45G
 * C-45G aircraft modified with tricycle undercarriage

 * Volpar (Beechcraft) Turboliner
 * 15-passenger version of the Turbo 18 with extended fuselage, powered by 2 705-hp Garrett TPE331-1-101Bs

 * Volpar (Beechcraft) Turboliner II
 * Turboliners modified to meet SFAR 23

Civil
, the Beechcraft Model 18 remains popular with air charter companies and small feeder airlines worldwide.

Military

 * 🇦🇷 Argentina
 * Argentine Air Force
 * Argentine Naval Aviation
 * 🇧🇴 Bolivia
 * Bolivian Air Force
 * 🇧🇷 Brazil
 * Brazilian Air Force
 * 🇨🇦 Canada
 * Royal Canadian Air Force 394 examples from 1941 to 1972
 * Royal Canadian Navy 10 examples from 1952 to 1960
 * VX-10 Squadron
 * VU-32 Squadron
 * Canadian Armed Forces
 * 🇨🇱 Chile
 * Chilean Air Force
 * Chilean Army
 * Chilean Navy
 * 🇨🇴 Colombia
 * Colombian Air Force
 * 🇨🇷 Costa Rica
 * Public Force of Costa Rica
 * 🇨🇮 Côte d'Ivoire
 * 🇨🇺 Cuba
 * Cuban Air Force - received two AT-7s, two AT-11s, a F-2B and a UC-45F in 1947
 * 🇩🇴 Dominican Republic
 * Dominican Air Force
 * 🇪🇨 Ecuador
 * Ecuadorian Air Force
 * 🇸🇻 El Salvador
 * Air Force of El Salvador
 * 🇫🇷 France
 * French Air Force
 * French Naval Aviation
 * 🇬🇹 Guatemala
 * Guatemalan Air Force
 * 🇭🇹 Haiti
 * Haiti Air Corps
 * Honduran Air Force
 * 🇮🇩 Indonesia
 * Indonesian Army
 * Indonesian National Police
 * 🇮🇷 Iran
 * 🇮🇹 Italy
 * Italian Air Force operated 125 aircraft from 1949 until the 1970s
 * 🇯🇵 Japan
 * Japan Maritime Self-Defense Force
 * Japan Coast Guard
 * 🇲🇽 Mexico
 * Mexican Air Force
 * Mexican Navy
 * 🇳🇱 Netherlands
 * Royal Netherlands Air Force
 * Dutch Naval Aviation Service
 * 🇳🇮 Nicaragua
 * Nicaraguan Air Force
 * 🇳🇪 Niger
 * Niger Air Force
 * 🇳🇬 Nigeria
 * 🇵🇾 Paraguay
 * Paraguayan Air Force
 * 🇵🇪 Peru
 * Peruvian Air Force
 * 🇵🇭 Philippines
 * Philippine Army Air Corps
 * 🇵🇹 Portugal
 * Forca Aerea Portuguesa
 * Portuguese Navy
 * 🇸🇴 Somalia
 * Somali Air Force – Withdrawn in 1991
 * 🇿🇦 South Africa
 * South African Air Force
 * South Vietnam
 * Republic of Vietnam Air Force
 * 🇪🇸 Spain
 * 🇱🇰 Sri Lanka
 * Sri Lanka Air Force
 * 🇸🇪 Sweden
 * Swedish Air Force
 * 🇨🇭 Switzerland
 * Swiss Air Force
 * 🇹🇼 Taiwan
 * Republic of China Air Force
 * 🇹🇭 Thailand
 * Royal Thai Air Force
 * 🇹🇴 Tonga
 * Tongan Maritime Force Air Force
 * Tongan Maritime Force Air Force

 * 🇹🇷 Turkey
 * Turkish Air Force
 * 🇬🇧 United Kingdom
 * Royal Air Force
 * Royal Navy – Fleet Air Arm 76 Lend-Lease
 * 701 Naval Air Squadron
 * 712 Naval Air Squadron
 * 723 Naval Air Squadron
 * 724 Naval Air Squadron
 * 728 Naval Air Squadron
 * 730 Naval Air Squadron
 * 739 Naval Air Squadron
 * 742 Naval Air Squadron
 * 755 Naval Air Squadron
 * 781 Naval Air Squadron
 * 782 Naval Air Squadron
 * 791 Naval Air Squadron
 * 🇺🇸 United States
 * United States Army
 * United States Army Air Corps
 * United States Army Air Forces
 * United States Air Force
 * United States Coast Guard
 * United States Coast Guard Reserve
 * United States Marine Corps
 * United States Navy
 * 🇺🇾 Uruguay
 * Uruguayan Air Force
 * 🇻🇪 Venezuela
 * Venezuelan Air Force
 * Zairian Air Force
 * Zairian Air Force

Accidents and incidents
The Beechcraft Model 18 family has been involved in the following notable accidents and incidents:
 * April 25, 1951: Cubana de Aviación Flight 493, a Douglas DC-4 bound from Miami to Havana, registration CU-T188, collided with a U.S. Navy SNB-1, bureau number 39939, on a practice instrument approach to Naval Air Station Key West. The collision and ensuing crashes killed all 34 passengers and five crew aboard the DC-4 and all five crew aboard the SNB. The accident occurred at midday, weather was clear with unlimited visibility, and both flight crews had been cleared to fly under visual flight rules, being expected to "see and avoid" other aircraft; the student flying the SNB was wearing view-limiting goggles, but the other SNB crew were not, and were expected to keep watch. Ground witnesses said that neither aircraft took evasive action prior to the collision, and the Civil Aeronautics Board attributed the accident to the failure of both flight crews to see and avoid conflicting air traffic.
 * 1967: Mohammed bin Awad bin Laden was killed in the crash of a Beechcraft 18 in Saudi Arabia.
 * December 10, 1967: American soul music singer Otis Redding, four members of his backing band the Bar-Kays, the pilot, and another member of Redding's entourage were killed in the crash of Redding's H18, registration N390R, into Lake Monona on approach to Truax Field in Wisconsin. The National Transportation Safety Board (NTSB) was unable to determine the cause of the crash, noting that the left engine and propeller were not recovered. Trumpet player Ben Cauley, the sole survivor of the crash, subsequently revived the Bar-Kays together with another band member who was aboard a different aircraft.
 * September 20, 1973: American folk rock singer-songwriter Jim Croce, four members of his entourage, and the pilot were killed when their chartered E18S, registration N50JR, crashed into a tree shortly after takeoff from Natchitoches Regional Airport in Louisiana.  The NTSB attributed the accident to reduced visibility due to fog, and to physical impairment of the pilot, who had severe coronary artery disease and had run 3 mi to the airport. An investigation conducted for a lawsuit against the charter company attributed the accident solely to pilot error, citing his downwind takeoff into a "black hole" of severe darkness, causing him to experience spatial disorientation.
 * September 26, 1978: Air Caribbean Flight 309, an air taxi flight by a D18S, registration N500L, crashed on approach to Isla Verde International Airport in Puerto Rico, killing the pilot and the five passengers aboard the aircraft and causing substantial property damage and injuries to bystanders on the ground. The pilot could not communicate with approach control and was following directions relayed by local tower controllers, who told the pilot to make a turn and maintain separation from a Lockheed L-1011 that was overtaking the flight, but the pilot did not turn, and the D18S passed underneath and very close to the L-1011. Both the NTSB and a U.S. District Court ruling attributed the crash to the D18S pilot's failure to correctly follow visual flight rules and air traffic control instructions to maintain separation from the much larger L-1011, causing a loss of aircraft control due to wake turbulence. A contributing factor was the pilot's difficulties in communication with controllers.
 * July 4, 1987: Ten people, including all then-current members of The Montana Band, were killed when the pilot of their chartered D18S, N132E, failed to clear a hillside near Lakeside, Montana, while performing a flypast of the venue where the band had performed earlier. The pilot performed an "abrupt" climb and performed a "hammerhead stall" maneuver, reversing direction and entering a dive. The accident was attributed to the pilot's poor judgment and failure to maintain altitude during unauthorized attempted aerobatics.

Argentina

 * AT-11A 3495 – at the Museo Nacional de Aeronáutica de Argentina in Buenos Aires.
 * C-45H 5621 – at the Museo Nacional de Aeronáutica de Argentina in Buenos Aires.
 * C-45H AF-555 – at the Museo Nacional de Aeronáutica de Argentina in Buenos Aires.
 * H18S c/no. BA-752 (former LV-JFH) – at the Museo Nacional de Aeronáutica de Argentina in Buenos Aires.

Australia

 * E18S c/no. BA-81 (former N3781B) - at the Queensland Air Museum in Caloundra, Queensland.

Belgium

 * 3NM floatplane c/no CA-191 (former C-FGNR) – at Pairi Daiza.

Brazil

 * AT-11 4615 - at the Museu Aeroespacial in Rio de Janeiro, Brazil.
 * C-45F 2856 - at the Museu Aeroespacial in Rio de Janeiro, Brazil.

Canada

 * C-45H 459 – at the Canadian Bushplane Heritage Centre in Sault Ste. Marie, Ontario. Tail code CF-MJY
 * 3TM 8034 – at the Canadian Bushplane Heritage Centre in Sault Ste. Marie, Ontario.
 * D18S c/no. A-141 (former CF-MPH) – at the RCMP Academy, Depot Division in Regina, Saskatchewan.
 * D18S c/no. A-142 (former CF-MPI) – at the Bomber Command Museum of Canada in Nanton, Alberta.
 * D18S c/no. A-156 – at the Canadian Warplane Heritage Museum in Hamilton, Ontario.
 * 3N c/no. A-652 (former RCAF 1477) – at the Royal Aviation Museum of Western Canada in Winnipeg, Manitoba.
 * 3NMT c/no. A-700 – at the Canadian Air Land Sea Museum at Toronto/Markham Airport in Markham, Ontario.
 * 3NM c/no. A-710 – at the North Atlantic Aviation Museum in Gander, Newfoundland and Labrador.
 * 3NMT c/no. A-782 (former CF-CKT) – at the Canadian Museum of Flight in Langley, British Columbia.
 * 3NMT c/no. A-872 – at the TransCanada Highway in Ignace, Ontario.
 * 3NM c/no. A-895 – at the Alberta Aviation Museum in Edmonton, Alberta.
 * 3NM c/no. 92-074 - at The Hangar Flight Museum in Calgary, Alberta.

Chile

 * D18S c/no. A-1024 (former FACh 465) – at the Museo Aeronautico y del Espacio in Santiago, Chile.

India

 * D18S VT-CNY former aircraft of the Raja of Mayurbhanj and later sold to Coal India Limited- at the Hotel Mayfair Lagoon in Bhubaneswar, Orissa.

Italy

 * C-45F 6668 – suspended inside the Olbia Costa Smeralda Airport passenger terminal in Olbia, Sardinia. This was the first aircraft owned by Alisarda Airlines and was used in the filming of the movie The Last Emperor.

Japan

 * H18 'JA5174' - the final Beech 18 produced (c/n BA-765), delivered January 1970 to Miyazaki Aviation College, Japan. In use until 1988, now preserved at the College, Miyazaki Airport.

Malta

 * C-45H 8304 – under restoration at the Malta Aviation Museum in Ta' Qali, Malta.

Mexico

 * UC-45J Expeditor "ETL-1320" (S/N): 18 - at the Museo Militar de Aviación.

Netherlands

 * C-45G 51-11665 – at the Aviodrome in Lelystad, Netherlands.

New Zealand

 * AT-11 3691 - at the Museum of Transport and Technology in Auckland, New Zealand.

Portugal

 * AT-11 2504 - at the Museu do Ar in Sintra, Portugal.

Spain

 * C-45H AF-752– at Fundación Infante de Orleans in Madrid, Spain.

Turkey

 * AT-11 Kansan 6390/9-930 – at Istanbul Aviation Museum.

United Kingdom

 * E18S G-ASUG c/no. BA-111 – at the National Museum of Flight in East Lothian, Scotland.

United States

 * AT-11 41‐27561 – at the National Museum of the USAF in Dayton, Ohio. or 42-37493
 * AT-11B 41-27616 – at the Travis Air Force Base Heritage Center at Travis AFB, California.
 * AT-11 42-36887 – at the Barksdale Global Power Museum in Bossier City, Louisiana.
 * AT-11 42-37240 – at the Lone Star Flight Museum in Galveston, Texas.
 * UC-45 42-37496 – at the Wings Over the Rockies Air and Space Museum in Denver, Colorado. This aircraft was originally an AT-11 before being remanufactured.

 * UC-45F 44-47342 – at the Alaska Aviation Heritage Museum in Anchorage, Alaska.
 * C-45G 51-11467 – at the EAA Chapter 1241 Air Museum at the Florida Keys Marathon Airport in Marathon, Florida.
 * TC-45H 51-11529 – at the Tri-State Warbird Museum in Batavia, Ohio.
 * C-45H 51-11696 – at the Museum of Flight in Seattle, Washington.
 * C-45G 51-11795 – at the Air Mobility Command Museum in Dover, Delaware.
 * C-45G 51-11897 – at the Castle Air Museum in Atwater, California.
 * C-45H 52-10539 – at the 1941 Historical Aircraft Group Museum in Geneseo, New York.
 * C-45H 52-10865 – at the Travis Air Force Base Heritage Center at Travis AFB, California.
 * C-45H 52-10893 – at the National Museum of the USAF in Dayton, Ohio.
 * UC-45J 09771 – at the National Museum of Naval Aviation in Pensacola, Florida. This aircraft was converted from the last civil Beech 18 built prior to WWII.
 * UC-45J 51225 - gate guard at Commemorative Air Force Lone Star Wing, Harrison County Airport (Texas).
 * UC-45J 23774 – at Laughlin AFB in Del Rio, Texas.
 * RC-45J 51233 – at the Tennessee Museum of Aviation in Sevierville, Tennessee.
 * UC-45J 51242 – at the CAF Central Texas Wing in San Marcos, Texas.
 * UC-45J 51291 – at the Aerospace Museum of California in Sacramento, California.
 * UC-45J 51338 – at the Minnesota Air National Guard Museum in St. Paul, Minnesota.
 * S18D c/no. 178 – at the Beechcraft Heritage Museum in Tullahoma, Tennessee.
 * D18S c/no. A-935 – at the Beechcraft Heritage Museum at Tullahoma Regional Airport in Tullahoma, Tennessee.
 * C-45H AF-824 – at the Beechcraft Heritage Museum in Tullahoma, Tennessee.
 * E18S c/no. BA-453 – at the Beechcraft Heritage Museum in Tullahoma, Tennessee.
 * H18 c/no. BA-670 – at the Lone Star Flight Museum in Galveston, Texas.

title: Beechcraft Model 18


text:
Claire Davenport

Claire Bernice Davenport (24 April 1933 – 25 February 2002) was an English character actress well known for her large physique.

Life and career
Davenport was born on 24 April 1933 in Sale, Cheshire, and began acting in 1961 with a theatre role in Caesar and Cleopatra at the Playhouse in Oxford.

Her film work includes roles in Return of the Jedi (as Yarna d'al' Gargan, originally billed as "Fat Dancer"), The Return of the Pink Panther, Adventures of a Plumber's Mate, Carry On Emmannuelle, The Tempest and The Elephant Man. On television, she appeared in The Dick Emery Show, Remington Steele, Doctor Who, Minder, George and Mildred, Robin's Nest, Fawlty Towers and at least three episodes of On the Buses, among others. She also made a cameo appearance in an episode of Mind Your Language. Among the last of her television appearances was a 1993 episode of The Smell of Reeves and Mortimer.

Death
Davenport stopped working after suffering a series of strokes in the 1990s. She died at the age of 68 in London on 25 February 2002 (not 4 March, as often stated) from kidney failure.

title: Claire Davenport


text:
User:Newkidd

Unless you keep your language less dirty, the account will be blocked. mikka (t) 16:33, 14 Jun 2005 (UTC)

title: User:Newkidd


text:
Blackmer v. United States

Blackmer v. United States, 284 U.S. 421 (1932), is a decision of the Supreme Court of the United States.

Harry M. Blackmer was a United States citizen resident in Paris. Blackmer was found guilty of contempt by the Supreme Court of the District of Columbia for refusing to appear as a witness for the United States in a criminal trial, which was related to the Teapot Dome Scandal, after being subpoenaed.

Blackmer was subsequently fined $30,000 and the costs of the court. Blackmer challenged the fine under the due process clause of the Fifth Amendment.

The Court unanimously ruled against Blackmer, with Chief Justice Charles Evans Hughes delivering the judgment and opinion of the Court and Justice Owen Josephus Roberts not participating.

Chief Justice Hughes, in delivering the opinion of the Court, stated "[n]or can it be doubted that the United States possesses the power inherent in sovereignty to require the return to this country of a citizen, resident elsewhere, whenever the public interest requires it, and to penalize him in case of refusal." Also, "[i]t is also beyond controversy that one of the duties which the citizen owes to his government is to support the administration of justice by attending its courts and giving his testimony whenever he is properly summoned."

title: Blackmer v. United States


text:
Category:Square Enix media files

Media pertaining to Square Enix, Anime, Manga, computer and video games, and films.

__NOGALLERY__

title: Category:Square Enix media files