text:
Guitar/Chord Reference

= Open Chords =

Open chords tend to sound "richer" than corresponding barre chords due to the fact that open strings resonate freely without any hindrance. Open chords typically sustain longer than their barre chord equivalent. An open chord is any chord that has one or more strings sounded without being fretted. Guitarists tend to use this name to refer to the chords that contain open strings that are played in the first position (first four frets).

Barre chords
Barre chords use a movable shape that can be shifted up in pitch and down in pitch along a string to give different keys.

Open seventh chords
Seventh chords, strictly speaking from a music theory perspective, means any seventh chord, including major, minor, dominant seventh, diminished and so on. In a beginning guitar context, however, "seventh chord" often means a dominant seventh chord, which is a major triad with a flatted seventh. The G dominant seventh chord, or G7 chord, is the notes G, B, D and F.

Chords in C major
Note that the chords in the key of C major consists of 3 major chords, 3 minor chords and 1 diminished chord. This holds true for all major keys.

Apprendre la guitare/Accords

title: Guitar/Chord Reference


text:
Urdu/Cover

Urdu

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

title: Urdu/Cover


text:
Statics

Objective
By the end of this course, you should understand the fundamentals of forces and moments, and be able to solve equilibrium problems for rigid (non-deformable) bodies in both two and three dimensions.

What You Should Already Know
In order to completely comprehend the material in this course, you should have a firm understanding of all math leading up to Calculus I. Also, an understanding of basic physics, as well as technical sketching is useful.

Introduction

 * Introduction to Statics
 * Measurement and Units
 * Vector Math

Forces

 * Newton's Laws and Equilibrium
 * Forces As Vectors
 * Resultants of Force Systems

Equilibrium For Points and Rigid Bodies

 * Rigid Body Equilibrium
 * Two-Dimensional Equilibrium
 * Three-Dimensional Equilibrium

Structural Analysis

 * Trusses
 * Method of Joints
 * Method of Sections
 * Multiforce Members

Internal Forces

 * Internal Forces

Moments of Inertia

 * Moment of Inertia

Center of Gravity and Centroids

 * Center of Gravity and Centroid
 * Center of Gravity Problems

Quizzes and Tests

 * Quizzes
 * Tests

Acknowledgement and Further Reading
Acknowledgements and Further Reading

Printable Version
There is a printable version of this book.

Física/Estática Mécanique, enseignée via l'Histoire des Sciences/Statique Introdução à Física/Estática

title: Statics


text:
Amateur Radio Manual/Conductors and Insulators

Certain elements, like copper in our discussion on atoms, have their valence electrons held weakly in their outer orbit. By supplying energy to the material (one way would be to heat it), we can make the electrons move randomly from one atom to the next. We could also attach a negative source of energy that repels the electrons and attach at the other end a positive source that would attract the electrons. This would force the electrons to move from the negative end to the positive end. We call that net movement of electrons 'electric current'. Substances that have this ability are known as conductors, and most metals are conductors of electrons.

Insulators, on the other hand, have their valence electrons bound tightly to the nucleus of the atom. They will not, under normal circumstances, allow the electrons to move easily by supplying energy to the material. However, note that by supplying enough energy (like a lightning strike) we can force even tightly held electrons to move.

Common insulators are porcelain, rubber, glass, and plastic. Be cautious with plastics however, some of them can be very good conductors and it is not easy to tell one from another.


text:
Statistics/Testing Statistical Hypothesis

There are many different tests for the many different kinds of data. A way to get started is to understand what kind of data you have. Are the variables quantitative or qualitative? Certain tests are for certain types of data depending on the size, distribution or scale. Also, it is important to understand how samples of data can differ. The 3 primary characteristics of quantitative data are: central tendency, spread, and shape.

When most people "test" quantitative data, they tend to do tests for central tendency. Why? Well, let's say you had 2 sets of data and you wanted to see if they were different from each other. One way to test this would be to test to see if their central tendency (their means for example) differ.

Imagine two symmetric, bell shaped curves with a vertical line drawn directly in the middle of each, as shown here. If one sample was a lot different than another (a lot higher in values, etc.) then the means would be different typically. So when testing to see if two samples are different, usually two means are compared.

Two medians (another measure of central tendency) can be compared also. Or perhaps one wishes to test two samples to see if they have the same spread or variation. Because statistics of central tendency, spread, etc. follow different distributions - different testing procedures must be followed and utilized.

In the end, most folks summarize the result of a hypothesis test into one particular value - the p-value. If the p-value is smaller than the level of significance (usually $$\alpha=5%$$, but even lower in other fields of science i.e. Medicine) then you reject the null-hypothesis, but this does not mean you accept the alternative hypothesis. The p-value is essentially the probability of obtaining a test statistic at least as extreme as the one observed. If the p-value is greater than the level of significance you fail to reject the null-hypothesis, but this does not mean that the null-hypothesis is correct.


text:
Conworld

Creating Your Own World
Conworld is a shortened form of constructed world. Thus, "conworlding" is world constructing, (otherwise known as world building) the art of creating fictional worlds. The ideal conworld is one with depth, consistency, and beauty, which is why Tolkien's Middle-earth is often held as the best existing example of a conworld. But conworlds are usually as beautiful as they are difficult to make.

