text:
GET

GET is a reference text for undocumented GET arguments available on queryable WWW pages.

Background: Web/Html forms are a process which allows users/viewers to Enter information on a web page which will then be sent to the web server for processing. The most common method for processing is called CGI ( Common Gateway Interface ) and this stipulates how the data will be passed to an external ( from the web server) program and how that program will generate web page to be displayed back to the user. The HTML form can specify one of two methods for data to be sent from the webserver, the first is GET which specifies that all information is included in the requested URL. The second is POST which specifies that additional information will be sent after the URL request. While there are advantages of both the biggest advantage of GET is that since everything is in the URL the input (and resulting display) can be bookmarked or saved in a link so that the data doesn't need to be re-entered each time. The biggest advantage of POST is that there isn't a limit on the size of the data which can be passed, so may claim that it also allows data to be passed secretly but that is a fallacy. What is not necessarily widely known is that since most writers of CGI scripts use libraries to decode the form data and most library writers check for a decode both GET and POST automatically and treat both types the same, you can turn most POST forms into GET requests/links which allow for documented exploration. HTML forms and GET (and POST) encoding is well documented on the web, and the source code can be easily viewed in most browsers with view source options.

GET arguments are the simplest means of querying a dynamic web page for specific information. They consist of a simple modification to the base URL, beginning with a "?" sign after the filename. Not all websites provide GET argument interfaces as part of their information portal, but many do.

For example, the Google web interface can be queried directly by URL. If you wish to search Google for "Wikipedia", you can simply type the following directly into your address bar: http://www.google.com/search?q=Wikipedia

Everything after the "?" is the GET argument, which tells the Google server what you are interested in. If you are unfamiliar with this, try experimenting by changing the text after the "q=" in the above URL.

Knowing GET arguments can be useful for everyday browsing, but are also a lot of fun for hackers (mostly the harmless type) to play with in writing computer scripts. Most web pages that allow GET queries do not, however, provide any documentation of the available parameters. In the Google URL above, it is easy to determine that the "q=" string indicates your "query" and whatever follows it is what Google looks up. The arguments are not always easy to decipher, however.

The idea of the GET Wikibook is to allow hacker types who have bothered to decipher cryptic GET strings to share their discoveries.
 * GET/Site list
 * GET/IP list

title: GET


text:
Talk:Polish/Neuter noun declension

Untitled
I'm Polish so I've fixed small mistake - locativ of 'piwo' (beer) is 'piwie', not 'piwu'. Simmilar 'słowo' - locativ 'słowie' (word), 'paliwo' - locativ 'paliwie' (gasoline).

More examples needed for -e
What about morze? -69.228.203.52 07:26, 6 June 2007 (UTC)

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

title: Talk:Polish/Neuter noun declension


text:
Conlang/Beginner/Words

Okay, you've decided on some sounds that you want to use in your language, on a way to write the sounds, and on what sounds can go where; now it's time to start word-building.

Morphology
Word building isn't as simple as picking a word from the dictionary and making up a pattern of sounds (don't worry, it's not as boring either). If you look in an English dictionary you will find many words that can be broken up into smaller words. For example, the word everybody can be split into the two words every and body. Even more often, you will find words that can be broken up into pieces that aren't actually full words. Indescribable can be broken down into in-, describe, and -able. You will notice that in- and -able, while not full words, still mean something (even if what they mean isn't exactly clear); the same word-parts appear in inadequate and readable and many other words.

These 'half words' are called affixes, and they build new words from simpler words or based on stems which do not stand alone (like in Latin, stems are a part of words, like "cor-"). (There are also affixes that change properties of a word without changing what word it is, like English -s for plural. The inflection, like plural "s", can be applied using affixes, but we'll deal with those in the next section.) You'll almost certainly want some word-building affixes for your conlang. They give your vocabulary texture, and the more of them you have, the more words you can add to your vocabulary just by inventing one new simple word.

There are lots of different kinds of affixes, depending on how they change a word when they attach to it. Some simple techniques you can use: An affix may take different forms on different words, like -able that on some words becomes -ible. Sometimes the forms used on different words are so different that you might think of them as different affixes, that just happen to mean the same thing and apply to entirely different sets of words — like the plural affix in goose → geese, where for most English words the plural affix has the form -s or -es.
 * add onto the front of a word (like in-).
 * add onto the end of a word (like -able).
 * insert into the middle of a word (like hip-hop -iz- in house → hizouse).
 * change part of a word (like goose → geese; of course that affix doesn't build a new word, but it shows another way an affix can work).

If you set up your word-building affixes to work the same way as in English, even if they use different sounds and attach differently, they'll still make your conlang feel similar to English. For example, if you have an affix equivalent to English un-, don't use it exactly the way English does. Experiment with it — you might have no word for "bad", but have "ungood" instead; maybe have a word for "uncommon" that doesn't use the "un-", in the same way "bad" isn't "ungood".

Vocabulary
The English word manual comes from the Latin word manus, which means "hand". Right? Well, sort of. Latin is a language with relatively few different words, so each word has to do a lot of work. The Latin word manus does mean "hand", the part of the human anatomy; but it also means "fist"; "handwriting"; "finishing touch"; "workmanship"; "team"; "gang"; "band of soldiers"; and "trunk", the part of the anatomy of an elephant. The English language has a tremendous number of different words, so the average word doesn't have to do nearly as much — but especially basic and common words may still have a fairly wide range of meanings, and the English word hand is like that; it can mean everything from a person's handwriting (like in Latin), or the pointy bits on a clock face, to the set of cards that a player holds in a card game. (Compare: Latin manus, English hand.)

No word in one natlang means exactly the same thing as any word in another natlang. To keep your conlang from feeling like English, don't give it words for just the same concepts as in English. Try to invent words that have the meanings of more than one English word, or are more specific than English words. Even better are words that fall between levels of description in English. For example, you might create a word that means "a four-legged hairy animal", to cover dog as well as horse, but not as much as mammal or animal. Think about a whole set of related or similar things (for instance, colors, animals, or family relationships) and how your language can divide that mass of reality into manageable parts in a different way than English. And think about additional, perhaps figurative, senses of a word (like all those extra meanings for manus or hand).

You can even create words for concepts that are only very clumsily expressed in English, such as: that awkward situation when something has happened, which is known to more than one present party, which neither wish to speak about, and suddenly they have nothing to say to each other. Another word could mean the same thing, but with another, unknowing party present, who senses a weird atmosphere between the other parties.

Part of the challenge of conlanging — whether you're building an artlang, engelang, or auxlang — is that you won't really know how your language is going to feel until you've got enough of it together to start saying interesting things in it. (That's also one reason why conlangers may tend to keep tinkering with their creations.) So how can you tell, early in building your vocabulary, whether it will come out too much like English? Well, as a rule of thumb, building a vocabulary of a hundred words or so should be a pretty massive job — done properly, it's a major milestone, like a small company landing its first big client — and each additional hundred words should be heavy work as well. If you easily reach, say, a thousand words, you're probably in real danger of producing a conlang that will always feel too much like your native language, no matter what sounds and grammar you give it.

title: Conlang/Beginner/Words


text:
Japanese/Vocabulary/Gairaigo

Gairaigo (外来語) are words of foreign origin.

title: Japanese/Vocabulary/Gairaigo


text:
Algorithms/Guidelines for Contributors

Introduction to the Series
This book is part of a series of three text books on data structures and algorithms:

 * Data Structures—A book suitable for a first course in data structures that presents the most common data abstractions and their construction and properties. A tutorial on the most key points.
 * Algorithms—A book suitable for a first course in algorithms that presents the most common algorithmic techniques and how to analyze algorithms. Assumes some knowledge of data structures. A tutorial on the most key points.
 * Advanced Data Structures and Algorithms—A book that covers more advanced material that assumes some prior knowledge of data structures and algorithms. While the first two books are tutorials, this book is more reference based. Thus, its content can be much more eclectic. Advanced (and interesting) material that doesn't fall into the tutorial nature of the first two books belongs in this book.

The reason these books are in a series is to help narrow their focus and to aid coordination of the efforts. An eventual goal is that books will be available for every computer science subject.

Guidelines

 * 1) If you want to fix a bug, simply click on "edit", make your changes, and click on save. We'll review the changes to be sure they are appropriate for the book. If you are unsure, you can visit the "discussion" page and ask there. In general, to make a small change, you don't need to ask first, and you can just use common sense to determine if your change is appropriate.
 * 2) If you would like to write a chapter, section, or part of a section, take a look at the items marked with "TODO" tags and start there.
 * 3) Be sure to read all other sections of the book first in order to avoid duplication of content.
 * 4) When writing a section, you can mark some parts as "[TODO: explanation]", where explanation describes what you intend to take place in that part. For example, if you aren't good at making images, you can make as a TODO item a description of the image that should go there. Perhaps someone who is effective at making images will notice this and provide one for you. The purpose of a TODO item is to give the plan of what should be written.
 * 5) This is a tutorial: We aren't aiming to create an encyclopedia of every algorithm ever created, nor are we trying to present the absolutely best versions of particular algorithms.
 * 6) Don't include links to wikipedia articles in the book's chapters: The idea is that each book is self-contained so a reader can print out the book and read it separately, instead of having to navigate through it online.
 * 7) The book uses a pseudocode language that should be familiar enough to those who know Algol-family languages (including C, Java, Pascal, and Python). It includes extra features that help abstract away nitty-gritty implementation details, and thus allows for the real algorithmic idea to be communicated, rather than focusing on the trivial implementation issues that are language dependent.
 * 8) Implementations in non pseudocode can be written for an appendix. These implementations can serve to be usable by readers and to make clear any possible ambiguities. Implementations should be tested well and include test cases. Implementation languages are Python, C, Java and Scheme.
 * 9) Put a star ("*") next to section or sub-section titles if the material presented there isn't essential to understanding the larger point of the chapter. (For example, a more junior reader might elect to skip or skim these sections.)
 * 10) Use primary sources when possible. If you do use a reference, put it on the references section. Never copy content without asking permission. Further, note that even some GFDL content uses a different license version (not all are forward compatible, either) and should not be copied without permission.
 * 11) Use the wikipedia as another source for material, but edit the material to present only the main points and ideas: the encyclopedic detail of the wikipedia can become a distraction when trying to learn just the basic concepts.
 * 12) Use the mathematical royal "we" for some phrases, but try to use the second-person "you" as much as possible: it makes sentences easier to construct that also sound more direct.
 * 13) Look for insights into understanding an algorithm or a part of the software engineering process in general.
 * 14) Avoid using the passive voice ("The article was written by us.").  Instead, try to use the active voice ("We wrote the article.").
 * 15) Don't use "this" as a pronoun, only use it as an adjective.

