text:
Race of Champions (Brands Hatch)

The Race of Champions was a non-championship Formula One motor race held at the Brands Hatch circuit in Kent, United Kingdom between 1965 and 1979, and again in 1983. It often attracted high quality entries from the Formula One World Championship. The first race was won by Mike Spence. The last running of the event was the last non-championship Formula One race (excluding the Formula One Indoor Trophy sprint event) and was won by reigning World Champion Keke Rosberg in a Williams-Cosworth after a tight battle with F1 rookie, American driver Danny Sullivan in a Tyrrell-Cosworth.

By Year
† Formula 5000 car

title: Race of Champions (Brands Hatch)


text:
Cyril Cartwright (civil servant)

Cyril George Fox Cartwright (18 April 1911 – 23 April 1943) was a British Colonial Service administrator. He died during the Japanese occupation of the Gilbert Islands.

Biography
Cartwight was the third son of the Rev. G. F. Cartwright. He attended Winchester College from 1924 to 1930; then he proceeded to Balliol College, Oxford and obtained his degree in 1933. He was appointed to the British Colonial Service and was posted to Ocean Island, which was the administrative centre of the Gilbert and Ellice Islands Colony.

He was acting Resident Commissioner of the Gilbert and Ellice Islands Colony on Ocean Island from December 1941 to August 1942. He was acting on behalf of Vivian Fox-Strangways, who had been appointed as Resident Commissioner, but because of the Pacific War, Fox-Strangways was seconded into the army and was located on Tulagi in the British Solomon Islands.

While he had the opportunity to leave Ocean Island when the personnel of the British Phosphate Commission were evacuated, he choose to stay to safeguard the people of Ocean Island. Japanese forces occupied Ocean Island on 26 August 1942. He was subjected to ill-treatment and malnutrition. He died on 23 April 1943.

He is named on the memorial inscriptions in Chapel Passage, East Wall of Balliol College, Oxford.

source: wikimedia

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

title: Cyril Cartwright (civil servant)


text:
Topic talk:Interreligious conflict studies

 * Mark the perfect man, and behold the upright: for the end of that man is peace. Psalms 37:37

Religion and War
What is the source of Religious warfare? When did it begin? Where will it end? Are the battles of Armageddon (Book of Revelation) and Kurukshetra (Bhagavad Gita) related? Could they be the same battle from two different perspectives? Just wondering. CQ 22:07, 16 December 2006 (UTC)
 * Religious warfare is over 6000 years old. The earliest extant texts relating warfare are religious in nature.  I recommend you check out William Hamblin's Warfare in the Ancient Near East to 1600 BC for more details.  The Jade Knight 08:33, 25 March 2008 (UTC)

Jainism
I just wanted to advocate for the inclusion of a topic on Peace in Jainism. Jainism is based on the concept of nonviolence. This religion is, I believe, a key example necessary in this topic as they strive for such a high level of peace, from not eating anything needed to be killed (i.e. everything but nonroot vegetables) to not stepping on bugs, and even to the extreme in somecases of starving to death in order to prevent harm to others. The reason are extensive but I think you get the idea. I just believe it should be included.

Text suggestion
I highly recommend using Warfare in the Ancient Near East to 1600 BC: Holy Warriors at the Dawn of History by William Hamblin. In it, he discusses extensively how, in the earliest records of war extant in the Middle East, warfare and religion were inseparably connected. It's well put together from a historiographical standpoint, as well, and not so technical as to be difficult to understand for normal, educated persons. The Jade Knight 02:34, 21 February 2007 (UTC)


text:
Sanskrit/Introduction

Sanskrit is an ancient language of the Indo-European family, from which is descended many languages found in northern India. The language is also known as 'devabhāṣā' (language of the gods) or 'devavaani' (voice of the gods). Since the 10th century CE, Sanskrit has been primarily written in the Devanaagari script, but it is common for the language to be printed or written in Indian vernacular scripts. The word Sanskrit is derived from the word 'saṃskṛtá' meaning "polished" or "perfectly done". The earliest form of Sanskrit is known as Vedic Sanskrit and was spoken by the people of India in the second millennium BCE. Classical Sanskrit, mostly associated with religion, philosophy, and literature, emerged later in the 5th century BCE after PaaNini's extensive grammar codified the language.

Sanskrit has a rich literary tradition whose most famous poets and playwrights include is Kaalidaasa, mostly known for his compositions Meghadutam, Kumaarasambhavam, Abhijnaanasakuntalam, and Raghuvamsam. The Vedas are written in the Sanskrit language and are the roots of Vedic culture. They are considered to be a collection of great knowledge and spiritual puissance. Samskrita Bharati, an NGO, has taken the initiative to popularize the Sanskrit language.

title: Sanskrit/Introduction


text:
Talk:Gary Leeman

External links modified
Hello fellow Wikipedians,

I have just modified one external link on Gary Leeman. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20130523081340/http://www.macleans.ca/article.jsp?content=20080404_125119_6064 to http://www.macleans.ca/article.jsp?content=20080404_125119_6064

Cheers.— InternetArchiveBot  (Report bug) 11:59, 11 October 2017 (UTC)

title: Talk:Gary Leeman


text:
Perl Programming/CGI

Assuming you already have an Apache server (or compatible server that reads a shebang! line - more on this in a moment) and a Perl installation running, it is fairly simple to start running a Perl program on the Internet.

First, you must have some way to access the program. Here we will deal with form data and submission, so we will assume that your form code in HTML has a property saying ACTION="programname.cgi".

The initial setup
CGI scripts begin like any other Perl program, with a "shebang", something like:

(see Perl Programming/First Programs for details)

Next load the CGI module:

The CGI module makes our work easy because it has pre-programmed functions in it for Internet use. Then we must create a handle to CGI - something that allows us to access the functions. We do this with:

This means that the variable $query is loading the CGI standard functions.

Now that our program is setup using the CGI module, it should look something like this:

So we have a program, it just doesn't do anything yet, and will actually cause a server error because the server has no output or any idea of what kind of output to display even if it had some.

Retrieving Information
Before we tell the server what to do with our output, we need to retrieve our input. To do this, we use the $query variable we declared earlier. Say we have a text box in the form that is named "Name" and we want to find out what was typed there. To do this, we put the following line of code in our program:

Now, this line of code introduces us to the param function (for "parameter"). The param function can do quite a few handy tricks for us, all of them nice ways to retrieve our variables. It processes all of the HTTP coding so all we get is a nice clean variable. Another note, you aren't required to use $Name as your variable. It's simply more convenient to only remember one name for the same variable. Still, use what's best for you.

Output
Now we must create our header information. CGI even makes THIS easy for us. Instead of memorizing a bunch of mime-type declarations (that you may do as well), all we must do is type:

and it prints out our header information. A note about headers. Inside the parenthesis, we may specify parameters like cookies to send to the user's browser. This becomes very useful later. For now we will just stick to the headers.

The last thing you need to put (though the program will run, displaying a blank page without it) is some output. Let's simply have it display the user's name back to them. This would look like.

The finished code
So we now have a complete program that processes a form, using only six lines of code. Isn't Perl great? The final code looks like this:

When put into perspective, we can see that the $query variable is a very important connection to the CGI module as it tells perl that the function you are referencing belongs to CGI; Again, you may declare any variable name in the place of $query so long as you are consistent, though you will find many developers use $query or <tt>$q</tt>. Also note the use of the <tt>escapeHTML</tt> method to avoid any HTML injection problems.

Final note: Make sure you change <tt>/usr/bin/perl</tt> to the path of your perl installation (assuming that is not it) so perl will execute properly.

Frameworks
There are a number of CGI frameworks to help with common CGI programming tasks:

 * CGI::Application
 * Catalyst

Perl/CGI

title: Perl Programming/CGI


text:
Demirar

Demirar (Демирар) is a rural locality (a selo) in Kilersky Selsoviet, Dokuzparinsky District, Republic of Dagestan, Russia. The population was 103 as of 2010.

