text:
Talk:How to Learn a Language

Untitled
Article transwikied from en:wikipedia. Page history:

 * 19:34, 11 Nov 2004 Eliazar (some restructuring...)
 * 19:18, 11 Nov 2004 Eliazar (Speaking and understanding - radio broadcasts)
 * 18:58, 11 Nov 2004 Eliazar m (Reading and writing)
 * 06:14, 11 Nov 2004 68.227.20.42 (is -> are)
 * 06:03, 11 Nov 2004 201.133.186.114 (Reading and writing)
 * 03:43, 11 Nov 2004 Samaritan m (Reading and writing - linked The Little Prince, speed reading, syntax edit)
 * 01:26, 8 Nov 2004 Jondel (External links)
 * 16:42, 4 Nov 2004 83.70.192.189 (small change: fix some markup)
 * 16:39, 4 Nov 2004 83.70.192.189 (small change: remove childishism)
 * 03:19, 24 Oct 2004 194.24.244.5
 * 01:11, 21 Oct 2004 Jondel (See also)
 * 00:39, 21 Oct 2004 Jondel (See also)
 * 15:37, 18 Oct 2004 Wayland (Categories)
 * 06:46, 29 Sep 2004 Jondel (External links)
 * 06:46, 29 Sep 2004 Jondel (External links)
 * 06:45, 29 Sep 2004 Jondel (External links)
 * 01:19, 23 Sep 2004 Michael Hardy m
 * 01:02, 20 Sep 2004 Elkmann (added external link)
 * 00:52, 20 Sep 2004 Elkmann (Reading & Writing)
 * 06:51, 12 Sep 2004 PierreAbbat (Same book in two languages)
 * 09:56, 10 Sep 2004 Jondel (Children)
 * 23:46, 29 Aug 2004 69.106.5.88 (useless comma)
 * 18:46, 29 Aug 2004 RedWolf m (disambiguation: French)
 * 12:45, 28 Aug 2004 Andycjp m (link)
 * 07:48, 25 Aug 2004 Jondel
 * 07:41, 25 Aug 2004 Jondel
 * 20:18, 19 Aug 2004 149.225.58.57 (Speaking and understanding)
 * 01:26, 18 Aug 2004 BenjBot m (Benjamin Goldenberg - Robot-assisted disambiguation: Accent)
 * 23:10, 3 Aug 2004 Andycjp m (Reading & Writing - link)
 * 16:32, 2 Aug 2004 Fibonacci m (Reading & Writing - Eliminating duplicated link)
 * 16:29, 2 Aug 2004 Fibonacci m (Speaking and understanding - Fixing links)
 * 05:22, 26 Jul 2004 Jondel (Speaking and understanding)
 * 05:22, 26 Jul 2004 Jondel (Speaking and understanding)
 * 05:21, 26 Jul 2004 Jondel (Speaking and understanding)
 * 02:15, 14 Jul 2004 Jondel (Reading & Writing)
 * 02:14, 14 Jul 2004 Jondel (Reading & Writing)
 * 02:13, 14 Jul 2004 Jondel (Reading & Writing)
 * 02:12, 14 Jul 2004 Jondel (Reading & Writing)
 * 06:29, 7 Jul 2004 Woggly m
 * 06:23, 7 Jul 2004 Woggly
 * 02:24, 7 Jul 2004 Eliazar (added new section: Polishing)
 * 23:22, 4 Jul 2004 Jondel (Speaking and understanding)
 * 23:22, 4 Jul 2004 Jondel (Speaking and understanding)
 * 12:20, 4 Jul 2004 Gdr m (Speaking & Understanding)
 * 02:50, 1 Jul 2004 68.158.66.27
 * 21:15, 30 Jun 2004 205.188.116.143 (tried to categorize the tips, rewording where necessary)
 * 05:12, 22 Jun 2004 Eliazar m
 * 09:32, 27 May 2004 148.233.86.206 (minor: added "at no cost")
 * 09:26, 27 May 2004 148.233.86.206 (changes: is -> it, the -> a, and added 5 tips (the last ones))
 * 04:14, 27 May 2004 Togo (Further Links)
 * 04:07, 27 May 2004 Togo (Furter Links)
 * 03:54, 27 May 2004 Togo (Links)
 * 00:28, 26 May 2004 Jondel
 * 00:27, 26 May 2004 Jondel
 * 22:42, 25 May 2004 66.169.119.161
 * 03:57, 10 May 2004 Premeditated Chaos
 * 10:08, 1 May 2004 M.e (wikified the formatting)
 * 09:47, 20 Apr 2004 Jondel
 * 09:45, 20 Apr 2004 Jondel
 * 09:42, 20 Apr 2004 Jondel
 * 09:41, 20 Apr 2004 Jondel (Simulate dialogues in your head while waiting in line.)
 * 08:37, 20 Apr 2004 Jondel
 * 08:34, 20 Apr 2004 Jondel (language learning requires evoked emotions and whole thought- phrases.)
 * 08:26, 20 Apr 2004 Jondel
 * 08:22, 20 Apr 2004 Jondel

-- Francs2000 00:35, 15 Nov 2004 (UTC)

17 Nov 2004 Jondel reloaded the whole most recent article from wikipedia.--Jondel 07:31, 17 Nov 2004 (UTC)

Passive Learning
There are several points in the article that suggest passive or subconscious learning. I'm not familiar with any studies supporting this theory. I'd suggest either referencing something on the subject or removing them. My field is technology and language pedagogy, so I could just be unfamiliar with the research, but I'm skeptical. It seems as though people have been adding tips onto a list for sometime. A bit of cleaning my be due. I would suggest an introduction to foreign language pedagogy based on resources from scholar.google.com, with the rest of the article, or separate articles, based on the four basic skills: reading, writing, listening, and speaking.

