text:
Talk:False Friends of the Slavist

This is looking good so far
This project here is something I've been watching with some anticipation to see just where it would be going. While it is multi-lingual, it is something that Wikibooks is going to be especially pleased that it is a part of our project. I can see many of the language instruction textbooks referencing this material, and it is an impressive reference work. Thank you for considering Wikibooks as a place to move content of this nature, and we are glad that it is here. --Rob Horning 17:46, 11 February 2006 (UTC)

 * Thank you very much, Rob. I'm happy that this material is welcome, and your comment has doubled my energy to get the conversion done soon.  --Daniel Bunčić 13:12, 14 February 2006 (UTC)

Homonyms
It is shame that diagonal entries in the table are wasted.

I suggest to use them for the tables of homonyms in the corresponding language. In reality, the homonyms are just the same "false friends" for a person not proficient in a particular language. Mikkalai 18:38, 1 March 2006 (UTC)

 * Not a bad idea. I only think that what causes troubles within a language are paronyms rather than homonyms. (See the German wikipedia article on paronyms for details, which is much better than the English one and even offers examples from Slavonic languages.) --Daniel Bunčić 19:24, 1 March 2006 (UTC)

Alphabetical order
I have just sorted all the pages in this book alphabetically, which should make orientation within a long page much easier. However, my external editor did not pay attention to diacritics, so e.g. ż and ž are now sorted as z, not after z as they should. If you find a sorting error like this on a page, please correct it manually. Nonetheless, I think already this primitive alphabetical order will be a great help. --Daniel Bunčić 19:09, 2 March 2006 (UTC)

Collaboration of the Month candidate
I have nominated this book for the Collaboration of the Month. This means that if you are a registered wikibooks user with at least 20 edits (or will be till the end of March) and you think that this is a good project worth working on, then please go to the nomination page and vote for this book by putting  #~  below the most recent vote. If our wikibook is elected Collaboration of the Month, it will be presented on the Wikibooks main page for the whole month of April, hopefully attracting lots of other users who can help improve it. Thanks a lot! --Daniel Bunčić 19:25, 2 March 2006 (UTC)

Rusyn
How about a section on the Rusyn language? Here is the Rusyn flag for the header...

Kazak 20:42, 5 March 2006 (UTC)

 * I would appreciate this very much. But a section on the Rusyn language? Is there any dictionary (not a false-friends one, just an ordinary orthographic and/or semantic dictionary) that is likewise accepted by Rusyns in Ukraine, Slovakia, Poland, Hungary, Serbia, Croatia, USA and Canada? If so, tell me the title of this dictionary. If not, how many Rusyn sections do we need then? I would say that we need at least two sections for Carpatho-Rusyn and Yugoslavo-Rusyn, but if I look at Русиньскый язык (ed. Paul Robert Magocsi, Opole 2004, in the series Najnowsze dzieje języków słowiańskich, ed. Stanisław Gajda) it seems there are even more (of course, mutually intelligible, but nonetheless differing) standards. And the main question, as there is much more work to do than just to add a flag (see False Friends of the Slavist/Editing help): Who will fill all these pages? --Daniel Bunčić 07:23, 6 March 2006 (UTC)

Sirov/surov & bula
I notice somebody removed some meanings from the map for bulka. I don't know whether that was the right thing to do, but anyway, some of those meanings are valid for bula - "a swelling or tumor" (slo), "muslim woman" (most of the balkans), possibly others.

Another interesting case I remembered is sirov - "of cheese" (slo), "raw" (scr) - this leads to speakers of scr finding Slovenian Cookbook:Börek shops hilarious for selling sirov (cheese/raw) and mesni (meat/local) burek. To make things a bit more complicated, surov is slo for both "raw" and roughly "cruel", while in scr it only has the latter meaning. 193.77.78.187 14:33, 1 June 2006 (UTC)

Redirect?
False Friends of the Slavicist should redirect to this article. -Iopq 15:53, 29 June 2006 (UTC)

Ласка
Русское ласка и польское łaska обозначают одно и то же: животное и милость. Спрашивается, а где тут «ложный друг» переводчика? — Wolliger Mensch

 * В польском слово łaska используется в значении животного Mustela nivalis реже, чем слово łasica, которое следует считать первостепенным названием этого животного. Кроме того, в польском слово не имеет значения 'caress', 'pieszczoty' (напр. материнская ласка = matczyne pieszczoty), как и обозначено на странице. Кстати, по-английски животное Mustela nivalis не просто weasel, а least weasel. Надо исправлять. — Weikko 0:32, 19 October 2006

 * Я сам это уже исправил. — Weikko 23:23, 20 October 2006

Я поляк и никогда я не говорю ласка на łasicę!! Никто из моих знакомых так не говорит. Это ошибка. В современном польском языке не изпользвается такое слово.--83.31.32.199 20:26, 16 September 2007 (UTC)

ISO 639-3 language codes
I think it would be better to use the ISO 639-3 language codes. Tobias Conradi 00:53, 24 June 2007 (UTC)

Duplication
I am concerned that the Serbo-Croatian title 'Lažni prijatelji slavista' is repeated only four times in succession. Clearly this is not enough because it fails to distinguish between Serbian-Serbian and the completely different language spoken in Republika Srpska. Not to mention excluding a separate entry for Serbian as spoken in parts of Kosovo, which is so incredibly different from Serbian (especially in its written form) that it even makes Serbian and Macedonian look like the same language. Please can we add a few more duplications of this title to make sure every reader can understand it, otherwise some might not find it in their own language.

Sorbian Flags
I noticed in this WikiBook that the flags of Upper and Lower Lusatia were made of Sorbian national flags with coat of arms of Saxony and Brandenburg added respectively. However, on the Wikipedia site about Sorbs, I found different flags: http://en.wikipedia.org/wiki/File:Flagaluzycgornych.png and http://en.wikipedia.org/wiki/File:Flagaluzycdolnych.png Do you think that the flags shouldbe replaced? I know that these flags are connected with the whole region and thus do not represent only Sorbian people, but I also do not think that we should use the Sorbian flag with German coat of arms.

The Big Slavic Dictionary
I've found this dictionary (it's more like a swadesh list for slavic languages): https://slavic.world Is it possible to achieve some cooperation with?