Geography
Demirar is located 5 km southwest of Usukhchay (the district's administrative centre) by road. Kavalar and Chuvalar are the nearest rural localities.

Nationalities
Lezgins live there.

title: Demirar


text:
The VelociPastor

The VelociPastor is a 2017 American comedy horror film written, directed, and edited by Brendan Steere. The plot follows pastor Doug Jones who becomes infected by an artifact, resulting in him turning into a velociraptor when he becomes angry. After screening at the B-Movie, Underground, and Trash (BUT) Film Festival on August 31, 2018, the film received a wide release in the United States on August 13, 2019, by Wild Eye Releasing.

Plot
Roman-Catholic priest Doug Jones witnesses his parents die in a car fire. He travels to China on a spiritual journey and comes across ninjas searching for an artifact said to turn people into the "Dragon Warrior". After becoming infected by the artifact, Doug begins having nightmares and goes out into the forest late at night as he transforms into a dinosaur. He saves Carol, a prostitute, from a thug.

Waking up in Carol's bed naked, with no memory of the night before, Doug initially believes they had sex, but after Carol tells him what happened he realizes the truth. Unpersuaded by her suggestion to use his new power to fight crime and get rid of people they believe are beyond spiritual salvation, he returns to the church for confession; speaking to Frankie Mermaid, Carol's pimp, he learns Mermaid is the one responsible for killing Doug's parents.

Enraged, Doug proceeds to kill Mermaid and, now convinced about her plan to fight crime, returns to Carol needing her assistance. Father Stewart, learning of Doug's new power, encourages Doug to lose it and stop killing. He takes him to see Altair, an exorcist, hoping to remove Doug's power. In a flashback, we learn Father Stewart saw a war buddy shot while off guard and that his love interest was killed in an accident. Back in the present, the exorcism fails and Doug transforms, taking one of Father Stewart's eyes.

Returning to Carol, Doug is confronted by ninjas. Father Stewart wakes up in a camp of drug-dealing Christian ninjas, led by Wei Chan who plans to sell highly addictive cocaine to people and then cut off supplies. Wei Chan hopes this will lead the addicts to turn to the church where he will eventually take over and use them as his army. Father Stewart rejects this idea and is killed. Doug and Carol are confronted by ninjas and plan to stop Wei Chan.

Doug is stopped by Sam the White Ninja, who he later realizes is his brother. Doug catches Sam off guard and uses telekinesis to take Sam's sword and kill him. Doug and Carol fight off more ninjas and are badly wounded. Doug, fighting off the remaining ninjas, is shot by Wei Chan with an arrow containing anti-venom to stop his transformation. Doug's hands are immune to the anti-venom and he proceeds to kill Wei Chan using his dinosaur powers, among other techniques. Doug carries Carol to the hospital where she recovers.

Doug, no longer a priest and with a billion dollar bounty on his head, plans on traveling the world with Carol and continuing their original idea of killing off criminals.

Production
Brendan Steere came up with the idea in 2010 while he was attending the School of Visual Arts in Manhattan, after his phone autocorrected "Velociraptor" to "Veloci Pastor". As a class project, Steere made a short film of fake grindhouse trailers which included The VelociPastor. His prior YouTube videos had around 45 views each, but the class project received around 45,000 views, resulting in the feature film idea. Steere stated, "The movie is made to be fun, and anybody looking for deeper meaning in the man-turns-into-a-dinosaur genre is probably on a fool's errand."

From 2011 to 2016, two attempts to crowdfund were made, first through Kickstarter and then through Seed&Spark. The film received funding from a private investor that the mother of Steere's friend knew.

Filmed on a budget of $36,000, Steere was influenced by director Guillermo del Toro.

Release
The VelociPastor premiered in Portland, Oregon on November 2, 2017. After being shown at various film festivals, the crew signed with sales agency Cyfuno Ventures who then brokered a deal with Wild Eye Releasing in 2018.

Home media
The film was released on region 1 DVD and streaming on August 13, 2019. The film is also available on Amazon Prime, YouTube and Roku. A Blu-ray was released on September 17, 2019.

Reception
On Rotten Tomatoes the film has an approval rating of 65% based on reviews from 17 critics, with an average rating of 5.5/10.

Alex McLevy, writing for The A.V. Club, said: "This movie is going to endure. It's got a killer hook, is fun to watch, and doesn't overstay its welcome. It has 'cult classic' written all over it." Michael Walsh of Nerdist said: "Is the movie good enough to be considered a truly great comedy? No, probably not. but it's still way better than most people would expect." Amanda Sink from The Hollywood Outsider said: "Albeit no cinematic achievement, The VelociPastor is a hysterically ludicrous horror-comedy that knows its absurdity and has no qualms inviting you in." Jeffrey Lyles on Lyles' Movie Files reports: "It's either the most absurd and ridiculous premise for a movie or the movie you've been waiting all of 2019 to see." Bobby LePire, for Film Threat, wrote: "Brendan Steere, his delightful cast, and committed crew have crafted a bonkers film that never stops entertaining."

Sequel
Steere has stated that he wants to do a sequel as he believes the world of VelociPastor is "so permissible and fun". In March 2020, Steere shared a sneak peek of the script on Twitter, making the announcement that the script was completed and is set to start filming at some point.

Production on The VelociPastor 2 wrapped on October 4, 2023. This is one year after the completed kickstarter where the team raised $118k. There is no release date. A big change from the first film is this one is being directed by Jesse Gouldsbury, the cinematographer and producer on the previous film. The screenplay is written by Brendan Steere and Gouldsbury, with Steere editing the film. Alyssa Kempinski, Carol in the films, has joined the production side as a producer this time around.

title: The VelociPastor


text:
Template:Did you know nominations/Alice Perry

The result was: promoted by Allen3 talk 14:51, 5 March 2015 (UTC)

Alice Perry

 * ... that Alice Perry (pictured) was the first woman to graduate as an engineer in Ireland and the United Kingdom?

Created by Smirkybec (talk). Self nominated at 00:05, 9 February 2015 (UTC).

 * Symbol confirmed.svg New enough and long enough with 2187 B of readable prose. The article is written neutrally, has inline citations, and doesn't not appear to contain any close paraphrasing. Exempt from QPQ as having had fewer than five DYK credits. The hook meets the formatting guidelines, is interesting, accurate, neutral, and supported by an inline citation. The image is free, used in the article, and renders well at 100X100. Request that this be held for International Women's Day on March 8. gobonobo  + c 13:10, 11 February 2015 (UTC)

authors: ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ


text:
Help:Pages

Every page on Wikibooks has a unique name (a string of characters) which appears in that page's URL and by which it can be wikilinked. Various different forms of the name can be used. In particular, the name as it appears in the URL uses underscore characters where the name displayed in large font as the page header uses spaces. Details of the forms of page names and restrictions on them are given below.

Creating
The form below will allow you to easily create a new page. The 'create page' button takes you to an edit page to enter the new text. If you want to experiment, use the sandbox first. The following characters are not allowed in page titles: # < > [ ] | { } and the forward slash (/) is reserved for creating subpages to comply with naming conventions. Names are case-sensitive and spaces are allowed. If you are seeking to create a recipe for the Cookbook or content for children as part of Wikijunior, you need to use a "namespace" prefix before the title (see below).

You can also start new pages by:

 * Following a link to a new page which does not exist yet, which likewise launches the edit page.
 * Adding a link to the new page on an existing page, such as the sandbox, and click the preview button to preview your changes. From the preview area click on the newly created link, which will switch you to editing a new page, if the page does not already exist, without updating the previous page.
 * Typing the name of new page in the address field of your web browser, replacing current page name. Using this method for the new page displays the default "Wikibooks does not have a page with this exact name" message. The default page has the usual Edit tab replaced by a Create tab, which can be clicked to begin adding content.

Links are a convenient way to navigate books and to make followers aware of new pages. Links to new pages typically exist to encourage people to add new material and/or as part of a plan to add new material. Links to new pages typically look different from links to existing pages in that they have a red color, causing them to often be called "red links" or "broken links". When a new page is created links typically change to a blue color, causing them to often be called "blue links" or "working links".

Namespaces

A Wikibooks namespace is a set of Wikibooks pages whose names begin with a particular prefix recognized by the software (followed by a colon), or in the case of the main namespace have no such prefix. For example, the user namespace consists of all pages with names beginning "User:". Books appear in the main namespace, with no prefix.

Wikibooks has 26 current namespaces: twelve basic namespaces, each with a corresponding talk namespace; and two virtual namespaces. These are all listed in the box to the right.

Basic namespaces
Wikibooks' basic namespaces and their functions are listed below.

 * Main namespace (no prefix): contains the general collection of books. Sometimes referred to as "mainspace". Some page names in mainspace start withe prefix Shelf: or Department:; those pages are to help readers find books, but they too belong to a book called the Wikibooks Stacks.
 * Project namespace or Wikibooks namespace (prefix Wikibooks:): contains many types of pages connected with the Wikibooks project itself: information, policy, essays, processes, discussion, etc. The prefix can be shortened to WB: (see Aliases below), and there are many short redirects in the namespace written with capital letters that make pages easier to access, so for instance, Reading room can be abbreviated WB:Reading room or even just WB:RR (due to RR being a redirect).
 * Subject namespace (prefix Subject:): a retired namespace; used to contain pages to help find books related to a specific subject, now replaced by the shelves and departments of the Wikibooks Stacks, in mainspace.
 * User namespace (prefix User:): contains user pages and other pages created by individual users for their own personal use. Pages under this namespace can still be viewed and modified by others, so do not keep any of your sensitive data here.
 * Cookbook namespace (prefix Cookbook:): pages about cooking recipes and methods reside in this namespace.
 * Wikijunior namespace (prefix Wikijunior:): books in this namespace are for infants to be read to and for young children to read to themselves.
 * File namespace or Image namespace (prefix File:): contains file description pages for image, videos, or audio files, with links to the files themselves. See Special:ListFiles. Since many files used in Wikibooks are housed at Wikimedia Commons, those files will not have local pages, but instead mirror file pages from Commons. There are three versions of links to files:
 * [[File:Foobar.jpg]] will insert the image, video, or audio directly into the page, except for audio MIDI files where a text link to the description page will be inserted;
 * File:Foobar.jpg will make a text link to the image, video, or audio description page;
 * [[Media:Foobar.jpg]] will make a text link directly to the image or audio or video clip.
 * The prefix Image: can be used instead of File: (see Aliases below).
 * MediaWiki namespace (prefix MediaWiki:): a namespace containing interface texts, such as the links and messages that appear on automatically generated pages. Pages in this namespace are permanently protected. For a list of these messages, see Special:AllMessages.
 * Template namespace (prefix Template:): contains templates—pages that are intended primarily to be used on other pages to insert standard text or boxes such as navigation links.
 * Category namespace (prefix Category:): contains category pages, which display a list of pages and subcategories that have been added to a particular category, and optional additional text.
 * Transwiki namespace (prefix Transwiki:): "transwiki" is the process of moving content from one Wikimedia project to another. Content in the Transwiki namespace have been moved to Wikibooks, but not yet incorporated into a book or other page.
 * Help namespace (prefix Help:): contains pages which provide help in using Wikibooks and its software, both for readers of books and for editors.

The basic namespaces are sometimes referred to as "article spaces", especially in contrast to "talk spaces". For instance: "File space is the article space of the File talk space."

Talk namespaces
Each of the above namespaces has an associated talk namespace. The talk namespaces are designated by adding talk: to the normal prefix. For example, the talk namespace associated with the main namespace has the prefix Talk:, while the talk namespace associated with the user namespace has the prefix User talk:. Most of the pages in the talk namespaces are used to discuss changes to the corresponding page in the associated namespace. Pages in the user talk namespace are used to leave messages for a particular user. The user talk namespace is special in that, whenever a user's talk page is edited, that user (if logged in) will see a box saying "You have new messages" on the top of every page that they view until they visit their talk page.

Virtual namespaces
There are two virtual namespaces that are not editable: Special and Media.

There are some virtual namespaces that are not editable:

The Special: namespace consists of pages (called special pages) that are created by the software on demand, such as Special:RecentChanges. These pages can be linked as usual, as Special:RecentChanges.

The Media: namespace can be used to link directly to a file, rather than to the file description page. See information above on the namespace.

Modules
A Wikibooks module is defined as a page that has textbook-like material on it and can be used to distinguish a content page from its talk page. A complete Wikibook is typically composed of many Wikibooks modules. With very few exceptions, all the printed text on the paper of a printed version of a Wikibook comes from one or another Wikibooks module of that book.

Only content found in the main namespace, Wikijunior namespace, and Cookbook namespace can be referred to as modules.

But not all pages in those namespaces are considered to be modules; some that are not are:
 * the Main Page
 * the Wikijunior portal
 * the Cookbook table of contents
 * many "redirect" pages, which are used to re-route one page to another page

Aliases
There are eight aliases defined for namespaces: WB: and Project: (both for the "Wikibooks" namespace), WJ: (for the "Wikijunior" namespace), COOK: (for the "Cookbook" namespace), SUB: (for the "Subject" namespace), CAT: (for the "Category" namespace), Image: (for the "File" namespace), and Image talk: (for the "File talk" namespace). All of these are case-insensitive.

If a link is made to a page title beginning with one of these strings, or if such a title is entered in the search box or used in a URL, the alias is automatically replaced by the true namespace prefix. Hence, entering WB:Reading room or Project:Reading room is equivalent to entering Reading room. It is not possible to create a page with a title beginning with one of the alias strings.

Case insensitivity
Standard namespace names and aliases are case-insensitive. The same applies to the first character after the colon. Hence the following all link to the same page:
 * Welcome, Welcome, Welcome, welcome
 * wB:Welcome, wb:Welcome, WB:welcome
 * PROJECT:Welcome, project:Welcome, ProjecT:Welcome, Project:welcome

Namespace-dependent functionality
The following software functions and configurations are dependent on namespace:
 * Search results, listings of recent changes and other special page output (such as Special:AllPages) can be restricted to particular namespaces.
 * The subpage feature can be enabled or disabled per namespace. It is currently disabled for the File, MediaWiki, and Category namespaces. But their talk spaces and all other namespaces have the subpage feature.
 * The random book feature (in the sidebar) feature is restricted to the main namespace.
 * Pages in the category and file namespaces are automatically treated as category pages and file description pages respectively, and links to such pages behave in the corresponding non-standard ways.
 * The template namespace is the default for using brackets (the "Template:" prefix can be omitted when performing these operations).  See Help:Templates for their use.

Discussing
A discussion page (also known as a talk page) is a page which editors can use to discuss improvements to a book or other Wikibooks page.

The discussion page associated with a content page is named "Talk:Example", where "Example" is the name of the content page. For example, the discussion page for discussion of improvements to the book Learning Theories is named Talk:Learning Theories. The discussion page associated with a page in another namespace is named by adding "talk" after the namespace label; for example, the discussion page for Welcome is called Wikibooks talk:Welcome.

User pages also have associated discussion pages (for example, User talk:Example~enwikibooks). When another editor needs to contact you, they will usually do this by leaving a message on your discussion page. When someone has left you a message that way, you will see an information notice the next time you log in or view a page on Wikibooks.

Where to find discussion pages

When viewing a book (or any other non-discussion page), a link to the corresponding discussion page appears on the "discussion" tab at the top of the page. Click this tab to switch to the discussion page; you can then view the discussion page and its history, and edit it if you want to add a question or comment.

If the "discussion" link is red, it means no discussion page has been started yet. Click the red link to begin a discussion page for that content page. (It is also possible for a discussion page to exist while the corresponding non-discussion page is a red link; this often occurs in User space, when a user has received discussion page messages but has not started a user page yet.)

To go back to the content page from its discussion page, use the leftmost tab at the top of the page, labeled "book". For pages other than those in books, this tab may say something different, like "user page" or "project page".

Sections
To discuss a new topic, start a new section by going to a new line and typing a title like this: == Heading ==, replacing "Heading" with a suitable title for the topic you wish to raise. Place new discussions at the bottom of the page. You can also use the tab labeled "add topic", at the top of a discussion page, which performs these steps automatically.

To respond to a discussion already in progress, add your comment below the last entry in the discussion. If you want to respond to a specific comment, you can place your response directly below it. When doing this, keep in mind the advice given below about indentation.

Sign your contributions
You should sign and date your contributions on all discussion pages. To do this easily, type four tildes (~) at the end of your comment, or just click the button on the row of buttons above the edit box. This will be automatically converted into a user signature and the date and time. (You can change the form of your signature using your user preferences.)

Indentation
Indentation is used to keep discussion pages readable. Comments are indented to show whether they are replies to other comments, and if so, which ones.

Comments are indented using one or more initial colons. Each colon represents one level of indentation. You will see these colons in the wikitext when editing a discussion page, but when viewing the page itself you will see the indents.

The first comment in a section will have no colons before it. When you reply to a statement, you should use one more colon than the number that appear in the statement you're replying to. For example, if you're replying to a statement that has 2 colons before it, your response should have 3 colons before it.

The following is an example of a discussion page discussion using indentation. The text typed in the edit box is shown on the left, and the resulting display on the right.

If you wish to reply to a comment that has already been replied to, place your response below the last response, while still only adding one colon to the number of colons preceding the statement you're replying to. In this example, note that Jane, George and Jim are each responding to John ' s comment.

Note that comments are displayed closer together when indented by the same amount (see George's reply in the example above). This can cause confusion to readers glancing through a conversation thread, since several multi-line comments can be mistaken for a single comment. To produce normal paragraph spacing, add a line break first as Jim has done.

The next example shows a more complex discussion. Even though Jane has responded to John first, and Elliot responded to Jane, we can still easily see that George's comment is meant to be in response to John's original question:

Note that if your comment consists of more than one paragraph, you must repeat the colons at the start of each paragraph. An alternative is to type the line break tag   in the wikitext instead of starting a new line.

When a long discussion has many indents, the discussion may be awkward to read, particularly on smaller screens. Eventually, for everyone's convenience, a replying editor will "start over" by responding without any colons at all. The outdent template can be used for this purpose.

You have new messages
After someone else edits your user discussion page, the alert below is automatically displayed on all pages until you view your user discussion page. If you click "new messages", it will direct you to the bottom of your discussion page. If you click "last change", it will show you the last edit done to your discussion page. You have new messages ( last change ).

How to use book discussion pages

 * Communicate: If in doubt, make the extra effort so that other people understand you. Being friendly is a great help. It is always a good idea to explain your views; it is less helpful for you to voice an opinion on something and not explain why you hold it. Explaining why you have a certain opinion helps to demonstrate its validity to others and reach consensus.
 * Stay on topic: Discussion pages are for discussing the page, not for general conversation about the page's subject (much less other subjects). Keep discussions focused on how to improve the page. Irrelevant discussions are subject to removal.
 * Be positive: Book discussion pages should be used to discuss ways to improve a book; not to criticize, pick apart, or vent about the current status of a book or its subject. However, if you feel something is wrong, but are not sure how to fix it, then by all means feel free to draw attention to this and ask for suggestions from others.
 * Stay objective: Discussion pages are not a forum for editors to argue their personal point of view about a controversial issue. They are a forum to discuss how the points of view of reliable sources should be included in the article, so that the end result is neutral. The best way to present a case is to find properly referenced material.
 * Deal with facts: The discussion page is the ideal place for issues relating to verification, such as asking for help finding sources, discussing conflicts or inconsistencies among sources, and examining the reliability of references. Asking for a verifiable reference supporting a statement is often better than arguing against it.
 * Share material: The discussion page can be used to "park" material removed from the page due to verification or other concerns, while references are sought or concerns discussed. New material can be prepared on the discussion page until it is ready to be put into the page; this is an especially good idea if the new material (or topic as a whole) is controversial.
 * Discuss edits: The discussion page is particularly useful to discussion about edits. If one of your edits has been reverted, and you change it back again, it is good practice to leave an explanation on the discussion page and a note in the edit summary that you have done so. The discussion page is also the place to ask about another editor's changes. If someone queries one of your edits, make sure you reply with a full, helpful rationale.
 * Make proposals: New proposals for the page can be put forward for discussion by other editors if you wish. Proposals might include changes to specific details, page moves, merges or making a section of a long page into a separate page.

Good practices

 * Before starting a new discussion, ensure there is not already an existing section on the same topic. Duplicating the same discussion in multiple sections on a discussion page causes confusion, erodes general awareness of points being made, and disrupts the flow of conversation on the topic.
 * Comment on content, not on the contributor: Keep the discussions focused upon the topic of the discussion page, rather than on the personalities of the editors contributing to the discussion page.
 * Sign your posts: To sign a post, type four tildes ( ~ ), and they will be replaced with your username and time stamp, like this: Example~enwikibooks 13:21, 9 May 2008 (UTC). Please note that it is impossible to leave an anonymous comment because your username or IP address is recorded in the page history.
 * Keep discussions focused: Discussions naturally should finalize by agreement, not by exhaustion.
 * Read the archives: If you are a new editor to a book, be sure to read the archives. Not only are content disputes valuable examples of discussion page behavior, but they contain a lot of expert knowledge surrounding the topic. You may quickly find your questions and/or objections have already been answered if you try searching all the archives for that page at once using the prefix parameter.
 * Be welcoming to newcomers: People new to Wikibooks may be unfamiliar with policy and conventions. Please do not bite the newcomers.  If someone does something against custom, assume it was an unwitting mistake.  Politely and gently point out their mistake, reference the relevant policy/guideline/help pages, and suggest a better approach.
 * Avoid posting the same thread in multiple forums. This fragments discussion of the idea. Instead, start the discussion in one location, and, if needed, advertise that in other locations using a link. If you find a fragmented discussion, it may be desirable to move all posts to one location, and linking to it. Make sure you state clearly in edit summaries and on discussion pages what you have done and why.

Unacceptable behavior

 * No personal attacks: A personal attack is saying something negative about another person. This mainly means:
 * No insults: Do not make ad hominem attacks, such as calling someone an idiot or a fascist. Instead, explain what is wrong with an edit and how to fix it.
 * Do not threaten people: For example, threatening people with "admins you know" or having them banned for disagreeing with you. Explaining to an editor the consequences of violating Wikibooks policies, like being blocked for vandalism, is permitted, however.
 * Do not make legal threats: Threatening a lawsuit is highly disruptive to Wikibooks, for reasons given at the linked page.
 * Never post personal details: Users who post what they believe are the personal details of other users without their consent may be blocked for any length of time, including indefinitely.
 * Do not misrepresent other people: The record should accurately show significant exchanges that took place, and in the right context. This usually means:
 * Be precise in quoting others.
 * When describing other people's contributions or edits, use diffs. The advantage of diffs in referring to a comment is that it will always remain the same, even when a discussion page gets archived or a comment gets changed.
 * Generally, do not alter others' comments, including signatures.
 * Do not ask for another's personal details
 * Do not impersonate other editors
 * Do not claim to be an administrator or claim to have an access level that you do not have, as this can be highly disruptive. User access levels can be checked at Special:ListUsers by anyone.

Archiving
It is customary to periodically archive old discussions on a talk page when that page becomes too large. Bulky talk pages may be hard to navigate, contain obsolete discussion, or become a burden for users with slow Internet connections or computers. There may be circumstances where it would benefit discussions to keep older sections visible on the talk pages; namely, to allow newly visiting editors to see which issues have been addressed already and avoid redundant discussion. However, this situation can be better addressed by use of the template. Notices should also be placed at the beginning of the talk page to inform all editors of an archive.

Regular pages are not archived because previous versions may be seen in the history tab; the practice of archiving is particular to talk pages and the reading rooms, which often swell to great length. Archiving one's own user talk page is optional; some users simply blank the page, as the history is kept available for future reference.

When to archive, and what may be the optimal length for a talk page, are subjective decisions that should be adapted to each case. For example, ongoing discussions and nearby sections they reference should generally be kept intact. When archiving by creating subpages cutting and pasting the content should be used, which retains the talk page history in a single location. It is helpful to label archives with dates and a brief summary of the main discussions.

Procedure
Archive pages are usually named as follows: take the name of the talk page, and add '/Archive #', where '#' is the number of the archive. Note that the word 'Archive' has a capital 'A', there is a space before the number, and there are no leading zeros.

For example:

 * the 20th archive of Talk:Main Page would be named Talk:Main Page/Archive 20
 * the first archive of User talk:Example would be named User talk:Example/Archive 1

Remember to use the correct namespace – the part before the colon (:) – when archiving your own user talk page. It should start with "User talk:", not "<tt>Talk:</tt>".

 * 1) Click on Edit for the talk page you wish to archive.
 * 2) In the edit box, highlight all the text you want to archive, right-click (Windows/Linux) or control-click (Mac) and then select cut. The text will then be copied to your clipboard. Note that any WikiProject header templates should remain on the main talk page and should not be cut and pasted to an archive page.
 * 3) While still in the edit window, make a link to the archive name you plan on creating – you can link directly to a subpage by putting a slash (/) in front of it.
 * 4) * If you're making a topical archive, use the name of the topic, for example <tt> /Place of birth debate </tt>.
 * 5) * If you're just archiving old discussion, use the next available number; so if the last archive page was Archive 3, call it <tt> /Archive 4 </tt>.
 * 6) * If there are no archives yet, call it <tt> /Archive 1 </tt>.
 * 7) * Archive links can be conveniently placed in an archive template (How to do this is described in the archive box section below)
 * 8) Save the page. You should now have a page of recent discussion with a red link to your archive at the top.
 * 9) Open the newly created subpage by clicking the red link. Paste the old discussions from your clipboard into the edit box.
 * 10) Add talk archive to the top and bottom of the page. This adds a notice explaining that the page is an archive, and links back to the main talk page.
 * 11) If this is a numbered archive, you can add a navigation template to make it easier to navigate through to other numbered archives. See the navigation templates section below.
 * 12) Save. You have now created an archive.

