text:
Wikipedia talk:Poképrosal

How do you get Pikachu on a bus? Poke 'im on.

Meh...
I would seem to be the only person who likes the articles specialized for each Pokémon just the way they are now, and who doesn't want a mass move-reorganization-etc. -_-; Almafeta 19:27, 27 May 2005 (UTC)
 * Nope, you're not alone. As soon as a poll is created for this, I will be voting against the proposition. --Pidgeot (t) (c) (e) 22:42, 27 May 2005 (UTC)
 * But the way it is now, some have even been nominated for deletion! While in those cases the Vfd has dissolved into "hold off until Poképrosal's finished" I don't know what fate they will meet when this is over and they are unmerged... Master Thief GarrettTalk 02:57, 28 May 2005 (UTC)
 * Meh. Over a half-million articles in the English wikipedia, and to some people the idea of a page per Pokémon is so abhorrent that they intend on replacing 380 articles with 1 table and 5 sections each with 380 redirects to 1 page that has 380 tables and 1900 sections.  I just don't get it.  -_-;  Almafeta 08:31, 28 May 2005 (UTC)

 * Yes! I agree. This is merging is just "busy work" to keep wikiaddicts doing something. Instead of doing merging, come to 2004 Encyclopedia topics and create content and fill in real content holes! Pcb21| Pete 09:29, 28 May 2005 (UTC)
 * It might be better to make pages on the Pokemon universe, etc., its own Wikipedia Project (poke.wikipedia.org?), if people are going to continue to attempt to delete these pages or attempt to move them into ambiguation pages. Almafeta 00:41, 30 May 2005 (UTC)

 * There is a Pokebook in Wikibooks that should cover the games in great detail (including map layout, walkthrough etc) iirc. Radiant_* 07:17, May 30, 2005 (UTC)

=Archive=

Proposal to merge
Wikipedia contains several hundreds of articles about individual Pokémon. However, the vast majority of these are stubs (see Category:Pokémon stubs), containing only a table of statistics such as the one to the right, and one or two lines of text.

Unfortunately, this does not make the information very accessible. If one wanted to compare statistics of a number of Pokémon, there is no convenient way of doing so. Also, information given on a basic Pokémon is often duplicated in the articles of evolutions thereof.

While certain Pokémon are obviously more notable than the rest (e.g. Pikachu, Mewtwo), arguably it is not feasible to write a lengthy treatise on each individual one.

The WikiProject Pokédex has not been very active lately, with less than 25 edits to project and talk page combined, since January 1st.

I believe, therefore, that the information on most individual Pokémon would become more legible and comprehensive if the relevant articles would be combined in groups. For instance, taking each subcategory of Category:Pokémon species by type, and merging those articles into a list.

See also the semi-policy on characters from fiction, WP:FICT.

Since this is rather broad in scope, I figured an RFC would be appropriate. I now yield the floor to comments. Radiant_* 12:21, Apr 22, 2005 (UTC)

Discussion
In theory, this is something I could agree with, but only as long as no information was lost, and people could feel free to split out articles if there was enough material. I fear people would use this as an excuse to remove what they see as "Poke-cruft". Meelar (talk) 13:13, Apr 22, 2005 (UTC) However, why shouldn't each POKéMON have it's own article? To quote your semi-policy:
 * It should be pretty simple to come up with a tabular format for these merged subsets of Pokéstuff so that no information is lost. I personally would like to see such stubs deleted, but this proposal is very agreeable. I don't have a problem with articles on individual Pokémon, per se, but stubs such as these have no encyclopedic value, as they are just statistics tables. android↔talk 13:21, Apr 22, 2005 (UTC)
 * I like the suggestion, but I think it's better suited for Wikibooks.
 * Fictional characters which are cultural icons transcending their appearance in a particular work of fiction, or who cannot be neatly tied to a particular work of fiction or fictional universe deserve articles of their own, regardless of other circumstances.
 * POKéMON is everywhere, and there is bound to be at least some merchandise for most, if not all, of them. In my opinion, this is enough to be transcending.--Pidgeot (t) (c) (e) 14:52, 22 Apr 2005 (UTC)
 * Unless you count trading cards, I seriously doubt there is 'at least some merchandise' for most Pokemon. Please provide some evidence thereof. Pokemon can be neatly tied to a particular fictional universe, even if that universe consists of several games, cartoons and movies. I agree Pikachu is transcending as a cultural icon, and possibly two or three others, but not most of them. By nature, it's not possible for all or even most characters in a setting to be transcendent. Radiant_* 15:10, Apr 22, 2005 (UTC)
 * I agree with Radiant. That's a rather curious reading of WP:FICT – all Pokémon exist within the same fictional universe and can be neatly tied to it. Using "has merchandise available" to define "transcendant" is a very bad idea. Take, for example, The Simpsons. IIRC, there are exceedingly minor characters that have their own action figures. Homer and Bart obviously deserve their own articles, but are Lionel Hutz, Bumblebee Man, and Professor Frink transcendant characters? I think not. android↔talk 17:43, Apr 22, 2005 (UTC)
 * Well then, how should the word be defined? Merchandise is, to me, an appearance outside of the characters' normal environment (the GB games). If this is not how transcendent is to be understood, then a different word should be used, since it's the only way you can apply one of the meanings of transcendent to a fictional universe.
 * (For the record, the bolded text was only placed in the quote to match the formatting used at WP:FICT. It was not supposed to imply that I thought part had a special significance.) --Pidgeot (t) (c) (e) 19:18, 22 Apr 2005 (UTC)
 * Ah, see, I thought you had emphasized those words. In any case, we both glossed over the term immediately preceding transcendant: cultural icon. Superman, Homer Simpson, and perhaps Pikachu are cultural icons; individual minor Pokémon are not. android↔talk 19:29, Apr 22, 2005 (UTC)
 * "Transcendant" is something like Dopefish. The only canonical appearance of the Dopefish was in the "Well of Fishes" level of Commander Keen 4.  However, it's had cameo appearances in games such as Quake, Descent III, Max Payne, and Wacky Wheels, it's been referred to in numerous other places, and the phrase "Dopefish lives!" and Dopefish forum avatars are relatively common sights. --Carnildo 19:48, 22 Apr 2005 (UTC)
 * Since most of the articles are stubs, it should be easy to come up with a horizontal-format table such that groups of related Pokémon can be merged into a single article, with each Pokémon having a table and a one- or two-line description. --Carnildo 17:57, 22 Apr 2005 (UTC)

Before anything is done, don't forget about Pokémon. The original intent was for Pokémon to be a game guide and ONLY a game guide, and the Wikipedia articles be on the parts of Pokémon that are not tied to the game (eg. the anime). There will inevitably be some parts that will interact with each other, while some parts of the Wikipedia articles will be removed once the books end has that information (note the particular inconsistencies of the infobox pages acrosss Pokémon pages). To this end, even the tables may vanish somewhat, and some articles may have little left. Of course, being a member of the Wikiproject, I feel that ideally each Pokémon should have their own page, but then there are practical considerations.

Anyways, Pikachu is certainly notable, and by extension their other forms. Starters and legendaries are also notable because of their nature. Porygon is notable for the seizures, and Jigglypuff is the most frequently-seen recurring anime character not associated with any particular trainer. These will have to be kept at the very least. (Some may consider keeping articles on team members).

Most Pokémon do have some form of merchandise associated with it outside of the video games and the TCG: there's the V-Trainer and various action figures (both legitimate and bootleg, as well as "fan-art").

kelvSYC 01:42, 23 Apr 2005 (UTC)

 * If there's a Wikibooks Pokémon game guide, then I suggest we transwiki all the Pokéstubs over there and delete them from Wikipedia, leaving a single "List of Pokémon" and an article on Pikachu. --Carnildo 02:10, 23 Apr 2005 (UTC)
 * Sounds like a plan to me. android↔talk 02:35, Apr 23, 2005 (UTC)

I strongly support this proposal. Recently similar action has been taken by User:Master Thief Garrett in the Zelda characters space (see Category: Legend of Zelda characters), and I consider it a vast improvement. The essential argument you're making is twofold:
 * 1) That individual Pokemon are not notable. Merchandise is not by itself evidence of notability. Notability can be seen as a measure of roughly how many people are familiar with a concept. Coca-Cola and George Washington are highly notable. Certain Simpsons episodes are fairly notable. Red-black trees are less notable. The mathematician Nicholas Mercator is hardly notable at all, but still has an article for other reasons. Although many people are familiar with esoteric Pokemon, these are only a tiny fraction of the number of people familiar with more common subjects.
 * 2) That it is not likely that a detailed article will be written on each Pokemon. This is due in part to their lack of notability (less people are familiar with them or care about them, so less are around to write about them), but it's also due to the limited amount of information provided by their creators and marketers, which can be easily summed up in a few paragraphs. However, I also support keeping the most famous Pokemon, such as Pikachu, in their own articles, in the same way that Link, Zelda, and Ganon still have their own articles. Deco 02:25, 23 Apr 2005 (UTC)

 * WOW! I never thought I'd end up being an example to others by doing something so sensible! I had similar plans with all these Pokemon, but, again, I feared mass fanboy reverts if I tried to "un-important-ise" a particular beloved character. But with this merging proposal, a general consensus viewpoint can emerge to combat such issues. Good old democracy. Master Thief Garrett 04:19, 23 Apr 2005 (UTC)
 * The mergification of the minor Zelda articles is a definite Good Thing™. android↔talk 04:30, Apr 23, 2005 (UTC)

 * I don't think that this proposal is strictly necessary. What the Wikiproject suffers from at present is a lack of interest - if more members could be persuaded to write articles that conform to a certain standard, each pokémon could have a detailed article and infobox. I would also support the notion that the Wikipedia and Wikibooks Pokédex should be greatly interlinked, to provide a more concise resource. As the spirit has now taken me, I may start to revamp the project and attempt to get more people interested. If there are any objections, let me know here or discuss it on the Wikiprojet's Talk page. CNash 16:29, 29 Apr 2005 (UTC)
 * Additionally: The vast majority of Pokémon stub articles have been created by an unregistered user (132.70.50.117), who has merely created the page with only the infobox and a stub template visible. (In the process, he hasn't followed some of the guidelines set out in the Wikiproject, but that's not the point.) This forced the remaining Wikiproject contributors to expand the articles before a call for their deletion or reorganisation was made - which we did not accomplish. I'll start blitzing through and see what I can fix up. CNash 22:26, 29 Apr 2005 (UTC)

 * While I am no fan of Pokemon- I rather despise it- I believe that these stubs should be merged. In my opinion, precedent is set by such articles as List of minor Star Wars characters: for the myriad relatively insignificant articles, there should be a composite merged page, but more prominent or major subjects (pokemon in this case) deserve to be articles in their own right. --M412k 01:11, 25 May 2005 (UTC)