Development Phases

 * 1) A table of contents should be created and more or less agreed upon. Such a table will set the scope for the book. Changes, of course, can be made later. ( DONE: The TOC is more or less agreed upon by contributors)
 * 2) After the chapters are broken up, the sections and subsections should be designed, with TODO items describing the content to go in that place. ( DONE)
 * 3) The most important concepts should be written first, to provide an anchor and context for the other material to be built from. ( IN PROGRESS: Join us!)
 * 4) Implement C, Java, Python and Scheme versions of the algorithms and put them in the appendixes. ( Still TODO...)
 * 5) Similar to an open-source project, more and more "features" (i.e., chapters and sections) should be added. This stage will happen after the First Edition milestone is met. However, when making improvements for the second edition, core items shouldn't be neglected. ( Still TODO...)

Writing a book takes time and dedication, but if you've come this far, it's probably going to be worth it. Just as free software programs don't simply drop from the tree, whole open books won't write themselves.

title: Algorithms/Guidelines for Contributors


text:
Trigonometry/Introduction

Trigonometry is the study of the properties of triangles.

 * "Tri" is Ancient Greek word for three,
 * "gon" means angle,
 * "metry" measurement

Together they make "measuring three angles of a triangle".

If you know some facts about a triangle, such as the lengths of its sides, then using trigonometry you can find out other facts about it. If you know the lengths of sides then you can find what the angles are. If you know the length of one side and of two of the angles, then you can work out what the remaining angle is, and also what the lengths of the other two sides are.

As a consequence the Ancient Greeks were able to use trigonometry to calculate the distance from the Earth to the Moon.

Starting to Learn Trigonometry
One of the first things we learn in trigonometry is how to calculate what the third angle in a triangle is when given the other two angles. For example, in a triangle if two of the angles are $$60^{\circ}\,$$ then the third angle must be $$60^{\circ}\,$$ too, since we know that they all need to add up to $$180^{\circ}\,$$.

However, if we're instead told two lengths, say 7cm and 10cm, and if we're not told anything about the angles, then the third length has a range of possibilities, it could be anywhere between 0 and 17cm.

Solving in a Right Triangle
Remember, a right triangle has one angle that measures $$90^{\circ}\,$$(a "right angle"). It's much simpler to calculate the missing third angle on a right triangle, so we will start by examining one, expect to see many more of them in the rest of this book.

In a right triangle we can work out the length of the longest side if given the lengths of the two shorter sides. In a right triangle the lengths of the sides have a particularly nice relationship to each other. The formula for this relationship is written:

 * $$a^2 + b^2 = c^2\!\,$$

The sides $$a$$ and $$b$$ are the ones that touch the $$90^{\circ}\,$$angle and $$c$$ is the longer diagonal side that is across from it. You may sometimes see $$c$$ called the hypotenuse.

See Pythagoras' Theorem to start using this formula to calculate the length of that missing side.

Solving in Other Shapes
What if the triangle isn't a right-angled triangle, though?

More complex triangles can easily be divided into right triangles, so we learn about right-angled triangles enables us to work with other kinds of triangles too. Trigonometry and trigonometric functions can also be used with more complex shapes such as squares, hexagons, circles and ellipses. Ultimately the most important mathematical tools we have for measuring the universe are based on the study of the mathematics of triangles.

Trigonometry is a fundamental step in your mathematical education. From the seemingly simple shape, the right triangle, we gain tools and insight that help us in practical and theoretical endeavors. The subtle mathematical relationships between the right triangle, the circle, the sine wave, and the exponential curve can only be fully understood with a firm foundation in trigonometry.

Applications

Because many physical questions can be framed in terms of triangles, trigonometry has found wide use in the physical sciences and engineering.

Trigonometry is needed in surveying and architecture since relationships between lengths and angles in triangles are used directly.