Flag of North Macedonia not showing
The flag of North Macedonia is not showing properly (for example, in False Friends of the Slavist/Russian-Macedonian. I fixed the flag in the navigation table. Niobian (discuss • contribs) 13:38, 18 February 2019 (UTC)
 * That problem appears to be located at /Head. --Pi zero (discuss • contribs) 22:15, 18 February 2019 (UTC)

New database of false friends now online
I have now published a searchable database system with the materials from this great Wikibook:

Database of False Friends in Slavic Languages

The new database has a search function and generates every page dynamically by querying a database and rendering the language material automatically. This makes it to provide a semasiological map for every term, be there only two terms of two languages.

The database has a different approach than this Wikibook. While here the materials are presented mostly around mono-/bilingual lists and semasiological maps on individual static pages with templates, the database arranges information around the individual searchable terms which are put into context to the terms of the other languages.

There are many other smaller differences, e.g. the database discriminates between aspect, has fields on synonymity and grammar, shows "see also's" and much more.

I would be happy if we could place a link to the database on some more prominent place than here.

I am looking forward to your feedback. Daniel Bunčić, please let me know if I did everything right with the copyrights disclaimer.--Pod-o-mart (discuss • contribs) 13:08, 18 May 2020 (UTC)

Merging Bosnian, Croatian and Serbian into one
This wikibook would be much more useful with one entry for Serbo-Croatian. The current Bosnian, Croatian and Serbian lists (this was evidently made before Montenegrin magically popped into existence) are 90%+ copy-paste with some omissions, as if some words "valid" in one are "invalid" in the other varieties. The repetition of "Lažni prijatelji slavista" is just the cherry on the top (of the page) and makes it look like a joke. -Vipz (discuss • contribs) 19:16, 7 July 2022 (UTC)

title: Talk:False Friends of the Slavist


text:
Modern Greek/Reading Exercises/Reading 03

= Song: Τα κλεφτόπουλα =

This song dates to the Greek War of Independence, 1821-1827.

Μάνα μου τα, μάνα μου τα κλεφτόπουλα τρώνε και τραγουδάνε, άιντε πίνουν και γλεντάνε

Μα ένα μικρό, μα ένα μικρό κλεφτόπουλο δεν τρώει, δεν τραγουδάει, βάι δεν πίνει, δεν γλεντάει Μόν' τ' άρμαντα, μόν' τ' άρμαντά του κοίταζε Του ντουφεκιού του λέει: «Γεια σου Κίτσο μου λεβέντη!»

Ντουφέκι μου, ντουφέκι μου περήφανο σπαθί ξεγυμνωμένο, μια χαρά είσαι το καημένο Πολλές φορές, πολλές φορές με γλύτωσες απ' του εχθρού τα χέρια με κυνήγαν νύχτα μέρα

Και τώρα με, και τώρα με λησμόνησες σαν καλαμιά στον κάμπο. Δεν μου λέεις τι να κάνω

[[Media:Modern_greek_kleftopoula.ogg|Audio recording]]

(Note: The words above are transcribed from the recording. In the second-to-last verse, the traditional words are actually "απ' του εχθρού τα χέρια κι απ' των Τούρκων τα μαχαίρια.")

Translation:

 * Mother, mother, the warriors, they eat and sing, they drink and make merry.

 * But one young warrior, he doesn't eat, he doesn't sing, doesn't drink or make merry.

 * He only looks at his weapons, and says to his musket, "Hello Kitso, my brave man!"

 * My musket, my proud musket, my sword unsheathed, a joy you are, my dear.

 * Many times, many times you saved me from the hands of my enemies who chased me day and night.

 * And now, and now you forget me like a reed in the field. You don't tell me what to do.

=Notes=

Adapted from http://el.wikipedia.org/wiki/Δίας_(μυθολογία)

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


text:
Cookbook:Chutney

A chutney is a variety of condiment similar to a relish, originating in South Asian cuisine. There is a wide variety, but chutneys usually consist of spiced fruits and/or vegetables. The texture can range anywhere from smooth to chunky, and the spiciness can range from mild to hot. They often have an acidic component.

External links and references

 * Gisslen's Professional Cooking (2015)
 * Oxford Companion to Food (2014)
 * Labensky et al., On Cooking (2019)
 * Culinary Essentials (2010)
 * Rinsky's The Pastry Chef's Companion (2008)

title: Cookbook:Chutney


text:
Biblical Studies/Christianity/Creeds and catechisms

The Apostles' Creed (Third or Fourth Century) I believe in God the Father Almighty Maker of heaven and earth. And in Jesus Christ, his only Son, our Lord; Who was conceived by the Holy Ghost, Born of the Virgin Mary, Suffered under Pontius Pilate, Was crucified, dead, and buried; He descended into Hell [lit., Hades]; The third day he rose again from the dead; He ascended into heaven, and sitteth on the right hand of God the Father Almighty; From thence he shall come to judge the quick and the dead. I believe in the Holy Ghost; the holy catholic Church; the communion of saints; the forgiveness of sins; the resurrection of the body; and the life everlasting. Amen.

The Nicene Creed (A. D. 325; revised at Constantinople in A. D. 381) We believe in one God, the Father Almighty; Maker of heaven and earth, and of all things visible and invisible.

And in one Lord, Jesus Christ, the only begotten Son of God, Begotten of the Father before all worlds; God of God, Light of Light, Very God of Very God, Begotten, not made, Being of one substance with the Father; By whom all things were made; Who, for us men and for our salvation, Came down from heaven, And was incarnate by the Holy Ghost of the Virgin Mary, And was made man; And was crucified also for us under Pontius Pilate; He suffered and was buried; And the third day he rose again, According to the Scriptures; And ascended into heaven, And sitteth on the right hand of the Father; And he shall come again, with glory, To judge both the quick and the dead; Whose kingdom shall have no end.

And we believe in the Holy Ghost, the Lord and Giver of life; Who proceedeth from the Father [and the Son]; Who with the Father and the Son together is worshiped and glorified; Who spake by the prophets. And we believe in one holy catholic and apostolic Church. We acknowledge one baptism for the remission of sins; And we look for the resurrection of the dead, and the life of the world to come. Amen.


text:
WebObjects/Case Studies/ShopToIt.ca

Shoptoit.ca is a comparison shopping search engine catering exclusively to Canadian consumers and merchants. The company, Shop To It Inc. was founded in the summer of 2004 by Clark Johannson, Scott Sanderson, and Brendan Duddridge. It went live on Canada Day, July 1st, 2005.

Shoptoit.ca was developed from the ground up using WebObjects, WOLips, and Eclipse on Mac OS X Tiger. It uses the Lucene search engine as a foundation for it's textual search and PostgreSQL for its back-end database. Shoptoit.ca is hosted on a large bank of Apple Xserves and Xserve RAIDs.

title: WebObjects/Case Studies/ShopToIt.ca


text:
Taxation in the United Kingdom/Legislation/Section 13AA of the Income and Corporation Taxes Act 1988

Starting rate
Where a qualifying company has profits (see definition below) which are less than £10,000 divided by one plus the number of its associates it may claim to be taxed at the corporation tax starting rate.

Qualifying company
Qualifying company for the purposes of this Section is a company which is:

(a) is UK-resident; (b) is not a close investment-holding company; and (c) is not an investment trust with eligible rental income (within the meaning of Section 508A of ICTA.

Marginal relief
Where such a company has basic profits between £10,000 divided by one plus the number of its associates and £50,000 divided by one plus the number of its associates, it may reduce its profits by such fraction as Parliament may from time to time decide multiplied by:

 * $$(R2-P)xI/P$$

Where:

 * R2 is £50,000 divided by one plus the number of associates
 * P is the amount of profits (see definition below)
 * I is the amount of basic profits, ie profits chargeable to corporation tax

The figures of £50,000 and £10,000 referred to above are proportionately reduced when applied to an accounting period shorter than 12 months.

Associated companies
An associated company which has no trade or business during the accounting period (or part whereof that it is associated) is ignored in the above calculation. Companies are associated if at a given time one has control of the other, or both are under common control. Control is construed here in accordance with Section 416 of ICTA.

A company is treated as associated with another for the whole accounting period, even if it is associated for only part of an accounting period.

Profits
Profits for the purposes of this section (except for basic profits) is taken as having a special meaning. It is:

 * Profits chargeable to corporation tax; plus

 * franked investment income ("FII") (ie dividends from UK companies multiplied by 10/9), except for FII received from a UK-resident company which is:

 * a 51% subsidiary of the receiving company, or a 51% subsidiary og a company of which the receiving company is a 51% subsidiary; or

 * a trading or holding company not taken out of this definition (see below) and which is owned by a consortium the members of which include the receiving company.

Section 13ZA of ICTA has further interpretative provisions in respect of this.

The bit taken out of the definition referred to above applies where the company distributing the FII is a 75% subsidiary of another company or when arrangements are in place whereby the paying company could become a 75% subsidiary.

FII received in trust, etc
FII received by a company includes FII received by another person on behalf of or on trust for the company, but not to any FII received by the company on behalf of or on trust for another person.


text:
Taxation in the United Kingdom/Legislation/Section 13AB of the Income and Corporation Taxes Act 1988

This Section introduces the non-corporate distribution rate.

The Section (and, indeed, all the non-corporate distribution rate provisions) apply to any accounting period in which the company makes one or more non-corporate distributions and the company's underlying rate of corporation tax is lower than the non-corporate distribution rate.

Where this Section applies, the company is taxed at the non-corporate distribution rate on an amount of its profits chargeable to corporation tax that are matched with a non-corporate distribution, and at the company's underlying rate on any remaining profits.

The non-corporate distribution rate is such rate as Parliament may from time to time determine.

This Section also introduces Schedule A2 to ICTA, which contains the detailed rules for the non-corporate distribution régime, and also definitions of terms such as "underlying rate" and "non-corporate distribution".


text:
Taxation in the United Kingdom/Legislation/Section 13A of the Income and Corporation Taxes Act 1988

Section 13A of ICTA defines close investment-holding company for the purposes of Section 13(1) and Section 13AA(8) of ICTA. The effect of those Sections is that a close investment-holding company is always taxed at the full rate of corporation tax (currently 30%).

A close investment-holding company is any close company that does not fall within Subsection (2).

A close company falls within Subsection (2) for an accounting period if throughout that accounting period it exists wholly or mainly for one of these purposes:

 * to carry on a trade or trades on a commercial basis;
 * to make investments in land, except where the land is let or to be let to a person connected with the company or a relative of a person connected to the company;
 * to hold shares and securities, or to make loans to a qualifying company (see below) which is controlled by or controls the company and itself wholly or mainly for the purpose of holding share or securities or making loans to one or more qualifying companies;
 * to co-ordinate the administration of two or more qualifying companies'
 * to help a trade or trades carried on by one or more qualifying companies or by a company which has control of the company;
 * to make investments as described in the second point above by one or more qualifying companies or by a company that controls the company.

A qualifying company is a company controlled by the company being considered, or which controls that company and which exists wholly or mainly for one of the first two purposes listed above.

A company that is being wound up is not treated as a close investment-holding company in its first accounting period of the winding-up if it wasn't a close investment-holding company in the last accounting period before the start of the winding-up.

Control is construed as for Section 416 of ICTA, relative has the meaning given by Section 839(8) of ICTA and Section 839 in full, which describes what is meant by "connected person" applies to this Section.


text:
User:Roscivs

Special:Recentchangeslinked/User:Roscivs

Table of Contents for Computer Go:

Computer Go Writing a Go Engine Writing a GTP Engine Writing an SGF Parser Writing a Go GUI Developer Resources Open source code GNU Go Utilities Mailing Lists

title: User:Roscivs


text:
Taxation in the United Kingdom/Legislation/Schedule A2 to the Income and Corporation Taxes Act 1988

This Schedule supplemented Section 13AB of ICTA, which introduces the non-corporate distribution régime. It had effect for distributions made between 1 April 2004 and 31 March 2006.


text:
Computer Go/Playing Go Online

Places to Play Go Online
https://go.mattle.online

http://www.gokgs.com/

http://boardspace.net/ (and other interesting games)

http://goshrine.com/

http://www.itsyourturn.com/

http://games.yahoo.com/

http://www.pandanet.co.jp/English/

http://www.dragongoserver.net/

http://www.361points.com/computergo/#gnugo (No registration necessary)

Places for Your Program to Play Go Online
http://www.gokgs.com/

http://cgos.boardspace.net/

title: Computer Go/Playing Go Online


text:
Scheme Programming/What defines Scheme?

Whenever we read about Scheme we will often hear the term 'functional programming'; this is true. Scheme was one of the first languages to effectively support this paradigm. What functional programming means is that when we program in Scheme we try to avoid 'side effects'; we don't change the value of variables as much when we've assigned them. In fact, all parts of Scheme that do so end in '!', (called a bang) which already hints that you're doing it wrongly unless you know what you're doing. Scheme is not purely functional though as it does allow side effects, and only discourages them. In Scheme, everything is an expression; a Scheme program is best seen as one long complicated expression; the lexical let block we saw before is an expression as it evaluates to a value. We could have, for instance, used that entire block as a conditional for an if-expression, which is encountered more than what some people would expect.

Another common trait of functional programming is that, of course, functions and procedures are made more powerful than in most other compiled languages. In Scheme, procedures are first-class objects; you can do the same things with them as integers with C. You can pass them to procedures, return them from procedures, store them in variables, or compute them at runtime as the result of an expression.

Scheme also, like most languages, has lexical scope. This means that where procedures are defined in the code defines how they behave, not where they are called. This might seem obvious, because all languages nowadays have lexical scope, but this is important because Scheme was one of the first to stress the importance of lexical scope which gave rise to closures which are nowadays widely implemented in many interpreted languages.

Scheme has no while-loops or for-loops. In Scheme a similar effect is achieved by simply letting a procedures call itself. "Isn't that inefficient?", some would ask, and the answer is, "No!". For Scheme is also characterized by, and pioneered the use of proper tail recursion: whenever a procedures calls itself in such a way that the same effect can be implemented by a loop or iteration, Scheme guarantees that the compiler will rewrite it to a loop at the machine-code level, so you will never run out of stack space or need useless time to call procedures when what you try to do can be rewritten to a loop.

We have already seen in the last section that Scheme can extend its own syntax. This is because Scheme, like any variant of Lisp has one very important property: the language is homoiconic; there is no essential difference between the program itself, and the data that the program manipulates. We already talked about the abundance of parentheses in Scheme source code. This is for a very good reason: the main data structure in Scheme is the so called list (hence: LISt Processor), and Scheme source code itself is also simply a very complicated list. Lists can contain other lists, and since data can be re-ordered, Scheme can easily re-write its own source code and instructions both at compile and runtime, which is how the syntactic extensions are implemented.

But if Scheme was the first to do so many important things, isn't Scheme old? Yes, it is old; it's one of the oldest languages still in use today, which can be seen as both that it's redundant, and that it has proven its worth.

title: Scheme Programming/What defines Scheme?


text:
Talk:Poker/Expected value

Sure the chance of getting the last Heart is 1 in 5? and not 1 in 4? 70.111.251.203 23:56, 11 February 2006 (UTC)

Should 5% be 19:1 and 4% be 24:1 (25% is 3:1, 3 + 1 = 4, 100/25 = 4; therefore if 100/5 = 20, the odds should be 19:1, because 19 + 1 = 20; likewise 100/4 = 25, the odds should be 24:1, because 24 + 1 = 25)

Perhaps a note in the next paragraph (where it talks about multiplying the bet by x where x is x:1) saying for easy calculation use 20:1 for 5% and 25:1 for 4%.

title: Talk:Poker/Expected value


text:
Introduction to Physical Science/1.4

=Experimentation= This section is primarily concerned with the methods behind taking basic measurements and drawing conclusions. Measurements are pieces of information that are gained by using tools directly. Conclusions are information gained by using calculations and reasoning that are based on Data.

=Measurement= The following sections will teach you how to use the tools you have to measure the indicated basic units.

Barrel (measurement), unit of capacity or volume in the United States and the United Kingdom, the definition of which depends on the material being measured. In the United States the dry standard barrel is equivalent to 105 dry qt, or 7056 cu in (116 liters), and a barrel of petroleum is defined as 42 U.S. gallons (159 liters). Various liquid measures containing from 31 to 42 U.S. gallons (119 to 159 liters) are commonly called barrels, however. A barrel of beer in the United Kingdom is defined as 36 imperial gallons (164 liters). See also Weights and Measures.(edited by Yoshil)

=Length= Length is the measurement of the distance from a given point A to a given point B.Length is usually measured using a basic ruler. A ruler is marked in both customary and SI units. You will use the SI units for all experimentation because in science, the SI system is the standard system of measurement. If what you are measuring is very small, then you will use the millimeter units. The millimeter is one thousandth of a meter (.001 meter). If the object is a small, but not tiny size than the centimeter is the standard unit of measurement. A centimeter is one hundredth of a meter (.01 meter). If what you are measuring is more that 100cm (1 meter) than a meter stick is the standard tool of measurement.

=Mass= Mass is the amount of matter that makes up the object being measured. Mass is measured using a balance or scale. There are several types of balances that all measure mass in different ways. A manual balance or scale uses known masses or weights called "mass standards" to determine the mass of the object on the other side. To use a manual balance, the following steps must be observed while using a manual balance.

Manual Balances
 When measuring substances within a container
 * 1) Setup the balance
 * 2) Use the balancing rider/mass to bring the pans to an even status
 * 3) Place the object to be measured on the measuring pan.
 * 4) Begin to place mass standards on the standards pan until the trays even
 * 5) When the trays are even count the mass standards on the standards tray and record your measurement.
 * 1) Before adding the substance to the container measure the mass of the container.
 * 2) Record the mass of the container
 * 3) Add the substance to the container
 * 4) Mass the container with the substance inside it using the above procedure
 * 5) Record the total mass
 * 6) Subtract the mass of the container from the total mass
 * 7) The result of this equation will be the mass of the substance

