text:
Spanish/Preterite

../Verbs/

The preterite verb form describes past actions that have begun or completed. The preterite sets something in the past as an event, with a beginning and an end. Spanish has another past tense form, the imperfect, that is used for past actions that are continuing, or for which its beginning or its end is not important.

Conjugate regular verbs in the preterite
-AR verbs

Eliminate the "-ar" and replace it with one of the following endings:

-é -aste -ó -amos -asteis -aron

Patinar (to skate) becomes:

patiné: I skated patinaste: you skated patinó: he skated patinamos: we skated patinasteis: you skated patinaron: they skated

Notice that the "nosotros" form conjugates the same as it does in the present tense. This can cause confusion so look for context tools to make sure you have the right tense.

-ER and -IR verbs

Eliminate the "-er" or "-ir" and replace it with one of the following endings:

-í -iste -ió -imos -isteis -ieron

Vender (to sell) becomes:

vendí: I sold vendiste: you sold vendió: he sold vendimos: we sold vendisteis: you sold vendieron: they sold

Conjugate irregular verbs in the preterite
There are 2 types of irregular verbs in the preterite tense. We will start with the more regular of the 2. The endings of these irregulars are all the same, which is why I am referring to them as more regular. The endings are: -e -iste -o -imos -isteis -ieron The stems of these verbs also change as follows: estar --> estuv andar --> anduv tener --> tuv poder --> pud poner --> pus saber --> sup caber --> cup hacer --> hic (exception: 'hizo') venir --> vin querer --> quis decir --> dij traer --> traj and any verb that ends in -ducir --> -duj Note that for stems ending in j the ending 'ieron' is shortened to 'eron' The more irregular verbs conjugate as follows: "Ir" and "Ser" fui fuiste fue fuimos fuisteis fueron

"Dar" di diste dio dimos disteis dieron

"Haber" hube hubiste hubo hubimos hubisteis hubieron

"Reír" reí reíste rió reímos reísteis rieron

"Leer" (similarly Creer) leí leíste leyó leímos leísteis leyeron

"Dormir" (similarly Morir) dormí dormiste durm ió dormimos dormisteis durm ieron

"Ver" v i viste v io vimos visteis vieron

title: Spanish/Preterite


text:
Spanish/Present Progressive

../Verbs/

"He is running. They are dancing. I am liking ... "

The above are examples of the present progressive tense, which is used for continuous actions that are taking place right now. This tense works the same way in English and in Spanish.

Take the verb "to be" (estar) and conjugate it in the present tense, then add the present participle on the tail end.

 Estoy caminando.  I am walking.  Estamos jugando.  We are playing.  Estas fingiendo.  You are faking.

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

title: Spanish/Present Progressive


text:
Spanish/Present Participle

../Verbs/

Running, jumping, skiing, thinking, talking, ...

Corriendo, brincando, esquiando, pensando, hablando ...

The present participle is formed by taking off the last two letters of a Spanish verb (-ar, -er, or -ir) and replacing it with -ando (-ar verbs) or -iendo (-er and -ir verbs).

Estar >  estando Comer >  comiendo Ser >  siendo Contar >  contando

The slightly irregular ir > yendo

title: Spanish/Present Participle


text:
Spanish/Past Participle

../Verbs/

Broken, thought, gone, ...

Roto, pensado, ido, ...

The past participle in Spanish is usually the same as the past tense. I thought, I had thought. But sometimes it is the same. I broke, I had broken. In English it is a different conjugation as a rule.

Take the -ar, -er, and -ir ending off of the infinitive and replace it with -ado (-ar verbs) or -ido (-er and -ir verbs).

Regular conjugation examples
Pensar >> pensado Comer >> comido Venir >> venido

Irregular conjugation examples
Romper >> roto Morir >> muerto

title: Spanish/Past Participle


text:
Spanish/Future

Spanish/Verbs

I will think, he will shout, you will die, ...

Pensaré, gritará, morirás, ...

—  or  —

Voy a pensar, va a gritar, vas a morir, ...

There are two ways to communicate future events in Spanish. In the first one, add an ending to the unchanged infinitive form of the verb. These same endings are used for all three types of verbs (-AR, -ER and -IR), which makes learning them easier:

-é -ás -á -emos -án

Pensaré: I will think Pensarás: you will think Pensará: it will think Pensaremos: we will think Pensarán: they will think

Iré: I will go Irás: you will go Irá: she will go Iremos: we will go Irán: y'all will go

There are 12 verbs which change their infinitives before adding the ending, and they can be classified into 3 catigories: First, the "drop 'e's" are "querer," "poder," "caber," "haber," and "saber." Each of these loses the 'e' before the final 'r' when forming the future tense. These can be remembered by the mnemonic "Quick People Can't Have Sushi." Next, the "add 'd's" are "venir," "valer," "salir," "tener," and "poner." For these, the 2nd to last letter of the infinitive is replaced with a 'd'. These can be remembered by the mnemonic "Vroom Vroom, Said The Porsche." Finally, the verbs "decir" and "hacer" change their infinitives to "dir" and "har" respectively before adding the ending. These must simply be memorised.

The alternate way to describe the future is to use the present tense of "ir," followed by the infinitive of the action verb.

Voy a saber: I am going to know Vas a mentir: You are going to lie Va a cazar: He/she is going to hunt Vamos a contar: We are going to count Van a poner: They are going to put

title: Spanish/Future


text:
User talk:Tomz~enwikibooks

hai~

Hey, i am not sure if the text u copied here is copyleft? --Yacht (talk)Q 02:07, 23 Feb 2004 (UTC)

Your account will be renamed
Hello,

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

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

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

Sorry for the inconvenience.

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

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

title: User talk:Tomz~enwikibooks


text:
Bicycles/Penetrating oil

Penetrating oil is useful for removing rust from parts and displacing water. It is more solvent than lubricant and should not be used as a substitute for lubricating oil where lubricating qualities are needed.

title: Bicycles/Penetrating oil


text:
User:Kokiri~enwikibooks

Hi there, I'm Kokiri. I also contribute to Wikipedia.

title: User:Kokiri~enwikibooks


text:
Spanish/Verbs List

Spanish/Verbs

A

 * Abrazar (to hug)
 * Abrir (to open) abro abras abra
 * Acabar (to finish)
 * Acabar de (to have just)
 * Acordar (to agree upon)
 * Acompañar (to accompany)
 * Acostarse (to go to bed)
 * Afeitarse (to shave oneself) ref.
 * Ahorrar (to save money)
 * Almorzar (to eat lunch)
 * Alquilar (to rent)
 * Amar (to love) - typical 1st conjugation verb
 * Añadir (to add)
 * Andar (to walk, to go, to ride)
 * Aparecer (to appear)
 * Apagar (to turn off)
 * Aplanar (to throw out)
 * Aplastar (to flatten)
 * Aprender (to learn)
 * Aprobar (to approve, to pass)
 * Arrastrarse (to crawl, to drag oneself) ref.
 * Arreglar (to fix)
 * Atacar (to attack)
 * Asistir (to attend)
 * Asustar (to frighten)
 * Aumentar (to increase)
 * Ayudar (to help)

B

 * Bailar (to dance)
 * Bañarse (to bathe) ref.
 * Barrer (to sweep)
 * Batir (to whisk)
 * Beber (to drink)
 * Besar (to kiss)
 * Borrar (to erase)
 * Bromear (to joke)
 * Bucear (to dive)
 * Burlarse (to make fun of) ref.
 * Buscar (to look for)

C

 * Calentar (to heat)
 * Calificar (to grade)
 * Caminar (to walk)
 * Cansarse (to tire) ref.
 * Cantar (to sing)
 * Casarse (to marry) ref.
 * Cazar (to hunt)
 * Celebrar (to celebrate)
 * Cenar (to dine, to have supper)
 * Cepillar(se) (to brush) can be ref.
 * Cerrar (to close)
 * Charlar (to chat)
 * Chupar (to suck)
 * Cocinar (to cook)
 * Coger (to catch)
 * Comer (to eat, esp. to eat lunch)
 * Comprar (to purchase, to buy)
 * Comprender (to comprehend, to understand)
 * Conducir (to drive)
 * Conocer (to know, to meet)
 * Contar (to relate)
 * Contestar (to answer, to reply)
 * Correr (to run)
 * Cortar (to cut)
 * Costar (to cost) (ue)
 * Crear (to create)
 * Creer (to believe)
 * Cuajar (to curdle)
 * Cubrir (to cover)
 * Cumplir (to fulfill)

D

 * Dar (to give)
 * Deber (to owe, should)
 * Decidir (to decide)
 * Decir (to say, to tell)
 * Dejar (to leave)
 * Desayunar (to eat breakfast)
 * Descansar (to rest)
 * Desear (to desire, to wish)
 * Deshacer (to undo)
 * Despedir (to fire)
 * Despedirse (to say goodbye)
 * Despertarse (to wake up) - Irregular: e -> ie
 * Destruir (to destroy)
 * Detener (to stop)
 * Dirigir (to lead, to guide)
 * Disculparse (to excuse oneself)
 * Discutir (to argue)
 * Distinguir (to distinguish)
 * Divertirse (to have fun) - Irregular: e -> ie
 * Doler (to hurt)
 * Dormir (to sleep, go to sleep) - Irregular: o → ue
 * Duchar(se) (to shower (oneself)) - Can be ref.

E

 * Echar (to deal (cards))
 * Elegir (to choose, to elect)
 * Empeorar (to worsen)
 * Empezar (to begin)
 * Empujar (to push)
 * Enamorarse (to fall in love)
 * Encantar (to be delighted about) - gustar-type verb
 * Encender (to light)
 * Enfermar (to get sick)
 * Enojarse (to be angry)
 * Enseñar (to teach)
 * Entender (to understand)
 * Entrar (to enter)
 * Escuchar (to listen)
 * Escribir (to write)
 * Esperar (to wait, to hope)
 * Esquiar (to ski)
 * Estar (to be)
 * Estudiar (to study)
 * Exportar (to export)

F

 * Fastidiar (to annoy, to tease)
 * Felicitar (to congratulate)
 * Fingir (to pretend, to fake)
 * Firmar (to sign)
 * Flipar (to be crazy about) - gustar-type verb
 * Freir (to fry)
 * Fusilar (to execute by firing squad)

G

 * Ganar (to win, to earn)
 * Gastar (to spend, to use up)
 * Gritar (to shout)
 * Guiar (to lead, to guide)
 * Gustar (to be pleasing) -equivalent to the english "to like"

H

 * ../Haber/ (to have [helper verb])
 * Hablar (to talk)
 * Hacer (to make, to do)
 * Hacer calor (to be hot)
 * Hallar (to find)
 * Helar (to freeze)
 * Herir (to injure)
 * Hinchar (to anger)
 * Huir (to flee)
 * Hundir (to sink)

I
 * Insultar (to insult)
 * ../Ir/ (to go)
 * Irse (to go [away]) reflexive verb
 * Invitar (to invite)
 * Injerir (to inject, insert)

J

 * Jalar (to pull)
 * Joder (to fuck)
 * Jugar (to play)
 * Jurar (to swear)
 * Juzgar (to judge)