categorise by type? or by species?
One possible categorisation idea is to have them listed by type (Electric, Bird, Bug, etc.) on core pages, rather than the [[Category: ]] sections that link to them at the moment. BUT the problem with this is that most if not all Pokemon are dual-type, and many can even learn attacks from multiple types other than their two core ones. So unless there is going to be a LOT of cross-linking, how will it be managed...? I really, really don't know. Master Thief Garrett 04:19, 23 Apr 2005 (UTC)
 * Alphabetically? If there's no characteristic of Pokemon that would make categorization easy, that might be the only way to go. android↔talk 04:31, Apr 23, 2005 (UTC)
 * hmmm... good thought, but you ideally want them together. Mareep evolves into Flaaffy, so with all the Electric-type ones together you could just scroll up/down to see the members of Mareep's evolutionary chain. Arranged by name, this would require you to click through to another page, which means more manual cross-referencing is required. Categorising by type would likely be a lot less work for contributors than an alphabetical arrangement would be. Both of these ideas have their advantages, as well as their drawbacks. Master Thief Garrett 04:37, 23 Apr 2005 (UTC)
 * Another idea is to categorise by species (Mouse, Wool, Bird, Patient, Seed, etc.) but the problem is that there are problably 80+ category description types. Some of them are shared, but would that divide the list up too much? Master Thief Garrett 04:43, 23 Apr 2005 (UTC)
 * Since there's too many species, and many are dual typed, I think the best solution is alphabetizing - but then it should be alphabetized by basic form, and all evolutions listed under the basic. Thus Flaaffy goes under Mareep, rather than under F. We can use colors (maybe) or intend-with-bullets * to indicate stage. Radiant_* 09:26, Apr 25, 2005 (UTC)
 * Better to have a few dozen broad categories than many more dozens of individual stubs. I'm for anything that will result in a simple, concise package that avoids an overload of excessively short articles. -- 8^D BD2412gab 00:21, 2005 Apr 28 (UTC)
 * Having looked around a few fan-run Pokedexes, they categorise Pokemon by their primary element type ONLY. Therefore, we could follow suit. Master Thief Garrett 00:52, 28 Apr 2005 (UTC)

new merged sections to be made too long by stat tables?
One other problem I see is with these tables. Now while they are very clear, very usable, and very complete, the problem is they take up a lot of space. So unless non-applicable columns are cut (like, say, Shiny, which ONLY applies to Gold/Silver/Crystal Pokemon) I think that what should have been a short merged list of non-noteworthy Pokemon will end up as pages and pages of stats. What is to be done about this? Master Thief Garrett 04:19, 23 Apr 2005 (UTC)
 * We should move the stat tables out of Wikipedia entirely, into the Pokémon wikibook. --Carnildo 06:33, 23 Apr 2005 (UTC)
 * OH! Of course! I hadn't thought of that. Yes that solves that issue...
 * --unless of course others disagree, if so please state your reasoning here, and quickly, before such changes are made to the content that it is "too late" to complain. Master Thief Garrett 06:53, 23 Apr 2005 (UTC)
 * The essential problem with this is that there's info in the stat tables not stated in the text which might still be useful in the consolidated articles. Another solution is to create a new stat table template taking the same arguments which produces a compact inline horizontal table or even a templated paragraph (a la Rambot). Then just change the template name during merging. Use subst if desired to make the template go away after saving. Deco 06:56, 23 Apr 2005 (UTC)

 * How about this for a table:

 * Carnildo 07:16, 23 Apr 2005 (UTC)

 * Good, good, very very good. I prefer sidebars of course, since they're, well, at the side(!) and don't get in the way of the body text, but seeing as there's no body text for it to interrupt that would be a very good solution! Well done! Master Thief Garrett 08:04, 23 Apr 2005 (UTC)

 * Let me give that a try...
 * Not bad eh? I do agree that most statistics aren't particularly encyclopedic (esp. since they differ between the card game and the computer game) but the table should be able to host species and type and related stuff, possibly using abbreviations for types. Radiant_* 09:24, Apr 25, 2005 (UTC)
 * Problem: That table is wide enough as it is, but doesn't include metric measurements - those used in all non-English POKéMON games. Maybe leave out the species, as was suggested above? --Pidgeot (t) (c) (e) 04:39, 28 Apr 2005 (UTC)
 * Okay. Radiant_* 07:19, Apr 28, 2005 (UTC)

Keep in mind that it has been discussed in the Wikiproject's talk space that video game statistics (including height and weight) are not encyclopedic, and should be removed. kelvSYC 03:24, 18 May 2005 (UTC)

Infobox Template
I recomend usage of templates, that way its uniformal. --Cool Cat My Talk 11:20, 24 Apr 2005 (UTC)

 * Yes, templates would of course be used to avoid any problems. However as said I slightly prefer the horizontal example above, so we don't get pages and pages of stat charts and nothing else. Master Thief Garrett 12:02, 24 Apr 2005 (UTC)
 * Easier done than said ;), However I was wondering why? --Cool Cat My Talk 05:56, 25 Apr 2005 (UTC)
 * With the difference between Pokémon up to 151 (Mew) and the later Pokémon (with the Special stat), and the Hoenn numbers, we're talking about several different templates. However, we could build them if we really want to. User142 09:58, 27 Apr 2005 (UTC)
 * Why? The goal here is to get the "game guide" information on individual Pokémon out of Wikipedia and into the Pokémon Wikibook. --Carnildo 18:06, 27 Apr 2005 (UTC)
 * It's already at Pokémon, well before all the infoboxes at Wikipedia were done. kelvSYC 03:27, 18 May 2005 (UTC)
 * I see most "pokemon" being nothing more than a stub after information is placed to the table, maybe a description of the creature may comrimise the actual article or history. It may be best to have the text and the template after instead of a side bar. Propbably there isnt enough to say about these creatures more than a stub. --Cool Cat My Talk 06:00, 25 Apr 2005 (UTC)

 * Are we not alowed to use images by the way? --Cool Cat My Talk 06:01, 25 Apr 2005 (UTC)

 * You are right that they will be eternal stubs. I would think the template should go below. The template should NOT incorporate the image, that should go to the right of the description, which will be struggling to be more than a few lines as it is.

 * I don't really know about the copyright of Pokemon character representations, but I assume they fall under Fair Use. Regardless, if the images are already uploaded then feel free to use them!!! If they turn out to be violations someone will have the image deleted. That's not your problem at all. Images are supposed to be uploaded with one of various Fair Use rights systems. Other users assume good faith on the part of the that uploader, that they fulfilled the restrictions correctly, and use the image straight away. It is only if *you* upload a violatory image yourself that you will recieve any sort of blame for its use. So don't worry! If it's here, make use of it! Master Thief Garrett 07:51, 25 Apr 2005 (UTC)

 * The images arguably fall under 'fair use'. I think they don't fit well with the tables though because of sheer size. Let's see... we could just use a sample number of images (which makes the 'fair use' even fairer). Or we could make each pokemon's name in the table a link to its image on /commons. Or we could add a separate page which is the pokemon image gallery, which is a matrix of images with proper names underneath. Radiant_* 09:28, Apr 25, 2005 (UTC)

 * IIRC, they seemed to have been on VFD on numerous occasions... kelvSYC 03:27, 18 May 2005 (UTC)

 * Um, that's one idea, but if someone casually comes looking up a Pokemon they've just read about they would surely want to actually SEE it not just read stats that mean nothing to an outsider. A separate gallery would require yet more click-thrus. Anyway there are lots of high-profile fansites using images all over and I don't see Nintendo shutting them down like they did the Zelda and Mario fan remake projects... Master Thief Garrett 11:06, 25 Apr 2005 (UTC)
 * Okay, good point. But most Pokeimages aren't that large... we could make the table rows a bit higher and allow room for a small pic. Radiant_* 11:33, Apr 25, 2005 (UTC)

 * The fair use assumption for these characters is most tenuous. Nothing horrific will happen as long as we have OCILLA, and we could strengthen the case for fair use by using low resolution images, using them for noncommercial purposes, and if they contribute significantly to the article, but keep in mind that they will almost certainly be omitted from redistributions in electronic and print form. Deco 09:29, 29 Apr 2005 (UTC)

 * Commons cannot have any copyrighted images. I think an image size thumb should be sufficent. Number of images is not how one determines fair usage. There is Star Trek, we should be perhaps paid for advertising. I do not personaly care either way, I was asking that so that I can modify the template to have an image or not by default. We would need a proper naming sceme if that would be the case, (like Template:flag2) --Cool Cat My Talk 02:46, 2 May 2005 (UTC)

...
Here is a flatter version:

I like this one better than the current "pseudo-template" in use for most of the Pokémon. If I can find my copy of the Complete Kanto-Johto Reference, I'll start working on some of the Pokémon stubs 001-251. --Brian Ryans 15:12, 30 October 2005 (UTC)

...

 * Ad-like? Indeed it is, I almost expect to see "buy now from Amazon.com" links beside those video listings! Anyway, as for the image, I'd say you should definitely have an image as the default. As I said above, if a non-Pokefan comes across it they want to know what it looks like.
 * I'd maybe put Shiny under General. It isn't really biological as sometimes traded Pokemon mysteriously gain Shiny-ness. Plus it would make the list more even and thus shorter. Perhaps the physical elements should be side by side, "Height/Weight"? That would also make it shorter. Master Thief Garrett 03:49, 2 May 2005 (UTC)
 * Your last edit to it somehow made it different. Now I've got a horizontal scrollbar... Master Thief Garrett 03:52, 2 May 2005 (UTC)

It normaly takes about 10 edits to make it look good. :) --Cool Cat My Talk 03:57, 2 May 2005 (UTC)

I am not a poke fan so I am merely working on a table. Correct anything if you like ;) --Cool Cat My Talk 04:00, 2 May 2005 (UTC)

 * Gosh, I can't be bothered handling this code (I'm more used to HTML) but here's an example I bunged together. Master Thief Garrett 04:18, 2 May 2005 (UTC)