Electronic Balances

Electronic Balances use programmed masses as standards for measurements. Electronic balances are also typicaly more accurate then manual ones. Certain procedures must be followed when using electronic balances.

When measuring substances within a container
 * 1) Turn the balance on
 * 2) Press the button that reads zero or tare (this sets the balance's counter to Zero. Doing this is called "zeroing" the balance)
 * 3) Add the mass to be measured gently to the balance's tray
 * 4) Read the measurement on the balance's display
 * 5) Record the measurement
 * 1) Turn the balance on
 * 2) Zero the balance
 * 3) Place the container on the balance's tray
 * 4) Zero the balance again
 * 5) Add the substance to the container
 * 6) Read the measurement on the balance's display
 * 7) Record the measurement

=Volume= Volume is the measurement of the amount of space an object takes up. Volume can be measured in two ways. The method used normally depends on the object to be measured.

Regular Objects
A regular object is an object whose sides can be measured with a ruler. Various formulas exist to find volumes of these objects.Some of the formulas are as follows where L=length, W=width, H=height, Ba=Base area, E=edge, R=Radius
 * Cube L*W*H=V or E3
 * Rectangular Prism L*W*H=V
 * Cylinder Ba*H
 * Pyramid 1/3*Ba*H
 * Cone 1/3*Ba*H
 * Sphere 4/3*π*R3

For Additional Formulas See Appendix: Formulae

Irregular Objects
Irregular objects are anything that does not have flat sides that can be measured with a ruler. The primary method used to measure such objects is called water displacement. In this method, a known amount of water is placed in a container, and the object to be measured is placed into the water. The water will rise within the container. The amount that the water rises by is the volume of the object. The procedure for water displacement measurements is as follows:

 * 1) Use a Graduated Cylinder or some other marked measuring implement to get a measure of water that will be over the top of the object.
 * 2) Record the amount of water in the container
 * 3) Place the object in the container
 * 4) Measure the level of the water
 * 5) Subtract the original level of the water from the new level
 * 6) Record the result

To find the volume of an irregular object you need more than just one tool. You need a graduated cylinder, an overflow can, and some water.

Fill the overflow can with water to the brim and let all the excess water drip out (the water above the nozzle.) Now place the cylinder under the overflow can's nozzle and slowly drop the object into the water. Now read the measurement on the cylinder to find the amount of water that dripped out of the overflow can. That is equal to the object's volume because 1 cubic centimeter =1 milliliter. (edited by Yoshil)

=Vocabulary and Questions=
 * length is the distance from a given point A to a given point B
 * Mass is the amount of matter within a given object
 * Volume is the amount of space an object takes up
 * Ruler is a tool that is used to measure small lengths
 * Millimeter is a unit of measurement equal to .001 meters
 * Centimeter is a unit of measurement equal to .01 meters
 * Meter Stick is a measuring tool that is one meter in length
 * Balance is a tool for measuring mass
 * Mass Standards are known amounts of mass used to measure objects on a manual balance
 * Regular Objects are objects that can be measured using simple length measurements and formulas only.

Covering The Reading

 * 1) If you have an object that is 90cm long, what is the tool preferred for measuring it?
 * 2) What type of tool uses mass standards to take measurements?
 * 3) If an object is 136cm long, what unit is useful for labeling it?
 * 4) What is the method for taking the volume of irregular objects?
 * 5) Would you measure the volume of a perfect rectangular prism using water displacement?
 * 6) What measurement does a balance take?

Critical Thinking

 * 1) If you have a cone with Ba=4cm2 and H=7cm what is its volume
 * 2) When a sphere has volume 535, then what is the measure of the radius?
 * 3) You drop an irregular object into a graduated cylinder containing 40ml of water, after it enters and the water settles, you read that the water level has risen to 64ml, what is the volume of the irregular object?
 * 4) If you measure an object using cm what is the maximum number of units you should have?

Exploration

 * 1) Use a graduated cylinder to measure some household objects around your house using water displacement.

title: Introduction to Physical Science/1.4


text:
User talk:71.141.25.145

Please stop adding nonsense to Wikibooks. It is considered vandalism. If you would like to experiment, use the sandbox. Thank you.

title: User talk:71.141.25.145


text:
Chinese Tractor Maintenance/Trouble Shooting

This page contains trouble shooting information that is applicable to most tractors.

Engine Start
This section describes some trouble shooting procedures for an engine that will not start.

Poor Electrical connection

 * Is there a good connection between the earth lead and the tractor frame?
 * Remove the earth lead,
 * Clean both earth lead and contact point with wire brush or sandpaper.
 * Replace.