L

 * Lastimar (to hurt emotionally)
 * Lavar (to wash)
 * Leer (to read)
 * Llegar a ser (to become)
 * Levantar (to raise)
 * Limpiar (to clean)
 * Llegar (to arrive)
 * Llevar (to bring, to carry)
 * Llorar (to cry)
 * ../Llover/ (to rain)
 * Lograr (to accomplish)
 * Luchar (to fight, to struggle)

M

 * Manejar (to drive)
 * Matar (to kill)
 * Mejorar (to get better)
 * Meter (to place inside)
 * Mirar (to look)
 * Mojar (to wet)
 * Molestar (to annoy, to bother)
 * Morir (to die)

N

 * Nacer (to be born)
 * Nadar (to swim)
 * Navegar (to navigate)
 * Necesitar (to need)
 * Negar (to deny)
 * Nevar (to snow)

O

 * Obtener (to get, to obtain)
 * Odiar (to hate)
 * Ofrecer (to offer)
 * Oír (to hear)
 * Oler (to smell) - Irregular: o -> hue
 * Olvidar (to forget)
 * Operar (to operate)
 * Orar (to pray)

P

 * Pagar (to pay)
 * Parecer (to appear)
 * Parecer a (to resemble)
 * Participar (to participate)
 * Partir (to cut, to leave) - typical 3rd conjugation verb
 * Pasar (to pass, to happen)
 * Pasear (to ride, to stroll)
 * Pedir (to ask for) - Irregular
 * Peinarse (to comb oneself) ref.
 * Pelear (to fight)
 * Pensar (to think)
 * Perder (to lose)
 * Perseguir (to chase)
 * Pintar (to paint)
 * Pisar (to step on)
 * Planchar (to iron)
 * Platicar (to chat)
 * Poder (to be able)
 * Poner (to put, to place, to set)Note: The Yo form of poner is "pongo"
 * Practicar (to practice)
 * Preguntar (to ask)
 * Preparar (to prepare)
 * Prestar (to lend)

Q

 * Quedarse (to stay) ref.
 * Quejarse (to complain, to grumble) ref.
 * Quemar (to burn)
 * Querer (to want, to like) - Irregular: e -> ie
 * Querer decir (to mean, to signify)
 * Quitar (to take away)

R

 * Rasurarse (to shave oneself)
 * Recibir (to receive)
 * Reciclar (to recycle)
 * Recordar (to remember)
 * Recoger (to gather, to pick up)
 * Regalar (to give [as a gift])
 * Regresar (to return)
 * Reír (to laugh)
 * Repartir (to distribute)
 * Resistir (to bear)
 * Rogar (to pray, to beg)
 * Romper (to rip, to break)

S

 * Saber (to know)
 * Sacar (to take out)
 * Salir (to leave, to go out)
 * Saludar (to greet)
 * Secar (to dry)
 * Seguir (to follow)
 * Sentarse (to sit)
 * Sentir (to feel)
 * Ser (to be)
 * Significar (to mean, to signify)
 * Sonar (to ring)
 * Sonreír (to smile)
 * Sonrojarse (to blush)
 * Soñar (to dream)
 * Soportar (to bear)
 * Subir (to go up, to get on)

T

 * Temer (to fear) - typical 2nd conjugation verb
 * Tener (to have, to own)e --> ie except for yo, which is "tengo"
 * Tener razón (to be right)
 * Tentar (to touch)
 * Terminar (to finish, to end)
 * Tirar (to throw, to shoot)
 * Tocar (to touch, to play an instrument)
 * Tomar (to take, to drink)
 * Trabajar (to work)
 * Traducir (to translate)
 * Tragar(se) (to swallow)
 * Traer (to bring)

U

 * Usar (to use)
 * Utilizar (to use)

V

 * Vencer (to conquer, to defeat)
 * Vender (to sell)
 * Venir (to come)
 * Ver (to see)
 * Viajar (to travel)
 * Visitar (to visit)
 * Vivir (to live)
 * Volver (to return)

Y

 * Yacer (to lie)

Z

 * Zafar (to untie)
 * Zanjar (to resolve)

Spanish/Verbs

title: Spanish/Verbs List


text:
Talk:Spanish/Verbs List

Someone who is familiar with Wiktionary, please let me know if it would make any sense to try to link these verbs over to that site. --Karl Wick

 * I took a look at Wiktionary (Spanish). First of all, to link these to Wiktionary would be wicked tedious. Also, it isn't a bilingual dictionary (i.e. it gives the definitions in Spanish), which wouldn't be very useful to students. It appears however, that each verb has a table of its conjugations, which would be useful. It would be tedious, as I said, but doable (if we had multiple people working on it, of course). --Fenoxielo 18:43, 3 Jul 2005
 * I know the previous comments were written years ago, but you should know that each Wiktionary is multilingual, meaning that if you want any word defined in English, you would look on the English Wiktionary, where Spanish words are also included. It would certainly make sense to have words link to Wiktionary. --Yair rand (talk) 02:05, 26 November 2009 (UTC)

Namespace?
I'm not very familiar with the organisation of Wikibooks, but wouldn't it be more logical if there was a namespace called Spanish and pages like this and Los Deportes were renamed 'Spanish:Lista de verbos' and Spanish:Vocabulario:Deportes etc? Is this easy to do? Redlentil 10:42, 1 Jan 2005 (UTC)

Update
I added some links at the bottom of the page to some Spanish verb books. --Fenoxielo 18:36, 3 Jul 2005

title: Talk:Spanish/Verbs List


text:
Talk:The Once and Future King/The Sword in the Stone/Chapter 17

The "anachronisms are explained -- Merlyn lives "backwards" in time. -- TT


text:
Bicycles/Tire patch compound

The glue used to apply patches to inner tubes. It is a form of contact cement. Unlike most glues, the parts to be joined should be put together after the glue has dried for a few minutes.

title: Bicycles/Tire patch compound


text:
Indonesian/Lessons/The house

^ Indonesian ^ | << Lesson 8: My Family | Lesson 9: My Home | Lesson 10: At School >>

Enseignement de l'indonésien/Leçons/La maison

title: Indonesian/Lessons/The house


text:
Bicycles/Maintenance and Repair/Pedals/Removing pedals

A pedal can be removed using a pedal wrench or, sometimes, an allen wrench if there is a hexagonal hole in the inside end of the pedal axle. A normal open end spanner/wrench will work on some pedals; an adjustable spanner/wrench spanner will typically not work, because the head is too wide to fit between the pedal and the crank. A good shop-quality pedal wrench will also be longer than these, for the required leverage. This leverage is also the limiting factor for the use of allen wrenches in this application.

If a normal spanner is all that you have (be it adjustable or not) then you may find that pedal removal is possible, especially if you are removing platform style pedals—these generally have larger lands for the spanner. Just take care not to scratch or gouge the crank arm (see photo at right). Position an adjustable wrench so that, when turned, the adjustable jaw is on the "inside" of the turn.

Usually, you should position the wrench as close to overlapping the crankarm as possible. (So that it is in front of the arm, not extending its line.) Before attempting to remove the right side pedal, make sure the chain is on the largest gear. (That way, if you slip, you'll have a more difficult time impaling yourself on the sharp chainring teeth.)

(Usually the left and right pedals are marked with an "L" or "R" on the end of the thread to make identification easy.)

Removing Bicycle Pedals

 * 1) The left pedal (for left foot) has a left-hand thread i.e. it unscrews in the opposite direction to most threads (to unscrew it, you have to turn it clockwise). Left and right side pedals have opposite threads. The right hand, drive side, pedal is right hand (normal) thread; the left hand, non-drive side, pedal is left hand (reverse) thread. One easy way to remember the directions is (with the bike the right way up) to position the wrench on the pedal nut and projecting vertically above it, and to always push the lever of the wrench toward the rear of the bicycle to loosen that pedal; this works on either side. The natural motion of the pedal (which is counter-clockwise) will unscrew the left pedal if it is not left-handed.
 * 2) Pedals, especially when they have not been removed in a long time, can be very tight. It is important to apply grease to the threads before reassembly, to facilitate the next disassembly. Doubly so if the parts will be in a corrosive environment. (Salted roads, near saltwater, etc.) Any general purpose grease is acceptable. Without grease, pedals are very likely to become seized later and make for troublesome removal.

Note that there are two sizes of pedal axles in common, current-day use: 1/2 inch diameter for the one piece cranks typically found on children's bikes and older American-made bikes, and 9/16 inch diameter for the two and three piece cranks found on most modern adult bikes. Both sizes have SAE threads at 20 tracks per inch.


text:
Spanish/Vocabulary/Sports

=Los deportes (Sports) =

Deportes (Sports)

 *  El fútbol   association football, soccer
 *  El baloncesto, basquetbol   basketball
 *  El beisbol   baseball
 *  El fútbol americano   American football
 *  El hockey   hockey
 *  El hockey de hielo  ice hockey
 *  El tenis   tennis
 *  El montañismo  mountain climbing
 *  El golf  golf
 *  La equitación horseback riding
 *  La natación  swimming
 *  Los bolos  bowling

Sujetos

 *  La pelota   ball (smaller, such as a baseball)
 *  El balón   ball (inflated, such as a basketball)
 *  El cesto   basket
 *  El gol   goal
 *  El equipo   team
 *  El juego   game
 *  El campo   field
 *  El partido   match
 *  El oficial   referee

Verbos

 *  jugar   to play
 *  ganar   to win
 *  perder   to lose
 *  empatar  to tie
 *  correr  to run
 *  esquiar  to ski
 *  montar a caballo  to go horseback riding
 *  patinar (en línea) to go (inline) skating
 *  patinar sobre hielo to ice skate
 *  ir a jugar al boliche to go bowling

title: Spanish/Vocabulary/Sports


text:
Bicycles/Thread locking compound

Thread locking compound is an adhesive designed to prevent parts from vibrating loose. Some brand names are Loc-Tite® and Permatex®. A light duty compound will be removable with simple hand tools. Heavier duty may require special equipment such as a heat gun. There are three standard Loctite grades

Loctite was invented in 1953 by Vernon Krieble, PhD. It is described as an anaerobic sealant. In other words, it sets without air. To set it must be in the presence of metal ions and the absence of oxygen. this allows it to set properly inside an assembled fastening.
 * Blue Removable No.242 which is applied to fasteners that you may want to unscrew easily.
 * Red High-Strength No.271 which is applied to fasteners that you seldom need to remove.
 * Green is a wicking grade of Loc-Tite® used on joints which have already been assembled

title: Bicycles/Thread locking compound


text:
Spanish/Vocabulary

 * Animals
 * Arts
 * Colors
 * Emergency Room
 * Food
 * Love
 * Music

 * Occupations
 * Outdoors
 * People
 * Sports
 * Technology
 * Describing Yourself

title: Spanish/Vocabulary


text:
Talk:Chinese (Mandarin)

