text:
User talk:Jsnaree

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. – Mike.lifeguard  | talk 11:33, 9 September 2007 (UTC)

Image:Bookcover learning.jpg
The image description page says that this is your work, yet you appear to have reserved all rights. Images you upload must be licensed in a way that is GFDL-compatible, except for fair use. You must not upload your own work as fair use. Please change the licensing of the image to an acceptable copyleft license, or mark the image for deletion by adding to the top of the image description page. This applies to any of your past uploads which are marked as fair use. Thanks! – Mike.lifeguard  | talk 00:01, 19 November 2007 (UTC)

Image:Bookcover learning final.jpg
You're not allowed to claim fair use on your own work. Please use a free license, or ask for the image to be deleted. Thanks – Mike.lifeguard  | talk 17:50, 1 December 2007 (UTC)
 * Please do not upload this image again unless it is freely licensed. If you do so, the image will be protected; if you circumvent that, you may be blocked. You are not permitted to claim fair use on your own images. If you want clarification or further justification, ask on my talk page. – Mike.lifeguard  | talk 21:23, 12 December 2007 (UTC)
 * I have nominated this for deleting per policy. This image can be replaced by one which is freely licensed. – Mike.lifeguard  | talk 23:09, 12 April 2008 (UTC)

Naming policy
Please structure your latest contributions to comply with the above. Also, it'd be nice to not have a class section number in the book title, so that the book can be made to work for a general audience later on. Similar to what you did at The Practice of Learning Theories. I wonder if you'd consider expanding Instructional Technology instead. Otherwise maybe you could move the pages to Instructional Technologies or something similar. – Adrignola talk 02:05, 9 November 2010 (UTC)

 * I will be renaming the book when it appears that work has completed on it. – Adrignola talk 17:24, 16 November 2010 (UTC)

title: User talk:Jsnaree


text:
User talk:89.190.211.122

Thanks for experimenting with Wikibooks. Your test worked, and has now been removed. Please use Sandbox for any other tests you want to do, since testing material in modules will normally be removed quickly. Please see the welcome page if you would like to learn more about contributing to our project. Thanks. Urbane  (Talk)   (Contributions)  12:17, 9 September 2007 (UTC)

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

title: User talk:89.190.211.122


text:
Famous Theorems of Mathematics

Not all of mathematics deals with proofs, as mathematics involves a rich range of human experience, including ideas, problems, patterns, mistakes and corrections. However, proofs are a very big part of modern mathematics, and today, it is generally considered that whatever statement, remark, result etc. one uses in mathematics, it is considered meaningless until is accompanied by a rigorous mathematical proof. This book is intended to contain the proofs (or sketches of proofs) of many famous theorems in mathematics in no particular order. It should be used both as a learning resource, a good practice for acquiring the skill for writing your own proofs is to study the existing ones, and for general references.

It is not however intended as a companion to any other wikibook or wikipedia articles but can complement them by providing them with links to the proofs of the theorems they contain.

One note here. There are usually many ways to solve a problem. Many times the proof used comes down to the primary definitions of terms involved. We will follow the definition given by the first major contributor.

High school

 * /Pythagoras theorem/
 * /Euclid's proof of the infinitude of primes/
 * /√2 is irrational/
 * sin2Θ+cos2Θ=1

Undergraduate

 * /e is irrational/
 * /π is irrational/
 * /Fermat's little theorem/
 * /Fermat's theorem on sums of two squares/
 * /Sum of the reciprocals of the primes diverges/
 * /Bertrand's postulate/
 * /Law of large numbers/
 * /Spectral Theorem/
 * /L'Hôpital's rule/
 * /Four color theorem/
 * eπi+1=0
 * /Gaussian integral/
 * /Gamma function/
 * /Zeta function/

Postgraduate

 * /Fermat's last theorem/
 * /Brouwer fixed-point theorem/
 * /Prime number theorem/
 * /Riemann hypothesis/

Old table of contents
Proofs and definitions will be arranged according to the fields of mathematics:

 * /Algebra/
 * /Analysis/
 * /Applied Mathematics/
 * /Geometry/
 * /Logic/
 * /Number Theory/
 * /Set Theory/
 * /Boy's surface/

Manual of style

 * Proof style - Style guide for proofs.

External links etc

 * Proofs on the wikipedia project
 * List of mathematical proofs
 * List of theorems
 * Mathematical Handbook for Scientists and Engineers: Definitions, Theorems, and Formulas for Reference and Review
 * The Hundred Greatest Theorems
 * ProofWiki.org - The online compendium of mathematical proofs

Beweisarchiv

title: Famous Theorems of Mathematics


text:
Famous Theorems of Mathematics/Analysis

Analysis has its beginnings in the rigorous formulation of calculus. It is the branch of mathematics most explicitly concerned with the notion of a limit, whether the limit of a sequence or the limit of a function. It also includes the theories of differentiation, integration and measure, infinite series, and analytic functions. These theories are often studied in the context of real numbers, complex numbers, and real and complex functions. However, they can also be defined and studied in any space of mathematical objects that is equipped with a definition of "nearness" (a topological space) or more specifically "distance" (a metric space).

Proofs are arranged in the following sections:

 * /Metric Spaces/
 * /Real Analysis/
 * /Functional Analysis/
 * /Harmonic Analysis/
 * /Complex Analysis/
 * /Differential Geometry/
 * /Topology/
 * /p-adic Analysis/
 * /Non-standard Analysis/ or model theory
 * /Numerical Analysis/

Most of the standard proofs of analysis studied at the undergraduate level are in the metric spaces section. This is so because proofs of such results in real analysis, complex analysis and even in topology are similar to them.

title: Famous Theorems of Mathematics/Analysis


text:
Famous Theorems of Mathematics/Analysis/Metric Spaces

A metric space is a tuple (M,d) where M is a set and d is a metric on M, that is, a function

 * $$d : M \times M \rightarrow \mathbb{R}$$

such that

 * 1) d(x, y) ≥ 0     (non-negativity)
 * 2) d(x, y) = 0   if and only if   x = y     (identity of indiscernibles)
 * 3) d(x, y) = d(y, x)      (symmetry)
 * 4) d(x, z) ≤ d(x, y) + d(y, z)      (triangle inequality).

The function d is also called distance function or simply distance. Often d is omitted and one just writes M for a metric space if it is clear from the context what metric is used.

Basic definitions
Let X be a metric space. All points and sets are elements and subsets of X.

 * 1) A neighborhood of a point p is a set $$N_r(p)$$ consisting of all points q such that d(p,q) < r. The number r is called the radius of $$N_r(p)$$. If the metric space is $$R^k$$ (here the metric is assumed to be the Euclidean metric) then $$N_r(p)$$ is known as the open ball with center p and radius r. The closed ball is defined for d(p,q) $$\le$$ r.
 * 2) A point p is a limit point of the set E if every neighbourhood of p contains a point q$$\ne$$p such that q $$\in$$ E.
 * 3) If p $$\in$$ E and p is not a limit point of E then p is called an isolated point of E.
 * 4) E is closed if every limit point of E is a point of E.
 * 5) A point p is an interior point of E if there is a neighborhood N of p such that N $$\subset$$ E.
 * 6) E is open if every point of E is an interior point of E.
 * 7) E is perfect if E is closed and if every point of E is a limit point of E.
 * 8) E is bounded if there is a real number M and a point q $$\in$$ X such that d(p,q) < M for all p $$\in$$ E.
 * 9) E is dense in X every point of X is a limit point of E or a point of E (or both).

Basic proofs
1. Every neighborhood is an open set

 * Proof: Consider a neighborhood N = $$N_r(p)$$. Now if q $$\in$$ N then as d(p,q) < r we have h = r - d(p,q) > 0. Consider s $$\in$$ $$N_h(q)$$. Now d(p,s) $$\le$$ d(p,q) + d(q,s) < r - h + h = r, and so $$N_h(q)$$ $$\subset$$ N. Thus q is an interior point of N.

2. If p is a limit point of a set E, then every neighborhood of p contains infinitely many points of E

 * Proof: Suppose there is a neighborhood N of p which contains only a finite number of points of E. Let r be the minimum of the distances of these points from p. The minimum of a finite set of positive numbers is clearly positive so that r > 0. The neighborhood $$N_r(p)$$ contains no point q of E such that q $$\ne$$ p which contradicts the fact that p is a limit point of E.

3. A finite set has no limit points

 * Proof: This is obvious from the proof 2.

4. A set is open if and only if its complement is closed.

 * Proof: Suppose E is open and x is a limit point of $$E^c$$. We need to show that x $$\in E^c$$. Now every neighborhood of x contains a point of $$E^c$$ so that x is not an interior point of E. Since E is open it means x $$\notin$$ E and so x $$\in E^c$$. So $$E^c$$ is closed.

 * Now suppose $$E^c$$ is closed. Choose x $$\in$$ E. Then x $$\notin E^c$$, and so x is not a limit point of $$E^c$$. So there must be a neighborhood of x entirely inside E. So x is an interior point of E and so E is open.

5. A set is closed if and only if its complement is open.

 * Proof: This is obvious from the proof 4.


text:
User talk:Blaisorblade

Welcome message
Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. Urbane  (Talk)   (Contributions)  13:52, 9 September 2007 (UTC)

title: User talk:Blaisorblade


text:
User talk:Victuallers

See me on English wikipedia Welcome, Victuallers!

Come introduce yourself in the general reading room or your project in the project reading room. If you have any questions, you can ask in the assistance reading room or contact me personally. Victuallers (talk) 14:44, 29 August 2010 (UTC)

title: User talk:Victuallers


text:
Talk:Intermediate Algebra/Linear Equations