(bryantt)

 * I'm not familiar with much about language learning, but you can add citation needed as a compromise for now.
 * There don't seem to be many active editors here so if you figure you can improve the book without upsetting anyone, just be bold and fix it up. --Swift (talk) 18:59, 6 January 2009 (UTC)

Audiobook (Pimsleur?)
This wikibook is a great effort to provide instructional tools in learning foreign language. It would be great if there is an accompanying audio instruction.

Recently I've been using Pimsleur methods to learn spanish, and I find it very good. If anyone is an expert in liguistic and language instructional methods, and is interested in doing Pimsleur audio on Indonesian language, I'd be delighted to help to read out the phrases, since I'm an indonesian native speaker. However, I can't be the one who organize and edit the audio because I don't have experience in language teaching methods. Besides, I think "pimsleur method" itself is not copyrighted (am I correct) although there are pimsleur branded instructional recordings released by Simon and Schuster. Hence I'd think it's possible to replicate the method and record our own instructional recordings in order to make language instruction more accessible (currently the Simon and Schuster Pimsleur is really expensive!).

Chaerani 01:46, 29 September 2006 (UTC)

Wikiprojet languages
I have started Wikiproject languages. Feel free to edit that page, add comment, critics and being bold.--Oualmakran Youssef 12:33, 1 April 2007 (UTC)

Mnemosyne software
I suggest that you add information about spaced-repetition software such as Mnemosyne software to the memorization section. I personally found it extremely helpful for memorization. I also suggest that you discuss IPA a bit in the section on pronunciation. 98.14.222.130 (talk) --SvenAERTS (discuss • contribs) 12:00, 19 April 2013 (UTC)

== Learning languages fast ! Encourage contributing to a list of words that both languages have in common or are very similar or easy to remember - that's a real giveaway - and little useful easy phrases and mnemotechnic means on how to remember them == It's alway very encouraging when you get to know some words in a foreign language fast. And why not start with an easy to remember list of words that are similar or very similar or for some reason easy to remember using a mnemotechnic means. Then why not start with some easy and very useful phrases and then spin out and learning how to conjugate verbs used in these very useful phrases?

--SvenAERTS (discuss • contribs) 11:41, 19 April 2013 (UTC)

title: Talk:How to Learn a Language


text:
User:Asbestos~enwikibooks

I'm a Wikipedia contributer since May 2004, and a brand-new Wikijunior contributer since mid-November. I'm currently working on the Solar System.

You can see my Wikipedia user page here.

I am best contacted at my Wikipedia talk page.

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

title: User:Asbestos~enwikibooks


text:
Talk:Koine Greek

Text of Greek Grammar

Untitled
Can you give a little framework of how you want the rest to be structured?

Pronounciation
I must refer to the wikipedia article regarding the pronounciation. The wikipedia article stresses that the changes in pronounciation have affected Koinè strongly, as one can find in the corresponding literature. What you describe here, is the classical pronounciation. Maybe you should review this chapter.2A02:587:C208:FEC2:CFC:F5F6:78B1:8F69 (discuss) 09:40, 8 July 2022 (UTC)

title: Talk:Koine Greek


text:
Thick Sand Motorcycling

How to survive thick sand
Riding a motorbike is often an exercise in defeating ones own instincts. Riding a bike in thick sand is a good example of this. Instinct says go slowly when approaching anything threatening; however, going slowly on a bike is a sure way of having an accident, more so when riding in a threatening situation.

When approaching an area of thick sand it is best to slow down while approaching, then gently accelerate upon reaching the sandy patch. Motion is what gives stability to any bike, be it a bicycle or a motorbike.

With a motorbike, this stability is especially linked to the back tire's grip on the ground. Applying too much power will cause the back wheel to spin, thus losing grip, causing the bike to either fall over or dig its back wheel into the sand.

If the sand is particularly thick, fine, or both, and the back wheel has dug itself in, the best thing to do in this situation is to get off, use the "clutch and accelerator" combined to gently apply forward motion; then run with the bike past the worst bit, and finally leap back on.

Instinct causes panic when it feels as if things are out of your control. Often, when in a situation like thick sand, the bike will throw itself about a bit; this is normal, and often a hint that one is going too slowly. The worst thing you can do on a bike is to stiffen up. Rather, sit upright, lean slightly forward, and relax your arms. If the going is really bad, stand up on the pegs, and lean forward. The main thing is relax and give the bike the power it needs to get out.

title: Thick Sand Motorcycling


text:
Talk:Thick Sand Motorcycling

Page history from How-to/Motorcycling.

 * 18:02, 8 Sep 2004 Merovingian m (fix)
 * 18:02, 8 Sep 2004 Merovingian m (Reverted edits by UltraAyla to last version by Booyabazooka)
 * 04:28, 5 Sep 2004 UltraAyla (How to survive thick sand)
 * 04:28, 5 Sep 2004 UltraAyla m (How to survive thick sand)
 * 01:00, 24 Aug 2004 Booyabazooka (grammar and such)
 * 22:06, 11 Aug 2004 Rossami m (removing vfd header)
 * 02:58, 30 Jul 2004 Kenwarren m (vfd)
 * 13:27, 6 Apr 2004 62.200.132.17
 * 13:26, 6 Apr 2004 62.200.132.17

-- Francs2000 01:20, 15 Nov 2004 (UTC)

title: Talk:Thick Sand Motorcycling


text:
User talk:Francs2000~enwikibooks

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 Francs2000. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Francs2000~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

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

Sorry for the inconvenience.

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

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

title: User talk:Francs2000~enwikibooks


text:
User:D.b.ingram