Civil engineers, mechanical engineers, and physicists use trigonometry to understand how forces will be applied, and what direction different objects will move in when they push on or bump into each other. Since trigonometric functions map to circles, and circles map to waves (we'll get to how all this works!), electrical engineers use trigonometry to make calculations about wavy patterns that they work with, such as AC power that comes out of your wall, or radio signals to your cell phone.

Computer graphics in movies and video games are actually millions of small triangles rendered on your screen, although there are a lot of little tricks that happen after that to make things look smooth and curvy.

title: Trigonometry/Introduction


text:
Talk:Trigonometry/Introduction

Hey someone please link that last sentence to the wikipedia, i dont know how? bananaclaw 09:01, 25 Dec 2004 (UTC)
 * You just add a standard link to wikipedia's page on the subject. Programmermatt 20:38, 25 July 2005 (UTC)

According to the Wikipedia article on Sexagesimal, it was the ancient Sumerians who first invented it, not the Greeks. Is this correct? Gotsomeideas (talk) 21:17, 9 June 2008 (UTC)

James.Spudemann made a HUGE edit where he changed the nature of the introduction. An introduction should, I think, promote eagerness in the reader to learn the subject, but I don't think the new introduction does that. I'll change the introduction with this in mind. 79.79.171.154 (talk) 10:19, 31 July 2010 (UTC)

I agree that was a hugely significant edit. It lost some important content and changed the book's tone. I feel that for someone wanting to learn trigonometry the original introduction, before James.Spademann's historical notes, was way better. This is in fact a general problem with how the book is shaping up. It's becoming less suitable for someone learning how to do trigonometry. I am adding back the lost material and making the historical background something readers are more likely to skip over on a first reading. JamesCrook (talk) 12:31, 12 October 2010 (UTC)

title: Talk:Trigonometry/Introduction


text:
User:Stephane.magnenat

I am a researcher in mobile robotics with a master in computer science. You can find more information about me on my homepage.

My contributions to Wikibooks
None up to now, but I'm interesting in improving Computer_Hardware.

title: User:Stephane.magnenat


text:
Conreligion

Religion is about our 'human spirit'. This may mean a simple shared philosophy, such as a 'team spirit' familiar to participants of successful sporting and military activities, or a highly complex set of religious beliefs, sacred laws and temporal regulations about how 'we' may conduct ourselves and how 'they' — the rest of the world — is (or should be) properly ordered.

History
Religion is a cultural manifestation that may have had a role in the survival of human groups and nations. Traditionally most religions were enforced, and people who failed to conform to religious rules (apostasy) or who expressed doubt (blasphemy) or interpreted things differently (heresy) were severely punished, often by death. Generally religion requires its adherents to support each other, and either enables or requires enemies (including the 'internal' dissidents just mentioned) to be suppressed or killed 'lawfully' within a general philosophy of 'divine justice' or some specific pronouncement of 'justified war'.

Religions develop depending on the way of life: Gathering and field work once were female activities and are highly dependent on the soil, leading to earth goddesses. On the other hand, hunting and pastoral work were reserved for men, causing their gods to be male. These gods are often associated with the weather or the sky.

Distortions
In much of the western world, where Christianity is dominant, a common mis-conception of religion is simply that it involves a God, or god-like figures such as emperors, royal households or priestly organizations. Since such people are supposedly 'appointed by God' they are generally assumed to be divinely authorized to rule, utterly incapable of error and so worthy of praise, love and devotion.

This westernized view is however, extremely incomplete. It excludes many human activities that generally fall under the heading of "religion" and distorts the spiritual beliefs of many people in other religions.

For example, Buddhism is a religion without a God. Though many forms of it have imagined the Buddha as a Christ-like figure, other Buddhists think of him as an historical figure — not to be worshipped, but respected as a man of insight who set an example for others to follow.

Afro-Cuban religions like Vodoun include loa, powerful beings who are not gods, and are not worshipped, but are dealt with as we deal with our fellow humans. Believers allow these beings to possess them, under certain specific and controlled circumstances, in order to converse with them and receive advice. Quasi-religious practices, such as Taoism, or certain tantric schools, are harder still to classify in any easy way.

So before we can arrive at a toolbox for building a constructed religion, we must arrive at a reasonable definition. I propose the following as a reasonable definition of a religion: A set of metaphysical beliefs that describe the sort of existence we live in, suggests a goal its adherents wish to attain, and prescribes a method whereby that goal may be obtained by the individual.

Forms of Religion
Religions take many forms and variations. Don't let difficult words (and -isms) scare you! Some of them are described below, but the most common forms are atheism (believing that there is no god), agnosticism (unsure if god exists or not), monotheism (one God), polytheism (many gods) as well as monolatrism, polylatrism, henotheism, kathenotheism, deism, idealism, and animism.

Atheism and Humanism
Atheism is non belief in Gods and Goddesses. ( Theism is belief in one or more of these. "A" is from Greek, meaning "not","without"; hence "Atheism" is "Without Theism".)

Atheists hold that ideas of Deities are merely human constructs.

Humanists omit belief in the Supernatural and concentrate on human life in this world. Some humanist groups have trained officiants to lead weddings, funerals, namings or other life-passage ceremonies if individuals need them.

All ethics are seen as derived from human understanding of actions and their consequences. Laws are not seen as given by Deities but arise out of society's consensus about how actions should be regulated.

Those who find Theism unbelievable of course share the common goals of all people who want to live in societies that promote happiness and security.

Agnosticism
View that God’s existence is unprovable: the belief that it is impossible to know whether or not God exists. Agnosticism is rarely the basis for a whole belief system but is commonly associated with atheism or skepticism.

Monotheism
Monotheism is the belief in one single god exclusively, and that no other gods exist. This is the form professed by most, if not all, denominations of Christianity, Islam, and Judaism, although Trinitarian sects of Christianity are sometimes construed — generally not by their own followers — to have a "pantheon" of three gods (the Trinity).

Polytheism
Polytheism is the counterpart of monotheism and holds that multiple gods (forming what is usually called a pantheon) exist. Most of the religions now regarded as "mythology" and most neopagan religions embrace some form of polytheism.

Monolatrism
(Note: Different definitions of Monolatrism appear. The definition given here is not the only one.) Monolatrists worship only one god, but believe other gods exist. They believe that the other gods leave non-worshippers alone. It has been suggested that early Judaism was a monolatrism based on alleged references to other gods in sacred texts.

Polylatrism
(Note: Polylatrism is not a word in real usage. It is used here for convenience and because the word just makes sense.) Polylatrism implies that a people worships a sub-set of gods exclusively but believes in the existence of other gods. They believe that other gods leave non-worshippers alone. Many neo-Pagans adhere to something akin to polylatrism, but the closest thing to a historical example we have might be the ancient Celts, which evidence suggests held a policy of "you worship your gods, we'll worship ours".

Kathenotheism
Kathenotheism is a hard concept for many to understand, but might be best described as worshipping a Divine Office instead of the god holding it. Kathenotheists might believe there is a series or cycle of supreme deities, and worship each one for only as long as they hold the power of supreme god.

Henotheism
Henotheists worship one single god while not denying the existence of others. The difference between henotheism and monolatrism is that henotheists seem to believe that the non-worshipped gods have power over those who don't believe in them.

Deism
(Note: Deism has had many forms over the years. This is just one.) Deists assert that a power created the world but abandoned it, or at least doesn't interfere with it. Some forms of Deism say that in creating the world, the creator became part of it; this is a kind of pantheism. This form of religion appeared heavily in the thinking of many Enlightenment era philosophers, though not as of yet in a major religion. Famous Deists include Thomas Jefferson and Benjamin Franklin.

Idealism
Idealists, in this sense, worship or strive toward a creed, philosophy, or perfect ideal and might be considered a secular religion. Examples include the North Korean philosophy of Juche and arguably many forms of Buddhism.

Animism
Animists believe that a soul or other supernatural power is in every single object. Mostly associated with pre-agricultural or hunter-gatherer cultures.

Manism
Manism is based on the belief that the deceased, often family members, mythological ancestors or saints, have a continued existence and/or possess the ability to influence the fortune of the living. Manism is most frequent in settled cultures.

Reincarnation
This is a belief that after death, one will be born again in some form. There are many belief systems around this idea. A Southeast Asian folk tradition holds that one is reborn into the same family, so that you might be your Great-Aunt Edith.

The most famous belief system pertaining to reincarnation is that of the Hindu Brahmins, which was exported to many lands and forms the basis of many New Age philosophies. In Brahminism, acceptance of one's station in life is necessary to improvements to one's status in future lives. Thus, a wealthy member of the nobility deserves his good fortune because of his actions in past lives, and the low-caste and untouchables similarly deserve their fate. The ultimate state, nirvana, is an extinguishing of all personality and desire.

Not all who believe in reincarnation share this philosophy. Gnostic Christians, Druids, and Native Americans among many others have their own ideas of what it is like.

Nothingness after Death
This is the belief that nothing happens after death, except the bodily functions and consciousness cease. Most people would agree that the lives of the more charismatic ancients are recorded in human fable, religious tradition or vernacular (written) historical records. It is thus common for humans to achieve a sort of vicarious immortality simply by leading a full life which is interesting so capable of being 'bought alive' in the minds of our survivors and their students.

Afterlife
This is the belief that some kind of world (an ideal heaven, limbo, underworld, or torment in hell) exists beyond the grave. It often provides at least two possibilities of happiness and torture based upon one's performance in life, or specific actions in one's life. This can be a powerful control myth for young impressionable warriors who may face death on the battlefield, and who must obey orders without question if their army is to be successful. It is also a useful mechanism for instilling 'ethical values' and promoting 'righteous behavior'.

The underworld, like the Ancient Greek Tartaros, might also be akin to nothingness; the dualism of Heaven and Hell is actually a quite recent invention. According to the Romans and Greeks, everyone —except for those who had directly committed a crime against the gods or those who had been really virtuous heroes— would go to the Asphodel Meadows, a vast land with nothing in it. It might be compared to Purgatory, although the Asphodel Meadows were permanent.

Spiritualists believe that the next life is a place where one goes on learning and having a variety of experiences just as we do during our lifetimes. Many ancient peoples including the Egyptians conceived of the afterlife as being like Earth but without life's problems.

Ritual
Although often overlooked, ritual holds an important place in human behavior. Ritual means repeating a sequence of activities in a routine (formulaic) way. Ritual may be something trivial, such as wearing 'lucky' clothes for certain important occasions such as job interviews, or extremely important aides to memory, such as the checks performed by a pilot before attempting to fly an airplane. Religious rituals generally are performed to make sure that all participants are 'of one mind' - that they have the same understanding of 'right' and wrong' behaviour.

Some rituals may seem bizarre, but hold an important 'survival' truth. The Pagan belief in sowing seed in the nude is an example. Without clothes, the farmer is sensitive to the air temperature, wind speed, soil condition, moisture content, presence of predators and so on. The 'comfortable' condition (in Southern Europe, where the practice emerged) just happens to be about ideal for seed germination, and so people who performed this naked sowing ritual also tended to have better harvests than those who did not!

Most religious rituals tend to be simply routine reminders of our ancestors successful seasonal habits. The feasts of special food (for example the Western Christmas or Saturnalia, which is a winter solstice feast that tends to prevent depression) or fasts or absence of something familiar (Notably in early spring, when food is scarce, and we need to lose fat gained during winter) are common manifestations of formerly successful seasonal survival strategies for our ancestors, who lacked central heating and refrigerators.

Most important however (both for a human survival and for our sheer enjoyment of human life) are public or religious celebrations of life's major events - birth, academic achievement, maturity, marriage, child rearing, sagacity and death. Most of these 'life changing' celebrations have become adapted, stylized and documented to reliably provide example, advice and guidance to attendees who aspire to achieving such goals.

title: Conreligion


text:
User talk:61.55.129.197

Don't spam. You will be banned if you continue. r3m0t (cont) (talk) 12:09, 25 Dec 2004 (UTC)

title: User talk:61.55.129.197


text:
Perl Programming/Conditionals

= Conditionals =

The if statement
The if statement is the primary conditional structure in Perl. The syntax is as follows:

If the boolean expression evaluates to true, the statements between the two braces will be executed. The braces around statements are mandatory, even if there is only one statement (unlike C or Java).

An alternative syntax to the if statement may be used on a single statement. This involves putting the conditional at the end of the statement rather than before, and does not include braces:

The following statements are synonymous:

You should choose whichever one is clearer in a given situation. For example, the following is legal, but unclear:

This hides the last (which is like break, and ends the loop) over at the right. Instead, use a postfix if:

The boolean expression conditional can contain any one of the comparison operators covered in the next section.

Multiple conditions can be checked together using the boolean expression operators:

 * && - logical and, C style; used for most conditionals
 * and - logical and, but with a lower precedence; used for flow control
 * <tt>||</tt> - logical or, C style; used for most conditionals
 * <tt>or</tt> - logical or, but with a lower precedence; used for flow control
 * <tt>!</tt>  - logical not, C style
 * <tt>not</tt> - logical not, but with a lower precedence

Conditional statements can also be extended with the <tt>elsif</tt> and <tt>else</tt> structures:

Note that an <tt>if</tt> statement is followed by any number (including zero) of <tt>elsif</tt> statements, and finally an optional <tt>else</tt> statement. The statements of an <tt>elsif</tt> will be executed, if its boolean expression is true, and no preceding <tt>(els)if</tt> statement's boolean expression is true. The trailing <tt>else</tt> (if present) is executed, if none of the preceding statements' boolean expressions are true.

Shorthand <tt>if ... else</tt> notation
If you want to shorten the conditional into one line, you may use the shortcut syntax:

This code uses the shorthand syntax within a line.

title: Perl Programming/Conditionals


text:
Perl Programming/Hash variables

A Perl hash is similar to an ordinary array, but instead of using integer indexes, a hash uses "keys" that can take on any scalar value. These are usually strings or numbers.

Syntax: instead of the  operator, associative arrays use the   symbol, and rather than square brackets , as in  , hash elements are referenced using curly brackets  , as in.

Hashes are one of the most powerful and commonly used features in Perl. A typical use would be to build a hash that contains a "dictionary", with each key being a word in the dictionary, and the corresponding values being the definitions of those words.

A hash containing the sounds various household pets make is below

'=>' and ',' are actually interchangeable, so the right side could look exactly like an array. This means that you can assign an array to a hash. In such an assignment, each element with an even index (starting from 0) in the array becomes a key in the hash. The following statements create the same hash as the previous one does But the first style is more preferred because it makes the statement more readable.

To access a hash element, use the curly brackets: will print the following to STDOUT

The cat goes meow.

To add a new sound item to a hash To overwrite an existing element, just reassign it To remove an item from a hash, use delete. Setting the value to undef does not delete the item; using exists on a key that has been set to undef will still return true.

"Associative Arrays"
Originally, a "hash" was called an "associative array", but this term is a bit outdated (people just got sick and tired of using seven syllables). Although it isn't intuitive for newcomers to programming, "hash" is now the preferred term. The name is derived from the computer science term, hashtable.

Printing hash contents
If you know PHP, you may have thought by now of some convenient way to print the contents of your array the way  does...

Counting the number of entries in a hash
To get the size of the hash, simply find the size of the result of the  function, by evaluating it in scalar context:

Hash of Hashes of Hashes
You can define multidimensional hash array variables. An example may look like this:

This code will produce:

1      a       A       FIRST 1      b       C       SECOND 1      c       B       THIRD $VAR1 = { '1' => {                    'c' => { 'B' => 'THIRD' },                    'a' => { 'A' => 'FIRST' },                    'b' => { 'C' => 'SECOND' }                  }          };

title: Perl Programming/Hash variables


text:
User talk:RaviP

see http://www.langwidge.com for more info about me

title: User talk:RaviP


text:
User:RaviP

See http://www.langwidge.com

title: User:RaviP


text:
User:Hansjörg~enwikibooks

 * Japanese: Kanji: Numerals

Flunetwork

 * Userpage in the German Wikipedia
 * Userpage in the German Wikibooks
 * Userpage in the Japanese Wikibooks

title: User:Hansjörg~enwikibooks


text:
Eclipse/Using Eclipse

Purpose
This book is intended for Java Developers, but other developers may also find some sections useful.

The goal of this book to make the reader a better (Java) Programmer.

Intended Audience - (Java) developers, anyone interested in improving the way he/she programs.

Prerequisites - None

Getting Started
As described in Eclipse website, Eclipse is an IDE for everything and nothing in particular. Eclipse core is a universal IDE (a general purpose development environment).

Downloading Eclipse
Eclipse doesn't come with the JRE. It is advisable that you download the latest JRE (Java Runtime Environment) from the Javasoft web site first.

After you have downloaded and installed the JRE, you may then download the Eclipse IDE. Another version of Eclipse is the EasyEclipse project. Its interface is about the same as Eclipse. You can download it instead from [easyeclipse.org]

Installing Eclipse
Installing Eclipse just involves unzipping the downloaded file into a directory. After unzipping the Eclipse IDE is ready to run.

Windows
Eclipse can be run by executing the file startup.jar. If Java Environment (JAVA_HOME) variables are defined then Eclipse IDE will automatically detect the JRE and start running.

Linux
After downloading, open the file eclipse.

Getting Help
Types of help available with eclipse:
 * 1) Online documentation
 * 2) Context sensitive help
 * 3) Hover help
 * 4) Active Help