Untitled
Hey all -- I've just expanded out the main page a little, since I thought that more topics should be discussed beyond simple greetings. I have set out a tentative structure for a wider treatment of chinese which is probably most useful for a beginner to learn. The idea of the "Exercises" which I added to Chapter One is to set out a few questions for students to work through according possibly to a corresponding lesson, with example solutions given at the end or on a separate page, although possibly this is more in the domain of Wikiversity. --Gremlin 29 December 2006

 * I moved all the new lesson ideas to the Chinese/Planning page for now. They're good ideas, but need to be more smoothly integrated with the book I think. Instead of making new headings for each chapter, I think it would be best to enter them all under the Lessons heading in the format already used. I think it's time for some of the later chapters listed to be renamed to subjects areas like the ones you added, but the old content should be moved first, maybe to a subpage of the Planning page. That's why I didn't do all that just now. Sometime soon. --Everlong 05:44, 5 January 2007 (UTC)

 * Sorry for the very late response. Thanks for the positive feedback. It was a good idea to move my ideas to the planning page, since afterall they were only intended as a sketch of what could be done. I might return and help out again when I can find the time. --Gremlin 4 February 2007

A new Cantonese book has just started up. If there are any Cantonese-speaking contributors in this crowd, we'd appreciate your help on the Cantonese book as well. Thanks! --Alissa 07:45, 22 May 2005 (UTC)

You may also want to check out Spanish which I have just organized, simplified and improved. Hope you don't mind I changed the splash image into a link to the contents page. --Karl Wick

Not at all -- this is a collective effort, so any and all help to further improve upon what is existent would be appreciated. -Taoster

Does anyone else plan on adding more to this Wikibook? I would like some collaboration on this, as one person's work will ultimately yield errors at some point or another. Yacht/Gboy? -Taoster

 * Hey, Taoster! u guys r so cool! when I came back here, I found out a lot of contents have already been added. :) About the textbook, I would like to help, but I know little about what other Chinese textbooks for English speakers are like, I want to check out some examples first. BTW, r u mandarin speaker?
 * And, here is my opinion: I don't think it's good to introduce the grammar at the very begining lessons, which would make learners boring. What do u think? --Yacht (talk)Q 02:31, 29 Jan 2004 (UTC)

 * BTW, shall we make a note that this textbook is in Simplified Chinese? --Yacht (talk)Q 02:45, 29 Jan 2004 (UTC)

This is a very good textbook on chinese! Keep up the good work guys, it's good to be able to have access to comprehensive texts like these for people with little money :)

I suggest writing the pinyin using the tone markings on the letters instead of with numbers. It would look a little cleaner and be easier to read.

It is great that someone does this stuff! I learned how cool Chinese can be. Keep up the good work. The only thing is that I would like to see section 5, and 6 done.

couple of things
Couple of things I'd like to say after writing a bit on pronunciation and lesson 1:

 * What's the purpose of "Fundamentals"? As far as I can see, it duplicates content that belongs elsewhere.
 * The current material introduces things too fast, too much... I've tried to cut this down by reducing the dialogue in Lesson 1 to just a few sentence structures. The result is a rather idiotic conversation but I don't think that can be helped.
 * Pinyin: currently we're using Unicode for pinyin. Does anyone think we should switch to using numbers for the tones?
 * I feel that using numbers for tones is not a good idea because it looks clunky and to me seems more difficult to read. Think of the tone marks like the special letter marks in French.

That's about it for now. -- Ran 05:23, 29 Oct 2004 (UTC)

Simplified and Traditional Chinese mixed up!
I am not doing this to the tradition Chinese, but the mixed-up is really ugly, and confusing. i don't think it's good for the learners. We need separate textbook for the needs of different learners. Mixing up is not a good option. Maybe we need to set up a Simplified Mandarin Chinese and Traditional Mandarin Chinese respectively. --Yacht 18:39, 18 Dec 2004 (UTC)

They're parallel to eachother, but I wouldn't say it's harder to learn. I think that people can just disregard the one that they don't plan on learning. As well, they're just simplifications of chars, you could probably run a script to convert a text from trad to simplified or vice versa.
 * TC > SC is problematic. eg ?? vs. ??. Nateji77 23:29, 25 September 2005 (UTC)

I like having both, since it is nice for learners that learn how to write one system, but perhaps only learn charater recognition of the other system.

i also like having both. on the mainland TC is often used in business/school names. Nateji77 23:29, 25 September 2005 (UTC)

 * I've thought on this quite a bit. I've seen books that:
 * have the traditional for lesson texts only, as an insert or in the back of the book
 * acknowledge the traditional, but just in the vocab section
 * have simplified/traditional/pinyin/english for everything
 * have traditional on the left page--simplified for the right, all the way through the book
 * or totally ignore the other character set
 * In my opinion, #2 would be the best trade-off with making the book less cluttered but still friendly to familiarization with the alternate character set. However, since it is a Wikibook, I think it's inevitable that people will volunteer the translations (as in fact happened), converting us to the #3 type. This makes me want to lean towards the #4 type with parallel texts. Especially after having tried using traditional while using an exclusively simplified book, I think having the two is necessary.

 * I think the best way to implement it would be making subpages with traditional in the form of Chinese/Lesson_1/traditional and just keeping the content all the same, which is easy enough. We can make a traditional Table of Contents template to make the traditional easy to navigate, and, being subpages, there's the automatic linking back to the simplified pages all the time. What does everyone think? --Everlong 09:13, 16 November 2005 (UTC)
 * I finally made the subpages change a few days ago. I think things look much neater without a simplified/traditional translation of everything. However I did leave the alternatives in for the dialogues and for the vocab lists so that readers can get to where they recognize the other set, but don't have it cluttering up every example sentence.
 * --Everlong 17:05, 22 March 2006 (UTC)

a proposed new outline
is here, check that out. --Yacht 08:08, 26 Jan 2005 (UTC)

Chinese Writing
Shouldn't the writing system be a wikibook of its own? If it's combined with Mandarin it is hard to reference to here for other Chinese languages (eg. Cantonese) which uses the same system?
 * I definitely think this wikibook needs to contain sections on how to write the characters learned in the dialogue. That means means some text gets duplicated between the two, but in my opinion a language textbook needs to have a holistic approach to its subject matter.Rycanada 21:08, 10 May 2006 (UTC)

Pronounciation
It would be nice to add audio recordings of the texts. It is very hard to understand the pronounciation just from the transscript.
 * Completely agree—for Chinese, I feel that audio is a must. Jade Knight 22:53, 19 March 2006 (UTC)
 * I'm working on including audio, linking the vocab lists to all the Wikicommons recordings available (current total: 3). I've put in a request with one of the recorders to do more to fill out our lessons, though I haven't heard back from him. When I find time I'll try to record them myself if need be, though they'll just be standins until a native speaker takes on the task. Eventually, whole dialogues could be recorded, even the grammar could be recorded as in the Spoken Wikipedia.
 * --Everlong 18:25, 22 March 2006 (UTC)
 * Update: The guy I asked, Peter Isotalo, of Wikicommons, contributed some more audio samples specifically for use in this book. We're now up to 19 vocab pronunciations now. See our Contributor's Guide to find out how to contribute your own sound samples.
 * --Everlong 16:25, 19 April 2006 (UTC)

why not in languages category?
can't find this book at http://en.wikibooks.org/wiki/Category:Languages (i don't know how to fix this, maybe somebody else does) --Tjalling 10:35, 20 July 2005 (UTC)
 * You just need to add the tag to a page for it to be added to the category. I'll add us to the list. --Everlong 02:54, 22 July 2005 (UTC)

Naming Policy
I'm going to start converting the Chinese textbook to conform with the new "slash convention" recommended for new wikibooks in Wikibooks Naming Policy as opposed to the now obsolete Wikibooks Naming Conventions we're currently using. The MediaWiki software will make automatic links back to main page from all subpages (i.e. - < Chinese), simplifying organization. Additionally, the slash convention could be used to easily expand in a logical heirarchy, as shown below. --Everlong 03:43, 17 August 2005 (UTC)

etc.
 * Chinese
 * Chinese/Pronunciation
 * Chinese/Lesson 1
 * Chinese/Lesson 1/Stroke Order
 * Chinese/Lesson 1/Exercises
 * Chinese/Lesson 1/Solutions

Copyright for main image: Image:China splash.jpg
This is just a note that the main China splash image is something that needs formal copyright attribution. If anybody who is working on this Wikibook knows of either what copyright license this image has been uploaded under, it would be greatly appreciated. --Rob Horning 02:45, 3 February 2006 (UTC)

More useful media!
The podcast, chinesepod has lessons in audio, and they are CC-by, which is completely wikimedia-compatible. Should we try to integrate them into the wikibook somehow? We'll need to convert them to .ogg of course. -- Kowey 00:35, 23 February 2006 (UTC)

Disentangling Traditional and Simplified
Thanks for everyone's hard work! This is a fantastic resource.

I was just wondering, if there is a separate Traditional wikiproject, why do the lessons have both Simplified and Traditional characters in them?

I've taken a short (4 month, 3 hours a week) course on Mandarin Chinese, so I've covered a lot of the same material that this has... but I find my textbook much easier to follow simply because my eyes wander over to the traditional version of the dialogue. Rycanada 21:00, 10 May 2006 (UTC)

 * (Oh, there is one exception to the Simplified-only rule in my textbook: There is a guide to writing characters at the end of each section, and that section contains traditional versions as well as simplified). Rycanada 21:00, 10 May 2006 (UTC)

Traditional / Simplified split is not working
The Traditional and Simplified versions should not have been split up! Now we have two parallel wikibooks teaching precisely the same topics except for a split in orthography, which doubles our workload. Changes and corrections made to one wikibook has to be made to the other one as well, which also doubles our workload. Moreover, it's inevitable that people will make changes or additions to one wikibook but neglect / forget to do it to the other, which splits our efforts and results in forking. Considering how stalled this wikibook already is, it is not helpful to split up what little we already have.

Moreover, it is not hard to teach two systems at the same time. In fact, I think it is a disservice to potential students if we don't show them both systems: many Chinese programs in fact do teach both systems simultaneously, with the expectation that students will learn to write one and read the other. Teaching two systems simultaneously does not take up that much space even, so why have we stopped doing it?

In short, I see huge problems and little advantage with this current split into Traditional and Simplified. If there are no objections, I will re-merge them together.

-- Ran 18:07, 28 May 2006 (UTC)

More reading passages?
This textbook is so far very elementary. I'm wondering if there should be more offered... maybe reading passages for slightly more advanced students? harder vocabulary lists from those reading passages? All of the chinese language textbooks (from china) that I've ever seen are structured that way. I would offer to write the passages but I am not a very good writer and my writing in chinese is even worse. However, I will volunteer to read and record passages. I am fluent in speaking and chinese is my first language. Blacksheepmails 04:24, 7 December 2006 (UTC)

 * The text may be elementary, but I don't think a new student would find anything about it too easy, what with studying grammar, pronunciation and writing simultaneously. It's a real struggle making everything gradual enough. We need to introduce useful vocab slowly so as to not overwhelm students with too many words a lesson. I've used books where the new vocab would vary from 40–90 per lesson, and it was not fun.

 * I'm wary too about adding reading passages with a lot of "supplemental" vocab words that won't be properly reinforced. Nevertheless, I think some extra passages could be good every few lessons. Most textbooks I've seen do that and it could be good for an occasional challenge and review without being intimidating. -- Everlong 11:10, 24 December 2006 (UTC)

 * Yes, the reading passages should be occasional. But also, not everyone using wikibooks will be a complete beginner. I came here first to learn spanish, which I have been learning for a while now.Blacksheepmails 01:41, 7 January 2007 (UTC)