i have a math problem here the is asking me to find the satndard form of this problem: slope-2/3 and y-intercept 6 can anyone help me

 * One point formula is y-y1 = m(x-x1). Here m is the slope and (x1,y1) = (0,6). Just plug in the values and simplify. Cheers.--Shahab 18:04, 9 September 2007 (UTC)

Point Slope form
Should I put something about point-slope form here? It is used when you know one point on the line and the slope, and can be graphed directly from.


text:
User talk:72.5.131.62

Welcome to Wikibooks.

Your various experiments on the Muggles' Guide have been removed; thank you for your interest but be aware that such edits may be considered vandalism and may get this IP address blocked. If you wish to make constructive additions to the project, please feel free; but do please take a look at the project standards before editing.

Chazz (talk) 18:12, 9 September 2007 (UTC)

title: User talk:72.5.131.62


text:
Talk:Ada Programming/Types/array

This article says "Do not use Integer as the element type, since negative occurrences do not seem sensible." Doesn't it mean to say index range instead of element type?

 * Yes, I think so. But the sentence should be played down, in some cases it could make sense. ManuelGR 19:16, 10 September 2007 (UTC)

title: Talk:Ada Programming/Types/array


text: User talk:24.184.229.243

title: User talk:24.184.229.243


text:
User talk:Kamuali

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. – Mike.lifeguard  | talk 19:22, 9 September 2007 (UTC)

Image copyright problem with Image:Basis of WC.pdf
Thanks for uploading Image:Basis of WC.pdf. The Wikimedia Foundation is very careful about the files included in Wikibooks because of copyright law, and requires that we maintain a strict copyright policy. The file may soon be deleted unless we can determine the copyright holder and status.

The copyright holder is usually the creator, the creator's employer, or the last person who was transferred ownership rights. Copyright information is signified using copyright templates. The three basic license types on Wikibooks are open content, public domain, and fair use. Find the appropriate template in Image copyright tags and place it on the image page like this:.

Please signify the copyright information on any other images or files you have uploaded or will upload. Remember that images or files without this important information or giving false information can be deleted by an administrator. If you have any questions, feel free to contact me, or ask another Wikibookian at the help desk. Thank you.  – Mike.lifeguard  | talk 19:23, 9 September 2007 (UTC)

 * Actually, this is a clear copyright violation. There is a copyright notice on the first page. It will be deleted soon unless you provide satisfactory copyright information.  – Mike.lifeguard  | talk 19:30, 9 September 2007 (UTC)

title: User talk:Kamuali


text:
Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nc6/3. Bc4/3...Nf6/4. Ng5

= Two Knights Defence =

4. Ng5!?
This move is interesting. While some in the past considered it ridiculous, others point out that White wins a pawn in the process.

The White Knight now threatens a fork with Nxf7, yet to do so it's broken a rule of opening development in that the same piece moves twice; if Black plays correctly then White will seriously fall behind in development. Black's only sensible way to defend f7 is to block the bishop's access with 4...d5, but the pawn on d5 itself is not fully defensible by Black.

Black has two sensible replies.

 * /4...d5/ The best way for Black to defend is to play d5, blocking the bishop from the weak f7 square.
 * /4...Bc5/ Ignoring the threat, a risky option is the Traxler Attack. Black can try a bishop sacrifice on f2 if White plays Nxf7. Instead, White will often prefer Bxf7+.

Additionally, black may choose to move the knight on f6. This opens up an attack on the white g5 knight. There are two sensible methods of achieving this:

 * /4...Nxe4/.
 * /4...Nd5/.

Theory table
1.e4 e5 2.Nf3 Nc6 3.Bc4 Nf6 4.Ng5

Statistics
Estimated next move popularity d5 80%, Bc5 19%, Others less than 1%


text:
User talk:69.69.143.131

 – Mike.lifeguard  | talk 20:07, 9 September 2007 (UTC)

title: User talk:69.69.143.131


text:
User:LoneGunmen~enwikibooks

My Other Wikimedia User Pages

 * My WikiQuote Userpage -
 * My Wikipedia Userpage -
 * My WikiBooks Userpage -
 * My WikiNews Userpage -

Books "Borrowed" From The "Library"

Language
 * Dutch
 * Quechua

Social Sciences
 * US Criminal Law

Cookbook Recipes
 * Cookbook: Empanada

title: User:LoneGunmen~enwikibooks


text:
User talk:Damian Yerrick

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. – Mike.lifeguard  | talk 20:54, 9 September 2007 (UTC)

title: User talk:Damian Yerrick


text:
User talk:Zginder

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. – Mike.lifeguard  | talk 20:57, 9 September 2007 (UTC)

Welcome
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * If you are a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI (requests for importation) to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using Wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add this page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck!

title: User talk:Zginder


text:
User talk:Jezarnold

Interested in adding material that will help people pass Networking / Security / Digital Home technology certifications and also further advice as required. Any questions? --Jezarnold 21:05, 9 September 2007 (UTC)

title: User talk:Jezarnold


text:
Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nc6/3. Bb5/3...Nf6/4. O-O/4...Nxe4/5. d4/5...a6

= Ruy Lopez:Open Game =

White's threatened bishop has five options, but any retreat along the f1-a6 diagonal it travelled on move 3 constitutes a loss of tempo, while Bxc6 gives a bad Exchange Variation where the lack of a fixed centre makes Black's bishop pair a fearsome force. So White is more or less forced to transpose into the Open Variation with Ba4.

This is a good example of a move-order trick. Fans of the Open Variation can avoid a whole world of nonsense (Exchange Variation, Worrall Attack, 5. d3) by playing 3...Nf6 and transposing later.


text:
Cookbook:Japanese curry

Japanese curry sometimes referred to as "wafuu curry", although similar to curry from other countries has a different taste and texture from curries that hail from India or other South-East Asian countries. Usually a roux is used as a base to give Japanese curry its texture, which is notably thicker than other curries.

A manufactured "roux" popularized by S&B Foods of Japan simplify curry cooking at home by eliminating the need to make broth. The product is usually labeled as sauce mix or Japanese curry mix. Homemade curry recipes in Japan vary widely and frequently include ingredients like carrots, potatoes, onion, apple, and honey.

Curry houses in Japan usually serve curry made with chicken, beef or shrimp alongside plain white rice (カレーライス, karē raisu). Some accompaniments include fried egg, grilled sausage, toast, breaded pork chop (katsu-curry) and pickled onions.

title: Cookbook:Japanese curry


text:
Nineteen Eighty-Four

This is a study guide for the book Nineteen Eighty-Four by George Orwell. The book is now out of copyright in many nations since January 2021, so free versions may be available online.

Table of Contents

 * /Background Information/
 * /Part 1/
 * Chapter 1
 * Chapter 2
 * Chapter 3
 * Chapter 4
 * Chapter 5
 * Chapter 6
 * Chapter 7
 * Chapter 8

 * /Part 2/
 * Chapter 1
 * Chapter 2
 * Chapter 3
 * Chapter 4
 * Chapter 5
 * Chapter 6
 * Chapter 7
 * Chapter 8
 * Chapter 9

 * /Part 3/
 * Chapter 1
 * Chapter 2
 * Chapter 3
 * Chapter 4
 * Chapter 5
 * Chapter 6

 * /Characters/
 * /Setting/
 * /Themes, Motifs, and Symbols/
 * /Important Terms/
 * /Quiz/
 * /Essay Questions/

title: Nineteen Eighty-Four


text:
Radiation Oncology/Medical Statistics

 * Random Variables
 * Distribution
 * Fisher's Exact Text (2x2)
 * Chi-squared Test (Χ2)

Information adapted in part from Using and Understanding Medical Statistics, Matthews DE and Farewell VT, Karger 2007

title: Radiation Oncology/Medical Statistics


text:
Nineteen Eighty-Four/Background Information

1984 was written by George Orwell in the 1940's after World War II. It is a dystopian novel depicting a so-called socialist government in Great Britain in the year 1984. In reality, the government is totalitarian, and controls everything from the economy to language.

Orwell is also known for the satirical novel Animal Farm.

Love is an important theme in the work. Love for a partner, love for a totalitarian regime, love for oneself and one's country and love in general, etc etc. The book ends on a note about love. You will see why if you carefully consider this theme throughout the work.

see also: Doublespeak which is an important defining feature of this work that crefully influenced other works. see also: Doublethink and Newsspeak herein noted and appended.


text:
Talk:Introduction to Chemical Engineering Processes

Translation
I'm starting a translation of this wikibook to Portuguese. Eventually I may feel tempted to add new stuff or improve this English language version, but never without discussing it with its previous authors or other experts first, so I'll appreciate if someone keep an eye in this discussion table.

Gabriel dCF, 09/09/2007

 * Hi Gabriel, please feel free to make any improvements you feel need to be made. I've made most of the edits to this book but am always hoping that what is here can be improved by others. I'd hardly call myself an expert, but I hope that what has been written so far is accurate. Regards. Mattb112885 (talk to me) 00:18, 10 September 2007 (UTC)