Fuel Problem

 * Is there fuel in the fuel tank?
 * Put fuel in the tank.
 * Is there water in the bowl?
 * Drain the water.
 * Is the fuel stale?
 * Drain fuel tank and bowl (and lines?).
 * Replace stale fuel.
 * Is the air temperature too cold for the fuel?
 * If the air temperature is below 45F and the fuel has not been winterized then the fuel may have frozen.
 * Remove all fuel from tank, fuel line, bowl and injectors.
 * Is the fuel valve turned on?
 * Turn on the fuel valve.

Cold Engine

 * Were the glow plugs used during the start procedure?
 * See the staring procedure
 * Was the compression release used during the start procedure?
 * See the starting procedure
 * Does then engine turn over too slow?
 * See the "Slow Turn Over" section.

Slow Turn Over

 * Is the battery charge low?
 * Charge the battery.
 * Is the engine oil too heavy for the air temperature?
 * Replace the engine oil with a lighter weight oil

Low/No Oil Pressure

 * Is the oil level below the full level on the dip stick?
 * Add oil to the engine to full level on dip stick.
 * (more stuff here)

Replacing/Flushing Hydraulic Fluid Caused 3 Point Hitch/FEL/Power Steering To Quit Working

 * Recheck the fluid level too ensure that you have enough.
 * The pump may have lost its prime.
 * Letting it set for a while (couple of hours) may allow it to reprime.
 * Loosening the fitting at the output of the pump may allow any air pressure to escape. Once oil starts to come out you've gotten all of the air at that point in the line that you are going to get.
 * As a last resort you can apply some pressure (2-4 psi) to the fluid resevore. Do not apply significant pressure or you can blow the seals in the pump.

Hydraulics Stopped Working

 * Check that your fluid level is sufficient. You may have lost too much fluid due to leaks.
 * The pump may have lost its prime from sucking air.
 * Check that all fittings are tight (you did this when the tractor was delivered right?). See above for how to reprime the pump if you still have problems after tightening fittings if any where loose.

Power Steering Sluggish

 * See

3 Point Hitch Stopped Working

 * See

Front End Loader Stopped Working

 * See

Operating Temperature Too High
First check the water level - release pressure and open cap very carefully when hot, or wait for engine to cool first.

The airflow through the radiator can become blocked from mud and grass straw. Some (most) Chinese tractors do not have a guard in front of the radiator. Use compressed air to blow out the derbies from between the fins. This usually works best blowing from the back, or fan side of the radiator. Be careful not to damage the very thin metal fins which zig zag between the water passages.

Other causes of overheating include, radiator blocked by rust, etc. Water pump failed.


text:
Tagalog/Ligatures

Tagalog uses the ligature na as a way for adjectives to modify nouns. In order to smoothen pronunciation, two other ligatures, -ng and -g (shortened forms of na), are also used.

Aralín (Lesson)
The Tagalog ligature na comes after words in order to modify them. For the sake of euphony, two other ligatures, -ng and -g, both shortened forms of na, are also used. The ligature used depends on the ending letter of the word, as shown below:

 * The ligature -ng is attached to words that end with a vowel
 * The ligature -g is attached to words that end with the letter "N"
 * The ligature na comes after the word being modified if it ends in a consonant other that "N"

Ang paggamit ng -ng (Usage of -ng)
As mentioned earlier, the ligature suffix ng is attached to words that end with a vowel, as shown in the following examples:

 * Ang puláng kama ay akin. (The red bed is mine.)
 * Marunong siyang magsalita ng wikang Ingles. (He/She can speak the English language.)

Ang paggamit ng -g (Usage of -g)
The ligature -g functions in the same way as -ng with the exception that the "N" from the latter is removed since the "N" is already incorporated into the word that the ligature is being attached to, as shown in these sentences:

 * Ang sínumang waláng sulatín bukas ay hindí pápasa sa klase ko. (Whoever does not have their essays tomorrow will not pass my class.)
 * Nandito ang aking mágasin. (My magazine is here.)

Ang paggamit ng na (Usage of na)
The ligature na does not attach itself to a word. Instead, it links the word being modified to the word being described. The na ligature only goes with words whose ending letter is neither a vowel nor ends with "N", as shown in these sentences:

 * Ang hayág na lugár na iyón ay malayò. (That public place is far.)
 * Máyroon akóng apat na tanóng. (I have four questions.)

^ Table of Contents ^ | <>

title: Tagalog/Ligatures


text:
Management Strategy/Cost Advantage

There are many sources of cost advantage:

Economies of Learning
Caused by an increase of dexterity and a continuous improvement of routines.

The experience curve
The cost of the nth unit of production is equal to the cost of the first unit of production times the cumulative volume of production to the negative of the elasticity of cost with regard to output.

C[n] = C[1]*(n^-a)

In laTex: $$Cn = C1*(n^-a) $$

Examples of experience curve: Honda, Harley Davidson.

Note that costs do not drop automatically as production increases, but rather that costs must be brought down by management's learning process.

Economies of Scale
Caused by indivisibility and specialization.

Economies of scale start benefiting an organisation when the volumes of transactions/production go up. The increase in profits as number of transactions/production go up because certain fixed costs are incurred irrespective of whether the volume is one or a hundred. For Example a Barber giving haircuts has to pay a fixed rental for his premises on a monthly basis whether he gives five customers a haircut or a hundred.

Let us assume that his rental is US $ 100 per month and he charges $ 10 for each haircut. Let us assume that other fixed costs like his salary, electricity etc.. are US $ 50 and his variable cost is negligible.

If he gets 10 customers a month he will incur a loss of US $ 50.

Revenue 10 x US $ 10 = US $ 100 Cost 150 US $.

Net Loss US $ 50.

If he gets 15 customers a month he will Break even.

Revenue 15 x US $ 10 = US $ 150 Cost 150 US $.

No Profit/No Loss.

If he gets 20 customers a month he will make a profit of.

Revenue 20 x US $ 10 = US $ 200 Cost 150 US $.

Net Profit US $ 50.

If he gets 25 customers a month he will make a profit of.

Revenue 25 x US $ 10 = US $ 250 Cost 150 US $.

Net Profit US $ 100.

Thus an addition of 5 customers has grown profits by 100 %.

Thus the more the volumes grow the profit will grow exponentially initially and then slowly grow at a constant pace. This is the power of Economies of Scale.

However if the premises is able to handle a fixed limit of 100 customers with the 101st customer requiring the renting of another premises with rental of US $ 100, the total profit will reduce from the 101st customer onwards till the 110th customer.

If he gets 100 customers a month he will make a profit of.

Revenue 100 x US $ 10 = US $ 1000 Cost 150 US $.

Net Profit US $ 850.

If he gets 101 customers a month he will make a profit of.

Revenue 101 x US $ 10 = US $ 1010 Cost 250 US $. (Increase rental of 100 $)

Net Profit US $ 760.

Thus an addition of 1 customer has decreased profits by US $ 90.

This is called diseconomies of scale.

The same analogy can be used for the other input factors like employees, furniture etc..

Production Techniques
Caused by automatization, better use of raw materials, and better quality.

Product design
Caused by facilitating automation and reducing use of materials.

Input costs
Caused by better locations, ownership of sources, bargaining power, and good relations with suppliers.

Capacity utilization
Caused by a ratio of fixed-to-variable-costs and because of the costs of increasing or reducing capacity.

Managerial Efficiency
Caused by a desire to be efficient.

title: Management Strategy/Cost Advantage


text:
User:Yondalf

Hi everyone! I have nothing to write here, only that I don't want links to my name to appear in red therefore I have created this page.

$$e^{i\pi} + 1 = 0$$

title: User:Yondalf


text:
User talk:Yondalf

Welcome to my talk page.

title: User talk:Yondalf


text:
Lua Functional Programming

This book is about the Lua programming language, inspired by and based on Paul Graham's work On Lisp. You should be familiar with the Lua language. Familiarity with the Lisp language is recommended but not required (I'm not too familiar with it myself but I've read introductory tutorials before and On Lisp does a pretty good job of explaining in English what the code snippets do).

On Lisp is an advanced Lisp tutorial showing the reader Lisp programming best practices. Lisp is a language suited for functional programming.

The purpose of this book is to investigate whether Lua can be used for similar functional programming tasks as Lisp, and whether Lua might actually be a "better" Lisp. To do that I've attempted to duplicate (in Lua) all the code snippets featured in On Lisp, among other things.

The chapters here have a one-to-one correspondence with On Lisp, wherever possible.

On the side note, the Lua Programming language is used in the creations of add-ons for the ever popular MMORPG World of Warcraft.

The Book

 * /Introduction/
 * /Arithmetic/
 * /Assignment/
 * /Functions/

title: Lua Functional Programming


text: Talk:Biblical Studies/Christianity/Christianity and the world's religions


text:
Lua Functional Programming/Functions

In Lua, as in Lisp, functions are a kind of data type; you can assign them to variables and pass them around in your code.

Defining Functions
Functions can be defined in the "ordinary" way, and we can call them. We can access the function object created simply by using its name without any parentheses. Thus we can pass the function as an argument, store it in a data structure, etc. So-called lambda expressions or anonymous inline functions can also be created in Lua. They are similar to the "ordinary" functions described above in almost every way. Note that functions and other variables share the same namespace in Lua (and in most other languages), unlike Lisp. In fact, in Lua, a function is just another kind of data you can store in a variable.