Orphans
你好! I found some orphaned pages belonging to this book: Please link to these pages in this book or mark them for deletion with delete. 谢谢, hagindaz 02:15, 14 July 2006 (UTC)
 * Chinese/Pronunciation
 * Chinese/Elementary Chinese + Elementary Chinese Lesson 1
 * Chinese/Appendix CE-B - Chinese/Appendix CE-C - Chinese/Appendix CE-D - Chinese/Appendix CE-K - Chinese/Appendix CE-M - Chinese/Appendix CE-N - Chinese/Appendix CE-P - Chinese/Appendix CE-W - Chinese/Appendix CE-Z

Adding lang attributes?
The display of Chinese in this book isn't too great in my browser because there are no "lang" attributes on the Chinese portions, so the fonts firefox chooses aren't correct. Does anyone know of a way we can implement the adding of "lang" attributes to the appropriate sections? --Echalon 05:13, 15 December 2006 (UTC)
 * I looked up lang's uses, and it seems it might be a good idea, both for specifying a font and for making the Chinese text a larger font than the English for readability. Looks even better since bold and italics don't work too well on Chinese, so this would allow alternative emphasizers to be specified.

 * I haven't used lang and don't know if it is allowed by the wiki software, but what font would you choose for best display? (In Firefox and Opera, since IE doesn't recognize lang.)
 * — Everlong 23:28, 15 December 2006 (UTC)

 * Personally I use AR PL ZenKai Uni, but really that should be up to every user. The idea is with the correct lang tags, I can set my preferences in the browser and everything should work out. All the tags really do is help the browser to decide what is English text versus Chinese text, and then the browser can make font choices based on that information. If everything was under a different character encoding it would be far easier, but with UTF-8 and kin we have to add that information ourselves. --Echalon 00:05, 17 December 2006 (UTC)

A bit too basic?
I feel like there are a lot of really basic "What is your name?" type lessons in here. I've had to learn a lot of Chinese in my time, and by the end of the first year of Chinese study, we were already on to more advanced topics of conversation. Fundamentally, I feel like this textbook should be structured around subjects of conversation, rather than around grammar. Each lesson should introduce new grammar and vocabulary, of course, but each should have its own unique subject of conversation. Just my 2 cents, gleaned from four years of Chinese study.--Danaman5 (talk) 12:13, 30 July 2008 (UTC)
 * I agree, I think really the "perfect" textbook will have a dialogue at the beginning that introduces a topic and a new grammatical concept. The next section of that lesson will introduce and explain the vocabulary used in the dialogue. The next section explains the grammatical concept introduced.  Following are drills/exercises that give the student an opportunity to apply what was learned.  This would allow for us to give students more vocabulary and topics will still addressing the fundamentals of the language.Shivasprogeny (talk) 06:21, 7 November 2008 (UTC)

WTF with the License？
According to the printable version header,this,textbooks is shared under CC-BY-SA 3.0.But the License at the end of the text says it is GFDL 1.3.Shall I change CCBYSA to GFDL?--Arthur200000 (discuss • contribs) 18:56, 3 October 2013 (UTC)

title: Talk:Chinese (Mandarin)


text:
Bicycles/Oil

oil suitable for use on bicycles can be a basic 30 weight automotive oil or one of the more recent synthetics.

Some recent oil products evaporate to a waxy finish on exposed areas, making them less likely to retain grit.

title: Bicycles/Oil


text:
User:Taoster~enwikibooks

Taoster is also an anagram of Toaster, but the two are not equivalent.

title: User:Taoster~enwikibooks


text:
Bicycles/Maintenance and Repair/Tools and Supplies/Pedal Wrench

A standard "pedal wrench" is an open-ended wrench designed to be thin enough to fit the narrow wrench flats (gripping surface) typical to pedals. A quality pedal wrench will be long enough (and preferably with angled openings) to provide significant leverage, and durable enough to allow repeated application of such force. Pedal wrench flats are typically 15mm in size. 9/16" (~14.3mm) is somewhat common on older pedals. 17mm and other sizes have been used, but you aren't very likely to encounter them.

(A "cone wrench" is thinner and shorter than a pedal wrench, and unable to provide appropriate durability or leverage for use on pedals. A standard open-end wrench (such as found on one end of a combination wrench) will sometimes fit on the flats, but is unlikely to provide proper leverage, while being likely to spread at the tips, ruining the wrench and possibly the flats.)

Pedal wrenches are also available for pedals with 6mm or 8mm internal hex ("Allen wrench") fittings in the end of the spindle, accessed from the back of the crank arm, through the pedal hole. A significant portion of modern pedals provide only this fitting, with no traditional wrench flats. These pedals wrenches differ from standard "Allen wrenches" primarily in that they provide longer and more comfortable handles, which is important to allow application of needed leverage.

In the U.S., there are two diameters (sizes) of pedal spindle (axle) threads which you are likely to encounter: 1/2" and 9/16". The first is generally used on bikes with a one piece crank, which will normally be an inexpensive or older bike. The second will usually be found on bicycles with two or three piece cranks, which includes many current multi-speed bicycles and higher quality older bikes. There are other pedal thread sizes, such as 14mm (French), but you are quite unlikely to encounter them in the U.S.

WARNING

Left-hand pedals are reverse threaded. (That is, you turn clockwise to loosen, counterclockwise to tighten. The Wright brothers introduced this to prevent pedals from unscrewing on their own.) Make very sure it's not cross-threaded, you are turning the correct direction, using the correct pedal, and use grease! (If any of the threads are stainless steel or titanium, it would likely be better to use an appropriate "anti-seize" compound instead of grease.) Pedals should be properly tight, 26 ft-lbs being a generic (not perfect) torque specification. (Rotational force equivalent to 26 pounds on the end of a foot long lever (the wrench), 52 pounds on a 6" lever, etc.)


text:
Spanish/Indicative

Verbs | Verb Tenses | Verbs List

El indicativo
These eight simple verb tenses and four compound tenses refer to an objective reality and are categorized by time: present, past, and '''future. ''' These verb tenses are the simplest and most commonly used.

 *  Tiempos presentes

 * Presente, presente progresivo
 * Presente perfecto
 *  Tiempos pasados

 * Imperfecto, imperfecto progresivo
 * Pretérito, Pretérito progresivo
 * Pluscuamperfecto o, perfecto pasado indicativo
 * Pretérito perfecto o, pasado anterior indicativo
 * Tiempos futuros

 * Futuro
 * Futuro perfecto o, futuro anterior, futuro anterior indicativo

title: Spanish/Indicative


text:
Spanish/Subjunctive

../Verbs/ | ../Verb Tenses/ | ../Verbs List/

Subjuntivo
These four verb tenses refer to the speakers' feelings toward the action and are about things that should or could be. These tenses are unfamiliar to English speakers as they are no longer commonly used in English grammar. They are divided into present, past, and future just like the indicative tenses.

 *  Presente

 * Presente de subjuntivo
 *  Pasado

 * Imperfecto de subjuntivo
 * Pluscuamperfecto de subjuntivo o, pasado perfecto subjuntivo
 *  Futuro

 * Futuro subjuntivo (today, used only in legal documents)

title: Spanish/Subjunctive


text:
Spanish/Conditional

../Verbs/ | ../Verb Tenses/ | ../Verbs List/

El modo potencial
These two verb tenses communicate what would happen or would have happened.
 * potencial simple estudiaría
 * potencial compuesto habría estudiado

title: Spanish/Conditional


text:
Spanish/Imperative

../Verbs/ | ../Verb Tenses/ | ../Verbs List/

Imperativo
This form gives commands.

To form the imperative mood of verbs, one normally takes the present subjunctive of the verb.

The major exceptions to this rule are the second person singular and plural forms of positive command. To form a positive second person singular command, use the third person singular indicative. To form a positive second person plural command, take the stem of the verb and add:

-ad if the verb is an ar verb.

-id if the verb is an ir verb.

-ed if the verb is an er verb.

Note that when making a negative command, such as "no cantes" (don't sing), the present subjunctive is used.

There are many exceptions to these rules.

 * Imperativo o, "el mandato"

title: Spanish/Imperative


text:
Talk:Spanish/Verb Tenses

Ugh. I have spent hours and hours on this page trying to make the presentation as simple and meaningful as possible. I think it makes sense to present the list of tenses in more than one way because it shows the relationships of the parts. Should they be on the same or different pages ? Is the way I have ordered them the most meaningful ? Someone who is a true linguist, please help me out here. -- Karl Wick

 * I'm a little confused about a couple of names. For example, the "potencial" would be called "condicional" (at least in Spain, I don't know if it's the same in Latin America).
 * As for the order of the tenses, in First_conjugation_verb_(Spanish), I made a table on the simple tenses of a typical verb (in this case, amar). I would suggest leaving subjunctive towards the end. Maybe...
 * INDICATIVO: presente - imperfecto - pretérito perf. simple - futuro - condicional + the corresponding composite tenses
 * SUBJUNTIVO: presente - imperfecto - futuro + the corresponding composite forms.
 * I'd note that pretérito perfecto compuesto (hube estudiado) is rare, and futuro de subjuntivo (estudiare) and futuro perfecto de subjuntivo (hubiere estudiado) are almost archaic and used only in law. Even so, I think a link to the last two forms would be useful. Not for people who don't know Spanish at all, but maybe for lawyers who would like to work in Spanish-speaking countries ^^ Sabbut 20:15, 27 Jan 2004 (UTC)

This page requires some serious work. I added the present subjunctive page, but there are many tenses that have not been addressed yet. I think that the archaic tenses should be on a separate page of "rare tenses," but that's just a thought. -Fenoxielo 5/18/05

I added a bit to the imperative section. It should probably be edited, but at least now there's something useful there.

Spanish vs. English Headings
It is hard for me to browse through this page and get what I need from it because all the names of the tenses are in Spanish. And I even know enough Spanish to read a book or newspaper or to have a simple conversation. What do others think about this? Would it be okay for me to add the English in addition to the Spanish? --Think Fast 14:04, 28 June 2006 (UTC)

Potencial vs. Condicional
Is it more correct to say potencial or condicional for the conditional tense? Also, is the conditional a tense or a mood? --Think Fast 14:05, 28 June 2006 (UTC)

title: Talk:Spanish/Verb Tenses


text:
User:R

fr:Utilisateur:R

I write mostly on the french Wikipédia. You might find it more convenient to write to me on my french page since I'm more often on fr: than on any other Wikimedia domain.

title: User:R


text:
Spanish/Parts of Speech

../Grammar Index/

 * ../Adjectives/
 * ../Adverbs/
 * ../Nouns/
 * ../Verbs/

title: Spanish/Parts of Speech


text:
Vietnamese/Personal pronouns

Vietnamese is a bit different than Romance languages, in that Vietnamese doesn't just use different pronouns for casual or formal situations, but Vietnamese actually uses different pronouns depending on the relation between the speaker and his/her audience. This relation takes gender, age, and status into account. Basically, Vietnamese refer to everyone as a family member. Also, it is common to use a third person personal pronoun in the first person.

Singular pronouns

 * bạn (friend)
 * informal, but not casual; a general-purpose version; use with caution

 * anh (brother)
 * to a male who is the same age as the speaker

 * bà (grandmother, old lady)
 * formal; to a female who is older than the speaker

 * chị (sister)
 * informal; to a female who is the same age as or older than the speaker

 * con (child)
 * from an adult to a child

 * em(younger sister or brother)
 * to a female who is the same age as the speaker, or to a person (of either gender) who is younger than the speaker (such as a child)

 * mày (you)
 * informal, even rude or insulting; to a person younger than the speaker, or to a person held in low esteem; use with caution

 * ông (grandfather, old man)
 * formal; to a male who is older than the speaker

 * cô (father's sister)
 * formal; to an older woman as old as one's father, a young (usually unmarried) woman

In addition, there are different pronouns for each kind of relative. For a listing of those pronouns, see Family.

(More to come.)

title: Vietnamese/Personal pronouns


text:
Spanish/Vocabulary/Emergency Room

= El Departamento de Emergencias (Emergency department) =
 *  las urgencias  :  emergency
 *  el almacén  :  storage room
 *  el almacén de material estéril  :  storage room for sterile equipment
 *  el almacén de material sucio  :  storage room for soiled equipment
 *  la ambulancia  :  ambulance
 *  los aseos  :  toilets
 *  el consultorio  :  examination and treatment room
 *  el despacho de la enfermera jefe  :  head nurse’s office
 *  el despacho del asistente social  :  social worker’s office
 *  la farmacia  :  pharmacy
 *  la habitación de aislamiento  :  isolation room
 *  la información  :  information desk
 *  el puesto  :  station
 *  el puesto de enfermeras  :  nurses’ station
 *  el puesto de la guardia de seguridad  :  security guard’s station
 *  la recepción  :  reception area
 *  la sala  :  room
 *  la sala de cirugía menor  :  minor surgery room
 *  la sala de consulta  :  consulting room
 *  la sala de enyesado  :  plaster room
 *  la sala de espera  :  waiting room
 *  la sala de observación  :  observation room
 *  la sala de observación psiquiátrica  :  psychiatric observation room
 *  la sala de reanimación  :  resuscitation room
 *  la sala de triaje  :  triage room
 *  la sala del personal  :  staff lounge
 *  la unidad móvil de rayos X  :  mobile X-ray unit
 *  la zona de camillas  :  stretcher area

= Equipo de primeros auxilios (First aid equipment) =
 *  el alcohol isopropílico  :  rubbing alcohol
 *  el algodón hidrófilo  :  absorbent cotton
 *  el antiséptico  :  antiseptic
 *  el apósito  :  triangular bandage
 *  el aspirador  :  aspirator
 *  la aspirina  :  aspirin
 *  la bolsa válvula máscara (ambú)  :  bag valve mask (manual resuscitator)
 *  el botiquín de primeros auxilios  :  first aid kit
 *  la camilla  :  stretcher
 *  la cánula orofaringea  :  oropharyngeal airway
 *  el collarín cervical (protector de cuello)  :  cervical collar (neck brace)
 *  la compresa de gasa  :  dressing
 *  el desfibrilador  :  defibrillator
 *  el esfigmomanómetro  :  blood pressure monitor
 *  el tensiómetro
 *  el esparadrapo  :  adhesive tape
 *  el fonendoscopio  :  stethoscope
 *  los guantes de látex  :  latex glove
 *  el hisopo  :  cotton swab (cotton bud)
 *  la jeringuilla  :  syringe
 *  el manual de primeros auxilios  :  first aid manual
 *  la máscara de oxígeno  :  oxygen mask
 *  el peróxido  :  peroxide
 *  las pinzas  :  tweezers
 *  las tablillas  :  splints
 *  el termómetro  :  thermometer
 *  las tijeras  :  scissors
 *  la tira adhesiva sanitaria  :  adhesive bandage
 *  la tirita
 *  la venda de gasa  :  gauze roller bandage
 *  la venda elástica  :  elastic support bandage

Sustantivos

 *  La sala de urgencias/emergencia:   emergency room
 *  La ambulancia:   ambulance
 *  El/la doctor/a:   doctor
 *  El/la enfermero/a:   nurse
 *  La medicina, el medicamento:  ''medicine
 *  La inyección:   injection
 *  Los puntos:   stitches

Conversaciones

 *  ¿Dónde te duele?   Where does it hurt?
 *  ¿Estás embarazada?   Are you pregnant?
 *  ¿Tienes una historia de problemas médicos, de riñon, pulmón, o corazón?   Do you have a history of medical problems, in the kidneys, lungs, or heart?
 *  ¿Eres diabético?   Are you diabetic?
 *  ¿Tienes alergias?   Do you have any allergies?
 *  ¿Estas tomando algún medicamento?   Are you taking any medicine?
 *  ¿Cuantos años tienes?   How old are you?

title: Spanish/Vocabulary/Emergency Room


text:
Bicycles/Degreaser

A degreaser is useful in removing greasy dirt from parts. Traditionally petroleum based products have been used. DO NOT use gasoline. Although it is an effective degreaser, its volatility (i.e. tendency to explode) make it a poor choice for shop work. If you must use a petroleum product, choose naphtha (usually available in hardware stores) or kerosene. A better choice is a modern, biodegradable water based degreaser. Specific blends for bicycle cleaning are available from bike shops and online retailers. You can probably save some money, though, by purchasing degreaser from an auto parts retailer. Whatever you use, after cleaning moving parts with a degreaser, always follow up with lubrication. All residual degreaser should be wiped off the parts before applying lubrication, as it would otherwise dilute the lubricant.

title: Bicycles/Degreaser


text:
HyperText Markup Language/Textual Formatting

As with almost all programming languages and Markup Languages there are several different ways of formatting text. HTML is no exception.

A popular way to format HTML is to use specific HTML tags such as ,  and. The World Wide Web consortium (W3C) suggest these tags may not be supported in future and that you use, and to add formatting to text on the HTML page.

In practice, these methods are both fine to use, but are limited in the ways that text can be formatted.

Thus, many HTML authors are shifting towards using CSS (Cascading Style Sheets) which employs "style sheets" and "inline styles" to add formatting to text. It should be noted that using CSS one can redefine the appearance of text inside all tags of a particular type. See the section on classes below for details.

Inline styles
Through CSS (Cascading Style Sheets) you can reuse code using "classes" which contain "styles" (ways of formatting text). You can also put CSS styles inline, as in the following:

This is a paragraph of double-size bold text

results in

This is a paragraph of double-size bold text

Classes
Classes can be defined in two places; in style tags in HTML documents and in external files, the "style sheets" referred to in the name "Cascading Style Sheets". The term "cascading" refers to the mechanism by which the correct style is chosen when multiple style sheets are to be applied to the same document.

An example style tag:

 a { font-weight: bold; } a.special { color:red; }

An example of the contents of a style sheet file: a { font-weight: bold; } a.special { color:red; }

HTML/Organizzare il testo


text:
User:Envia~enwikibooks

I've looked forward to open textbooks. Now we can make them, thanks to wikibookians and wikipedians.

title: User:Envia~enwikibooks


text:
Heat Transfer

About this book

An introductory text which should be of particular interest to students of chemical or mechanical engineering.

Contents of subject

/Introduction/ The basics

/Heat Balances/ What goes in must come out

/Conduction/ A mechanism of heat transfer

/Convection/ A mechanism of heat transfer

/Radiation/ A mechanism of heat transfer

/Heat Transfer with Phase Change/ Different rules apply when this happens

/Heat Exchangers/ Industrial devices for heating, cooling and saving energy

/Appendices/ There may be something in here later

/Bibliography/ Recommended for more in-depth study

title: Heat Transfer


text:
The Voynich Manuscript

Welcome
The Voynich manuscript, described as "the world's most mysterious manuscript", is a work which dates to the early 15th century, possibly from northern Italy. It is named after the book dealer /Wilfrid Michael Voynich/, who purchased it in 1912.

Some pages are missing, but the current version comprises about 240 vellum pages, most with illustrations. Much of the manuscript resembles herbal manuscripts of the time period, seeming to present illustrations and information about plants and their possible uses for medical purposes. However, most of the plants do not match known species, and the manuscript's script and language remain unknown and unreadable. Possibly some form of encrypted ciphertext, the Voynich manuscript has been studied by many professional and amateur cryptographers, including American and British codebreakers from both World War I and World War II. As yet, it has defied all decipherment attempts, becoming a cause célèbre of historical cryptology. The mystery surrounding it has excited the popular imagination, making the manuscript a subject of both fanciful theories and novels. None of the many speculative solutions proposed over the last hundred years has yet been independently verified.

The Voynich manuscript was donated to Yale University's Beinecke Rare Book and Manuscript Library in 1969, where it is catalogued under call number MS 408 and called a "Cipher Manuscript".

Perhaps the appeal of Voynich research is that (a) it is truly cross-disciplinary, and (b) it rewards endeavour and persistence. This wikibook is intended to help you get started on what has already been (for some) a long road of (self-)discovery - the page you may find most useful at first is the Guide To Voynich Jargon.

Table of contents

 * 1) /Content/
 * 2) /History/
 * 3) /Jargon/