Matlab and Excel
Hi everyone! Matlab is propietary software and not very usefull for personal purpouses unless you take it from non-legal sources. I suggest to include in the table of contents only open-source software as OpenOffice and Octave. Thanks,--Lupus (talk) 02:23, 20 April 2008 (UTC)
 * Hi Lupus, the original intent is to include software that someone would likely use in a business or academic environment and as much as I am a proponent of open source, it is still true that MATLAB and Excel are more common in industry (and in academia) than open office or Excel. I have nothing against including some things specific to free software (if you would like to make a note of this I would not object at all) but it does not make sense to me to exclude anything that's not, especially since the proprietary stuff is more commonly used. Mattb112885 (talk to me) 04:21, 20 April 2008 (UTC)
 * Hi Mattb112885, I'll try this in the book that we're composing in spanish. In part you're right with Matlab, but maybe in the case of Excel the similarities are nearby and it will be more 'open' to introduce them all as "calulous spreadsheets" (or something like it, I guess you have a word for what in spanish is "hojas de cálculo"). Thanks a lot, and great job, Matt! --Lupus (talk) 12:03, 20 April 2008 (UTC)
 * I agree, I think we can just call them "spreadsheets" and then make a note like (such as Excel, GNUmeric, OpenOffice Calc, etc.) further down the page to let them know that yes it was written for Excel (since that's the most common and it's the one I know best at least, though if someone else knows more about another one's eccentricities they're welcomed to write some stuff about them too) but should be usable with other applications. I'll do this as I have more time, I'm just passing by atm. Do you have a link to the spanish page? I'd be interested in taking a look at it (I do not read or write spanish but that's what google's translator is for!). Regards. Mattb112885 (talk to me) 16:20, 20 April 2008 (UTC)
 * Of course,it's right here. You'll see that is still in the initial phase, I'm too busy now but it's in my plans to finish it. Regards,--Lupus (talk) 16:54, 20 April 2008 (UTC)


text:
Talk:Physics with Calculus/Mechanics/Fluid Mechanics

What is fluid mechanics doing in this section? I propose moving it to the very end because the equations of fluid mechanics are more difficult than the equations of electrodynamics.

Hey guys just to point out... there are a few attempts to develop fluid mechanics, we should unite ?


text:
Nineteen Eighty-Four/Part 1/Chapter 1

In the first chapter we are introduced to the world of Winston Smith, an ../../Outer Party/ worker in Oceania. The quality of his life is meager, and he is secretly dissatisfied with Big Brother. He buys a diary from a ../../Proletariat/ shop and starts writing in it. This action is considered a "../../Thoughtcrime/", and those accused of it are never seen again. Nobody knows what happens to them. During ../../Two Minutes Hate/, a traitor to the party known as Emmanuel Goldstein appears on the telescreen, and is subject to the hatred of the government workers. For some reason, an ../../Inner Party/ member, O'Brien, catches his eye as someone who's "political orthodoxy was not perfect." Meanwhile, Winston subconsciously writes "DOWN WITH BIG BROTHER" in his diary, and despairs because the ../../Thought Police/ would find out and punish him.

title: Nineteen Eighty-Four/Part 1/Chapter 1


text:
User talk:Gabriel dCF

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.

Also, I saw your message on the talk page to Introduction to Chemical Engineering Processes, I would say that you can make any improvements you want to the book (I've made most of the edits to that book so far), since that's what the wiki is for after all! I'm glad to see someone has found interest in it, and wish you luck in your translation. Unfortunately I don't know a word of Portuguese but I hope the end result is useful to speakers of that language as well. Regards. Mattb112885 (talk to me) 00:21, 10 September 2007 (UTC)

_
Thanks a bunch, Matt! It'll be very nice to discuss with you how can we improve this book. Guess I'll have a piece of talk with the responsibles for the translation os the Spanish language version too, see if we can cooperate.

Best regards, Gabriel dCF 01:16, 10 September 2007 (UTC)

title: User talk:Gabriel dCF


text:
Physics with Calculus/Thermodynamics/Pressure and Temperature

In its most basic and most conceptual form, pressure is force per unit area. Of course, we all have a basic intuition about what pressure is. However, it's a little more slippery to define rigorously because we could in principle have a different pressure at every point, then it's not really force per unit area on a macroscopic scale. Furthermore, what force and what area are we even talking about?

What we really mean is that if we draw a small closed surface (like a sphere) around some point in a fluid, then the pressure is the outward force from the fluid inside the surface divided by the area or the surface. Of course, the surface must be orientable (you can't draw a Klein bottle around it), but more importantly, as the surface you draw gets smaller (say you choose a sphere, then shrink the radius), the pressure calculated must get closer to a definite value. Of course, these are all mathematical subtleties, and there are many more, all of which may be ignored.

One thing you should realize is that for any given surface, the total force on it is the surface integral of the pressure. Equivalently, for a small surface (infinitesimal), the force is merely the pressure times the area.

Notice also that pressure cannot produce a shear force, only a normal force.

Now, imagine a small rectangular prism of fluid of dimensions dx, dy, dz. Let's look at the two opposite sides normal to the x axis, let's call them A, and A'. Now, we want to find out the total force on this cube from the fluid surrounding it. The total force in the x direction is the force on A' minus the force on A. The force on A is the pressure at A times the surface area, let's call it dy dz, so P(x) dy dz. The force on A' is not quite the same; if we take the linear approximation, which becomes exact as dx, dy, and dz become smaller, then it is

$$ P(x)\, dy\, dz + \frac{\partial P}{\partial x}\, dx\, dy\, dz$$. All the higher order terms can be neglected because when they are divided by dx dy dz, they will become zero.

The force in the x direction is then

$$\frac{\partial P}{\partial x}\, dx\, dy\, dz$$.

Repeating the process for the other faces gives us

$$ d\vec{F} = \left(\frac{\partial P}{\partial x}, \frac{\partial P}{\partial y}, \frac{\partial P}{\partial z}\right)\, dV$$

Dividing through by dV (strictly speaking, we should be using delta's instead of d's, but you get the same result), and changing notation, we get

$$ \vec{F} = \nabla P$$

where $$\vec{F}$$ is force density.


text: Wikijunior:World at Work/Barista

title: Wikijunior:World at Work/Barista


text:
Wikijunior:World at Work/Wood gatherer

fr:Wikijunior:Le monde au travail/Garde forestier

title: Wikijunior:World at Work/Wood gatherer


text:
New Zealand History

A Concise New Zealand History

Chapters

 * Preface
 * Introduction

PART 1: EARLY HISTORY:
 * Polynesian Settlement of New Zealand (1300)
 * Maori Culture and Lifestyle up to 1840 (1300-1840)

PART 2: EUROPEAN EXPLORATION AND SETTLEMENT:

 * First European Explorers to Discover New Zealand (1642-1800)
 * A New Economy Introduced to New Zealand (1791-1840)
 * Missionaries Dispatched to New Zealand (1814)
 * The Treaty of Waitangi (1840)
 * European Colonisation of New Zealand (1800s)
 * The New Zealand Wars (1843-1872)
 * Railways Introduced to New Zealand (1863-1873)
 * The Colonial Government

PART 3: NEW ZEALAND IN THE TWENTIETH CENTURY:

 * The Dawn of the Twentieth Century (1900-1914)
 * New Zealand's Involvement in World War I (1914-1918)
 * New Zealand in the Great Depression (1930s)
 * New Zealand in World War II (1939-1945)
 * Mid to Late Twentieth Century (1945-1999)
 * Famous New Zealanders in the Twentieth Century
 * Politics in the Twentieth Century

PART 4: NEW ZEALAND'S RECENT HISTORY:

 * New Zealand's Recent History (2000-2007)
 * New Zealand Prime Ministers at the Start of the Twenty First Century (1999-2008)
 * New Zealand Government at the Turn of the Twenty First Century (2000-2008)
 * New Zealand History/New Zealand During the COVID 19 Pandemic and the 2020 Recession (2019-?)

END NOTES:

 * Bibliography
 * Authors and Contributors
 * Print version
 * [//upload.wikimedia.org/wikipedia/commons/0/06/New_Zealand_History.pdf PDF version]

title: New Zealand History


text:
New Zealand History/Preface

Intention of this book
The intention of this book is to provide an open-content, concise textbook on New Zealand history that is easy for anyone who is interested to read.

A Note to Authors
This book is a work in progress, so feel free to contribute to it in places you see as unfinished or lacking information.

The only major guidelines that authors of this project should follow, are to use New Zealand (British) spelling, follow the Wikibooks rules on unbiased writing, and keep the chapters fairly short and concise. Also, when distinguishing dates, use BC and AD. Otherwise, what authors choose to put in, as long as it is relevant and factual, is up to them.

Continue to the Introduction ›

title: New Zealand History/Preface


text:
Cookbook:Ropa Vieja (Caribbean Shredded Beef)

Ropa vieja, which is Spanish for "old clothes," is a popular Caribbean dish consisting of shredded beef (often skirt or flank steak), vegetables, and a sauce.

The origin of ropa vieja is from the Canary Islands, which are Spanish islands off the coast of North Africa in the Atlantic Ocean. The original version of Ropa Vieja contained leftovers, but later became a shredded meat dish with garbanzo beans and potatoes in the Canary Islands. Some versions in the Canary Islands contain beef or chicken or pork, or a combination of any of the three. Ropa vieja is widely prepared in the Caribbean today. Ropa vieja is listed among traditional Panamanian cuisine, Cuban cuisine, Puerto Rican cuisine, Dominican cuisine and Canarian cuisine.

Below is a typical Cuban recipe, which does not include garbanzo beans.

Ingredients

 * 1 kg boiled beef (preferably flank steak, but any meat with long threads will do)
 * ⅓ cup olive oil
 * 1 onion
 * 3 garlic cloves
 * 1 green bell pepper
 * 1 red bell pepper
 * 1½ cup tomato sauce
 * 1 tsp salt
 * 1 bay leaf
 * 1 cup red cooking wine or beer

Procedure

 * 1) Cut the meat in pieces, not too small, not too big. Using a pressure cooker, boil the meat for about 15 minutes. Add a teaspoon of olive oil to the water to avoid foaming; also, add a teaspoon of salt. After boiling the meat, save 1 cup of the broth.
 * 2) Shred the meat in thin strips using a fork. Chop the onion, cut the peppers in thin strips and mince the garlic cloves.
 * 3) Sauté the garlic and the onion for a bit in hot oil, then add the peppers, sauté a bit more. Add the meat and the rest of the ingredients, including the cup of broth.
 * 4) Cook the mix over low heat for 20–30 minutes. Stir a few times. Season to taste.

Notes, tips, and variations

 * You can also add a hint of red wine to spice it up.