All pokemon pages should be named as: Pokedex:pokemon name. This way we will evade any posible conflicts. Redirects are also recommended. --Cool Cat My Talk 05:02, 2 May 2005 (UTC)

 * Yes, definitely. Shouldn't there be a "é" in it though? Anyway, I think the images should be named "Pokemon:name" or "Pokedex:name" so the images don't get "lost" and they're all grouped as much as possible (when you look at the Special:Images page, etc.) Master Thief Garrett 05:51, 2 May 2005 (UTC)
 * I'm pretty sure you can't use colons in file names on UNIX systems, and you definetively can't on Windows (which most people use). Therefore, that naming scheme would be impossible to implement for images.
 * The standard is to use name (Pokémon) (see Mew), assuming you want name to be the (potential) disambiguation page. (There are instances where you don't.) Pokedex:name would only be suited for Wikibooks, where this is a standard way of indicating topic.
 * Don't forget what WP:D states, though: "Do not disambiguate, or add a link to a disambiguation page, if there is no risk of confusion." Unless there really is anything to confuse, you should be leaving article names as-is - for example, Pikachu should stay at Pikachu, since there's nothing to confuse it with. --Pidgeot (t) (c) (e) 20:50, 2 May 2005 (UTC)
 * Unix file systems allow any character except the forward slash "/" and the null character (character #0) to be used in a filename. That said, putting unusual characters into filenames on Wikipedia is generally a bad idea, as web browsers frequently don't handle them properly. --Carnildo 22:47, 2 May 2005 (UTC)
 * I have no idea why I said : because of course  is the way it's done here. But can the template engine handle it? I mean, if someone searches for Pikachu will the current page work, or will we have to make a new redirect from there to Pikachu (Pokemon)? I mean, can the naming structure mutate, or does it HAVE to be  (Pokemon) ? Master Thief Garrett 00:30, 3 May 2005 (UTC)
 * The structure is per definition mutating, since indicates disambiguation. WP:D says we should leave article names as-is unless there is need for disambiguation - that is, articles should be at Pikachu, Hitmonlee, etc., rather than Pikachu (Pokémon), Hitmonlee (Pokémon), etc., so long as we don't have anything else by that name to write about - and even then, the disambiguation page might be better placed at Pikachu (disambiguation), depending on what the other thing is.
 * When moving a page, a redirect will automatically be left behind. That way, Pikachu will automatically go to Pikachu (Pokémon) after the move, without us having to do anything else. --Pidgeot (t) (c) (e) 01:55, 3 May 2005 (UTC)
 * Wow, the new version looks great! Master Thief Garrett 05:51, 2 May 2005 (UTC)
 * Gah, the headers refuse to line up. I think I'll write it in HTML and see if these HTML>Wiki converters can do a better job... Master Thief Garrett 08:05, 2 May 2005 (UTC)
 * Did some more more fiddling, the headers now line up. Sort of. Better than they used to anyway... still testing to see how this can be optimised for lower screen sizes... Master Thief Garrett 09:13, 2 May 2005 (UTC)
 * Works well under IE but slightly differently under Firefox. Works perfectly in 800x600 on both, will have to alter some things to make 640x480 works. It almost fits, but not quite. Might have to abbreviate something... Master Thief Garrett 00:30, 3 May 2005 (UTC)

If anyone needs any info for the infoboxes, possibly to expand them, you can get pretty much everything from here: http://eevee.racso.com/, in case you needed to know. Or anything. I hope this is the right place to mention it. RickGriffin 03:03, 3 May 2005 (UTC)

Naming Convention example: Pokédex:Pikachu, Image:Pokédex:Pikachu. Also Pikachu should redirect to Pokédex:Pikachu, etc. we can "move" pages from Pikachu to Pokédex:Pikachu, would create redirects for us. It is imperative that it be : as ignores all material before :, while that can be fixed by simply adding a new dataitem it defeats the point of an infobox. --Cool Cat My Talk 12:46, 3 May 2005 (UTC)

 * Strongly oppose use of any colons at all. The Pokédex: prefix is an indication of disambiguation, (which is usually done using on Wikipedia) which is not needed for most POKéMON. You don't expect an article like HTTP to be at Protocol:HTTP (or HTTP (protocol) for that matter), do you? Additionally, I'm not sure the Image namespace is as flexible as you want it.
 * For grouping, this is done through categories, not prefixes. --Pidgeot (t) (c) (e) 16:25, 3 May 2005 (UTC)
 * As I explained it is necesary for technical reasons. I cannot put slashes in images. Collons are fine because reprots everything after last colon.  will print the ugnly material inside (pokemnon or whatever) and will make a mess. You will make my, programmer/template designers, job expodentialy eassy if you use colons. Else I am not sure how do do this without several extra inputs. --Cool Cat My Talk 20:27, 3 May 2005 (UTC)
 * Exactly which inputs would you need? If it's for the images, couldn't you hardcode a prefix and suffix into the template? --Pidgeot (t) (c) (e) 21:06, 3 May 2005 (UTC)
 * I don't understand the problem. The page currently says "Missing image Poképrosal.png". It's cutting off the "Wikipedia:" already, so can't we use this with the Pokemon pages as we've got them right now? If I put this on Pikachu, it would look for Pikachu.png, right? Why does there have to be a naming convention? As long as the image name matches the page name, it always gets the right picture linked to it, right? We might have to depose a few of the inadequate pictures already holding those core namespaces, but other than that it should work... shouldn't it? Master Thief Garrett 22:43, 3 May 2005 (UTC)
 * As far as all this "Pokédex" stuff goes, shouldn't it be going into the Wikibooks Pokémon game guide, leaving only the basics on Wikipedia? --Carnildo 18:16, 3 May 2005 (UTC)

...

 * No, the Jean-Luc Picard would belong to same category. --Cool Cat My Talk 20:27, 3 May 2005 (UTC)
 * Please elaborate on what Jean-Luc Picard has to do with only having POKéDEX details in Wikibooks. --Pidgeot (t) (c) (e) 21:06, 3 May 2005 (UTC)
 * We have a database of Star Trek characters, various other anime etc. Why is there a problem with this animes characters? --Cool Cat My Talk 20:59, 6 May 2005 (UTC)

...
Bottom of the page must have a link box linking to the entier contents of pokedex. --Cool Cat My Talk 13:14, 3 May 2005 (UTC)
 * Yes, that's obvious! But should it be a template so people just type or whatnot, or does it have to be a copy-'n'-paste? Master Thief Garrett 22:43, 3 May 2005 (UTC)
 * Templates I say, one template having all pokedex entries. --Cool Cat My Talk 20:59, 6 May 2005 (UTC)

Wikibooks?
I see there has been some talk of moving all the content to wikibooks. I proposed somthing like this a while back. I will say it again in the hopes that it gains some traction this time. We port these article (all of them but the most notable) over to wikibooks. Start a new wikibook (or merge it with the old one which currently has limited scope) dedicated to pokemon. Then we redirect all pokemon to the main pokemon article (or the list of pokemon). It's like starting an encyclopedia dedicated to pokemon. If the book is only about the pokemon univerese (as opposed to a universe within the real universe) then every pokemon species is notable enough to have a page. A solution? Maybe we can do this with other subjects (Simpsons episodes? or Star Trek battles?) I think this a better sollution to creating a new namespace or whatever you want to call "Pokedex:" BrokenSegue 01:35, 4 May 2005 (UTC)

 * Thats inheritely pushing human knowlege to other wiki projects unnecesarily. You want to push all fictional content out of wikipedia? I think and bluntly say that usage of a namespace is best. Be a uniter not a divider, unite human knowlege :D --Cool Cat My Talk 21:01, 6 May 2005 (UTC)

 * I consider myself an organizer. By moving the articles and discusion of articles on individual Pokémon to a Pokémon wikibook, it collects all the information in one place, rather than diluting it in the other half-million encyclopedia articles.  That makes it easier for potential contributers to find. --Carnildo 21:29, 6 May 2005 (UTC)
 * Do I want to "push all fictional content out of wikipedia"? No. Of course not. I want to put huge lists of repeated information to a more concentrated and useful place. There are things which are very specialized which would do better elsewhere. The content still exsists on a wiki so I don't see why this is a threat to content. A namespace is meant for a class of information. Images, Articles or Wikipedia (Some other wikis have a source namespace for specific source information [poor man's wikisource]). A pokemon namespace seems silly. It is a specfic subject not a class of data. Moving the content to wikibooks makes more sense (do you want to make a cookbook namespace?). BrokenSegue 21:46, 6 May 2005 (UTC)
 * In a sense, then, Wikibooks would be like the EB Macropaedia. RickGriffin 21:39, 7 May 2005 (UTC)
 * What's EB Macropaedia? I can't find anything about it online? BrokenSegue 01:38, 8 May 2005 (UTC)
 * Encyclopedia Britannica is organized into two sections. The first dozen or so volumes, called the "Micropedia", are relatively short articles on a wide range of subjects.  The maximum depth any of them goes into is similar to that of the top-level article on World War II.  The next dozen and a half volumes, called the "Macropedia", are extremely detailed coverage of a small number of subjects -- think Category:World War II and all subcategories. --Carnildo 04:43, 8 May 2005 (UTC)
 * I imagine the book as an encyclopedia of pokemon. In that way every pokemon and charcter would be notable (as all the species are notable here). BrokenSegue 14:45, 8 May 2005 (UTC)
 * Recall that Wikibooks is a source of instructional material - it's not a Macropaedia of any kind (Wikibooks is not Wikipedia), and treating it as such would likely have the modules involved put up on VFD there, and as an admin there, I'd have no hesitation in deleting it. kelvSYC 03:35, 18 May 2005 (UTC)
 * Then let's change the purpose and definition of wikibooks. This link is Broken 21:35, 1 Jun 2005 (UTC)
 * I think this sort of organization is a good idea in many ways, but will never happen for political reasons — threatening to move someone's content to Wikibooks is as good as threatening to delete it, with Wikibooks as relatively unpopular as it is. Deco 23:47, 6 May 2005 (UTC)
 * Hopefully if we began to integrate Wikibooks with Wikipedia, Wikibooks will be become more popular and thus less objectionable for moving material. I agree however, politics ruins everything. BrokenSegue 01:17, 7 May 2005 (UTC)
 * Why is Wikibooks unpopular? I thought the whole idea was that you could ramble on and on with FAQ-ish details such as would never fit an article? So why's it unpopular?
 * Or perhaps we need it moved here into a "Wikibooks:" namespace... Master Thief Garrett 04:22, 7 May 2005 (UTC)
 * For the same reason Wiktionary, Wikisource, and a bunch of tiny Wikipedias are unpopular. They came along later, they have less contributors, they don't have high Alexa and Google ranks, they're not in the papers, and they didn't get Slashdotted twice. But hey, everything grows in time. I don't think moving Wikibooks into Wikipedia would work though - the benefit of Wikipedia's flat structure is that it's great for internal linking and creating a sophisticated web of related concepts, while Wikibooks has a strong hierarchy. Deco 09:11, 7 May 2005 (UTC)
 * Why is Pokémon limited in scope? Recall that Pokémon was designed from the ground up to be part of Game Guides and Strategy - adding stuff that is irrelevant to the game would pervert its original intention.  Furthermore, if you plan on dumping anime info to Wikibooks, why would you need instructional material on a TV series such as this? kelvSYC 03:32, 18 May 2005 (UTC)

