text:
Dutch/Alfabet

Het alfabet ~ The alphabet
The Dutch alphabet, like English, consists of 26 basic letters. However, there are also a number of letter combinations. The following table includes a listing of all these letters and a guide to their pronunciation. As in English, letter sounds can differ depending upon where within a word the letter occurs. The first pronunciation given below (second column) is that in English of the letter (or combination) itself. Reading down this column and pronouncing the "English" words will recite the alphabet in het Nederlands (in Dutch). Note that letter order is exactly the same as in English, but pronunciation is not the same for many of the letters. Trouble areas for Anglophones are marked in red

Diacritics
Diacritics are not very numerous in Dutch and they are mostly limited to loans, but the orthography does for example demand a diaeresis, mostly on ë and ï in words like geërgerd, geïnteresseerd. It marks the boundary of two syllables and is fairly common. It is not to be confused with the German umlaut that only occurs on a few German loans like überhaupt.

Less commonly, the orthography also allows stress marks to be added. Acute accents can be used for that purpose, but only then if:
 * 1) special and unusual emphasis in sentence is to be indicated, e.g. to express surprise
 * Heb je een áúto?!
 * 1) the context leaves doubt about the identity of the word:
 * Een school doorlópen is niet hetzelfde als een school dóórlopen.

There are some 200 words and word forms that occur in two forms that only differ in stress pattern, where that can be an issue.

For diphthongs and doubled vowels both vowels are marked as in áúto. In principle this holds for the digraph ij as well. The j should also get an acute, but computers usually do not facilitate that. Here we will write íj if the need arises.

A stress mark is not be confused with an accent grave, aigu or circonflex as it can occur on the more numerous French loans like café, à propos or maîtresse. Interestingly Dutch orthography maintains the î in the latter, although French dropped it in 1990. The grave is also used on the verb blèren. It is an indigenous onomatopoeia that mimics the bleating of sheep with an unusual long [ɛ:] sound.

The cedille is rare but occurs in a few French and Portuguese loans like façade, Curaçao

A useful tip is to install a Dutch international keyboard. For Microsoft operating systems this will tell you how to proceed.

Klinkers
Dutch has quite a few vowels (13). To be well understood by a native speaker it is imperative to master them, which can be quite challenge for native speakers of languages that rely more on their many consonants such as Russian. One general observation is that they are always pronounced as more or less pure (or only slightly diphthongized) vowels as in French, never quite as drawled or 'chewed upon' as in many varieties of English. Admittedly this does vary from speaker to speaker and region to region, but for Anglophones it is certainly advisable to limit the 'drawling'.

Most vowels occur in pairs that are traditionally indicated by the terms short and long. Unfortunately, this nomenclature is rather misleading because the difference is not so much a matter of length, but rather a difference in the position of the tongue root (lax vs. tense, or in Dutch: gedekt and open, covered and open).

Which variety occurs in a word is shown pretty systematically in Dutch spelling, using the spelling rule a described below.

In addition there is a neutral vowel that occurs in almost all unstressed syllables, the schwa /ə/ as is does more or less in English as well. It is spelled with an 'e', so that this letter has three meanings: the above two in stressed syllables, the schwa in unstressed ones.

The spelling rule
The vowels oe and eu are single, but as we saw above five vowels occur in open/covered pairs: a, e, i, o, u. There is a systematic way in the spelling to indicate which of the two varieties is intended.
 * An open syllable ending in a vowel has the 'long' open variety,
 * A closed syllable ending in one or more consonants has the 'short' covered variety..

 * Example:

If a conflict arises, either the vowel or the consonant is doubled:

 * zaak - zaken both have /a/ (business - businesses)
 * zak - zakken both have /ɑ/ (bag- bags)

Notice how the formation of the plural necessitates a good mastery of this principle. The vowels oe and eu do not exhibit the dual quality of the other vowels.

The case of the letter i is a bit special. There has been a double ii in the past but to avoid confusion with a hand-written u it was replaced by ij. Afterwards the long /i:/ sound it represented became a diphthong /ɛɪ̯/ (although many dialects retain /i/). To write the /i/ sound Dutch mostly uses -ie.

The covered version as in rit corresponds more to the English sound in will or rid, than to the German sound in mit or Kind.

As said above, the distinction 'short'-'long' has little to do with pure length, because the change from open to closed is much more important. There is an exception. In front of -r the long vowel may indeed just be the same vowel held a bit longer:

In front of -r there are a few other oddities:

The u
Notice the value of the open letter 'u' in Dutch. As in French it denotes the /y/ sound. Thus, in German it corresponds to ü.

Open variety It is relatively rare in Dutch because most words that used to have it have shifted it to the diphthong ui. It occurs mostly at the end of words like u, nu or in front of a w or r: ruw, stuur.

 * Trick: whistle a high note; freeze your lips, tongue and sing instead of blowing. Your tongue should be right behind your front teeth and your lips strongly rounded as gripping a small straw.

Closed variety

 * North Carolinians have no problem with this sound. They use it all the time in words like but, buddy, Jesus etc. It is a bit farther back in the mouth than in most American speech.

The oe
This combination represents the [u] sound in German Mut or Spanish tu. Most languages use 'u' as German and Latin. (French uses 'ou', English often used 'oo', although it does have words like shoe). The Dutch /u/ sound is strongly rounded and dark with the tongue pretty far retracted back in the mouth. American 'oo' sounds tend to be intermediary between /u/ and /y/ and that is a problem. Compare:

The eu
This combination represents another difficult vowel for Anglophones. In German it is written as ö as in Möwe. In IPA as [ø].

Before "r" vowels have a tendency to be modified:

Diphthongs

 * ei and ij are both /ɛɪ̯/

 * au and ou are both /au/ as in English now

 * ui is /ʌy/ needs to be learned by ear, it is a bit like in French l'oeil.

 * aai is /aɪ̯/

 * ooi is /oɪ̯/

 * ieu is /iu/ or /iy/

 * eeu is /eu/

 * uw is /yu/

Diphthongs like /ɔɪ̯/ (as in English toy) or /ɑɪ̯/ (as in English my) are not used in the standard language. In various dialects they do occur and producing them is often frowned upon. They are considered 'lower class' in many circles.

In unstressed syllables like the suffix -lijk the ij represents a schwa.

Medeklinkers
Most consonants in Dutch are pronounced more or less the same way as in English but there are a number of notable exceptions. First of all a number of phonemes that English has are simply missing in Dutch. Phonemes are sounds that suffice in marking one word as different from the other.

Missing phonemes

 * /θ/ : th as in thing.
 * /ð/ : th as in that.
 * /g/ : g as in good.

Please avoid these sounds when speaking Dutch.

Even /ʃ/ : sh as in ship is not really a native Dutch sound, but it occurs in quite a few loans from various sources (Frisian, English, German, French) and as most Dutch people learn English these days they are quite familiar with it. The same thing goes for /ʒ/ as in garage and their affricate versions as in /ʧ/ in church or /ʤ/ George. None of them are native to Dutch.

The g, ch and sch problem
The spelling sch- can be rather confusing for people familiar with some German. In German it is used to write the /ʃ/ sound, where English uses sh-. In Dutch the sch- combination also occurs quite frequently but is pronounced rather differently. In most cases it presents a combination of s+ch where the latter is the voiceless velar fricative /x/ as heard in German Bach or Scottish loch.

 * schip : /sxɪp/

In older versions of the orthography (prior to 1947) the combination -sch represented a simple /s/ sound in final position. The guttural ch at the end had gone mute. (Originally it represented a k- sound as it still does in some dialects and in Frisian). The final -s ch spelling is still used for one rather common ending: -is ch and also in numerous geographical names as they have never been altered in spelling:

 * chaotis ch : /xa'oːtis}}/ (not: xa'oːtiʃ/
 * 's-Hertogenbos ch : /sɛrtoːɣən'bɔs/, (not: /ʃɛr'toːɣənboʃ/ )

In principle Dutch has both a voiceless and a voiced velar fricative and the letter 'g' represents the voiced one and the combination 'ch' the voiceless one. However, the number of words where this creates a phonemic distinction is very small:

 * logen /ˈloːɣən}}/ contrasts with:  loochen  /ˈloːxən/

It depends on the region whether this distinction is actually made in the spoken language. Around Amsterdam it would not be, further south the phoneme 'g' is often pronounced as a voiced palatal fricative, so that the difference becomes more pronounced.

Worldwide, the voiced /ɣ/ sound is pretty rare. It only occurs in a few languages like Arabic and Gaelic. As many native speakers do not use it either, it is recommended not to bother about it and use the voiceless /x/ for both, unless your mother tongue happens to have the difference.

The Dutch "r"
Another, similar, problem for English-speaking learners is the Dutch "r". Essentially there are two, both of which were historically trilled.

Alveolar
The first, alveolar /r/, is the "rolling" trilled "r" also used in Spanish, produced with the tip of the tongue against the alveolar ridge. This sound was considered standard only a few decades ago and is still used by quite a few speakers. That includes the author of this book, who grew up at the southern edge of the Randstad, the Drechtsteden region, as well as many people outside the Randstad, including Flanders.

Uvular
However, particularly in the Randstad, the rolling alveolar /r/ is gradually replaced by a voiced velar or uvular trill [ʁ], which is also used in many dialects of German; it is also similar to the French "r", but is voiced and articulated somewhat further forward (it is less "throaty"). Both /r/ and /ʁ/ sounds are often not trilled when spoken by native speakers; the alveolar [r] is more often a light tap, while the uvular /ʁ/ can turn into a fricative or approximant. This also presents a considerable challenge for those unaccustomed to the sound when they are confronted with words like groot ("big"). The first two sounds tend to blend to one lengthy velar/uvular /xoːt/ or /ɣoːt/, which may cause confusion with words like rood (red) and goot (gutter).

Approximant
A third type of r currently making inroads into Dutch is Gooise R (/ɹ/), named after the Gooi area in the Netherlands, where Dutch television is produced (Hilversum) and this speech feature is popularly thought to have originated. This concerns an approximant sound, not unlike American /ɹ/ in words such as bar, without trilling or friction.

Voiceless consonants

 * p represents /p/, but unlike in English it is never aspirated.
 * poot /poːt/, kaap /kaːp/
 * f represents /f/ as in English
 * fuut /fyt/, schaaf /sxaːf/

 * t represents /t/ a true dental. Unlike UK-English it is not aspirated and unlike US-English it does not become a /ɾ/ in the middle of a word.
 * th is retained in the spelling in some words, but it simply represents /t/
 * toe /tu/, beter /ˈbeːtər/
 * s represents /s/
 * samen: /ˈsaːmən/
 * in few cases it can be a /z/ sound but much less frequently so than in German:
 * organisatie: /ɔrɣaːniˈzaːtsi/

The latter word also contains an exception on the rule that t represents /t/. In the ending -tie (corresponding to -tion) it is pronounced as a quick /ʦ/ combination, as in Russian "ц".

 * k represents /k/. again it is never aspirated as often happens in English or German.
 * kop /kɔp/, kraak /kraːk/

In contrast to English it is not silent in combinations like kn-: knie' /kni/

 * ch represents /x/ as discussed above, except in recent English loans. This phoneme is quite common.
 * schraag /sxraːx/, schichtig /ˈsxɪxtəx/

Devoicing and assimilation
As in German, but unlike English all consonants at the ends of words are devoiced (..at the ents off worts are devoist...). You may hear that phenomenon when people speak English with a strong Dutch accent.
 * zaad: /zat/