What we know about VMS

 * Illustrated medieval folio written in an undeciphered script.
 * From the illustrations – hairstyles and features of the human ﬁgures – as well as the shapes of the glyphs, the manuscript is posited to have been created in Europe. Carbon-dating at the University of Arizona has found that the vellum was created in the 15th century, and McCrone Associates has asserted that the ink was added shortly afterwards.
 * The manuscript is divided into quires – sections made out of folded parchment, each of which consists of folios, with writing on both sides of each folio (Reeds, 2002).
 * Including blank pages and pages with no text, there are 240 pages, although it is believed that some are missing (Pelling, 2006)
 * 225 pages include text, and most are illustrated.
 * The text was probably added after the illustrations, and shows no evidence of scratching or correction.
 * The text is written left to right in paragraphs that are left-aligned, justiﬁed, and divided by whitespace into words. Paragraphs do not span multiple pages.
 * Under the most used transcription, as there are ambiguities, the VMS is comprised of 8114 word types, and 37919 word tokens.
 * Based on the illustrations, the manuscript has traditionally been divided into six sections: (1) herbal, containing drawings of plants; (2) Astronomical, containing zodiac-like illustrations; (3) Biological, mainly containing drawings of female human ﬁgures; (4) Cosmological, consisting of circular illustrations; (5) Pharmaceutical, containing drawing of small containers and parts of plants, and (6) Stars (sometimes referred to as Recipes), containing very dense text with drawings of stars in the margins.
 * Currier (1976) observed from letter and substring frequencies that the text is comprised of two distinct ‘languages’, A and B. Interestingly, the Biological and Stars sections are mainly written in the B language, and the rest mainly in A.
 * The word frequency distribution follows Zipf's law, which is a necessary (though not sufﬁcient) test of linguistic plausibility. We also ﬁnd that the unigram word entropy is comparable to the baseline texts.

Source: What we know about the Voynich manuscript, by Sravana Reddy and Kevin Knight. http://www.isi.edu/natural-language/people/voynich-11.pdf

Page-by-page commentary
See: The Voynich Manuscript/Page-by-page commentary

The Voynich Manuscript has more than 200 pages, divided up into twenty quires (as per the following links). The first 7 quires are standard quires consisting of 4 nested bifolios each. Quire 8 once consisted of 5 such bifolios but only 2 remain. From quire 9 onwards, quires often consist of only one or two multiple folding bifolios. Exceptions are quires 13 (5 standard bifolios) and 20 (7 standard bifolios of which 6 remain). Further details are available at the description of each quire.