Automated archival
MiszaBot can automatically create cut-and-paste archives for any discussion page (one that has "talk" in the namespace), by moving sections to a subpage when they have received no comments for a specified period of time. See User:MiszaBot/Archive HowTo for instructions on setting this up.

Navigation templates
If the archive page is a numbered archive page ("Archive #" where # is the number of the archive), you can add a navigation template to make it easier to navigate through to other numbered archives.
 * archive-nav needs the archive number as a parameter – for example on Archive 3.
 * archive nav similar to the above, but a dynamic list of links, – for example on Archive 33.
 * atn is similar, but doesn't need a parameter.

Archive box
On regularly archived talk pages, it is useful to have an "archive box" template. Common usage is to place the archive box below other header templates and before the first section heading so that the box appears to the right of the table of contents. Alternatively, the talk header template will provide automatic links to archives using standard naming.

If the new archive has been created through the cut and paste procedure and if the page already has an archive box, add the link to the new archive page to it if the archive box has a manual listing.

If there is no archive box yet, you may want to set one up. Use the archives template for an automatic listing of archives if using the standard naming. If using nonstandard naming, the template will accept a manual list on a subpage of the talk page being archives. It can also be collapsed and can be configured to include a search box for easy searching of archive pages. See the documentation for details.

Moving
Pages may be moved to a new title if the previous name is inaccurate, incomplete, misleading, or for a host of different housekeeping reasons. When a page is renamed, its page history is attached to the new name, and the previous title is automatically redirected to the new name (bots and administrators have the option of suppressing the redirect). Only autoconfirmed users may move pages due to persistent page move vandalism. If you are an unregistered user or newly registered user, you may request a page move at Reading room/Administrative Assistance.

The terms "rename" and "move" mean the same in this context. They just refer to different models for picturing the operation:

 * rename: keep the page but give it another name; the page history is now attached to the new name; a new page with the old name is created which redirects to the new name and whose page history records the renaming.
 * move: move the contents and the page history to a new page; change the old page into a redirect; change the page history into one that only records the move.

When a page in the file namespace (that is images, media) is moved, the associated file is moved as well. Only Wikibooks administrators can move these pages. Pages in the category namespace cannot be moved.

Reasons for moving a page
There are many reasons why you might wish to rename a page:
 * The title has been misspelled, does not contain standard capitalization or punctuation, or is misleading or inaccurate
 * The title does not follow Wikibooks' naming conventions
 * The name is ambiguous and renaming it in some way will avoid confusion with an existing, similarly named topic
 * The scope of the page has been reduced, extended, or otherwise changed
 * It is a page that has been created as a subpage of a Wikibooks user's user or user talk space for development purposes, and it is ready to be posted to the mainspace

How to move a page
Note that in order to be able to move pages yourself, you must be logged in, and you must be autoconfirmed). Moreover, the move will fail if a page already exists at the target name, unless it is simply a redirect to the present name that has never been modified (check the edit history).