"Pokémon:" namespace
Do you have ANY idea why I request a namespace? --Cool Cat My Talk 15:12, 7 May 2005 (UTC)
 * To tell you the truth, not entirely. You said that it was needed so that "we will evade any posible conflicts." I have gathered that this naming system will somehow make the templates and images more functional (in combining them all into one page). I don't see why such a move is ncessary. The content in the tables is trivial and should be in the current wikibooks project. Any other content could be ported over to wikibooks. If I have missunderstood your motives I'll gladly change my position on the matter.  BrokenSegue 15:32, 7 May 2005 (UTC)
 * I think I do, but it's a bad choice IMO, since it's a highly non-standard way of doing things. Also, it's not very intuitive to uninitiated users - once POKéMON Diamond/Pearl are released, there will be people creating new pages without knowing about the virtual namespace. And it would look out of place on disambiguation pages (using Mew as an example):

The word mew can have several meanings: (...) (...)
 * A Pokémon of that name.
 * A band from Denmark of that name.

 * I think the very least you could do to argue for the namespace idea is tell us why it's so much easier to make your template with a virtual namespace, rather than using the extra inputs, how many extra inputs would be needed, as well as which ones.
 * I'm pretty open to ideas, but unless you can give good arguments for why this is a better solution, I see no reason to break standard policy and do pre-emptive disambiguation. --Pidgeot (t) (c) (e) 18:29, 7 May 2005 (UTC)
 * We can only have a uniformal database with a namespace for data elements such as mew. The template asumes page name to be the name of the creature and also atempts to load the image that carries.  returns the currenct articles page name.

 * As you can see  does not display "Wikipedia:" but Poképrosal ignoring : and everything before it. Thats why namespace is better than / or --Cool Cat My Talk 06:37, 9 May 2005 (UTC)
 * The database stores the namespace seperately from the article. So in the database, this article is actually called "Poképrosal", and has its namespace value set to whatever value maps to Wikipedia. With a virtual namespace, however, it would be stored as part of the name - try going to Pokemon:Mew and write, then preview. You'll get Pokemon:Mew, since that's what the article name field contains (or rather, would contain) in the database.
 * In other words, unless you can get an ACTUAL namespace created (which I consider extremely doubtful), your Pokemon:* articles would require exactly the same as * (Pokémon) would. This gives even less reason to use a virtual namespace. --Pidgeot (t) (c) (e) 06:52, 9 May 2005 (UTC)

 * inventing a new namespace is VERY MESSY. It means a new policy, look at the Portal:Cricket debate...
 * I agree that the new pages being made is a problem if we change naming formats... that would just make them be worthless redirects...
 * ...let's put it another way, do you want to rename 384+ Pokemon to "Pokemon:" or "Pokemon/" or whatnot? I know it's probably possible to configure a bot to do that, but even so, need we create that many redirects, and for what?
 * OK, rather than argue about that, let's decide another thing first: the images.
 * How big can images be to actually be detailed, and yet still be thought of as fair use?
 * How should the images be named, or should they be merely named after the Pokemon itself?
 * Personally I think that new naming images (ONLY new ones) "Pokedex_Name" or "Pokedex-Name" or similar *might* help. There is currently no naming format and there's probably already a "Pikachu.jpg" and other "namehere" images that aren't necessarily going to be suitable for pokedex purposes, and moving/renaming them gets messy.
 * If we at least decide that first some work can be done. Then at least the lists can be organised.
 * Similarly, are we moving the stat tables in whole or in part to WikiBooks, and if so what moves and what stays? I think actually getting on with altering the content we have now is more important than arguing about how to name it. Master Thief Garrett 07:06, 9 May 2005 (UTC)

...

 * Creating a new namespace is a can of worms. People interested in doing so should start a discussion on that in general (not just on Pokemon in particular), from the Village Pump.
 * Stats (e.g. at:20, def:30) are prime source material and thus belong in Wikibooks rather than Wikipedia.
 * So I'd say we keep Stage, Number, Evolves from/to, Species, Type, Abilities and Signature attack. Makes for a neat table, no?
 * Merge by something, I believe species was the idea from above.
 * Given the amount of images, they should probably be thumbnails and simply the creature on white background.
 * HTH, Radiant_* 14:24, May 9, 2005 (UTC)

merge by type ultimatum!
It seems we're spending weeks arguing over naming formats. I am sick of waiting, I want some action.

Now I had already suggested merging by Type1 and giving a list of links to Type2 members, so what I propose is to re-use existing (redirect) pages like Grass Pokémon and move all the Pokemon there, and then at the bottom give links to the Pokemon that have that as their secondary type (if any).

I'm not going to mess with the special tables and will for now leave the tables as-is (in case significant changes are made to the template code) so it'll just be a cut-n-paste.

Sound OK? Yes? No? Either way, if I don't hear back about this soon I'm gonna be bold and do it anyway... so speak up if you will! Master Thief Garrett 05:29, 11 May 2005 (UTC)

 * Go ahead. --Carnildo 06:03, 11 May 2005 (UTC)

 * OK then! Can anyone think of any ones that should NOT be merged with their kind? Pikachu of course, but are there other extremely notable ones? Master Thief Garrett 06:36, 11 May 2005 (UTC)

 * As someone who only has a general idea of what Pokémon is about, I can't think of any. My brother, who is a rational Pokémon fan (contradiction in terms, I know), can't think of any.  Just in case there are some besides Pikachu, I'd suggest that any article with enough text to extend beyond the end of the table shouldn't be merged. --Carnildo 07:30, 11 May 2005 (UTC)
 * Concur with that, article length seems a good criterion. Mew comes to mind, and probably that cat thingy that Team Rocket always has with them. Radiant_* 07:33, May 11, 2005 (UTC)
 * I concur that any sufficiently long article should not be merged, unless you can make it shorter without losing essential content (a Pokemon shouldn't earn its own article on account of meaningless rambling alone.) Deco 09:01, 11 May 2005 (UTC)

 * I disagree with merging the articles. I'm planning to significantly change the infobox insofar as which fields should be included (for example, omitting base stats, which belong in the Wikibook and - with the release of Diamond and Pearl looming - could change!). Since no dynamic action appears to be taken as regards to this project - my proposals, etc. go unanswered and uncommented - I'll simply take the action required without approval from any other member. Revert if you wish; I'm only trying to make the Project a little easier to manage. If only more people would concentrate on expanding articles! CNash 09:34, 11 May 2005 (UTC)

 * I'd be happy to comment on your proposals, only I am not sure where you've proposed them. I've checked the PokeStubs article and Wikiproject, and this page, and the only thing I've found is that you propose to revive and get more people interested in the WikiPokoject. So did you?
 * What is basically at stake here, is that several people object to stubs, and prefer them merged. Also, personally I think you cannot describe Bellsprout without also describing Victreebel. That seems to be the consensus here. Of course, if you want to change any of the stubs into a good article, by all means do so! Remember that merges can be broken out if/when more information is added. Radiant_* 09:56, May 11, 2005 (UTC)

 * I too missed these proposals, I guess they got "lost in the mail" what with all the namespace talk.
 * So you want a page for each and every Pokemon? Well, while one could easily take the Pokedex description and write something based on that, wouldn't that just be more fancruft waffle? I mean, is it really worthwhile to non-fan readers to have huge tracts about each obscure Pokemon?
 * Also, 99% of Pokemon fall under the WP:FICT rule about minor characters.
 * Before reading this I'd already merged some starters as a test, into Grass Pokémon and Fire Pokémon respectively. I think it's quite tidy that way. Charizard breaks the page length rule, but I'm sure I smell at *least* a little waffle in there. In retrospect his anime appearance perhaps makes him just noteworthy enough, but ah well...
 * No information is actually being lost in this process, so why have disparate pages? Master Thief Garrett 10:31, 11 May 2005 (UTC)
 * It's important to note that the information should NOT be fan speculation; the information I add to my articles is taken directly from the pokédex entries on that pokémon. Anyway, I have since been bold and affected changes to the infobox, as well as started to write a few more articles. Funny you should mention Bellsprout et al - I've just finished writing Weepinbell and Victreebel's articles. CNash 11:05, 11 May 2005 (UTC)

 * Garrett -> looks like a definite improvement. I've changed the infoboxes a bit on Grass Pokeys, please tell me what you think of it. Radiant_* 11:28, May 11, 2005 (UTC)
 * You've just done a little nitpicking, and it looks fine! I wouldn't do too much on the infoboxes if I were you, as that can be done at a later date when the template is done. Otherwise you're basically doing them twice over. Master Thief Garrett 12:20, 11 May 2005 (UTC)

 * Nash -> sounds good. More info = more Pedia :) Radiant_* 11:28, May 11, 2005 (UTC)

 * A problem is determining the notability of the Pokémon. Here is a list of Pokémon that are highly notable IMO:
 * Bulbasaur
 * Charmander
 * Charizard
 * Squirtle
 * Blastoise
 * Pikachu
 * Raichu
 * Clefairy
 * Jigglypuff
 * Meowth
 * Ditto
 * Eevee
 * Vaporeon
 * Jolteon
 * Flareon
 * Umbreon
 * Espeon
 * Togepi
 * Mewtwo
 * Mew
 * Celebi
 * Lugia
 * Ho-oh Andros 1337 02:43, 12 May 2005 (UTC)

Notable in what way? Most people who've had little or no exposure to Pokémon, like myself, would only recognize Pikachu and a few others out of that list. (I must admit I recognize Squirtle, Charmander, and Jigglypuff, though I can't explain why.) None of these except Pikachu are culturally or otherwise significant outside of the context of the Pokémon universe. Also, most of those articles are lengthy – this proposal is mainly about stub articles, where there's little or no content beyond the game stats. android↔talk 03:07, May 12, 2005 (UTC) At the very least, we should have articles on POKéMON that play a very major role in the games, the anime series or the movies, or possess a very unique attribute (Eevee evolves into any of 5 different POKéMON, all on the list, Ditto can breed with any breedable POKéMON). With the only possible exception being Blastoise, all of those on Andros' list fulfill that criteria. I'd also choose Articuno, Zapdos, Moltres, Entei, Unown, Jirachi and Deoxys - and possibly extend it to have articles on all legendary POKéMON.
 * I'm afraid that, despite being somewhat of a gaming geek, I haven't heard of over half the Pokemon on Andros's list. But anyway, yes, lengthy articles should not be merged into lists. Radiant_* 08:18, May 12, 2005 (UTC)