text:
New Zealand History/Introduction

‹ Back to the Preface

Introduction to A Concise New Zealand History
This is a concise textbook on New Zealand history, designed so it can be read by virtually anyone wanting to find out more about New Zealand history.

The textbook covers the time span of human settlement in New Zealand. It includes:
 * The discovery and colonisation of New Zealand by Polynesians.
 * Maori culture up to the year 1840.
 * Discovery of New Zealand by Europeans.
 * Early New Zealand economy and Missionaries in New Zealand.
 * The Treaty of Waitangi.
 * European colonisation, and conflict with the Maori people.
 * Colonial, Twentieth Century and Modern Government.
 * Important events in the twentieth century and recent times.

Find out how events in New Zealand's humble beginnings have shaped the way the country is in the present day.

Forward to Polynesian Settlement of New Zealand ›

title: New Zealand History/Introduction


text:
New Zealand History/Authors

‹ Back to the Bibliography

Authors

 * Original Author: Helpfulstuffnz
 * Additions by: Ferrum Dominus

title: New Zealand History/Authors


text:
XQuery/XQuery from SQL

The Scott/Tiger example
A classic database widely used in teaching Relational databases concerns Employees, Departments and SalaryGrades. In Oracle training material it is known by the demo username and password, Scott/Tiger.

These three tables converted to XML (via the XML add-in to Excel  XQuery/Excel and XML ) are:

Employees XML Table MySQL

Departments XML Table MySQL

Salary Grades XML Table MySQL

A port of the Oracle SQL file to MySQL can be found here.

Execution environments
The eXist demo server is used for the XQuery examples. These are returned either as plain XML or converted to table format.

The equivalent SQL queries are executed on an MySQL server,also based at the University of the West of England in Bristol

Task: How many Employees?
SQL: select count(*) from Emp; MySQL