The steps for moving a page are as follows:
 * 1) With the page to be moved displayed, choose the "move" option near the top of the page. In the default layout, this is in a drop-down menu to the right of the screen, after "History" and the "Watchlist" star (see picture). You'll be asked for a new name for the page, and given the option to also move the page's talk page (this box should usually be left checked). Complete the "Reason for move" field (which is like an edit summary). Although filling out the "Reason" field isn't required, you should state a reason for the page move.
 * 2) When ready, click the move button and, if successful, the page will be renamed to the new title.
 * 3) Once the page has been moved, this will be recorded in the Move Log and a "move has succeeded" message will be displayed.

The old title will become a redirect page, so any links to the old title will still go to the new page. However, note that double redirects (pages that redirect to the original page), will not automatically follow to the new page, so you can follow the following procedure to correct this:
 * 1) Open the "What links here" in the toolbox near the bottom of the sidebar.
 * 2) In the section of that page marked filters, click on the button labeled "Hide links". This will result in the page only showing redirects to the prior name. Open each of the redirect pages (best to do so in new tabs), click Edit for each one, and change their target to the name of the page to which you have moved the page.

You should never just move a page by cutting all the text out of one page, and pasting it into a new one; old revisions, notes, and attributions are much harder to keep track of if you do that. (But you may have to if, for instance, you're splitting a page into multiple topics. If you do, please include a note in the new page's edit summary and talk page stating where you took the text from.) Also see below.

Moves where the target name has an existing page
In most cases non-administrators cannot complete a move where the existing page exists. Administrators can move a page, deleting an existing page with a name equal to the new name of the moved page, in one step.

If the new title already exists and isn't just a redirect to the old title, with no history, and you are not an administrator, the wiki will tell you that you can't rename the page. If this happens, list the move at Reading room/Administrative Assistance, or (if the replacement of the existing page merits further discussion) nominate the existing page for deletion (typically via Request for Deletion).

Move-protected pages
Administrators can protect pages from moves, so that only administrators can move them. Pages that are protected from editing are also protected from moves. If a page is protected from moves, the "Move" link will not be available. In this case, you can ask that an administrator move it for you, but you should not manually move the page by copying the contents to the new page and redirecting the old page to the new page, as this destroys the page history.

Undoing a move
To undo a move from page A to page B, simply move page B back to page A.

Note that usual "undo" link on history or diff pages does not work on moves.

The software requires that the redirect be pointing to the page you're moving it from. Therefore, if a vandal moved Page A to Page B to Page C, you cannot simply move C to A, you have to:
 * 1) Move page C to page B
 * 2) Move page B to page A

If page A has subsequently been edited, only an admin can sort things out:
 * 1) Delete page A (make sure it has no useful history)
 * 2) Move page B to page A.
 * 3) Delete page B (should be a history-free redirect to page A)

"Move wars" are highly unproductive, and leave vast numbers of pointless redirects littering the place, which some poor soul will have to fix.

After undoing a move, if you do not need B as a redirect, edit the page and tag it for deletion with.

Swapping two pages
To swap pages A and B, including history:
 * 1) Move page A to page C (previously non-existing)
 * 2) Tag page A for deletion with.
 * 3) Move page B to page A (allowed because A is deleted)
 * 4) Tag page B as above
 * 5) Move page C to page B (allowed because B is deleted)
 * 6) Tag page C as above

Help with this task can be found at Reading room/Administrative Assistance.

Fixing cut-and-paste moves
Sometimes renamings have been performed by new users without access to the move function or by unregistered users who are not permitted to rename pages. Such manual moves were done using cut and paste. As a result, the page history of a page can be split among two or more different pages.

In some circumstances, administrators are able to fix this by merging page histories.

Warning: this procedure may only be undone by an administrator, by spending quite silly amounts of time: to undo a merge, every single version has to be manually reassigned to the correct source page (by deleting the revisions that are in the correct location currently and moving the other revisions to their new correct location, then undeleting the revisions that were in the correct location). Do not do this if you are not sure what you are doing.