Additionally, if there's an article on a POKéMON, we should try to have articles on all of its evolutions. --Pidgeot (t) (c) (e) 13:34, 12 May 2005 (UTC)
 * If you have information to improve an article beyond sub-status, by all means do so! Merging isn't necessarily permanent - you can break an article out if there's enough information. It's not about the "honor" of having a separate article, it's about the accessibility of the information. I would find it plausible to merge Eevee's five possible evolutions to the bottom of Eevee, for instance.
 * For instance, Garrett has merged Charmander/Charmeleon/Charizard. I found that a useful article because it makes it easy to compare the two, don't you agree? Radiant_* 14:02, May 12, 2005 (UTC)
 * Well, in my view, properly merged articles can substitute for seperate articles, so I'm not saying that this shouldn't necessarily be the case. I'm just saying that it's more important to have some additional information on those. --Pidgeot (t) (c) (e) 14:23, 12 May 2005 (UTC)
 * I wholeheartedly agree. More info = better wiki. However, I am personally unable to provide additional info on Pokemon since that just isn't among my areas of expertise. So I'm hoping to help the wiki by contributing to organizing information. Radiant_* 14:40, May 12, 2005 (UTC)
 * It's always good to have someone helping who doesn't know a **** about the subject, just to keep the objectivity correctly focussed :) Master Thief Garrett 06:08, 13 May 2005 (UTC)

 * Delete or merge all of the list above. The notion that any of those (except mabye for Pikachu which might be considered a very minor cultural icon) is remotely encyclopedic must seem ludicrous to anyone outside the Pokemon community. Martg76 12:18, 15 May 2005 (UTC)
 * Heck, it seems ludicrous to me, and I'm *inside* the Pokemon community. Master Thief Garrett 14:42, 15 May 2005 (UTC)
 * As for being a "minor" cultural icon, the other day I read that children can recognise Ronald McDonald easily, second only in recognisability to Santa... and I'd bet that Pikachu would pull in a close third! Master Thief Garrett 07:06, 17 May 2005 (UTC)
 * Depends. What sort of numbers is Joe Camel getting these days? --Carnildo 17:57, 17 May 2005 (UTC)
 * In Japan, Pikachu is more well-known than Mickey Mouse, so if Pikachu is "only" a minor cultural icon, then the same applies to Mickey Mouse. Still, you'd never argue against having an article on him, would you? --Pidgeot (t) (c) (e) 07:26, 18 May 2005 (UTC)
 * First, no one is suggesting that Pikachu does not deserve his own article. In fact, Radiant and I have explicitly stated that he does. Second, I find it hard to believe that Pikachu is more well-known in Japan than Mickey. Perhaps among the younger generations, but among the population as a whole? Do you have a source?
 * I'm afraid I no longer know where to find that source (it was a long time ago that I read it), but I do know it was a very reputable source (at least in my experiences with them), and that it covered the population as a whole. --Pidgeot (t) (c) (e) 11:35, 21 May 2005 (UTC)
 * The only reason to keep any of this Pokécruft as a separate article for each character, would be if people would want to look for the character's name without knowing that it is a Pokemon. That may well happen with a few well-known names such as Pikachu. Or perhaps, if the name is also an ordinary language word or name not connected with Pokemons, for example Mew (the cat noise; seagull; etc). I read somewhere that there is a separate Wiki for Pokemons :: that is the best place for Pokemon information. Anthony Appleyard 22:11, 20 May 2005 (UTC)
 * That's what redirects are for, Anthony. Radiant_* 11:31, May 23, 2005 (UTC)
 * Don't forget, though, redirects can't take you to a specific part of an article - if it were to do that, you'd have to use HTTP redirection while keeping a map of where you've been to avoid loops (this would require only one redirection, meaning you have to load everything before the page loads). This means that going to the section of one of the "later" POKéMON will take a longer time, since you need to load more data (which can be a LOT for some types, and easily become a struggle for 56Kers), and find the appropriate entry in the TOC. --Pidgeot (t) (c) (e) 22:40, 27 May 2005 (UTC)

Thing is, nobody needs a "policy consensus" to merge articles. Just do it if you want to. --Tony Sidaway|Talk 12:04, 25 May 2005 (UTC)
 * Nice theory. In practice, for a major merge like this, if you don't have sufficient support, the Pokéfanatics will revert any and all attempts. --Carnildo 18:27, 25 May 2005 (UTC)
 * Yes, consensus must be made if this is to go through. WP:FICT is only a semi-policy - that is, a guideline - and thus something that cannot be enforced on this high a number of articles with no consensus whatsoever. A poll should be created soon. Actually, I'd start it now, expect I feel polls should always be started by those in favor of the new idea. --Pidgeot (t) (c) (e) 22:55, 27 May 2005 (UTC)

Poll Open or Closed?
Is the poll open or closed, as it states on Poképrosal/Poll The poll will continue for one week from 23:26, 27 May 2005 (UTC), but it hasn't been closed yet. Hiding 09:48, 14 Jun 2005 (UTC)
 * Good point. I've marked it as closed, it's time has elapsed. Radiant_ >|< 09:51, Jun 14, 2005 (UTC)

Proposal to challenge the Poképrosal idea
I am against Poképrosal. Poképrosal is controversial. It has alienated me from the Pokémon franchise. Notability policy concerning fiction is a semi-policy, or guideline. The notability of the Pokémon is unclear and overlooked. It is once said that the WP:FICT guidelines do not actually apply to Pokémon. Pokémon is Nintendo's second best-selling franchise. The majority who supported Poképrosal got it all wrong and overlooked the situation. The foreign language Wikipedias still have separate articles of each individual Pokémon, and this Poképrosal only applied to English Wikipedia. That is nonsense right there. I have seen enough of the controversial policy activity at Wikipedia as it is. Even Mewtwo and Lucario got merged into the Poképrosal list, although they played very major roles in the media they appeared in. I do not really like TTN, for that user is too strict in applying the policies. There could also be a userbox saying "This user is against Poképrosal." I am strongly against merging articles on individual Pokémon who appeared in the Super Smash Bros. series as playable characters to be merged into lists. Decimus Tedius Regio Zanarukando (talk) 05:54, 29 April 2008 (UTC)

Archive of the old Pokepages
Did anyone ever archive the old Pokemon pages? I looked around and I couldn't seem to find them, and the wikibooks link no longer exists. KimiNewt (talk) 20:40, 12 March 2009 (UTC)
 * If you want to see the old Pokemon pages such as Geodude, then go to their normal link, then at the top of the List you got redirected to, click the link that says "Redirected from Geodude" and then go to history, and pick the latest non-redirect version. --Blake (talk) 15:25, 21 May 2009 (UTC)

title: Wikipedia talk:Poképrosal


text:
Montea

Moutya or Moutia, is a traditional African dance similar to the Sega, but with often more pronounced suggestive movements. Female and male dancers move in rhythm to the beat of the often single drum made of dried goatskin and lightly heated up by a bonfire prior to the start of the Dance (and regular during the evening). Dancing starts off slowly in time to the beat of the drums, but speeds up and becomes more erotic as the beating becomes faster and faster and faster.

The beat and dance are always accompanied by singing, which usually recounts the hardships and joys of everyday life. Until the late 1970s, the Moutya was considered more of a risqué dance and generally shunned.

Inscription on the Intangible Cultural Heritage List of Humanity
In 2019, Seychelles attempted to register Moutya as an intangible cultural heritage site, but the application was deemed incomplete. Registration finally takes place in 2021. David André, Seychelles' Secretary General for Culture, describes the registration as an achievement, which he believes will enable the cultural element to be passed on to future generations. According to the official UNESCO description, the moutya expresses cultural identity and preserves traditional elements. It is transmitted through imitation, documentation and research.

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

title: Montea


text:
Ammasandra

Ammasandra (sometimes referred to as Adityapatna) is a small township in Turuvekere taluk, Tumkur district in the state of Karnataka, India.

Demographics
India census,. workers. Ammasandra had a population of 4236. Males constitute 51% of the population and females 49%. Adityapatna has an average literacy rate of 82%, higher than the national average of 59.5%: with 54% of the males and 46% of females literate. In Ammasandra, 7% of the population is under 6 years of age.

title: Ammasandra


text:
File:AnthraxVolume8TheThreatIsReal.jpg

Summary
Anthrax – Volume 8: The Threat Is Real album cover.

Copyright 1998 Elektra Records

title: File:AnthraxVolume8TheThreatIsReal.jpg


text:
Talk:Psychic paper

Please would someone explain why this should be deleted.
 * Because it's trivial - it's a minor plot device that can be, and is explained by a single sentence in every episode it shows up in, and nothing more. It duplicates information unnecessarily to have its own article and it's not even very interesting. See the VfD page. --khaosworks 14:57, May 27, 2005 (UTC)
 * But it does appear in more than one story. And, why does Captain Jack use it, anyway? That should mean that it has an origin... other than the Doctor. If it appears more in the 2nd season, or has an origin, then deleting it might be a bad idea. It would also keep people from having to explain it in every episode... And it would be nice to have a picture of the psychic paper... --Travlr23 13:56, 28 May 2005 (UTC)
 * Wikipedia is not a crystal ball - if it becomes significant later, then we can always recreate the article. As it is, it's simply not notable, and has no significance othber than a plot device - which, as I said, we can dispose of in one sentence. "It makes people see what you want them to see." That's not hard. --khaosworks 14:35, May 28, 2005 (UTC)

title: Talk:Psychic paper


text:
Category:Carbonyl complexes

This category is for metal complexes of carbon monoxide.

title: Category:Carbonyl complexes


text:
Talk:Furnace Room Lullaby

Album length - too short
The current length listed for this album (23 min 33 sec) just doesn't add up...does someone have a link to a more official length figure? I'll try to find one myself as well... - McCart42 (talk) 14:26, 2005 May 27 (UTC)
 * Adjusted to 36:20 from sum of track times. Of course this ignores pregap, but it's a good approximation. - McCart42 (talk) July 5, 2005 02:26 (UTC)

title: Talk:Furnace Room Lullaby


text:
Rosopsida

Rosopsida (Batsch, 1788) is a botanical name for a group of flowering plants recognized at the rank of class. The name is derived from that of the included family Rosaceae. As used in the Reveal system it is a subset of the dicots, a paraphyletic group recognized at various ranks in other systems, and includes:
 * subclass Caryophyllidae
 * subclass Hamamelididae
 * subclass Dilleniidae
 * subclass Rosidae
 * subclass Cornidae
 * subclass Lamiidae
 * subclass Asteridae