I am a senior Chemical Engineering undergraduate student at Texas A&M University, College Station, with a minor in Linguistics.

title: User:D.b.ingram


text:
User:James Dennett

See my page on the original C2 wiki.

My primary focus here on Wikibooks is in writing about C++ Programming.

title: User:James Dennett


text: User talk:68.225.239.63

title: User talk:68.225.239.63


text:
Introduction to Philosophy/Logic/Bibliography

Introduction to Philosophy > Logic > Bibliography

I have difficulty recommending any books on logic. Perhaps that indicates the need for the present work. Perhaps you can recommend one to me. You might want to look at:

Wilfred Hodges, Logic  Penguin Books, 1977  ISBN 0140219854

The next two books on the list are definitely rather mathematical:

 * Elliott Mendelson, Introduction to Mathematical Logic Wadsworth & Brooks/Cole, 1987  ISBN 0534066240

 * The word 'introduction' in the title needs to be taken with a pinch of salt.

 * Boolos & Jeffrey, Computability and Logic

Up: Logic Table of Contents


text:
Introduction to Philosophy/Logic/Fault Diagnosis

Introduction to Philosophy > Logic > Fault Diagnosis

Our propositional calculus can be quite useful for descriptions of systems and fault diagnoses. Here are some propositions regarding part of a fairly simple plumbing system:

____________________________________________
 * If there is an overflow in the upper tank, then the buzzer is sounding or there is an electrical problem.
 * If there is water dripping from the ceiling, then there is an overflow in the upper tank.
 * The buzzer is not sounding.
 * There is water dripping from the ceiling.

 * There is an electrical problem.

As with many things the propositions could be divided into:

 * observations, e.g. 'the buzzer is sounding';
 * hypothetical if-then statements;
 * diagnoses.

Anyway, to show that the argument above is valid, we first assign letters to all the elementary propositions:

 * p - there is an overflow in the upper tank;
 * q - the buzzer is sounding;
 * r - there is an electrical problem;
 * s - water is dripping from the ceiling.

Then we can write our propositions out using symbols:

 * P → (q ∨ r)
 * s → p
 * ¬ q
 * s

With fairly simple systems, one's intuition usually provides the correct answer fairly quickly. If you think of a chemical plant or a power station, the chains of inference can get quite complicated, yet swift action may be required in the case of a fault. In this case automated reasoning in the form of 'expert systems' can be quite useful. (Of course then there is the problem that the expert system could be faulty. Here we encounter the problem of infinite regress.)  When the reasoning gets complicated, the kind of analysis we have done here becomes useful.

If this kind of thing interests you, then perhaps you should study artificial intelligence.


text:
The Linux Kernel

Contents

 * About the book
 * /Human interfaces/
 * about HID, media, v4l, UVC, ALSA, console, input, cdev, security
 * /System/
 * about booting, devices, buses, PCI, interfaces, /Syscalls/, /sys, /proc, modules, updating and debugging
 * /Multitasking/
 * about processes, threads, scheduling, synchronization, interrupts
 * /Memory/
 * about address spaces, memory allocation, memory mapping, VM, pages, data types, swap
 * /Storage/
 * about block devices, filesystems, VFS, ext3, disk cache, SATA, SCSI,
 * /Networking/
 * about network drivers, Ethernet, sockets, TCP/IP, NFS

 * /External links/

title: The Linux Kernel


text:
Pascal Programming/Routines

In the opening chapter routines were already mentioned. Routines are, as it was described before, reusable pieces of code that can be used over and over again. Examples of routines are  /   and   / . You can invoke, call, these routines as many times as you want. In this chapter you will learn
 * how to define your own routines,
 * the difference between a definition and declaration, and
 * the difference between functions and procedures.

Different routines for different occasions
Routines come in two flavors. In Pascal, routines can either replace statements, or they replace a (sub‑)expression. A routine that can be used where statements are allowed is called a. A routine that is called as part of an expression is a.

Functions
A  is a routine that returns a value. Pascal defines, among others, a function. The function  takes one  -expression as a parameter and returns   or , depending on the parity of the supplied parameter (in layman terms that means whether it is divisible by 2). Let’s see the function  in action: is pronounced “odd of x”. First, the expression in parentheses is evaluated. Here it is simply, the variable’s value to be precise, but a more complex expression is allowed too, as long as it eventually evaluates to an  -expression. The value of this expression, the actual parameter, is then handed to a (in this case invisible) block of code that processes the input, performs some calculations on it, and returns  or   according to the calculation’s findings. The function’s returned value is ultimately filled in in place of the function call. You can, in your mind, read  /   in place of , although this is dynamic depending on the given input.

Procedures
Procedures on the other hand cannot be used as part of an expression. You can only call procedures where statements are allowed.

Effects
A  may use functions, and the other way around. Do not understand a  as a mere substitute for an expression. In the following section we will learn why.

Rationale
The dichotomy of routines, distinguishing between a  and a , is meant to gently push the programmer to write “clean” programs. Doing so, a routine does not conceal whether it is just a replacement for a sequence of statements or shorthand for a complex, difficult to write out expression. This kind of notation works without introducing nasty pseudo types like, for example,  in the C programming language where every routine is a function, but the “invalid” data type   will allow you to make it (in part) behave like a.

Definition
Defining routines follows a pattern you are already familiar with since your very first. A  is, in some regards, like a special routine: You can run it as many times as you want through OS-defined means. A ’s definition looks almost just like a routine’s.

A routine is defined by, in that order. The routine header shows a couple differences depending on whether it is a  or. We will first take a look at blocks, since these are the same for both types of routines.
 * 1) a header, and
 * 2) a block