Follow this procedure to merge page histories:

 * 1) Suppose we wish to merge edit history from Alabama/History (old title) into History of Alabama (new title):
 * 2) Move Alabama/History to History of Alabama with comment history merge.  A warning will appear stating that the destination page exists and asks whether you want to delete the page to make way for the move.  Check the box to delete the page.
 * 3) Undelete the History of Alabama page.
 * 4) Edit History of Alabama to restore the most recent version.

Note that the page history will often look wrong until the last step here is carried out, because it doesn't update after an undeletion until the next time the page is edited.

Automating multiple page moves
Administrators are also given an option to move up to 500 subpages and talk subpages along with the desired page. This is useful for talk pages with archives. Standard users can move the subpages by hand. If an entire book with its subpages is being renamed, request assistance from an administrator.

Merging
A merger is a non-automated process by which the content of two pages is united on one page. Reasons to merge a page include: unnecessary duplication of content, significant overlap with the topic of another page, and minimal content that could be covered in or requires the context of a page on a broader topic.

Merging is a normal editing action, something any editor can do, and as such generally does not need to be proposed and processed. If the merger is controversial, however, you may find your merger reverted, and as with all other edits, edit wars should be avoided. If you are uncertain of the merger's appropriateness, or believe it might be controversial, or your merger ends up reverted, you can propose it on either or both of the affected pages.

Proposing a merger

 * 1) Create one discussion section, typically on the destination page's discussion page (also known as the talk page). This should include a list of the affected pages and a merger rationale.
 * 2) Tag each page with the appropriate merger tag. All tag discussion page links should be specified to point at the new discussion section.

To propose a merger of two or more pages, place the template at the top of each page or section.

Please use the third parameter to direct to the same discussion page. Otherwise, two separate discussions could take place in each of the respective discussion pages. If the third parameter is not specified, the "discussion page" links lead to the discussion pages of both merger candidates.

If you know which page should be removed, use on that page, and  on the page that will remain and will receive the contents of the source page. Unless a third parameter is specified in these templates, all discussion page links to lead to the discussion page of the destination page, avoiding the two separate discussions problem that may occur with merge. It may still be preferable to link to a section on the discussion page; this is useful for directing the reader to a specific section of a long discussion page, when it may not otherwise be obvious where the discussion is located.

After proposing the merger, place your reasons on the discussion page.

Closing instructions
If there is clear agreement with the proposal by consensus, or if there is silence, proceed with the merger.

To provide clarity that the merger discussion is over and that a consensus has been reached, it may be important to close and then archive the proposal discussion. To close a merger proposal discussion, indicate the outcome at the top. If the merger is particularly controversial, one may take the optional step of requesting closure by an uninvolved administrator at Reading room/Administrative Assistance.

To archive a merger proposal discussion, a closed template is generally placed between the header and the top of the discussion and a end closed template will need to be placed at the bottom of the discussion.

Here is an example of how to archive a merger proposal discussion:

==Merger proposal== Hi, I would like to discuss...

Performing the merger
There are two basic types of merger; which to use depends on how much content of the source page you want to keep:

 * Full-content paste merger - most content, clean and fast
 * Selective paste merger - some content, clean but slow

Also remember that almost all pages have a discussion page. To avoid losing quick access to that historical discussion, a link to the source page's discussion page should be placed at the top of the destination's discussion page, such as:

Full-content paste merger

 * 1) Open the source and destination pages in two separate edit windows/tabs.
 * 2) Cut/paste the entire content from the source page into the destination page and remove the mergefrom tag.
 * 3) Save the destination page, with an edit summary noting "merge content from SOURCE PAGE " (This step is required in order to conform with Wikibooks' licensing requirements.  Do not omit it nor omit the page name.)
 * 4) Edit the destination page again and delete the redundant content, editing until it looks good and consistent.
 * 5) Save the destination page.  (Edit summary of "cleanup after paste/merger" is appropriate.)
 * 6) Check "What links here" on the source page for any links to the page and correct them to point to the destination page instead.
 * 7) Ask for a history merger between the two pages by placing  above all content on the source page.

Performing a merger in this manner is beneficial when you want to include all the content from both pages in the final page and the source page will no longer exist.

Selective paste merger

 * 1) Open the source and destination pages in two separate edit windows/tabs.
 * 2) Cut/paste the desired content from the source page into the destination page and remove the mergefrom tag.
 * 3) Preview and edit the destination page until it looks good and consistent.
 * 4) Save the destination page, with an edit summary noting "merge content from SOURCE PAGE " (This step is required in order to conform with Wikibooks' licensing requirements.  Do not omit it nor omit the page name.)
 * 5) Delete the text taken from the source page, note the merger (including the page name) in the edit summary, and save the page.
 * 6) Check What links here" on the source page and correct any links that should point to the merged content page.
 * 7) Add  onto the talk pages of both pages. This not only helps clarify attribution at the destination, but helps prevent inadvertent later deletion of the source history.
 * 8) Afterwards, DO NOT ask for a history merger between the two pages.

Performing a merger in this manner is beneficial when the source page will continue to exist in a revised form and the page history for that content must be kept in place with the material that remains following the merge.

Deleting
Pages can only be deleted by administrators and community consensus must have been demonstrated. For certain uncontroversial circumstances, users can request a speedy deletion. Any page that does not fall under the scope of the project or has no meaningful content may be nominated for deletion.

Note that the editors will often have contributed the content in good faith and may be offended by the nomination. If you have concerns about whether the content belongs at Wikibooks, begin by addressing it on the talk page. Often the content contributor will understand that it is out of scope and accept the need to move the content elsewhere. Being polite and helpful in finding the relevant portions of Wikibooks policies goes a long way.

Should you nominate a page for deletion, consider notifying major contributors (the deletion tags provide a handy code). Be respectful and detailed. In the case of a speedy deletion, distinguish between worthless content and good faith efforts, both in the speedy tag reason, as well as on contributor pages.

Speedy deletion
There are certain situations where consensus does not have to be demonstrated for each case. See WB:SPEEDY for the list of criteria. Essentially, if a page has no meaningful content, it can be deleted. You can also ask for pages where you are the only contributor of, or pages in your part of the user namespace to be speedily deleted.

To nominate the page, place at the top of the page, with the   citing the speedy deletion criteria.

When in doubt, make a formal request for deletion (see below).

Requests for deletion
Should talk page discussions not bear fruit, you can make a formal request for deletion which consists of three steps.

 * 1) Place rfd at the top of the page in question. If you are nominating a whole book, it's enough to tag the main page.
 * 2) Notify contributors, for example with rfd warning. If they may not have seen the discussion on the talk page, restate your rationale there. Should the content be deleted, the talk page goes as well and your note may be the only sign of that page once they return.
 * 3) Take your request to Requests for deletion. There is a handy link titled "add a new entry" which pre-loads a template and lists a few tips above the text area.

Discussions are rarely closed within a month, but can go on for several times that longer if discussion continues or consensus is not reached. A page is only deleted if there is consensus. Without consensus, the page is kept. As with all consensus decisions at Wikibooks, there are no votes; only arguments.

title: Help:Pages


text:
Hospitality management

THE SCHOOL OF HOSPITALITY MANAGEMENT
A school which will provide a series of modules on key aspects of hospitality management for professionals interested in a career in food service, hotels or the hospitality industry. Additionally this school contains a department which takes care about free Hospitality Exchange Networks.

A Wikiversity school is a large organizational structure which can contain various departments and divisions. The departments and divisions should be listed in the departments and divisions section. The school should not contain any learning resources. The school can contain projects for developing learning resources.

Divisions and Departments
Divisions and Departments of the School exist on pages in "topic" namespace. Start the name of departments with the "Topic:" prefix; departments reside in the Topic: namespace. Departments and divisions link to learning materials and learning projects. Divisions can link subdivisions or to departments. For more information on schools, divisions and departments look at the Naming Conventions.
 * Introduction to the hospitality industry
 * Foodservice Management
 * Hotel Management
 * Hospitality Exchange Networks
 * Tourism

Active participants
The histories of Wikiversity pages indicate who the active participants are. If you are an active participant in this school, you can list your name here (this can help small schools grow and the participants communicate better; for large schools it is not needed).
 * Housetruck247 22:18, 16 May 2009 (UTC)
 * Kylephoto760 15:52, 25 May 2011 (UTC)

School news

 * 14 October 2006  - School founded!

title: Hospitality management


text:
Talk:Sold Out (In Stereo)

"studio album"
This appears to be a live album. <IP_ADDRESS> (talk) 17:09, 24 July 2009 (UTC)

title: Talk:Sold Out (In Stereo)


text:
Talk:Davy Fitzgerald

Capital G
Should it not be Fitzgerald, as seen in the sources? Tameamseo (talk) 16:27, 5 November 2008 (UTC)
 * I would have thought so as well. Derry Boi (talk) 16:53, 6 November 2008 (UTC)

External links modified
Hello fellow Wikipedians,

I have just added archive links to 1 one external link on Davy Fitzgerald. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
 * Added archive https://web.archive.org/20111012101532/http://www.rte.ie:80/sport/gaa/championship/2011/1012/fitzgeraldd_clare.html to http://www.rte.ie/sport/gaa/championship/2011/1012/fitzgeraldd_clare.html

Cheers.—cyberbot II  Talk to my owner :Online 16:23, 18 February 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 1 one external link on Davy Fitzgerald. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20090913063851/http://www.rte.ie:80/sport/gaa/championship/2009/0809/kilkenny_waterford1.html to http://www.rte.ie/sport/gaa/championship/2009/0809/kilkenny_waterford1.html

Cheers.— InternetArchiveBot  (Report bug) 15:53, 30 December 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 3 external links on Davy Fitzgerald. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20160116150838/http://www.sixmilebridgegaa.com/news/showfullnewsstory.asp?id=2383&category=latestnews to http://www.sixmilebridgegaa.com/news/showfullnewsstory.asp?id=2383&category=latestnews
 * Corrected formatting/usage for http://www.rte.ie/sport/gaa/championship/2009/0809/kilkenny_waterford1.html
 * Added archive https://web.archive.org/web/20131004221202/http://www.gaa.ie/gaa-news-and-videos/daily-news/1/0609130813-profile-davy-fitzgerald/ to http://www.gaa.ie/gaa-news-and-videos/daily-news/1/0609130813-profile-davy-fitzgerald/