Eclipse Help can be accessed using external browser http://localhost: / . The values for these fields can be found in preferences.ini file. Eclipse uses a tomcat server for displaying help documentation.

Configuring Eclipse
(Use different workspaces for different JREs otherwise due to autobuild wrong .class files will get generated)
 * Tuning your JRE

Workspace
Resource (projects, folders, files)

.metadata folder contains information about the workspace.

Keep different workspaces for different development projects (or different customers)

Bookmarks - A bookmark acts as a link to a particular line in a file.

Tasks - A task is created against each java error. Tasks can also be created as an reminder for some activities to be performed. Task contains priority and completion status. Tasks can also work as bookmarks.

(See command line options)
 * Running Multiple Instances of Eclipse at the same time

Perspectives
You can create your own (customized) perspective using configurations.

Running Other Applications within Eclipse

 * File Association (External Programs)
 * Run (External Tools)

need a "how to"/tutorial for External Tools running a main class in one project while referencing a jar file elsewhere. ex. project DoesReallyNeatStuff creates output based on project SomeStuff. How does a project reference the other project using External Tools?

Java Development using Eclipse
syntax highlighting, code completion, code assist, tasks and views.
 * Writing Code - generate, edit and navigate Java code.
 * Debugging
 * Team Work
 * Improving Productivity - hooking into well defined plugin points
 * Using Eclipse Code

Introduction

 * Related Topics:** Java, Java Runtime Environment (JRE),SWT

Introduction to Eclipse
Eclipse Project is made available under the Eclipse Public License.

About Eclipse contains information about what is eclipse.org?

Eclipse Download

Eclipse Project FAQs

Eclipse Projects

Eclipse 3.0.1 Online Help

Eclipse Community

Eclipse Configuration Management
Preferences and Properties in the Eclipse Workbench UI

Eclipse Architecture
Notes on the Eclipse Plug-in Architecture

Eclipse Plug-In Programming

 * PDE Does Plug-ins
 * A First Look at Eclipse Plug-in development
 * Naming Conventions
 * Eclipse Platform API v3.2

Miscellaneous
Branding your application

 * Eclipse - tool integration platform - open source
 * Eclipse community - 1000s of developers - around 50 software companies
 * Eclipse vision - new paradigm for development tools - platform centric - not tool centric - towards Universal IDE
 * Eclipse Project - tools built independently - work together as integrated sets
 * Eclipse Plug-ins - seamless integration - your imagination is the limited - 100 active Open Source Projects and vendors.

Highlights
debugger - breakpoints, display value of variable, hot code replace support - change your code while in debug mode, preference settings - tailor according to your needs yourself,
 * Eclipse 3-in-1 - a Java development environment, a tool integration platform, and an open source community.
 * Editor -anticipates your next move - code assist, think faster that you write use spell checker, refactoring - iterative process of improving your code Object Oriented approach, scrapbook - experiment with expressions, search tools,

Java doc comments templates
 * General purpose - For both programming and non-programming development tasks

integrated support for Ant, JUnit

Basic Concepts

 * Developer's Toolset - (design) modelling tool, IDE, version control, word processor,
 * Artifacts - architecture diagrams, code and user documentation
 * Workspace is a directory where your projects are stored.
 * Workbench consists of views, perspectives and editors.
 * Views provide alternate way of navigation.
 * Editors are associated with the file types. External editors can also be used with editors. OLE based editors integrates well with Eclipse.
 * Perspectives are collection of views.

Eclipse Architecture

 * Eclipse Platform
 * SWT
 * JFace
 * GEF/GMF
 * Workspace
 * Workbench
 * Help
 * Team
 * Debug
 * Plug-In
 * Extension Points
 * Plug-In Development Environment (PDE)
 * Platform Runtime

WorkBench Terminology
predefined tags TODO, FIXME, XXX
 * Menu bar
 * Tool bar
 * Perspective
 * Fast View bar
 * Resource Navigator
 * Properties View
 * Message Area
 * Text editor
 * Outline view
 * Bookmarks view
 * Editor status area
 * Tasks view -
 * Stacked view
 * Help View

Standard Widget Toolkit (SWT)
The SWT is a collection of APIs that allow writing GUIs (Graphical User Interfaces). The APIs are focused on providing tools to allow "widgets" (graphical controls such as checkboxes, edit controls, etc.) to be displayed and manipulated.

Related Projects
EMF - Eclipse Modelling Framework EMF is a modeling framework and code generation facility for building tools and other applications based on a structured data model. EMF allows a model described using Annotated Java, XML or modeling tools to be generated as executable Java code. The generated code allows the model structure to be inspected, and the model data to be queried, updated and persisted to external storage.

Accelerators(Key Board Shortcuts)

 * 1) Ctrl + F6 - switching between various editors.

How To's

 * 1) Creating Ant Build File.
 * 2) Create a simple project.
 * 3) Create a new file with .xml as extension
 * 4) Open Ant editor
 * 5) Write the Ant script
 * 6) Run As External Tools

 * 1) Creating a user defined Task Tag
 * 2) Select Tools > Preference
 * 3) Select Task Tag
 * 4) Add new Task Tag

title: Eclipse/Using Eclipse


text:
User:Mononoke~enwikibooks

Hi

Me on other Wikis:

http://de.wikipedia.org/wiki/Benutzer:Mononoke

de:Benutzer:Mononoke pl:Wikipedysta:Mononoke es:Usuario:Mononoke fr:Utilisateur:Mononoke

title: User:Mononoke~enwikibooks


text:
Talk:Japanese/Kana/Lessons/Hiragana/Lesson 2

Untitled
According to this page: http://www.thejapanesepage.com/hka.htm the stroke order for the 'ka' is different...

I learned in elementary school: curve-line → slash → spot, and I think you can write better in this way. But the stroke order is not so important...(if you can write well, that's ok) --Brevam 03:41, 21 Mar 2005 (UTC)

I learned sweeping curve, vertical line, dot. Also, GO is next to KO, as well as in the alternate section near GE, etc. I think the one near KO is unneeded and identical.

Mneumonic for Ko
It seems a little more complicated than it needs to be. Why not leave out the "far away, closer to you" stuff? That's not relevant for remembering the two lines being start and finish lines and "Go!" I'm going to edit it to make it simpler, but if there's some reason for the additional complexity feel free to revert. --Anonymous 2008/01/08

 * Nevermind. I see that it was all because of the "tail" on the top line; but it's a very confusing mneumonic. It should probably be rewritten. In any case, I'm just going to ignore all that stuff and just remember "Go!"


text:
User:Franl~enwikibooks

Hi, I'm Fran Litterio. To leave me a message, visit my talk page. To learn more about me, visit my personal Web page. To send me email, you need to get my email address. I'm also a contributor to Wikipedia. You can visit my Wikipedia user page.

Here are some links that only work for the currently-logged user (i.e., you):

 * Your watchlist without your edits.
 * Here is your monobook.js file.

I'm currently interested in (or contributing to) these Wikibooks:

 * Domain specific languages
 * Regular Expressions talk

 * Programming languages bookshelf
 * C++ Programming talk ✤ Python talk ✤ Tcl talk ✤ Bourne Again Shell talk

 * Computer Software Bookshelf
 * Linux Guide talk ✤ Inside Linux Kernel talk ✤ Linux kernel talk ✤ Linux For Newbies talk

 * Computer science bookshelf
 * Cryptography talk ✤ Open Source talk ✤ Internet Technologies talk

 * IT bookshelf
 * Networking talk

Helpful Wikibooks Links
General:

 * All bookshelves ✤ Staff lounge ✤ Textbook planning ✤ Requested Wikibooks ✤ IT bookshelf ✤ How to start a book ✤ Manual of Style

FAQ Collection:

 * Overview FAQ ✤ Contributing FAQ ✤ What is a module? ✤ Editing FAQ

Policies and guidelines:

 * What is Wikibooks ✤ Editing policy ✤ Image use policy ✤ Deletion policy ✤ Naming conventions

title: User:Franl~enwikibooks


text:
Korean/Lesson I2

Introduction
An important part of being able to understand and speak Korean is that one must have a firm understanding of the grammar used to make coherent sentences. During these first few lessons we shall focus on building a usable grammar base. In this lesson, we will learn some more useful particles, Present progressive, future tense, and the requesting form. We will also learn some new grammar, but it will not be the main focus of this lesson.

Conversation
Here we find Joseph meeting 찬호 again.

Dialogue

 * 찬호: 앗! 오래간만 입니다, 조세프!
 * 조세프: 네, 안녕하십니까, 찬호?
 * 찬호: 네. 저는 지금 학교로 가고 있습니다.
 * 조세프: 선생님을 만나겠습니까?
 * 찬호: 아니요, 공부하겠습니다. 조세프는 오늘 숙제를 하겠습니까?
 * 조세프: 네, 저는 집에서 하겠습니다.
 * 찬호: 그래요. 안녕히 가십시오.
 * 조세프: 안녕히 계십시오.

Conversation review
찬호 begins with another greeting:

 * 찬호: 앗! 오래간만 입니다, 조세프!

"오래간만 입니다" can be translated as: "Long time, no see" in English. At first, it's a hard expression to pronounce, but a little bit of practice should untie your tongue.

 * 조세프: 네, 안녕하십니까, 찬호?
 * 찬호: 네. 저는 지금 학교로 가고 있습니다.

New vocabulary, new particle, new verb tense. 지금 means “now”. In a later lesson, we will learn many words such as "later, tomorrow, yesterday, just a second ago, etc". In the next part, 찬호 uses a new particle with a similar meaning to what we learned before: "N + (으)로". This particle means "to", "toward", or "in the direction of". It can be interchanged with "에" relatively safely, but "로" with its additional usages, is a little more versatile. If the noun ends in a consonant then it becomes "으로" (집으로). Simple.

Finally, we have a new verb tense: the present progressive tense. It can also be made into a statement or question by adding the "VS + 고 있습니다" or "VS + 고 있습니까" forms. The strange thing about this verb tense is that the standard "VS + ㅂ/습니다" can mean the same thing! Remember in lesson 1, Joseph said "집에 갑니다". This could have also been said "집에 가고있습니다" or even "집으로 가고 있습니다." It is your choice. Some combinations sound more natural to others, but a beginning student doesn't have to be concerned with that. You will eventually get the feel of what sounds right.

 * 조새프: 선생님을 만나겠습니까?

This might sound funny, but one of the most important things to learn in Korean is not found in this sentence. Where is the subject? Is it 선생님 (“teacher”)? No, there is no subject. In Korean, if the subject of the next sentence is understood, it can be omitted. This is often found in colloquial English:

 * English speaker A: "I'm a little busy."
 * English speaker B: "Oh, studying today?"

However, in Korean, you can omit the subject more freely than English, and sometimes other elements can also be omitted, resulting in very short sentences. Well, if 선생님 ("teacher") isn't the subject, what is it? It's the direct object!

The particle 을 is used to designate the direct object of the sentence, i.e. the thing or person upon which the action is happening. In most textbooks, this is usually denoted as "을/를" because "을" comes after words ending in a consonant, and "를" comes after words in a vowel. This particle is omitable, but for the beginner, it's best left in so nothing gets confused.

Now, based on what we have learned so far, one might guess that the verb stem of the verb in this sentence is "만나겠다", which is a perfectly logical guess, but wrong. The actual verb stem is "만나다" which means "to meet" (as you might have gleaned from the previous paragraph). The "겠습니다" or, more correctly "겠다" is the future tense form. For this form, it is unimportant whether the verb stem ends in a consonant or vowel. Simply add "겠" and then finish off with "습니다" to speak politely. Easy as 파이, no?

 * 찬호: 아니요, 공부하겠습니다. 조새프는 오늘 숙제를 하겠습니까?

This sentence may sound a little strange, but it is nonetheless correct. 공부하다 means "to study", 오늘 means "today" and 숙제 means "homework." 하다 will be explained in more detail later, but for now, it means "to do" when by itself. Notice the 를 on 숙제? What is he doing? his homework!

 * 조새프: 네, 저는 집에서 하겠습니다.

Finally, we have another particle, 에서, which is translated "from" or "at". In this case, it functions as "at". Notice "Yes, I will do it at home."

 * 찬호: 그래요. 안녕히 가십시오.
 * 조새프: 안녕히 계십시오.

그래오 is a polite way of saying "okay." It also means "Yes that's right."

Korean sentence order
Korean sentences have a different word order from English. Whereas an English sentence typically has a Subject-Verb-Object word order, a Korean sentence typically has a Subject-Object-Verb word order. For sentences with only a subject and a verb, Korean and English word order is essentially identical:

If a sentence includes an object, the English and Korean order differs:

English: I am reading a book. English: I(subject) am reading(verb) a book(object)

Korean: 저는 책을 읽고 있습니다. Korean: 저는(subject) 책을(object) 읽고 있습니다(verb).

Predicates
A more complete understanding of Korean sentence order requires an understanding of Korean predicates (서술부어). As in English, complete Korean sentences must have a predicate that contains a conjugated Korean word (용언). Also as in English, Korean verbs (동사) are conjugated and so can be sentence predicates. However, with regard to forming sentences, Korean differs from English in two important ways:
 * 1) Korean sentences do not require subjects (주어), just predicates.  (That is, a Korean sentence with only a predicate is grammatically complete.)
 * 2) Korean adjectives (형용사) can be conjugated and used as sentence predicates.