Block
A block is the synthesis of a productive part (statements) and (optional) declarations and definitions. In Standard Pascal (as laid out by the ISO standard 7185) a block has a fixed order: All items but the last one, the productive part, are optional.
 * 1) constant definitions (the  -section)
 * 2) type definitions (the  -section)
 * 3) variable declarations (the  -section)
 * 4) routine declarations and definitions
 * 5) sequence (, possibly empty)

In EP, the fixed order restriction has been lifted. There, sections and routine declarations and definitions may occur as many times as needed and do not necessarily have to adhere to a particular order. The consequences are detailed in the chapter “Scopes”. For the remainder of this book we will refer to EP’s definition of block, because all major compilers support this. Nevertheless, the order defined by Standard Pascal is a good guideline: It makes sense to define types, before there is a section that may use those types (i. e. -section).

Header
A routine header consists of
 * 1) the word   or  ,
 * 2) an identifier identifying this routine,
 * 3) possibly a parameter list, and,
 * 4) lastly, in the case of functions, the data type of an expression a call to this function results in, the result data type.

The parameter list for routines also defines the data type of every single parameter. Thus, the header of the function  could look like this: Take notice of the colon after the parameter list separating the function’s result data type. You can view functions as sort of special variable declaration which also separates an identifier with a colon, except in the case of a function the “variable’s” value is computed dynamically.

Formal parameters, i. e. parameters in the context of a routine header, are separated by a semicolon. Consider the following procedure header: Note that every routine header is terminated with a semicolon.

Body
While the routine header tells the processor (usually a compiler), “Hey, there’s a routine with the following properties: […]”, it is not enough. You have to “flesh out”, give the routine a body. This is done in the subsequent block.

Inside the block all parameters can be read as if they were variables.

Function result
In the sequence of the block defining a function there is automatically a variable of the function’s name. You have to assign a value exactly one time, so the function, mathematically speaking, becomes defined. Confer this example: Note that the block did not contain a -section declaring the variable , but it is already implicitly declared by the function’s header: Both the name and the data type are part of the function header.

Declaration
A routine declaration happens most of the time implicitly. Declaring a routine, or in general any identifier, refers to the process of giving the processor (i. e. usually a compiler) information in order to correctly interpret your program source code. This information is not directly encoded in your executable program, but it is implicitly there. Examples are: Declarations make an identifier known to denote a certain object (“object” mathematically speaking). Definitions on the other hand will, hence their name, define what this object exactly is. Whether it is a value of a constant, the value of a variable, or the steps taken in a routine (the statement sequence), data defined through definitions will result in specific code in your executable file, which may vary according to the information given in related declarations; writing a variable possessing the data type  is fundamentally different than writing a value of the type. The code for properly storing, calculating and retrieving  and   values differs, but the computer is not aware of that. It just performs the given instructions, the circumstance that a certain set of instructions resemble operations on Pascal’s data type  for instance is, so to speak, a “coincidence”.
 * A variable declaration tells the processor to install proper provisions in order to reserve some memory space. This chunk of memory will be interpreted according to its associated data type. However, neither the variable’s name, nor the data type are in any way stored in your program. Only the processor knows about this information as it is reading your source code file.
 * A routine header constitutes a routine declaration (which is usually directly followed by its definition ). Here again, the information given in a routine header are not stored directly in the executable file, but they ensure the processor (the compiler) will correctly transform your source code.
 * Likewise,  declarations merely serve the purpose of clean and abstract programming, but those declarations do not end up in the executable program file.

Routing
Routines are selected based on their signature. A routine signature consists of Thus the signature of the function  reads. The function named  accepts one   value as the first (and only) argument.
 * 1) the routine’s name,
 * 2) the data type’s of all arguments, and
 * 3) (implicitly) their correct order.

Overloading
Pascal allows you to declare and define routines of the same name, but differing formal parameters. This is usually called overloading. When calling a routine there must be exactly one routine of that name that accepts parameters with their corresponding data types.

Persistent variables
Some compilers, such as the FPC, allow you to use constants as if they were variables, but different lifetime. In the following example the “constant”  exists for the entire duration of program execution, but is only accessible in the scope it was declared in. The program will print,  ,   for every call. Lines 2, 4, and 5 contain specially crafted comments that instruct the compiler to support persistent variables. These comments are non-standard, yet some are explained in the appendix, chapter “Preprocessor Functionality”.

Note, the concept of typed “constants” is not standardized. Some object-oriented programming extensions will give nicer tools to implement such behavior as demonstrated above. We primarily explained the concept of persistent variables to you, so you can read and understand source code by other people.

Benefit
Routines can be used as many times as you want. They are no tools of mere “text substitution”: The definition of a routine is not “copied” to the place where it is called, the call site. The size of the executable program file remains about the same.

Utilizing routines can also be and usually is beneficial to the development progress of a program. By splitting up a programming project into smaller understandable problems you can focus on solving isolated issues as part of the big task. This approach is known as divide and conquer. We now ask you to slowly shift toward thinking more about your programming tasks before you start typing anything. You may need to spend more time on thinking about, for example, how to structure a routine’s parameter list. What information, what parameters, does this routine require? Where and how can a recurring pattern be generalized through a routine definition? Identifying such questions needs time and expertise, so do not be discouraged if you are not seeing everything the task’s sample answers show. You will learn through your mistakes.

Keep in mind, though, routines are no panacea. There are situations, very specific situations, where you do not want to use routines. Recognizing those, however, is out this book’s scope. For the sake of this textbook, and in 99% of all your programming projects you want to use routines if possible. Modern compilers can even recognize some situations where a routine was “unnecessary”, yet the only gain is that your source code becomes more structured and thus readable, albeit at the expense of being more abstract and therefore complex.

Tasks
Notes:

title: Pascal Programming/Routines