Functional Arguments
Function objects can be passed to other functions as arguments. To invoke an argument as a function, just append the parenthesised list that you want to invoke it with. Using the  function defined earlier, we can do things like The "canonical" example of a function that takes another function as a parameter is. Unfortunately  does not come with Lua, so we'll have to code it ourselves. This is a simple  implementation that only works with one array. But it works well: A more complex  implementation that works with more than one array is possible: And let's use it: Sort is built-in, though, and we can pass a sorting function if we want. On Lisp provides an example of a remove-if implementation in Lisp. Remove-if is not built-in into Lua, so we might as well code a Lua implementation which is equivalent to the Lisp code below. Compare with the following Lisp code: Both the Lua and Lisp code above are tail-recursive safe (see Tail Recursion below). (Most implementations for both languages support tail-recursion optimising.) Just for comparison, here's how I would code a "pure" Lua version: In Lua, we have to define the helper functions  and   which is built-in into Lisp, but using the   is quite easy:

title: Lua Functional Programming/Functions


text:
Tagalog

Mabuhay!

Tagalog is spoken in the Philippines by about 22 million people, it is known as Filipino internationally and is the official language of the Philippines. Tagalog comes under Austronesian languages. Tagalog is derived from taga-ilog, taga usually means "native of" and ilog means "river" thus, taga-ilog means "river dweller". The language uses fragments from Sanskrit, Malay and Javanese. The early archaeological evidence of the use of Tagalog is the Laguna Copperplate Inscription.

Tagalog is spoken by Filipinos in the Philippines and Filipinos abroad (either native speakers of Tagalog or non-native speakers who studied Tagalog in the Philippines or elsewhere). It contains loanwords from Malay, Arabic, Chinese, Spanish, English, and other languages. Tagalog pronunciation can be difficult because of lexical stress and the presence of glottal stops which are normally not written in everyday writing.
 * /Why study Tagalog/
 * /How to use this Tagalog Wikibook/
 * /About Tagalog/

Saligang Tagalog (Basic Tagalog)

 * Mga Alpabeto — The Alphabets
 * Mga Pambati — Greetings such as Kumusta?, and Telling your name
 * Itó, Iyán and Iyón — This, That, That (over there)
 * Mga Bilang/Numero — Numbers

Balarilà - Grammar

 * Tagalog grammar
 * Mga Pang-urì (Adjectives)
 * Mga Pang-abay (Adverbs)
 * Ang Panahunan (Conjugation)
 * Mga Pangatníg (Conjunctions)
 * Mga Pang-angkóp (Ligatures)
 * Mga Pangngalan at Pangmarká (Nouns and Markers)
 * Mga Panlapì: Mgá Unlapì, Gìtlapì, Hulapì, át Kabilàan (Affixes: Prefixes, Middle Affixes, Suffixes and Side-to-Side Affixes)
 * Mga Pang-ukol (Prepositions)
 * Mga Panghalíp (Pronouns)
 * Mga Panakláw (Quantification Words)
 * Mga Pananóng (Question Words)
 * Mga Pandiwa (Verbs)

Major literary works

 * Ibong Adarna
 * Florante at Laura
 * Works of José Rizal
 * Noli Me Tangere
 * El Filibusterismo

Cultural works

 * Mga Alamát (Legends)
 * Mga Maiiklíng Kuwento (Short Stories)
 * Ang Pinagmulán ng Lahì
 * Karunungan: Tangláw ng Kalayaan
 * Nagíng Sultán si Pilandók
 * Mga Tugmâ (Rhymes)
 * Bahay Kubò
 * Lerón-Lerón Sintá
 * Mga Tulâ (Poems)

Silipin din (See also)

 * oldwikisource:Category:Tagalog

Tungkól sa Aklát na Itó (About This Book)

 * Mga May-akdâ ng Wikibook Tagalog (Authors of the Tagalog Wikibook)
 * Kasaysayan ng Wikibook Tagalog (History of the Tagalog Wikibook)

Mag-ambág! (Contribute!)
Please remember that this is a wiki textbook. Feel free to edit it, update it, correct it, and do anything to boost its capabilities to teach those who read this textbook, and/or otherwise increase its teaching potential.

For more information on what a wiki is, visit the Wikipedia page on the wiki.

Tagalog

title: Tagalog


text:
User talk:Sky Harbor

Welcome
Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * Check out our help page if you need additional help.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Take a look at Naming policy
 * See list of templates which can save your time
 * 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.

Good luck!--Derbeth talk 09:06, 12 February 2006 (UTC)

Tagalog Table of Contents
Please do not name pages like that. Use syntax like: Book/Chapter. --Derbeth talk 09:06, 12 February 2006 (UTC)

Pictures
As you can see at the top of this page, "All unlicensed images uploaded to wikibooks before November 1, 2006 will soon be deleted." You have uploaded images and some of them are untagged. You can see them here. Please review them and add appropriate tags. If you have any questions, feel free to ask me. --Think Fast 04:30, 13 November 2006 (UTC)

title: User talk:Sky Harbor


text:
Common Lisp/Advanced topics/CLOS

Common Lisp Object System (CLOS) is a part of Common Lisp that allows to use object-oriented programming techniques in your programs. It defines concepts such as object, class and method and their interaction. CLOS is the most powerful object system available in any programming language, and mastering the more peculiar aspects of it may take time. Fortunately, it is not necessary to be a CLOS expert to use it.

Two orthogonal concepts of CLOS are classes and generic functions. Let's start with the first one...

Classes and objects
A class is a "template" that describes the structure and behavior of its instances. Every kind of Lisp data is an instance of some class. There are built-in classes, such as the class of integers, or the class of strings. You can use the function class-of to determine the class of some Lisp object.

(class-of 5) => # (class-of "aaaa") => #

The results may be printed differently in your particular implementation, but the idea is the same:  is Lisp syntax for unreadable data, which doesn't mean that it's unreadable to humans, but to the Lisp reader. It's easy to determine that 5 is an instance of the built-in class integer and "aaaa" is an instance of the built-in class string.

Built-in classes are usually not very interesting. But there is a way to create user-defined classes, and it's achieved with the defclass macro. Each instance of a user-defined class would have a number of slots which could contain various Lisp data. Let's see a typical use of defclass:

(defclass book    ((author :initarg :author :initform "" :accessor author) (title :initarg :title :initform "" :accessor title) (year :initarg :year :initform 0 :accessor year))   (:documentation "Describes a book"))

It has the following structure:

(defclass name (superclasses)   (slots)    options)

We'll ignore superclasses for now, let's look at slots instead. Each slot has a name and several options attached to it. The options are:
 * - a keyword what would be used to supply slot values when an instance of a class is created.
 * - if no value for a slot was supplied, it would be initialized with the result of evaluating initform. If there is no initform, an error would be signaled.
 * - specifies a function to read a particular slot.  means: create a function aaa so that (aaa instance) would return the value of the slot.
 * - specifies a function to write to a particular slot.  means: create a function bbb so that (bbb value instance) would set a slot of an instance to value.
 * - specifies a function to read and write a value of a slot.  means: create a function foo and create a function (setf foo) so that (foo instance) reads a value of a slot and (setf (foo instance) value) sets a value of a slot.
 * Note:  is wrong! You need different names for reader and writer. Use   instead.
 * - provide a documentation string for a specific slot.

Every option is entirely optional, however at least one of  or   should be supplied to be able to initialize a slot at the time of object creation. Failure to do so would result in a runtime error.

As for class options, the only one that's useful is, which provides a documentation string for the whole class.

Now that we have a class, we can create some instances of it. Everything in Lisp is an object, but the instances of a standard class, such as the one defined by defclass above, are called standard objects. For the remainder of this section the word object refers to standard object.

How to make a new object? A function make-instance is what we need:

(setf *my-book* (make-instance 'book))

Now *my-book*'s value is an object of the class book. The first argument to make-instance may evaluate either to the class itself (such as a result of class-of call) or the symbol that names a class (such as a result of quoting this symbol). In this case we'll use the symbol, which is much easier to produce.

Let's look at *my-book*:

(class-of *my-book*) => # (author *my-book*) => "" (year *my-book*) => 0

The book is rather bland right now. Its fields are set to default class values, but it's easy to change them:

(setf (title *my-book*) "ANSI Common Lisp") (setf (author *my-book*) "Paul Graham") (setf (year *my-book*) 1995)

This is because an appropriate accessor functions were set up in the class definition. In general case accessing slots of an object is somewhat harder. For example, if only reader functions were defined, you are still able to change slots, using slot-value function:

(setf (slot-value *my-book* 'year) 1995) (year *my-book*) => 1995

You can ditch reader functions as well and read slot values using slot-value function too. This however doesn't add readability to your code.

Most of the time you don't want to create an object with all slots set to default values. For example, if you want to make an object representing a specific book, you already know its title, author and year, and you want to initialize a new object with these values, not some useless empty strings. If there is an :initarg option specified in the slot definition, this slot can be initialized with a user-specified value at the time of the object's creation. It is possible by supplying a corresponding keyword argument to make-instance:

(make-instance 'book                :author "Paul Graham"                 :title "ANSI Common Lisp"                :year 1995)

Since the default values for book slots are always useless (there is no year 0, and there is no book with an empty title), the :initform slot options should be removed. Then, a user who forgets to initialize a slot will get an error, and will fix it by providing all necessary information next time. It is also wise to provide only :reader functions for slots that are not intended to change (this is the case with every slot of our book class). In short, provide only those options that could be useful.

title: Common Lisp/Advanced topics/CLOS


text:
Philippine History

Welcome to this book on the history, culture, tradition and government of the Philippines from ancient times until the present day.

Table of contents

 * /Preface/

Unit 1: Prehistory and Ancestral Heritage

 * 1) /Prehistory/
 * 2) /Before The Coming of Spanish Colonialists/

Unit 2: The Spanish Colonial Era

 * 1) /The Spanish Conquest/
 * 2) /The Impact of Spanish Rule/
 * 3) /The Disunited Resistance/
 * 4) /The Propaganda Movement/
 * 5) /The Philippine Revolution/
 * 6) /The Spanish-American War/