Reveal's use of the group corresponds largely to Cronquist's class Magnoliopsida (but minus subclass Magnoliidae) and to the eudicots of the APG II system minus Ranunculales and some other early-branching groups.

The name has not been used in most of the more influential recent classification systems, such as the Cronquist system, the Thorne system, the Takhtajan system or the APG II system.

title: Rosopsida


text:
Motion control

Motion control is a sub-field of automation, encompassing the systems or sub-systems involved in moving parts of machines in a controlled manner. Motion control systems are extensively used in a variety of fields for automation purposes, including precision engineering, micromanufacturing, biotechnology, and nanotechnology. The main components involved typically include a motion controller, an energy amplifier, and one or more prime movers or actuators. Motion control may be open loop or closed loop. In open loop systems, the controller sends a command through the amplifier to the prime mover or actuator, and does not know if the desired motion was actually achieved. Typical systems include stepper motor or fan control. For tighter control with more precision, a measuring device may be added to the system (usually near the end motion). When the measurement is converted to a signal that is sent back to the controller, and the controller compensates for any error, it becomes a Closed loop System.

Typically the position or velocity of machines are controlled using some type of device such as a hydraulic pump, linear actuator, or electric motor, generally a servo. Motion control is an important part of robotics and CNC machine tools, however in these instances it is more complex than when used with specialized machines, where the kinematics are usually simpler. The latter is often called General Motion Control (GMC). Motion control is widely used in the packaging, printing, textile, semiconductor production, and assembly industries. Motion Control encompasses every technology related to the movement of objects. It covers every motion system from micro-sized systems such as silicon-type micro induction actuators to micro-siml systems such as a space platform. But, these days, the focus of motion control is the special control technology of motion systems with electric actuators such as dc/ac servo motors. Control of robotic manipulators is also included in the field of motion control because most of robotic manipulators are driven by electrical servo motors and the key objective is the control of motion.

Overview
The basic architecture of a motion control system contains:
 * A motion controller, which calculates and controls the mechanical trajectories (motion profile) an actuator must follow (i.e., motion planning) and, in closed loop systems, employs feedback to make control corrections and thus implement closed-loop control.
 * A drive or amplifier to transform the control signal from the motion controller into energy that is presented to the actuator. Newer "intelligent" drives can close the position and velocity loops internally, resulting in much more accurate control.
 * A prime mover or actuator such as a hydraulic pump, pneumatic cylinder, linear actuator, or electric motor for output motion.
 * In closed loop systems, one or more feedback sensors such as absolute and incremental encoders, resolvers or Hall effect devices to return the position or velocity of the actuator to the motion controller in order to close the position or velocity control loops.
 * Mechanical components to transform the motion of the actuator into the desired motion, including: gears, shafting, ball screw, belts, linkages, and linear and rotational bearings.

The interface between the motion controller and drives it control is very critical when coordinated motion is required, as it must provide tight synchronization. Historically the only open interface was an analog signal, until open interfaces were developed that satisfied the requirements of coordinated motion control, the first being SERCOS in 1991 which is now enhanced to SERCOS III. Later interfaces capable of motion control include Ethernet/IP, Profinet IRT, Ethernet Powerlink, and EtherCAT.

Common control functions include:
 * Velocity control.
 * Position (point-to-point) control: There are several methods for computing a motion trajectory. These are often based on the velocity profiles of a move such as a triangular profile, trapezoidal profile, or an S-curve profile.
 * Pressure or force control.
 * Impedance control: This type of control is suitable for environment interaction and object manipulation, such as in robotics.
 * Electronic gearing (or cam profiling): The position of a slave axis is mathematically linked to the position of a master axis. A good example of this would be in a system where two rotating drums turn at a given ratio to each other. A more advanced case of electronic gearing is electronic camming. With electronic camming, a slave axis follows a profile that is a function of the master position. This profile need not be salted, but it must be an animated function

title: Motion control


text:
User talk:Jeodesic

RfD nomination of "Do You Know"? (The Ping Pong song)
I have nominated for discussion. Your opinions on the matter are welcome; please participate in the discussion by adding your comments at the discussion page. Thank you. Floaterfluss (talk) (contribs) 04:25, 8 January 2008 (UTC)

Stubs
Thanks a bunch! I'm really new at this (you may have noticed) and I'm not really sure if I'm even doing this right. I just wanted to say thanks for the assistance! TigressofIndia (talk) 01:33, 9 January 2008 (UTC)

Feedback, please
Hello, ... Thnx fer your recent tweaks to  ... I tried to keep the sandbox in User space but I guess the   tag made it visible in Article space after all ... My bad!

Well, at least you must have seen the Talk page and sussed what I was doing. :-)

Happy Editing! — 17:51, 9 January 2008 (UTC)
 * No problem, yours is far from the first stub-tagged user-space page I've come across. Jeodesic (talk) 00:26, 10 January 2008 (UTC)

thanks
thanks for adding that stub to phantom arcade Matster9090 (talk) 13:08, 24 January 2008 (UTC)

Undid redirect
Hi! I undid your page move of the Corpus Catholicorum (Series) for reasons which I explain on Talk:Corpus Catholicorum (Series). However, I'm not exactly clear on how to proceed with fixing the links (I never have had occasion to do this before). So I thought if perhaps you had a moment, you wouldn't mind giving me a hand. Sure would be much obliged! Thanks. Delta x (talk) 01:50, 31 January 2008 (UTC)

 * Hey, Jeodesic, Back again! First, let me say thanks for responding, and thanks for the heads-up regarding moving the article again – this time using a lower case “s” for “series”. Sometimes the devil really is in the details! I’ll definitely read over the link you provided.

 * In the meantime, I’m afraid I need press you into service again. At the risk of appearing a total ignoramus, I’m still at a loss as to exactly how to go about fixing the links in the two articles that link here.

 * You see, I was under the impression that when I moved the page back to its original name, all the links to the (now old) name i.e. Corpus Catholicorum (CC) -- which were red links to begin with -- would automatically revert back to being red links again.

 * I just assumed that the article - Corpus Catholicorum - would have been deleted by the move back process. But as you can see, the lk Corpus Catholicorum is not red, and it links right back to Corpus Catholicorum (Series), which is precisely what it's not supposed to do.

 * So my question is, why is that, and again, how does one go about fixing it? Changing the link on the Augustus II the Strong for example, wont fix the problem. So specifically, what do I change so that the CC lks again appear red and no longer lk to the redirect page?

 * Also, I was thinking of using one of those red lks to start a WP article on the other Corpus Catholicorum (now that I’m aware there is another CC!). And one final question (for the moment at least). ;) What about the redirect page, once all links have been changed so that nothing links to it, is it deleted?

 * Again, thanks for any assistance. Delta x (talk) 06:53, 31 January 2008 (UTC)

 * Oh, I see what you are saying. For some reason, I had stuck in my head the idea that this type of page move  (undo a redirect) differed from “ordinary” page moves in that in such instances, the page moved from would just be deleted, thus resetting everything to its original state. I see now that’s not how it works, and that, as far as the MediaWiki software is concerned, a move is a move is a move, and in every instance, the page moved from is never automatically deleted, but simply becomes a redirect. I do think it would be helpful if the software had a degree of greater flexibility. Perhaps in the future. Meanwhile, I'll just change the link titles so everything points where it should and not worry about having to set things back to their "original state." And I will certainly do some more reading up on this when I get a little extra time.

 * Thanks for the help and for the clarification; I'm a little more knowledgeable now. Delta x (talk) 21:14, 31 January 2008 (UTC)

Horace Hagedorn
Thanks for correcting it for me, I didn't spend much time on it, but you did a marvelous job. Though I must say I was very annoyed that it was proposed for deletion. :-( Emj (talk) 18:08, 2 February 2008 (UTC)

History of Serranilla Bank
I've added an explanation on why I created article at Talk:History_of_Serranilla_Bank Tom (talk) 14:48, 18 February 2008 (UTC)

stub
Hi Jeodesic. Thanks for this, I was able to add another ref. :-) cygnis insignis 17:25, 25 February 2008 (UTC)

BD template
Due to substing it seems to be recommended that Lived be used instead. /Lokal_Profil 22:24, 27 February 2008 (UTC)

lol, you stubbed a hoax
Seriously, look at this, you seriouly didn't notice that it was a hoax while stubbing it? :) --Enric Naval (talk) 21:26, 18 April 2008 (UTC)
 * Apparently not, but as the page has been deleted, it's somewhat hard to tell why I failed to notice. I'll just blame late-night editing... Jeodesic (talk) 17:27, 19 April 2008 (UTC)

AfD nomination of Trevor Lyman
An article that you have been involved in editing, Trevor Lyman, has been listed for deletion. If you are interested in the deletion discussion, please participate by adding your comments at Articles for deletion/Trevor Lyman. Thank you. Do you want to opt out of receiving this notice?

Disam hatnotes
You're adding disambiguation hatnotes to articles whose titles aren't ambiguous, like Jack Evans (D.C. Council). Please see WP:NAMB. —KCinDC (talk) 23:37, 12 October 2008 (UTC)

List of bands whose members are all deceased
I made this article following talk at Talk:Mitch Mitchell. I think it's an OK list in the style of list of notable last events, but there isn't that much substance to it and it's hard to define who is, and who isn't a member. It seems like Jimi Hendrix Experience is the first well known rock band to have all of its members/former members dead.-Piebald Avarice (talk) 15:55, 22 November 2008 (UTC)

Pornstar (film)
Copyvio has been corrected and the article expanded and sourced.  Schmidt,  MICHAEL Q. 00:09, 25 November 2008 (UTC)

Brave New Video
Eyh, I agree it's borderline. I declined it because I interpreted it as "artwork by a serious artist" rather than "some lame stuff some kids put up on YouTube". After looking more fully at it, I've PROD-ded it, because while there is enough doubt against an A7 in mind, it's fairly clear that its notability is shaky at best. Lankiveil (speak to me) 13:05, 16 December 2008 (UTC).

Reviewer granted
Hello. Your account has been granted the "reviewer" userright, allowing you to review other users' edits on certain flagged pages. Pending changes, also known as flagged protection, is currently undergoing a two-month trial scheduled to end 15 August 2010.

Reviewers can review edits made by users who are not autoconfirmed to articles placed under pending changes. Pending changes is applied to only a small number of articles, similarly to how semi-protection is applied but in a more controlled way for the trial. The list of articles with pending changes awaiting review is located at Special:OldReviewedPages.