Conworlding is a many-faceted process, and can be divided into a large number of sub-fields, each of them with its own enthusiasts. For example, conlangers are people who like to make their own languages (known as conlangs, short for constructed languages). Conmappers like to draw maps of fantasy worlds. Consports enthusiasts dream up games that might be enjoyed in a fantasy world. In general, the prefix "con-" in front of any real-world field turns it into its conworlding counterpart: conmusic, conart, conpoetry, conhistory, consocieties, conreligions, conphilosophies... the list goes on. Name any area of study, and chances are that a conworlder has dabbled in it already!

Many people have had conworlding ideas before: a sketched map, a drawing of an outlandish race, or a simple secret language. At this point budding conworlders ask: "Now what?" So I have a map — How do I decide where the mountains go? How do I make the language sound cooler and less boring? How do I make up impressive mythologies? Can I create music that doesn't sound like any sort of music on earth?

It might seem that for really thorough answers to those questions — if you don't care how much time or effort it takes to get them — you would want to research the actual branches of science that deal with those things: geology, linguistics, anthropology, music theory, etc. Doing it that way could take an enormous amount of time and effort, though. These are all huge subjects, and the things about them that are of most interest for conworlding may not be the things that are of most interest to specialists in those fields. Details that would be of great value to you may be buried in a sea of details. High-level insights of the sort you need for conworlding may be entirely absent from the literature of the subject, because the sorts of alternative situations that matter to a conworlder may not be what experts in the subject spend their time on.

What you need is a guidebook, not to the whole subject, but to the things about the subject that especially matter for conworlding. That's where this series of books comes in. We'll tell you what you need to know for conworlding, skipping over the superficial tourist traps, and including the really interesting sights that aren't on the standard tour.

So pick an area that interests you, and start creating!

The Way of Con | Example Conworlds | Writing fiction set in your conworld

Conplanet | Conmap | Conlang | Consociety | Conhistory | Conreligion | Conphilosophy | Conart

title: Conworld


text:
Conlang

Conlanging is the craft of creating languages. People create languages —conlangs— for all sorts of reasons, practical, theoretical and artistic. This book will show you how. The book has three parts, each aimed at a different level of experience; they are meant to be read in order, but more proficient readers may skip earlier sections.
 * The Beginner level takes you through the steps of creating a conlang, without a lot of technical details and terms. With the help of this level, you can make an interesting conlang that doesn't accidentally copy the sound and feel of your native language.
 * The Intermediate level takes you through the parts of a language, avoiding really esoteric technical details and terms, but providing a systematic working knowledge of the building blocks from which conlangs are made. With the help of this level, you can make conlangs with added depth.
 * The Advanced level explores language features and techniques that can give a conlang extra flair. With the help of this level, you can make conlangs that are sophisticated, exotic, or even outright alien.

{| align="center" width="100%"
 * width="50%" valign="top" style="border:1px solid #0066bb;padding:1em;padding-top:0.5em"|

Other resources

 * Linguistics
 * IPA
 * The Conlanger's Library
 * Word generators
 * Awkwords, a simple word-generating website
 * Drift, a script in the Python programming language that generates words
 * WALS, World Atlas of Language Structures
 * CALS, Conlang Atlas of Language Structures
 * width="50%" style="border:1px solid #0066bb;padding:1em;padding-top:0.5em" valign="top" |

 * }

Glosopoesia שפות_מתוכננות

title: Conlang


text:
Conlang/FAQ

Here are answers to some frequently asked questions related to conlanging.

What's a "Language"?
There are many ways that people communicate with each other, but we don't usually call all of them "language". So presumably, any definition of the word should be somewhat selective.

When linguists talk about language, they usually refer to communication that uses very specific parts of the brain (the and  areas), and that has, as a result, some very peculiar characteristics that may be due to the architecture of those areas. For example:

 * 1) Languages can be learned "natively".  As children, we learned spoken languages from our parents and friends, without any need for formal instruction.  You can't say this about arithmetic or even written language — those had to be learned consciously, either by having someone teach you, or, at least, through some conscious, rigorous study on your own.  This is also the difference between a language you actually speak and a language you took in school — the latter you had to memorize and so forth, so you probably aren't that fluent in it; the former you soaked up, so you speak it natively.
 * 2) Languages have rules.  No, we're not just talking about the rules you learned in English class, and hated.  (Trust us, we hated those too.)  Every language has intricate, complicated rules that are coded right into our brains when we learn it.  Most of the time, we don't even realize we're following them.
 * 3) Languages use words.  Yeah duh, you say.  But think about it this way — when someone says "bird", there's nothing in their mouth, on the "b", or the "ir", or the "d", that's got anything to do with a bird.  But it means bird anyway.  That's the power of words in a language, since words can abstractly represent things without actually looking or sounding like those things.  (Of course there are words that break this rule, like "splash" and "crash", but the point is, not ALL words have to be like that.)

If we follow all of the above rules, then there are just two or three basic sorts of languages in the world — spoken languages, like English or French or German (it doesn't matter if they're sometimes represented in writing); sign languages, like American Sign Language; and, to some extent, written languages. Encodings, like Morse code, Semaphore, etc., aren't language in themselves, although they can be used to directly represent language.

The status of written language is a bit complicated. Writing is often treated as just a representation of spoken language, in which case it's an encoding and not language in itself. There exist conlangs that are purely written, though, with no spoken form at all, like ; these clearly aren't encodings of something else. They might fail the test of being learnable natively — but most conlangs are never learned natively by anyone (the biggest exception being Esperanto, with perhaps a thousand native speakers), so whether most conlangs could be learned natively is already a matter for speculation.