The web-pages linked onwards from there are intended to summarise the debate relating to individual pages - what could they mean? To what are they similar? What interesting (visual or statistical) properties do they have? (etc)
 * Main herbal section - Quires 1-7
 * Mixed quire - Quire 8
 * Astronomical/cosmological section - Quires 9-10 (note that quire 10 also contains the start of the zodiac section!)
 * Zodiac section - Quires 11-12
 * Biological/balneological (bathing nymph) section - Quires 13-14 (contains the "9-rosette" fold-out page)
 * Pharmacological+herbal section - Quires 15-19
 * Recipe / calendar / almanacke section - Quire 20

Cross-page commentary
This section is designed to contain commentaries on features spanning multiple pages of the VMs.
 * /Currier Languages (A & B)/
 * /Statistical features of the text/
 * /Neal Keys/
 * /Page ordering/
 * /Titles/
 * /Nymphs/
 * /Long gallows/
 * /Paints/
 * /Inks/
 * /Marginalia/
 * /Emendations/
 * /Alphabet/

Timeline/provenance

 * Abbot Beere (Bere) of Glastonbury
 * John Dee and Edward Kelly

People who claim to have broken the VM's code

 * /Alisa Gladyseva/
 * /William Romaine Newbold/
 * /Robert Brumbaugh/
 * /Leonell Strong/
 * /Leo Levitov/
 * /John Stojko/
 * /Gordon Rugg/
 * /Claude Martin/
 * /Michael Sasscer/
 * /Stephen Bax/
 * /Jutta Kellner/
 * /Sukhwant Singh/

External Resources

 * http://www.voynich.net/ - starting point for the English-language VMs. mailing list (started originally in 1991).
 * Voynich MS entry in Wikipedia
 * http://www.voynich.nu/
 * http://voynich-ms.de/wiki/Hauptseite - German VMS wiki

title: The Voynich Manuscript


text:
Vietnamese/Glossary/A-K

This glossary covers only the words used in this textbook. For a more complete listing of Vietnamese words and phrases, please see Wiktionary.

A

 * anh
 * man;
 * you (to a male who is the same age as the speaker)

B

 * bà
 * woman;
 * you (formal; to a female who is older than the speaker, or to the speaker's grandmother);
 * grandmother

 * bác
 * parents's older sister of brother

 * bạn
 * friend;
 * you (informal, but not casual; a general-purpose version; use with caution)

C

 * cha
 * father

 * chị
 * you (informal; to a female who is the same age as or older than the speaker)

 * chim
 * bird
 * penis

 * con
 * child
 * you (from an adult to a child)

 * chó
 * dog

 * Cô
 * Mrs.; (formal)
 * aunt (father younger sister)

E

 * em
 * you (to a female who is the same age as the speaker, or to a person who is younger than the speaker, such as a child)

D

 * Dì
 * aunt (mother youger sister)

G

 * gà
 * chicken

title: Vietnamese/Glossary/A-K


text:
Bicycles/Maintenance and Repair/Tools and Supplies/Multi-tool

A multi tool combines several tools into one package.The individual tools may,for example,all fold into the handle. The swiss army knife is an example of a general purpose multi tool. In recent years, a number of manufacturers have produced multi tools specifically intended for bicycle repair. For example:
 * Blackburn

 * Crank Brothers

 * Park

 * Pedros

 * Topeak


text:
Latin/Lesson 4-Principal Parts

Principal Parts
All Latin verbs are identified by four principal parts. By using the four principal parts, one can obtain any and all forms of the verb, including participles, infinitives, gerunds and the like.

Examples of principal parts from verbs of each conjugation:

 * 1st: ambulō, ambulāre, ambulāvī, ambulātum (to walk)

 * 2nd: doceō, docēre, docuī, doctum (to teach)

 * 3rd: mittō, mittere, mīsī, mīssum (to send)

 * 4th: audiō, audīre, audīvī, audītum (to hear)

For all regular verbs, the principal parts consist of the first person singular present active indicative, the infinitive, the first person singular perfect active indicative, and the supine (or in some texts, the perfect passive participle).

 * Deponent verbs have only three principal parts:

 * patior, patī, passus sum (to suffer)

 * ūtor, ūtī, ūsus sum (to use)

 * Likewise, semi-deponent verbs have only three:

 * audeō, audēre, ausus sum (to dare)

 * gaudeō, gaudēre, gavīsus sum (to rejoice)

Some verbs lack fourth principal parts (e.g., timeō, timēre, timuī, —; to be afraid); others, less commonly, lack a third in addition (e.g., fero, ferre, tuli, latum; to bring/carry). Others, such as sum, esse, fuī, futūrus, may use the future active participle (futūrus) as their fourth principal part; this indicates that the verb cannot be made passive.

title: Latin/Lesson 4-Principal Parts


text:
Talk:Ada Programming/Mathematical calculations/Trigonometry

Can some diagrams be borrowed from wikipedia? e.g. http://en.wikipedia.org/wiki/Trigonometry.
 * 219.89.185.25 21:34, 1 January 2006 (UTC)

Gee, someone needs to find some suitable diagrams. I had a tough time describing right triangles and a unit circle only in words... and I'm too lazy to find diagrams :-\. Ugen64 01:58, 16 Jan 2004 (UTC)

I'll make some in SodiPodi right now..Thunderbolt16 05:15, 16 Jan 2004 (UTC)

I drew it incorrectly with not the hyp to the unit circle to the leg. I'll fix this pretty quick

Um, where are the answers?

...to the exercises

Some notation for an angle must be included in defining the trig ratios because the value of the angle measure is one of the three variables in the equation. Math anxious students need to see as many visaul clues as possible in order for them to build an understanding of this concept.

Elementary Trigonometric Functions
Their teachers have taught my children the memory aid "SOHCAHTOA", pronounced so-ka-toe-a. Sin == Opposite / Hypotenuse, Cos == Adjacent / Hypotenuse. Tan == Opposite / Adjacent. This might be considered for adding to this section. Walrii 20:26, 12 May 2006 (UTC)

Suggest delete page
It's not clear what useful role this page plays in the book. I think it is simply an introduction to the topic of trigonometry, which already exists in more well-developed form at the beginning of the book. Any objections to deleting the page? Douglas W. Mitchell (talk) 16:22, 26 August 2010 (UTC)


text:
User:Cprompt

In DOS, the command prompt was often referred to as the c: prompt when the current directory was set to the root directory of the C: hard disk partition.

I have a somewhat more interesting user page on the English Wikipedia. I'm less of an editor on Wikibooks than I am on the Wikipedia. On Wikibooks, it seems I am more of a reader.

I have an account by the same name on the English Wikipedia, the Simple English Wikipedia, the Esperanto Wikipedia, and Wiktionary.

title: User:Cprompt


text:
Talk:Python Programming

About

 * Started: 19 October 2003
 * Size: 27,300 words (Oct 2013)
 * Printable version
 * Printable version
 * Printable version

Safety of user input data
Hi i didn't found anything about preventing XSS injection and SQL injections. I think its important part of doing web apps. Chris.
 * Although avoiding XSS injection and SQL injection is indeed important, I believe it is a cross-language skill that should be learned separately from the language itself (it could make a book by itself). There are however, aspects of certain language that is often an easy weak-point for malicious hackers coupled with careless programmer. In python, these weak points would be (not a complete list): input (python 2.x and below), eval, exec, popen, and subprocess, possibly open too. These weak points should be mentioned.

Non-programmers python tutorial
If anyone wants to, feel free to take any material from the tutorial that I wrote for the python programming language. Non-programmers python tutorial. I grant permission to relicense it under the GNU Free Documentation License (though I would recommend keeping the public domain exception for the programming samples). Josh Cogliati. Jrincayc 15:42, 16 Jan 2004 (UTC)

Thank you very much! I'll start to integrate it into the module ASAP Thunderbolt16 22:56, 17 Jan 2004 (UTC)
 * I started wikifiying it to simplify integrating it in. See my User:Jrincayc page for the contents. Jrincayc 02:43, 1 Jun 2004 (UTC)
 * More or less finished wikifying it. See User:Jrincayc/Contents -- Jrincayc 02:54, 2 Jun 2004 (UTC)
 * I plan on moving it from User:Jrincayc to Non-programmers Python Tutorial, if nobody objects. I am doing this because the server honors.montana.edu is being permanently shutdown, so I wish to start changing links to it to point to wikibooks rather than honors.montana.edu.   Jrincayc 02:44, 31 August 2006 (UTC)
 * Josh's work is now avaialable at http://www.andamooka.org/reader.pl?section=easytut as his link to the website at U. Montana is broken.--DavidRoss 06:23, 7 August 2006 (UTC)

 * Thank you. That looks excellent. We now have Non-Programmer's Tutorial for Python.
 * Well, that's technically merely a redirect to the specific version of Python we recommend for new people.
 * At the moment it redirects to Non-Programmer's Tutorial for Python 2.6.
 * Someday it will become a redirect to Non-Programmer's Tutorial for Python 3 (after a few more issues are resolved).
 * Even further in the future I expect Non-Programmer's Tutorial for Python to redirect to Non-Programmer's Tutorial for Python 4. :-) --DavidCary (discuss • contribs) 19:18, 29 February 2012 (UTC)

Explain what makes this book unique
People mentioned that Python is already covered in:
 * the book "How to think like a Computer Scientist: Learning with Python", which is already a comprehensive text about Python and covers a lot of topics on programming. Why not use that? --Offray
 * Dive Into Python by Mark Pilgrim, which is licenced under the GNU FDL--::Noldoaran 18:14, 6 Aug 2004 (UTC)
 * The official Python documentation --Beuc

Please add a note in the synopsys or introduction about what fostered the development of this wikibook :)

September 2004 revamp
I am about to delve into this thing, and find it's pretty much in disarray. It appears nobody is workin on it, so I'm going to go right ahead.

I have a structure in mind. The sections of the book will go something like this:

 * 1) Introduction - What is Python; Getting Python; Editing Python programs.
 * 2) Tutorial - A series of examples and exercises.
 * 3) Language concepts - Indepth and complete treatment of Python's implementation of syntax, variables, flow control, files, classes, etc.
 * 4) Standard modules - Indepth documentation of standard modules.
 * 5) Function reference - Indepth documentation of standard functions. (Not sure about this section.)
 * 6) Appendices - List of keywords and similar stuff.

See User:Yath/Python for the full chapter outline.

Yath 19:24, 24 Sep 2004 (UTC)

Web scripting
I'd like to read how to write a page containing a python script and how to configure apache to understand python. Thanks 158.193.85.212 07:28, 5 May 2005 (UTC)

Using saved programs
Could somebody elaborate on how to get a saved python program? I entered the program in a notepad file. But when I try to get it on the python command line, it says that the : in C:\ is wrong syntax. How do I get the programs? --elpenmaster

Naming policy
You might want to consider the WB:NP. Your current naming convention is deprecated and has several disadvantages - e.g. it has no navigational links. Also your worthy effort is neither considered a book nor a section inside a book. See wikistats which implements an extensive book and section detector.