Unit 3: The American Colonial Era

 * 1) /The Philippine-American War/
 * 2) /American Rule/
 * 3) /The Commonwealth of the Philippines/

Unit 4: The Philippines in World War II

 * 1) /The Japanese Invasion/
 * 2) /The Japanese Occupation/
 * 3) /The Liberation/

Unit 5: The Modern-Day Philippines

 * 1) /The Third Philippine Republic/
 * 2) /The Recognition of the Tao/
 * 3) /The Year of Discontent/
 * 4) /The Marcos Dictatorship/
 * 5) /The EDSA Revolution & the Fifth Republic/
 * 6) /The New Tiger of Asia/
 * 7) /EDSA II and III/
 * 8) /Contemporary Philippines/

Appendices

 * Presidents of the Philippines
 * Vice-Presidents of the Philippines

Wikipedia links

 * History of the Philippines
 * Philippines

title: Philippine History


text:
Wikibooks:Policies and guidelines/Vote/Naming policy

Naming policy

Introduction
Currently Wikibooks has no official naming policy. We cannot enforce any naming convention on new books, there is no clear guideline for new users how to name pages. This proposal is an attempt to introduce a minimal, simple set of rules. It does not cover all cases - things like naming of templates, categories, book name shortcuts etc. will be discussed later (if neccessary) and please do not connect them with this proposal.

Proposal

 * New books - only slash is allowed as delimiter for page names. Page names must be in format .  Colon as delimiter is reserved to Cookbook only.
 * Existing books - Any convention can be used, provided that book name is included in every chapter title. Consequently, we don't allow chapters with generic names like Contents anymore that don't also have the book name in the title. No cleanup boxes regarding page naming will be used on any existing books.  Existing books must provide their own backlinks on all pages (except slash convention which automatically provides the backlinks).
 * Enforcement - Polite cleanup request can be put on the discussion page (not the module page) of nonconforming new books.  There is no enforcement for existing books.

Advantages

 * is widely spread with existing and mostly used with new books
 * consistent, clear, easy to understand for readers and editors naming policy
 * slash convention provides pre-formatted automatic backlinks to the higher level pages (bookname, chaptername)
 * slash convention provides exclusive possibility to use fast links to subchapters ( /chapter/ ) and sibling chapters ( ../sibling/ ), saving the time for typing the longer form ( bookname/chapter )
 * colon convention: only one applicable for namespaces (which Cookbook is)
 * removes status quo where:
 * two completely different books may link to the same chapter without knowing it (like Contents)
 * automatics tasks (use of bots to fix errors) are hard
 * it may confuse readers and contributors (if a contributor sees two books with completely different naming conventions)
 * two different naming convention in one book are allowed

Disadvantages

 * does not let book authors decide which naming convention is best for them
 * forces book section names to look like computer file names, such as: Windmills/Australian farms
 * if authors want to use a better book section title, such as "History of Windmills on Australian Farms" then the page appears to have two large-font titles
 * slash convention inserts a mandatory (no option to turn it off) second line of text on each page with the pre-formatted backlink, which is unnecessary if pages include their own backlinks or book contents template such as Botany example.

Votes
Only registered users with at least 20 edits can vote. Vote ended at March, 1st 00:01 GMT with the result that the motion had passed with a margin of 14 to 2.

Yes
VOTE NOW CLOSED
 * 1) Aye Krischik T 17:42, 12 February 2006 (UTC)
 * 2) Yes Plus existing books should be encouraged (though not, for now, mandated) to adopt the format that would be mandatory for new books, Jguk 15:40, 13 February 2006 (UTC)
 * 3) Yes Although I'd like to see the colon convention included as an option for new books as well.  We need some sort of policy at the moment, and the debate over allowing colons can take place as a separate issue and vote.  --Rob Horning 16:17, 13 February 2006 (UTC)
 * 4) Yes - Works for me. -Matt 18:00, 13 February 2006 (UTC)
 * 5) Yes - We need consistency, this is a start, but should be expanded to all books.  Gerard Foley 22:09, 13 February 2006 (UTC)
 * 6) Yes  I'm also adding a comment (existing books) below in the Discussion section.  --JMRyan 22:57, 13 February 2006 (UTC)
 * 7) Yes Although I'd also like it to be extended to all books at some time in the future. Consistency is important. ManuelGR 22:48, 14 February 2006 (UTC)
 * 8) Yes --Kernigh 00:27, 15 February 2006 (UTC)
 * 9) Yes As one of main supporters of this policy I am of course for it ;-) Derbeth talk 09:23, 15 February 2006 (UTC)
 * 10) Consistancy is as important as getting it exactly right. -- LV (Dark Mark) 02:45, 17 February 2006 (UTC)
 * 11) Aye But see note below. --kwhitefoot 11:22, 17 February 2006 (UTC)
 * 12) Yes For existing books, we may want to consider changing them but keeping redirects around for links  --Gabe Sechan 22:27, 17 February 2006 (UTC)
 * 13) Yes The Doc  As we done in it:wb, all bookpages should be renamed 12:01, 19 February 2006 (UTC)
 * 14) Yes though I wonder the possibility of, say, "Programming" namespace...(?) - marsian 04:45, 21 February 2006 (UTC)

No
VOTE NOW CLOSED
 * 1) No- A vote of No means authors may use the slash convention, or they may use the colon convention or other acceptable convention. KHatcher 16:36, 21 February 2006 (UTC)
 * 2) No- I disagree to being forced to use a naming convention that has definite disadvantages (See Discussion below). Authors must have options open when they start a wikibook. BDB 18:37, 24 February 2006 (UTC)

Discussion
Very long discussion was carried out at Wikibooks talk:Naming policy.

Colon
I noticed Rob Horning's vote and how he said he wanted colon convention for new books but that it could be discussed later. I thought this vote was quite solid on the stance of new books with respect to colon convention in that it will not be allowed. Period. I personally want colon convention as a guaranteed final no with this vote. Do others think this topic is still open, because I certainly didn't think it was after all the discussion? -Matt 18:05, 13 February 2006 (UTC)

 * Anyone can propose any modification they want after this policy is adopted (assuming it gets adopted). Whether such a modification is accepted, though, is another matter, and will come down to whether there is consensus for it, Jguk 18:29, 13 February 2006 (UTC)

 * You got it spot on Jguk. I want a naming policy of some sort to already be an enforced policy, regardless of where it goes from there.  Matt and I can argue over the use of colons as a separate issue, and I guess we have two different opinions here.  We should not have the tyranny of the majority forcing concepts and issues onto everybody, and just because I feel that some sort of policy needs to happen doesn't mean that I agree with the whole thing.  This policy is going to be amended eventually at some point in the future, and it should be.  New users are going to come to Wikibooks and older ones (perhaps myself) are going to leave.  Policies of this nature should not be "set in concrete" with no possible chance to be reviewed for being relevant later on.  The current policy of almost everything goes, slash, colon, caret, asterix, kumquat, parenthesis, midi-chlorian, or no naming convention at all is IMHO unacceptable and something that needs to be changed.  --Rob Horning 13:00, 19 February 2006 (UTC)

existing books
I have voted "Yes" above. I am, however, uncomfortable with the wording for existing books. My preference is for the slash policy to apply to all books but to leave it unenforced for existing books that meet the stated minimum requirements. That way, we at least begin to process of phasing out or deprecating non-slash namings. I understand and am happing to support leaving the existing books issue as a problem to be solved later: we need to start making decisions somewhere. But even with this, I would prefer the policy sounding more explicitly like we're leaving the existing books issue as a problem to be solved later and less like a decision to grandfather in existing books' names. --JMRyan 23:15, 13 February 2006 (UTC)

talk page
I have started to use the talk page to mark violations - as suggested in this vote. And I feel that it does not work. NC violations are often done by new users which are not in the habit of checking the talk page. Of course I stay with yes as I believe this minimalistic approach is a very good start and if something does not work out as hoped we can much easier sort that out later. --Krischik T 11:51, 15 February 2006 (UTC)

 * User talk pages are also a good place to turn to if you want to get ahold of new users. That orange banner ("You've got new messages") is usually sufficient to get a new user to pay attention.  --Rob Horning 13:24, 19 February 2006 (UTC)

 * That only works if the user is actualy registered. Which is a argument for restricting top level creation to registered user only. --Krischik T 06:52, 25 February 2006 (UTC)