text:
Puzzles/Arithmetical puzzles/Luxury Cars/Solution

Puzzles | Arithmetical puzzles | Luxury Cars | Solution

Los Angeles - 256 New York - 192 San Francisco - 144 Boston - 108 Miami - 320

Reasoning
Let L, N, S, B, M be the numbers of cars sold at Los Angeles, New York, San Francisco, Boston and Miami respectively.

The statement of the puzzle gives these equations:

L = (L + N + S + B + M)/4 + 1 N = (N + S + B + M)/4 + 1 S = (S + B + M)/4 + 1 B = (B + M)/4 + 1 L + S = B + N + 100 (a)

The first four equations can be simplified:

4L = L + N + S + B + M + 4 4N = N + S + B + M + 4 4S = S + B + M + 4 4B = B + M + 4

3L = N + S + B + M + 4 3N = S + B + M + 4 3S = B + M + 4 3B = M + 4

3L = N + 3N = 4N (b) 3N = S + 3S = 4S (c) 3S = B + 3B = 4B (d) 3B = M + 4      (e)

From equation (a) we have

4L + 4S = 4B + 4N + 400 => 4L + 4S = 3S + 3L + 400 => L + S = 400 => L = 400 - S

Combining this equation with equations (b) and (c) gives

3(400 - S) = 4N => 9(400 - S) = 12N = 16S => 3600 - 9S = 16S =>       25S = 3600 =>         S = 144

From this result and equations (b) to (e), the remaining values easily fall into place:

L = 256 N = 192 S = 144 B = 108 M = 320


text:
User:Smjg

Hi! Stewart here, a regular on Wikipedia who, when on Wikibooks, mostly does Puzzles.

On other Wikimedia projects

 * Wikipedia Meta-Wiki
 * Wikipedia
 * Vikipedio

title: User:Smjg


text:
Talk:Puzzles/Easy Sequence 3/Solution

Solution (a) doesn't make sense. Look - the differences are 1, 4, 8 i.e. 2^0, 2^2, 2^3. -- Smjg 16:22, 15 Nov 2004 (UTC)

title: Talk:Puzzles/Easy Sequence 3/Solution


text:
Wikijunior:Solar System/Asteroid belt

The asteroid belt lies between the planets Mars and Jupiter. It contains lumps of rock and metal much smaller than planets. These lumps are called asteroids or minor planets. They are not visible from Earth with the naked eye, but many may be seen through binoculars or small telescopes.

The largest asteroid in the solar system is called "2001 KX76." In the asteroid belt, the four largest bodies are Ceres (a dwarf planet named after the Roman goddess of agriculture), Vesta (the Roman goddess of the home), Pallas (the granddaughter of Poseidon), and Hygiea (the Greek goddess of health). These four bodies make up about half of the asteroid belt.

Some asteroids are less than a kilometer across. Unofficially the limit has been set at 50 meters, and anything smaller than that is going to be simply called a meteoroid. With advances in telescopes and particularly for objects that travel close to the Earth, some objects smaller than 50 metres have indeed been seen passing nearby the Earth.

There are probably several million asteroids in the solar system. Over 96,000 asteroids have been given numbers. Almost 12,000 of them have names. But even though there are a lot of asteroids, the asteroid belt is mostly empty space. Traveling through the asteroid belt in a space ship would not be very much like what you see in a science fiction film. This would not be the same in the first 100 million years of the solar system's history (had humans evolved and discovered film). The asteroid belt lost 99.99% of its mass in the first 100 million years of the solar system.

What are they named after?
The first asteroids were named after mythical heroes and gods much like the major planets. The first to be discovered was named Ceres after the Roman goddess of growing plants (particularly grain) and of motherly love. The second asteroid discovered was called Pallas and was named after one of the Greek gods of wisdom. Asteroids are also given a number in the order of their discovery, so Ceres is 1, Pallas is 2, and so forth.

As the number of known asteroids increased, they ran out of mythical names so other names were used instead. Some asteroids were named after countries. For example asteroid number 136 is named Austria. Others were named after plants, for example 978 Petunia. 1620 Geographos was named after the National Geographic Society, in recognition to their efforts at sharing knowledge about the Solar System. Many are named after people, both alive and dead. In a couple of cases, like 2309 Mr. Spock, asteroids were named after the discoverer's pet cat. This last type of naming is discouraged, but it still happens from time to time. Even fictional characters have been used.

Today, names for asteroids can be suggested by the people who discover them. The names become official after a group of people reviews them to make sure they are not offensive or too much like another name. Because so many asteroids are now being found, most new asteroid discoveries are not even getting a name at all, but rather a numbered code. It is not likely that they will ever be given a formal name, at least in this century.

The actual word Asteroid can refer to any member of the family of Asteroidea; in other words, a starfish. The etymology of the word comes from Ancient Greek ἀστεροειδής, literally meaning star form. The Ancient Greeks probably must have mistook the asteroids for stars.

Most of the asteroids have symbols representing them; for example, Ceres has ⚳, representing Ceres's scythe, and Pallas has ⚴, reperesenting Athena's spear.

Who discovered them?
Asteroid Belt Facts:

 * The total mass of all the asteroids in the asteroid belt is about 1/35th of that of our moon.
 * The largest object in the asteroid belt, Ceres, makes about 1/3 of the total weight of all the asteroids.
 * Ceres is the only dwarf planet in the asteroid belt.
 * Vesta is the only asteroid that can ever be seen with the naked eye. Its magnitude can reach +5.1, about the same as Uranus.
 * Although people probably saw Vesta and Uranus thousands of years ago, they were not recognised to orbit the Sun until 200 years ago.