Cheers.— InternetArchiveBot  (Report bug) 22:08, 4 May 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on Davy Fitzgerald. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20160116150838/http://www.sixmilebridgegaa.com/email/email.asp?id=2244&category=latestnews&title=Down%20Memory%20Lane%20-%20County%20Finals%20of%20the%2090s&firstline=& to http://www.sixmilebridgegaa.com/email/email.asp?id=2244&category=latestnews&title=Down%20Memory%20Lane%20-%20County%20Finals%20of%20the%2090s&firstline=&

Cheers.— InternetArchiveBot  (Report bug) 09:47, 19 September 2017 (UTC)

title: Talk:Davy Fitzgerald


text:
Wikipedia:Featured article candidates/Battle of Cannae

Battle of Cannae
I believe that this is a highly informative page that provides a comprehensive view of the Battle, as well as quotes, tactical dispostions, and its effects. Furthermore, I believe that this article fully meets the given WP:WIAFA for a featured article......--chub 23:16, 23 March 2006 (UTC)

 * Two comments: One, per WP:LEAD, the lead should be expanded, and two, the external links in the text should also be converted to WP:FOOTNOTEs and have citation information. Thanks, AndyZ 20:41, 20 March 2006 (UTC)

 * Approve: But other than the few minor errors mentioned above (which can be easily corrected), I see no other reason why this article shouldn't be accepted--<IP_ADDRESS> 21:07, 20 March 2006 (UTC)

 * You have a lot of inline citations refering to the samefootnotes. Unfortunately, the baclinks will only ever link to the first citation. You might want to convert the article to the system. I'll help if you wantCirceus 22:09, 20 March 2006 (UTC)

 * Support, looks very well-written and well-cited. It would be nice if the citations were converted to format and if the lead was lengthened, both points already brought up, but those alone are not sufficient to stop me from supporting. — Cuivi é  nen , Thursday, 23 March 2006 @ 02:20 (UTC)

 * Comment. Battles articles have usually a picture or a painting of the scene as a lead image. The map is really bad, I took a while before finding the Cannae town. I suggest you improve it by showing only the Italian peninsula. CG 16:59, 23 March 2006 (UTC)

 * Adressing and acting upon comments: I appreciate the advice. I have expanded the lead. I am not aware of the system, so I may need help with improving the citations. --chub 23:17, 23 March 2006 (UTC)
 * Citations I converted the article to Cite.php s ,but there were a couple issues:
 * I found 3 refs without equivalent notes, 2 were labelled "sealy" and one "gowen". They are still in the source, but commented out.
 * If a references does not have footnotes attaches, do not put note before it. These refs are in the "References" section instead of "Footnotes"
 * There are still 2 external links that should be converted to footnotes (The Cannae book link and the Titus livius citation), you might want to look into Cite web
 * I could not properly reference the PDF because I could not access it (A failure I blame on a problem with the PDFdownload extension of Firefox), someone else should fix it.
 * Circeus 15:47, 24 March 2006 (UTC)

 * Support: The article appears to be extremely well-written with numerous citations that are now properly formatted (for the most part). --<IP_ADDRESS> 23:46, 24 March 2006 (UTC)

 * Minor Comments: As far as details and content goes, this article is indeed FA-worthy. Inline citations are properly formatted and the lead has been expanded as requested. However, there is still room for improvement. I recommend that this article undergo minor grammatical revision if (or before) it is to be saved as a featured article (fragments in the lead need to be eliminated. Furthermore, I suggest that (1) The lead include more details about the aftermath of the Battle (it provides a summary of the battle itself but devotes only two lines of info on its effects) (2) and The "United States Military Academy" text on the images be removed (I think they are, for all purposes, unecessary). But other than that, the article seems to be considerably well-written and EXTREMELY informative. --<IP_ADDRESS> 02:20, 25 March 2006 (UTC)

 * The United States Military Academy text is not unecessary - but is part of the conditions of use of the copyrighted images. - Vedexent 16:31, 25 March 2006 (UTC)

 * Another Comment: Someone also needs to check the numbers of casualties, since battle casualties (in all military history articles in general) often have a tendency to contradict each other.--<IP_ADDRESS> 05:41, 25 March 2006 (UTC)

Lead of Article: I've made some minor adjustments to the lead. Unfortunately, I know very little about this topic, so I could not add any further details.--<IP_ADDRESS> 05:41, 25 March 2006 (UTC)

 * The lead is long enough in my opinion. It should not go in-dept and should only contain the most significant details. According to WP:LEAD: "The lead should briefly summarize the most important points covered in an article in such a way that it could stand on its own as a concise version of the article.". The fact that Cannae was not a decisive battle (meaning it did not determine the outcome of the Second Punic War) means that its strategic effects were limited. The defection of Capua and other Italian city states was perhaps the only significant strategic effect from the battle, and it is already mentioned in the lead.--Chubdub 19:06, 25 March 2006 (UTC)

Strong Support + Comment: Looking over these commments and the recent adjustments made, I think the format of this article has been greatly improved. Together with the content (which features highly detailed descriptions about the tactical dispositions and an abundance of additional facts), I would say that this article is certainly FA-worthy. Alhtough I would like to see more pictures of the battle itself rather than just diagrams. I know this is ancient history, and no photos were in existence back then. So I found this "virtual reenactment" from the TV series of Decisive Battles (TV series)

http://home20.inet.tele.dk/creativ/Cannae1.jpg --P.O.N.Y. 19:21, 25 March 2006 (UTC)

 * Unfortunatly such images cannot be used due to copyright restrictions. Images in an article have to be in the public domain, or have permission granted by the copyright holder. - Vedexent 20:46, 25 March 2006 (UTC)

 * Weak oppose
 * I'd like to see my earlier comments on citations acted on,especially about making the PDF cited properly.
 * I don't think the big "trivia" section belong there. After all, if it is "trivia", then isn't it by definition unencyclopedic? If the material in there is really pertinent, then it should be possible to work it in the rest of the article. Circeus 19:52, 25 March 2006 (UTC)

 * Support Article looks great and ready for featuring. Circeus 00:19, 27 March 2006 (UTC)

Weak oppose with hopes the objections can be cleared up so the article gets the FAC it clearly deserves: - This is a well written article, with a balanced approach of Carthaginian and Roman perspectives, it describes the larger background of the war, the rationale of the commanders in their deployment, clearly lays out the stategies of the two forces, what happened as opposed to what was supposed to happen (at least for the Romans), and goes on to explore the results an significance of the battle. I think a lot of praise is deserved by the nominating author who has obviously put a great deal of time, research, and effort into this article.

However, there are large blocks of facts that are mentioned, without citation. The makeup of the forces is in question, but by who - what sources are being accepted by the author? There are claims for the strategy and viewpoint of Varro and Hannibal; facinating and informative, but where do they come from?

I'm of the opinion that there should be a 1:1 ratio of claim (or group of related claims) and referance: "X was the case [1]. This caused Y [2]. There is evidence that Q,W, and W were probably in place, and this most likely would have lead to M[3], although it has been said by others that they would have resulted in P instead [4]." My example is pretty citation heavy (really, citations shouldn't be inside a sentance), but you get the idea.

Unfortunatly there are large blocks of claims that read like they do come out of the volumes in the bilbiography, so I don't think they are spurious, but they are not referenced, so I cannot find them.

This is well written and informative article. I just think it needs to be a little more informative about where it gets the information from. - Vedexent 19:44, 26 March 2006 (UTC)

 * Slight retraction - some of the views attributed to Varro and Hannibal are cited. Plus, the ones that are not could be due to recent re-organization of some of the paragraphs by ... ahem... me.... (mea culpa) - and the citing author may want to examine the "tactical deployment" section to see if the citations need to be moved around. There are other areas that still do have the problem I outlined, however. - 19:51, 26 March 2006 (UTC)
 * Support' with Minor niggling complaint - The author did a boatload of footnoting since my comment. We also discussed the footnoting style, and while I personally would like to see page numbers in the references, they don't seem to be needed for the Wikipedia style :) The only slight complaint I might still have re inline references is that there seem to be two diffrerent styles of footnotes being used - and because of this the numbering sequence seems to jump around out of sequence. Other than that, looks good to go :) - Vedexent 01:03, 27 March 2006 (UTC)


text:
304th Tactical Fighter Squadron (JASDF)

The 304th Tactical Fighter Squadron (第304飛行隊 (dai-sann-byaku-yon-hikoutai)) is a squadron of the 9th Air Wing of the Japan Air Self-Defense Force. It is based at Naha Air Base, in Okinawa Prefecture, Japan. It is equipped with Mitsubishi F-15J/DJ and Kawasaki T-4 aircraft.

History
The squadron was founded on August 1, 1977 at Tsuiki Air Base in Fukuoka Prefecture flying the McDonnell Douglas F-4EJ. A number of the early pilots had previously flown the North American F-86F Sabre with 10th Squadron, which had just been disbanded. During this period the JASDF still followed a system in which the numbering of a squadron was dependent on the type of aircraft it operated. Single digit squadrons operated the F-86F, 100-numbered squadrons operated the F-86D, 200-numbered squadrons operated the F-104J and the new squadrons operating the F-4 were numbered in the 300s. The pilots retrained on the F-4 and from 1978 were responsible for Quick Reaction Alert duties around Fukuoka.

In January 2016, the squadron relocated to Naha Air Base in Okinawa Prefecture as part of the newly-formed 9th Air Wing.

Tail marking
The squadron's aircraft bear the likeness of a tengu on their tails. Tengu are goblin-like creatures from Japanese mythology. Known for their skill with swords and possession of mystical powers, they were said to inhabit Mount Hiko in Fukuoka, located near the squadron's original base at Tsuiki.

Fighter aircraft

 * McDonnell Douglas F-4EJ (1977–1990)
 * Mitsubishi F-15J/DJ (1990–present)

Liaison aircraft

 * Lockheed T-33A (1977–1993)
 * Kawasaki T-4 (1991–present)

title: 304th Tactical Fighter Squadron (JASDF)


text:
User:Sreeraj Kozhukkunnon

Sreeraj is born in 4th April 1982. Completed his primary and upper education in Government schools. He is an average student.

title: User:Sreeraj Kozhukkunnon


text:
Kalateh-ye Luyedani