When reviewing, edits should be accepted if they are not obvious vandalism or BLP violations, and not clearly problematic in light of the reason given for protection (see Reviewing process). More detailed documentation and guidelines can be found here.

If you do not want this userright, you may ask any administrator to remove it for you at any time. Courcelles (talk) 05:43, 20 June 2010 (UTC)

Speedy deletion nomination of International Development Exchange

A tag has been placed on International Development Exchange, requesting that it be speedily deleted from Wikipedia. This has been done under section G11 of the criteria for speedy deletion, because the page seems to be unambiguous advertising which only promotes a company, product, group, service or person and would need to be fundamentally rewritten in order to become encyclopedic. Please read the guidelines on spam and FAQ/Organizations for more information.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Click here to contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be removed without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, you can place a request here. Epicgenius (talk to me • see my contributions) 21:50, 6 May 2013 (UTC)

ArbCom elections are now open!
MediaWiki message delivery (talk) 12:52, 23 November 2015 (UTC)

Speedy deletion nomination of Category:Room 2012 albums

A tag has been placed on Category:Room 2012 albums requesting that it be speedily deleted from Wikipedia. This has been done under section C1 of the criteria for speedy deletion, because the category has been empty for seven days or more and is not a disambiguation category, a category redirect, a featured topics category, under discussion at Categories for discussion, or a project category that by its nature may become empty on occasion.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. Liz Read! Talk! 16:12, 9 December 2020 (UTC)

Speedy deletion nomination of Category:Misha (singer) albums

A tag has been placed on Category:Misha (singer) albums indicating that it is currently empty, and is not a disambiguation category, a category redirect, a featured topics category, under discussion at Categories for discussion, or a project category that by its nature may become empty on occasion. If it remains empty for seven days or more, it may be deleted under section C1 of the criteria for speedy deletion.

If you think this page should not be deleted for this reason you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. Please do not remove the speedy deletion tag from the page yourself. Liz Read! Talk! 16:23, 3 October 2021 (UTC)