The first asteroid to be discovered was Ceres, on 1 January 1801, by Giuseppe Piazzi accidentally. At first he thought this was a comet, then later a planet! When it was realised it was too small Sir William Herschel (the astronomer who discovered Uranus) made up the word "asteroid" to describe it, using the Ancient Greek word aster, meaning star, and the -oid, meaning form or shape. In other words a star-like planet, because he couldn't see any details due to the small size of the object.

By 1807 another 3 asteroids were discovered, but no more were found until 1845 when a persistent asteroid hunter named Karl Ludwig Hencke found a fifth, and sixth asteroid in 1847. Ever since then at least one new asteroid has been found each year.

In 1891, the first pictures of the night sky were taken to find more asteroids. This led to the discovery of many more asteroids. A picture of the same part of the sky is taken on two different nights. When the two pictures are lined up, the stars will be in the same places but an asteroid will have moved.

In our modern times, over 280,000 asteroids have been discovered. Many more are being found all the time. Some of these asteroids pass near the earth and astronomers want to find any that come close to our planet. Large numbers of asteroids are now being discovered by machines.

What are they made of?
Three out of four asteroids are made of rock that is rich in carbon. The rest are made of the metals iron and nickel. About half of these are pure iron and nickel; the rest are mixed with compounds of silica, the element that makes up rocks. Each of the larger metal asteroids contains huge amounts of iron: much more than is mined every year on Earth. Vesta, the brightest asteroid, has a very unusual composition - being made of high-density volcanic rocks.

Scientists are very interested in what asteroids are made of because it can help them learn how the solar system was formed. Several spacecraft have visited asteroids to learn more about them.

Are there asteroids outside of the asteroid belt?
Most asteroids are found in the asteroid belt, but not all. Some asteroids orbit closer to the Sun, and many asteroids orbit beyond Neptune. Asteroids that closely approach Earth are called Near-Earth Asteroids. Sometimes pieces of asteroids strike the Earth, burning in the atmosphere as a meteor. If they are large enough, they might actually hit the surface and become meteorites.

A centaur is a mythical beast having a horse's body with a man's head and torso in place of the head and neck of the horse. There are some asteroids in the outer solar system that are called Centaurs. It is hard to tell whether any one Centaur is an asteroid, comet, or Kuiper Belt object. For example, the first Centaur to be discovered was Chiron(In Greek Mythology, an important centaur). But some scientists think it is a comet, not an asteroid. Officially it is called both the asteroid 2060 Chiron and the comet 95P/Chiron!

In most cases when an asteroid's orbit crosses the path of a planet such as Jupiter, at some point the asteroid will either hit the planet or else be hurled into another orbit. Many of the small moons of some planets may have once been asteroids that were captured by the planet's gravity when they came too close. However there are two points along the orbit of a planet were an asteroid can safely linger. These are found at a point one-sixth (or 60°) of an orbit ahead of the planet, and the same distance behind the planet. These sites are called Lagrange points, and they are found where the force of gravity from the Sun and the planet balance out with the motion of the asteroid's orbit. The asteroids found in these spots are called Trojans, and they move around the Sun at the same velocity as the planet.

Ceres

Ceres is a large Dwarf Planet like Pluto located in the asteroid field. The difference between Ceres and most other dwarf planets is that it is also an asteroid. Ceres is one of the few asteroids that are shaped like      a sphere, and it may have some ice just underneath its dusty surface. It was discovered in 1801 by Giuseppe Piazzi, who was an Italian astronomer.

Some famous asteroids
Ceres the first discovered and biggest asteroid in the solar system.

The asteroid Ida has its own moon named Dactyl. A number of asteroid moons have now been found.

Next Topic: Jupiter

title: Wikijunior:Solar System/Asteroid belt


text:
Wikijunior talk:Solar System/Asteroid belt

Name
As a chapter, this should be called "Asteroid Belt" with a capital "B". I'd move it, but I'm worried it might mess up the templates. Rachel 16:45, 19 October 2005 (UTC)

Should it be just called asteriods? Most of the info is just on asteroids - generally. There isn't even a section on how the belt came to be, or why it stays there ( all ordered) but yet there are other asteroids randomly in the solar system etc. [[User:cilstr 11:45, 16 August 2006

Writing this module as an introduction to other modules
When doing the "cleanup" of this module, it might be nice to make this more into an introduction of the asteroids as a general topic, with this being a launching point to other sections on specific Asteroids. There is indeed a rich history for Ceres and Vesta, and some detailed information together with pictures (important for kids!) of several other asteroids. Ceres in particular is going to be an interesting topic not only because it is the largest of all asteroids, but because there is a robotic mission that is going to do specific exploration of that asteroid that has already been designed and is scheduled to launch some time next year. --Rob Horning 19:25, 19 October 2005 (UTC)

Response
I dont really understand your point, but I agree that this module needs an overhaul (if your not working on this anymore, then disregard), but as I edit I will focus on reorganization and rewriting Basejumper123 01:00, 11 May 2006 (UTC)

Reorganize
I removed these pictures from the top of the page in order to reorganize it, Im no good at coding, so would someone turn this into legitamate code that will fit on the page?

 "] ]"

 * Sorry but I reverted you. Whilst reorganising you removed the section on what asteroids were made of and you removed they key facts box on asteroids. I realise that the top of the page is a bit ugly at the moment but some of that is caused by the cleanupboxes. Theresa knott 13:58, 12 May 2006 (UTC)

April 26, 2007- I know that the asteroid belt is awesome and I also know that the gravitational pull of the planets occasionally take an asteroid or two out of the belt. Jupiter is the planet that keeps the asteroid belt in place as it revolves around the sun. P.S.- There are around 40,000 asteroids in the asteroid belt.