Disenfranchisement by obscurity
I think that the whole issue is being discussed in terms that make it almost impossible for those who are not well versed in computing to understand it, which means that only those people will vote. Also as the proposed structure fits what most such people deal with every day dissenting opinions will appear to be rare not because other possibilities do not have merit but because the population that feels competent to discuss the question is selected from a population that is likely to vote for one particular alternative. In fact many of the terms seem vague even to me and I have over thirty years of computer experience. Is there a page that actually clearly defines the terms 'name space', 'title', 'bookshelf', 'bookname', etc.? The title of the book that I have contributed most to is 'Visual Basic Classic' but I suspect that 'bookname' refers to 'Programming:Visual Basic Classic'. If I replace the colon with a slash what is the 'bookname' then? Perhaps we need to take an even stricter computing stance and define a formal syntax. It isn't enough to talk vaguely of 'computer file names', not every file system uses a hierarchical structure and many users of such systems don't understand them when they do. I hope some of that made sense. --kwhitefoot 11:48, 17 February 2006 (UTC)

 * I read the proposal as meaning that all pages in the book "Book Name" must start with "Book Name/". After that, individual books are free to do anything sensible that best fits in with that book. I don't agree with you that your book title there would be "Programming:Visual Basic Classic". It would still be "Visual Basic Classic" - it would sit on a "Programming" or "Computer Programming" bookshelf, Jguk 12:17, 17 February 2006 (UTC)

 * If I remember correctly, there was some discussion earlier about the naming of "Programming:Foobar" books. I didn't pay much attention to it at the time since I don't work on those books.  I think (others may have more accurate information for you) that this was at least semi-resolved in favor of renaming the "Programming:Foobar" books to names like "Foobar" or "Foobar Programming".  The books Programming:Ada and Programing:C# were moved to Ada Programming and C# Programming while Programming:Prolog and Programming:Visual Basic .NET were moved to Prolog and Visual Basic .NET.  In addition, Programming itself was moved to Computer programming.  If you should follow along, then you would move Programming:Visual Basic Classic to "Visual Basic Classic" or (less likely) "Visual Basic Classic Programming" or even "Programming in Visual Basic Classic".  Although the colon in Programming:Visual Basic Classic was originally intended as a delimiter, it can no longer properly serve as such because there is no longer a "Programming" book.  This does, unfortunately, leave the status of your title somewhat vague.  (1) Perhaps your books is best regarded as a subook within the now non-existent (except as a redirect) book "Programming"—an unfortunate status.  In this case, your bookname is "Programming".  (2) If you replace the colon with a slash, then your bookname is unambiguously "Programming" and your book is unambiguously a subbook of the non-existent "Programming"—again an unfortunate status.  (3) Perhaps the colon in your book should be interpretted as just a colon (as in Harbison and Steele's "C: A Reference Manual").  Then your bookname is "Programming:Visual Basic Classic".  In that case, your book at least partially follows the slash convention because of pages like Programming:Visual Basic Classic/Strings.  My guess is that the lack of a space following your colon makes (1) the more likely interpretation.  In any case, your book is on the Programming languages bookshelf because that bookshelf has links to your book.  My advice—free and worth every penny you paid for it— is that it would be best to rename the book to "Visual Basic Classic" or "Programming in Visual Basic Classic".  If there are multiple active authors, this would require a consensus among them.  If you like, there is a bot, tsca.bot, that can help with the drudgery.  It's assistance has to be requested, I don't know how such a request proceeds.  I hope this ameliorates the obfuscation and renders everything perspicacious. :-)  --JMRyan 20:38, 17 February 2006 (UTC)