When a spoken language has an extensive literary tradition, the spoken form of the language tends to change faster than the written form, so that after a while the language has two different registers — a formal (or "literary") register and an informal (or "vulgar") register. This effect is called. The different registers aren't usually considered separate languages as such; but since, for example, written English is often the common language shared by native speakers of English and American Sign Language, some have suggested that perhaps written English should be considered distinct from both. That would mean that if you both speak and write English, you're bilingual.

Also, when any encoding is used intensively for direct communication, rather than just as a transcription of speech, the encoding tends to develop idioms of its own that don't come from the language it supposedly represents. In Morse code, for example, the "abbreviation" for laughter is HI, because of how it sounds in Morse code (not because of how the represented letters sound in spoken language): dit-dit-dit-dit dit-dit. That doesn't make Morse code a language, but it's one small step in that direction. Written languages may develop small flourishes like that as well, like.

Other forms of communication, like traffic signs, hand gestures (that are not structured signing), dogs barking, bees dancing (even assuming that is communication, which is debated), etc. are not languages, in the linguists' sense.

Are there simple and complicated languages?
Yes — but probably not in the way most people think.

Some languages have been written down for a long time, have lots of literature and poetry to go with them, and have thick grammars too. These languages are "richer" in the sense that they may have a bigger vocabulary and a richer library of cultural links and so on. But they are not more "complicated".

Linguists have found that pretty much all languages, from those spoken by the simplest nomads to the builders of great empires, are all about similarly "complicated", in the sense that they all have the complex structures necessary to convey human thought and reason. The aboriginal languages of North America, for example, have been found to have massive verb tables that put Latin and Greek to shame. And while languages like English and Chinese don't have these verb tables, they do have complicated systems of syntax (or sentence structures) that put those North American languages to shame.

What about people who say, for example, that "Spanish is easier to learn than German"? Well — a lot of this depends on the way the language is taught in schools, the amount of sheer memorization demanded of beginners, and how similar the language is to your native language. If you're a native English speaker, for example, you may find Japanese baffling, but Korean people usually find Japanese easier to learn than English!

Simple languages do exist, in two ways. Pidgins are broken, halting "languages" that people who can't speak each other's languages end up speaking. If these pidgins are taught to children in a community, however, they tend to become full languages within a generation — what we call creoles — so a pidgin can be seen as a new language in the process of birth. On the other hand, dying languages are languages that few people speak, and therefore aren't really being taught to children — these languages tend to get simpler and then die out.

When did language begin?
It's very hard to know, since we didn't have tape recorders back then. We are reasonably sure, however, that language has been spoken for a very very long time, tens of thousands of years at least, many centuries before agriculture or civilization began anywhere in the world. This is because all people everywhere today, in every corner of the world, speak languages as complex as everyone else's.

By the way, languages did not begin in Egypt or Sumeria (as far as we know, anyway). Those were just the first cultures we know of to write down languages that they already spoke. Languages must have been spoken by all human beings many millennia before that.

What's the difference between a language and a code?
A language has a unique grammar, phonology, vocabulary, and set of "roots" from which new words can be derived. All natural languages are descended from parent languages, as well, though for conlangs this is not strictly necessary.

A code or cipher, on the other hand, is merely a way of changing one language into something else. Codes and ciphers have no set grammar, vocabulary, or anything like that, and usually exist solely for the purpose of obscuring communication.

Too many people will get a dictionary and create a single counterpart for every word in there and then proclaim, "Look! I invented a language!" This isn't altogether a new language, though. Conlangers call this sort of vocabulary-replacement a relex, and it's one jumping-off point to get into creating languages; but there's more to a real language that just its dictionary.

What's the "Sapir-Whorf hypothesis"?
If you hang around conlangers for long, you'll hear references to "Whorfianism" or the "". Those are two names for the same thing, which also goes by other names such as "principle of linguistic relativity".

Simply put, the hypothesis says that how a person thinks depends on the language they use to think about it. Modern writers usually distinguish between a "strong hypothesis", that your language forces you to think one way rather than another, and a "weak hypothesis" that your language encourages you to think one way rather than another. Nowadays the strong hypothesis isn't really taken seriously by mainstream linguists, but most linguists believe some version of a weak Sapir-Whorf hypothesis. Lots of conlangs explore some version or other of the hypothesis.

The idea is most closely associated with Benjamin Lee Whorf, 1897–1941, who studied native North American languages of the Uto-Aztecan family — which are dramatically differently structured from European languages — and suggested that speaking such profoundly different languages would give a person a different way of looking at the world. Einstein's theory of relativity was a recent development at the time, and Whorf likened this linguistic notion to Einstein's theory because physical relativity says that how you perceive the world depends on your physical reference frame, while linguistic relativity says that how you perceive the world depends on your language. Edward Sapir, 1884–1939, was an important figure in the early history of modern linguistics, and Whorf's mentor. Sapir too expressed ideas of this sort. It's pretty common, though, for an idea to get named after somebody without their having ever actually said it; Sapir and Whorf both said things like this at various times, but they weren't the first to do so, never coauthored a paper about it, didn't present it as a hypothesis, and dabbled in stronger and weaker forms without explicitly making the modern strong/weak distinction.

Many loglangs are at least partly explorations of the Sapir-Whorf hypothesis; but also some philosophical languages are as well, such as, a well-known conlang attempting to support women's thinking, which was used in a series of feminist science fiction novels.