Korean sentences that include subjects, indirect objects, direct objects, and complements often arrange them in this order:

Above is the usual word order in Korean, which is the order most easily understood by native speakers of Korean. However, excluding the predicate (the verb), the placement of other words is not entirely relevant to the meaning of the sentence. The following arrangements have the same meaning as the above example:

Vocabulary: 어휘

 * 오래간만 입니다 - Long time, no see!
 * 선생님 - Teacher
 * 숙제 - Homework
 * 만나다 - To meet
 * 공부하다 - To study
 * 하다 - To do
 * 지금 - Now
 * 오늘 - Today

Grammar: 문법

 * VS + 겠습니다 - Future Tense
 * VS + 고 있다 - Present Progressive
 * N + (으)로 - Toward
 * N + 을/를 - Direct Object Marker
 * N + 에서 - From, At, Location of Action

Practice: 연습
Conjugate the following verbs with the future and present progressive tenses in polite form:

Add 에서, (으)로, and 을/를 particles to each noun:

<>

title: Korean/Lesson I2


text:
User talk:Franl~enwikibooks

Hi! Feel free to leave me a message below. To add a message, please click on the "+" in the tabs at the top of this page, which will make your message appear in a separate section. — franl

Automata Theory
As per our discussion at Regular Expressions, I have decided to create a new wikibook on the topic of automata theory. We can use this new book to serve as a foundational background behind regular expressions, so that we can talk about the advanced topics on that subject, without having to lay all the theoretical groundwork. Currently, this new book exists only as a preliminary outline HERE on my users page. Any comments or suggestions on this new outline would certainly be appreciated. --Whiteknight (talk) (projects) 00:22, 12 June 2006 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Franl. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Franl~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:10, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:59, 19 April 2015 (UTC)

title: User talk:Franl~enwikibooks


text:
User:Luqui~enwikibooks

Wikipedia:User:Luqui

title: User:Luqui~enwikibooks


text:
Talk:Myers-Briggs Type Indicator/INTP

re:

"Misunderstood, INTPs are burdened by their idealism, searching restlessly for their one true love, or for their one true friend."

i, as an intp, STRONGLY agree. i also know another intp very well and they feel the same.

title: Talk:Myers-Briggs Type Indicator/INTP


text:
Hindi/Pronunciation

One of the biggest challenges for a native English speaker when learning Hindi is the pronunciation.

Hindi Consonant Sounds
Velar - from the soft palate, where the mouth becomes the throat

Ka-क, Kha-ख, ga-ग, gha-घ, nga-ङ

Palatal - from the hard palate

cha-च, chha-छ, ja-ज, jha-झ, ña-ञ

Retroflex - from the point where the palate joins the teeth

ta-ट, tha-ठ, da-ड, dha-ढ, Na-ण, Ra-ड़ (retroflex “flap”), Rha-ढ़ (aspirated retroflex “flap”)

Dental - from the teeth

ta-त, tha-थ, da-द, dha-ध, na-न

Labial - from the lips

pa-प, pha-फ, ba-ब, bha-भ, ma-म

Liquids, semivowels

ya-य, ra र, la ल, va व, sha श, shha ष, sa स,        ha-ह

Borrowed letters: za-ज़, fa-फ़, zha-श़

title: Hindi/Pronunciation


text:
Cookbook:Cuisine of Malaysia

| Southeast Asian cuisines

 * Arisa – A rare, traditional chicken dish
 * Eurasian Smore – Beef-shank stew
 * Bah Kut Teh – Pork Spare Rib Herbal Soup
 * Pulut Durian – Glutinous rice with Durian
 * Coconut Rice (Nasi Lemak) – A type of rice cooked with coconut milk
 * Pattaya Fried Rice – Fried rice covered with omelette and chilli sauce

title: Cookbook:Cuisine of Malaysia


text:
GCSE Science/Generating electricity answers

Some thoughts on the questions posed... (perhaps this will become an 'answers' page in due course?)

Q1. Think back to the ideas presented on 'GCSE Science/Induction':  Increasing the speed of rotation is like moving the magnet in and out of the coil faster, so the waveform on the oscilloscope will be bigger in relation to the y-axis (larger voltage induced). However, since the rate of rotation is increased, the frequency will also be greater, so the peaks will be closer together, hence correct answer is 'C'.

Q2. Some typical sources of a.c. are the alternator on a car and the generator at a power station. Sources of d.c. include dry cells (commonly known as 'batteries' in the UK), photovoltaic cells (solar panels), lead-acid accumulators and smoothed d.c. power supplies found in science labs.

Q3. A typical device which only works with d.c. is (as mentioned in the article - if you were paying attention!) the electric motor (the split-ring commutator type depicted in the article about the motor effect). A device which doesn't mind whether you use a.c. or d.c. is the light bulb.

Q4. Was this question put in as a red-herring, or a means of challenging brighter pupils?! Well, what did you make of it? Tricky, given the setting? Well, since hair-dryers need to blow out a lot of hot air, their power requirement is fairly large. This means that batteries won't last long enough to be a viable option! With this in mind, the only sensible thing to do is use mains, i.e. alternating current. The heater element doesn't care which way the current is flowing - it just gets hot. This does pose a problem for the motor, though. It can't be the split-ring commutator variety, since it would just vibrate on the spot, get hot, and then die! (Electric motors invariably keep their windings from overheating by drawing in cooler air from outside their housing as they rotate.) So, one of those special a.c. motors mentioned earlier has to be used...

Q5. The useful component he was thinking of is called a 'diode'.

(Most diodes are now made from semiconductor materials, but the original diode was called a 'thermionic valve'. From your knowledge of Biology (particularly of the heart) why do you think the term 'valve' is appropriate?)


text:
Wikibooks talk:Transwiki log/Articles moved to here

Duplication problem with How to learn a language article
There is a problem involving a duplication of the How to learn a language article that was originally on the en.wikipedia.

The article exists in two separate forms and appears to have been brought in twice:

 * How to learn a language
 * How to learn a language

Each has its own unique editing history. The one in the Transwiki domain is much more active. I would suggest the other version has have its edits merged into the Transwiki version and then be deleted.

Oska 00:38, 28 Dec 2004 (UTC)
 * done. Gentgeen 01:39, 28 Dec 2004 (UTC)

 * Please correct me if I'm wrong but it appears that you have simply deleted the article under the Transwiki namespace and put in a redirect to the other version. If so that is not a good solution as the Transwiki version had been much more active and from memory (as the history page for that version has now disappeared) had about 30 edits made to it since being moved to wikibooks. The other version has only 3 edits made to it. My suggestion was for the articles to be merged, not for the (probably better) Transwiki version to be lost.

 * I would have done the merge myself but I was unsure if I had completely understood what had happened. I have been trying to find out what the protocol is for bringing stuff into wikibooks and what went wrong in this case. I can't do the merge now because it appears one of the versions has been lost.

 * The transwiki namespace seems to be problematic in allowing an article to be unintentionally forked like this. Why not just move the article into its normal title right from the start?

 * Oska 08:41, 28 Dec 2004 (UTC)

I guess I will have to type in text to make this test work. Apologies. --Xyzzyplugh 06:01, 28 March 2006 (UTC)