Naming Policy or Naming Guideline
As I see it, Naming policy is soon going to be an enforced policy. Wikipedia and wikibooks, in addition to being sources of information, are also about freedom - freedom to write an article or a book the way you want. This freedom underlines the beauty of variety in our life. I believe most of the Wikibookians have forgotten what the fifth and most important pillar of wikipedia (Please see Five pillars of wikipedia) is all about. Making more rules and enforcing them will make wikibooks more uniform but will impose more restrictions on newcomers and existing authors. This is my basic objection to enforcing Naming policy. Secondly, the proposed policy of using slash as a delimiter for pagenames has a few disadvantages that supporters have ignored. In a subject like Medicine, topics may appear under several chapters because disease or the human body unlike man-made software or anything else overlap with each other and may not be clearly distinguished from one another. Technically speaking, medicine deals often with continuous variables unlike the discontinuous variables that students of engineering or computer science deal with. For specific examples, a topic like Reflex Sympathetic Dystrophy may appear under the Chapters Hand and Microsurgery, Paediatric Surgery and Sports Medicine. The colon convention makes it easy to list the topic under the various chapters without repeating! The colon helps to identify and link with the book it belongs to. This way there will be no internal links between books. I would rather look at the books as a collection of articles on a topic rather than a didactic and dogmatic collection of strictly named chapters conforming to an enforced policy. Thirdly, the automatic link-back is no justification for following the slash convention. More cleaner and attractive navigation templates have been created by authors ( See Botany) and there is no reason to curb this creativity by providing an auto link-up. Fourthly,the least important of the reasons, the slash convention will make the heading of each page long, and if the hierarchy is deep, if I may say so, UGLY. The colon will keep the title of each page short, succinct and tidy. I concede that there are books where the slash may be a better option, hence I support the idea of allowing authors to dedcide for themselves what would serve the purpose of their book better. --BDB 19:47, 24 February 2006 (UTC)

 * The proposed policy would only effectively mandate that all pages in a book begin with Book Title/. After that, page organisation is very much up to the individual authors. On your comparison to wikipedia, I'd note that this is a separate project, and we are free, and should be free, to have separate rules where appropriate, Jguk 07:38, 25 February 2006 (UTC)

 * I'm not so sure that the current proposed policy is necessarily that free with the idea. Cookbook is an example of how something came from a pseudo namespace to a full namespace within this project, and the colon was a critical part of that.  I don't know if the full namespace was necessarily critical to the Cookbook as a WikiProject, but it does give that book a distinctive flair.  If the Cookbook is given an exemption, it is just a matter of time before other book projects start screaming for the same "equal treatment" as well, and I fail to see why Cookbook is some unique position, other than it is the pet project (that is not necessarily a problem here on Wikibooks) of a couple of administrators who got ahold of some developers to make it a namespace. I strongly encourage individuality on the part of authors, and the fact that the Colon is naturally a logical separator makes it seem like a reasonable alternative.  I tend have the philosophy that policies, rules, or laws should only be enacted when somebody has been seriously abusing the situation and you want to make sure you can effectively punish idiots in the future if they try to do the same thing that has hurt people in the past.  The rule about some sort of naming policy is valid, as naming modules anything under the sun (like pretending this is Wikipedia and you can have chapters like Table of Contents, Index, or Appendix) just doesn't make sense, and it is a pain to try and relink orphaned content that has been named like that.  Orphaned modules are a very serious problem here at Wikibooks, and it will be considerably worse in the future.  As to the specific style beyond having the name of the book somewhere in the module title (preferably in the beginning for search purposes) I am prepared to fight that battle and allow other standards as well.  --Rob Horning 08:03, 25 February 2006 (UTC)
 * "Wikipedia and wikibooks, in addition to being sources of information, are also about freedom - freedom to write an article or a book the way you want" – no, it's not freedom, it's an anarchy. In Wikipedia you cannot write article however you want - there are standards for biographical articles, articles about countries etc. I don't think that having free choice for naming pages is important for book authors. As I have written before, book authors should write books not try to invent new naming scheme. Naming scheme is something completely irrelevant, most readers don't look what is the actual name of page, they read the content. "Making more rules and enforcing them will make wikibooks more uniform but will impose more restrictions on newcomers and existing authors." If I were a newcomer wanting to contribute I would get really confused when I found many books using completely different page naming. And what if a book uses two different styles? "Fourthly,the least important of the reasons, the slash convention will make the heading of each page long, and if the hierarchy is deep, if I may say so, UGLY." This shows you don't understand the proposition. You can have book hierarchy as deep as you want and have page name consisting only of two parts: book name and chapter name. Slash convention is not about showing internal book structure in page name, its about showing book name in the page name, nothing more. "I would rather look at the books as a collection of articles on a topic rather than a didactic and dogmatic collection of strictly named chapters conforming to an enforced policy." Books are not loose collection of articles. Try to print and then read such "book". Consciousness studies is a good example of well-constructed wikibook. --Derbeth talk 11:55, 25 February 2006 (UTC)
 * Jguk, though you mention that it mandates changing only the title/subpagename, the changes you have made in Orthopaedic Surgery extends into title/subpagename1/subpagename1 as in Orthopaedic Surgery/Basic Sciences/Bone Injury and Repair. Are we implementing the policy because we want or need to be different from wikipedia? Wikibooks is a different project and will but not necessarily have a separate set of rules. The point I am trying to raise is whether we need naming guidelines instead of rigid policies.
 * Derbeth, I will be back soon to answer the points you have raised.BDB 17:07, 25 February 2006 (UTC)

 * I'm quite happy to see any other structure you want implemented on the Orthopaedic Surgery pages as long as each page in the book starts with "Orthopaedic Surgery/". I was trying to preserve the existing structure of that book, whilst renaming it. Unfortunately, it soon became clear to me that I wasn't quite sure what that existing structure was (there appeared to be two competing structures, but if I'm wrong here, I apologise). This is why I stepped away from making lots of other changes. If you can tell me what the structure is that you think should happen for the book, I'd be happy to help implement it. On the Wikipedia point, we are different from wikipedia - this means that we do not necessarily have the same rules and structure as wikipedia, not that we deliberately set out to have different rules and structures - we should do whatever is appropriate to wikibooks, Jguk 18:01, 25 February 2006 (UTC)

 * I am still not clear on this. The structure I prefer is Orthopaedic Surgery: and not Orthopaedic Surgery/. Why is this rule being enforced when it is still a proposal? The naming policy is still listed under Proposals and not under the Enforced column and are we not discussing on the vote? But probably because some of us do not want namespaces like Cookbook to exist we would prefer Title/ structure over Title:. I am not decided on what is best and thats the reason for being here. Probably, Title/Chaptername: would serve the purpose. I have also found difficulty in piping with the slash structure while it is simpler with the colon. I would imagine, searching for a topic in wikibooks would be very inconvenient with the slash convention. I would love to hear from you on these. Going back to wikipedia, I would like to add to what you said: "we should do whatever is appropriate to wikibooks" - irrespective of whether it is from wikipedia or not. -BDB 18:24, 25 February 2006 (UTC)

 * To be honest, the first ones I saw and changed were in the format Page title (orthopaedic surgery), had I seen things entirely consistent on Orthopaedic Surgery: Page title I'd have left it alone. Whatever happens, I trust we agree that there should be consistency, and it's better that the book title comes first, Jguk 21:03, 25 February 2006 (UTC)

 * Yes I was quite undecided on how the book should be structured at that point of time and there were pages that were named Subpagename1(Title). I totally agree with you that the book title should come first followed by chaptername or subpagename. -BDB 06:55, 26 February 2006 (UTC)

 * Derbeth, with freedom comes responsibility, anarchy arises when we stop being responsible. And I think wikibook authors have been far from being irresponsible. Do not mistake the seemingly chaotic activity in wikibooks as anarchy. There are always patterns in chaos and it takes a while for them to become clear. I was of, and still am of the opinion that the lesser rules we force on authors the more beautiful wikibooks will turn out to be. Let us have guidelines but not enforced policies. Wikipedian standards evolved over a period of time. They were not implemented overnight. An author should exercise as much right to the structure of the book as he does to its contents. Whether everyone is interested is not relevant. What naming convention a book should have ideally must be decided by its authors not by you, me or any admin. I sincerely did not understand this part - "You can have book hierarchy as deep as you want and have page name consisting only of two parts: book name and chapter name. Slash convention is not about showing internal book structure in page name, its about showing book name in the page name, nothing more. ". Could you explain this to me more clearly? Lastly, though the goal of wikibooks would be to look like a printed book, I believe it is quite different from printed matter. -BDB 18:47, 25 February 2006 (UTC)
 * Ok. Let's have a fictional Medicine book. You want to write a chapter "Thymus". You don't name page like: "Medicine/Immunology/Organs of the Immune System/Thymus", although this is how this chapter is located in hierarchy of your book. You just call it "Medicine/Thymus". Is it really long? You write: "An author should exercise as much right to the structure of the book as he does to its contents." But Wikibooks has nearly three years, there was a lot of time for the authors to play and see how different naming conventions work. Now slash convention is the most popular and I don't see any reason why we should allow more naming conventions which don't have advantages this one has. Freedom is important thing, but what for do you need the freedom in choosing delimiter you use in your book? Is choice between colon and slash important for you? I don't accept freedom just for freedom, we are not here to give anyone freedom to do whatever he wants, we are here to write good books. Wikipedia is not a democracy, neither is Wikibooks. In Wikipedia, you cannot name page "Cobra - snake" or "Cobra, snake", such page would be renamed immediately without even asking you and noone says Wikipedia is not free. --Derbeth talk 15:36, 26 February 2006 (UTC)

 * Derbeth, I am compelled to follow the pagename structure you propose. Thumbs up to Medicine/Thymus!! But I completely disagree with your freedom concept.Though you mention - "wikipedia is not a democracy", and this is an official policy (see Wikipedia is not a democracy), I would request you to read further and see Wikipedia is not a bureaucracy, and I quote - "Disagreements should be resolved through consensual discussion, rather than through tightly sticking to rules and procedures. Instruction creep should be avoided. Follow the spirit, not the letter, of any rules, policies and guidelines". I rest my case! -BDB 18:42, 26 February 2006 (UTC)

 * But we are discussing here. You are giving a very wrong example. Yes, we shouldn't produce tons of guidelines and policies, but they are always some rules that have to be obeyed to keep order on the project. Consider disambiguation pages naming convention at Wikipedia - are you allowed to ignore it? No, because it is fundamental. I see naming policy as such fundamental rule; fundamental because in fact there aren't many policies here and we are not demanding much. Just name pages how we require and everything is ok - that's what we are saying. Proposed naming convention is really simple, in a nutshell: "add bookname-slash to name of every page you create in your book". Consider it - we give book authors a vast area of freedom, naming policy does not prevent them from organising book as they want. In my opinion page names are not part of creative work, it's like filenames on the computer - it's not important how they are named, the important thing is what's inside. Imagine operating system which allows you only to start file names with a capital letter. This is some kind of restriction, but does it have any practical meaning what is the first letter of a file name? If I edit or print it, it's completely irrelevant. --Derbeth talk 22:06, 26 February 2006 (UTC)


text:
Philippine History/Preface

Welcome to what is arguably the first free, open-content textbook on Philippine history, culture and government. As a resource to help Filipinos and foreigners alike understand more about the Philippines, its people and its heritage.

As a free, open-content resource, this textbook is designed to be open to all persons, and as such, edits, updates, fixes and the like are highly welcomed and indeed appreciated. It is believed that through the collaborative efforts of all persons involved that this project will indeed be successful and as such bring the Philippines to the world.

This project would have never taken off without the involvement of all persons who have worked so hard on this project. And although the Philippines as a nation is still young, may its history be preserved for time immemorial.

title: Philippine History/Preface


text:
Wikibooks talk:Policies and guidelines/Vote/Naming policy

Wording of policy
I think I understand the direction that this policy is going, but I'm trying to find another example other than "contents" for a generic chapter name. The emphasis here, IMHO, is that we don't want to have people naming "chapters" with random names like this is a duplicate of Wikipedia. Periodic Table is one that comes to mind that has been used in the past which is generally something that should not be used in this generic sense, but instead should conform to the naming policy instead.

The point here is that we don't want to discourage the use of a table of contents for a Wikibook, or to stop the practice of a "front page" followed by a seperate table of contents. Personally, I think that is an impressive format and is asthetically nice for those Wikibooks who have done that. This is just to stop using the page Contents, which has been abused repeatedly in the past by many new Wikibooks, as evidenced by its deletion history. See http://en.wikibooks.org/w/index.php?title=Special%3ALog&type=delete&user=&page=Contents for details. I just think we can give a better example. --Rob Horning 11:55, 12 February 2006 (UTC)

 * Introduction? Or maybe I have books on the same subject at Wikijunior, GCSE, A-Level and undergraduate level. Those books may share similar page names. I could have, say, Wikijunior Kings and Queens of England/Henry VIII, GCSE History/Henry VIII, A-Level History/Henry VIII and Wikiversity History/Henry VIII, not to mention references to the Shakespeare play, Henry VIII', Jguk 16:46, 13 February 2006 (UTC)


text:
Tagalog/Lesson 3

Aralin 3 — Itó, Iyán and Iyón''

This lesson will teach you about itó, iyán and iyón, the Tagalog words for "this", "that" and "that (over there)", respectively, as well as their usage and how to use them properly.

Pangungusap (Dialogue)
The characters for this dialogue are Rosario and Pilar. The dialogue will be in Tagalog first, then an English translation will appear below the Tagalog original.

Sa Tagalog (In Tagalog)

 * Rosario: Pilar, anó itó?
 * Pilar: Itó ang susi sa bagong bahay ko.
 * Rosario: Anó namán iyán?
 * Pilar: Iyán namán ang bahay.
 * Rosario: Ang gandá!
 * Pilar: Alám ko. Gustó mong pumasok?
 * Rosario: Sige.

Salin sa Inglés (English translation)

 * Rosario: Pilar, what is this?
 * Pilar: This is the key to my new house.
 * Rosario: What is that?
 * Pilar: That is the house.
 * Rosario: It's so beautiful!
 * Pilar: I know. Do you want to go inside?
 * Rosario: Okay.

Talasalitaan (Vocabulary)

 * Bahay: House
 * Gandá: Beautiful (literally, "beauty")
 * Itó: This
 * Iyón/Iyán: That
 * Pumasok: To go inside
 * Sige: Okay
 * Susì: Key

Aralín (Lesson)
Tagalog uses three words to represent the words "this" and "that": itó, iyán and iyón. Itó means "this", while both iyán and iyón mean "that", depending on the context.

Ang paggamit ng itó (Usage of itó)
The word itó can be used in different ways, dependent on its location within the sentence. In most cases, if it is in the middle or at the end of a sentence, it is written by itself without modification, as in the cases of this sentence:

 * Ang taong itó ay tulóg. (This person is asleep.)
 * Anó itó? (What is this?)

The ligature -ng is attached when describing objects. This never happens at the end of a sentence and only occurs if itó is placed at the beginning or at the middle. Some examples include:

 * Itóng aklat ay akin. (This book is mine.)
 * Násaan itóng pook? (Where is this place?)

Attaching the ligature -ng and the case marker mgá makes itó plural, becoming "these", as shown by this sentence:

 * Itóng mgá awto ay sa kanyá. (These cars are his/hers.)

Ang paggamit ng iyán at iyón (Usage of iyán and iyón)
Iyán or iyón are used depending on the relative distance of the referred object or person to the speaker and to the listener. The difference is as follows:

 * Iyán is used when the referred object or person is far from the speaker but near the listener.
 * Iyón is used when the referred object or person is far from both the speaker and the listener.

Let's have an example. Two kids named Santiago(Spanish for "James") and Corazon are pretty far apart. A cat passes near Lisa.

(Pilipino)
 * Santiago: Lisa, anó iyán?
 * Corazon: Iyan ay Pusà.

(Ingles)
 * ''Santiago: Lisa, What's that? (near you or close to you)
 * Corazon: That's a cat.

Later on, Santiago and Corazon both see a spider crawling on the ceiling.

 * Santiago: Lisa, anó iyón?
 * Corazon: Gagambá.

 * Santiago: Lisa, what's that (over there)?
 * Corazon: That's a spider.

Ligatures are also used when describing objects. However, unlike itó, which attaches the ligature -ng, iyán and iyón attach the ligature -g, since both words end with the letter "N". The use of such ligatures are exemplified below:

 * Iyáng kompyuter na iyán ay akin. (That computer near you is mine.)
 * Iyóng pera na iyón ay para sa tao. (That money over there is for the people.)

When the case marker mgá is attached after iyáng or iyóng, it makes them plural, becoming "those", as shown below:

 * Iyáng mgá gamit mo ay dapat linisin. (Those things of yours need to be cleaned up.)
 * Iyóng mgá damít ko ay kailangang ipadalá sa opisina. (Those clothes of mine need to be delivered to the office.)

title: Tagalog/Lesson 3