"Atlantis, Arise!(Transformers episode)" listed at Redirects for discussion
The redirect [//en.wikipedia.org/w/index.php?title=Atlantis,_Arise!(Transformers_episode)&redirect=no Atlantis, Arise!(Transformers episode)] has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at  until a consensus is reached. Gonnym (talk) 23:10, 2 June 2023 (UTC)

"Attack of the Autobots(Transformers episode)" listed at Redirects for discussion
The redirect [//en.wikipedia.org/w/index.php?title=Attack_of_the_Autobots(Transformers_episode)&redirect=no Attack of the Autobots(Transformers episode)] has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at  until a consensus is reached. Gonnym (talk) 23:10, 2 June 2023 (UTC)

title: User talk:Jeodesic


text:
Variable data printing

Variable data printing (VDP) (also known as variable information printing (VIP) or variable imaging (VI)) is a form of digital printing, including on-demand printing, in which elements such as text, graphics and images may be changed from one printed piece to the next, without stopping or slowing down the printing process and using information from a database or external file. For example, a set of personalized letters, each with the same basic layout, can be printed with a different name and address on each letter. Variable data printing is mainly used for direct marketing, customer relationship management, advertising, invoicing and applying addressing on selfmailers, brochures or postcard campaigns.

Variable data printing: customization and operational methodologies
VDP is a direct outgrowth of digital printing, which harnesses computer databases and digital print devices and highly effective software to create high-quality, full color documents, with a look and feel comparable to conventional offset printing. Variable data printing enables the mass customization of documents via digital print technology, as opposed to the 'mass-production' of a single document using offset lithography. Instead of producing 10,000 copies of a single document, delivering a single message to 10,000 customers, variable data printing could print 10,000 unique documents with customized messages for each customer.

There are several levels of variable printing. The most basic level involves changing the salutation or name on each copy much like mail merge. More complicated variable data printing uses 'versioning', where there may be differing amounts of customization for different markets, with text and images changing for groups of addresses based upon which segment of the market is being addressed. Finally there is full variability printing, where the text and images can be altered for each individual address. All variable data printing begins with a basic design that defines static elements and variable fields for the pieces to be printed. While the static elements appear exactly the same on each piece, the variable fields are filled in with text or images as dictated by a set of application and style rules and the information contained in the database.

There are three main operational methodologies for variable data printing.

In one methodology, a static document is loaded into printer memory. The printer is instructed, through the print driver or raster image processor (RIP) to always print the static document when sending any page out to the printer driver or RIP. Variable data can then be printed on top of the static document. This methodology is the simplest way to execute VDP, however its capability is less than that of a typical mail merge.

A second methodology is to combine the static and variable elements into print files, prior to printing, using standard software. This produces a conventional (and potentially huge) print file with every image being merged into every page. A shortcoming of this methodology is that running many very large print files can overwhelm the RIP's mad processing capability. When this happens, printing speeds might become slow enough to be impractical for a print job of more than a few hundred pages.

A third methodology is to combine the static and variable elements into print files, prior to printing, using specialized VDP software. This produces optimized print files, such as PDF/VT, PostScript or PPML, that maximize print speed since the RIP only needs to process static elements once.

Software and services
There are many software packages available to merge text and images into VDP print files. Some are stand-alone software packages like SYNC Infographic VDP Generator, however most of the advanced VDP software packages are actually plug-in modules for one or more publishing software packages such as Adobe Creative Suite.

Besides VDP software, other software packages may be necessary for VDP print projects. Mailing software is necessary in the United States (United States Postal Service) and Canada to take advantage of reduced postage for bulk mailing. Used prior to the VDP print file creation, mailing software presorts and validates and generates bar codes for mailing addresses. Pieces can then be printed in the proper sequence for sorting by postal code. In Canada, Canada Post now offers a 'Machineable' personalized mail category which does not require addresses to be sorted into any specific order before mailing; therefore reducing the need for specialized sorting software to obtain optimal postage rates.

Software to manage data quality (e.g. for duplicate removal or handling of bad records) and uniformity may also be needed. In lieu of purchasing software, various companies provide an assortment of VDP-related print file, mailing and data services.

Benefits
The difference between variable data printing (VDP) and traditional printing is the personalization that is involved. Personalization allows a company to connect to its customers. Variable data printing is more than a variable name or address in a printed piece; in the past, a variable name would have been effective, because it was a new concept at the time. In today’s world, marketers expect personalization to reflect the interests of the customer. In order for VDP to be successful, the company must first know something about the customer. For example, a customer who loves baseball might be given a VDP postcard containing an image of their favorite baseball player. Compared to a generically printed marketing postcard, such a VDP postcard is more likely to be effective, because the customer is more likely to read the material that it carries. Conversely, an example of an ineffective VDP piece would entail mailing a postcard to the same customer with an image of a soccer player. If the customer has no interest in soccer, then he or she might or might not pay attention to the postcard. The ultimate goal is to attract the customer's attention to a sales pitch of some type, with the intent of generating demand for a product or service (which might be something that the customer has no need for, but which the advertising manages to convince the customer to pay for anyway). As a communication tool, personalization enables the company to communicate in such a way as to develop business relationships with prospective customers and also to maintain relationships with their current customers. In this way, a prospect who is converted to a customer can then be converted to a loyal customer, who continues to buy goods or services from that company. A company that produces good-quality products or provides useful services will retain the loyal customers that it has created.

Another benefit of VDP is the increase in the response rate and the reduction in response time. Because personalization more effectively catches the attention of the consumer, the response rate of a mail campaign increases. Personalization also decreases the response time, because the mailed piece generally has a more profound and more meaningful effect on the consumer. This effect, in turn, induces the consumer to respond more quickly, especially if the mailed piece contains a call to action such as a time-limited offer with a clearly enunciated deadline. In contrast, a mailed piece that is not eye-catching may instead be set aside and forgotten until a later date. Therefore, in such a case, it might take weeks or longer for a response to be obtained, if one is in fact obtained at all.

Integration
Variable data printing can be combined with other platforms – such as PURLS, email blasts, and QR codes; all three platforms are considered marketing tools. Many people have found the benefit of combining all of these platforms in order to have a successful campaign. Email blasts and PURLS allow a company to find out information about their consumer. An email blasts usually doesn’t contain much personalization, but it can. The bulk of the personalization would be seen in a PURL. A PURL is a personalized uniform resource locator (URL). In short, it is a landing page. It is also where most of the knowledge about the consumer will be gained. The email blasts will contain a PURL, which will lead the consumer to a personalized page. The PURL is where a company can gain information about the consumer through the requested information. The QR code can be added to a mailed piece. It works like an email blasts. It directs the consumer to a website. The integration of these three platforms can help a campaign.

Origin of the concept
The origin of the term variable data printing is widely credited to Frank Romano, Professor Emeritus, School of Print Media, at the College of Imaging Arts and Sciences at Rochester Institute of Technology. Mr. Romano does not explicitly take credit for coining the term but points to his use of it as early as 1969 and its appearance in the 1999 book, “Personalized and Database Printing”, that he authored with David Broudy.

The concept of merging static document elements and variable document elements predates the term and has seen various implementations ranging from simple desktop mail merge, to complex mainframe applications in the financial and banking industry. In the past, the term VDP has been most closely associated with digital printing machines. However, in recent years the application of this technology has spread to web pages, emails, and mobile messaging.

title: Variable data printing


text: Template:WW2 Brit Comm infantry guns

title: Template:WW2 Brit Comm infantry guns


text:
File:Skycladburntbone.jpg

Summary
The cover to A Burnt Offering for the Bone Idol by Skyclad.

title: File:Skycladburntbone.jpg


text:
User:AbinoamJr

See http://pt.wikipedia.org/wiki/Usuário:AbinoamJr for my page in portuguese.

Interwiking to portuguese wikipedia is what I do most here.

title: User:AbinoamJr


text: Category:WikiProject Cities

title: Category:WikiProject Cities


text:
A Burnt Offering for the Bone Idol

A Burnt Offering for the Bone Idol is the second album by British folk metal band Skyclad, released in 1992.

Track listing
Source: Metal Archives All music by Steve Ramsey, All lyrics by Martin Walkyier.

The samples in War and Disorder have been compiled by Kevin Ridley.

title: A Burnt Offering for the Bone Idol


text:
Pancreatectomy

In medicine, a pancreatectomy is the surgical removal of all or part of the pancreas. Several types of pancreatectomy exist, including pancreaticoduodenectomy (Whipple procedure), distal pancreatectomy, segmental pancreatectomy, and total pancreatectomy. In total pancreatectomy, the gallbladder, distal stomach, a portion of the small intestine, associated lymph nodes and in certain cases the spleen are removed in addition to the entire pancreas. In recent years, the TP-IAT (Total Pancreatectomy with Islet Autotransplantation ) has also gained respectable traction within the medical community. These procedures are used in the management of several conditions involving the pancreas, such as benign pancreatic tumors, pancreatic cancer, and pancreatitis.

Indications
It is performed for a variety of reasons, including:
 * Inflammation
 * Necrotising pancreatitis
 * Chronic pancreatitis with pain
 * Trauma
 * Neoplasms
 * Adenocarcinoma (85%)
 * Cystadenoma (mucinous/serous)
 * Cystadenocarcinoma
 * Islet cell tumors (neuroendocrine tumors)
 * Papillary cystic neoplasms
 * Lymphoma
 * Acinar cell tumors
 * Severe hyperinsulinemic hypoglycemia

Types
The most common surgical procedure involving removal of a portion of the pancreas is called a pancreaticoduodenectomy.

Among common consequences of complete or nearly complete pancreatectomy are deficiencies of pancreatic endocrine or exocrine function requiring replacement of insulin or digestive enzymes. The patient immediately develops type 1 diabetes, with little hope for future type 1 diabetes treatments involving the restoration of endocrine function to a damaged pancreas, since the pancreas is either partially or completely absent. Type 1 diabetes can be treated with careful blood glucose monitoring and insulin therapy. Because the pancreas is responsible for the production of many digestive enzymes, a pancreatectomy should only be given as an option for pancreatic disease which is life-threatening, such as pancreatic cancers. It is very important to note that even after a pancreatectomy, pain still exists in most patients.

A distal pancreatectomy is removal of the body and tail of the pancreas.

Prognosis
After a total pancreatectomy, the body no longer produces its own insulin or pancreatic enzymes, so patients have to take insulin and enzyme supplements. Those who were not already diabetic become so. Glycemic control is challenging even for relatively young and healthy apancreatic people, owing to the digestive challenges of not having endogenous insulin and pancreatic enzymes under autonomic control. It can be insurmountably challenging depending on age and comorbidities. But overall, quality of life in patients after total pancreatectomy is comparable with quality of life in patients who undergo a partial pancreatic resection.

An experimental procedure called islet cell transplantation, most frequently the autotransplantation of islets isolated from the explanted pancreas into the portal vein, exists to help mitigate the loss of endocrine function following total pancreatectomy.

title: Pancreatectomy


text:
Balsham

Balsham is a rural village and civil parish in the county of Cambridgeshire, England, which has much expanded since the 1960s and is now one of several dormitory settlements of Cambridge. The village is south east of the centre of Cambridge beyond the A11 road and near Newmarket and Haverhill.

At the 2021 census, Balsham parish had a population of 3,594.

History
In 1015, Balsham was totally destroyed by Viking raiders. A sign on the village green commemorates the sole survivor of the attack who escaped by hiding in the parish church. It was the birthplace of scholastic philosopher Adam of Balsham.

In 1568 Richard Killingworth, Esq., was granted an estate at Balsham, which in 1590 belonged to his son and heir John Killingworth and was called Place Manor, much later becoming Place Farm. In 1617, the year of John's death, he still held the manor on the site of what in 1975 was called Balsham Place, together with freehold and copyhold lands, an enclosure in Balsham Wood, and heathland in the west part of the parish. His eldest son Giles (born 1571) thereafter held the manor of the Charterhouse Foundation, the feudal superior. A Mr. Killingworth still held the estate in 1715 when it appeared to extend to 261 acres, but in 1756 it was for sale.

The area between Balsham and West Wratting is said to be the haunt of the mythical Shug Monkey.

Holy Trinity Church
The current church has a mix of dates, with the bell tower being the oldest part, dating from the 13th century. It was possibly built by Hugh de Balsham, who was Bishop of Ely between 1257 and 1286. The chancel dates from the early 14th century, whilst the nave with its clerestory dates from the late 14th – the 26 stalls with their misericords were added during this building phase and probably date from 1400. A rood loft was added in the latter half of the 15th century, and the chancel roof was raised with its clerestory being added at the same time.

At some (unrecorded) time between the Dissolution of the Monasteries and the end of The Commonwealth, 17 of the misericords were removed, leaving nine. In the 19th century one misericord, which may have been the work of Canon H.J.S. Burrell, a former rector who was a noted woodcarver, was added.

The 19th century saw some extensive renovation, with the roofs being renewed, and the clerestories being repaired. A vestry was added on the north side in 1867, and further restoration was carried out in 1875. Further works have been carried out in the 20th century, with the addition of a chapel in the north aisle, containing an Elizabethan altar table. In 1973 the bell tower was strengthened.

There are images and a description of the church at the Cambridgeshire Churches website. The church has a number of 15th-century memorial brasses, including two rectors, John Sleford (d. 1401) and John Blodwell (d. 1462), and an unknown knight in Yorkist armour (c.1480s). All have been moved from their original locations within the church.

The village was at one time noted for its large community of Familists, members of an Anabaptist religious sect led by as Christopher Vitell. There is also an extensive history of other non-conformist congregations, from at least 1654.

Governance
Until 2024, Balsham was part of the now-abolished South East Cambridgeshire constituency for UK general elections, a Conservative safe seat. Under new boundaries established in the 2023 Periodic Review of Westminster constituencies, the village became part of South Cambridgeshire at the 2024 general election. The constituency has been represented by Liberal Democrat MP Pippa Heylings since July 2024.

Balsham is in the Linton Electoral Division for County Council elections.

Balsham is in the South Cambridgeshire local government district. Balsham Parish Council meets on the 3rd Monday of each month (excluding August and December) at the Sports Pavilion. The village is part of a two-seat Ward that also comprises Carlton, Castle Camps, Horseheath, Shudy Camps, West Wickham, West Wratting and Weston Colville.

Geography
Balsham is a large parish covering 1831 ha. It is located at 52.13167°N, 0.32278°W in south east Cambridgeshire, near the county boundaries with Essex and Suffolk. The village is 9 mi south east of the city of Cambridge. The larger village of Linton is to the south west, and smaller villages of West Wickham and West Wratting lie to the south east and north east respectively.

The village is sited on a ridge which runs from east to west, reaching 380 ft at its eastern edge. From the village, the ground falls away to open countryside.

Economy and landmarks
Balsham has a post office/general store and a Coffee Shop (which was, until recently, a butcher's shop, hence the name "The Old Butchers" ). The village also has two public houses – The Black Bull and The Bell.

Prince's Memorial is a full-sized bandstand opposite the village green.

The Icknield Way Path passes through the village on its 110-mile journey from Ivinghoe Beacon in Buckinghamshire to Knettishall Heath in Suffolk. The Icknield Way Trail, a multi-user route for walkers, horse riders and off-road cyclists also passes through the village. A stone marking the route of the Icknield Way is located on the village green.

Transport
There is a very limited local bus service running through the village operated by Stagecoach that terminates in Cambridge. Buses run approximately every two hours between Haverhill and Cambridge. The A11 road runs within 2 mi of Balsham, providing easy links to Stansted Airport and London. The nearest railway stations to Balsham are Audley End and Whittlesford Parkway on the West Anglia Main Line to London Liverpool Street, and Cambridge which connects several lines including the Cambridge line to London King's Cross. Balsham is served by two airports: Cambridge Airport and London Stansted which is about 20 miles away.

Balsham was served briefly by train in the 1840s by Balsham Road on the Newmarket and Chesterford Railway, one of the earliest railway closures in history when the line was diverted to Cambridge.

Education
The Meadow Community Primary School on the High Street provides for primary school children aged from 4 to 11. The school had 234 pupils in 2016. Children from the surrounding villages West Wratting, West Wickham, and Weston Colville also attend the school, travelling there by bus. Children of secondary school age travel to nearby Linton Village College.

Culture and sports
The Holy Trinity Church holds two services every Sunday and communion every Wednesday. The church also plays host to two yearly concerts by the village choir, the Balsham Singers. The village has a large recreation ground and bowling green used by football, cricket, and bowls teams.

Media
Balsham is covered by several local newspapers. The Cambridge Evening News is published each afternoon and occasionally contains news about the village, while the Haverhill Echo appears every Thursday. The Saffron Walden Reporter is a free newspaper delivered weekly to every residence in the village. Balsham Review is a monthly parish magazine with local news, sporting reports, and advertisements. Local radio stations include BBC Radio Cambridgeshire and Heart Cambridge.

title: Balsham


text:
Middle Bass Island

Middle Bass Island is an island of the U.S. state of Ohio, located in Lake Erie. A small town, Middle Bass, lies on the island. The 805-acre (3.258 km2) island is shaped like the Big Dipper and is one of three Bass Islands located at the center of a group of 23 smaller islands. It is located in Put-in-Bay Township, Ottawa County, Ohio.

Some of its more famous neighbors are South Bass Island, with the town of Put-in-Bay, Kelleys Island, and Pelee Island.

History
The island was landed upon by French explorer, Robert La Salle, in 1679. The abundance of wildflowers on the island impressed La Salle and his crew so much that they appropriately named it Isle des Fleures, the Island of Flowers. It would retain this name for the next 200 years until it was acquired by a German count in 1856. With the aid of immigrant German workers, the island was used for grape cultivation. This proved to be a very successful undertaking. Old aerial photos of the island (and its neighbor, North Bass Island) show the majority of the island covered with neat rows of grapevines.

By 1875, Middle Bass Island's Golden Eagle Winery was reputed to be the largest wine producer in the United States. The Lonz family acquired the business in 1884 and owned and operated it until the death of George Lonz in 1968. Lonz Winery has often been compared with the wineries of the German Rhineland. The old castle-like structure has been visited by countless dignitaries including five American Presidents. The winery is now part of a corporation bearing the Lonz name. Since 1979, the wines have been made by Italian enologist Claudio Salvador.

On July 1, 2000, tragedy struck the Lonz Winery when a terrace collapsed leaving one dead and dozens injured.

Lonz Winery was purchased by the state of Ohio and Middle Bass Island State Park established in 2001.

Lonz Winery has been renovated by the state of Ohio, and was reopened to the public on June 22, 2017. They are not producing or selling wine on site, but it is open for tours. The nearby Lonz mansion is planned to be renovated and open to the public by 2024.

Tourism
Middle Bass is serviced by the Miller Boat Line from Catawba Island and the Middle Bass Ferry Line from Put-In-Bay. It is common to use Middle Bass as a less crowded base and then take the Sonny S (sole ship of the Middle Bass Ferry Line) to Put-In-Bay for the day.

Middle Bass Island Airport has a 1852-foot runway with commercial air-taxi service. Middle Bass-East Point Airport offers a 2,085-foot turf runway.

title: Middle Bass Island