--Krischik T 07:15, 11 October 2005 (UTC)

 * Adding to this, it would be a good idea in my opinion to drop the "Programming" pseudo-namespace. Books are starting to move out of that, notably Ada Programming. -Matt 23:41, 17 January 2006 (UTC)

 * Now what should be the new location, is it Python?. --Baijum81 04:40, 8 June 2006 (UTC)
 * One day the pages should be moved by a bot to fit the new scheme, but I'm not sure how to request that. Going to the bot maintainer's talk page will probably do it. -Matt 14:30, 9 June 2006 (UTC)

 * I'm adding the Development stages to each of the sections to it's easier to find stuff to work on at a glance. Help:Development_stages I'm not going to 100% beside any sections (yet) as I am not a python expert, and I am reluctant to say that a section that is complete.  Once I have done this, I will work on fleshing out some of the sections that need content.

 * I am new to contributing to wikibooks--well to any of the wikimedia projects--so any pointers or suggestions would be helpful. -DavidRoss 20:00, 6 Aug 2006 (PDT)

Unified Navigation
The navigation bars on this book are problematic: there doesn't seem to be any kind of general consensus on navigation bar template. What is/should be the convention? --Quartz25 21:19, 8 March 2007 (UTC)

For reference, the convention seems to be to use the  template for the top, and no template is used on the bottom. --Quartz25 23:54, 11 June 2007 (UTC)

Changes to the Introduction section
The introduction, as it now appears, is convoluted, incomplete, and circular. Thus I propose the following pages to be used in the following order:

1. Installing the python language itself
 * Broken down by platform

2. Interactive mode Python interpreter.
 * With demonstrative "Hello World" program (or perhaps a very simple print "What Is Your Name?", print "What is your quest?", print "What is your favorite color?") example.

3. Non-interactive mode python interpreter.
 * With the same demonstrative Hello program, instructing the user to use a simple text editor to save it as a text file.

4. Python Editors & Addons
 * (broken down by OS)
 * I'm placing this last, because this section is always going to be very much up in the air relative to a user's own tastes, but the link to the Python Editors should be maintained.
 * Furthermore, some people will be quite happy with the simple built-in text editors for quite a while, and we want to get them up to coding as quickly as possible, thus this section isn't, strictly speaking, necessary.
 * The addons come very last, because people just taking their first steps into python probably aren't looking to extend the language; again, not strictly necessary, not here anyway.
 * In fact, this last page could probably be best served as 2 separate sections of the appendix.

Once I figure out how to create subfolders and subpages in my user page, I'll start posting my reworking of the introduction there, and people can start commenting as they see fit. --MyOwnLittlWorld 19:24, 4 June 2007 (UTC)

The pages are up now at my user page, please tell me what you think and whether or not the intro should be replaced. Thanks, MyOwnLittlWorld 23:18, 4 June 2007 (UTC)

Question or Suggestion on the TOC
When you say User Interface on the TOC to you mean a topic on UI creation or is it a section to explain the UI of Python IDLE. And if its a UI section I will suggest some GUI Programming using the Tkinter Library if possible also support the Glade Library.

Few changes or Updates
--Dragonecc (talk) 01:34, 8 December 2007 (UTC)
 * 1) Help on the Python OOP page. I can use a little more help on the terms as their still too technical.
 * 2) Help with the installation of Python language (Ubuntu and Mac section)

Two links to Gaming
There seems to be two links to the module "Game Programming in Python" in the index. Should one be deleted? It is messing up the navigation on each page.

If so, which one should go? I was thinking about getting rid of the one under the section "Learning to program in Python" because the game programming is a more advanced subject.

--hypergeek14 (talk) 21:14, 26 July 2008 (UTC)

I have just noticed that there are also two links to the Files module. This time I think the link under "Rocking the Python (Modules)" section should go, as files are a basic concept.

--hypergeek14 (talk) 21:21, 26 July 2008 (UTC)

 * The deed has been done.
 * --hypergeek14 (talk) 21:44, 29 July 2008 (UTC)
 * --hypergeek14 (talk) 21:44, 29 July 2008 (UTC)

Examples?
I would like to understand the reasons for using dictionaries, tuples, lists, etc. I can't see the reasons for doing most of the things in this language. There are never an explanation of why you'd want to use certain things. Hires an editor (talk) 21:40, 18 February 2010 (UTC)

redundancy
Is there a reason why most of the content is there twice? Once under "Learning to program in Python" and once under "Python concepts". I believe we should merge those sections. Especially the following are very similar:

 * Errors and Exceptions
 * Flow control and Decision control
 * Scoping and Namespaces

Also I dont see a reason why modules need to be treated separately but still appear many times before in the text. I would also like to fix that. Any other suggestions? Greetings --Hannes Röst (talk) 07:56, 20 August 2010 (UTC)
 * Yes, I believe the sections were written by separate people with differing visions of the final book. I was trying to rewrite the whole thing coherently, but moved on to other projects.  You can see my single plan here.  Your goals seem similar to what I was thinking.  I might return as I would like to teach Python to a friend from this. --Jesdisciple (talk) 12:12, 23 August 2010 (UTC)

Which version of Python to use
Python 2.x or 3.x? The book in its current form contains many examples and explanation of language structures, internal functions, statements and all of that. However, there seems to be great inconsistency in the implementation of it. The most glaring is the use of print as a function (3.x style) or as a bare statement (2.x style). Whichever choice is made, it needs to be clearly represented somewhere, that or all examples need a note as to the language major version they're written in, or even written in both major versions as examples should be copy/past-able.

Drivers for a decision 2 vs 3:
 * How long is this book expected to be useful (3.x is going to be more useful in the longer run)
 * Is third-party package support critical for people still learning the language (as most exist purely for 2.x and 2to3 is not a tool for those new to the language)
 * What version is mastered by the editors here (going with 3, only to discover a wholesome three people know it, is a disappointment about to happen)

 * Greetings while you may have a valid point on newer Python release, there are some problems. Python 2.6 is highly use release across major Linux :releases and corporate development.  For this environment Python module are a great impact and migration to Python 3 make have costly deployment.  :Until modules are translated to Python 3 or native supported development for Python 2.6 will continue. This has being experimented with other :programming language like Cobol, Fortran and Pascal.  Also this book samples could be easily ported to Python 3 with minor changes.  Went the :development community embrace Python 3 then the book could either be ported or a new book could be written.
 * Hope this help.
 * Hope this help.

 * --Dragonecc (talk) 16 January 2011(UTC)

 * Question remains. Is this book based on Python 2 or 3 or is it mix of both? In any case it should be clearly stated. --Usp (discuss • contribs) 18:29, 22 March 2013 (UTC)

Python 2 Vs Python 3
As there are substantial differences between Python2 and Python3, it would be better if this book clearly stated which version it does cover to avoid leading newbies onto a steep learning curve. --Mecanismo (discuss • contribs) 17:05, 26 July 2013 (UTC)
 * The book mainly covers Python 2; in each location in which it covers Python 3 in addition, it should state so explicitly. An example of indicating which Python is being described is at Python Programming/Input and Output. --Dan Polansky (discuss • contribs) 20:03, 13 October 2013 (UTC)

Archive Old Discussions
Let's archive the old discussions. It is pointless and confusing having them around if they are no longer relevant. Hackbinary (discuss • contribs) 21:50, 13 October 2013 (UTC)
 * This is for you Dan-the-man, so could you revert the Talk page back to where I had it last night, and copy in the additions that we both have put on it? Thanks in advance. Hackbinary (discuss • contribs) 21:51, 13 October 2013 (UTC)

 * I oppose archiving the old discussions. I only support their archiving after the page becomes long, which it has not. --Dan Polansky (discuss • contribs) 22:08, 13 October 2013 (UTC)

Contents / Landing Page re-org
Last night I reorganised the Contents page. Danielle Polansky was not happy with some of words that I chose for section headings. I propose reverting back my changes, and use the following headings: Intro --> Getting Started Basics --> Fundamentals I introduced a new section called 'Code Reuse' that moves out everything from Functions, to Classes, and namespaces. Modules is redundant Standard Library Modules Third-party modules Writing extension modules --> Extending Python Appendices What are your thoughts? Hackbinary (discuss • contribs) 21:50, 13 October 2013 (UTC)
 * I oppose your changes, now as before.
 * Your "Dan-the-man", "Danielle Polansky", and "Danny boy" are not in good faith. Go away and find another playground. --Dan Polansky (discuss • contribs) 22:10, 13 October 2013 (UTC)
 * And you calling me a moron is in not in good faith. You talking down to me is not good faith.  If you would like to be treated with respect and dignity Dan, then I suggest you treat others with respect and dignity.  Your treatment of me has been rather undignified, and I am glad that I illustrated that to you.Hackbinary (discuss • contribs) 22:27, 13 October 2013 (UTC)
 * You conceded that chapters did not follow logically. Here is my revision of the page for you to review again:   Hackbinary (discuss • contribs) 22:27, 13 October 2013 (UTC)
 * It is you that I wish could find another playground. All I want to do is add some content, and already expressed, improve the readability, and ease of use of the book. You seem to have some idea in your head on how it should be, but you will not share it and you are unwilling to have others contribute how they think the book should work.  And you have taken a very abrasive, demeaning tone with me.  Hackbinary (discuss • contribs) 22:27, 13 October 2013 (UTC)
 * I am pressing ahead with reorganising, refactoring, and rationalising the chapters and chapter order as there is a fair bit of duplicated content which needs to be sorted through. I have organised the chapters into what I think are a coherent order.   There is currently duplication across numerous chapters, and as much as as possible, I have grouped chapters with similar content together, but their names may not be representative of their content at this time, eg text is really about strings.  Hackbinary (discuss • contribs) 16:28, 15 October 2013 (UTC)
 * If you think you have a better order, or vision on how it should be, let's discuss, and get it documented Hackbinary (discuss • contribs) 16:30, 15 October 2013 (UTC)
 * I disagree with such parts of your edits as is renaming "Basics" to "Fundamentals" or even "The very Language Basics". I disagree with edits that are not constituting an objectively unquestionable improvements but rather are pushing a personal preference when these edits come from someone who is not interested in contributing actual content to the book. You are not prevented from adding content; you are prevented from an arbitrary reorganization. No, you should not be "pressing ahead with reorganising, refactoring, and rationalising" as long as your content contribution to Wikibook is nearly nonexistent and there is an opposition to that reorganizing. --Dan Polansky (discuss • contribs) 08:03, 19 October 2013 (UTC)
 * Sorry, you're inactivity lead the status quo being changed. While you have contributed some good content, you are not the dictator of Programming Python. The content must be rationalised in a progressive manner, and if you are unwilling to be cooperative, I will seek assistance from others.  You have a track record of being obstinate, and forcing your views on others.   To begin with Basics is not a good section title.  The word is overly generic and does nothing to articulate that the section is about core building blocks of the language, Fundamentals on the other hand says this is core material to what will be discussed further on.  Furthermore, it makes immeasurable sense to organise related chapters that duplicate content together, before the content is merged into one chapter.  Do you not concur that the chapters Sequences, Data types, Numbers, Strings, Text, Lists, Tuples, Dictionaries, and Sets duplicates a fair amount of material?  Do not agree that this needs to merged together in a managed, organised and controlled way? If you are going to be so argumentative, and obstructive to the work that I am doing, then fine, that is your decision, but I am going to press ahead.  If you wish to discuss it, and compromise, then I am happy to do the same.  I am not willing to be in a situation where you feel that you can call the shots and that you feel that you can make arbitrary decisions yourself.  Over the past week I have been reading through chapters with greater detail, and reading through the change logs, and for example I do not approve of your revert 6 Oct, Input and Output  as it seems to me that using with is the better way to open a file context and read the file because 1.) you do not have to explicitly close the file once the execution path falls out of scope, and 2.) the handling of exceptions is better with the with block.  My point is that you make arbitrary changes yourself that have dubious merit.Hackbinary (discuss • contribs) 12:50, 20 October 2013 (UTC)