A bit confused
I have copied and pasted w:User:Endgame1/AutoCAD Layers to Transwiki:AutoCAD Layers. But even though w:Help:Import tells me that this is not enabled on Wikimedia wikis, it seems that there is a way to import with the history intact. Also there seems to be just one person doing all the transwikis. Can someone point me in the right direction of what I'm meant to be doing.--Konstable 01:10, 2 November 2006 (UTC)

 * Well, Special:Import doesn't work on Wikimedia wikis by default. However, things at the English Wikibooks are almost never the default. The developers enabled the import function here a few weeks ago. As stated in the Help page you found, only an admin can perform an import. I'll go see if I can remember how to import a file for you. Gentgeen 10:32, 2 November 2006 (UTC)

 * Yup, that was as easy as I remember, and I still managed to screw it up. The imported page with its history (and talk page) are at Transwiki:Endgame1/AutoCAD Layers and Transwiki talk:Endgame1/AutoCAD Layers. Gentgeen 10:38, 2 November 2006 (UTC)

 * You didn't screw it up, it was just confusing because someone on wp had userified the article. I hadn't imported it yet because (a) the userifying made it a pain in the butt, and (b) totally forgot about it. It just needs to be moved to the nonuserified name... will do now. -- SB_Johnny | talk 13:09, 2 November 2006 (UTC)

 * Sorry, I didn't make that clear. I had to import it twice, as the first time, I imported the talk page over the content page. I fixed it with a speedy delete and re-import of the pages, which is still pretty easy. Even with having to do it twice, it's faster than the old copy-paste transwiki process. Gentgeen 23:23, 2 November 2006 (UTC)

 * Puh, yeah, no kiddin! But next time don't speedy, just move it to Transwiki_talk and then re-import :). -- SB_Johnny | talk 23:33, 2 November 2006 (UTC)


text:
Esperanto/Traveling

-

Verb Conjugation
In lesson 1, we learned that the base form of a verb – the infinitive, which ends in -i – is translated "to verb". The present tense of any Esperanto verb ends in -as and is translated "I verb", "I am verb'ing", or "I do verb". Note that "I" is only an example and can be replaced with anything.

Now we will learn the future and past tenses, the command form of a verb, and even how to form verbs that lack tense altogether.

 * Future Tense:The future tense is formed by replacing the -i ending of the infinitive with -os. These can be translated "I will verb" or "I will be verb'ing".
 * Past tense:The past tense is formed by replacing the -i ending of the infinitive with -is. These can be translated "I did verb" or "I verb'ed".
 * Imperative:The imperative is the form one would use when they are telling somebody what to do, and is therefore sometimes called the command form. For example, in the sentence "Bob, please run to the store", "run" is an imperative. In Esperanto, these are formed by replacing the -i of the infinitive with -u.
 * Conditional:This form is used when a verb lacks a tense and refers to something that could potentially happen or have happened, and it is not really a tense, as such. For example, "Bob would run if Jim were to tell him." Bob may not have run yet, and Jim has not necessarily asked him to. All we know is that Bob would run if Jim would tell him to. Esperanto has no word for "would", but the meaning of it is reached by replacing the -i of the infinitive with -us.

These are all the forms of the active voice, that is, when the subject is the one "doing the verb". The passive voice, when the subject is "being verb'ed" by something else, will be covered later.

Be sure to memorize the "theme vowels" for each tense: a for the present, o for the future, and i for the past. They show up in many places within the language, particularly the participles, which are explored in the next section.

Participles
Participles are adjectives formed from verbs, and are used to describe somebody who did, is doing, or will do a verb. The English language has two types of participles: the present active participle and the past passive participle.
 * The present active participle is an adjective describing somebody who is doing something in the present. For example, "The running boy will soon arrive home." "Running" is a participle.
 * The past passive participle describes somebody who, at some time in the past, had the verb done to them by something else. For example, "The torn and crumpled paper was thrown in the trash." The paper is torn because, in the past, somebody tore it, and it's crumpled for the same reason. In English, the passive participle usually looks the same as the past form of the verb, as is the case with "crumpled" ("he crumpled it", "it is crumpled"), but not for "torn" ("he tore it", "it is torn").

Esperanto, however, has eight participles. Since English only has two participles, these don't always have perfect translations. Take a look at the table of forms below. If not already obvious, they are formed by replacing the final -i of the infinitive with these forms. Those in yellow exist in English, the rest have imperfect translations.

Because four of the participles have imperfect translations, they will have to be rephrased when translated into English.

At the same time, the English sentence "The tree which will be chopped down is tall." can be translated "Arbo haketota alta estas." instead of the more literal "Arbo, kiu estos haketata, alta estas."

Vojaĝado (Travelling)
Buying a plane ticket / Aĉeti veturo-bileton
 * Ludoviko: Saluton, mi volas aĉeti veturo-bileton.
 * Vendisto: Al kiu urbo?
 * Ludoviko: Al Parizo.
 * Vendisto: Bone, la aviadilo ekflugos el Berlino al Parizo post dudek minutoj.
 * Ludoviko: Dankon.

Asking and Answering Questions
Asking questions in Esperanto is very easy to accomplish with the help of a few question words.

Asking Yes/No Questions
In Esperanto, all questions that require "yes" or "no" as an answer begin in "Ĉu"; no other change is made to the sentence. For example, "Do you eat?" would be said "Ĉu vi manĝas?".

In English, "It is a dog." would be asked "Is it a dog?". You may notice that the only change is that "it" and "is" switch places. This is not true of Esperanto: all you have to do is put "Ĉu" at the beginning of the sentence. That's it. ("Ĉu ĝi estas hundo?" means "Is it true that it is a dog?" or more simply "Is it a dog?".)

Answering Yes/No Questions
Answering Yes/No questions is very easy: "jes" means "yes" and "ne" means "no".

Other Types of Questions
Here is a list of several basic question words:

These words may be useful in answering questions that use the above words:

Notice how all these words are linked to the question word that has same ending. This system of words, called the correlatives, will be dealt with in a later chapter.

Exercise: Translation

 * Ludoviko: Min helpu!
 * Virino: Jes?
 * Ludoviko: Mi bagaĝojn de mia edzino mislokas. Ĉu vi povas trovi ĝin?
 * Virino: Jes, mi havas ĝin jam.
 * Ludoviko: Bonege! Mia edzino feliĉega estos. Kie vi trovis ĝin?
 * Virino: Tie, apud mia bagaĝon.
 * Ludoviko: Estas strange. Se mi havus monon, mi vin pagus. Dankon, sinjorino, kaj adiaŭ!
 * Ludoviko revenis lian edzinon.
 * Edzino: Ludoviko! Ĉu vi havas mian bagaĝon?
 * Ludoviko: Jes, ĝi trovita de virino bona estas.

What You Need to Know

 * To change a standard sentence into a yes or no question, place the word "ĉu" in front of it.
 * The Table of Correrlatives in Appendix H, in order to ask questions.
 * The forms and uses of infinitive, imperative, and conditional verbs.
 * The forms of the past and future tenses.
 * The forms of the six participles and how to use and translate them.

{{Only in print|1=

Translation Key

 * Vojaĝado
 * Ludwig: Hello, I want to buy a ticket.
 * Seller: To which city?
 * Ludwig: To Paris.
 * Seller: Okay, the plane will take off from Berlin to Paris in twenty minutes.
 * Ludwig: Thanks.

 * Exercise
 * Ludwig: Help me!
 * Woman: Yes?
 * Ludwig: I lost my wife's luggage. Can you help me find them?
 * Woman: Yes, I already have them.
 * Ludwig: Very well! My wife will be very happy. Where did you find them?
 * Woman: There, next to my luggage.
 * Ludwig: That's strange. If I had money, I would pay you. Thank you, miss, and goodbye!
 * Ludwig returned to his wife.
 * Wife: Ludwig! Do you have my luggage?
 * Ludwig: Yes, it was returned to me by a good woman.

}}

-

title: Esperanto/Traveling


text:
Talk:Esperanto/Appendix/Alphabet and pronunciation

Untitled
The 'o' in dot and the 'o' in or seem to be different o's
 * The 'o' in dot is the correct sound. --Gabriel Beecham 00:30, 19 Feb 2005 (UTC)

Why does the U first have an accent in the beginning of the article and further down an umlaut?15:37, 24 March 2006 (UTC)

Audio
I'm making recordings of all the sample Esperanto words. I'm almost done, but I want to clear something up before I finish: I'm not sure ĝojo is such a great example for the oj diphthongs. When the noun ending is added, a syllable break will usually be inserted, and the word typically sounds like ĝo-jo, unless I force it. Hovever, any plural noun should do the job, so I'll change it to lingvoj (languages) unless there are any objections. I hope this will be clearer, and I'll be back soon with my finished recordings. --WurdBendur 05:59, 31 July 2006 (UTC)

Ought to change
Ref (Post-edit notice) The 'o' sound in the main table states o as in French mot or o as in Spanish no, but I don't speak French or Spanish. From what I gather, this would be the sound of o as in "cord" or "sorry", and I think this being an English Wikibook it would be best to include English examples for all instructive content. ~Jafet 11:22, 19 November 2007 (UTC)

Near the end in the diphthongs section you mention the pronunciation of 'boy' for one digraph and then 'buoy' for another. To people who are from the UK (like me) this is confusing because we pronounce both words exactly the same (with that 'oy' sound) but I know that Americans pronounce each differently. It might help to mention that on the page to stop us Brits getting confused!


text:
Amateur Radio Manual/Ohm's Law and Resistors

This chapter is an overview of resistors and their practical concerns. Resistors are fundamental building blocks of amateur radio, being used for current limiters, voltage dividers, oscillators, filters and more.

Resistors

 * Resistors, generally speaking, resist the flow of electricity. They prevent some electrons from travelling through them. This means that current flow is reduced. Almost all materials have resistance (some, such as superconductors, have zero resistance.)
 * At an atomic level, resistors oppose the flow of electrons. Some compounds have only a moderate hold on their electrons. Thus, electricity can flow, but with less energy. These compounds are said to have a high resistance. Copper has a very loose hold on some of its electrons, which can consequently have its electrons dislodge with very little energy. Thus, copper has a low resistance.
 * The unit of resistance is the Ohm, named after Georg Ohm. An Ohm is the unit of resistance that will allow one Ampere to flow if an electromotive force of one Volt is applied. The symbol for an Ohm is a capital omega (Ω).

Practical Resistors
Two important things to know about resistors when using them are their schematic symbols and the resistor color code.

 * Fixed resistors, as the name implies have a fixed resistance.
 * Potentiometers have a variable resistance

The Resistor Value Color Code

A resistor generally has four color bands. The first two bands give the first two digits e.g. brown, black represents "10". The third band indicates the multiplier. This is merely the number of zeros you add to the end of the first two digits. For example, black, brown, red represents "10" "00", or "1000 Ω" or "1 kΩ".