Proofing
I did a quick proofing check of this page and have a few suggestions: Thanks. — RJHall 21:52, 21 August 2006 (UTC)
 * 1) It contains lumps of rock much smaller than planets. There are asteroids that are made primarily of metal. (See "M-type asteroid" on wikipedia). It would be more correct to say "rock or metal", or even "rock and metal".
 * 2) The largest asteroid is 2001 KX76. While this is true (depending on whether the plutino definition is accepted by the IAU) '2001 KX76' is in the Kuiper belt, rather than the asteroid belt. I would suggest changing the text to read: "The largest asteroid in the solar system is 2001 KX76. The largest asteroid in the asteroid belt is Ceres, which is 1,032 kilometers across."
 * 3) Some asteroids are less than a kilometer. It should say "across".
 * 4) some objects have been seen that are indeed smaller than 50 meters that merely pass nearby the Earth. Awkwardly worded. How about: "some objects smaller than 50 metres have indeed been seen passing nearby the Earth."
 * 5) Due to some automated asteroid scanning observatories and a systematic exploration of the Solar System for near-Earth asteroids seems too technical. "Because so many near Earth asteroids are now being found" cuts to the chase. Perhaps the "Who discovered them?" section could mention the automated observatories?
 * 6) Ida is the only asteroid with a moon, named Dactyl. Not even remotely true. At least 37 have been discovered so far. There may be many, many more. C.f. the wikipedia article on "Asteroid moon".
 * These are changes that should be made. If you don't get around to it, I'll do it in the next week or so. --Xixtas 05:09, 31 August 2006 (UTC)
 * Okay it's done. Thanks. — RJHall 18:04, 3 September 2006 (UTC)

Table of largest asteroids in the belt?
Would it make sense to include a table of the five largest asteroids (by maximum dimension) in the belt? — RJHall 18:37, 9 November 2006 (UTC)

 * That seems like a good idea. I have a question though. Is Ceres still an asteriod? I thought it was now a dwarf planet and not an asteroid. Is it both? --xixtas 21:04, 9 November 2006 (UTC)

 * Out of curiosity, how many asteroids fit the current IAU definition of a "minor planet"? (aka with Pluto, Quorar, etc.) That might be a good limit on what to include in this table, as I think Ceres and Vesta both fit the description and definition.  --Rob Horning 21:23, 9 November 2006 (UTC)

 * According to Wikipedia Ceres is considered a dwarf planet and Vesta, Pallas and Hygiea may be if it is determined that their shapes are formed by hydrostatic equilibrium. Wikipedia Dwarf Planet. According to NASA "According to the IAU, more dwarf planets are expected to be announced in the coming months and years. Currently, a dozen candidate dwarf planets are listed on IAU's dwarf planet watchlist, which keeps changing as new objects are found and the physics of the existing candidates becomes better-known." and "Instead, on August 24, 2006, an alternate proposal came into effect labeling Ceres a 'dwarf planet'. It is not yet clear whether dwarf planet status is, like planet status, a sole defining category, or whether dwarf planets also retain their previous minor body classifications such as 'asteroid.'" --xixtas 04:37, 10 November 2006 (UTC)
 * Well, since this is about the asteroid belt, we could just say "Largest bodies in the asteroid belt". That would get around whether they are asteroids or not. — RJHall 22:48, 17 November 2006 (UTC)

Trojan asteroids
The one portion of the text that I think may be problematic for wikijunior is the final paragraph of "Are there asteroids outside of the asteroid belt?" I.e. the whole concept of Trojans, Lagrange points, and 60° stable orbit locations. Is this going to work for a very young reader? Perhaps that paragraph needs to be simplified or explained a little more? Thanks. — RJHall 18:36, 9 November 2006 (UTC)
 * The paragraphs contain some interesting information. I think they add value to the article, but may be a little overly technical for the audience. So I'm not sure. I would lean toward trying to simplify the language rather than removing them completely. --xixtas 21:10, 9 November 2006 (UTC)
 * I tried to work on the text, but I'm not sure I completely succeeded. Thanks. — RJHall 19:25, 18 November 2006 (UTC)


text:
Project Management

Project Management is an organized approach to guiding a project from its inception to closure. Managing projects is becoming more and more important as we enter the digital era. To cope with the pace that this transition demands, a method is required to manage projects so they can yield quality work, while incorporating efficient use of time and resources. In this Wikibook, several project management methods/processes are outlined: the Project Management Body of Knowledge (PMBOK) and Projects in Controlled Environments (PRINCE2) approaches can be applied to managing any type of project; whereas methods such as SDM, DSDM, RAD, ISAC, SA/SD, IEM and OO are specific to managing Information Technology (IT) projects. Before some of these project management methods/processes are explored in this Wikibook, we will review some project essentials, such as the definition of a project and the project lifecycle.

Table of Contents

 * /Fundamentals/
 * /Portfolios/Programs Management/
 * /Organization structures/

The Project Management Body of Knowledge (PMBOK)

 * Core Knowledge Areas
 * Scope Management
 * Time Management
 * Cost Management
 * Quality Management

 * Facilitating Knowledge Areas
 * Communications Management
 * Human Resources Management
 * Risk Management
 * Procurement Management

 * Coordination Knowledge Area
 * Integration Management

PRINCE2 (PRojects In Controlled Environments)

 * Starting Up a Project
 * Directing a Project
 * Initiating a Project
 * Controlling a Stage
 * Managing Stage Boundaries
 * Managing Product Delivery
 * Closing a Project

Case Studies

 * /Northstar/

Appendices

 * /FAQs/

title: Project Management


text:
Talk:Perl Programming/Function reference

I removed the last two examples of grep, as they are better accomplished through map and for respectively. grep should not be used in a void context. MrItty 18:54, 15 Nov 2004 (UTC)