Kalateh-ye Luyedani (, also Romanized as Kalāteh-ye Lūyedānī) is a village in Zeberkhan Rural District, Zeberkhan District, Nishapur County, Razavi Khorasan Province, Iran. At the 2006 census, its population was 58, in 14 families.

title: Kalateh-ye Luyedani


text:
Talk:XML - Managing Data Exchange

We will work on this soon. thank you, Viji
 * might also want to get rid of that leading space "XML: " - it looks weird and is destined to cause link errors. --IanCarter 00:18, 20 June 2006 (UTC)

This is coming real soon
 * 1) Should the contents maybe be organized into sections, e.g. Basic Concepts, Advanced Techniques, Real-World Examples?

there is a link - it is in real small size and it says => back to XML: Managing Data Exchange. If you know how to make it bigger let us know!
 * 1) Once I am in a chapter, there is no link to get back to the main book - There should be 'up' link?

Proper name
XML stands for "Extensible Markup Language", not "eXtensible Markup Language". You can consult the W3C site to verify.

Many of the examples in the book use tables to put line numbers to the left of code. The numbers do not line up properly with the lines of code in my browser, however (Mozilla). Might I suggest either leaving off the line numbers or including them inline, like I've done in the SVG chapter? I guess a better situation would be if the wiki software could automatically insert line numbers. I realise that the reason for putting the line numbers in a separate table cell is to avoid them being copied to the clipboard if the code is selected.

I thought one way might be to use an <ol> to automatically number the lines, but it seems that Mozilla will copy the numbers to the clipboard too.

 * -- Cam

 * I think it would help a lot if there was some way to have the wiki software format XML. Syntax highlighting and automatic line numbering would really help the readability of these pages. --- Sploo22 12:15, 30 Oct 2004 (UTC)

Goals and audience
I've just popped over here from the Wikipedia XML page. Can someone explain to me:
 * What is the goal, or focus, of this book? Is it basic tutorial? A reference manual? Guidance on advanced techniques?
 * Who is the intended audience? Beginners? Managers trying to get a flavor? Experience XML'ers trying to extend their knowledge?
 * What are the recommended pre-requisites? What knowledge should I have? I noticed a list of recommended software in the Preface.

It's useful to have this sort of information either on the first page, or with an explicit link on the first page.

Thanks.

DanielVonEhren 18:43, 1 Feb 2005 (UTC)

 * I agree yeah. Basically the problem is this book has a section /Introduction to XML, but no section called /Introduction. How about it? -- Harry Wood - 10:28, 2 August 2006 (UTC)

subchapters
I'm a little surprised to find "CSS" and "style sheets" as separate subchapters. IMHO it'd be better to understand when having the tweo subchapters "CSS style sheets" and "XSL style sheets and transformations". BTW why is CSS itself explained (it's not a language defined by XML) instead of the use of CSS within XML? (the "Learning objectives" lists "know how to implement and use CSS on a XML document" but there is mainly CSS for HTML but very few for XML in general) I don't get the point...but maybe there was a discussion earlier :) then please insert the power points into the introduction.

Naming convention
Current book naming convention is depreciated. I suggest changing it to slash convention. --Derbeth 16:37, 2 November 2005 (UTC)

 * I second this suggestion. --Kernigh 03:01, 5 November 2005 (UTC)

Domain-specific languages bookshelf
Hello,

would you please check the Domain-specific languages bookshelf. There are several books on the whish list for which your book has chapters. Do we need extra books or will the chapters be exhaustive enough once they are finished. If the later is true then please trim the whish list.

Many of the chapters are planned for revision. And will probably be revised in future classes. This cycle of revision will be over in June 2006, let see if they give a better picture then

Thank you.

--Krischik T 07:17, 30 November 2005 (UTC)

XML versus Programming:XML versus XML: Managing Data Exchange
The following is a chronology posted by Kernigh:

 * At the start, XML redirected to XML: Managing Data Exchange, and there was a separate book called Programming:XML.
 * At 5 November 2005, Kernigh ( contribs ) decided to propose the merger of Programming:XML, a short introduction to XML, into XML: Managing Data Exchange, general introduction to XML, by marking the two pages with mergeto and mergefrom respectively.
 * At 29 December 2005, <IP_ADDRESS> ( contribs ) made four edits. The first two edits changed other users' comments on this page (Talk:XML: Managing Data Exchange). Kernigh reverted these edits at 18 January 2006. The third edit replaced the redirect at XML with list linking XML to both XML: Managing Data Exchange and Programming:XML (see here. A post to Talk:XML said that XML should become a new book that is a general introduction to XML.
 * From 13 to 17 January 2006, <IP_ADDRESS> ( contribs ) made several edits to XML: Managing Data Exchange, mostly small changes to spelling and presentation format. During this process, <IP_ADDRESS> removed the merge tags of Kernigh, and <IP_ADDRESS> replied to <IP_ADDRESS> at Talk:XML.
 * At 16 January 2006, Derbeth ( contribs ) sent Programming:XML to Votes for deletion.

I have decided to again redirect XML to XML: Managing Data Exchange, and to vote to delete Programming:XML. Because I am redirecting Talk:XML here, you can view the posts of <IP_ADDRESS> and <IP_ADDRESS> through this permalink. --Kernigh 03:32, 18 January 2006 (UTC)

Orphaned pages
I've found Answers (XML) - will you merge it to this book or can it be deleted? Please mark useless pags with delete. --Derbeth talk 00:01, 23 January 2006 (UTC)

Speedy Deletion Candidate
I am confused with a couple of pages I've come across that seem to be related to this Wikibook. All I'm asking for is to have somebody try to explain the rationale for trying to delete these Wikibook modules and to note where the content may have been duplicated or some other editorial reason for trying to delete this stuff. For now, I'm removing the deletion template tags, but if the contributors here would like to remove this content, please make a clear note as to why you feel the content needs to go.

Something simple like: "This is a duplcate of XML: Managing Data Exchange/Introduction to XML" or "obsolete content no longer need for project" is all that I'm looking for. Leaving the reason out nor any discussion on the discussion page about why it needs to be deleted makes it hard for me as an administrator to understand why the content needs to go. Thank you for your work in this part of Wikibooks, however. The pages to review are the following:

 * XML: Managing Data Exchange/Single-Entity (Chapter 2)
 * XML: Managing Data Exchange/Introduction
 * XML: Managing Data Exchange/A single entity (Answers)

--Rob Horning 17:45, 23 January 2006 (UTC)

Thanks!
Hi everyone,

Thanks to everyone that is working on this. Great start. I am an instructor and am trying to create a series of free XML learning modules usable in Moodle and I would like to use/reuse as much work as possble.

I teach in the US and many of the organizations use ISO/IEC 11179 date element names (see the WikiPedia entries on ISO/IEC_11179. This uses an UpperCamelCase three part name.

My goal is to start with very simple re-usable teaching structures and build on them. I would also like to add quiz materials in some XML format for Moodle. I am looking into that now.

I put a sample of what I am working on here: XML Schema before I realized that some of the tables were part of your materials. I apologize for the duplication.

Also, please tell me more about yourselves, your background and objectives. Anyone build re-usable learning objects before? Leanrning Objects. I have not done this in the past. Everything was a one-off based on my library of over 3000 PowerPoint slides. It seems very hard to be able to design learning modules that can be re-used by many people.

- Dan User:dmccreary

Hi Dan !

Thanks for your interest! You have just stumbled upon a work in progress and you will probably see many changes in the coming months. We are students at the University of Georgia in the Management Information Systems department. This XML wikibook is a class project. We are learning, teaching, and revising together. Dr. Watson is our teacher and I am a member of the Editorial Board. Things are just getting started and may appear a bit messy, but we are working on organizing and cleaning up the book. Feel free to give us suggestions (we saw your post in the one to one relationship chapter). It is nice to have outside eyes. Also, you can just email me at<EMAIL_ADDRESS>
Thanks, Viji

Neat professional book
Good job. But dont forget the PDF Version when you have finished. See PDF versions. I have started a Print Version template to get you started. RobinH 20:42, 9 March 2006 (UTC)

Thanks for your input!

Rtw 18:39, 26 March 2006 (UTC) Thanks for the pdf

Warning
I am going to remove Image:Tree.PNG, Image:TreeBranch.PNG and perhaps other images without license information used in this book. I tried to contact the uploader of these images but did not get any answer. --Derbeth talk 08:46, 27 July 2006 (UTC)

Orphans
These pages are not linked to from anywhere in this book. Please either incorporate them into the text or mark them for deletion by typing on each page.

 * XML - Managing Data Exchange/Parsing
 * XML - Managing Data Exchange/Print version
 * XML - Managing Data Exchange/XSL from chapters
 * XML - Managing Data Exchange/C.3
 * XML - Managing Data Exchange/C.4
 * XML - Managing Data Exchange/C.5
 * XML - Managing Data Exchange/C.6

Thanks! --hagindaz 22:30, 28 July 2006 (UTC)

Idea
I haven't seen a chapter about in-line documentation in programming like C#. There is a recommendation for tags to be used in such comments:  It might we worth mention if it hasn't been already. --Stefán Örvarr Sigmundsson 02:01, 27 September 2007 (UTC)

PDF request!
Hi Folks,

Can i please ask for a PDF version of this XML manual? Thanks
 * Ditto -- Sj (talk) 02:34, 1 February 2009 (UTC)
 * I agree - a PDF would be very handy! -- MHCABI (talk) 22:40, 28 June 2009 (UTC)

Document Type Definitions
I think we should add a chapter on DOcument Type Definitons. While XML Shemas can be usful in certatin contexts, DTDs sould be mentioned I will add a chapter right after Data Schemas If there are any objections please say so Wolframalpha (talk) 02:09, 11 June 2009 (UTC)

Syntax Highlighting Extension
I've seen a lot of books using a Wiki extension called SyntaxHighlighting_GeSHi. I think it would be nice to have such highlighting around here. I'm just a beginner at WBooks but I may try to help with the syntax highlighting if you need, it may take a while for me to get all gears going but I'd love to contribute!

Congratulations for the good work you've dedicated to this book!

Hopugop (discuss • contribs) 18:51, 11 December 2011 (UTC)

Suggested IDE/editor for this textbook?
Should there be a recommended IDE or XML editor for this textbook? The preface recommends NetBeans, which is lovely (depending on how you feel about Oracle...), but then there's also a whole chapter near the end of the book about the proprietary Exchanger XML Lite editor, and the rest of the text is IDE-agnostic. It seems that the book could benefit from either referring to a consistent editor (e.g. all the examples being NetBeans-specific, with a YMMV note for those using other software), or from intentionally exposing the reader to a wide range of software. As it is, it's inconsistent and perhaps confusing to people new to markup languages and text editors. Sandbergja (discuss • contribs) 16:37, 8 September 2012 (UTC)

Reviewing page
Hello, can someone review this article edit: XML - Managing Data Exchange/SVG!? There are also some fixes in. Thanks in advance. (PS: I'm from the german SVG-WikiProject) -- Perhelion (discuss • contribs) 18:25, 23 February 2013 (UTC)

Hyphen in the title?
Any idea why the title of this book uses a hyphen (-) instead of the (arguably) more correct en dash (–)? — Ivan Shmakov (d ▞ c) 22:00, 29 January 2014 (UTC)

What is Markup?
XML is known as markup language, which defines some types of rules that can be easily understood by human or machine to encode XML document. So here, whatever information is added to the XML document, it can be kept with some rules that define different labels for information. We can also call the set of symbols that used to store information.

If you want more just look here. XML Tutorial

title: Talk:XML - Managing Data Exchange


text:
Teknowhore

TeknoWhore is a studio album by the American industrial metal band Bile, released in 1996. The album was released on the now defunct Energy Records and had not been reproduced since the company's fold in 2000. After being out of print for three years, Bile decided to re-release the album alongside their out-of-print first release, Suckpump, as a digipak titled Frankenhole in 2003. TeknoWhore was written and recorded by Krztoff, produced by Krztoff and Slave, mixed by Slave, and engineered by Steve Spaperri and Patrick Gordon.

Critical reception
The Washington Post wrote that "the band's world view is as contrived and perverse as its style, which alternates slamming synthbeats with aimless interludes of burbling music and ironic samples from old movies and documentaries."

Track listing

 * 1) "Intro" - 2:09
 * 2) "Teknowhore" - 2:08
 * 3) "Weather Control" - 4:38
 * 4) "No One I Call Friend" - 6:28
 * 5) "Habitual Sphere" - 4:38
 * 6) "Compound Pressure" - 5:14
 * 7) "Interstate Hate Song" - 3:35
 * 8) "Green Day" - 1:12
 * 9) "No I Don't Know" - 2:31
 * 10) "Suckers" - 2:18
 * 11) "Lowest Form" - 4:54
 * 12) "You Can't Love This (Pt. 1)" - 1:00
 * 13) "You Can't Love This (Pt. 2)" - 6:08
 * 14) "You Can't Love This (Pt. 3)" - 3:21
 * 15) "You Can't Love This (Pt. 4)" - 6:26
 * 16) "Solitude Is Bliss" - 10:15