Is there a natural language with <feature>?
Some conlangers enjoy inventing weird features for their conlangs, but then discover some time later that there is actually a natural human language that has that feature. A classic case is the "Monster Raving Loony" alignment (we'll discuss alignment in the Advanced level), which was devised by members of the Conlang Mailing List who named it Monster Raving Loony because it would create inherent ambiguity in the language — making it impossible to tell which of the two arguments to a transitive verb is the subject of the sentence — and therefore seemed absurd. Only then someone noticed a language in Iran that actually has that sort of alignment.

This phenomenon is so common that conlangers have a name for it. It's called anadewism — which is an acronym for another natlang already dunnit, except worse.

So, when you're having fun with some really weird feature in your conlang, don't let it interfere with your enjoyment when you discover there's a natlang that does something like it!

Is there a conlanging community?
Short answer: There is now. A central place to look, from which to work outward to all the other parts of the modern conlanging community, is the.

Before the Internet, conlanging was mostly done privately by individuals who had no way of knowing if anyone else shared their peculiar pursuit. In a (now classic) lecture about artlanging in 1931, called , J.R.R. Tolkien described an experience as a soldier in World War I:
 * We were listening to somebody lecturing on map-reading, or camp-hygeine, or the art of sticking a fellow through without (in defiance of Kipling) bothering who God sent the bill to; rather we were trying to avoid listening, though the Guards' English, and voice, is penetrating. The man next to me said suddenly in a dreamy voice: 'Yes, I think I shall express the accusative case by a prefix!'

J.R.R. Tolkien helped make artlanging somewhat respectable: as an academic and scholar of ancient languages, he not only came out publicly as a committed designer of artistic fictional languages, but used those languages to create a hugely successful series of novels. When the internet came along, people who had never before been able to find others with the same eccentric interests began to discover each other and form on-line communities, and one of these groups was conlangers. The conlanging community formed especially around the, created in 1991, which was the origin of the term "conlang". The first was held in 2006, and the, which amongst other things now runs the conference, was formed the next year.

Are there awards for conlanging?
There is one, that the conlanging community generally respects. Since 2006, conlanger David J. Peterson has given an award he calls the to one conlang each year that he found especially worthy of note. The award is, he cheerfully admits, not sanctioned by any larger body, it's just his own arbitrary choice; however, the Smiley Awards are respected in the conlanging community because Peterson, and his opinions, are respected in the conlanging community.

The languages Peterson has selected are generally already fairly well-known and respected in the community. For each he writes an essay, explaining interesting features of the language and ending each essay with a section on "How [this language] Has Made Me Smile". The essays are of interest in themselves, for the insights they offer into the art and craft of conlanging.

Is there professional conlanging?
Until about 2009, it might have been tempting to answer "no", despite a few scattered cases. But, that was the year the movie Avatar was released, and the year HBO hired a conlanger to create languages for their planned TV series Game of Thrones. Since then the answer has to be, at least somewhat, "yes".

Before then, there were a few isolated cases of TV or movie conlangs. The earliest we know of was, back in the 1970s; children's TV producers Sid and Marty Krofft hired a professional linguist, Victoria Fromkin, to create a language for a race of primitive humanoids for TV show Land of the Lost. The first widely known conlang on-screen was, created for the 1984 movie Star Trek III: The Search of Spock by linguist Mark Okrand at the behest of the movie's director Leonard Nimoy, based on some sample phrases devised for Star Trek: The Motion Picture by James Doohan. It was still largely perceived by the general public as an aberration within Star Trek fandom.

In 2009, though, James Cameron's Avatar became one of the highest-grossing movies ever, prominently featuring conlang for which Cameron had hired a professional linguist (though not a conlanger), Paul Frommer. Then, in 2011, HBO's TV series Game of Thrones began, featuring and  conlangs. HBO had gone through the (LLC) in 2009 to advertise for a conlanger to create languages for the new series (under a tight non-disclosure agreement, of course), and LCC co-founder David J. Peterson won the contract. Peterson has since received other TV/movie conlanging contracts.

Peterson remarked in his 2015 print book  that movies and TV are a small market for conlanging skills, and suggested book authors might enrich their material by teaming up with conlangers to create linguistic backdrops for their story worlds.

What is the earliest conlang?
The earliest example we know of a constructed language, as such, is, described in the 1100s C.E. by , a German Benedictine abbess. Lingua Ignota has been studied by professor on English of the University of Rochester, whose book on the subject, Hildegard of Bingen's Unknown Language: An Edition, Translation, and Discussion, came out in 2007. (Professor Higley is the creator, under pseudonym Sally Caves, of the highly regarded artlang .) Lingua Ignota is apparently a partial relex of Latin, using Latin's grammar and drawing on its vocabulary while introducing more than a thousand new words, and written in a constructed alphabet of 23 characters.

Hildegard of Bingen has long been considered a saint in various branches of Catholicism. After a long and rather muddled procedural relationship with Rome, she was made a Doctor of the Church in 2012 by Pope Benedict XVI, resolving her status as a Saint of the Church as a whole, and making her only the fourth woman recognized as a Doctor of the Church — basically, a saint for her contribution to Catholic thought. Saint Hildegard's feast day, September 17, has gained some traction in the internet conlanging community as a conlanging holiday, when conlangers wish each other a happy Saint Hildegard's day.

title: Conlang/FAQ


text:
Conlang/Beginner/Sounds

Spoken language is much older than written language. Many beginning conlangers try to build their first languages out of written words without paying too much attention to what they will sound like, but this approach, while usable, is really the wrong way 'round. Before any written language existed, all the rules that govern how languages work — the rules of grammar — were already in place; what they determined was how language was built from patterns of sound.

What sounds will you have?
The first step is to decide on what sounds to use in your language. No languages use precisely the same set of sounds; for example, the sound "th" in English does not occur in most other languages (although it does in some, such as Swahili, Greek, and European Spanish); conversely, many languages contain sounds that English does not use at all.

You probably already know that sounds are classed as consonants and vowels. In deciding on what sounds to use in your language, it often helps to consider these two categories separately. A chart of consonant and vowel sounds is available in an appendix. For now, don't worry about the symbols used; just enjoy hearing some of the exotic sounds you might want to add to your language! But don't get too exotic; make sure that you can pronounce all the sounds you're going to use, and that you can tell them apart easily. (There will be plenty of time for building conlangs that you can't pronounce yourself after you've built ones you can — like a juggler practicing with eyes open before trying it blindfolded!) Another guideline is: don't add more sounds than you will actually need. If you want to use lots of non-English sounds, maybe think about deleting some sounds that English does use as well.

But regardless of what sounds you ultimately decide to use or not use, remember that it is important not to throw in every sound you come across; limit yourself to a system of sounds, rather than every sound that exists. If you find yourself with 50 sounds without a good reason why, you have probably gone overboard. The sounds should also be similar to one another in some way; avoid having "freak" sounds that have no relatives. For example, if you have an aspirated stop (a hard consonant like "t", with a puff of air after it), try to have more than one (but not every aspirated stop).

Choose a convenient way to spell out the sounds you've chosen, so that you can easily write about them, and be sure to write down a clear explanation of just what your spelling rules are. It's a good idea to imitate standard descriptions of your sounds, rather than devising your own; that's the best way to be sure it's clear — even to you, some time later — just what sounds you intended. In the Intermediate level of this wikibook, we'll cover the computer-friendly notation CXS (short for Conlang X-SAMPA), and its big brother IPA (the International Phonetic Alphabet), which are ways to spell out sounds without depending on the spelling rules of any particular language.

What sounds can go where?
When you have your sounds, you will have to work on ways of putting them together. Languages differ greatly in this respect: for example, English usually requires every syllable to contain a vowel; even words with no vowel written, such as the mathematical term "nth", are pronounced with one — "enth". Not all languages follow this rule; some, on the other hand, require every syllable to end with a vowel. If you are going to allow consonants to come after vowels at the end of syllables, you might only allow one consonant, or you might allow a cluster (as English does). Some sounds might be prohibited from certain positions; for instance, the "ng" sound in English can never begin a word, but in Tagalog it can. English allows many clusters of consonants, but prohibits many others: a word may begin str, but not zdr. You can make your own decisions on what clusters to allow; Russian and Polish, for example, have no problem with clusters like zdr.

What sounds do I want?
The types of sound used in a language (especially a themed language, such as Elvish) depends on the theme itself. For example, an Elvish language would be very liquid-heavy with many approximants while Orcish would have fewer gliding sounds and more gruff chokes. Keep in mind that there are two kinds of sounds: voiced and unvoiced. Feel free to pick and choose, but remember that if your people can make a voiced sound, they can most likely make a voiceless one, and vice versa.

title: Conlang/Beginner/Sounds


text:
File:Example1 underdamped.png

Example of underdamped response for LCR circuit Created in GNUPLOT 6 Aug 04 Used in http://en.wikibooks.org/wiki/Electronics:RCL_time_domain_simple

title: File:Example1 underdamped.png


text:
Conlang/Advanced/Grammar/Forming words

Polysynthesis
A polysynthetic language is characterized usually by verbal inflections to the point that word order is largely free. Natlangs that are polysynthetic include Mohawk. It is common in North American Indian languages. There are few polysynthetic conlangs, like Bp@x’àãókxá, Noyatowa, Ilothwii and Terpish.

A polysynthetic language generally marks the verb for the number, person, and class (if there are noun classes) of the subject, and sometimes the direct object. The verb is generally marked through affixes that may be prefixes or suffixes. The language may be agglutinative or fusional. In addition, tense, aspect, and any other information about the verb are usually marked on the verb.

Here's a hypothetical example:

In addition, it is frequent for polysynthetic languages to incorporate nouns. This means that the noun forms a compound with the verb. To illustrate again:

A great deal of explanation can be found here: http://zbb.spinnwebe.com/viewtopic.php?f=10&t=1253

Jeff Burke has written this description of polysynthetic languages:

Polysynthesis is a grammatical phenomenon most famously present in many North American Indian languages; the Algonquian and Iroquoian tongues are the most well-known. These languages, instead of using case endings on nouns and conjugational endings on verbs, mark both subject and object inside the verb; further, subject and object inflections are considered the actual arguments of the verb, while any free-standing nouns associated with a verb are like dislocated topic phrases. Here is an example from Mohawk, an Iroquoian language spoken in upstate New York and southern Ontario:

Teiotahià:kton wá:keke’

Nominalized and rendered in normal English, this is 'I-ate a-banana'; but a more literal translation would be 'A-banana, I-ate-it'. The pronominals 'I' and 'it' (the arguments of the verb root -k- 'eat') are expressed via the prefix ke-, which indicates a singular first-person subject and a singular third-person object. ke- is, then, akin to noun case and verb conjugation fused into a single marker and attached to the verb. Mohawk has some fifty-odd of these pronominal prefixes that express subject-object combinations; and a prefix is mandatory on every verb. By contrast, the noun teiotahià:kton 'banana' stands in relation to the verb wá:keke’ only indirectly, as a topical phrase stands in relation to a central clause in English.

Cheyenne, an Algonquian language spoken in southern Montana and Oklahoma, also marks subject and object on the verb, but does so differently; instead of a fusional marker, it uses a prefix for subject and a suffix for object. Witness:

Hetane návóómo

Literally translated, this means 'A-man, I-saw-him'. Hetane is the noun 'man' standing in relation to the verb návóómo 'I-saw-him' like a topical phrase. Ná- is the prefix for a singular first-person subject; -o is the marker for a singular third-person object.

In addition to marking both subject and object inside the verb, polysynthetic languages often make use of noun incorporation. This is a phenomenon where a noun becomes, in essence, an inflection on a verb. Incorporated nouns can be, depending on the language and circumstances, direct objects, indirect objects, subjects, locatives, and of other kinds. Mohawk makes heavy use of incorporation, as in:

Watia’tawi’tsherí:io

This translates as 'It-is-a-good-shirt', where the noun root atia’tawi (a word that can be used to refer to basically any upper-body garment) is present inside the verb. Cheyenne also uses noun incorporation on a regular basis:

Nátahpe’emaheona

This verb, meaning 'I-have-a-big-house', contains the noun morpheme maheo 'house'.

Noun incorporation can look bewildering, but is best understood in terms of English compounding. Babysit is an example of a word with an incorporated direct object; and words like deer-hunter and manslaughter make use of the same kind of incorporation.''

The headmarking inflections can be better understood by thinking of Romance languages like Spanish, which inflects for details about the subject. Polysynthetic languages take this concept further and inflect the verb for details about the object as well.

title: Conlang/Advanced/Grammar/Forming words


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:
Talk:Conworld

Conworld
Hmm. It looks like a good start so far. Nice job! :P

Some comment/questions though:

Looking at the categories on the main page, I think we should fuse a few together. Conscripting should be merged with Conlanging (as I can already see you have a "writing systems" section in the conlanging one).

Also, what's the difference between "Concultures" and "Consocieties"?

And as for the "Conmusic", "Conart", and "Consports", well, couldn't those be merged into Conculture? Or at least merge Conmusic and Conart.

Also, what will you put in "The Way of Con-" and "Exemplary Conworlds"?

So far so good, though :D

-- Maknas

 * Ran, you really should leave Conart seperate, just so you can use it as a heading. Even it breaks the flow and structure. It's just that good.

 * -- Space Dracula

the above was moved from http://spinnoff.com/zbb/viewtopic.php?p=120771

 * Yeah, Conscripting and Conmusic should probably be merged into Conlanging and Conart.

 * As for Consocieties, I was envisioning a sort of "Conpolitics/Coneconomics/Consociety" kind of thing. You know, like how the government is run, social classes, etc etc. Maybe there's a better way of putting that?

 * Exemplary Conworlds would be a list of well-made conworlds! Almea, for example, would be on the list. And as for the "Way of Con-", I thought of it as a sort of philosophy section. You know, some people make conworlds for fun, some make it to express their views, some make conworlds that are scientifically accurate, some people are freer with magical systems and such. The "Way of Con-" was meant to summarize all of it, as an overview of worldbuilding styles and such. -- Ran 14:40, 7 Aug 2004 (UTC)

 * I've gone ahead and merged the Conmusic and Conscripting sections. -- Maknas 16:08, 7 Aug 2004 (UTC)

Use of Con-
I don't think that each of catogories should begin with Con- as this could scare of newcomers. We should explain the popular usage of the prefix in The way of Con- but limit it's use within the actual articles. --Ingolemo 15:01, 7 Aug 2004 (UTC)

 * Duly noted... I've added a paragraph of explanation on the Conworld page. How does it look now? -- Ran 15:24, 7 Aug 2004 (UTC)

 * The paragraph is good but, what I meant was that we should avoid the use of colloquial terms from the ZBB (such as con-whatever or natlang) which would not be understood by anyone who is not from the conworld community. Although we could refer them to the Glossary when such word appear, I don't think the wikibook should require the learning of colloquial terms when constructed whatever and natural language would suffice. --Ingolemo 16:26, 7 Aug 2004 (UTC)

New ToC's
I've went ahead and made some starting Tables of Contents for some of the other sections off the main page. Ran, if you would, you should probably work out the base for the 'Way of Con' and 'Exemplery Conworlds', since I still don't exactly understand what you mean... And is there a way to see all of the new discussions in the ConWorld WikiBook? It's a pain to have to look through each page's Talk Pages. -- Maknas 16:48, 7 Aug 2004 (UTC)

 * The Related Changes might do that. - Circeus

 * You could always add each page to your watchlist and then check that every so often. --Ingolemo 17:01, 7 Aug 2004 (UTC)

 * Ooh, that works. Thanks! -- Maknas 17:17, 7 Aug 2004 (UTC)

conmusic
I am willing to write an article on conmusic to publish as a chapter of conarts Markus Miekk-oja 18:12, 7 Aug 2004 (UTC)

 * Go ahead. Do you want someone to make a ToC for the "Conart" section first? -- Maknas 18:14, 7 Aug 2004 (UTC)

That'd be preferrable, yes. Markus Miekk-oja 19:03, 7 Aug 2004 (UTC)

 * Done. I don't know much about the field, so it's still pretty simple. Just click on the "Music" link in it to start editing. -- Maknas 19:11, 7 Aug 2004 (UTC)

Editing
Just a little suggestion. Please, when you make an edit to a page (excluding Talk pages), please describe the edit you made in the "Summary" box next to the "Save Page" button. This makes it a lot easier to track changes. -- Maknas 20:50, 12 Aug 2004 (UTC)

"Conscripting" considered infelicitous
The trouble is that English already has a word "conscript"; as a noun it means a person pressed into service (often against their will), and as a verb it means to press a person into service.

I'd just edit the page except that I don't have a ready substitute. Conorthography? Conwriting? I dunno.

 * We could say Con-script as the introductory title, and then use conscript everywhere else? I'm fairly sure there won't be much problems--Circeus 22:18, 31 Aug 2004 (UTC)

 * I don't see any problem. English already has many such homophones that are easially determined by context (not vs. knot or poor vs. pour). I doubt the average English speaker would be able to confuse con-script and conscript to such an extent (especially as the naming priciples are explained on the front page) -- Ingolemo 12:58, 11 Sep 2004 (UTC)

Conhistory, Fiction and the Lexicon RPG
I am not sure I see a great distinction between 'conhistory' and 'writing fiction set in your conworld'. Perhaps the latter topic would be better incorporated into the former. Seems to me the Lexicon RPG (Google it if it means nothing to you) would be an interesting topic to cover as it provides a tool for creating conhistory in a usable form and is a game activity in its own right.

 * I'm afraid I don't quite see your point. For me, conhistory and writing fiction are distinct subjects. The major difference between the two is the time; Conhistory takes place during the past and Fiction is set in the present.

 * I googled for "the Lexicon RPG" but I'm afraid I don't quite understand what this has to do with conhistory - Ingolemo 14:37, 8 Dec 2004 (UTC)

Anybody there?
Hey there, I just found this wikibook and it's awesome, but I noticed that there hasn't been any discussion here since '04. Are people still writing? --Ajallan 17:12, 31 October 2007 (UTC)

My thoughts exactly. 195.189.142.115 (talk) 15:23, 26 January 2008 (UTC)

Where is everyone? Everything you've made so far is perfect. Does anyone still work on this? -- 78.0.230.128 (talk) 18:25, 4 April 2008 (UTC)

Interwiki Link to wikia:Conworld and wikia:Conlang
Hello there,

perhaps it would be great to interlink Wikipedia articles and Wikia sites like these with this project: Are there Templates for beautified interwiki Links for the above (WP and Wikia) on en.wikibooks? -- 80.136.66.147 (talk) 09:16, 25 April 2008 (UTC)
 * Conworld
 * Conlang
 * Conworld
 * Conlang

What about even more ambitious conworlding projects?
So far this set of wikibooks are pretty good in covering more common con-world projects (e.g., creating a language, a culture, maps, or even planets), but what about even more complex or ambitious projects?

For example, I know of a project involving a universe where there aren't stars and galaxies and planets, but spherical worlds formed by the emanation of something called 'ley'.

One of my past personal projects also involved the creation of an entire universe complete with its own version of the Big Bang, its own physics and elementary particles (if it can be called that; those "elements" are completely unlike particles in the real world), resulting in a complex structure only a small part of which is inhabited. It was much fun to start with completely different premises than the real universe and discover the consequences of your choices as you go. (The resulting world was also extremely foreign, completely unlike "our" universe in almost every respect.)

And what about fantasy worlds where there aren't planets and galaxies as such, but planes (astral planes?) and other large-scale structures? It would be nice to discuss these different approaches to con-universe structure. —The preceding unsigned comment was added by 208.181.115.4 (talk • contribs) 00:32, 8 July 2008.

Objectives of this series
I've rewritten the paragraph of the main page about what this series of books is for. It seemed too easy to infer, from the old paragraph, that each of these books is just a short summary of a subject for people too lazy to read an actual book on that subject — which would be a slap in the face to both the books and the readers. Poor form, to suggest either that the readers are lazy, or that if they aren't lazy they shouldn't bother with these books. Poor policy, to tell prospective authors of these books that they should aim low. I realize I'm setting the bar for these books almost impossibly high, but some of these proposed books should be able to reach that high — and in the long run, IMO, the ones that can't probably shouldn't be kept. Although it might not actually be practical to ask that the entire series eventually become Featured Books, it still seems that a book with no hope of ever achieving that status is underjustified.

The question I set out to answer was, what would make it worthwhile to read these books as something other than scaled-down versions of good introductory books on their subjects? Otherwise, the thing to do would be to make sure wikibooks has good introductory books on all these subjects. Before tackling the paragraph here I honed my thoughts on the subproblem of objectives for the Conlang wikibook, which is after all a particularly separable part of the series. (Conlanging is often logically, as well as historically, prior to conworlding: building languages doesn't require any peripheral constructions, while at the same time it tends to motivate and inspire them, as with Tolkien who created languages and then found that to make the languages sufficiently rich he had to build an entire cosmos to go around them.)  But a good introductory book on linguistics isn't going to be a good introduction to conlanging (unless, perhaps, deliberately designed from that perspective), and in fact the Conlang wikibook has had to struggle continuously against the linguistics-book impulse. Pi zero (talk) 18:38, 16 November 2008 (UTC)

Merge
Philosophy and religion should be merged into belief systems.

title: Talk:Conworld


text:
Introduction to Psychology/Child and Adolescent Psychology/Childhood and Sociology

Sociology as a science of the social phenomena is interested in "Infancy" as an object of study under multiple aspects; we will quote only some examples:
 * The change of the view on infancy described by the historians and conceptualized by the sociologists in terms status and role, the statute being allotted by l exterior (the company) him lai$ant more or less of freedom to assume the role qu'il is supposed to play there. Industrialization, the migration of the campaigns towards the city, the work of the children having burst the old family structures, sociology studied in detail the social relations with l interior of this new reduced family structure and to which places it assigns the children. Well other changes of the company, the m?urs, the family was described and analyzed by the sociologists from the point of view of their impact on infancy: Emancipation of the women (the replacement of paternal authority with parental authority), multiplication of the cases of divorce and l'attribution of the custody charge of the children and in a concomitant way multiplication of the recomposed families prolongation of the schooling; the unemployment of the young people and their prolonged stay in the residence of the parents.

Another phenomenon was analyzed very finely by sociology: c'est the increasing sum of pocket money at the disposal of the child which was planned in term to be able d'achat d'un specific group of the company which became the privileged target d'une publicity specifically conceived with its intention.

Sociology also highlighted that in the various social layers which make a company, the status and roles of the members d'une family are not in the same way defined. Aujourd'hui one can also - grace, inter alia, with sociology - evaluate health or pathology d'un family group by holding account of its behavior vis-a-vis with waitings qu'a the company towards him. This last point forms part of the theorization d'une particular psychological therapy qu'est the family therapy that, for lack of place, we will not n'aborderons here.

A last point - in particular compared to sociology - must be underlined: two close sciences (here psychology and sociology) can have the same subject of study (Infancy) but arrive at apparently contradictory results if one is unaware of that the point of view on an object of study is never same the science with the other and that methodologies diverge.

Thus, sociology studied the evolutions of the role and statute of the father and the mother with l interior of the family following l emancipation of the women, and how the infant was implied in these changes. In parallel, the psychologists highlighted that simultaneously with this evolution in the imagination of the infants the mother always represents love, protection and permissiveness whereas the father continues to represent the law and repression.

This point must point out qu'il to us is necessary always much prudence when one wants to generalize a phenomenon observed and more still when one seeks to transpose it from one science to another.


text:
Talk:Swing Dancing

This is a great idea for a textbook! It's possible to insert animated gifs into wikibooks pages; that might be useful for a few demonstrations.

 * Thanks! It'd be cool if somebody was able to construct something similar to the animated gifs present at jiveoholics anonymous. Unfortunately, I really don't have the graphics know-how to do something like this. Alternatively, somebody could take photographs of people performing the moves. --NeuronExMachina 07:40, 14 Aug 2004 (UTC)

6 count basic section
I have a few comments on the 6 count basic section.

The basic step I was taught has the back step coming first. Using the numbers for the steps listed here, the lead starts with #5 then 6 then 1 on through the rest of the steps. And, for the follow it is a mirror image of the lead, going back with the right foot instead of the left.

Plus, I was tempted to just delete the word "crap." Instead I'll just say I don't think personal opinions about the triple step was a proper thing to add. Actually for a beginner, I wouldn't have mention that any step taking up those 4 counts could be substituted for the side/side moves. They usually have enough trouble remembering to keep frame while keeping count to the basic step.

go nuts.
This is a wiki, so anything that you see that you feel like you can improve, you should change. --Waxmop 00:37, 4 Sep 2004 (UTC)

Is this a how-to?
I think that this would make a fine addition to the how to section. Just because it isn't written like crap and doesn't baby the reader, doesn't mean it wouldn't be good there.

Naming and types of dance to include
220.253.16.253 As with the swing dance wikipedia article, it might make sense to distinguish between the swing dances under discussion in this book - eg lindy hop, west coast swing, etc etc etc - and to make some sort of comment about the types of steps which are most frequently associated with each style _historically_ and in the current swing dancing world.

Overall Structure
220.253.16.253 It might be useful to reference the history of 'swing dancing' at the beginning of the article, and then to divide each section into specific styles (with some sort of disclaimer at the beginning making it clear that it's perfectly ok to borrow from each style in the social context), with a comment about each style. Not to reproduce the individual wikipedia articles, but to perhaps make it clear that 'swing dancing' is a wide genre, made up of many styles (with different histories).

Cultural Specificity
220.253.16.253 It's important to note that 'swing dances' and 'swing dancing' culture are different in each city and local scene. For eg, there is almost no west coast swing dancing in Australia, yet ceroc and rock and roll are very popular and quite similar in dance style, yet differnt in culture. The discussion of etiquette in this wikibook is a good example.

Reorganization
I'm going to suggest some basic reorganization here. Per other Wikibooks that I've seen and liked, I think it makes the most sense to have the Swing Dancing page as a Table of Contents for the Manual. Then the subpages (e.g. East Coast Basic, Charleston Basic, Lindy Hop Basic, Intermediate Moves, etc.) link off of that. If no one has any objections I'll be bold in the next few days.--Will.i.am 23:01, 16 October 2006 (UTC)
 * OK, I did it. I did some major revamping of the structure here to make it all un-orphaned and easier to follow.  Now all it needs is some TLC.--Will.i.am 23:14, 18 October 2006 (UTC)

Application for visualisation
Just a heads up if you want to add some pictures of the steps to this book. There is a nice free Java application, that can be used for illustrating dancing steps that already has the basic moves for all dances built in. Have a look here: http://www.sebastianbauer.info/index.php?page=simpledance If you create new moves, don't forget to write a mail to the author, so he can make them available to everyone. --84.178.123.44 (talk) 16:19, 27 April 2009 (UTC)

title: Talk:Swing Dancing