Construction Techniques
There are three main construction techniques used in making resistors: wirewound, carbon composition, and metal film.

 * Wirewound
 * As explained in this book about resistors, the narrower a conductor, the higher its resistance. Also, the longer it is, the higher its resistance. Combining these two characteristics, a wirewound resistor consists of a long, thin wire wrapped in a coil. This creates a high resistance.
 * Pros
 * Can be made to very close tolerances (tolerance is how close the actual value is to the listed value)
 * High power handling capability
 * Cons
 * Bulky
 * Expensive
 * Highly inductive
 * Carbon Composition
 * This resistor consists of a carbon powder in a container with wires attached to it. Its resistance can be changed when manufactured by using different concentrations of carbon in the powder.
 * Pros
 * Very cheap
 * Non-inductive
 * Cons
 * Poor tolerance
 * Poor stability (i.e. the value of the resistor can change considerably with time)
 * Metal Film
 * This resistor consists of a container with a thin metal film on it. Its resistance at manufacture can be changed by etching the metal away in certain patterns.
 * Pros
 * Inexpensive
 * Non-inductive
 * Cons
 * If stressed beyond their limits, metal film resistors tend to stop conducting entirely rather than have their resistance changed. This is often a benefit, as in some cases no operation is preferable to unpredictable operation.

Ohm's Law
Ohm's Law a fundamental principle in electronics. The law states the relationship between electromotive force, current and resistance. Knowing any two of these allows the third one to be discovered. It is expressed as "E = IR", where E is the electromotive force in Volts, I is the current in Amperes, and R is the resistance in Ohms.

Consider the following two examples.

Examples
Answer:
 * 1) The voltage and resistance are known. The current must be found. From Ohm's Law, $$\mathrm{I} = \frac{\mathrm{E}}{\mathrm{R}} = \frac{12 \mathrm{V}}{1 \Omega} = 12 \mathrm{A}$$
 * No.

Answer:

From Ohm's Law, $$\mathrm{R} = \frac{\mathrm{E}}{\mathrm{I}} = \frac{5 \mathrm{V}}{2.5 \mathrm{mA}} = 2 \mathrm{k\Omega}$$

Notice in this case that milliamps were used instead of Amps. We are allowed to do this because we used kilohms as the unit of resistance ( 1 mA = 0.001 A).

Series and Parallel Combinations of Resistors

This image shows a schematic of two resistors in series. This is a series arrangement because the resistors are aligned head to tail; the current going through one resistor goes through both. The two most important aspects of this circuit are

where $$\mathrm{I_\mathrm{tot}}$$ is the total current and $$\mathrm{E_\mathrm{tot}}$$ is the total voltage
 * 1) $$\mathrm{I_\mathrm{tot} = I_1 = I_2}$$
 * 2) $$\mathrm{E_\mathrm{tot} = E_1 + E_2}$$

The current and voltage equations are determined from Kirchhoff's laws.

This image shows a schematic of two resistors in parallel. This is a parallel arrangement because the tails of the resistors are connected to each other and the heads are connected to each other. The two most important aspects of this circuit are:

where $$\mathrm{I_\mathrm{tot}}$$ is the total current and $$\mathrm{E_\mathrm{tot}}$$ is the total voltage
 * 1) $$\mathrm{E_\mathrm{tot} = E_1 = E_2}$$
 * 2) $$\mathrm{I_\mathrm{tot} = I_1 + I_2}$$

Once again, the current and voltage equations are determined from Kirchhoff's laws.

Effective Resistance of Series and Parallel Combinations
The effective resistance of combinations of resistors can be determined by Ohm's Law. In the serial case, $$\mathrm{E_\mathrm{tot}} = \sum_n{E_n}$$, while $$\mathrm{I_\mathrm{tot}}=\mathrm{I}_n$$ for all n. Since $$\mathrm{E}_n=I\times \mathrm{R}_n$$, $$\mathrm{E_\mathrm{tot}} = \sum_n{I\times R_n} = I\sum_n{R_n}$$. Dividing voltage by current gives resistance, $$\mathrm{R}_\mathrm{tot} = \sum_n{R_n}$$.

In the parallel case, $$\mathrm{I_\mathrm{tot}} = \sum_n{I_n}$$ and $$\mathrm{E_\mathrm{tot}}=\mathrm{E}_n$$ for all n. Since $$\mathrm{R}_\mathrm{tot}= {\mathrm{E_\mathrm{tot}} \over \mathrm{I_\mathrm{tot}}} = {\mathrm{E} \over {\sum_n{\mathrm{E} \over{\mathrm{R}_n}}}} = {1 \over {\sum_n{1 \over \mathrm{R_\mathrm{n}}}}}$$

Voltage Drops
A voltage drop is the voltage across a component. In the example of the two resistors in series above, the voltage drop across $$\mathrm{R_1}$$ is $$\mathrm{E_1}.$$ By changing the value of a resistor, the voltage drop across it can be changed, allowing a variable voltage to be created from a fixed voltage.

Power
Resistors restrict the flow of electricity. However, the energy expended doing so must go somewhere. In the case of resistors, the energy is radiated as heat. This is what heats up the filament in a light bulb or the heating elements in a toaster. There is a limit to how much power a resistor can dissipate safely. As a rule, the bigger (in size) the resistor, the more power it can dissipate.

Power is measured in Watts (abbreviated W), with one Watt equal to one Joule per second. In electronics, $$\mathrm{P} = \mathrm{EI}.$$ This permits calculation of the power dissipated by a resistor.

 * 1) If voltage and current are known, then the power is simply their product.
 * 2) If voltage and resistance is known, then:
 * $$\mathrm{P} = \mathrm{EI} = \mathrm{E} \times \frac{\mathrm{E}}{\mathrm{R}} = \frac{\mathrm{E^2}}{\mathrm{R}}.$$
 * 1) If current and resistance are known, then:
 * $$\mathrm{P} = \mathrm{EI} = \mathrm{IR} \times \mathrm{I} = \mathrm{{I^2}R}.$$


text:
Blender 3D: Noob to Pro/The Game Engine

Next page: Your first test Previous page: Intermediate Animation -- Back to Index

The Blender Game Engine lets you create games. You can do this either with python scripts or with special tools built into the Blender interface.

Next page: Your first test Previous page: Intermediate Animation -- Back to Index

title: Blender 3D: Noob to Pro/The Game Engine


text: User talk:219.130.212.86

title: User talk:219.130.212.86


text:
The Pagan Beliefs Surrounding Christmas

Contents

 * 1) /Introduction/
 * 2) /The Date Jesus was Born/
 * 3) /Traditions of Christmas/
 * 4) /The Christmas Tree/
 * 5) /Bibliography/

title: The Pagan Beliefs Surrounding Christmas


text:
The Pagan Beliefs Surrounding Christmas/Introduction

The month of December holds one of the most celebrated holidays in the world. Although Christmas is extremely popular, do we really know the story behind this celebration? Indeed, many questions go unanswered when it comes to Christmas. Today we are going to explore those questions and answers. We are going to look into many controversial aspects of Christmas, including things such as dates, customs, and traditions, so join me in this marvelous exploration of Christmas.


text:
The Pagan Beliefs Surrounding Christmas/The Date Jesus was Born

Was Jesus born on December 25?
The Bible doesn't explicitly state the date of Jesus' birth, but it does give clues. Luke 2:8-14 speaks of shepherds living outdoor and tending to a flock of sheep. The text reads, "And there were in the same country shepherds abiding in the field, keeping watch over their flock by night." Some people have concluded that this would be an unlikely practice in the month of December, for it is argued that the weather conditions would be too cold to live outside or tend to a flock of sheep.

On the other hand, the lands immediately to the east of Bethlehem begin to descend sharply down toward the Dead Sea, so that it is much warmer, even in December. Shepherds would not keep their sheep in the immediate vicinity of Bethlehem at any time of the year since sheep are always kept away from farmlands so as to avoid the sheep eating crops. It is therefore reasonable that the birth of Christ took place at any time of the year, including December.

_______________________________________________________________________________________________________

The Book of Luke tells us that John the Baptist was 6 months older than Jesus, [Luke 1:26]. The book also tells us when John was conceived so it is possible to approximate the time of John's birth...and that of Jesus.

John's father, Zechariah, served as a priest in the division of Abijah, [Luke 1:5]. His priestly duty entailed one week of temple service every year plus three more weeks during the three yearly festivals.

His division was the eighth so his period of temple service began in the eighth week of the year, [I Chronicles 24:10]. The Hebrew year, being lunar, began in the spring around late March early April. The eighth week would then generally fall around the first of June the way we show the months of the year on our calendar.

Luke 1:23-24 tells us that Elizabeth, John's mother, became pregnant right after Zechariah's service in the temple. This would have been mid June....approximately. This means that John the Baptist would have been born around mid March....or close to Passover. Jesus would have been conceived in John's sixth gestational month by the Holy Spirit, [Luke 1:26] which would have been December....so Jesus would have been born around the middle of September. This event would have probably taken place about the time of the last Hebrew Holiday of Sukkot,(Feast of Tabernacles). Since everyone was expected to travel to Jerusalem for the three annual feasts this is probably the real reason why there was no room in the inn.

During the Feast Days the normal population of Jerusalem, 120,000, would probably swell to well over 1,500,000 folks. This would not be the case in the Month of December as there were no annual Feast Days then. Bethlehem, being a "suburb" of Jerusalem would likely fill up quickly with the overflow. This time would also be consistent with the shepherds still in the fields during September. The weather in Israel during December can be quite cold so flocks are usually brought into shelter no later than the middle of October.

The 25th of December date is not scriptural and as you can see by the above evidence is not likely.


text:
The Pagan Beliefs Surrounding Christmas/Traditions of Christmas

Another aspect of Christmas that receives much criticism is its traditions. Traditions such as kissing under mistletoe are very popular, but have no biblical reference at all. Bill McLain wrote in his book, “There are many legends about mistletoe. One Scandinavian legend states that Loki, the god of destruction, killed Baldur, the god of peace, by shooting him with an arrow made from mistletoe. Other gods and goddesses were saddened by Baldur’s death and asked that his life be restored, which it was. In appreciation, his mother Frigga hung up the mistletoe and promised to kiss all who passed under it. Because of this, mistletoe became the symbol of both forgiveness and love.” There are also a few other beliefs of mistletoe from around the world. During the Middle Ages, people would hang mistletoe over doors and on their ceilings to scare off evil spirits and prevent witches from entering. In addition, there is an old superstition that if you place a twig of mistletoe under your pillow you will not have any nightmares.


text:
The Pagan Beliefs Surrounding Christmas/The Christmas Tree

It is safe to say that the Christmas tree is one of the most recognized symbols of Christmas, yet the origins of the Christmas tree are not clear. There is a legend that Saint Boniface started the custom of the Christmas tree in Germany around the eighth century. It is said that Saint Boniface found a group of pagans worshipping an oak tree and became angry; consequently, he proceeded to cut down the Oak tree. Immediately a small fir tree is said to have sprouted from the middle of the oak stump and reached to the sky. Thus, Saint Boniface told the onlookers that this would be their holy tree because it was evergreen, a symbol of everlasting life.