Credits

 * Bile in the studio:
 * Krztoff - Lead vocals, guitarz, bass, sitar, drums, distortions, atmospheres, Kawai K-1, samples, porno, programming, Zoom FX, pedals, Roland W-30, line input overdrives.
 * Slave - a.k.a David Stagnari - Programming, EMS-Synthi, RFB-40 shortwave, Juno-106, Korg Monopoly, Oberheim Matrix 6, samples, loops, treatments.
 * Brett and Archie A.K. did backup vox on "Teknowhore" and "No I Don't Know."
 * Omen spewed 'emu omenfuck' backgrounds on "You Can't Love This."
 * Bile on the road:
 * Krztoff - Lead vox, guitarz, programs
 * Brett Pirozzi - Vox, bass, guitar
 * R.H. Bear - Keyboards, bass and video
 * Slave - Keyboards, EMS Synthi, programs
 * Darrell - Lightning and effects
 * No Live freakshow:
 * Produced by Slave and Krztoff
 * Mixed by Slave
 * Recorded in Music Palace, Long Island, N.Y., Summer-Fall 1995
 * Engineered by Steve "Potso" Spaperri and Patrick Gordon
 * 1/2in. tape editor - Slave
 * Album arrangement, sequence and interludes by Krztoff and Slave

title: Teknowhore


text:
liker

Etymology 1
From.

Noun

 * 1) One who likes.

Etymology 2
From.

Etymology
From.

Verb

 * 1)  to like

Etymology
From, , from.

Adjective

 * 1) alike, similar
 * 2) equal
 * 3) probable
 * 4) suitable, appropriate

Etymology
From, from.

Noun

 * 1) liqueur

title: liker


text:
Talk:Thaimail

De-PRODed
Pinging Piotrus per request. Thaimail was Thailand's first and largest free web-mail provider in the '90s. There must surely exist reliable sources covering it that satisfy the GNG, but since it was twenty years ago they'd mostly be offline. --Paul_012 (talk) 04:43, 27 April 2017 (UTC)
 * Its closure in 2015 was widely reported on, included by the news station Voice TV. --Paul_012 (talk) 04:54, 27 April 2017 (UTC)

title: Talk:Thaimail


text:
strisciare

Etymology
From.

Verb

 * 1)  to rub
 * 2)  to crawl
 * 3)  to wheedle; to be obsequious; to curry favor
 * 4)  to drag
 * 5)  to scrape; to scratch
 * 6)  to swipe (a credit, debit, etc. card)
 * 7)  to graze, to touch lightly
 * 8)  in the game of tressette, to strike a card against the table to indicate that one has only simple cards of the same suit
 * 1)  to scrape; to scratch
 * 2)  to swipe (a credit, debit, etc. card)
 * 3)  to graze, to touch lightly
 * 4)  in the game of tressette, to strike a card against the table to indicate that one has only simple cards of the same suit
 * 1)  to swipe (a credit, debit, etc. card)
 * 2)  to graze, to touch lightly
 * 3)  in the game of tressette, to strike a card against the table to indicate that one has only simple cards of the same suit
 * 1)  in the game of tressette, to strike a card against the table to indicate that one has only simple cards of the same suit
 * 1)  in the game of tressette, to strike a card against the table to indicate that one has only simple cards of the same suit

title: strisciare


text:
User:Ajay Hebbalkar

Ajay Hebbalkar born on 4th May 1994 in Dharwad Karnataka, India. His Parents are Prakash Hebbalkar and Padma Hebbalkar.His sibling is Akshata Hebbalkar. He completed his school in St Joseph's High school Dharwad. Pre University in Karnatak science College Dharwad. Engineering in KLS VDRIT Haliyal, and Completed GME from Mangalore Marine College, in Mangalore.

title: User:Ajay Hebbalkar


text:
Bloom's Taxonomy

Bloom's Taxonomy *

Benjamin Bloom created this taxonomy for categorizing levels of abstraction - thus providing a useful structure in which to describe Lesson Plan Components: Interest Approach, Discussion, Presentation, Demonstration, and Test Items. Content Goals start with an active verb. Note the 'Cues' below, which suggest active verbs that may be used when creating Lesson Plan Components. See the Example Lesson Plan.

Knowledge
 * observation and recall of information
 * knowledge of dates, events, places
 * knowledge of major ideas
 * mastery of subject matter
 * Cues: list, define, tell, describe, identify, show, label, collect, examine, tabulate, quote, name, who, when, where, etc.

Comprehension
 * understanding information
 * grasp meaning
 * translate knowledge into new context
 * interpret facts, compare, contrast
 * order, group, infer causes
 * predict consequences
 * Question Cues: summarize, describe, interpret, contrast, predict, associate, distinguish, estimate, differentiate, discuss, extend

Application
 * use information
 * use methods, concepts, theories in new situations
 * solve problems using required skills or knowledge
 * Cues: apply, demonstrate, calculate, complete, illustrate, show, solve, examine, modify, relate, change, classify, experiment, discover

Analysis
 * seeing patterns
 * organization of parts
 * recognition of hidden meanings
 * identification of components
 * Cues: analyze, separate, order, explain, connect, classify, arrange, divide, compare, select, explain, infer

Synthesis
 * use old ideas to create new ones
 * generalize from given facts
 * relate knowledge from several areas
 * predict, draw conclusions
 * Cues: combine, integrate, modify, rearrange, substitute, plan, create, design, invent, what if?, compose, formulate, prepare, generalize, rewrite

Evaluation
 * compare and discriminate between ideas
 * assess value of theories, presentations
 * make choices based on reasoned argument
 * verify value of evidence
 * recognize subjectivity
 * Cues: assess, decide, rank, grade, test, measure, recommend, convince, select, judge, explain, discriminate, support, conclude, compare, summarize

*Adapted from: Bloom, B.S. (Ed.) (1956) Taxonomy of educational objectives: The classification of educational goals: Handbook I, cognitive domain. New York ; Toronto: Longmans, Green.

Note: IPSI uses Bloom's work as modified by Simpson and Kratwold to create three domains: cognitive, psychomotor, and affective. The first, second and fourth levels of Bloom form the cognitive domeain. The third level of Bloom forms the psychomotor domain and the fifth and sixth levels of Bloom form the affective domain. Accordingly, content will be parsed into one of nine categories --- three levels of cognitive, three of psychomotor and three of affective. These nine categories are sufficiently precise so that prescriptions regarding instruction and testing can be aligned with the intent expressed in content goals.

title: Bloom's Taxonomy


text:
Sovetsky Put

Sovetsky Put (Советский Путь) is a rural locality (a selo) and the administrative center of Novomikhaylovsky Selsoviet, Loktevsky District, Altai Krai, Russia. The population was 652 as of 2013. There are 7 streets.

Geography
Sovetsky Put is located 26 km northwest of Gornyak (the district's administrative centre) by road. Removsky is the nearest rural locality.

title: Sovetsky Put


text:
Warren Faidley

Warren Faidley (born May 11, 1957) is an American storm chaser. Faidley is credited as the world's first full-time, professional storm photographer.

Biography
Faidley is a graduate from University of Arizona and Pima Community College.

His very first tornado chase landed him in Saragosa, Texas a small community that had been swept away by a violent F4 tornado on May 22, 1987. His professional career was launched in October 1988 after he took a photograph of lightning hitting a light pole in an oil and gasoline tank farm in Tucson, Arizona. The image was published in Life Magazine, billing him as a "Storm Chaser."

In 1997 Faidley was the subject of Stephen Kramer's book Eye of the Storm.

title: Warren Faidley