Assimilation with the previous word often devoices the consonant in initial position as well:
 * het zaad: /tsaːt/

The neutral article het is often reduced to a prefixed t-sound in the spoken language and occasionally rendered as such in the written language as: 't. Het zaad -> 't zaad.

Notice however that both the /z/ and the /d/ reappear in the plural:

 * de zaden: /də ˈzaːdən/

Contrary to d, the letters v and z are not written in the final position in such cases:

 * de vaas - de vazen: /də vas - də ˈvazən/
 * de graaf - de graven /də ɣraf - də ˈɣravən/

Voiced consonants
Apart from the devoicing effects Dutch has the following voiced consonants:

 * b represents /b/ as in English
 * baas /bas/
 * v represents /v/ as in English, although its voicing is less emphatic
 * bevel /bəˈvɛɫ/
 * d represents /d/ as in English
 * dader /ˈdadər/
 * z represents /z/ as in English
 * ziezo! /ziˈzoː/
 * g represents /ɣ/ not /g/ as in English (see above)
 * gegraven /ɣəˈɣraːvən/, gracht /ɣrɑxt/

Around Amsterdam the tendency to devoice is so strong that /v/ /ɣ/ and /z/ are seldom heard in any position. People use /f/, /x/ and /s/ instead.

Liquids, nasals, clusters

 * m represents /m/ as in English
 * mooi [moːi]
 * w represents /ʋ/, it is a labiodental approximant, not a bilabial one. Bring your upper teeth close to your lower lip and produce sound without breath. Put otherwise: produce a v-sound without breath. Speakers from e.g. Surinam often do use the bilabial version.
 * water [ˈʋaːtər]

Thus, in the Netherlands f, v and w are all pronounced with the upper teeth resting on the lower lips but there is a distinction in voicing and in aspiration (blowing)

In erwt /ɛrt/ (pea) the w is silent for most speakers, but in initial wr- (wraak /vraːk/ or /ʋraːk/) w tends to sound more like /v/.

Although the pronunciation of "w" varies, it is not silent as in English. For the combination kn- the same holds: the 'k' is clearly pronounced:

 * n represents /n/ as in English
 * nonnetje /ˈnɔnətjə/ (/ˈnɔnəcə/)

Many plurals (including the plural forms of the verb) have an ending -en. For many speakers this is pronounced as /-ə/ and the final n is dropped, but this is not true for all speakers. It depends strongly on the region of the speech area you are in. Around Amsterdam it is certainly /-ə/, but in Groningen or in West-Flanders it is a syllabic /-n/ instead. It also depends on how well people are trying to articulate or on the next word. If the latter starts with a vowel the -n is more likely to be pronounced.

 * ng /ŋ/ as in English sing, never /ŋg/ as in finger (the latter uses a /g/ that Dutch does not have). It does not occur in initial position, much like in English.
 * vinger /vɪŋər/

Even in loans the /ŋg/ tends to be avoided: mango : [ˈmɑnɣo] or [ˈmɑŋɣo]

 * nk /ŋk/ as in English sink (This involves a /k/ sound that Dutch does have)

 * j represents a /j/ sound, which in English usually written as y. The English j as in Jack is virtually unknown.

 * jacht: /jɑxt/, borrowed into English as: yacht.