pdf problems
In the pdf version page 94 (numbered 90) has the page number superimposed over text. The first 2 pages aren't numbered, the next 2 are numbered III & IV, & the rest are numbered starting with 1. The Contents are on pages III, IV, & 1 with the text starting on 3 which doesn't make sense. At least on my system, pages 157-159 print out cropped. In the case of 157 and 159, cropping some of the blank space at the top and bottom respectively solved the problem. To fix 158 I suggest putting the entire section 36.3 on page 159. 69.72.92.242 (discuss) 00:31, 26 December 2013 (UTC)

Printed version very differ from main article, October 2015
First I notice missed "Extending with ..." chapters in existing PDF. I generated PDF myself (mediawiki2latex 7.21) from current article, but then I found that "Extending with ctypes" and some another chapters no included in printer version too. So maybe they need to be synchronized? Yasondinalt (discuss • contribs) 18:48, 25 October 2015 (UTC)

Yes I think you need to modify the printable version to include these chapters respectively. It should be rather obvious for you how to do that. Thanks for using mediawiki2latex. Yours --Dirk Hünniger (discuss • contribs) 19:14, 25 October 2015 (UTC)

Ok, I will compare articles in few days. Thank you for very useful tool! Yasondinalt (discuss • contribs) 19:21, 25 October 2015 (UTC)

Chapter 4, 5 and 6 are Missing
Noticed a very annoying issue with the PDF after printing the entire thing out and binding...

Chapter 4,5 and 6 are missing and contain only the text like:

I think it may have to do with that navigation (Redirected from) which I have removed and it waiting for moderation Surfer190 (discuss • contribs) 12:25, 27 December 2015 (UTC)

Hey, I resolved the issue just now. Clear you Bowser Cache and redownload the PDF. Thanks for reporting the issue. --Dirk Hünniger (discuss • contribs) 13:49, 27 December 2015 (UTC)

This book for sale on Amazon
This book seems to be available for sale on Amazon. That's kinda cool. Good to see wikibooks content being made available in that form. Good to see an example of commercial use of the content too I guess, but...

It's rather expensive though. I mean it's kind of a normal technology book price £19.89 on the UK store. I would expect it to be cheaper, given that it's available to download from here for free, and authored here by volunteers. Either that or I would expect the profits to be donated to wikibooks (which may be the case, but I don't see any label about that). Otherwise it feels a little bit like purchasers are being misled, and the community here is not being adequately rewarded.

How do others feel about it? It's not really my place to be outraged, since I've not authored any of this book myself. It could be that the book was actually authored elsewhere and copied in here, or authored by a few people here who are now profiting from publishing the book on amazon. What's the situation?

-- Harry Wood (discuss • contribs) 21:28, 29 January 2016 (UTC)

Shouldn't this be updated to Python 3?
Since Python 2 is now officially deprecated, I think this should really be updated to Python 3. This is the most complete Wikibooks reference body on Python, and it would really be a shame if it just got supplanted by the Non-Programmer's Tutorial for Python 3. Milanand (discuss • contribs) 11:55, 12 December 2020 (UTC)
 * I'm currently working on this here. Milanand (discuss • contribs) 12:37, 12 December 2020 (UTC)
 * I've lost access to my old account, but I'm still working on this here. Milanandreew (discuss • contribs) 07:13, 18 December 2020 (UTC)

Migrate to Python 3
This book is currently very disorganized; the Python 2 and Python 3 seem to be mixed together. I think that the book should be completely migrated to Python 3 because it is more useful in the long run. At the very least, the book should either be about Python 2 or 3, so there isn't confusion. Calgary341 (discuss • contribs) 20:24, 18 February 2022 (UTC)

If people still want the Python 2 stuff, we can simply make a new book called Python 2 Programming or something like that. Calgary341 (discuss • contribs) 20:26, 18 February 2022 (UTC)

 * Seems a reasonable proposition. Additionally, it would be nice if it explained how Python 2 differed in syntax, if at all. -- Jules (Mrjulesd) 22:20, 18 February 2022 (UTC)
 * There could be a page called something like "Python 2 vs. Python 3" somewhere. Calgary341 (discuss • contribs) 17:32, 19 February 2022 (UTC)
 * Whoops, just realized that page already exists! Calgary341 (discuss • contribs) 21:45, 19 February 2022 (UTC)
 * Indeed: Python Programming/Python 2 vs. Python 3. --Dan Polansky (discuss • contribs) 14:58, 4 June 2022 (UTC)
 * Now that Python 2 is no longer supported (support ended in 2020), I agree with migrating the book to Python 3. The first obvious impact is on all the print statements that should now become print functions (invocation uses brackets), then there is the true division (3/2==1.5), then there is the new unicode treatment, and then there are other differences. Changing the print statements is a straightforward if laborious task, but making sure everything else is correctly covered will be more of a challenge. --Dan Polansky (discuss • contribs) 14:58, 4 June 2022 (UTC)
 * I migrated print statements and performed some other changes to migrate the book to Python 3. One thing that remains is converting the external links to point to Python 3 documentation. An independent review searching for remaining things to do and mistakes would be helpful. --Dan Polansky (discuss • contribs) 11:01, 5 June 2022 (UTC)

title: Talk:Python Programming


text:
User:Jrincayc

See my user page on english

Wikification of non-programmers python tutorial

 * Non-Programmer's Tutorial for Python 2.6/Front matter
 * Non-Programmer's Tutorial for Python 2.6/Intro
 * Non-Programmer's Tutorial for Python 2.6/Hello, World
 * Non-Programmer's Tutorial for Python 2.6/Who Goes There?
 * Non-Programmer's Tutorial for Python 2.6/Count to 10
 * Non-Programmer's Tutorial for Python 2.6/Decisions
 * Non-Programmer's Tutorial for Python 2.6/Debugging
 * Non-Programmer's Tutorial for Python 2.6/Defining Functions
 * Non-Programmer's Tutorial for Python 2.6/Lists
 * Non-Programmer's Tutorial for Python 2.6/For Loops
 * Non-Programmer's Tutorial for Python 2.6/Boolean Expressions
 * Non-Programmer's Tutorial for Python 2.6/Dictionaries
 * Non-Programmer's Tutorial for Python 2.6/Using Modules
 * Non-Programmer's Tutorial for Python 2.6/More on Lists
 * Non-Programmer's Tutorial for Python 2.6/Revenge of the Strings
 * Non-Programmer's Tutorial for Python 2.6/File IO
 * Non-Programmer's Tutorial for Python 2.6/Dealing with the imperfect
 * Non-Programmer's Tutorial for Python 2.6/The End
 * Non-Programmer's Tutorial for Python 2.6/FAQ

title: User:Jrincayc


text:
Talk:Puzzles/Decision puzzles/Weighings Once More/Solution

Hi, good idea to have a general proof! Here are some things I am not so happy about yet:

You say that S(n) can measure weights between 1 and |S(n)|. In standard mathematical notation |S(n)| would be just the number of elements in S(n) which is n+1 (maybe we should introduce another symbol like W(n) or so). Also, to be technically precise, we should write $$\lfloor 3^{(n+1)}/2 \rfloor$$ rather than 3^(n+1)/2 for the upper bound of weights that can be measured. Thomas

The answer (four weights: {1,3,9,27}) is correct as far as the question is posed. But, as the question does not require weights to be measured in a single weighing, the question and answer both miss an interesting aspect of measuring integral weights: that it is not necessary for the scale to be balanced to correctly identify an unknown weight. With four known weights, {2,6,18,54}, it's possible to measure up to 80, not just 40:

If x < 2, then x = 1.

If x = 2, then x = 2.

If 2 < x < 6-2, then x = 3, etc.

You could repose the question with 80 instead of 40, or turn it around and ask what range of integral weights can be measured using four known weights.

Munin


text:
User:Minderaser

Email contact martoon42@linuxmail.org

AIM: martoon42

title: User:Minderaser


text:
User talk:Minderaser

Hi,

I intend to help writing LPI certification course. Actually I already have courses for 101, 201 and 202, although there are far from ready. The courses I have are made with OpenOffice Impress (presentation). That's compressed XML. Do you how to extract the content to the wiki?

I also intend to translate them to French. Yann 19:29, 13 Jun 2004 (UTC)

Hi, I got your message. Yes, I already upload 2 books and I plan to upload one more. Yann 14:07, 24 Dec 2004 (UTC)

title: User talk:Minderaser


text:
Vietnamese/Authors

The following people have started lessons as part of this textbook, or have made notable contributions to an existing lesson. They should be able to answer questions you may have about the Vietnamese language or Vietnamese culture:

 * Minh Nguyễn
 * Started the Vietnamese textbook, and at last count has started 8 lessons so far.
 * Nam Đỗ
 * I added some parts of my book into this course.

If you feel that you have made notable contributions to this textbook, please feel free to add your name to this list.

title: Vietnamese/Authors


text:
Talk:Vietnamese

My book
I also wrote a Vietnamese course Let's Learn Vietnamese

Writing a course
Great that Wikibooks will now have a Vietnamese course! I'm looking forward to it. I will probably start learning Vietnamese next year.

Have you seen the article on creating a language course on Wikibooks? I think it's quite useful. Also, you may want to have a look at the course format I found works best for students: Bite-sized language lessons. Good luck!

Junesun 15:24, 29 June 2006 (UTC)

Continued updates?
Doesn't seem the material has been updated any time recently, so just wanted to do a shout out to let you authors know that there are those of us still interested in learning Vietnamese. Also believe my case is quite common: fluent Vietnamese speaker who can't write Viet and reads Viet using English phonetics (which is basically an educated guess most of the time... I can do it on the fly though ;D ), so if you folks could consider making a course for Native English speakers who know how to speak Viet but can't write or really read Viet, that would be great. 206.188.32.1 (discuss) 03:26, 10 November 2011 (UTC)

title: Talk:Vietnamese


text:
Vietnamese/Version history

This is a history of the changes that this textbook has gone through:

23 December 2003

 * Vietnamese Wikibook started.

Version numbers will be in the form majorRelease#. minorRelease#. revision#, and drafts will be 0. x versions (sort of like beta versions).

title: Vietnamese/Version history


text:
The Voynich Manuscript/Leo Levitov

Levitov's claim of decipherment has been thoroughly discredited.

For a critique by linguistic science, by Jacques B.-M. Guy, see http://www.voynich.net/reeds/gillogly/levitov

For a critique by historical analysis, by Dennis J. Stallings, see http://web.archive.org/web/20010410030648/http://www.geocities.com/ctesibos/voynich/levitov2.htm

title: The Voynich Manuscript/Leo Levitov