XQuery: count(//Emp) XML

Task: How many Departments?
SQL: select count(*) from dept  MySQL

XQuery: count(//Dept) XML

Task: Show all Employees with a salary greater than 1000
SQL: select * from emp where sal > 1000; MySQL

XQuery: //Emp[Sal>1000] XML Table

Task: Show all Employees with a salary greater than 1000 and less than 2000
SQL: select * from emp where sal between 1000 and 2000; MySQL

XQuery: //Emp[Sal>1000][Sal<2000] XML Table

Here, successive filter conditions replace the anded conditions implied by 'between'.

Although there is no 'between' function in XQuery, it is a simple matter to write one:

declare function local:between($value as xs:decimal, $min as xs:decimal, $max as xs:decimal) as xs:boolean { $value >= $min and $value <= $max };

which simplifies the query to //Emp[local:between(Sal,1000,2000)] XML Table

and has the advantage that the conversion of Sal to a number is now implicit in the function signature.

Task: Show all employees with no Commission
SQL: select * from emp where comm is null; MySQL

XQuery: //Emp[empty(Comm/text)] XML Table

Note that empty(Comm) is not enough, since this is true only if the element itself is absent, which in this sample XML it is not.

XQuery: //Emp[empty(Comm)] XML

Task: Select the first 5 employees
SQL: select * from emp limit 5; MySQL

XQuery: //Emp[position <=5]

XML Table

List Employee names and salaries
SQL: Select ename,sal from emp MySQL

Surprisingly, selecting only a subset of children in a node (pruning) is not supported in XPath.

//Emp/(Ename,Sal) XML retrieves the required elements, but the parent Emp nodes have been lost.

//Emp/(Ename|Sal) XML is better since it keeps the elements in sequence, but it does not return Emp nodes with only the Ename and Sal children as required.

//Emp/*[name(.) = ("Ename","Sal")] XML uses reflection on the element names.

XQuery: for $emp in //Emp return  {$emp/(Ename|Sal)}

XML Table

Here an XQuery FLWOR expression is used to create a new EMP element from the original elements.

Computing the Annual Salary
Task: Compute the Annual Salaries of all employees. The Annual Salary is computed from 12 times the Monthly salary plus Commission. Since commission may be null, it must be replaced by a suitable numeric value:

SQL: select 12 * sal + ifnull(comm,0) from emp; MySQL

XQuery: //Emp/(12*number(Sal)+(if(exists(Comm/text)) then number(Comm) else 0)) XML

The SQL function COALESCE is the same as IFNULL but will accept multiple arguments:

SQL: select 12 * sal + coalesce(comm,0) from emp; MySQL

XQuery: //Emp/(12*number(Sal)+ number((Comm/text,0)[1])) XML

The lack of a schema in this simple example to carry information on the type of the items, leads to the need for explicit conversion of strings to numbers.

Note the XQuery idiom: (Comm/text,0)[1]

computes the first non-null item in the sequence, the counterpart of COALESCE.

Selecting and Creating Columns
Task: List the employee names with their Annual Salary.

SQL: select ename, 12 * sal + ifnull(comm,0) as "Annual Salary" from emp; MySQL

XQuery: for $emp in //Emp return  {$emp/Ename}  {12*number($emp/Sal)+ (if (exists($emp/Comm/text))             then number($emp/Comm)             else 0) }

XML Table

Again we have the problem of tree-pruning, but now with added grafting, which again requires the explicit construction of an XML node.

IN
Task: Show all employees whose Job is either ANALYST or MANAGER

SQL: select * from emp where job in ("ANALYST","MANAGER") MySQL

XQuery: //Emp[Job = ("ANALYST","MANAGER")] XML Table

NOT IN
Task :Select all employees whose Job is not 'ANALYST' or 'MANAGER'

SQL: select * from emp where job not in ("ANALYST","MANAGER")  MySQL

This doesn't work:

XQuery: //Emp[Job !=("ANALYST","MANAGER")] XML Table

The generalised equals here is always true since everyone is either not an ANALYST or not a MANAGER. This works:

XQuery: //Emp[not(Job =("ANALYST","MANAGER"))] XML Table

Distinct values
Task: Show the different Jobs which Employees have MySQL: select distinct job from emp;     MySQL

XQuery: distinct-values(//Emp/Job) XML

Pattern Matching
Task: List all Employees with names starting with "S"

MySQL: select * from emp where ename like "S%"; MySQL

XQuery: //Emp[starts-with(Ename,"S")] XML Table

See starts-with

Task: List all Employees whose name contains "AR"

MySQL: select * from emp where ename like "%AR%"; MySQL

XQuery: //Emp[contains(Ename,"AR")] XML Table

See contains

Task: List all Employees whose name contains "ar" ignoring the case

MySQL: select * from emp where ename like "%ar%"; MySQL

LIKE in SQL is case insensitive, but fn:contains is not, so the case needs to be converted:

XQuery: //Emp[contains(upper-case(Ename),upper-case("ar"))] XML Table

See upper-case

More complex patterns need regular expressions.

MySQL: select * from emp where ename regexp "M.*R"; MySQL

XQuery: //Emp[matches(Ename,"M.*R")] XML Table

See matches

Similarly, SQL's REGEXP is case-insensitive, whereas additional flags control matching in the XQuery matches

MySQL: select * from emp where ename regexp "m.*r"; MySQL

XQuery: //Emp[matches(Ename,"m.*r",'i')] XML Table

('i' makes the regex match case insensitive.)

Simple Inner joins
Task: Find the name of the department that employee 'SMITH' works in:

SQL :  MySQL

XPath :

XML

Perhaps a FLWOR expression in XQuery would be more readable:

let $dept := //Emp[Ename='SMITH']/DeptNo return //Dept[DeptNo = $dept ]/Dname

XML

Task: To find the names of all employees in Accounting

SQL: MySQL

XPath:

XML

XQuery:

let $dept := //Dept[Dname='Accounting']/DeptNo return //Emp[DeptNo = $dept]/Ename

XML

Note that in this release of eXist, the order of the operands in the equality is significant - to be fixed in a later release.

XQuery:

XML

More complex Inner Join
Task: List the name of each Employee, together with the name and location of their department.

SQL:

select ename, dname,location from emp, dept where emp.deptno = dept.deptno;

MySQL

Where elements must be selected from several nodes, XPath is insufficient and XQuery is needed:

XQuery:

This join could be written as:

for $emp in //Emp for $dept in //Dept where $dept/DeptNo= $emp/DeptNo return  {$emp/Ename} {$dept/(Dname|Location)}

XML Table

But it would be more commonly written in the form of a sub-selection:

for $emp in //Emp let $dept := //Dept[DeptNo=$emp/DeptNo] return  {$emp/Ename} {$dept/(Dname|Location)}

XML Table

Inner Join with Selection
Task: List the names and department of all Analysts

SQL:

select ename, dname from emp, dept where emp.deptno = dept.deptno and job="ANALYST";

MySQL

XQuery:

for $emp in //Emp[Job='ANALYST'] let $dept := //Dept[DeptNo= $emp/DeptNo] return  {$emp/Ename} {$dept/Dname}

XML Table

1 to Many query
Task: List the departments and the number of employees in each department

SQL:

select dname, (select count(*)           from emp           where deptno = dept.deptno         ) as headcount from dept;

MySQL

XQuery:

for $dept in //Dept let $headCount := count(//Emp[DeptNo=$dept/DeptNo]) return  {$dept/Dname} {$headCount}

XML Table

Theta (Inequality) Join
Task: List the names and salary grade of staff in ascending grade order

Grades are defined by a minimum and maximum salary.

SQL:

select ename, grade from emp, salgrade where emp.sal between salgrade.losal and salgrade.hisal;

MySQL

XQuery:

for $emp in //Emp let $grade := //SalGrade[number($emp/Sal) > number(LoSal)][number($emp/Sal) < number(HiSal)]/Grade order by $grade return <Emp> {$emp/Ename} {$grade} </Emp>

XML Table

Recursive Relations
The relationship between an employee and their manager is a recursive relationship.

Task: List the name of each employee together with the name of their manager.

SQL:

select e.ename, m.ename from emp e join emp m on e.mgr = m.empno

MySQL

XQuery:

for $emp in //Emp let $manager := //Emp[EmpNo = $emp/MgrNo] return <Emp> {$emp/Ename} <Manager>{string($manager/Ename)}</Manager> </Emp>

XML Table

The XQuery result is not quite the same as the SQL result. King, who has no manager, is missing from the SQL inner join. To produce the same result in XQuery, we would filter for employees with Managers:

for $emp in //Emp[MgrNo] let $manager := //Emp[EmpNo = $emp/MgrNo] where $emp/MgrNo/text return <Emp> {$emp/Ename} <Manager>{string($manager/Ename)}</Manager> </Emp>

XML Table

Alternatively, an outer join returns all employees, including King:

SQL:

select e.ename, m.ename from emp e left join emp m on e.mgr = m.empno

MySQL

Conversion to an organisational tree
The manager relationship defines a tree structure, with King at the root, her direct reports as her children and so on. A recursive function in XQuery solves this task.

XQuery: declare function local:hierarchy($emp) { <Emp name='{$emp/Ename}'> <Reports> {for $e in //Emp[MgrNo = $emp/EmpNo] return local:hierarchy($e) }      </Reports> </Emp> }; local:hierarchy(//Emp[empty(MgrNo/text)])

XML

Conversion to a Department/Employee Hierarchy
For export, a single XML file could be created with Employees nested within Departments. This is possible without introducing redundancy or loss of data because the Dept/Emp relationship is exactly one to many.

XQuery: <Company> {for $dept in //Dept return <Department> {$dept/*} {for $emp in //Emp[DeptNo = $dept/DeptNo] return $emp }   </Department> } </Company> XML

With this simple approach, the foreign key DeptNo in Emp has been included but it is now redundant. The except operator is useful here:

<Company> {for $dept in //Dept return <Department> {$dept/*} {for $emp in //Emp[DeptNo = $dept/DeptNo] return <Employee> {$emp/* except $emp/DeptNo} </Employee> }      </Department> } </Company>

XML

Note that this assumes there are no attributes to be copied. If there are, these would be copied with

Working with the hierarchical data
This hierarchical data can be queried directly in XQuery.

Path to Employee
Almost all the queries remain the same (except for the change of element name to Employee). This is because the path used to select Emps in the Emp.xml document is   and is now   in the merged document. If a full path had been used, this would need to be replaced by

Simple Navigation
Task: To find the department name of employee 'Smith'

XQuery:    XML

Task: To find the names of employees in the Accounting department

XQuery:    XML

Department /Employee Join
The main changes are in queries which require a join between Employee and Departments because they are already nested and thus become navigation up (from Employee to Department ) or down (from Department to Employee) the tree.

many - one
The query to list the Employees and the location of their Department with separate documents was:

for $emp in //Emp for $dept in //Dept where $dept/DeptNo=$emp/DeptNo return <Emp> {$emp/Ename} {$dept/(Dname|Location)} </Emp>

XML Table

With one nested document, this becomes:

for $emp in //Employee return <Employee> {$emp/Ename} {$emp/../Location} </Employee> XML Table using the parent access to move up the tree.

1 - many
To list departments and the number of employees in the separate tables is :

for $dept in //Dept let $headCount := count(//Emp[DeptNo=$dept/DeptNo]) return <Dept> {$dept/Dname} <HeadCount>{$headCount}</HeadCount> </Dept>

XML Table

which becomes:

for $dept in //Department let $headCount := count($dept/Employee) return <Department> {$dept/Dname} <HeadCount>{$headCount}</HeadCount> </Department>

XML Table

Summary data
Task: Show the number, average (rounded), min and max salaries for Managers.

SQL: SELECT count(*), round(avg(sal)), min(sal), max(sal) FROM emp WHERE job='MANAGER'; MySQL

XQuery:

(count(//Emp[Job='MANAGER']),round(avg(//Emp[Job='MANAGER']/Sal)),min(//Emp[Job='MANAGER']/Sal),max( //Emp[Job='MANAGER']/Sal))

XML

Better to factor out the XPath expression for the subset of employess:

let $managers := //Emp[Job='MANAGER'] return (count($managers),round(avg($managers/Sal)),min($managers/Sal),max($managers/Sal))

XML

It would be better to tag the individual values computed: let $managers := //Emp[Job='MANAGER'] return <Statistics> <Count>{count($managers)}</Count> <Average>{round(avg($managers/Sal))}</Average> <Min>{min($managers/Sal)}</Min> <Max>{max($managers/Sal)}</Max> </Statistics>

XML

Grouping
Task: Show the number, average (rounded), min and max salaries for each Job.

SQL: SELECT job, count(*), round(avg(sal)), min(sal), max(sal) FROM emp GROUP BY job; MySQL

In XQuery, grouping must be done by iterating over the groups. Each Group is identified by the Job and we can get the set (sequence) of all Jobs using the distinct-values function:

for $job in distinct-values(//Emp/Job) let $employees := //Emp[Job=$job] return <Statistics> <Job>{$job}</Job> <Count>{count($employees )}</Count> <Average>{round(avg($employees/Sal))}</Average> <Min>{min($employees/Sal)}</Min> <Max>{max($employees/Sal)}</Max> </Statistics>

XML Table

Hierarchical report
Task: List the departments, their employee names and salaries and the total salary in each department

This must generate a nested table.

SQL: ?

XQuery:

<Report> { for $dept in //Dept let $subtotal := sum(//Emp[DeptNo = $dept/DeptNo]/Sal) return <Department> {$dept/Dname} {for $emp in //Emp[DeptNo = $dept/DeptNo] return <Emp> {$emp/Ename} {$emp/Sal} </Emp> }        <SubTotal>{$subtotal}</SubTotal> </Department> }  <Total>{sum(//Emp/Sal)}</Total> </Report>

XML

Note that the functional nature of the XQuery language means that each total must be calculated explicitly, not rolled up incrementally as might be done in an imperative language. This has the advantage that the formulae are explicit and independent and can thus be placed anywhere in the report, such as at the beginning instead of at the end:

<Report> <Total>{sum(//Emp/Sal)}</Total> { for $dept in //Dept let $subtotal := sum(//Emp[DeptNo = $dept/DeptNo]/Sal) return <Department> <SubTotal>{$subtotal}</SubTotal> {$dept/Dname} {for $emp in //Emp[DeptNo = $dept/DeptNo] return <Emp> {$emp/Ename} {$emp/Sal} </Emp> }     </Department> } </Report>

XML

Restricted Groups
Task: Show the number, average (rounded), min and max salaries for each Job where there are at least 2 employees in the group.

SQL:

SELECT job, count(*), round(avg(sal)), min(sal), max(sal) FROM emp GROUP BY job HAVING count(*) > 1;

MySQL

XQuery:

for $job in distinct-values(//Emp/Job) let $employees := //Emp[Job=$job] where count($employees) > 1 return <Statistics> <Job>{$job}</Job> <Count>{count($employees )}</Count> <Average>{round(avg($employees /Sal))}</Average> <Min>{min($employees /Sal)}</Min> <Max>{max($employees /Sal)}</Max> </Statistics> XML Table

Selecting by Date
Task: list all employees hired in the current millenium

SQL: SELECT * from job where hiredate >= '2000-01-01' MySQL

XQuery: //Emp[HireDate >= '2000-01-01']

Actually this comparison is a string comparison because of the lack of a schema to define HireDate as an xs:date.

XML Table

title: XQuery/XQuery from SQL


text:
New Zealand History/European Explorers

‹ Back to Maori Culture and Lifestyle up to 1840

Abel Tasman
Abel Tasman, a Dutch explorer, was one of the first Europeans to discover New Zealand on the 13th of December 1642, in his search for the Great Southern Continent. Tasman noted in his journal that it was a large land, uplifted high (the area he sighted was near the Southern Alps). He called New Zealand 'Staten Landt' which refers to the 'Land of the (Dutch) States-General'.

The first encounter Tasman had with the Maori was on the 18th of December in Taitapu Bay (now Golden Bay), when two canoes from the shore approached Tasman's ship. Communication was not possible, as the Dutch and the Maori couldn't understand each other's languages.

Later, more canoes approached the ship, so the Dutch sent out a boat to tempt the Maori to come on board. One of the canoes rammed the small Dutch boat, killing some sailors. The Dutch, in turn, fired at the Maori when more canoes approached, causing the Maori to retreat to shore rapidly.

After this, Tasman travelled to the tip of the North Island before leaving New Zealand waters.

James Cook
British explorer, James Cook, captain of the Endeavour entered New Zealand waters on the 6th of October 1769, and laid anchor at today's Poverty Bay. When Cook saw smoke, he realised the land was inhabited, he and a group of sailors headed to shore, in the hope of befriending the natives and taking on board refreshments. The Maori were hostile, however, and the British had to fire on the Maori in self-defence.

Cook attempted trade with Maori again at a different location, but with no success. He managed to sketch 2400 miles of coastline on the journey and proved New Zealand was not part of a major continent. He returned to New Zealand another two times in the 18th Century.

Jean-Francois-Marie de Surville
Jean Francois Marie De Surville, was a captain of the French East India Company ship, Saint Jean Baptiste. He entered New Zealand Waters on the 12th of December 1769, 11:15am, off the Coast of Hokianga. On 16th of December, the French Ship rounded North Cape. Captain James Cook and Captain Jean propably passed within 20 to 25Km from each other. One Day later, on the 17th, Jean discovered what he called 'Lauriston Bay', Unbeknown to him, Captain James Cook had already named it 'Doubtless Bay'. From the 18th to the 31st of December, Jean anchored off North of Doubtless Bay. At that point, Maori Waka rowed out to him, and begun the first acts of Trade in New Zealand.

However, peacefully relations between the Maori and the French didn't last. Two days later, Jean perceived that the Maori were stealing a Boat which had drifted ashore. In retaliation, Jean Burned down various Huts, food stores, nets and Canoes. Soon after, he took prisoner of the Ngati Kahu leader, Ranginui. Unfortunately, Ranginui died out at sea, on the 24th of March 1770.

Jean Francois Marie De Surville Confirmed the Non-existence of Davis Land otherwise known as Terra Australias. This mythical Southern continent was hypothesised to 'Balance' the earth. Forward to A New Economy Introduced to New Zealand ›

title: New Zealand History/European Explorers


text:
User talk:125.31.28.124

Hi, thanks for editing the kapampangan wikibook I really appreciate any help.

Your addition of the word "ra", requires some explanations. In this learning method, we are trying to never use a wrod unless the word has been explaned beforehand.

Could you explain the meaning of "ra", and why it is required?

Thanks a lot --Lgriot 08:45, 10 September 2007 (UTC)

title: User talk:125.31.28.124


text:
Editing Wikitext/Tables

Tables allow us to structure data on a screen into neat rows and columns. This is useful in many situations. In fact, many other box-like structures on web pages use tables as their basis.

Wikitext tables are based closely on HTML tables. If you are familiar with HTML, you may be happy to learn that you can use HTML tables in Wiki pages. However, the wiki markup code, as it is called, uses fewer characters and does not use closing tags. Wikitext tables are quite basic in their simplest form, but like their HTML equivalents, they can be formatted to an enormous extent by the addition of HTML attributes and CSS styles. This page explains how to make tables.

For those who just need a quick Wikitext or HTML table that they can modify for their work, refer to ../Tables Ready to Use/.

Basic layout
Here is a basic table example:

Wikitext Table Symbols

 * Outer curly bracket-and-pipe symbols denote a table.
 * Pipe-and-hyphen symbols denote a new row.
 * Pipe symbols on their own denote a data cell.
 * Exclamation marks denote heading cells.
 * Pipe-and-plus symbols denote a table caption.

Notice that the table has been given standard borders and formatting by using ; without this, tables are less clearly formatted. Properties defined elsewhere, in a Wiki style sheet in fact, have centered the heading cells and made them bold. The same default conditions have made the table's background color white, the text black, and placed its caption at the top.

Notice also that the columns of the basic table expand to accommodate the widest text. If some table cells are to be left blank then columns might become very narrow. Users often place special hidden characters into cells to expand such columns. The character used is the non-breaking space, &nbsp;, so called because its original intention was to keep any two words together that are linked by it.

These simple tables do not have any margins around them to space them from other text. To make sure that they do not get mixed up with these other parts of the page they can be preceded and followed with the code   The template clear often exists to do the same thing with less markup. This makes sure that both the table and any text that follows it start on new lines of their own. Tables can also include margin styles that perform this spacing.

This simple table code, or any other used in the examples can be can be copied and pasted into the Sandbox or into other pages for testing and extension. To extend such a table, just add more rows and data cells.

Alternative Layout
There are two other table layouts that work in Wiki pages; both make identical tables to the basic one shown above. The first listing is fairly similar but writes the cell code for a row in one single line. Note that there is a double pipe symbol used for a cell separator:  When heading cells are arranged in this way, double exclamations are used instead of double pipes.

The second listing is the HTML equivalent of a wikitext table, and is sometimes easier to use when such a table is to be displayed by a template. It is a fact that the pipe symbols of Wiki tables can conflict with other such symbols in templates, and the use of HTML tables is one method of avoiding such problems. When HTML tables are used, they have more liberal syntax rules; for example, they can have line-spacing between their elements whereas wikitext tables cannot.

Technical note: ''It might be as well to know that HTML tables can be made in some HTML editors, and that these are often provided free on the internet. The internet also provides the use of HTML-to-Wikitext converters for code, but not for the opposite conversion. So, for the few cases where both a Wikitext and an HTML version of the same table are needed, it might be best to make the HTML version first, then simply convert it to Wiki''.

The term seen in the code, class="wikitable", is called an HTML attribute, and applies the standard formatting rules for a wikitable to make these examples more clear. Notice also that the formats differ slightly; the HTML table's styles are placed within the opening element tag, while the Wiki styles are just written after the  symbol. Attributes and other styles are discussed in the next section.

More Notes on Layout

 * Table elements that start on new lines can be indented.
 * Line spacing between such elements is not generally permitted.
 * Tables have modifying HTML attributes of their own, e.g. border, width, and align, etc., as do most HTML elements.
 * Additionally, tables can be changed with classes, IDs, and styles. See later.
 * Tables to be displayed in templates are best made with HTML.
 * Wiki heading cells have built-in styles; they are already bold and centered.

HTML tables need text in their cells to be properly displayed. If a blank cell is intended then entering a non-breaking space, &nbsp;, avoids problems.

CSS Styles
The simple tables shown above can be used just as they are, but their users will likely need to apply some extra formatting sooner or later. To extend a table's structure, many just add new rows with their cells, or extra cells in existing rows. These methods have merit, since colors and formats can be preserved. When a more ambitious table is needed then the information in this section will be found useful.
 * Table styles are sets of instructions or rules that add formats to the work,.
 * Styles can be specified and named in style-sheet lists called classes. Then a class- declaration is made in the table line, that is, writing the class name calls it into use. The effect of doing so is to apply all of the styles in the named class to the table.  An example of such a table class declaration is.
 * Styles can also be fully specified within tables; these are called inline styles, and provided that they are written in the appropriate part of the table, they can override styles contained in classes declared in the table line.
 * Users of Wikitext make use of inline styles because there are few useful classes to format tables; the writing of new style-sheet classes would be the preferred method but, by necessity, this activity is in the domain of administrators.
 * Style rules can be used to format all of the table's parts.
 * HTML attributes can be used too, but their formats differ from those of CSS styles. Many are now obsolete, so always consider CSS first.
 * Styles and attributes can be used in conjunction to good effect.

The general formats for writing these styles can be found in the drop-box Style Formats below and a summary of properties can be found in another. The sections of this page contain numerous code examples that illustrate how styles are placed for a given effect, and the reader new to the subject is advised to follow the wording of the code for the best understanding. More on the precedence of styles can be found in the Wikibooks page The CSS Cascade, though the work might be more than is needed for a basic understanding.

Numerous examples of HTML tables and their Wikitext equivalent coding can be seen on the page Tables Ready to Use. At times it is easier to understand a particular point from such examples, or to recall details already learned.

Style Rule Priorities
When styles for similar formats are written into the various parts, (elements), of a table, it is possible for one set of formats to be in conflict with another set. In general, any formats closer to the cell text will supersede similar formats further away from it.

For example, if the background color of a table is set to red using a style expression in the table line, then another expression in a cell could specify the cell color blue. A row's color could be specified differently also. Subject to the rules of priority, only some parts would be affected and the remaining parts of the table would retain the color set for them in the table line. These simple priorities are listed here:

 * Styles written in cells supersede similar styles applied at row or table level.
 * Styles written in rows supersede similar styles applied at table level.
 * A CSS Style is given priority over an HTML attribute  when both are at the same level.  For example, if a CSS margin property places a table near the left margin of the page, then the additional centering of the table with the attribute align would be disregarded.   Although these formats are not identical, the implied CSS positioning has priority over that of the attribute at the same level.
 * Attributes can sometimes have priority. This can happen only if the attribute is at a table level that is closer to the text.  For example: if a table level CSS style sets text to be right-aligned, and a cell attribute centers it, the cell will have centered text while the rest of the table will be right-aligned.
 * A class declaration's CSS styles can be modified by in-line CSS styles at the appropriate level in the table, though attributes cannot override these. Attributes can of course apply to styles not specified by the class at all.  The nature of classes is described in the WikiBooks page Class and Style Notes.

If these priorities seem complicated, they are easier to understand in practice. In the following table a number of text colors are applied at each of the table, row, and cell levels. To help understand the basic hierarchy, refer to the code module below while following these points.
 * The default color for a table's text is black.  This is not apparent from the code but is a consequence of the Wiki style sheet.
 * A CSS class declaration,, applies various styles to the table all at once, including a gray background.  It also uses a black text color.
 * A table style applies red text to the whole table. Without other code, all text would be red.
 * A row style applies blue text to the second row and green to the third. Because the rows have higher priority than the table, they change the text colors.
 * A cell style applies maroon text for two cells. The cell levels have more priority than the table or row and can change certain parts even more.
 * The closer the style is to the text, the higher its priority in setting formats. Further formats applied directly to the data with HTML tags or wikitext are also possible.

What you type
{| class="wikitable" style="color:red;" | style="color:maroon;"|A1 : Maroon Cell Style |A2 : Red Table Style | style="color:maroon;"|B1 : Maroon Cell Style |B2 : Blue Row Style | C1 : Green Row Style | C2 : Green Row Style | D1 : Red Table Style | D2 : Red Table Style
 * - style="color: blue;"
 * - style="color: green;"
 * }

What you get
This description of CSS priorities has been limited deliberately. The setting of CSS priorities is complex and is determined by various factors. The place that styles are written within the web page or its various style-sheets has an affect, the so-called source of the styles, and there is a hierarchy for these sources. For example, user style-sheet important styles are set higher than any author styles. Additionally, within each collection of styles that exists from a certain source, there are further priorities set; these follow complex rules of precedence; (IDs higher than classes and classes higher than element styles, etc.). There is also a rule for duplicated styles that are in conflict, and at times, it is only the browser's work sequence that decides which of various similar styles is to be used. An overview of how CSS priorities work for web pages is given in The CSS Cascade.}}

The Table Parts
Tables coding needs a basic knowledge of the table spaces.

The table spaces are just the main table elements and the adjustable parts within it. This short section explains the terminology of the table and gives some idea of the nature of its formatting.

Refer to the drop-box The Table Design Spaces for the text.

Borders
Borders are used to set the table from the other parts of the page, and are often used for decoration.

Borders can be set for the whole table at once, or for any individual part of it. The thickness, style, and color of these borders can all be specified, and there are even rules for the four individual sides.

This section describes the various options available for making borders and attempts to introduce a few of the lesser known formats. Refer to the drop-box Border Styles for a summary of border styles.

 * The example below has various borders.  Initially, there are no all-round borders on this basic table.   An outer border is set for the table perimeter, and various borders are set for the bottom of the individual cells.   In addition, the background color of the whole table has been changed to lightyellow, then the heading color changed after that to brown.   The text color of the headings has been set to white to give better contrast against the new background.   Follow the details in the example below:

What you type: What you get

Cell Spacing

 * Cell spacing refers to the space that surrounds each cell in a table. It is also called border spacing .
 * It can be made to be zero, but it is more often set to some practical value to space the cells apart, and to improve the layout.
 * Sometimes the borders can be made to overlap and this is called collapsed borders.
 * At times the horizontal and vertical spacings can be made different.
 * There are two methods in use for spacing borders; the HTML attributes method and the CSS styles method.
 * Spacings can only be written into the table line.

 * Mixing style and attribute methods can cause confusion for borders and spacing.
 * Large tables are best used with HTML attributes since they reduce work.

 * This cellspacing method produces its best appearance for borders made with the border attribute.
 * In this method, applying a value for cellspacing separates the borders appropriately.  Setting a value of zero for these  thin internal borders gives a fairly similar result to the collapsed borders seen in CSS styles, and has a neat appearance for little effort.   If the cellspacing attribute is omitted altogether a small amount of spacing is nonetheless added.
 * The borders made with the border attribute are compound.  That is, they are always made from two different colors.   In HTML the two colors can be specified, but in wikitext they cannot.   The default state sets a lighter color for the bottom and right borders, and the darker color for the left and top.
 * The borders made with attributes apply to the whole table, including the table perimeter. When the value is varied, the outside perimeter changes but the inside borders retain a nominal value.
 * When more elaborate borders are needed, the border styles must be used, and to space them the corresponding border-spacing properties are preferred.

These are examples of the cellspacing attribute.

Cellspacing Attribute Notes

 * The attribute cellspacing is simple to use.
 * Use cellspacing for large tables to reduce work.
 * If the cellspacing attribute is omitted, a small default spacing is applied.
 * The method nearly collapses attribute-set borders with cellspacing=0. For truly collapsed borders, i.e., borders that are overlapped, use CSS styles. See below.
 * Thin internal borders made with border=1,nonetheless look reasonable with cellspacing=0, especially when the alternative CSS method involves much work.

Both formats give results as follows:

The same example using thin borders looks like this:

Separated borders can have uniform or non-uniform spacing:

In the first coding form, there is uniform border spacing given by the single figure. In the second form the two figures produce horizontal and vertical spacings respectively. The non-uniform results are as follows:

The same example using thin borders looks like this:

The separated borders state can place borders side-by-side by setting the spacing to zero. For completion these cases for thick and thin borders are shown:

The same example using thin borders looks like this:

Borders made with the border attribute should use the cellspacing attribute to collapse or space its borders. Similarly, CSS spacing should be used with borders made with CSS. Confusion can arise in attempting to integrate these two methods.

Problems sometimes occur with the cellspacing attribute. For example, when a table is to be displayed as the parameter of a template, the template is likely to fail. To avoid it, the table should be made in HTML, the cellspacing attribute should be removed, and the CSS styles should be used instead. In addition, wikitext should be changed to HTML. At other times the attribute form can be useful since it gives a good effect for little coding work. }}

Cell Padding

 * Cell padding refers to the space that surrounds the text in a cell. It can also be applied to a table, to pad the space just inside its perimeter.
 * Padding is maintained even when the cell width changes.
 * Single words of text are usually handled with alignment rather than padding.
 * All four sides of a cell can be padded differently.
 * Table padding can be applied in some browsers provided that the borders are not collapsed.
 * There are two methods for padding; the HTML attributes method and the CSS styles method.
 * Attributes are written in the table line, and the CSS styles are written in the cell or the table line, depending on the formatting intention.

Use attributes and styles

 * Cell styles and the table attribute cellpadding can be used together in the same table without confusion.
 * Uniform cell padding for cells uses the HTML attribute cellpadding in the table line.
 * Non-uniform padding for cells uses styles in the cell lines.
 * Table padding of any kind needs a style in the table line, but can only be used without difficulty when the borders are separated. Some browsers, for example Internet Explorer 6, will not render padding set in the table line at all, though both Opera and Firefox will do so.

The HTML attributes method
These are examples of the cellpadding attribute.

Cellspacing Attribute Notes

 * The attribute cellpadding is simple to use.
 * The attribute applies uniform padding to cells only.

Coloring
Background coloring can be done for the whole table, or for individual cells. So also for the coloring of text. When cellspacing is used the table background property sets the color between the cell borders and the cell background the colors within. A selection of color names is provided in the drop-box. Should more color data be needed during design work, call any or all of the drop-box templates Lightcolors, Mediumcolors, Darkcolors, or Greycolors directly into the sandbox.

The CSS color styles
The style rule to set both the background and text colors is typically:

where background is the background color of the element and color is the color of text.

These colors can be set in any of the table, row, or cell elements, and follow the usual CSS style priorities discussed previously.

There are at least three ways to specify a color:
 * Use the color name, for example; red, blue, mistyrose, etc.
 * Use the RGB value for the color; for example; RGB(140,100,65).
 * Use the HEX notation for the color; for example, (includes the semi-colon);

To further emphasise the point, the following three style expressions for black text on a beige-like background are equivalent:

Note that the use of the HEX notation has a trailing semi-colon. Since a semi-colon is also used as a separator for style rules, it is entirely likely that two semi-colons will appear in code together. Neither of these should be omitted.

Spanning
Tables that have the same number of columns in each row, and for the sake of argument, the same number of rows in each column, are referred to as uniform tables. However, non-uniform tables can be made by merging cells, that is referred to in wikitext and HTML as spanning.

What you get
}

Colspan notes

 * Styles are separated from data with a pipe symbol.
 * HTML attributes border and colspan use an equals sign separator.
 * Colspan can be thought of as reaching to the right.
 * The spanned cells should be omitted in code.
 * Inconsistent values do not extend the table.

Similarly, we can do the same thing with rows:

What you type

Rowspan notes

 * Styles are separated from data with a pipe symbol.
 * HTML attributes border and rowspan use an equals sign separator.
 * Rowspan can be thought of as reaching downwards.
 * The spanned cells should be omitted in code.
 * Inconsistent values do not extend the table.

Row spans with column spans
The two attributes rowspan and colspan can be combined to simultaneously span vertically and horizontally:

Mixed span notes

 * Rowspan and colspan attributes can be applied to the same cell.
 * Spans between cells can be made only for comparable joining dimensions.
 * The spanned cells should be omitted in code.
 * Removal of spanned cells must not cause a row to be empty. For example, an attempt to further form a rowspan between H and L would require that the cell L as the last remaining cell in the row, be removed, and the join would fail.

Width and Height
There are three distinct behaviours for tables when content is added to the cells; this assumes that there is more that a few characters.

 * The first case is the most common; that is, for unformatted text. That is, text that depends on the software to wrap its lines.
 * The second kind of behaviour is for pre-formatted text within pre-formatting tags, or the addition of box-like structures, such as other tables or images.   This second set is characterised as having default widths or assigned widths of their own.
 * The third kind of table content is a very long character string without spaces in it, of the kind sometimes seen in program listings.

These three cases are explained in more detail below.

Unformatted Text Behaviour
Consider the case of unformatted text. When the width settings of a table and its cells are not set in code, the text added to cells causes the cells and table to expand to the full width of the page before any text wrapping takes place. In the absence of width settings a full-width table might be produced.

When the width of a table and the widths of its cells are fully specified, the cell text will start to wrap when the text of individual cells reaches their cell borders. Then, at some stage with increasing text, the cell will extend downward, while maintaining its width setting. This behaviour is apparent even when the height of cells has been specified.

Formatted Text and Boxes
Consider the case where the cell contents have either a default width or a preset width of their own. Let us assume that the content is to be an image. Whether or not the widths of the cells are set in code, the image will expand the cell to accommodate itself. If the table width was set then the other cells might even be narrowed or extended in height to maintain the intended table width and its contents. When the table width cannot be maintained in this way, the table is extended, perhaps beyond the right margins of the page. This behaviour is often seen for text in pre-formatted text tags. To avoid these problems simply limit the content's width, within its own coding.

Long Text Strings without Spacing
Table cells often contain code listings as text so that users can see how code is written. Some of these code lines are quite long and ordinarily would be wrapped in the width set for the table. However, because unspaced text is treated as a single word, the table cannot break it in the middle for wrapping. In this case the table is extended, regardless of the width settings. This lack of wrapping can be a puzzle elsewhere, even where long-line wrapping has been planned. The problem is avoided by placing an adequate number of spaces in long text strings. For example, a CSS style expression allows spaces at many points, provided that they are not placed immediately before either a semi-colon or a full-colon.

Relative Width Example

 * Width uses absolute units like pixels, or relative units like percentage.
 * Relative units are useful since the page width need not be known.
 * Relative width relates to a percentage of the page's width in the case of a table, or to the table if the width setting is for a cell.
 * Height need never really be fixed, though it sometimes helps to give some minimum height to the work.

A table set with relative widths can be seen below. The table is set to occupy half of the page width, ( width=50% ),  and the two leftmost columns are each to take up twenty-five percent of that. Note that the cell widths are to become twenty-five percent of whatever width is given to the table, and that neither the width of the page nor the eventual width of the table need ever be known. The image uses its own dimensions to occupy the remaining width and is also centered with its own code. Notice that although both rows have been specified to have the same height, the image has made the top row deeper. Advantage is also taken of this layout to show the basic horizontal and vertical text alignments.

Example Notes

 * The columns are set to 25%, 25%, and 50% (implied), of the table width respectively.
 * The table is set to 50% of the available page width.
 * Both rows are initially set to 60 pixels in height.
 * The image forces the top row to be 90 pixels in height, but has enough horizontal space.
 * The image's dimensions are set within the image code.
 * The image also uses its own code to horizontally position itself; (center)
 * The text cells introduce the various text alignments

Table Alignment
Tables can be aligned horizontally on the page with the HTML attribute 'align' , with the CSS style 'float' , and with the CSS style 'margin'. In each case these style-rules are placed in the table line. The crude vertical alignment of tables is accomplished by the use of the text line break, while fine adjustments can be made with CSS margin styles.

 * The HTML attribute method makes use of the align attribute in the table line to position the table at left, center, or right of the available space, and examples of its use can be seen in table code throughout this page.   The only point to note is that for the centering of tables, margin CSS styles in the same table line will take priority over align.  Top and bottom margins will not cause problems but the use of left or right margins will. Text can float around such a table with the exception of the centered case.
 * The CSS style 'float'  cannot place a table in the center of the available space but is limited to left and right.  It has the advantage that text can float around the table.
 * The CSS style 'margin' is best and by its settings can place a table anywhere in the horizontal alignment.  When the margin property is set to  auto the table is placed at the center of the horizontal containing space.   The same result can be obtained with the judicious use of relative measurements(%).   The extent to which text floats around a table positioned with margin depends on how much space remains.

See the examples in the drop-box below.

Content Alignment
As is the case for most table styling, there are two main methods; HTML attributes and CSS styles.

 * All text can be positioned using attributes. See the table below for the examples.
 * The vertical positioning of images and other box-shapes needs the style property vertical-align, with horizontal positioning using their own coding.

The attribute alignment summary is as follows:
 * Align sets the horizontal alignment of text.  It has values of left, center, or right. For example align=center to center text (or a table).
 * Valign sets the vertical alignment of text.  It has values of top, middle, and bottom.   There is no equivalent use in the table line.
 * Vertical alignment of text uses valign at cell level, or the CSS property vertical-align.
 * Vertical alignment of images and nested tables uses only the CSS property vertical-align at cell level.
 * Images and nested tables set their horizontal alignments within their own coding.
 * Vertical alignment cannot be set at table level.

The following tables show the styles to use for a given effect and in particular the use of the HTML attributes align and valign. In addition, the vertical alignment of images and nested tables is shown in the code block and table that follows.

Attribute text alignment combinations
and  Attributes       This is  and.  This is   and.  This is  and.  This is  and. The text is justified.  This is  and. This is  and. This is  and. <td width=140px align=justify valign=middle>This is  and. The text is justified. <th style="padding:10px;"> <td height=80px width=133px align=left valign=bottom >This is  and. <td width=140px align=center valign=bottom >This is  and. <td width=140px align=right valign=bottom >This is  and. <td width=140px align=justify valign=bottom >This is  and. The text is justified.

Vertical alignment of images and nested tables
<td style="padding:10px;"> <td style="padding:10px;"> <td style="padding:10px;"> <td height=160px width=180px style="vertical-align:top; border:5px solid brown;"> <td width=180px style="vertical-align:middle; border:5px solid salmon;"> <td width=180px style="vertical-align:bottom; border:5px solid brown;"> <td width=180px style="vertical-align:top; border:5px solid salmon;">

Sorting and hiding
Tables can be made so that when displayed on the page, clicking a link will sort the table. Clicking it again will sort it in the opposite direction. Each column is given a sorting link, so sorting can be done on any column. The method allows the user to view the data from different viewpoints.

Tables can also hide their contents. These tables are called collapsible. Collapsible tables resemble a simple box in the collapsed state; then, when the box is clicked with the mouse, the table reverts to the expanded state, and is revealed. The link has a toggle action; clicking the link again hides the contents. Such tables help to unclutter the page, and so avoid distraction from the main themes. They are of particular use for supplementary information.

Sortable tables
In its simplest form, adding the class declaration  class="sortable"  to the table line of any table makes a sortable table, regardless of other classes and styles applied. The following code illustrates the method, and the result is shown below. Click the links in this resulting table to see how sorting works:

For a more extensive treatment of this topic, readers should see meta:Help:Sorting.

Collapsible tables
The code for a collapsible table much resembles the code for an ordinary table, with the addition of a class declaration. (Some Internet Explorer browsers experience faulty links).

This is also a good example of how to declare multiple classes. The basic shell coding for a collapsible table and the result can be been below.

The result is:

Whether or not the wikitable class is included, the purple heading is a default feature. HTML attributes and CSS styles can however, be applied to the heading as with all other parts.

When the width attribute is used, the expanded width and the initial width will be the same and fixed by it. In this condition, unformatted text will wrap in the set width. Preformatted text will extend the box to the length of its longest line. Box structures such as HTML tables and images will expand the drop to the enclosures' width.

If the intention is to display unformatted text but to have an initial box width that is narrower than the open box width, then the displayed contents should be placed within a nested table cell of its own, and that table set to the required open width setting. Note also that the default text alignment for this collapsible table is center.

When the width attribute is omitted, the initial width is set by the width of the heading text. In this condition, unformatted text will expand the box to the available width of the page, and  Preformatted text will extend the box to the length of its longest line. Box structures such as HTML tables and images as always will expand the drop to the enclosures' width.

An alternative to making your own collapsible table can be had using the template Dropimage. This template has a comprehensive set of options, including the options to change an entire style expression, and class. It is based on the Collapsible class. The result of using Dropimage can be seen by reviewing the effects of the drop-boxes on this page. Readers who need more information on collapsible tables, and in particular for information on combining sortable and collapsible tables, should see meta:Help:Collapsing.

title: Editing Wikitext/Tables


text:
Past LSAT Explained/PrepTest 34

Form 2LSS52

Section 1 Reading Comprehension
Passage 1 Social Science authoritarian regime and political change

Question 1
Main idea
 * 'l;hyh jkl kj

Question 6
Passage 2 Humanity Blues and Spirituals
 * African American Culture

Question 11
Passage 3 Natural Science Evolution and Lamarck's Hypothesis Jean Lamarck Escherichia coli

Question 13

 * laissez-faire
 * minimum wage

Question 18
Passage 4 Law
 * United Nations Convention Relating to the Status of Refugees
 * Handbook on Procedures and Criteria for Determining Refugee Status
 * United Nations High Commissioner for Refugee (UNHCR)

Question 1

 * impute
 * Ad hominem

Question 3

 * vegetarian
 * eggplant
 * zucchini casserole

Question 10

 * Learning disability

Question 12
IDENTIFY This is a Strengthen/Weaken question.

READ This passage introducessynesthesiacs who defies the traditional notion of senses. ANALYZE

(A) Correct If this is true, the synesthesiacs' response that suggest their ability to transcend the usual boundaries is no longer reliable. Because they cannot express what they are sensing, we cannot base our conclusion on their reponses.

(B) Incorrect. The existence of the sixth sense is irrelevant. The passage concerns with the five senses known and how those of the synesthesiacs differ from those of normal people.

(C) Incorrect. Whether their experiences form a pattern or not does not matter.

(D) Incorrect. This may in fact strengthen the argument by providing some historical basis for synesthesia.

(E) Incorrect. Some side fact that do not really impact the argument.

CHOOSE

Response (A) weakens the argument by invalidating the synesthesiacs responses.

Question 16
IDENTIFY This is an Assumption question. This question tests your ability to grasp technical aspects of photography and camera. READ

The author is trying to lead us to believe that the difference in the lense resolutions don't matter.

ANALYZE

To find the answer, it is helpful to negate each choice and see whether it negatively impacts the argument. (A)Incorrect. The definition does not really matter.

(B)Correct. This must be assumed. If this is not assumed, then the difference in resolution does matter since it determines the deficiencies of available film. We would need to worry about the resolution of the lenses when we buy a camera.

(C)Incorrect. Even if this is not true, the effect will be uniform on all the films. It does not  weaken the argument.

(D)Incorrect. So what? Photographic technique is outside the scope.

(E)Incorrect. Only is the key here. Even if there are many important factors beside these two, the argument may still make sense. Why? Because those other factors may be same for all cameras and films so they are constant (fixed).

CHOOSE (B) is the best answer.

Question 19
Antacid

Question 22
capital punishment

Question 24
IDENTIFY This is a Parallel Reasoning question.

READ Some key words are
 * unbeknownst
 * mincemeat pie
 * denigrate

ANALZE

CHOOSE

Section 4 Analytical Reasoning
|34

title: Past LSAT Explained/PrepTest 34


text:
User talk:89.207.160.254

Thanks for experimenting with Wikibooks. Your test worked, and has now been removed. Please use Sandbox for any other tests you want to do, since testing material in modules will normally be removed quickly. Please see the welcome page if you would like to learn more about contributing to our project. Thanks. Urbane  (Talk)   (Contributions)  15:47, 10 September 2007 (UTC)

title: User talk:89.207.160.254


text:
User:Yzmo/FUS

This is a screenshot of the finished first room map for the GtkRadiant book.. I'm not making it smaller cause people may wan it in full size, and i think that this is OK as it doesn't hinder the company to sell the game or anything, it should just illustrate the subject.

title: User:Yzmo/FUS


text: File:FirstRoomInGameRadiant.jpg

title: File:FirstRoomInGameRadiant.jpg