In combination with i it forms a diphthong: ij. Although this is a two letter combination, both letters get capitalized at the beginning of a sentence: ijs -> IJs (ice). /ɛis/. The suffix -je that forms the rather ubiquitous diminutives tends to palatellize the previous consonants or even fuse to a palatal stop all together in rapid speech.
 * blaadje /ˈblaːtjə/ (/ˈblacə/

 * y is not a native Dutch letter but it occurs in loans where it is pronounced /i/ or /j/.

 * l represents an /l/ that is neither velarized (dark) as most English l's are, nor is it the slender variety as in German, French (or Irish). It is neutral and in between.
 * lila /ˈlilaː/

 * r can represent a variety of sounds. A rolled 'r' /r/ was more or less the norm, but is heard less and less. A variety of uvular forms is taking its place. Retroflex ones (as in US English) sound distinctly foreign.

 * h represents /ɦ/ a voiced version of the h-sound commonly heard in English and German. It only occurs in initial position of a syllable.
 * behang /bəˈɦɑŋ/, herfst /ɦɛrfst/

 * the glottal stop ` is not rendered in the ortography, unless by a hyphen, e.g. in na-apen /ˈnaʔapən/.

It is much less used than in German, e.g. theater: /teˈjatər/ rather than /teˈʔatər/.

Clusters of consonants are common in Dutch although perhaps less so than in language like Russian. Usually speakers will pronounce all the consonants in the cluster, but if clusters are consecutive, e.g. in compound words, some elision may occur. E.g. in the compound vaststellen typically only one 'st' is actually pronounced. Clusters can occur both initially and finally in a syllable:

 * staal
 * feest
 * spek
 * wesp

Common initial clusters: bl-, br-, chl- chr-, dr-, dw-, fl-, fn-, fr-, gl-, gn-, gr-, kl-, kn-, kr-, kw-, pl-, pr-, sch-, schr-, sf-, sj-, sk-, sl-, sm-, sn-, sp-, spl-, spr-, tr-, tw-, vl-, vr-, wr-, zw-

Syllable Stress
Dutch is -like English and German but unlike French- a typical stress language. One syllable tends to get all the attention. It is at the same time loud, long and high in pitch and it never has a schwa ə. Instead it has a full vowel or a diphthong. Unstressed syllables tend to be short, low, soft and usually have a schwa, although there are exceptions.

Stress is not represented in the spelling unless ambiguity can arise for native speakers. In that case acutes can be added, otherwise orthographic rules demand that they be omitted. For non-native speakers this is a bit of a problem, but often an educated guess can be made which syllable is the stressed one.

Because the schwa is written as a e in the orthography it is often quite clear where the stress falls in a word:

 * verlaten : /vər' la tən/ has only one non-schwa syllable la and sure enough that is where the stress goes.

Unfortunately for the non-native speaker the letter e is also used for other purposes.

 * verleden : /vər' le dən/

The middle -e represent a full /e/ sound (as the ai in bait), but that is only clear for a native speaker. But with a bit of knowledge of grammar it will be clear that /led/ is the root of a verb (lijden actually) and that ver- is a prefix and -en the suffix. In general, the root of a verb (or noun) will get the stress in Dutch.

Of course, there are complicated cases:

 * december : /d e 's ɛ mb ə r/

It's a word which has three e's, each pronounced differently. The first syllable has a full [e] even though it is not stressed.

Of course there are cases where stress is not clear even for native speakers; a good example are the separable and non-separable verbs, e.g. the verb doorlopen can be either dóórlopen or doorlópen with a different conjugation and different meaning.

In such cases Dutch spelling does allow stress patterns to be written with an acute, but only if otherwise confusion might arise.

Some words and names can have rather surprising stress patterns:

 * Veluwe is Véluwe /' ve lyə/ for example, not Velúwe and Enschede is Énschedé, not Enschéde. In names ending in -dam the stress is usually on that syllable: Amsterdám, Rotterdám, unless a contrast is made between them "niet Ámsterdam maar Rótterdam"

Capitalization
The rules for capitalization in Dutch are similar to those in English. Capitalization occurs at the beginning of a sentence. Eigennamen (proper names, e.g., of persons, organisations, countries etc.) are capitalized, but soortnamen (generic names) are not.

As mentioned above, when a word beginning with ij has to be capitalized, both letters become capitals, e.g. IJsselmeer.

Exercise
<< Contents Page

title: Dutch/Alfabet


text:
XML - Managing Data Exchange/A single entity

Introduction
In this chapter, we start to practice working with XML using XML documents, schemas, and stylesheets. An XML document organizes data and information in a structured, hierarchical format. An XML schema provides standards and rules for the structure of a given XML document. An XML schema also enables data transfer. An XSL (XML stylesheet) allows unique presentations of the material found within an XML document.

In the first chapter, Introduction to XML, you learned what XML is, why it is useful, and how it is used. So, now you want to create your very own XML documents. In this chapter, we will show you the basic components used to create an XML document. This chapter is the foundation for all subsequent chapters--it is a little lengthy, but don't be intimidated. We will take you through the fundamentals of XML documents.

This chapter is divided into three parts:
 * XML Document
 * XML Schema
 * XML Stylesheets (XSL)

As you learned in the previous chapter, the XML Schema and Stylesheet are essentially specialized XML Documents. Within each of these three parts we will examine the layout and components required to create the document. There are links at the end of the XML document, schema, and stylesheet sections that show you how to create the documents using an XML editor. At the bottom of the page there is a link to Exercises for this chapter and a link to the Answers.

The first thing you will need before starting to create XML documents is a problem--something you want to solve by using XML to store and share data or information. You need some entity you can collect information about and then access in a variety of formats. So, we created one for you.

To develop an XML document and schema, start with a data model depicting the reality of the actual data that is exchanged. Once a high fidelity model has been created, the data model can be readily converted to an XML document and schema. In this chapter, we start with a very simple situation and in successive chapters extend the complexity to teach you more features of XML.

Our starting point is a single entity, CITY, which is shown in the following figure. While our focus is on this single entity, to map CITY to an XML schema, we need to have an entity that contains CITY. In this case, we have created TOURGUIDE. Think of a TOURGUIDE as containing many cities, and in this case TOURGUIDE has no attributes nor an identifier. It is just a container for data about cities.

Exhibit 1: Data model - Tourguide

XML document
An XML document is a file containing XML code and syntax. XML documents have an .xml file extension.

We will examine the features & components of the XML document.

 * Prologue (XML Declaration)
 * Elements
 * Attributes
 * Rules to follow
 * Well-formed & Valid XML documents

Below is a sample XML document using our TourGuide model. We will refer to it as we describe the parts of an XML document.

Exhibit 2: XML document for city entity

Prologue (XML declaration)
The XML document starts off with the prologue. The prologue informs both a reader and the computer of certain specifications that make the document XML compliant. The first line is the XML declaration (and the only line in this basic XML document).

Exhibit 3: XML document - prologue

xml  =   this is an XML document

version="1.0"  =   the XML version (XML 1.0 is the W3C-recommended version)

encoding="UTF-8"  =   the character encoding used in the document - UTF 8 corresponds to 8-bit encoded Unicode characters (i.e. the standard way to encode international documents) - Unicode provides a unique number for every character.

Another potential attribute of the XML declaration:

standalone="yes"  =   the dependency of the document ('yes' indicates that the document does not require another document to complete content)

Elements
The majority of what you see in the XML document consists of XML elements. Elements are identified by their tags that open with < or  or />. The start tag looks like this:, with a left angle bracket (<) followed by the element type name, optional attributes, and finally a right angle bracket (>). The end tag looks like this:, similar to the start tag, but with a slash (/) between the left angle bracket and the element type name, and no attributes.

When there's nothing between a start tag and an end tag, XML allows you to combine them into an empty element tag, which can include everything a start tag can: . This one tag must be closed with a slash and right angle bracket (/>), so that it can be distinguished from a start tag.

The XML document is designed around a major theme, an umbrella concept covering all other items and subjects; this theme is analyzed to determine its component parts, creating categories and subcategories. The major theme and its component parts are described by elements. In our sample XML document, 'tourGuide' is the major theme; 'city' is a category; 'population' is a subcategory of 'city'; and the hierarchy may be carried even further: 'males' and 'females' could be subcategories of 'population'. Elements follow several rules of syntax that will be described in the Rules to Follow section.

We left out the attributes within the  start tag — that part will be explained in the XML Schema section.

Exhibit 4: Elements of the city entity XML document

Element hierarchy

 * root element -   This is the XML document's major theme element. Every document must have exactly one and only one root element. All other elements are contained within this one root element. The root element follows the XML declaration. In our example,  is the root element.

 * parent element -   This is any element that contains other elements, the child elements. In our example, is a parent element.

 * child element -   This is any element that is contained within another element, the parent element. In our example, is a child element of.

 * sibling element -   These are elements that share the same parent element. In our example, , ,, , , , , , , and are all sibling elements.

Attributes
Attributes aid in modifying the content of a given element by providing additional or required information. They are contained within the element's opening tag. In our sample XML document code we could have taken advantage of attributes to specify the unit of measure used to determine the area and the elevation (it could be feet, yards, meters, kilometers, etc.); in this case, we could have called the attribute 'measureUnit' and defined it within the opening tag of 'area' and 'elevation'.

Cayo

Selangor

The above attribute example can also be written as:

1. using child elements

2. using an empty element

Attributes can be used to:

 * provide more information that is not defined in the data
 * define a characteristic of the element (size, color, style)
 * ensure the inclusion of information about an element in all instances

Attributes can, however, be a bit more difficult to manipulate and they have some constraints. Consider using a child element if you need more freedom.

Rules to follow
These rules are designed to aid the computer reading your XML document.

 * The first line of an XML document must be the XML declaration (the prologue).

 * The main theme of the XML document is established in the root element and all other elements must be contained within the opening and closing tags of this root element.

(e.g. data stuff ).
 * Every element must have an opening tag and a closing tag - no exceptions

=> the parent element's opening and closing tags must contain all of its child elements' tags; in this way, you close first the tag that was opened last:  data  <subChildElementA>data</subChildElementA> <subChildElementB>data</subChildElementB> </childElement2> <childElement3>data</childElement3> </parentElement>
 * Tags must be nested in a particular order

 * Attribute values should have quotation marks around them and no spaces.

 * Empty tags or empty elements must have a space and a slash (/) at the end of the tag.

 * Comments in the XML language begin with "".

XML Element Naming Convention
Any name can be used but the idea is to make names meaningful to those who might read the document.

 * XML elements may only start with either a letter or an underscore character.

 * The name must not start with the string "xml" which is reserved for the XML specification.

 * The name may not contain spaces.

 * The ":" should not be used in element names because it is reserved to be used for namespaces (This will be covered in more detail in a later chapter).

 * The name may contain a mixture of letters, numbers, or other characters.

XML documents often have a corresponding database. The database will contain fields which correspond to elements in the XML document. A good practice is to use the naming rules of your database for the elements in the XML documents.

Simple Internal DTD
Every element that will be used MUST be included in the DTD. Don’t forget to include the root element, even though you have already specified it at the beginning of the DTD. You must specify it again, in an <!ELEMENT> tag. <!ELEMENT cdCollection (cd)> The root element, <cdCollection>, contains all the other elements of the document, but only one direct child element: <cd>. Therefore, you need to specify the child element (only direct child elements need to be specified) in the parentheses. <!ELEMENT cd (title, artist, year)> With this line, we define the <cd> element. Note that this element contains the child elements, , and. These are spelled out in a particular order. This order must be followed when creating the XML document. If you change the order of the elements (with this particular DTD), the document won’t validate. <!ELEMENT title (#PCDATA)> The remaining three tags,, , and don’t actually contain other tags. They do however contain some text that needs to be parsed. You may remember from an earlier lecture that this data is called Parsed Character Data, or #PCDATA. Therefore, #PCDATA is specified in the parentheses. So this simple DTD outlines exactly what you see here in the XML file. Nothing can be added or taken away, as long as we stick to this DTD. The only thing you can change is the #PCDATA text part between the tags.

Adding complexity
There may be times when you will want to put more than just character data, or more than just child elements into a particular element. This is referred to as mixed content. For example, let’s say you want to be able to put character data OR a child element, such as the <b> tag into a element:

<!ELEMENT description (#PCDATA | b | i )*>

This particular arrangement allows us to use PCDATA, the <b> tag, or the <i> tag all at once. One particular caveat though, is that if you are going to mix PCDATA and other elements, the grouping must be followed by the asterisk (*) suffix. This declaration allows us to now add the following to the XML document (after defining the individual elements of course)

With attributes this is done a little differently than with elements. Please see following example:

In order for this to validate, it must be specified in the DTD. Attribute content models are specified with:

<!ATTLIST element_name attribute_name attribute_type default_value>

Let’s use this to validate our CD example:

<!ATTLIST cd remaster_date CDATA #IMPLIED>

Choices
<ATTLIST person gender (male|female) “male”>

Grouping Attributes for an Element
If a particular element is to have many different attributes, group them together like so:

<!ATTLIST car horn CDATA #REQUIRED seats CDATA #REQUIRED steeringwheel CDATA #REQUIRED price CDATA #IMPLIED>

Adding STATIC validation, for items that must have a certain value
<!ATTLIST classList  classNumber CDATA #IMPLIED building (UWINNIPEG_DCE|UWINNIPEG_MAIN) "UWINNIPEG_MAIN" originalDeveloper CDATA #FIXED "Khal Shariff">

Suffixes
So what happens with our last example with the CD collection, when we want to add more CDs? With the current DTD, we cannot add any more CDs without getting an error. Try it and see. When you specify a child element (or elements) the way we did, only one of each child element can be used. Not very suitable for a CD collection is it? We can use something called suffixes to add functionality to the <!ELEMENT> tag. Suffixes are added to the end of the specified child element(s). There are 3 main suffixes that can be used:

 * ( No suffix ): Only 1 child can be used.
 * ( + ): One or more elements can be used.
 * ( * ): Zero or more elements can be used.
 * ( ? ): Zero or one element may be used.

Validating for multiple children with a DTD
So in the case of our CD collection XML file, we can add more CDs to the list by adding a + suffix: <!ELEMENT cd_collection(cd+)>

Using more internal formatting tags
Bold tags, B's for example are also defined in the DTD as elements, that are optional like thus:

<ELEMENT notes (#PCDATA | b | i)*> <!ELEMENT b (#PCDATA)*> <!ELEMENT i (#PCDATA)*> ]> _______________ <classList classNumber="303" building="UWINNIPEG_DCE" originalDeveloper="Khal Shariff"> <firstName>Kenneth </firstName> <lastName>Branaugh </lastName> <studentNumber> </studentNumber> Excellent , Kenneth is doing well. etc

{| width="100%" border="1"
 * - style="horizontal-align:wraptext;"
 * style="background-color:lightyellow" |

Case Study on BMEcat
One of the first major national projects for the use of XML as a B2B exchange format was initiated by the federal association for material management, purchasing and logistics (BME) in cooperation with leading German companies, e.g. Bayer, BMW, SAP and Siemens. They all created a standard for the exchange of product catalogues. This project was named [http://www.bmecat.org/English/index.asp? BMEcat]. The result of this initiative is a DTD collection for the description of product catalogues and related transactions (new catalogue, updating of product data and updating of prices).

Companies operating in the electronic commerce (suppliers, purchasing companies and market places) exchange increasingly large amounts of data. They quickly reach their limits here by the variety of data exchange formats. The BMEcat solution creates a basis for a straightforward transfer of catalogue data from various data formats. This lays the foundation to bringing forward the goods traffic through the Internet in Germany. The use of the BMEcat reduces the costs for all parties as standard interfaces can be used.

The XML-based standard BMEcat was successfully implemented in many projects. Nowadays a variety of companies applies BMEcat and use it for the exchange of their product catalogs in this established standard.

A BMEcat catalogue (Version 1.2) consists of the following main elements:

CATALOG This element contains the essential information of a shopping catalog, e.g. language version and validity. BMEcat expects exactly one language per catalog.

SUPPLIER This element includes identification and address of the catalog suppliers. BMEcat expects exactly one supplier per catalog.

BUYER This element contains the name and address of the catalogue recipient. BMEcat expects no more than one recipient per catalog.

AGREEMENT This element contains one or more framework agreement IDs associated with the appropriate validity period. BMEcat expects all prices of a catalogue belonging to the contract mentioned above.

CLASSIFICATION SYSTEM This element allows the full transfer of one or more classification systems, including feature definitions and key words.

CATALOG GROUP SYSTEM This element originates from version 1.0. It is mainly used for the transfer of tree-structures which facilitate the navigation of a user in the target system (Browser).

ARTICLE (since 2005 PRODUCT) This element represents a product. It contains a set of standard attributes.

ARTICLE PRICE (since 2005 PRODUCT PRICE) This element represents a price. The support of different pricing models is very powerful in comparison with other exchange formats. Season prices, country prices, different currencies and different validity periods, etc. will be supported.

ARTICLE FEATURE (since 2005 PRODUCT FEATURE) This element allows the transfer of characteristic values. You can either record predefined group characteristics or individual product characteristics.

VARIANT This element allows listing of product variants, without having to duplicate them. However, the variations of BMEcat only apply to individual changes in value, leading to a change of Article ID. Otherwise there can’t exist any dependences on other attributes (especially at prices).

MIME This element includes any number of additional documents such as product images, data sheets, or websites.

ARTICLE REFERENCE (since 2005 REFERENCE PRODUCT) This element allows cross-referencing between articles within a catalogue as well as between catalogues. These references may used restrictedly for mapping product bundles.

USER DEFINED EXTENSION This element enables transportation of data at the outside the BMEcat standards. The transmitter and receiver have to be coordinated.

You can find a typical BMEcat file here.
 * }

ONLINE Validator
GIYBF

Well-formed and valid XML
Well-formed XML -  An XML document that correctly abides by the rules of XML syntax.

Valid XML -  An XML document that adheres to the rules of an XML schema (which we will discuss shortly). To be valid an XML document must first be well-formed.

A Valid XML Document must be Well-formed. But, a Well-formed XML Document might not be valid - in other words, a well-formed XML document, that meets the criteria for XML syntax, might not meet the criteria for the XML schema, and will therefore be invalid.

For example, think of the situation where your XML document contains the following (for this schema):

<cityName>Boston</cityName> United States <adminUnit>Massachusetts</adminUnit> :  :   :

Notice that the elements do not appear in the correct sequence according to the schema (cityName, adminUnit, country). The XML document can be validated (using validation software) against its declared schema – the validation software would then catch the out of sequence error.

Using an XML Editor
Check chapter ../XML Editor/ for instructions on how to start an XML editor. Once you have followed the steps to get started you can copy the code in the sample XML document and paste it into the XML editor. Then check your results. Is the XML document well-formed? Is the XML document valid? (you will need to have copied and pasted the schema in order to validate - we will look at schemas next)

XML schema
An XML schema is an XML document. XML schemas have an .xsd file extension.

An XML schema is used to govern the structure and content of an XML document by providing a template for XML documents to follow in order to be valid. It is a guide for how to structure your XML document as well as indicating your XML document's components (elements and attributes - and their relationships). An XML editor will examine an XML document to ensure that it conforms to the specifications of the XML schema it is written against - to ensure it is valid.

XML schemas engender confidence in data transfer. With schemas, the receiver of data can feel confident that the data conforms to expectations. The sender and the receiver have a mutual understanding of what the data represent.

Because an XML schema is an XML document, you use the same language - standard XML markup syntax - with elements and attributes specific to schemas.

A schema defines:

 * the structure of the document
 * the elements
 * the attributes
 * the child elements
 * the number of child elements
 * the order of elements
 * the names and contents of all elements
 * the data type for each element

For more detailed information on XML schemas and reference lists of: Common XML Schema Primitive Data Types, Summary of XML Schema Elements, Schema Restrictions and Facets for data types, and Instance Document Attributes, click on this wikibook link => http://en.wikibooks.org/wiki/XML_Schema

Schema reference
This is the part of the XML Document that references an XML Schema:

Exhibit 5: XML document's schema reference

This is the part we left out when we described the root element in the basic XML document from the previous section. The additional attributes of the root element <tourGuide> reference the XML schema (it is the schemaLocation attribute).

xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'  -  references the W3C Schema-instance namespace

xsi:noNamespaceSchemaLocation='city.xsd'  -  references the XML schema document (city.xsd)

Schema document
Below is a sample XML schema using our TourGuide model. We will refer to it as we describe the parts of an XML schema.

Exhibit 6: XML schema document for city entity

Prolog
Remember that the XML schema is essentially an XML document and therefore must begin with the prolog, which in the case of a schema includes:

The XML declaration:
 * the XML declaration
 * the schema element declaration

The schema element declaration:

The schema element is similar to a root element - it contains all other elements in the schema.

Attributes of the schema element include:

xmlns -  XML NameSpace - the URL for the site that describes the XML elements and data types used in the schema.

You can find more about namespaces here => ../Namespace/.

xmlns:xsd -  All the elements and attributes with the 'xsd' prefix adhere to the vocabulary designated in the given namespace.

elementFormDefault -  elements from the target namespace are either required or not required to be qualified with the namespace prefix. This is mostly useful when more than one namespace is referenced. In this case, 'elementFormDefault' must be qualified, because you must indicate which namespace you are using for each element. If you are referencing only one namespace, then 'elementFormDefault' can be unqualified. Perhaps, using qualified as the default is most prudent, this way you do not accidentally forget to indicate which namespace you are referencing.

Element declarations
Define the elements in the schema.

Include:

 * the element name
 * the element data type (optional)

Basic element declaration format:

Simple type
declares elements that:

 * do NOT have Child Elements
 * do NOT have Attributes

example:

Default Value

If an element is not assigned a value then the default value is assigned.

example:

Fixed Value

An attribute that is defined as fixed must be empty or contained the specified fixed value. No other values are allowed.

example:

Complex type
declares elements that:

 * can have Child Elements
 * can have Attributes

examples:

1. The root element 'tourGuide' contains a child element 'city'. This is shown here:

Nameless complex type

Occurrence Indicators:

 * minOccurs = the minimum number of times an element can occur (here it is 1 time)
 * maxOccurs = the maximum number of times an element can occur (here it is an unlimited number of times, 'unbounded')

2. The parent element 'city' contains many child elements: 'cityName', 'adminUnit', 'country', 'population', etc. Why does this complex element set not start with the line: ? The element 'city' was already defined above within the complex element 'tourGuide' and it was given the type, 'cityDetails'. This data type, 'cityDetails', is utilized here in identifying the sequence of child elements for the parent element 'city'.

Named Complex Type - and therefore can be reused in other parts of the schema

The <xsd:sequence> tag indicates that the child elements must appear in the order, the sequence, specified here.

Compare the sample XML Schema and the sample XML Document - try to observe patterns in the code and how the XML Schema sets up the XML Document.

3. Elements that have attributes are also designated as complex type.

a. this XML Document line: would be defined in the XML Schema as: b. this XML Document line: would be defined in the XML Schema as:

Attribute declarations
Attribute declarations are used in complex type definitions. We saw some attribute declarations in the third example of the Complex Type Element.

Data type declarations
These are contained within element and attribute declarations as:  type=" " .

Common XML Schema Data Types

XML schema has a lot of built-in data types. The most common types are:

For an entire list of built-in simple data types see http://www.w3.org/TR/xmlschema-2/#built-in-datatypes

Using an XML Editor => ../XML Editor/

This link will take you to instructions on how to start an XML editor. Once you have followed the steps to get started you can copy the code in the sample XML schema document and paste it into the XML editor. Then check your results. Is the XML schema well-formed? Is the XML schema valid?

XML stylesheet (XSL)
An XML Stylesheet is an XML Document. XML Stylesheets have an .xsl file extension.

The eXtensible Stylesheet Language (XSL) provides a means to transform and format the contents of an XML document for display. Since an XML document does not contain tags a browser understands, such as HTML tags, browsers cannot present the data without a stylesheet that contains the presentation information. By separating the data and the presentation logic, XSL allows people to view the data according to their different needs and preferences.

The XSL Transformation Language (XSLT) is used to transform an XML document from one form to another, such as creating an HTML document to be viewed in a browser. An XSLT stylesheet consists of a set of formatting instructions that dictate how the contents of an XML document will be displayed in a browser, with much the same effect as Cascading Stylesheets (CSS) do for HTML. Multiple views of the same data can be created using different stylesheets. The output of a stylesheet is not restricted to a browser.

During the transformation process, XSLT analyzes the XML document and converts it into a node tree – a hierarchical representation of the entire XML document. Each node represents a piece of the XML document, such as an element, attribute or some text content. The XSL stylesheet contains predefined “templates” that contain instructions on what to do with the nodes. XSLT will use the match attribute to relate XML element nodes to the templates, and transform them into the resulting document.

Exhibit 7: XML stylesheet document for city entity

The output of the city.xsl stylesheet in Table 2-3 will look like the following:

You will notice that the stylesheet consists of HTML to inform the media tool (a web browser) of the presentation design. If you do not already know HTML this may seem a little confusing. Online resources such as the W3Schools tutorials can help with the basic understanding you will need =>(http://www.w3schools.com/html/default.asp).

Incorporated within the HTML is the XML that supplies the data, the information, contained within our XML document. The XML of the stylesheet indicates what information will be displayed and how. So, the HTML constructs a display and the XML plugs in values within that display. XSL is the tool that transforms the information into presentational form, but at the same time keeps the meaning of the data.

Prolog

 * the XML declaration;
 * the stylesheet declaration;
 * the namespace declaration;
 * the output document format.

The XML declaration

The stylesheet & namespace declarations
 * identifies the document as an XSL style sheet;
 * identifies the version number;
 * refers to the W3C XSL namespace - the URL for the site that describes the XML elements and data types used in the schema. You can find more about namespaces here => ../Namespace/.  Every time the xsl: prefix is used it references the given namespace.

The output document format This element designates the format of the output document and must be a child element of

Templates
The <xsl:template> element is used to create templates that describe how to display elements and their content. Above, in the XSL introduction, we mentioned that XSL breaks up the XML document into nodes and works on individual nodes. This is done with templates. Each template within an XSL describes a single node. To identify which node a given template is describing, use the 'match' attribute. The value given to the 'match' attribute is called a pattern. Remember:  (node tree – a hierarchical representation of the entire XML document.  Each node represents a piece of the XML document, such as an element, attribute or some text content). Wherever there is branching in the node tree, there is a node. <xsl:template> defines the start of a template and contains rules to apply when a specified node is matched.

the match attribute

<xsl:template match="/">

This template match attribute associates the XML document root (/), the whole branch of the XML source document, with the HTML document root. Contained within this template element is the typical HTML markup found at the beginning of any HTML document. This HTML is written to the output. The XSL looks for the root match and then outputs the HTML, which the browser understands.

<xsl:template match="tourGuide"> This template match attribute associates the element 'tourGuide' with the display rules described within this element.

Elements
Elements specific to XSL:

For more XSL elements => http://www.w3schools.com/xsl/xsl_w3celementref.asp.

PHP Methods of XML Dom Validation
Using the DOM DocumentObjectModel to validate XML and with a DTD DocumentTypeDeclaration and the PHP language on a server and more http://wiki.cc/php/Dom_validation

Browser Methods
Place this line of code in your .xml document after the XML declaration (prologue).

PHP Methods of XSLT Transformation
This one is good for PHP5 and wampserver (latest). Please ensure that *xsl* is NOT commented out in the php.ini file.

Example 1, Using within PHP itself (use phpInfo function to check XSLT extension; enable if needed) This example might produce XHTML. Please note it could produce anything defined by the XSL. Example 2:

XML Colors
For use in your stylesheet: these colors can be used for both background and font

http://www.w3schools.com/html/html_colors.asp

http://www.w3schools.com/html/html_colorsfull.asp

http://www.w3schools.com/html/html_colornames.asp

--- Using an XML Editor => ../XML Editor/

This link will take you to instructions on how to start an XML editor. Once you have followed the steps to get started you can copy the code in the sample XML stylesheet document and paste it into the XML editor. Then check your results. Is the XML stylesheet well-formed? ---

/Definitions/
XML SGML Dan Connelly RSS XML Declaration parent child sibling element attribute

*Well-formed XML

PCDATA

/Exercises/
Exercise 1.

a)Using "tourguide" above as a good example, create an XML document whose root is "classlist" . This CLASSLIST is created from a starting point of single entity, STUDENT. Any number of students contain elements: firstname, lastname, emailaddress.

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


text:
Talk:General Biology/Getting Started/Introduction

If someone knows how to make the text flow around the pictures, please help me out. Thanks !! --Karl Wick

 * no problem Gentgeen 00:51, 9 Jan 2004 (UTC)

I added an example to illustrate the process of scientific inverstigation.

Characteristics of Life
Shouldn't the definition include something about adaptation through natural section? Italienmoose (talk) 11:56, 5 June 2010 (UTC)


text:
Talk:Puzzles/How do you ... ?/Crossing the Bridge

Wait .. that would not work, the person would have an experienced downward force while pushing each apple up into the air that would, depending on how long the upward accelaration took, be greater than his stationary weight. That is, to push the apples up into the air the apple is still pushing the person down onto the bridge. --Karl Wick

Can't he take them over one at a time? -- Darac


text:
User talk:Gentgeen

If you erase someone else's comments to make your own, I will revert without reading what you wrote.

Thanks Genteen !! --Karl Wick User talk:Karl Wick re: General Biology/Getting Started/Introduction

A related question: do you know how to code it so that if I have a floating div-style box I can but a border around the inside of it so that the text in the box does not go all the way up to the edge ? I would like the color of the box to extend another bit beyond where the text ends. I did a trial over at the sandbox but was not able to make it work. Thanks !! --Karl Wick

Thanks
Hi Gentgeen,

Thanks for featuring my Tarbes Salad at wikibooks! You make my mother proud.

Leland

thanks
Thanks for all your work on the cookbook. You have improved it greatly. - liblamb 17:01, 12 Jul 2004 (UTC)
 * Aww, shucks. Gentgeen

Administrator
Hi Gentgeen. As Tuf-Kat is away, I have made you a sysop following the vote at Requests for adminship. Please make sure you read the relevant policies linked to from Administrators before using your sysop powers here, and be careful where those policies differ from those that you are more used to on the English Wikipedia. I'm surprised you have 2000 users and only one bureaucrat. I would like to advise you to nominate someone for the role, especially since your current one is away. Good luck with your adminship. Angela (steward) 00:20, 9 Aug 2004 (UTC)

Hi
Thanks for the welcome, Gentgeen. As you might have guessed, I'm an import from wikipedia. I finally got curious about all those people saying "Take it to wikibooks" and checked it out. Mostly I plan to supplement wikipedia articles with links (Recipes for food dishes seem the most appropriate). The Steve 13:10, 26 Sep 2004 (UTC)

Wikipedia recipe
I found a recipe for Garlic parmesan pasta all by it's lonesome at Wikipedia. I was wondering if there was a procedure for moving such recipes or if I should just copy and paste it over to Wikibooks. The recipe is a dead end page with no links anywhere else in Wikipedia. liblamb 21:46, 30 Sep 2004 (UTC)
 * Found one for giblet soup too. liblamb
 * Copy and past successful. Find them here and here.  I havn't suggested the recipes be deleted in Wikipedia yet. liblamb 20:53, 7 Oct 2004 (UTC)

From a fan
I was just thinking that those Chinese IP addresses needed a range block, and there you are, already there, and done it. Kudos, to you! :) Dysprosia 08:55, 10 Oct 2004 (UTC)

Thanks
I'm using your stylesheet(hope you don't mind), so I just wanted to say thanks. --IBB 15:36, 16 Oct 2004 (UTC)

Wikipedia dumps
I was wondering what we do with "Wikipedia dumps," which is my term for when Wikipedians dump an article that doesn't fit in Wikipedia into Wikibooks without taking into consideration the way Wikibooks works. Has there been discussion about this before that I can read? This came up because of this page. The pages now in Wikibooks link only to themselves and the likelyhood of someone finding them is very small by a search. Of course I can create links for it in the Misc. categpru but I was wondering if anything can be added to the conversation at Wikipedia to better inform people on best Wikibooks practice, if there is better practice. Thanks for the help. liblamb 18:33, 19 Oct 2004 (UTC)

 * From Panic2k4 talk page

no, most of the wikipedia content on wikibooks has been properly credited to the original authors. When it hasn't, the problem is either fixed or the page is deleted. Gentgeen 22:21, 22 Nov 2004 (UTC)

 * FYI, I had tried to start discussions about this at Staff_lounge and w:Wikipedia:Village pump (policy) before I saw the thread here. -- Paddu 11:03, 23 Nov 2004 (UTC)

Cookbook administrator abuse
Hi Gentgeen I would like to ask you, how was Cookbook:Human any less valid an article than Cookbook:Chicken? Please undelete it. This is not the first time you have taken actions I do not believe are justifiable by policy, and if you have no explanation for this based on policy, it won't be the first time for that, either.

--node

'It is time we defined ourselves': copyright and other concerns
Hello Gentgreen. I am concerned that the material downloaded today (27.10.2004) by Attention-tunnel, originally from the works of Di Murray and Andrew Walker and the late Marc Segar, is not released under the GFDL, or a Creative Commons, and therefore cannot/should not be used on Wikibooks. The other concern I have is that the material from Autism and Computing is a 'data dump' and does not fulfill the criteria for a Wikibook, or for that matter a Wikiversity. The third concern of mine is that this page is vulnerable to vandalism, I believe a link-spammer came. Would appreciate if you checked up here. Also, what is the status of the Aspergia Mythos and Ethos in relation to Wikibooks? Sincerely EuropracBHIT 06:40, 27 Oct 2004 (UTC).

Thanks for the welcome and the suggestions. I will add some kind of disambiguator. Danny 16:02, 7 Nov 2004 (UTC)

Thanks old timer
hey there thank you for the heads up. unfortuneately i am unable to download/upload stuff as my contributions to wikipedia are all done from my desk at work. actually thats sort of how i found wikipedia as we have restrictions on internet use and can only surf .org .gov and our intranet. fortuneatly/unfortuneately because i have a lot of time on my hands i can however make contributions. what i need is a way to import images from example nasa.gov into wikimedia or wikibooks/wikipedia whatever. also i am still learning so i need to know how to do it as well. any ideas? --Larsie 18:39, 8 Nov 2004 (UTC)

thanks for the help
wow, thanks for the offer. it would actually be etremely helpfull to the wikijunior project if we could get images of the planets from wikipedia articles into the commons. if you are willing it would be much appreciated. --Larsie 20:38, 8 Nov 2004 (UTC)

Programming:_C_-/-_-/- a copyvio?
Please check Staff_lounge too. See if that's also a copyright violation. And BTW it could be possible that the wikipedia article itself was a copyvio.

BTW, if this just increases traffic to Staff_lounge, I'd be happier :) -- Paddu 21:01, 22 Nov 2004 (UTC)

 * Oops! Sorry I missed the message you'd posted on my talk page. I'll try to compile a list of material copied from Wikipedia. But note that depending on the interest the wikibooks community has on my service I may or may not be doing any good to wikibooks, as explained in User talk:Mkn. -- Paddu 12:04, 26 Nov 2004 (UTC)

Hello, Gentgeen just posted a reply to your questions/moderation you should also check a duplication of the problem in your talk page referring wikipedia dumps that was not addressed and it seems that if your interpretation of the GFDL is right wikibooks will have lots of trouble correcting this...--Panic 22:19, 22 Nov 2004 (UTC)

re: Links
Thanks. I hope I've done those correctly. If not, I wouldn't mind help. I'm also not sure this submission is well-structured for a Wikibooks contribution. It seemed to model one that was already here (Nasrudin) but I could also see people considering it a "Wikipedia dump". Your thoughts? Rossami 00:45, 1 Dec 2004 (UTC)

Re: my user page
oh well your objection and compromise both seem quite fair, and i would be more than willing to change it, if i could work out how to edit the damn thing. If i click on User:The bellman it takes me to w:User:The bellman and cause its a cross wiki redirect there is no "redirected from foo" at the top of w:User:The bellman. Any Ideas? The bellman 03:14, 21 Jan 2005 (UTC)
 * Ah, now you understand some of the bad things about interwiki redirects. You need to manually construct a url with &redirect=no at the end in the browser address bar, in this case http://en.wikibooks.org/w/index.php?title=User:The_bellman&redirect=no . You'll also need to do it for your talk page at http://en.wikibooks.org/w/index.php?title=User_talk:The_bellman&redirect=no.
 * Gentgeen 09:37, 21 Jan 2005 (UTC)
 * Thanks mate. The bellman 10:22, 21 Jan 2005 (UTC)

hey GENTGREEN, i have question
-- hello gentgreen. i was a contributor to beating season. i understand how beating season was too controversial for wikibooks. however i would still like to contribute to the project. could i write a book about the history of violence and opression of women? like a real book, not a joke like BEATING SEASON??? -kyle
 * I replied at your talk page. Gentgeen

Please modify main page for me
Hi Gentgeen. As explained in Talk:Main_Page, I would ask you to add 3 lines to the Main Page, in order to include a teaser for the book of the month. Here is a demo of how the Main Page should look after the change: User:Andreas_Ipp/Main_Page_suggestion. I week ago (before you locked the page) I could have done the change by myself, now I depend on some administrator (which is fine with me). Thanks! --Andreas Ipp 13:04, 23 Jan 2005 (UTC)

 * I just noticed it was not locked anymore :-) ... I just made the change by myself. --Andreas Ipp 13:15, 23 Jan 2005 (UTC)

Why o why?
Why o why did I not check my Wikibook talk page sooner. All this time I've been editing on Wikipedia and I've been manually signing and time stamping my signature!! Haha, thanks Genteen. :) —Christiaan 22:35, 24 Jan 2005 (UTC)

advertising
I suggest you take another look at. --68.204.254.4 09:11, 29 Jan 2005 (UTC)

please distinguish this book
Can you fix this? Please do so, or find someone who can.

Every recipie has a link to "Catagories". Oh my. I click on that, and I see...

 * Abugida writing systems
 * Ada 2005 feature
 * Ada programming language
 * Algebra
 * Anthropology
 * Arts

That's just the letter A. While algebra may be useful for modifying a recipie, it really does not belong in a cookbook. Catagories from unrelated wiki books should not be leaking into the cookbook. I suspect that the Ada programmers have no use for Albanian recipies, but they can always just go to the cookbook if they get hungry. They don't need to be tempted by delicious Argentine recipies while trying to learn about Ada 2005.

Strange non-cookbook stuff also leaks into the "recent changes" page. I suspect I'd also get it if I used the "random module" link, which really should be "random recipie" and "random ingredient".

The only thing these wikis might reasonably share would be user accounts, and THAT is not working, at least between Wikipedia and the cookbook. Oh, the suffering. :-(

BTW, adding "Cookbook:" to all the links gets old fast. Because of this, and case-sensitivity being enabled, one is required to use the "|" to rename all links. This greatly detracts from the ease-of-use that wikis are known for. If the cookbook were more distinct, this prefix would not be needed.

I certainly do understand why things are the way they are. This does not change the simple fact that things are a great big mess. Renaming the "Categories" link isn't of much use, though I guess renaming it to the non-breaking-space character would be an improvement! Really, that link should work within the cookbook and only within the cookbook. The cookbook seriously does need a domain name for itself. Then some server-side bot can go through and rip out all the "Cookbook:" prefixes. AlbertCahalan 02:44, 31 Jan 2005 (UTC)

The Special:Specialpages stuff is unusable too. For example, I look in the New Images gallery and see nothing about the cookbook. The cookbook gets drowned out by physics and biology. Everywhere I look, wiki features are unusable, with cookbook data being crowded out by unrelated stuff. Everywhere I look, there are links that take me to some generic place outside the cookbook. Even Main Page is misleading and wrong, and the reason why every cookbook recipe has to include a link back to the main page of the cookbook. AlbertCahalan 03:17, 1 Feb 2005 (UTC)

featured recipe
Practically nobody in the USA can use this. We don't have scales or balences in our kitchens at all, never mind ones using French units.

It's OK to have meat in pounds, or by volume. Everything else must be by volume. Quantities much larger than a cup can be in those French units, because large glass measuring cups are marked both ways. For everything else, we need traditional units.

This is way more important than following the template, having a picture, or almost anything else.

BTW, the recipe intro and the categorization+title combo are offensive to a billion people. Not me, but... expect some vandalism. Kashmir is very much disputed, with 3 countries claiming it or parts of it.

Forking policy
Do take a look at the proposed forking policy; I'd be appreciative of any input before I start spamming it to other interested parties ;) However, hand-in-hand should be a dispute resolution policy also, though since 'books is smaller I doubt we'd have the numbers for the sort of structure 'pedia proper has. Thanks Dysprosia 01:38, 15 Feb 2005 (UTC)

cookbook images
I think it's kind of important to be sure that the images match up with the recipes. Grabbing possibly unrelated images from the commons can be very misleading. For example, you had gingerbread men attached to the gingerbread recipe. (gingerbread is a spice bread, in loaf form, but kind of wide and short more like a cake)
 * Good catch. When I added that image, the description wasn't there, and I didn't check the recipe very well. Gentgeen 00:06, 17 Apr 2005 (UTC)

image locations
Why would somebody not use the commons for an image?

I guess I could see it for an ingredient or tool image being used under the "fair use" provision of copyright law. This reason should not apply to recipes. Hopefully there won't be any need to take advantage of fair use; unlike Wikipedia there shouldn't be any special must-have images that can't be redone. (for example, I can make a new spatula image but not one of an airplane hitting the WTC)

Maybe a Julia Child or Iron Chef image?

I guess I just don't see the need for placing images anywhere other than in the commons. The commons has a somewhat functional way to organize images, unlike wikibooks AFAIK.

AlbertCahalan 22:28, 23 Apr 2005 (UTC)

 * I agree, I prefer commons to specific project uploads myself. However, wikibooks doesn't have control of commons, and the commons pages don't list which articles and modules the image is used on.  Additionally, someone can upload a different image to wikibooks with the same title, overwriting the one at commons.  In my mind, none of these is important enough to not use commons, but other users may think differently.

subpages
I would really like to keep the cookbook free of subpage usage. The idea seems to be somewhat poorly thought through; it assumes a strictly tree-structured book. The header it generates is ugly and inflexible, being redundant to any normal cookbook header. Plus a more obscure annoyance: the "/" makes one-article-per-file scripted processing much more awkward on a UNIX-like system.

 * I agree. When I first got here some of the recipes were at Cookbook:Recipies/Recipe name (sic), which just seemed wrong. Gentgeen 20:18, 24 Apr 2005 (UTC)

double boiler
I think that is way off. Double boilers sure do contact the water.

I'd never heard of a bain-marie before, but the Wikipedia article seems to indicate that a bain-marie is used in an oven. Presumably this would mean the inner pot needs a lid, to avoid baking, and the handle would need to be something that can't melt.

I'm fairly sure the "bain-marie" picture is not in fact a bain-marie. It definitely qualifies as a double-boiler.

chicago sirloin
I don't believe that Midwestern recipes is an appropriate category for Chicago Sirloin with Cabernet Balsamic Reduction. This is a meal with more European influences than anything Midwestern, and certainly does not deserve to be grouped in with chicken wings and Tater tot casserole.

Thanks for your time. Ntm 05:40, 1 May 2005 (UTC)

Chicago sirloin is a style of cooking the steak - chargrilled and rare, not neccesarily the cuisine that the recipes that comes from. But thanks for your input, I will definitely recategorize this recipe when I find one that fits. Thanks! Ntm 23:39, 1 May 2005 (UTC)

anon IP blocks
Infinite IP blocks have two problems: I can't help but be reminded of the problem of being unable to send email because the previous IP address owner caused trouble. AlbertCahalan 07:49, 9 May 2005 (UTC)
 * 1) IP addresses can get reassigned (per-user, or via sale of a whole netblock with thousands of addresses).
 * 2) Some of these may be temporarily infected zombie machines.

Cookbook:Campfire Trout
I see that Cookbook:Campfire_Trout requires bacon, but... why? It isn't used as far as I can see. AlbertCahalan 07:50, 14 May 2005 (UTC)

cookbook things
There are a couple things on the Talk:Cookbook page that I'd like your opinion on. If you have a few minutes I'd appreciate your attention. Kellen 07:21, 23 Jun 2005 (UTC)

 * Thanks for the comment on the advertising. I'd also like your opinion on tagging each recipe with Category:Recipe (to create an index). This is buried in the "categorization proposal" that Albert was not too thrilled about =) Kellen 00:55, 27 Jun 2005 (UTC)

Proposal for policy overhaul
As a fellow admin who might be interested, it might interest you that I've started to think about changes to existing policy and project scope so that policies are more clearly defined (as suggested by User:Aya, who claims existing policies to be ambiguous) and more open (as suggested by User:Robert Horning over the biography debacle). I've made a post on textbook-l as a result, please reply to my talk page for feedback. KelvSYC 05:49, 26 July 2005 (UTC)

welcome back
yay you're editing again! Kellen T 23:50, 5 August 2005 (UTC)

Pipe trick
I'm editing Cookbook:Clear soup and discovered that 'pipe trick' is perfect thing and makes work with cookbook articles lot easier. For example, until now I was not aware that writing  cookbook:carrots  will provide correct link to carrots.

Maybe you should write about pipe trick in Cookbook guidelines for contributors? --Derbeth talk 10:54, 8 January 2006 (UTC)

 * Yeah, the pipe trick should have started working when "Cookbook:" became an actual namespace. I'll go check out the cookbook editing guidlines and recipe templates, and note the new "trick" for our editors.  Thanks, Gentgeen 19:22, 9 January 2006 (UTC)

Policy review
Policy is not the most exciting subject at Wikibooks but we do have some major unresolved issues.

The most important issue, in my opinion, is Dispute resolution which starts by declaring that:

"Currently there is no official organized process to resolve disputes between users"

The suggested remedy for this is: Ad hoc administration committee which puts into place the absolute minimum in terms of an enforcement apparatus.

The second most important is No personal attacks where a vote has recommended the policy be enforced but it still languishes as "proposed".

The third policy that is needed and which will prevent edit disputes from getting out of hand is Editing disputes policy.

Other policies that need consideration are at: Policies and guidelines.

Please spare a minute or two to peruse these issues. RobinH 12:17, 28 April 2006 (UTC)

PAGENAME
Hiya. I saw that you added to a few recipes. While this works in the short term, I think it's a waste of your (or anybody's) time to do that. We should strongly encourage the mediawiki developers to provide some sort of fix that actually works for us rather than twiddling with magic page variables. If we are forced to use PAGENAME, I think we should see if Uncle G or someone else who is proficient with bots could help us out, rather than doing it by hand. Kellen T 00:25, 6 May 2006 (UTC)

 * You might also recall that doing: will automagically sort by  for you. Less typing =) Kellen T 22:22, 20 June 2006 (UTC)

 * It will? I'll have to try that. Gentgeen 03:03, 21 June 2006 (UTC)

cookbookwiki
What do you make of cookbookwiki? Kellen T 18:40, 7 May 2006 (UTC)

 * I actually found it off your WP talk page =) Kellen T 23:59, 11 May 2006 (UTC)

monobook
You're totally right! The whole body has class .ns-102! This could be pretty fun; we could even override the logo! Imagine superimposing a knife and fork on top of it or something. Kellen T 02:08, 6 July 2006 (UTC)

Study Guide for CFA Exam Level III
you deleted this book on 21 June, 2006 as a "copyvio". There is currently a request on WB:VFU to have this book undeleted, under the stated assumption that the author would remove any material in violation of copyright or fair use. I don't know enough about the material to cast a vote on this manner, but if you feel that the material could be made to not violate policy if it were undeleted, i will vote to undelete. --Whiteknight (talk) (projects) 19:24, 19 July 2006 (UTC)

 * Hey, Gentgeen. Could you look at WB:VFU again?  Some discussion has been added.  I believe I can quickly remove the offending content and am eager to start working on this guy again.  Thanks.  --VivekVish 14:39, 27 July 2006 (UTC)

General voting rules/Proposal
I want to call the attention of all wikibookians, especially active admins to the discussion about the new voting policy. Wikibooks currently does not have a concrete voting policy in effect, so the adaptation of this policy will potentially create immediate differences in the way business is conducted here. Due to large amounts of discussion, changes, and dissention, there are several versions of this policy being considered:

 * Version 1 Written by User:Whiteknight
 * Version 2 Written by User:Jguk
 * Version 3 User:RobinH's revision of Jguk's version
 * Version 4 Written by User:Kellen
 * Version 5 Whiteknight's Revision of Kellen's Version.

Also, there are additional issues being discussed, such as the inclusion of a "minimum contributions" clause, that will limit users with less then 20 votes from editing. Also, there is a proposed clause that would allow this 20 vote minimum to be raised in response to abuse.

I am sending this same message to all currently active admins. I hope you are able to come in and give your opinions on this matter. --Whiteknight (talk) (projects) 20:47, 11 August 2006 (UTC)

Thanks
For fixing the main page (and the related vandalism) and it's been a while since you've gotten new messages I see :-) MichaelBillington 06:57, 27 September 2006 (UTC)

Please comment or vote...
Wikibooks:Request for enabling special:import

This would make the transwiki of recipes from en.wp a lot easier (recipes seem to make up the majority of w:Category:Copy to Wikibooks). The folks at meta have asked for a show of local support for turning it on. -- SB_Johnny | talk 12:10, 12 October 2006 (UTC)

Sorry... one more vote please?
One more thing to smooth out the transwiki process... Wikibooks:Request_for_enabling_special:import. We're asking that "Transwiki:" be given namespace status so we can import to it directly. -- SB_Johnny | talk 19:56, 16 October 2006 (UTC)

Analog and Digital Conversion/Other Reconstructors
On 17 July you deleted this page, I assume because it was a stub? I've undeleted it, because I do plan on adding more material to it (even if i have been slow in doing so). I hope you don't mind. --Whiteknight (talk) (projects) 16:08, 27 October 2006 (UTC)

Hooray for fixing the main page
Thanks for fixing Template:New so that the main page is normal again. I can't believe that the main page was like that for an hour. I was trying to figure out what was the cause of the weird formatting. So again, thanks! -Hyad 08:34, 21 November 2006 (UTC)
 * Thanks. Gentgeen

cookbook wantedpages script
I've done some minor tweaks on the wantedpages filtering (no more underscores); User:Kellen/Scripts. Kellen T 00:02, 19 January 2007 (UTC)

 * Cool. I've never actually used the script, however. I always update the list by hand, which is probably a waste of time, but it's my time to waste. Gentgeen 18:45, 19 January 2007 (UTC)

 * Give it a try. It's easy enough if you have a nix system and the basic tools (lynx, grep, and sed). It'll format everything automagically for you. Maybe I could make a cron script to update it here... hrm. Kellen T 20:10, 19 January 2007 (UTC)

Cookbook category order
G'day mate, I recently added the magic word to some of the Cookbook templates, so you no longer need to specify the sort for most pages. For those that you do, e.g. non-ANSI page name, you should specify it as a parameter to the template, e.g. . cheers, Webaware talk 23:56, 27 May 2007 (UTC)
 * Thanks. Gentgeen

Bfbggon
Hi. This guy Bfbggon keeps putting these sick pictures on my talk. He used to keep putting it on after every time I deleted it, but he's not doing that anymore. What happened to him?

My reviewer request
Hi Gentgeen: Please consider supporing my request to become a reviewer. Moby-Dick4000 (talk) 01:05, 30 August 2009 (UTC)

Requests for permissions
Due to inactivity, you've been nominated for removal of the administrative tools. If you wish to support or oppose the matter, please visit the page linked above. Thank you for your contributions up to this point. -- Adrignola talk contribs 13:37, 22 December 2009 (UTC)

WCI 2011 : Accelerating Wikibooks : Would like to discuss!
Hello!

I will be delivering a Talk at the Wikimedia Conference India 2011 on the topic of "Accelerating Wikibooks".

Over the next few days, I aim to make the proposal more and more wholesome and relevant. I'd like to discuss with you about the proposal and hope you can recommend me a few names on Wikibooks with whom I can discuss this.

I'd be very happy if you could discuss the proposal at User:Thewinster/Accelerating_Wikibooks

--Thewinster (discuss • contribs) 08:20, 26 September 2011 (UTC)

Summary of the proposal
This is not a summary of the final talk, only a tentative guideline.

 * Create Roadmaps for a book
 * Define Learning Outcomes
 * Annotate and Discuss new content available from around the web.
 * Minor tweaks and fixes which concentrate on crowdsourcing.
 * Identifying Small Contribution that advance a book and designing good UIs and triggers according to B.J. Fogg's Behavior Change Model, 8 Step Design Process. The paper can be found here at Persuasive Design : Eight Step Process by B. J. Fogg

Hungarian Cheese Dumplings
Hello @Gentgeen! It looks like back in 2004 you edited the Kovaim recipe and stated that they were Hungarian. Someone has since asked about it, and I was wondering if you could explain what made you decide they're Hungarian. Thanks!! —Kittycataclysm (discuss • contribs) 16:18, 2 October 2022 (UTC)

title: User talk:Gentgeen


text:
Invertebrate Zoology

Preface

 * Introduction to the Guide
 * How to use the Guide
 * A special note ~ How to contribute
 * Contributors

Chapters

 * 1) /Introduction/
 * 2) /Protozoans/
 * 3) /Metazoans/
 * 4) /Sponges/
 * 5) /Cnidaria/
 * 6) /Ctenophores/
 * 7) /Flatworms/
 * 8) /Nemerteans/
 * 9) /Pseudocoelomates/
 * 10) /Annelids/
 * 11) /Mollusks/
 * 12) /Arthropods/
 * 13) /Chelicerates/
 * 14) /Crustaceans/
 * 15) /Insects/
 * 16) /Echinoderms/

title: Invertebrate Zoology


text:
Invertebrate Zoology/Guide Introduction

<< Contents Page

Introduction to the Invertebrate Zoology Study Guide
This Study Guide to Invertebrate Zoology is a textbook at Wikibooks shelved at the biology bookshelf section and intended to establish a course of study in the subject of Invertebrate Zoology, mostly utilizing articles found in Wikipedia, with links to other relevant web sites as appropriate. In some cases, portions of the text from Wikipedia articles have been used to materially develop introductory text within the Guide.

For the new user, it need be pointed out that Wikipedia differs from a standard encyclopedia in two important respects: 1) it is a hypertext document, and 2) it is open and editable, and therefore constantly changing. For the student following this or any guide through Wikipedia to cover a specific subject, it is recommended that each article (page) be read first in its entirety, before any hyperlinks are followed to other topics or explanations. It is too easy, otherwise, to simply become lost in a maze of links, and miss the main thrust of an article presented as an assignment from the Guide. Because Wikipedia is constantly changing (and, it is hoped, improving) the quality of each article encountered will be variable. Some articles are well written and go to adequate depth, whereas others, lacking a proponent, are shallow and incomplete. This short-coming should diminish with time, but can be a problem.

One clear advantage to using this Guide linked to a hypertext like Wikipedia is the "circular redundancy with serendipity" factor that arises when an article is read and its hyperlinks followed; this factor can be a powerful learning tool. The persistent reader is subjected to a fairly high degree of repetitive reading, often presenting slightly different perspectives on the same general topic, with the result that learning comes from redundancy. At the same time, some hyperlinks lead down less relevant paths, bringing new and unanticipated knowledge.

title: Invertebrate Zoology/Guide Introduction


text:
Invertebrate Zoology/Authors

This study guide to invertebrate zoology is a textbook at Wikibooks filed under Zoology and intended to establish a course of study in the subject of Invertebrate Zoology, mostly utilizing articles found in Wikipedia, with links to other relevant web sites as appropriate. Contributors are encouraged to spend time developing the relevant articles at Wikipedia, maintaining this textbook as a guide to those articles. At some future time, it may be desirable to simply import whole articles over to build a Zoology textbook rather than a "guide book", however the present approach seems to be a good one for getting a useful text at Wikibooks based upon the initial author's experience with Botany. Another Wikibook, Ecology, follows a similar approach, but requires more text per page, because of less congruence between chapter material and articles at Wikipedia.

The contributors to this book included:

 * Eric Guinther, biologist and environmental consultant living in Kaneohe, Hawaii envisioned this "project" and developed the approach.
 * AFriedman (talk), a User who also performs research in this field on Wikiversity

title: Invertebrate Zoology/Authors


text:
User:Bronger/LaTeX Einführung

Allgemeine Richtlinien:

Der Plan ist, von der alten Methode, LaTeX zu erläutern, wegzukommen. Der ganze historische Ballast wird sofort aufgegeben. Das heißt z.B.:

Die Hoffnung ist, dadurch einen maximal effektiven Einstieg zu ermöglichen. Es ist eine Einführung ("Tutorial") und kein Lehrbuch, das dem Anspruch der Umfassendheit genügen will.

Es soll aber ein in sich geschlossenes Büchlein darstellen. Die typischen Elemente eines Dokuments sollen abgedeckt werden.

=Was ist LaTeX?=

LaTeX ist ein Computer-Programm, mit dem man Texte schreiben kann. Seien es kurze Memos, Briefe, längere Berichte, Studienarbeiten oder auch ganze Bücher: LaTeX kommt mit nahezu allen Textsorten problemlos zurecht. Für jeden dieser Fälle garantiert LaTeX ein professionelles, perfekt gestaltetes Layout.

LaTeX legt dabei besonderen Wert auf drei Dinge:
 * 1) Bei der Eingabe des Textes soll sich der Autor voll auf seinen Text konzentrieren können, und nicht von Layout-Einstellungen, Seitenumbrüchen oder ähnlichem abgelenkt werden.
 * 2) Beim Druck oder der Bildschirmdarstellung des Textes wird bestmögliche Qualität abgeliefert, selbst wenn der Autor von solchen Dingen keine oder kaum Ahnung hat.  Es wird dabei ein Niveau erreicht, das beispielsweise mit Word nicht zu realisieren ist.
 * 3) Zuverlässigkeit.  Der Kern des LaTeX-Systems gilt als einer der stabilsten und bugfreiesten überhaupt.  Selbst bei sehr komplexen Dokumenten, z.B. mit vielen Grafiken und Tabellen, bleibt das Programm belastbar und schnell.

Soweit es das Erzeugen von Dokumenten angeht, ist LaTeX ein vollwertiger Ersatz für Textverarbeitungsprogramme wie Word. Es ist alles dabei, was das Herz begehrt: Formatierung, Schriftarten, Grafiken, Tabellen, Aufzählungen, Fußnoten, Querverweise, Rechtschreib-Kontrolle, automatische Verzeichnisse, etc.

Es gibt sogar einige Dinge, die LaTeX den meisten anderen Programmen voraus hat. Zwei Beispiele:
 * LaTeX kann selbstständig für alle Abbildungen und Tabellen des Dokumentes die bestmöglichen Plätze suchen. Obwohl der Autor das auch überstimmen kann, lernt man diese Hilfe schnell zu schätzen.
 * Leute, die ihren Dokumenten Literaturverzeichnisse anfügen müssen, können das zu einem guten Stück automatisch durch LaTeX erledigen lassen.

Kein WYSIWYG
In Word tippt man seinen Text, und man sieht ihn dabei auf dem Bildschirm genau so, wie er später aus dem Drucker kommt. Man nennt diese Technik "WYSIWYG". Es ist eine komfortable Möglichkeit der Texteingabe.

LaTeX geht dennoch einen anderen Weg. Man tippt seinen Text, sieht dabei jedoch nur Inhalt und Struktur (Gliederung) des Textes. Es fehlen also Dinge wie Schriftarten, Seitenumbrüche oder Zeichenabstand. Das ist zwar spartanisch, reicht aber völlig aus, um den Text zu bearbeiten. Keine Sorge: Es genügt ein Tastendruck, um jederzeit ein Vorschau-Fenster zu aktualisieren, in dem das Endergebnis absolut verbindlich dargestellt wird, und zwar noch akkurater als mit Word.

Das ist quasi eine Not, aus der LaTeX eine Tugend macht. Zum einen ist der Verzicht auf WISYWIG ein wichtiger Grund für die Zuverlässigkeit von LaTeX. WYSIWYG ist nämlich eine sehr aufwendige und daher etwas anfällige Technik. Zum anderen hat so der Autor seine Ruhe vor Layout-Fragen. Wenn man will, kann man zwar auch mit LaTeX das Layout nahezu beliebig beeinflussen. Aber wenn nicht, sorgen die Vorgaben der Profis, die LaTeX gemacht haben, für ein hervorragendes Resultat.

=Die Installation unter Windows=

Wir werden in diesem Abschnitt erfahren, wo man LaTeX herbekommt und wie man es unter Windows installiert. Wenn man erst mal schauen möchte, wie LaTeX ungefähr funktioniert, kann man auch vorerst diesen Abschnitt überspringen und mit dem nächsten, "Das erste Dokument", weitermachen.

 * 1) Bezugsquellen (Downloads, Bestellen; muß eventuell mit dem Folgenden verquickt werden)
 * 2) Software:
 * 3) * Acrobat Reader
 * 4) * Ghostscript/GSView
 * 5) * MikTeX (full)
 * 6) * TeXnicCenter
 * 7) Knappe Beschreibung der Installation, ohne Alternativen zu nennen.

=Das erste Dokument=

Erste Schritte
Grundsätzliches zum Handling des Editors

Um endlich mal konkret zu werden, gibt man folgendes Dokument in den Editor ein … \documentclass{scrartcl}      % Wir brauchen keine Kapitel \usepackage[ansinew]{inputenc} \usepackage[T1]{fontenc} \usepackage{graphicx,mathptmx,courier,textcomp,booktabs} \usepackage[scaled]{helvet}

\usepackage[ngerman]{babel}   % Neue deutsche Rechtschreibung

\begin{document}              % Hier geht der eigentliche Text los

Hallo! Dies ist der erste Absatz dieses einfachen Textes. Ich muß jetzt hier ein wenig herumlabern, um ihn ein wenig länger zu bekommen, sonst kann man nachher nicht so schön sehen, wo der eine Absatz aufhört und wo der andere anfängt.

Dies ist der zweite und letzte Absatz.

\end{document}                % Und hier hört er auf … und drückt und F7 und F5. Es öffnet sich ein Fenster, in dem man den Text so sehen kann, wie er auch später aus dem Drucker kommen wird.

Aber was bedeutet das, was wir gerade getippt haben? Die allererste Zeile ist \documentclass{scrartcl} und sie besagt, dass unser Text keine Kapitel benötigt. Die Alternative wäre gewesen, stattdessen \documentclass{scrbook} zu schreiben. Dann hätte unser Dokument Kapitel haben können. Die folgenden vier Zeilen sagen LaTeX unter anderem, daß wir Windows benutzen. Es leider nötig, es einzufügen, aber unnötig, seine genaue Bedeutung zu kennen. Glücklicherweise muß man es nur einmal pro Dokument eingeben, und man kann es aus einem anderen Dokument herauskopieren.

Die Anatomie eines LaTeX-Befehls
Die überwiegende Zeit tippt man einfach seinen Text, egal, welches Programm man dafür benutzt. Aber manchmal muß man seinen Schreibfluß unterbrechen, z.B. weil ein neuer Abschnitt beginnen soll, oder weil man eine Grafik einfügen möchte. In Word muß man dann auf Icons klicken, Menüpunkte anwählen oder Tastenkürzel benutzen. In LaTeX fügt man Befehle und Umgebungen ein. Diese Befehle und Umgebungen kann man mit seinem Text zusammen im Editor-Fenster sehen. Der Editor färbt sie zur besseren Übersicht blau ein.

Fangen wir mit den Befehlen an. Unser kleines LaTeX-Beispiel beginnt mit \documentclass{scrartcl} Das ist ein typischer LaTeX-Befehl. Er sagt aus, daß wir einen Text ohne Kapitel schreiben wollen. Ein LaTeX-Befehl hat immer den folgenden Aufbau:
 * 1) Er beginnt mit einem umgekehrten Schrägstrich "\", einem sogenannten "Backslash".
 * 2) Dann folgt der Name des Befehls, z.B. "documentclass" für "Die Klasse des Dokumentes".
 * 3) Als letztes kommen zusätzliche Angaben, die sogenannten Parameter.  Sie stehen jeweils in geschweiften Klammern {...}, und es können keiner, ein, zwei oder manchmal noch mehr für einen Befehl sein.  Mehr als zwei ist aber extrem selten.  Unser Beispiel-Befehl hat nur einen Parameter, nämlich eben das Kürzel "scrartcl".

Die zweite Gattung von sonderbaren Dingen in LaTeX-Texten sind die Umgebungen. Umgebungen klammern einen Textes ein. Unser Beispiel-Dokument von vorhin enthält genau eine Umgebung, und es ist sogar die wichtigste: \begin{document} ... \end{document} Die document-Umgebung enthält das ganze Dokument. Jede Umgebung beginnt mit \begin{Umgebungsname} und endet mit \end{Umgebungsname} Ganz selten haben auch Umgebungen Parameter. Die stehen dann hinter dem \begin{...}.

Die Schnellvorschau
YAP

Endgültige Vorschau & Drucken
PDF-Erzeugung (pdflatex), Acrobat-Reader

An dieser Stelle hyperref erwähnen.

Wenn mal was schiefgeht …
Typische Probleme: (Probleme mit Grafiken werden dort behandelt.)
 * LaTeX-Kompilierfehler
 * Probleme mit dem Editor (Undo u.ä.)

=Formatierung=

 * \emph
 * Sonderrolle der Anführungsstriche, german.sty-Befehle, zumindest "" und "~.
 * Dinge wie \&, \$, <tt>\%</tt>, <tt>\S{}</tt>, <tt>\LaTeX{}</tt>
 * Listen
 * mathptmx, mathpazo

=Tabellen=

tabular & table. Querverweise mit <tt>\ref</tt>? Soll man gleich mit booktabs arbeiten?

=Grafiken=

graphicx, <tt>\includegraphics</tt> und figure. Behandlung von pdf, png und jpeg.

=Ein größeres Beispiel=

Diplomarbeit-artig.

Projekt-Funktion von TeXnicCenter erwähnen?

=Anhang=

Grafiken, die nicht PDFs, PNGs oder JPEGs sind
ps2pdf (oder besser epstopdf?), gif --> png.

Formeln

 * Sofort AMSTeX einbinden, z.B. eqnarray gar nicht mehr erwähnen.
 * Verweis auf die umfassende LaTeX-Symbol-Liste im Internet, d.h. nur Tabellen mit den wichtigsten Symbolen einbinden.

Das Erstellen eines Literaturverzeichnisses

 * Manuell
 * BibTeX nennen, aber nicht beschreiben.

Weiterführende Literatur
Kurzbeschreibung, KOMA-Script, etc.

Kritische Anmerkungen zu jeder Referenz, insbesondere beim Kopka

title: User:Bronger/LaTeX Einführung


text:
User talk:Bronger/LaTeX Einführung

Warum schreibst Du das Buch nicht gleich unter LaTeX-Einführung oder besser LaTeX-Schnellkurs? Nachtrag: Habe jetzt unter LaTeX-Schnellkurs mit dem Projekt begonnen. – 217.1.206.25 09:59, 9 Jan 2004 (UTC)

 * Weil solche Projekte, wenn sie zu früh an die große Glocke gehangen werden, schnell zerfleddert werden. Erst recht, wenn es derart unorthodox ist.  Die Idee dazu entstand gesten bei einem Abendessen, und es ist geplant, das ganze fühestens im April mit Anfängern im Rahmen einer Einführungsveranstaltung auszuprobieren.  Dann wird sich zeigen, ob das Konzept brauchbar ist.

 * Nimm dir zum Beispiel deine MacOS-Erweiterung in deinem Schnellkurs: Das ist sicher löblich und kompetent geschrieben, aber dann mußt du im folgenden wieder zwei Editoren (oder einen generischen) beschreiben, was ein Anfänger gar nicht gerne hat. – Torsten Bronger 10:52, 9 Jan 2004 (UTC)

 * Habe ich mir auch überlegt, aber durch TeXShop gibt es auf einmal soviele Apple-Anwender, die mit TeX anfangen wollen, daß es irgenwie schade wäre, wenn man denen nicht einen möglichst einfachen TeX-Einstieg anbieten könnte. Man kann ja im Hauptverlauf den Vorgang unter Windows beschreiben und nur auf das Wikibooks-Modul verweisen, das den Vorgang unter Mac OS X erklärt. Eine andere Variante wäre: zwei Inhaltsverzeichnisse, die auf die jeweils richtigen Module verweisen. Was hältst Du denn davon? 217.1.206.25 11:01, 9 Jan 2004 (UTC)

 * Beides sind interessante Ideen. Man sollte versuchen, dort, wo es nicht unbedingt nötig ist, auf Screenshots und direkte Erwähnung von TeXnicCenter-Funktionen zu verzichten.  Dadurch hielte man die Zahl der auszutauschenden Module minimal.  Leicht wird das aber nicht.  Es ist ja nicht nur mit der Beschreibung der Editor-Grundfunktionen getan.  Auch die PDF-Erzeugung, die Behandlung von Kompilierfehlern sowie die Schnellvorschau sind vom OS abhängig. – Torsten Bronger 11:26, 9 Jan 2004 (UTC)

Deine Konzeption gefällt mir gut. Besonderen Wert würde ich auf ausführlich kommentierte Musterdokumente legen. – 217.1.206.25 10:02, 9 Jan 2004 (UTC)

 * Das ist sicher eine gute Sache. – Torsten Bronger 10:52, 9 Jan 2004 (UTC)

 * Ein paar einfache Musterdokumente könnte ich auch beisteuern (scrlttr2 & g-brief), ich müsste sie nur noch kommentieren, dürfte aber machbar sein (meine eigenen Anfänge liegen schließlich noch nicht allzu weit zurück). Auch ein längeres Fanfic (knapp 30 Seiten) würde ich eventuell hergeben, ist aber eben 99% Text und kaum LaTeX. Bei Windows-spezifischen Dingen kann ich aber nicht helfen, davon habe ich keine Ahnung.

 * Das Projekt lebt nun bei, weil es dort CVS-Zugriff gibt. Ich bin aber gerne bereit, zum Wikibooks-LaTeX-Projekt beizusteuern.  Es ist bereits seit seinem Bestehen auf meiner Watchlist.

title: User talk:Bronger/LaTeX Einführung


text:
Spanish/Verb Tenses

../Verbs/ | ../Verbs List/

Vosotros

 * ../Vosotros Usage/

= Los tiempos de los verbos: por simples y compuestos =

 * infinitivo estudiar - to study
 * gerundio estudiando - studying
 * participio presente estudiando - studying
 * participio pasado estudiado - studied - used with Haber

Siete tiempos sencillos

 * 1) presente de indicativo estudio - I study
 * 2) imperfecto de indicativo estudiaba
 * 3) pretérito estudié
 * 4) futuro estudiaré
 * 5) potencial simple estudiaría
 * 6) presente de subjuntivo estudie
 * 7) imperfecto de subjuntivo estudiara

Siete tiempos compuestos

 * 1) perfecto de indicativo he estudiado
 * 2) pluscuamperfecto de indicativo había estudiado
 * 3) pretérito anterior hube estudiado
 * 4) futuro perfecto habré estudiado
 * 5) potencial compuesto habría estudiado
 * 6) perfecto de subjuntivo haya estudiado
 * 7) pluscuamperfecto de subjuntivo hubiera estudiado

= Los tiempos de los verbos: por modos =

Gramatically, there are different ways of classifying Spanish verb forms (as well as the verbs of any language). The one most people understand is "tense", but another very important classification is the "mood." A "mood" is differentiated from a "tense" in that it does not express time per se (which is what "tense" really means). Unfortunately, "mood" is not really a very good name either because moods do not express moods of the speaker (happy, sad, etc.) The mood is used to classify how the verb is used grammatically in the sentence; that is, how the verb usage works together with the other parts of the sentence. Spanish has the following verb moods:

 * Indicative (indicativo): Used to express statements of fact as the main verb of a clause
 * Participial (participio, gerundio): Used to convert a verb into a noun or adjective to express not actions but rather qualities or objects related to the verb
 * Conditional (potencial): Used together with other clauses to indicate a potential fact.
 * Subjunctive (subjuntivo): Used together with a main clause to indicate that the subordinate clause is somehow under discussion (mooted).
 * Imperative (imperativo): Used to express a direct command.

In many cases, along with the name of the mood also goes a tense. A given form of a verb normally has both mood and tense, although when the mood is indicative usually the name of the mood is not stated. This is one thing that makes the concept of moods hard to understand. When we talk about the "present tense" of a verb, we really should say "indicative mood, present tense". This would make it clear that when we say "subjunctive mood, present tense" we're not dealing with anything particularly strange, only a little different.

 * infinitivo
 * gerundio
 * participio presente
 * participio pasado

El modo indicativo

 *  En el tiempo presente

 * presente de indicativo, presente progresivo de indicativo
 *  En el pasado

 * imperfecto de indicativo, imperfecto progresivo de indicativo
 * perfecto de indicativo
 * pretérito
 * pluscuamperfecto de indicativo
 * pretérito anterior
 *  En el futuro

 * futuro
 * futuro perfecto

El modo subjuntivo

 *  En el presente

 * presente de subjuntivo
 *  En el pasado

 * imperfecto de subjuntivo
 * perfecto de subjuntivo
 * pluscuamperfecto de subjuntivo
 * El futuro subjuntivo (estudiare)
 * El futuro perfecto subjuntivo (hubiere estudiado)

El modo potencial

 * potencial simple
 * potencial compuesto

El modo imperativo

 * imperativo

Spanish | ../Verbs/ | ../Verbs List/

title: Spanish/Verb Tenses


text:
Spanish/Imperfect

../Verbs/

The imperfect tense communicates:
 * continuing past events (translates English was/were __ing)
 * customary, habitual events in the past
 * planned future events

Verbs are conjugated to the imperfect by taking off the last two letters of the infinitive and replacing them with an ending based on -ía or -aba.

Conjugating regular verbs in the imperfect
This is probably the easiest verb tense to conjugate.

-AR verbs take on the -aba endings. Here is an example:

Bailar (to dance)

 bailaba: I danced  bailabas: you danced  bailaba: he, she, it, you (formal) danced  bailábamos: we danced  bailabais: you danced  bailaban: they, you (plural, formal) danced

-IR and -ER verbs take on -ía endings. Examples:

Venir (to come)

 venía:  I came  venías:  you came  venía:  he, she, it, you came  veníamos:  we came  veníais:  you came  venían:  they, you (formal) came

Comer (to eat)

comía: I ate comías: you ate comía: he, she, it, you ate comíamos: we ate comíais: you ate comían: they, you (formal) ate

Irregular verbs
There are only three.

Ser (to be)

era: I was eras: you were era: he, she, it was, you were éramos: we were erais: you were eran: they were

Notice the accent in the "nosotros" form of "ser" and "ir."

Ir (to go)

iba: I used to go ibas: you used to go iba: he, she, it, you used to go íbamos: we used to go ibais: you used to go iban: they used to go

Ver (to see)

veía: I used to see veías: you used to see veía: he, she, it, you used to see veíamos: we used to see veíais: you used to see veían: they used to see

That's it! Those are all the irregulars.

title: Spanish/Imperfect