Historically, an oak tree named Irminsul (meaning Great Pillar) was in fact venerated by the Saxon tribes of Germany as the symbol of their chief god, Tiu, also known as Saxnot. Located in the vicinity of the modern town of Goettingen, the Irminsul was destroyed on the orders of the Frankish emperor Charlemagne during the late 8th century CE, as part of a military campaign to subdue the Saxons and convert them to Christianity.

Although many versions of the story exist, many authorities believe that the true origins come from ancient Egypt. Bill McLain writes, “On December 21, the shortest day of the year, ancient Egyptians decorated their homes with green palm branches to symbolize life’s triumph over death.” Before Christianity, plants and trees that remained green throughout the year were believed to have special meaning for people in winter. Bill McLain continues explaining, “Romans used evergreens to decorate their homes during the winter festival of Saturnalia, which honored Saturn, the god of farming.” In addition, Ancient Druids, a member of an order of priests in ancient Gaul and Britain who appear in Welsh and Irish legend as prophets and sorcerers, were known to place evergreen branches over doors to frighten away evil spirits.

People decorate the trees with baubles and tinsel to make it look really pretty to impress guests. Lights are put up outside houses as well to impress people in the cars driving past.


text:
User talk:Franzjosefmehr~enwikibooks

Komplexe Zahlen
Hallo,

ich habe das Modul Komplexe Zahlen in die deutschsprachigen Wikibooks übertragen. Wenn du dem Bild Image:Komplex1.JPG und Image:Komplex2 1.JPG noch eine Lizenzangabe hinzufügen könntest, könnte ich die Bilder auch kopieren. Würde mich freuen dich bald in der deutschsprachigen Wikibooks begrüßen zu können. Gruß -- Daniel 22:50, 28 Dec 2004 (UTC)

 * Hallo,

 * das Kästchen reicht leider nicht aus. Du musst nochmals explizit angeben, dass du die Bilder unter die GUN FDL stellst (ist zugegeben etwas verwirrend). Genaueres erfährst du unter . Hier in den englischsprachigen Wikibooks ist dies etwas anders, da hier auch Bilder verwendet werden dürfen, die unter Fair – Use stehen. Diese sind allerdings weit eingeschränkter nutzbar als GNU FDL Bilder. Deshalb achten wir in den deutschsprachigen Wikibooks sehr darauf, dass die Bilder unter der GNU FDL oder Public Domain gestellt werden.

 * Bei mir gab es keine Probleme den Kurs zu löschen. Hab das mal in den deutschsprachigen Wikibooks gemacht (ich hoffe ich hab nicht zuviel gelöscht bzw. das richtige gelöscht).

 * Zu deiner Frage ob die Kurse auf deiner Seite interessant sind: Ich kann hier nur für die deutschsprachigen Wikibooks sprechen. Aber generell würde ich sagen: auf jeden Fall. Auf der Diskussionsseite solltest du dann noch einen Vermerk machen, dass du selbst der Autor bist und den Text unter die GNU FDL stellst (z.B. "Ich selbst bin Autor dieses Kurses und stelle hiermit den Kurs unter die GNU FDL" oder so ähnlich). Dies ist natürlich nur für die Kopie von (eigenen) Webinhalten ins Wikibooks notwendig.

 * Beiträge solltest du nur auf den entsprechenden landessprachigen Wikibooks machen, da ansonsten beispielsweise jeder nach Beiträgen zu   komplexen Zahlen auf der deutschsprachigen Wikibooks sucht. Möglicherweise sind hier noch einige deutschsprachige Beiträge, die aber alle noch aus der Zeit vor der Auftrennung in die nationalen Wikibooks stammen, als es nur das internationale Projekt gab.

 * Gruß -- Daniel 19:44, 29 Dec 2004 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Franzjosefmehr. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Franzjosefmehr~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:10, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:59, 19 April 2015 (UTC)

title: User talk:Franzjosefmehr~enwikibooks


text:
Cookbook talk:Potato Omelet

The standard Omelette shouldn't include any fillings. See m-w.com.

 * Right now we've got (at least) three Omelette recipes. Being an omelette purist is not the first thing I would worry about. Grimm

I think the omelette pages need to be revised. I propose one description (not recipe) of what an omelette is on the Omelette page (with a redirect from Cookbook:Omelet). Some short descriptions (with pictures, perhaps, like on the Cookbook:Melon page) of typical omelets, French, Japanese/Asian, Spanish and links to specififc recipes. What's described here seems like a french omelet, as does the Cookbook:Omelet, so those two recipes should be merged into one French Omelet recipe (with soime additional info). We should also decide on whether to use omelette or omelet. Omelette is more popular according to google, but I think Omelet is better for non-french omelettes. risk 13:31, 11 August 2005 (UTC)
 * Agreed re:centralizing this as a "type" of food. I'd almost like to suggest using the category page for this purpose. Since Omelette is more popular, it's probably the one we should use, but we should definitely have a redirect to the other. Kellen T 18:43, 11 August 2005 (UTC)

title: Cookbook talk:Potato Omelet


text:
Cookbook:Southern Cuisine

Recipes
 * Biscuits and Gravy
 * Burgoo
 * Cabbage and Bacon
 * Cajun Red Beans and Rice
 * Candied Sweet Potatoes
 * Chicken-fried Steak
 * Chicken Livers
 * Collard Greens (recipe)
 * Country Fried Steak and Gravy
 * Creamed Corn
 * Fried Chicken
 * Fried Green Tomatoes
 * Fried Okra
 * Grits
 * Key Lime Pie
 * Skillet Cornbread
 * Southern Cornbread
 * Spoonbread
 * Turnip Greens

title: Cookbook:Southern Cuisine


text:
MySQL

MySQL is a free, widely used SQL engine. It can be used as a fast database as well as a rock-solid DBMS using a modular engine architecture.

The purpose of this wikibook is to provide a practical knowledge on using the database from two points of view:
 * application developer: learn about SQL basics, phpMyAdmin, query optimization
 * system administrator: learn about installation, security, maintenance, failover, high availability

Best of all, this book is freely available for everybody to use and share, under the GNU Free Documentation License and the Creative Commons Attribution/Share-Alike License.

Contents

 * /Introduction/
 * /MySQL Practical Guide/
 * /Databases manipulation/
 * /Language/
 * Browsing the databases
 * Specifying table names
 * Definitions
 * User Variables
 * Alias
 * Data Types
 * Table manipulation
 * Data manipulation
 * Queries
 * Using/Dealing with NULL
 * Operators
 * Import / export
 * Functions
 * /Stored Programs/
 * Spatial databases
 * Exercises
 * /Pivot table/ or a crosstab report
 * /Table types/
 * MyISAM and InnoDB
 * Merge Table
 * MEMORY / HEAP
 * BDB
 * BLACKHOLE
 * /Comparison/
 * With other databases
 * With SQL92
 * Writing portable, non-MySQL-specific code
 * /Administration/
 * /Replication/
 * /Optimization/
 * /Maintenance and evolution/
 * /APIs/

Appendices

 * /Debugging/
 * /CheatSheet/
 * /Contributors/

Related wikibooks

 * Structured Query Language: about general SQL programming, with lots of exercises.
 * Converting MySQL to PostgreSQL: highlights the differences between the two database servers

Freely-licensed documentation and samples
The following source is released under the GFDL and hence a good candidate for inclusion in the wikibook, as well as joint writing efforts:

 * (CC-BY-SA 3.0)

Non-freely-licensed reference documentation

 * MySQL has a great used commented documentation on their website - and it's completely free.

title: MySQL


text:
PHP Programming/Caching

A cache is a collection of duplicate data, where the original data is expensive to fetch or compute (usually in terms of access time) relative to the cache. In PHP, caching is used to minimize page generation time.

Classification
PHP provides several cache systems :

PHP basically has two main types of caching: 'output caching' and 'parser caching'. PHP 'output caching' saves a chunk of data somewhere that can later be read by another script faster than it can generate it. 'Parser caching' is specific feature. PHP is a scripting language and code is not compiled or optimized to a particular computer. Every PHP file must be parsed and that takes time. This type of time minimization is 'parser caching'.

Include caching
Example:

File:class.test.php

File:program.php

output: Class loaded Hello world! Hello world!

Array caching
Example:

File:program.php

output: sum(0)=0 computed sum(1)=1 computed sum(2)=3 computed sum(3)=6 computed sum(3)=6 from cache sum(4)=10 computed

Session caching
Example:

file:program.php

output: computed My Name is Bill.

output after refresh: cached My Name is Bill.

Shared variables
Example:

file:program.php

output: $this->list[0]["info"]="small info nr 1" $this->list[0]["big"]="" $this->list[0]["info"]="small info nr 1" $this->list[0]["big"]="added big info, maybe structure of objects"

Output Caching
The server cache policy is included into, visible with (with option "I" for header):

Example:

title: PHP Programming/Caching


text:
Algorithms/Print version

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".

= Contents = If you have saved this file to your computer, click on a link in the contents to go to that section. = Introduction =
 * Chapter 1: Introduction
 * Chapter 2: Mathematical Background
 * Chapter 3: Divide and Conquer
 * Chapter 4: Randomization
 * Chapter 5: Backtracking
 * Chapter 6: Dynamic Programming
 * Chapter 7: Greedy Algorithms
 * Chapter 8: Hill Climbing
 * Appendix A: Ada Implementation
 * GNU Free Documentation License

= Mathematical Background =

= Divide and Conquer =

= Randomization =

= Backtracking =

= Dynamic Programming =

= Greedy Algorithms =

= Hill Climbing =

= Ada Implementation =

= GNU Free Documentation License =

title: Algorithms/Print version


text:
User:Jgruber

I am a mathematician by education with some years of research in algebra and currently software engineer by profession - although working on a degree in artificial intelligence.

title: User:Jgruber


text: Template:Chinese (Mandarin)TOC

title: Template:Chinese (Mandarin)TOC


text:
Chinese (Mandarin)/Lesson 6

= Lesson 6: What do you want to buy? 你想要買什麼?=

NOTE: It's also appropriate with close friends (ones who you would use "你" (nǐ) instead of "您" (nín) with) to greet with "哎" (aì), the closest equivalent in English being "Hey". This can precede or even take place of the traditional "你好" greeting, and partially serves as an attention-getter. However, if the pronunciation of "哎" (aì) is stretched/lengthened, it may sound as if you are complaining about something, which uses the same word.

Vocabulary

 * 嗨 / hài = hi
 * 去 / qù = go
 * 哪儿 （哪兒） / nǎr = where
 * 图书馆 (圖書館） / túshūguǎn = library
 * 再见 （再見 / zàijiàn = bye, goodbye (literally: see you again)

title: Chinese (Mandarin)/Lesson 6