"Program Functions"
This needs to be cleaned up. It seems that all of the functions in this section (save 'caller') are listed elsewhere in the page. I've already removed my and local, as they were defined in Misc Functions. The rest seem to be listed under Module Functions. -- MrItty 19:53, 16 Nov 2004 (UTC)

"examples"
At the bottom, it states that uc and lc reverse each other. This sets off alarm bells- is lc(uc("QWERTY")) actually "qwerty"? I don't know Perl, so it may be intelligent enough to make that distinction. Not a user-- ARC. 13:24, 3 Jun 2005 (EST)

 * lc lowercases an entire string. uc uppercases it.  so in that sense, yes, they're "reverse".  But lc(uc("Foo")) is not "Foo". --RandalSchwartz 00:41, 28 Jun 2005 (UTC)

Structure
I've made this page my definitive perl function reference page but it is still quite unstructured and incomplete.

Might I suggest: ==Category== ===Function=== ====Action==== Description of action ====Returns==== Description of return value ====Syntax==== function($variable = default value); ====Example==== Example 1; Example 2; ====See Also==== * link to function - To {Description of action} * link to function - To {Description of action} For example: ==Array functions== ===pop=== ====Action==== Remove the last element from an array ====Returns==== The element removed ====Syntax==== pop(@array = @_); ====Example==== $LastElement = pop(@MyArray); ====See Also==== * Function reference - To remove an a set of elements from an array * Function reference - To remove the first element from an array

===splice=== ====Action==== Remove a set of elements from an array. Optionally, replace those elements with a new array ====Returns==== An array of elements removed ====Syntax==== splice(@array=@_,$first=0,$last=$#array,@replacementArray=) ====Example==== splice(@Array); # Removes all elements from array splice(@Array, 10); # Removes from element 10 to the end of the array splice(@Array, -10); # Removes the last 10 elements of the array splice(@Array, 0, 10); # Removes the first 10 elements of the array @NewArray = splice(@Array, 0, 10); # Removes the first 10 elements of the array and returns those 10 items splice(@Array, 0, 10, @Array2); # Replaces the first 10 elements of the array with Array2 ====See Also==== * Function reference - To remove the last element from an array * Function reference - To remove the first element from an array Any thoughts on this?


text:
Wikijunior:Solar System/Kuiper Belt

Kuiper Belt Facts:
 * The Kuiper belt is the most recently discovered section of the Solar System.

Beyond the orbit of Neptune lies the Kuiper belt. It extends outward an additional three billion kilometers away from the Sun. The belt contains different-sized lumps of icy mixtures. These lumps are called Kuiper belt objects. The biggest are called minor planets or dwarf planets. The Kuiper belt may have formed when the gravity of the young planet Jupiter hurled the objects out to where they are now. The Kuiper belt is named after Gerard Kuiper (rhymes with "viper"), one of several astronomers who hypothesized about a field of small objects beyond Neptune.

What are Kuiper belt objects?
The objects in the Kuiper belt are frozen mixtures of dirt, ice and organic compounds. They are a lot like comets. Some of the objects have a reddish color and others are gray.

How big are the Kuiper belt objects?
Scientists consider Pluto to be one of the largest Kuiper belt objects. It is 2390 km across and is a dwarf planet. The next largest known Kuiper belt objects are Orcus, 2003 EL61 and 2005 FY9. Orcus is about 1600 km (1,000 miles) across; 2003 EL61 is 70% the size of Pluto and 2005 FY9 is about 50% to 70% of Pluto's size.

Recently, scientists found another dwarf planet named Eris that is even bigger than Pluto. The scientists don't know its exact size, but they think it is about 20% larger than Pluto. At the time it was found, it was almost 100 times further away from the Sun than the Earth. It can come about as close to the Sun as Pluto. Eris has a moon named Dysnomia. The orbit of Eris is tilted almost 45 degrees compared to Earth's orbit. Pluto's orbit is only tilted by 17 degrees.

Other large Kuiper belt objects about or over 1000 km across are Pluto's moon Charon, Quaoar, Varuna, Ixion, 1996 TL66, 2002 TX300, 2002 TC302, 2002 UX25 and 2002 AW197. Ceres, the largest asteroid in the asteroid belt, is about 950 km across.

There are many other Kuiper belt objects that are only a few kilometers or tens of kilometers across.

How many Kuiper belt objects are there?
Over a thousand Kuiper belt objects had been found by astronomers. Scientists think that there might be more than seventy thousand large objects in the Kuiper belt. Even though there are so many objects in the Kuiper belt, it is very light, weighing between 1/25 and 1/30 of Earth's mass.

What is it named after?
After the first object in the belt other than Pluto and its moon Charon was spotted from the Mauna Kea Observatory in Hawaii in 1992, the belt was named after the astronomer Gerard Kuiper. Back in 1951 this scientist wrote that he thought this belt might exist, but there was no proof at that time. Other astronomers, including Frederick Leonard, Kenneth Edgeworth, and Julio Fernandez, also thought that the belt existed. For this reason some astronomers call it the Edgeworth-Kuiper belt.

What are the Kuiper belt objects named after?
When an object is discovered in space, it is given a temporary name called a "provisional designation". This temporary name begins with the year the object was discovered, followed by some letters and numbers that tell in what month and in what order it was discovered. Later on, important objects are given formal names, often taken from mythology.

The Kuiper belt objects Orcus, Charon, and Varuna were all named after mythological gods of the underworld. Ixion was named after a mythological person in the underworld. Quaoar was named after a creation god of the Native American Tongva people.

Next Topic: Oort Cloud

Wikijunior Sonnensystem/ Kuipergürtel

title: Wikijunior:Solar System/Kuiper Belt