text:
QBasic/Flow Control

Conditional execution
To choose between two or more sections of the program to execute, the IF statement can be used. It is also possible to use the WHILE, DO UNTIL and CASE statements. All of these control conditional execution by using a Boolean logic 'test', the result of which is either TRUE or FALSE. To repeat a section of code for a set number of times, the FOR statement is used.

The IF test can be executed in a single line, however it can also be used like the others to control a block of code.

True or False
Boolean logic is a test that yields one of only two possible results, true or false. The tests are always mathematical in nature .. when two characters (or strings) are 'compared' it is their ASCII codes that are used (thus a < b and b < A).

The comparison operators used in qbasic are: = true if two variables are equal < true if the first is less than the second =< true if the first is less than or equal to the second > true if the first is greater than the second >= true if the first is greater than or equal to the second <> true if the two are unequal

Multiple tests can be linked together in the comparison, using the 'AND', 'OR' and 'NOT' operators. We will cover exactly what these mean later on, but you probably understand the first two already.

IF
One of the most useful statements in QBasic is the IF statement. It allows you to choose what your program will do depending on the conditions you give it. The next few programs will be taking a look at ways to use the IF statement.

IF [conditional] THEN [do this]

The single line IF is the simplest example. To execute a block of code, the END IF is used

IF [conditional] THEN [do this] [and do this] ...   [and also do this] END IF

IF...THEN...ELSE
IF [conditional] THEN [do this] ELSE [do that]

To choose between two different code blocks, the ELSE statement is used.

IF [conditional] THEN [do this] ..  [and do this] ELSE [do that] ..  [and also that] END IF

13 ELSEIF
As an alternative to starting an entirely new IF THEN ELSE statement sequence. You can follow the THEN statement(s) with ELSEIF [conditional] THEN. This does not create a new level of nesting.

IF [conditional] THEN [do this] .. [and do this] ELSEIF [conditional] THEN [do that] .. [and also that] ELSEIF [conditional] THEN [do the other] .. [and also ...] ELSE [do this final thing] END IF

FOR...NEXT
FOR = TO [STEP ] [do this] ... [and do this] NEXT

may be + or - and is optional. If omitted the default is +1. The code contained within the FOR loop will always be executed at least once because it is only at the 'NEXT' statement that the value of the variable is checked against the end value.

When the NEXT statement executes, the variable is modified by STEP value and compared against the end value. If the variable has not yet exceeded the end value, control is returned to the line following the FOR.

You can exit a FOR loop early with the EXIT FOR command.

WHILE...WEND
WHILE [do this] ..   [and this] WEND

If the condition is true, the code following the WHILE is executed. When the WEND command is executed, it returns control to the WHILE statement (where the condition is tested again). When the condition evaluates to FALSE, control is passed to the statement following the WEND.

15WHILE.BAS
In the example above, you see a press any key prompt that waits until the user presses a key. (The INKEY$ feature will be described under Advanced Input.)

DO...LOOP
DO   [this] ..   [and this] LOOP WHILE / LOOP UNTIL

The DO...LOOP construct is a more advanced of the WHILE loop - as with other flow control blocks, it is marked by DO and LOOP to denote the boundaries.

It relies on a conditional statement placed after either DO or LOOP:

As an alternative, you can instead replace WHILE with UNTIL have the loop continue until a specific condition is met:

In some versions of BASIC the UNTIL or WHILE condition can follow the DO statement rather than the LOOP statement (pre-test) as apposed to the above shown (post-test).

SELECT CASE
SELECT CASE CASE [do this] CASE [do instead] ...   CASE ELSE ... END SELECT

The select statement is a substitute for repeated use of IF statements. The is evaluated and compared against each CASE in turn. When a CASE is found to match, the [do this] code following is executed. If an EXIT CASE is executed, control passes to the line following the END SELECT, otherwise the next CASE is checked. If no matches are found, the CASE ELSE is executed. Note that may be a number, character or string or logical expression (eg '>0', '<>1'). Note also that multiple CASE matches may be found and executed (so, for example, if two CASE are 'CASE >1' and 'CASE >10', a that evaluates to 11 (or more) will result in both CASE >1 and CASE >10 being executed)

If a parameter would be covered by more than one case statement, the first option will take priority.

title: QBasic/Flow Control


text:
Cookbook:Barbecue Sauce (Kansas City-style)

| Sauce

Barbecue Sauce is a tomato or ketchup based sauce used on meats. Kansas City-style barbecue sauce is the most common version used in the United States. It is tomato- or ketchup- based with sweet, sour and smoky elements. Barbecue sauce can be added to the meat before, during or after cooking. This version contains quite a bit of sugar, so it should be added near the end or after cooking the meat to avoid burning the sauce.

Ingredients

 * 1 cup (235 mL) ketchup
 * 6 tablespoons (90 mL) Worcestershire sauce
 * 4 tablespoons (60 mL) butter or margarine
 * 3 tablespoons (45 mL) white vinegar
 * 1 tablespoon (15 mL) plain prepared mustard
 * 3 tablespoons (45 mL) finely minced yellow onion
 * 4 teaspoons (20 mL) bottled liquid smoke flavor (hickory)
 * ¼ teaspoon (1 mL) Louisiana-style red pepper sauce
 * ½ cup (120 mL) brown sugar
 * 1 tablespoon (15 mL) granulated sugar
 * 1 teaspoon (5 mL) salt

Procedure

 * 1) Combine all ingredients in a saucepan.
 * 2) Mix well.
 * 3) Simmer over low heat for 20 minutes, stirring occasionally.

Notes, tips, and variations

 * This sauce tastes very close to commercial barbecue sauces such as Masterpiece and Bullseye.

Warnings

 * Keep refrigerated
 * Add to meat near end or after cooking to avoid burning sauce because of sugar content.

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


text:
Cookbook:Yogurt

| Dairy

Yogurt or yoghurt is a pudding-like food made from milk fermented in a culture of (typically) Lactobacillus delbrueckii bulgaricus and Streptococcus salivarius thermophilus bacteria. "Live active culture" is a type of yogurt that has the live bacteria still in it, also known as Curd in the Indian subcontinent. Some people believe that this "live" yogurt has special health benefits. The other variety is pasteurized yogurt, officially known as Heat Treated Fermented Milk, where the yogurt is heated to kill the bacteria. This pasteurized yogurt is usually available in supermarkets. Many websites and blogs include pages that serve as instruction books on how to make yogurt out of milk, such as one run by Brendon and Ryan Ross. Yogurt derives romfrom the Turkish word yoğurt and in English, the word can be spelled either 'yogurt' or 'yoghurt'.

Characteristics
Lactic and other acids produced during fermentation give it a slightly sour taste. This may be offset by adding sugar or other sweeteners, along with additional flavorings. Yogurt without sweeteners or flavorings is typically referred to as plain yogurt or natural yogurt.

Varieties
Many varieties and forms of yogurt are commercially available, such as:

 * Greek yogurt
 * Skyr
 * Yogurt drink
 * Frozen yogurt
 * Dairy-free yogurt

Uses
Yogurt can be eaten on its own or used as an ingredient in cooking. In western countries, it is usually eaten with fruit or jam.

Yogurt can also be substituted for buttermilk when baking, as in the recipe for Corn Muffins.

Yogurt can also be used as a garnish for savoury food, particularly in the Middle East and South Asia.

List of Indian recipes using curd:

 * Cookbook:Grape Lassi
 * Cookbook:Raita
 * Cookbook:Hyderabadi Marag
 * Cookbook:Sev Puri
 * Cookbook:Biryani
 * Cookbook:Yogurt Curry Soup (Kadhi)
 * Cookbook:Dahi Baingana

title: Cookbook:Yogurt


text:
History of Elven Writing Systems

Welcome to the WikiTextBook on History of Tolkien’s Elven writing systems

also known as

Quenta Eldatencelion

Being an Account on the Elvish Writing Systems through the Ages and Modes as exemplified and described in the works of Professor John Ronald Reuel Tolkien.

Theories written and expressed by various Elvish scholars through the years, and compiled in the Common Speech.

Go to Foreword >>

title: History of Elven Writing Systems


text:
User:GregFrotton

This is a wonderful idea!

title: User:GregFrotton


text:
History of Elven Writing Systems/Foreword

Fantasy author J. R. R. Tolkien invented many writing systems to be used by his Elves and other races in his fictional world of Middle-earth.

This is a detailed account of the writing systems used by the Elves. The essay is concentrated on the process of time in the fictional history and the Ages of Middle-earth, and its purpose is to show how writing could have evolved by various races of the legendarium, as well as the interrelation between modes. The logical process behind evolution of each system from the other is speculated.

Disclaimer
The document doesn't include many explicit quotes from Tolkien’s writings for reference, but it is clear that many statements set forth are conclusions out of the authors' judgement from the sources and evidence. Words like “assume”, “speculate”, “reconstruct”, “must” and “perhaps” are used, and the reader must have in mind that these theories have not been ensured by examples or explicitly stated by Tolkien.

The same applies to the examples of some writing systems, like early Certhas, specimina of which Tolkien haven’t left to us at present. On the contrary, this essay provides all of known (elvish) Tengwar samples that have been written by Tolkien, leaving the final judgment to the reader.

What this document is not

 * The document is by no means a tutorial for starters, or a guide of how to write Tengwar. Although it can be used as such, there are better and more practical tutorials and guides available. What can it be used for is a reference guide for all known systems (some of them hypothetical or reconstructed) and is recommended as a supplement for such a study by a starter.
 * The document does not try to describe every single system that came into Tolkien’s mind, but takes account only his “latest” elaborations that he must have considered “current” while writing Lord of the Rings and the later Silmarillion. So no description of the early Sarati, the “Valmaric script” or the “Runes of Pengolodh” will be found there.
 * English and Old English modes for Tengwar devised by Tolkien won't be described either.

Legal remarks
The essay tries not to show anything that goes beyond Fair Use and doesn’t quote so extensively from Tolkien's work as to run afoul of it. All quotation is used for the purpose of supporting the analysis that forms the vast majority of the work.

History
Eldatencelion started as a timeline of all the changes that took place forming the Elvish writing systems according to the information given in Appendix E to The Lord of the Rings. An early form was hosted kindly in Gwaith-i-Phethdain in a portable document format, and was soon translated into Italian by Eldalie.it. It was ported to wiki format on January 2005 and has been improved and changed ever since.

On reading this document
The reader must have the following way of formatting in mind:
 * Names of published corpus are in bold: LotR, King’s Letter, Moria Gate Inscription
 * Words or sounds used as samples (usually elvish) are in italic: thúle, parma
 * Tengwar names are not in italic, but their first letter is capital: Thúle, Parma
 * Minus are used to show etymological process or change in pronunciation: *áse > áze > áre
 * Non-attested hypothetical forms (usually archaic) are asterisked: alda < *galadâ
 * Wrong forms are asterisked twice: alda < *galadâ, not **aladâ
 * Primitive stems and etymological roots are always in capital: alda < GALAD

FA, SA and TA mean First, Second and Third Age respectively.

Note: The document makes heavy use of certain fonts of Tengwar, Runes and, in a case, Sarati. The fonts that need to be installed in order to view this document properly are:
 * Sarati Eldamar and
 * Tengwar Parmaite, both by Måns Björkman
 * Cirth Erebor by Dan Smith
 * Gondolinic Runes by Ronald Kyrmse

Some other compatible fonts will also work since most of the best-known tengwar fonts follow the layout proposed by Dan Smith. In some cases, Tengwar doesn’t render correctly in Internet Explorer, so other browsers are recommended (the display is fine in Mozilla Firefox). The problem can alternatively be overpassed by copying and pasting the text into a word processor such as MS Word.

Acknowledgements
The present form of the essay owes much to the contributions of knowledge by Helge Fauskanger, Måns Björkman, Daniel Adriës, Ryszard Derdzinski, Carl Hos and others, as well as the editors of Vinyar Tengwar.


text:
History of Elven Writing Systems/Age of Starlight

= Sarati = Rúmil of Tirion was a Noldorin scholar and the composer of Ainulindale. Before that he was the inventor of the first elvish writing system in the Valian Year 1179. It has been suggested that his system was based on an even more ancient, unrecorded writing system of the Noldor, but this is hardly probable. The Sarati (“significant marks”), as he called his letters, were ideal for writing both on stone and on paper, but we have only seen what seems to be their “calligraphic” versions.

Several different writing-directions were used with the script. Rúmilian texts were written in rows or in columns like Japanese, LTR like the western scripts, RTL like eastern scripts or boustrophedon (RTL–LTR–RTL etc.) like some ancient Greek inscriptions.

Rúmil decided that the vowels should be written with diacritics and not with independent letters, since, according to the linguistic perceptions of the Valinorean loremasters, vowels were considered as “colours” of the consonants.

Todate various interinconsistent modes of Sarati have been published, from various stages of Tolkien's youth and development. They are mostly used for English or early Qenya words and phrases. Unfortunately there is no definite, compatible to Lord of the Rings-Quenya mode of Sarati known.

= Early Tengwar = Fëanáro Curufinwë (better known as Fëanor) invented the tengwar (“signs representing audible phonemes”), strongly influenced by the Sarati, in the Valian Year 1250. From that time on, the term Sarati, from the general notions of “letter”, only refers to the Rúmilian writing system.

Rumilian Influence
With the first sight one might observe the stylistic influence of the Sarati. Especially two of the sarati (namely P p and B b ) are visually similar to the shape of a tengwa, since their morphology is consisted of a “line” and “curves”. The organization of the tengwar follows the aforementioned concept, where the form of the letter reflexes its sound. Fëanor decided that the doubling of a “curve” should add voice to the “basic” sound, and generally the way the “curves” are doubled is similar to the “p” and “b” sarati, so these two sarati must be his main inspiration.

Fëanor therefore, by reducing the number of variable elements, produced a simpler and more consistent set of characters. The two basic elements of the tengwar were a “stem” (telco) and a “bow” (lúva), which could be combined and modified in a number of different ways. Fëanor decided that the tengwar whose telcor and lúvar were organized in a particular way, represented a certain group of related sounds: The telcor determined how the sound was articulated, and the lúvar where in the mouth it was made.

The greatest difference between the systems was that the tengwar were written from left to right.

Table
It is more probable that the Tengwar system was not especially based on the needs of Quenya, Feanor's mother tongue; this is obvious when we compare the Quenya mode table with other, later modes, where the phonemes fit to the Tengwar table more consistently. It is therefore possible that the Tengwar started initially more like a generic phonological 'template', on which all later derived modes and spellings could be based. The dialects of Aman as well as ancient reconstructed words could then be written with an adaptation of that generic system.

The following table is based on a theory by Jim Allan, published in An Introduction to Elvish. It shows a reconstruction of the original theoretical 'template' of the Tengwar, perhaps never used in any language.

The only mode known closest to the theoretical values would be the General Use mode, of which we first hear millennia later.

Note that the second-to-last series represents voiceless consonants.

=Quanta Sarme= Unlike Rúmil, Fëanor considered vowels as independent sounds and not just “colours” of the consonants, so he devised the “full writing” (Quanta Sarmë).

Quanta Sarme had distinct letters for vowels (ómëar or óma-tengwi), and was used by the Loremasters for special purposes only. No texts of this system are known to us, and its usage and characters are unknown, but Tolkien says that it was used in Middle-earth for other languages, like Sindarin, where the tehta-mode was inconvenient.

This system is not heard much thereafter and it seems that its usage hasn't endured into the following Ages. However by the above information, we can easily assume that it was the predecessor of the Mode of Beleriand, and the letter Osse ] is maybe the only remnant of that (otherwise extinct) system.

=Original Quenya mode= Despite Fëanor is said to prefer the Quanta Sarme, he also used a more 'conservative' system which (judging by the majority of the subsequent samples) seem to have been proved far more popular. Fëanor held the idea of syllabic analysis of the words by the Sarati, and made also use of signs (tehtar) for vowels (instead of the full letters), placed over the preceding tengwar/consonants, indicating their “colour”. A consonant followed by a vowel was considered as a “full letter” (ñávëa or ñáva-tengwë). The sarat ‘ was imported from the previous system, and when a vowel had no preceding consonant, it was used as a carrier for convenience in writing. This system however was used by Fëanor mainly for tradition and brevity, favouring the Quanta Sarme instead.

Apart of the standard consistent characters, there were also additional tengwar which don't fit in the structure. These are usually modifications of the standard tengwar. Hyarmen is a modification of Charma, Úre is of Wilya, and Anna derived from an earlier sarat.

Table
According to Appendix E (mixed with other recently published sources) and our knowledge on Quenya phonology evolution, we can reconstruct a Tengwar table, hopefully as close to the original Feanor's concept as possible:

Examples
Like the Sarati, the Amanya system of the tengwar is also unknown at this point. According to the theories mentioned above, they will be tentatively reconstructed, showing some tengwar transcriptions of various Quenya words as pronounced in Fëanor’s time. For better understanding the words and the connection between spelling and etymology, alongside are given the etymological roots or the better attested later Quenya forms:
 * dE6U, *cheru < KHER
 * 1E.6R, taurë
 * 1`C.D6R, *tawarë > tavar
 * `C.D,Fj, *awazel > aurel
 * hEm#, ''*3alda > alda
 * 1Ulj$, tuilë < TUY

Possible examples of Quanta Sarme
We know absolutely nothing about the Quanta Sarme orthography and the following are purely conjectural, based solely on what we know about 'classical' tengwar.
 * ],Ö], azya
 * l]y]55], Yavanna
 * ½]5., hanu < HAN

= An alternative mode = For variant spellings, the general hypothetical 'template' above could have been implemented. For example, we have no clue on how the Vanyar and Teleri used the known Tengwar, since their dialect possessed sounds not found in Noldorin, like independent d and b. The Vanyarin poem’s name, Aldudénie, is known from the Silmarillion, and the word ulban, “blue”, is also adapted from Valarin by the Vanyar. They could probably write these words by modifying this flexible system according to their language (like the Noldor and the alien speakers did later in Middle-earth), but some sources state that the Vanyar kept the Sarati. Tolkien notes that the system of Fëanor provided the means of expressions for more sounds than those occuring in Quenya and Telerin, but he doesn’t mention them or the reasons.

In Addenda et corrigenda to the Etymologies, an old version of the tengwar by Tolkien appears. Some tengwar have different names and values. It is not known if this mode coexisted with the one presented above, or if one evolved after the other.

Table
= Certhas = During that time, the Sindar of Beleriand began developing an alphabet for their language. Its letters were entirely made for carving on wood, stone or metal, hence their angular forms and straight lines. These letters were named cirth (sing. certh).

The assignment of values was unsystematic. The form of a certh was consisted of a stem and a branch. The branch was found usually on the right side of the stem, and sometimes on the left, but with no phonetic significance. Therefore 3 would just be an alternative form of 1.

The following cirth were given by Tolkien as the most ancient of the later Angerthas. They had possibly different values at that time than the ones given below. Since we lack any other evidence though, we will use the known standard values of the letters to have a framework of discussion and make our comparisons; this is not so far-fetched as it seems: it's possible that at some later stage, some sound values were 'stuck' to some of the cirth, setting some stable basis for Daeron to make his final standardization.

If we are to accept the known values to these old Cirth, we will observe that they don’t cover all the sounds of Sindarin, since we are missing rh, lh, mh, v, y, œ. The most possible explanation is that those early Cirth were used for the “Old Sindarin” tongue, and many of the above mentioned sounds indeed didn’t exist in that language. However this doesn't explain the absence of sounds w and a. This indicates that some ancient, unknown cirth could have existed, but didn’t make it to the later systems and therefore aren't given by Tolkien; a fuller table therefore can't be reconstructed.

As for the vowel usage, perhaps the certh for u possibly was used for w (like in early latin orthography). The certh for a can’t be guessed, so maybe this sound was “meant” (like in some Quenya Tengwar Modes). More possibly it was one of the two cirth whose value can’t be determined, or it was one of some other cirth that did not survive till the later Angerthas.

Long vowels were evidently indicated by doubling (cf. the known certh for long o, n, is a simplified form of bb ).

 * Note: The term “Old Sindarin” is used hypothetically to facilitate understanding of Sindarin etymology, although we don’t know if it actually existed, and when. The term “Old Sindarin” is not a term used by Tolkien, but the term, as well as the language, are based on “Old Noldorin” as known by him.

Examples
As mentioned, it is probable that this primitive Certhas were used “Old Sindarin”, and we can try to see how some words could be written. The spelling exemplified here assumes that like in Latin, a single certh was used for w and u, and similarly for k, t and p for kh, th and ph. Since we can’t guess the form of a, we will consider that it was actually ommited.
 * g82Rb@, STBRON (*sthabron), “carpenter”
 * Sbbl, WÔI (*wôia), “envelope”
 * bReaa, ORKLL (*orkhalla), “superior”
 * ua52z, ÑLMBE (*ñalambe), “barbarous speech”
 * lSRl@z, IURINE (*yurine), “I run”
 * Sz9, UED (*weda), “bond”

Certhas Daeron
In the Valian Year 1350, Dairon (better known as Daeron), the Minstrel and Loremaster of Doriath, reorganised the cirth and added new ones, making the extension of the cirth known as Angerthas Daeron (“Long Runerow of Daeron”), used for inscribing names in Menegroth. The Dwarves working for Thingol liked them and adopted them, making them known also in the East, beyond the Mountains.

The nature and the timeframe of the standardization however are obscure; some point the similarities between q et 1 with 1 and 8 as signs that Daeron was influenced by the Tengwar, therefore this mustn't had occurred before the return of the Noldor, which means during the First Age. Unlike the previous system, the reversal of the certh had a phonemic significance: reversed cirth were softer versions of their originals. This also gives us another information: perhaps lenited consonants must have started to occur in Sindarin around that time.

Tolkien mentions that at that time (or maybe later) a sound of mh was needed. The most appropriate solution was to revert the certh for m to indicate its softening, but 5 (we assume it was this certh) couldn’t be reverted, so m was given to 6 (which until then had a value unknown to us), and 5 got the value of hw. The same process took place with r, l etc., and maybe at that time the distinct cirth for semivowels and umlauts, like w, y and œ, were employed.

Examples
There are no Angerthas Daeron texts by Tolkien either, so we cannot know how the text forms can look like. By some English specimina we see at least that words are separated by dots, phrases by colons and longer periods by 3 or 4 dots. We don’t know if Angerthas Daeron, like Tengwar, used other diacritics for modificators or combinations like nd, mb, dw, gw or diphthongs. It seems, however, quite straightforward, and for now we use them in close correspodence to the latin letters. The following examples attempt to show words as would be in the Age of the Starlight (Daeron’s time), so the first and last examples should be Gelydh and Elvellon in the 3rd Age.
 * c@@b@IluIumaG!, Annon-iñ-ñGœlydh, “Gate of the Noldor”
 * lItlR0I#l@, I-chirth hin, “these runes”
 * rSRz@I2x@Iz@@l, Guren bêd enni, “my heart tells me”
 * za7zaab@, Elmhellon, “Elf-friend”

Go to:

 * ../Foreword/
 * ../First Age/


text:
History of Elven Writing Systems/First Age

= Mode of Beleriand = When the Noldor came to Middle-earth, they were forbidden by King Elu Thingol to use Quenya and were forced to adopt Sindarin. They adapted Tengwar to their new language, taking advantage of their inherent flexibility to other sounds, imitating maybe the way the Teleri of Aman represented the Telerin sounds that didn’t exist in Quenya. For some obscure reasons we do not know, they found the most usual tehta-mode inappropriate for Sindarin, and they took therefore also example of the original Fëanorian Quanta-Sarme, using distinct tengwar for vowels.

The Mode of Beleriand seems to have been held “traditionally” by the Noldor who were established in Eregion during the 2nd Age, as seen on the Moria Gate Inscription written by Celebrimbor. After Eregion was destroyed in SA 1697, the Noldor migrated to Imladris, where the Mode of Beleriand was perhaps used even till the 3rd Age. The only Beleriandic texts attested are the Moria Gate Inscription and A Elbereth Gilthoniel, the hymn of Imladris. Many of the tengwar haven’t been attested in those texts, and it’s uncertain if they were used at all.

It seems that Sindarin speakers found use only for 3 of the 5 témar. Of the Quessetéma, only Wilya is attested, as a final -u (spelled -w by Tolkien, in tîw). There is also an a-tengwa, not corresponding with any of the older ones known from Quenya. We don’t know if it was a new invention or imported from a Quenya semivowel unknown to us, but more probably it is the a-letter from Fëanor’s Quanta-Sarme.

Since the vowels were separate letters, the carriers took vowel values too. The short carrier was for i, while in the King’s Letter, written in the later 'General Use with full writing', used in Arnor, we see the long carrier for the semiconsonantal initial sound y- (spelled i- by Tolkien, as in Ioreth). We don’t know if the latter was an Arnorian employment or was used even back in the original Beleriand Mode.

In the same text, we also find the w-tehta used over consonants as well for labialisation (edwen, which would be written here as l2èl6 ), since the Quessetéma was discarded. A tilde is used before stops for nasalisation, since Anto, Ampa etc. took different values.

Diphthongs were expressed by tehtar. Two overdots, maybe a remnant of the Tyelpetéma, used for -i in the diphthongs ai, ei and ui. Similarly for au (spelled -aw finally by Tolkien), we assume the w-tehta was used (caun, a]é6 ). ae is attested written with the separate letters for a and e, and maybe the same applies to the diphthong oe too. Another tehta was used to indicate long vowels, an acute accent called Andaith (á, ]R )

A well-known tehta that indicates long consonants, the under-tilde, wasn’t used. Long m and n were written with Malta and Númen (i.e., doubling of the lúva), while in the Moria Gate Inscription, other long consonants were written with two letters, so maybe this under-tilde wasn’t used earlier in Aman either, but is a later device.

In the King’s Letter, the letter of lenited m (mh) appears, which is a “nasal variant of v” or “spirant m”, but we don’t know its form in this mode.

Examples
The best known sample of the Mode of Beleriand is of course the Moria Gate Inscription, written by Celebrimbor of Eregion, a Noldorin place where this Mode was preserved.

- l5I6 2.7`6 ]7]6 yh7`] - ql2h yljjh6 ] y`5h - - `y 6]7r` 9]Ö6 ld]1p - aljlw7`wPh7 h l7ls`h6 1lÕ3]1p ` 3`n 9`6 -

Ennyn Durin Aran Moria. Pedo mellon a minno. Im Narvi hain echant. Celebrimbor o Eregion teithant i-thiw hin.

Tolkien has written the hymn of Imladris, A Elbereth Gilthoniel, in this mode. Imladris, inhabited by the refugees of Eregion, is one of the places that might have kept the Mode of Beleriand, even in the 3rd Age.

= Runes of Gondolin = This system was perhaps an invention of Pengolodh or other loremasters, and was employed obviously in Gondolin (or in Nevrast, at earliest).

Like the Tengwar and the Cirth, the forms of these runes show a relation between sound and shape. It is not known if the few similarities to the cirth are coincidental or not. Pengolodh, however, was not aware of the Cirth before he, with the survivors of destroyed Gondolin, migrated to the Mouths of Sirion.

It is not known if the values given by Tolkien (and presented here) are the original, or his own adaptation for writing English, Modern or Old. One reason against the former is that the sounds given are not found in the known elven languages of the First Age, but it may be that it was designed for notating a variety of languages. Glamdring and Orcrist, the famous swords, had probably inscriptions in that system, because Elrond (who it is stated to know of all types of runes) could read their inscriptions since he was born in Arvernien, while Gandalf was unable to.

The system of Gondolin was perhaps dropped out of use after its fall, but used for a while in Arvernien. It is mentioned that there Pengolodh was fascinated by the Certhas Daeron brought by the survivors of Doriath (perhaps it seemed to him a more perfected system), and adopted it for his works. They seem to have been obsoleted and forgotten by the Third Age, and this is supported by the abovementioned fact that only Elrond could read the swords’ inscriptions.

This system has appeared only in an article of Mythlore issue 69, by Paul Nolan Hyde, publishing an early concept of Tolkien. Its existence is not explicitly stated in the known later texts, but the above story about Glamdring is evidence that indeed a different kind of runes was used in Gondolin.

Examples
If we accept the values of the runes above, maybe these were the inscriptions of the famous swords of The Hobbit:
 * glamdriñ, Glamdring (Foe-hammer)
 * orkrist, Orcrist (Orc-cleaver)

Go to:

 * ../Age of Starlight/
 * ../Second Age/


text:
User talk:150.101.18.200

why did you edit beating season's author section?

I have no idea who the author is. However, if the guy whose name was put at the bottom is a real person and he had nothing to do with the article, then it's pretty unfair that his name was put there. If he isn't a real person, well, then it doesn't matter if I removed it. And if he really was the author, then he can go ahead and put his name back on it if he really wants to be associated with such rubbish. And if you're the author, well, go and put you're name back there - I won't remove it again.

title: User talk:150.101.18.200


text:
User talk:69.42.5.198

Please stop vandalizing pages. Thunderbolt16 06:32, 14 Jan 2005 (UTC)

title: User talk:69.42.5.198


text:
Cookbook:Allspice

Allspice, also called Jamaica pepper and sometimes pimento, is the unripe berry of the Pimienta dioica tree. It is dried and used as a seasoning in various cuisines. Its name comes from its flavor, which is reminiscent of many spices.

Characteristics
Allspice berries are small, round, and brown when dried—similar in appearance to peppercorns. Their flavor profile comes largely from eugenol, which give similarity to cloves, cinnamon, and nutmeg. Most of the flavor is in the seed husk.

Use
Allspice is the primary spice in Jamaican jerk spice. It goes well with other spices containing eugenol (cinnamon and nutmeg), cineole (cardamom), phellandrene (pepper and star anise), and linalool (coriander).

title: Cookbook:Allspice


text:
Cookbook:Grand Union Bacon

| Breakfast

Ingredients

 * 1 egg
 * 3 drops Tabasco sauce
 * Bacon strips (very thin and lean)
 * Very fine cracker crumbs or dust
 * Butter

Procedure

 * 1) Beat the egg with the Tabasco sauce.
 * 2) Dip bacon in the egg mixture, and roll in cracker dust.
 * 3) Add butter to a frying pan over medium heat. When pan is well heated, add the bacon. Fry until golden brown.
 * 4) Flip bacon over, cook the other side, and serve on a napkin.

title: Cookbook:Grand Union Bacon


text:
Cookbook:Durian

Durian is a green, spiny fruit from Southeast Asia.

Characteristics
The fruit of the durian is large (5–10 lbs) and ovoid, with a hard and spiky yellow-green exterior. The inside of the fruit contains multiple fleshy, yellow segments with single seeds. This flesh can be very soft and smooth in texture or fibrous, depending on the variety.   However, the most famous property of the durian is its smell, which is extremely pungent and compared to various odors like skunk, cheese, onion, or rotting.

The durian falls off the tree once ripe, and it continues to ripen further for a few days afterwards, growing more intense in smell as it does. It may also undergo slight fermentation during this time. Once opened and exposed to the air, the flesh will begin to degrade.

Selection and storage
In Southeast Asia, durian is widely available fresh. A few recommendations are given for evaluation of a durian's ripeness. One is to knock on the fruit and select those with a hollow sound, while another is to examine the rind and see if it has started to crack—this is cited as a sign of ripeness. The stem should look solid and not overly dried, which would indicate lack of freshness. In general, the durian will become overripe by 1 week after falling from the tree. The aroma of durian becomes more pronounced with increasing ripeness, and different individuals may prefer the fruit at different stages of ripening. Once opened, a durian should be eaten quickly.

Durians can sometimes be found in general supermarkets in Western countries, frozen and thickly wrapped in plastic.

Preparation
A durian is opened by splitting it along natural sections. You might be able to see them on the outside as places where the spines run parallel. A durian can be forced open with the hands. Though not needed, a sturdy knife can be helpful to get things started.

Use
Durian fruit is used to flavour a wide variety of sweet edibles such as traditional Malay candy, ice kachang, rose biscuits, cakes, and, with a touch of modern innovation, ice cream, milkshakes, mooncakes and even cappuccino. It can also be incorporated into pancakes, jams, and custard. Pulut durian is glutinous rice steamed with coconut milk and served with ripened durian. In Sabah, red durian (D. dulcis) is fried with onions and chilli and served as a side dish. Tempoyak refers to fermented durian, usually made from lower quality durian that is unsuitable for direct consumption. Tempoyak can be eaten either cooked or uncooked, is normally eaten with rice, and can also be used for making curry. Sambal tempoyak is a Sumatran dish made from the fermented durian fruit, coconut milk, and a collection of spicy ingredients known as sambal.

title: Cookbook:Durian


text:
Cookbook:Sriracha

| Sauces

Sriracha is a sweet hot sauce made from red chiles and garlic that is popular in Asia and the Southern United States. It has the consistency of ketchup. It is often eaten on pasta, hamburgers, and hot dogs.

Ingredients

 * 1/2 pound red Thai chiles, destemmed
 * 1/3 cup malt vinegar
 * 3 tbsp minced garlic

Procedure

 * 1) Combine all ingredients in a food processor and pulse until desired consistency. Refrigerated in a squirt bottle, this will last well, forever.

title: Cookbook:Sriracha


text:
Miwok (Central Sierra)

Central Sierra Miwok is a nearly extinct Native American language of central California, closely related to the other Miwok languages (spoken from Marin to Yosemite) and ultimately a member of the widespread Penutian family of the west coast of North America.

Lesson 1
Traditionally, Central Sierra Miwok was not a written language; however, it has been written by linguists using phonological notation and a few special symbols.

It has 6 vowels:
 * a, e, i, o, u are all pronounced as in Spanish - that is, ah, eh, ee, oh, oo
 * ï (usually written y by linguists) is a sound not found in English, halfway between the vowels in the English words "book" and "mitt". It sounds like Turkish ı or Russian ы.

Most of its consonants occur in English:
 * ch (written č by linguists), h, k, l, m, n, ng (written ŋ by linguists), p, s, sh (written š by linguists), w, y (written j by linguists)

but a couple don't:
 * In English there is only one t sound. In Miwok there are two: an "alveolar" t, like English t (written ṭ by linguists) and a "dental" t, like Spanish or Italian t (written t by linguists).  Since the "dental" t sounds closer to English th, and there is no th sound in Miwok, it will be written "th" here.
 * ^ (written ˀ by linguists) is called a glottal stop - it effectively means you don't combine the vowel before it together with the vowel after it, but stop between them instead.

If a t plus an h or an s plus an h is intended, instead of a th or sh sound, we will write s'h, t'h to remove ambiguity.

Both vowels and consonants can be doubled, like in Finnish; you pronounce aa longer than a, and tt longer than t.

Lesson 2
Let's start with a few simple nouns:

 * person: miwwï
 * acorn-bread: ïlee
 * acorn soup: nïppa

and verbs:

 * say: kachchï
 * eat: ïwwï

English makes a difference between "I" and "me", or "he" and "him": you say "he" if he is the one doing something (subject case), and "him" if something is being done to him (object case). In Miwok, you have to make this distinction for all nouns: you add -^ at the end of the subject, and -y at the end of the object. If you did this in English, you might say: "I eat nïppay", but "The nïppa^ spilled", for instance.

The order of words is different from English: instead of saying "man bites dog", you would normally say "man dog bites".

 * The person eats acorn-bread: miwwï^ ïleey ïwwï
 * The person eats acorn soup: miwwï^ nïppay ïwwï
 * The person says "ah": miwwï^ "aa" kachchï

title: Miwok (Central Sierra)


text:
Radiation Oncology/Chemotherapy

This is a brief listing of chemotherapy drugs that may be useful for the radiation oncologist to know. It is not to be an in depth discussion of how these drugs work, but it may touch on their basic type of action (i.e. nucleoside analogues).

PharmGKB

Chemotherapy combinations

Nitrogen mustard analogues

 * Cyclophosphamide
 * Chlorambucil
 * Melphalan
 * Chlormethine
 * Ifosfamide
 * Trofosfamide
 * Prednimustine

Alkyl sulfonates

 * Busulfan
 * Treosulfan
 * Mannosulfan

Ethylene imines

 * Thiotepa
 * Triaziquone
 * Carboquone

Nitrosoureas

 * Carmustine
 * Lomustine
 * Semustine
 * Streptozocin
 * Fotemustine
 * Nimustine
 * Ranimustine

Epoxides

 * Etoglucid

Other alkylating agents

 * Mitobronitol
 * Pipobroman
 * Temozolomide
 * Dacarbazine

Folic acid analogues

 * Methotrexate
 * Raltitrexed
 * pemetrexed (Alimta)
 * Multitarget agent, inhibits several folate-dependent enzymes.
 * Indication:pleural mesothelioma (combined with cisplatin), second line NSCLC

Purine analogues

 * Mercaptopurine
 * Tioguanine
 * Cladribine
 * Fludarabine
 * Clofarabine

Pyrimidine analogues

 * Cytarabine
 * fluorouracil (generic 5-FU, Adrucil, Carac, Efudex, Fluoroplex, Fluorouracil)
 * Pyrimidine analogue. Prodrug. Requires activation by thymidine phosphorylase (TP) to yield 5-FUdR then by thymidine kinase (TK) to form the active product to fluorodeoxyuridine monophosphate (FdUMP). 5-FdUMP forms a stable complex with thymidylate synthase resulting in disruption of DNA synthesis. Also incorporated into RNA and causes RNA disruption.
 * Toxicity: myelosuppression, N/V, stomatitis, diarrhea, hand-foot syndrome. Coronary vasospasm

 * Tegafur
 * Carmofur
 * Gemcitabine

 * capecitabine (Xeloda)
 * Oral. Mimics continuous infusion of 5-FU. Prodrug. Undergoes transformation in live by carboxylesterase then cytidine deaminase then thymidine phosphorylase (TP) which converts it to 5-FU.
 * Toxicity: Compared to 5-FU, lower diarrhea, stomatitis, N/V, neutropenia; more hand-foot syndrome and hyperbilirubinemia.
 * Leucovorin (Enhancer)
 * Supplements intracellular folate supply, resulting in inhibition of thymidylate synthesis (TS)

Anthracyclines

 * Antitumor antibiotics, produced by Streptomyces soil fungus
 * Mechanism: Intercalate between DNA base pairs and prevent DNA replication
 * Toxicity: cardiac (arrhythmias, CHF)

 * doxorubicin (Adriamycin, Rubex)
 * Indications: ALL, AML, CLL, breast CA, gastric CA, SCLC, NSCLC, epithelial and germ cell ovarian CA, thyroid CA, neuroblastoma, Wilms' tumor, transitional bladder cell CA, cervical CA, endometrial CA, squamous cell carcinoma of the head and neck, primary hepatocellular CA, pancreatic carcinoma, hepatoblastoma, thymoma, gestational trophoblastic tumors, prostate CA, Hodgkin's disease, NHL, sarcoma, multiple myeloma, adrenocortical CA, carcinoid tumors, advanced esophageal CA, retinoblastoma
 * daunorubicin (Cerubidine)
 * Indications: ALL, AML, CML, Wilm's tumor, neuroblastoma, NHL
 * epirubicin (Ellence, Pharmorubicin)
 * Indications: node+positive breast CA, metastatic breast CA, esophageal/GEJ CA, locally unresectable and metastatic gastrica CA, advanced NSCLC, limited and extensive stage SCLC, Stage III-IV ovarian CA, Hodgkin's disease, NHL, soft-tissue sarcoma
 * idarubicin (Idamycin)
 * Indications: adult AML
 * mitoxantrone (Novantrone, generic)
 * Indications: hormone-refractory prostate CA, locally advanced and metastatic breast CA, adult AML, recurrent adult ALL, NHL. Also multiple sclerosis

Other Antibiotics

 * '''mitomycin-C (Mitomycin; Mutamycin)
 * Mechanism: cross-links DNA
 * Indications: gastric CA, esophageal CA, pancreatic CA, biliary CA, colorectal CA, anal CA, breast CA, H&N CA, NSCLC, cervical CA, bladder CA, CML
 * Toxicity: delayed bone marrow suppression, pulmonary fibrosis

 * '''bleomycin (Blenoxane)
 * Mechanism: unknown but may involve binding to DNA, inducing lability of the DNA structure, and reduced synthesis of DNA
 * Indications: Squamous H&N CA, esophageal CA, thyroid CA, cervical CA, penile CA, vulvar CA, testicular CA, HL, NHL, Kaposi's sarcoma, osteosarcoma, malignant pleural/pericardial/peritoneal effusion, melanoma, ovarian CA, gestational trophoblastic tumors, mycosis fungoides, verruca vulgaris

 * plicamycin (Mithracin)
 * Mechanism: complexes with DNA in the presence of divalent cations, thus preventing synthesis
 * Indications: testicular CA
 * Other indications: hypercalcemia and hypercalciuria associated with neoplasm, Paget's disease

Vinca alkaloids

 * Vinblastine
 * Vincristine
 * Vindesine
 * Vinorelbine

Podophyllotoxin derivatives

 * Etoposide
 * Teniposide

Colchicine derivatives

 * Demecolcine

Taxanes

 * Paclitaxel (Taxol)
 * Abraxane (ABI-007) - albumin-bound nanoparticle paclitaxel. Possibly less neurotoxicity.
 * Docetaxel (Taxotere)

Other

 * Trabectedin

Platinum drugs
Cross-link DNA, block transcription and replication

 * Cisplatin (IV)
 * Toxicity: Ototoxicity
 * Carboplatin (IV)

 * Oxaliplatin (IV)
 * Toxicity: Peripheral neuropathy. no nephrotoxicty. Moderate hematologic toxicity

Topoisomerase I inhibitors

 * irinotecan (Camptosar)
 * Derivative of natural alkaloid camptothecin.
 * Indications: metastatic CRC
 * Toxicity: delayed diarrhea, myelosuppression.

 * topotecan (Hycamtin)
 * Indications: metastatic ovarian CA, SCLC, NSCLC, myelodysplastic syndrome, CML

Monoclonal Antibodies

 * Edrecolomab
 * Rituximab
 * Trastuzumab
 * alemtuzumab (Campath)
 * Indications: B-CLL, second line
 * Gemtuzumab
 * cetuximab (Erbitux) (IV)
 * Anti-EGFR (HER-1, c-ERB-1)
 * Toxicty: acneiform rash (face and trunk). Should limit sun exposure.

 * bevacizumab (Avastin)
 * Binds and neutralizes VEGF

 * pertuzumab, 2C4, (Omnitarg)
 * HER2 dimerization inhibitor
 * Use in prostate cancer

 * panitumumab (Vectibix)
 * Fully human Anti-EGFR (IV)
 * Colon ca.

Small molecule agents

 * Bortezomib (Velcade) - inhibits proteasome / ubiquitin pathway. Inhibits NFKB (nuclear factor κ-B), several cytokines, VEGF, fibroblast growth factor
 * Multiple myeloma
 * Thalidomide - immunomodulator.
 * Multiple myeloma
 * Lenalidomide - analog of thalidomide
 * Multiple myeloma
 * Imatinib (Gleevec), STI-571 - tyrosine kinase inhibitor of ABL, BCR-ABL, KIT, PDGF receptor. Targets ABL tyrosine kinase which is activated by BCR-ABL translocation (i.e. Philadelphia chromosome).
 * CML (BCR-ABL), GIST (KIT/c-kit), Dermatofibrosarcoma protuberans (PDGF)
 * Gefitinib (Iressa) - inhibits tyrosine kinase domain of EGFR
 * non-small cell lung cancer
 * FDA approved for: single drug therapy for refractory NSCLC
 * Sunitinib (Sutent) - anti-angiogenesis
 * Renal cell carcinoma
 * Temsirolimus (CCI-779) - m-TOR inhibitor
 * Renal cell carcinoma
 * Lapatinib (Tykerb) - EGFR tyrosine kinase inhibitor
 * Renal cell carcinoma, her-2-neu positive breast cancer
 * Sorafenib (Nexavar) - anti-angiogenesis. Inhibits VEGF, Ras kinase, and PDGF.
 * Dasatinib
 * CML

title: Radiation Oncology/Chemotherapy


text:
Radiation Oncology/Cancer biology

 * Please see Radiobiology

title: Radiation Oncology/Cancer biology


text:
Subject talk:Library and information science

Plans?
Well, this is a new one on me. I had never heard of Wiki Books or the Wikiversity, and here's an entry for LIS. What ideas do you have for this page? Do you intend to offer a lot of info? Where is all of this going? I'm a young librarian with a passing interest in the wiki and just happened by here.

I'll check back and see who's around later. Good luck!

LIS program
I started the LIS program because I realized that much of what I learned in my MLIS program could be done at my own pace at home. I'm hoping to pass on much of what I payed my hard-earned tuition for, so that others can perhaps learn some of this on their own. The program is loosely structured on the LIS program I attended. As time goes on, I hope to slowly develop each of the "classes."

I of course welcome any additions that anyone can offer.Clifflandis 23:48, 19 Jan 2005 (UTC)

Wiki Research Skills??
I'm teaching electronic media and research skills to high school freshman, and this seems like a really good place to develop a basic primer for such a course. My course covers internet beginnings and history, seach tools, surface web and deep web as resources, information evaluation, and basic library research skills. I'm interested in adding sections on blogging and the wiki-world of information, too.

But here's the thing: These are amazing new ways of constructinig information - but I wonder about how they will develop. It seems it will be increasingly important and necessary to find ways to contextualize these forms of information, and that that needs to be taught to people, too. The wiki-world and the blogosphere need to be understood to be in relation to other more traditional forms of information. In fact, a great part of their value lies in just that fact that they are so free. But, that does not make them necessarily better, more correct, more reliable, less biased, less corrupted than other forms of information. The freedom has value - and that requires a certain acceptance of responsibility on our parts. For young people, most people, really, all "information" is equal. THey jump into a see of words and accept it all. !here is no concern, much less understanding that there IS a context in which we are living, giving, receiving this information, and that that context has meaning, too.

At any rate, getting back to the course, it seems that media skills modules that address some of these aspects of information organization, evaluation, retrieval, and meaning making, could be a great wiki-library tool, useful for all kinds of learners.

What do you all think?

Is this school still active?
Hi there,

I'm new to the WikiWorld and only came across WikiVersity on Friday (25/11). I got all excited and thought I'd build myself a LIS School only to find that this one was already here.

Only thing is that there isn't a lot of content here and there hasn't been much activity recently either. This has got me wondering if the school is still active.

I'd really like to be involved in moving the school forward - It's just I dont want to offend anyone by doing too much and being accused of taking over or worse things

Is the school still being worked on?

Thanks

--Woo 14:58, 27 November 2005 (UTC)

Move from Wikiversity to Wikibooks
This page seems to be a Wikibook, not a school of Wikiversity. I suggest moving the six blue links here to a bookshelf, or merging them into one book. That would fix the present naming-convention problem. --Kernigh 17:23, 1 February 2006 (UTC)

Removed Redirect
Starting an actual wikiversity school at Wikiversity:School:Library and information science.


text:
Cookbook:Sashimi

| Cuisine of Japan

Sashimi is raw meat, sliced very thin. It is typically served with onigiri or sushi. Although the meat used is usually a kind of fish, beef can also be used.

Ingredients

 * Fresh fish fillet (e.g. salmon, tuna, etc.)

Procedure

 * 1) Slice fish as thinly as possible across the grain to keep it tender, like you would a steak.

Notes, tips, and variations

 * Since the fish is raw, it is important that it be as fresh as possible.
 * Some people avoid freshwater fish (e.g. freshwater eel, salmon) entirely for sashimi, because they may contain parasites that do not live in saltwater.
 * Eel's blood contains a toxin, and eel needs to be cooked to break down the toxin.

title: Cookbook:Sashimi


text:
Cookbook:Tamarind

| Fruit

Tamarind is the flat, brown pods of a tree (Tamarindus indica). The bittersweet pulp within these pods is used in Asian and Latin American cuisine.

id:Resep:Asam jawa

title: Cookbook:Tamarind


text:
MediaWiki talk:Sitestatstext

do we have the page views and edits swapped? It seems odd that there'd be more edits than views. Gentgeen 23:50, 14 Jan 2005 (UTC)

title: MediaWiki talk:Sitestatstext


text:
Online OsiriX Documentation/OsiriX Developer Overview

 * ^ >

OsiriX is developed in collaboration by a core group of developers headed by Antoine Rosset. To allow collaborative development the current source code is stored on a remote server at the sourceforge site. Getting the code and merging changes is handled by the SVN version management system.

In order to build your own copy of OsiriX you must have Apple's developer tools (Xcode) v 3.1. For best results use the latest version of Xcode. Currently (July 2008) Xcode v 3.1 is only available as part of the iPhone SDK. It can be downloaded from http://developer.apple.com/iphone/program/. It is available for free though you will have to set up an account.

The next two sections describe how to get the source code and compile it once you have it.

OsiriX オンライン解説文書/OsiriXディベロッパーの概要


text:
User talk:Jdl32579~enwikibooks

Hey, I'm also working on the Writing pages. I've applied for an MFA at Minnesota (small world). Please let me know if I've done too much or over-stepped my bounds or anything like that --Atrivedi 01:30, 15 Jan 2005 (UTC).

Your account will be renamed
Hello,

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

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

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

Sorry for the inconvenience.

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

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

title: User talk:Jdl32579~enwikibooks


text:
Online OsiriX Documentation/OsiriX Anonymous and Developer SVN access

< | ^ | >

In order to check out (fetch an initial copy) of the OsiriX source code, you need to have Subversion installed.

Anonymous Access
Anonymous access is simple if you don't plan to submit any changes to the project. Open up Terminal. cd to a root directory to check out your code. Mine is /Users/spalte. Then type: svn co https://osirix.svn.sourceforge.net/svnroot/osirix osirix

This will then chunder for a while and you will end up with a directory called osirix containing the source ie for my setup /Users/spalte/osirix. Now you are ready to build the project.

When the download is complete open the project in x-code, then select the unzip binaries target and build this and then build the development target.

OsiriX オンライン解説文書/OsiriXディベロッパー_開発者及び匿名ユーザのSVNによるアクセス


text:
Online OsiriX Documentation/Building OsiriX

< | ^

Now that you have the source code you are ready to build.

1) Open osiriX.xcodeproj

2) Choose '"Unzip Binaries" as the active target and then click Build.

3) Choose "Development" as the active target and then click Build.

You should now have an application that runs. Before you run though if you already have a version of OsiriX installed on your system, BACKUP your OsiriX user data folder since this app will use the same version and there could be conflicts.

OsiriX オンライン解説文書/OsiriXディベロッパー_OsiriXをビルドする


text:
Online OsiriX Documentation/Using getosirixCVS.pl

< | ^

I have written (or more accurately pinched from the bibdesk website) a perl script to get the osirix source code called getosirixCVS.pl. Download this onto your machine. it is probably easiest to save it in your development directory. Mine is /Users/jefferis/dev. Go to the Terminal and run as follows:

gjg5:~/dev jefferis$ perl getosirixCVS.pl

Answer the questions and you will get a response that looks like this if you are using anonymous cvs ******************************* Welcome to osirix development. This script will get the stuff you need from cvs to build osirix. Developers should set SF_USERNAME to use ssh access Are you a developer using ssh access (y/n)? "n" cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/osirix login Password is empty--just hit return when asked for a password Executing: cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/osirix login (Logging in to anonymous@cvs.sourceforge.net) CVS password: "Press return" Do you want a specific tag? (empty for none or enter tag(eg TRY_RTF_041503) "Press return" Executing: cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/osirix co  osirix cvs checkout: Updating osirix U osirix/AdvancedQuerySubview.h U osirix/AdvancedQuerySubview.m U osirix/Analyze.h ...  U osirix/pixelmed/DICOMPersonNameAttribute.xcode/lpysher.pbxuser  U osirix/pixelmed/DICOMPersonNameAttribute.xcode/project.pbxproj **************************** getosirixCVS done.You will have to expand zip files as follows:  find osirix -iname "*.zip" -execdir unzip {} ";" After that open osirix/OsiriX.pbproj/ and commence the build. 1) compile DCM.framework target FIRST. This will create the OsiriX.framework for OsiriXBurner application 2) compile 'OsirixBurner.xcode' file 3) compile all the PreferencePanes projects located in the 'Preference Panes' folder 4) compile 'Osirix.pbproj' file with OsiriX target

or like this if you are using Developer access:

******************************* Welcome to osirix development. This script will get the stuff you need from cvs to build osirix. Developers should set SF_USERNAME to use ssh access Are you a developer using ssh access (y/n)? y What is your sourceforge username (setenv SF_USERNAME for a default)? jefferis Do you want a specific tag? (empty for none or enter tag(eg TRY_RTF_041503) "Press return for HEAD" Executing: cvs -z3 -d:ext:jefferis@cvs.sourceforge.net:/cvsroot/osirix co osirix The authenticity of host 'cvs.sourceforge.net (66.35.250.207)' can't be established.  DSA key fingerprint is 02:ab:7c:aa:49:ed:0b:a8:50:13:10:c2:3e:92:0f:42. Are you sure you want to continue connecting (yes/no)? yes  Warning: Permanently added 'cvs.sourceforge.net,66.35.250.207' (DSA) to the list of known hosts. jefferis@cvs.sourceforge.net's password: cvs checkout: Updating osirix U osirix/AdvancedQuerySubview.h U osirix/AdvancedQuerySubview.m ...

And voila!

Here is the perl script. Save as getosirixCVS.pl. If you have the choice, make sure that you use Unix line terminations otherwise perl will complain.:

# print "\n*******************************\n"; print "Welcome to osirix development.\n"; print "This script will get the stuff you need from cvs to build osirix.\n"; print "Developers should set SF_USERNAME to use ssh access\n"; $SFNAME=getSFName; if ($SFNAME ne "") { prepdev; } else { prepanon; } $bibtag=gettag; getsources; print "\n****************************\n"; print "getosirixCVS done."; print "You will have to expand zip files as follows:\n"; print "find osirix -iname \"*.zip\" -execdir unzip {} \";\"\n"; print "After that open osirix/OsiriX.pbproj/ and commence the build.\n"; print << "EOF"; 1) compile DCM.framework target FIRST. This will create the OsiriX.framework for OsiriXBurner application 2) compile 'OsirixBurner.xcode' file 3) compile all the PreferencePanes projects located in the 'Preference Panes' folder 4) compile 'Osirix.pbproj' file with OsiriX target EOF sub getSFName { if (defined $ENV{'SF_USERNAME'} ) { return $ENV{'SF_USERNAME'}; } else { print "Are you a developer using ssh access (y/n)? "; $DEV = ; if ( $DEV =~ /^n/ ) { return ""; } else { print "What is your sourceforge username (setenv SF_USERNAME for a default)? "; $SFNAME = ; chomp($SFNAME); return $SFNAME; }  } } sub gettag { if (defined $ENV{'SF_BIB_TAG'} ) { $bibtag = $ENV{'SF_BIB_TAG'}; } else { print "Do you want a specific tag? (empty for none or enter tag(eg TRY_RTF_041503) ";   $bibtag = ;  }  chomp($bibtag);  if ($bibtag eq "") {    return $bibtag;  } else {    return "-r $bibtag";  } } sub prepanon {   $CVS_METHOD = "pserver";   $SFNAME = "anonymous";   $LOGIN = "cvs -z3 -d:$CVS_METHOD:$SFNAME\@cvs.sourceforge.net:/cvsroot/osirix login";   print "$LOGIN\n";   print "\nPassword is empty--just hit return when asked for a password\n";   tryGet($LOGIN); } sub prepdev {   $ENV{'CVS_RSH'} = 'ssh';   $CVS_METHOD = "ext"; } sub getsources {    $GETMAIN = "cvs -z3 -d:$CVS_METHOD:$SFNAME\@cvs.sourceforge.net:/cvsroot/osirix co $bibtag osirix";    tryGet($GETMAIN);    # not relevant for osirix    #$GETVENDOR = "cvs -z3 -d:$CVS_METHOD:$SFNAME\@cvs.sourceforge.net:/cvsroot/osirix co osirix_vendorsrc";    #tryGet($GETVENDOR); } sub tryGet {   $toGet = shift;   print "Executing: $toGet\n"; if ( (system $toGet) != 0) { #return of 0 indicates success print "cvs failed. Check messages above. Should I try again? (y/n)?"; undef $tryAgain; $tryAgain = ; if ($tryAgain =~ /^y/) { getsources; } else { print "cvs failed. Please read messages above and"; print " try again in a few moments\n"; exit; }  }  }
 * 1) !/usr/bin/perl -w
 * 1) This script was written for fetching the BibDesk CVS tree
 * 2) I basically just did a search and replace for osirix
 * 3) Greg Jefferis 21 May 2004
 * 1) Set the BIB tag

--Jefferis 02:17, 15 Jan 2005 (UTC)

OsiriX オンライン解説文書/OsiriXディベロッパー_getosirixCVS.plを利用する


text:
Talk:Graphic Design/Principles of Design

It should have some examples for us to understand. Aww bith...


text:
Talk:General Relativity/Coordinate systems and the comma derivative

"Now, we change coordinate systems via the Jacobian.." Please continue, I can't tell what you're saying. 67.118.118.183 04:34, 15 Jan 2005 (UTC)

Huh? Isn't the comma derivative the tensor quantity that is the normal partial derivative adjusted by a sum over the Christoffel symbols? If the Christoffel symbols are zero, as they are in a flat space, the covariant derivative is the same as the normal derivative, but in general this is not the case. Or am I missing something?

The tensor quantity that you're talking about is the covariant derivative and it's written as X;c - Itzamna 2 Feb 2009


text:
Cookbook:Rice Vinegar

Created from fermented rice, rice vinegar has a softer and milder than normal white vinegar.

title: Cookbook:Rice Vinegar


text:
Cascading Style Sheets/Defining Style Rules

You associate formatting instructions with a web page by defining CSS rules (whether in separate files, embedded, or inline see ../Applying CSS to HTML and XHTML/)

Syntax
Each rule has two parts: a selector and a group of one or more declarations surrounded by braces (curly brackets):

 * selector { declaration; declaration2; ...}

Each declaration is formed like this:

 * property: value

Remember that there can be several declarations in one rule. A common mistake is to mix up colons, which separate the property and value of a declaration, and semicolons, which separate declarations. A selector chooses the elements for which the rule applies and the declaration sets the value for the different properties of the elements that are chosen.

The property is one of many properties. w3.org has a list of all of the CSS Properties.

Basic Uses
Here is an example of how you would make all  elements appear bold:

The  declaration has the property   and the value   which makes the font bold.

That would appear like this:

A slightly more complex example is

That would appear like this:

You can use many other properties, and values, but this is just a beginning as to how to use CSS.


text:
Bambara

Bambara, or Bamanakan in the language itself, is a language in West Africa, mostly in Mali, where it is mother tongue of the Bambara people (30% of the population), and where 80% of the population can communicate in the language. Bambara will also be useful in Burkina Faso, Côte d'Ivoire, and Gambia. Together with Jula (French spelling Dioula), Malinké, and Mandingo, it belongs to the Mandekan family of more or less mutually comprehensible languages, which itself part of the Mande group, which is a Niger-Congo language subgroup. The bambaran tribe were mostly Muslim.

It is a Subject Object Verb language and it is a tonal language with two tones. It uses seven vowels a, e, ɛ, i, o, ɔ and u (a like in car, e like in echo, ɛ similar to the second e in echelon but more open, i like in India, o like in for, ɔ like the final sound in gnaw, and u like in the name Honolulu).

History, influences
In the past and present Bambara has strongly been influenced by French. Any knowledge of French is of great use when learning Bambara. And during your first attempts of actually speaking the language you can try to use French words if you don't yet know the Bambara word for something.

Sound
It is a tonal language, with two different tones, high and low. Within a word the tone can only be rising.

Grammar
Like Turkish and Japanese, it is an agglutinative language, meaning that morphemes are glued together to form a word.

The basic sentence structure is Subject Object Verb. Take the phrase, "n t'a don" (I don't know [it]). "n" is the subject (me), "a" is the object (it), and "[ka] don" is the verb ([to] know). The "t'" is from the present tense marker "té." "té" is the negative present tense marker and "bé" is the affirmative present tense marker. Therefore, "n b'a don" would mean "I know it".

Contents

 * Verbs
 * Vocabulary

Particles
There are no definite particle in Bambara.

Gender
Gender can explicitly be expressed by using the suffixes -muso for feminine and -kè for masculine. For instance

 * jakuma
 * cat

 * den
 * child

Questions
In Bambara there are three different ways for turning a sentence into a question. The first is simply using a question mark, or a change of expression, of tone, which is common in French, and the other two are like Japanese and Chinese where an interrogative particle is used to indicate that the sentence is a question:

 * 1) .. wa?  - at the end of a sentence
 * 2) ¿yali .. - at the beginning of a sentence

Interrogatives

 * min? (at the end of the sentence)
 * where?

 * mun .. ?
 * what?

 * munna .. ?
 * why

 * jon .. ?
 * who?

Plural
The plural is indicated with a w at the end of a word, and uu for words ending in u.

 * musow
 * women

Pronouns

 * ne : me, I, my, mine
 * i : you, your, yours
 * a : he, she, him, her, his, hers, it
 * aw : you, your, yours (plural)
 * an : us, our, ours
 * u, alou : they, their, theirs

Note that Bambara doesn't have a special possessive pronoun. Possession is formed using the ka particle, e.g. ne ka mobili - my car.

title: Bambara


text:
History of Elven Writing Systems/Second Age

= Quenya Mode = Some changes occurred in Noldorin phonology, already in Valinor, that differentiated it from the dialect of the Vanyar: th merged with s, initial ch with h and maybe later, but still before the Exile, z with r. Those changes were inherited to Exilic Quenya which slowly evolved further.

There is not much known about the slow elvish evolution in 2nd Age, but certainly the sages of Númenor, as well as Elven sages of middle-Earth, were using the Quenya Tengwar and applied some changes and simplifications to them. It is not known when exactly those changes that brought us to the final form of the table in Appendix E took place, but if we consider some changes as “early” or “late”, we could attribute some intermediate stages to the 2nd Age. It still must be noted that some changes described here could not had happened then, but later.

Aldwin Lowdham wrote some Numenorian names with tengwar and Lisa Star believes this writing represents a Numenorean mode. This mode reminds of Sanskrit: since a was very frequent, its sign was sometimes left out, and the sound was just meant, giving the script therefore an abugida flavour. An unutixë (underdot), which in this case was called Putta, was used to indicate that a consonant is not followed by any vowel (Minyatur, t%5Ô1Y6Ê ).

Examples
Concerning the mode of Númenor, this is how Elendil’s Oath can be transcribed

- `V1 `V`7Rj°^ `V2^7R5: `M1~Mj%`V5È = 8`B5^t$ t7Uy5È `6 dTm%5Ô6 1R5: `w6 t$1; --

''Et Eärello Endorenna utúlien. Sinomë maruvan ar Hildinyar tenn' Ambar metta.''

And other words. Please pay attention to their etymology:

3f92^ 	Sangahyando < *Thangahyando (‘Throng-cleaver’, a name)

`V,Fj^°d6 	*Erellochar < Ezellochar (Green Mound in Valinor)

9FjLn 	Helwa < HEL (pale blue)

d^q8Ê 	Hopas < *Chopasse (harbour)

=General Use mode= The Noldor founded Eregion in the year 750 of the Second Age. When this civilization reached its peak, it was already a cultural and financial crossroad of races: Noldor, Sindar, Dwarves and Men, Dúnedain or other.

In The Howlett Rivendell Inscriptions, Tolkien affirms that there was a "general use (applicable to both S[indarin] and Q[uenya])" around the end of the Third Age but there is some evidence that the same or similar concept must have been employed back to the Eregion times: The Third Age "general use" shown by Tolkien is consistent to the Second Age the Ring-inscription, which, Isildur says, is "fashioned in an elven-script of Eregion" ; this mode bore many similarities to the actual theoretical and unused values of the Tengwar.

A similar system is also used for the few late Second Age Adûnaic words in Edwin Lowdham's Manuscript, Text I, we may tentatively assume that the "general use" is of Númenorian influences.

The origins of the General Use Mode are unclear; we can assume that it originated in Eregion that could satisfy the needs of non-Elvish languages and facilitate writing and communication in those multicultural circumstances; out of this contact Sauron could have inscribed the Ring. But it is also possible that this Mode originated in Númenor and spread with the use of Westron.

Since the Ring Inscription is the only Second Age source for this, and because the "General Use" is mentioned mostly in context to the Third Age, please see the relevant section

= Angerthas Daeron = Similar to the "General Use" modes, the Cirth also saw universal usage. The Gelydh (Noldor) made use of the cirth and made a name for them in Quenya, Certar. They even extended the Certhas and added several cirth. The adding of 2 whole new rows was attributed to the Ghelydh (CH-row and QU-row). It was considered an extention of Certhas Daeron, so it was named Angerthas Daeron (''and+certhas=long runerow).

Tolkien is not clear about when the name 'Angerthas Daeron' was used. An Introduction to Elvish interprets Tolkien as if the Angerthas was an earlier invention, while the authors use the custom name 'Angerthas Eregion' to refer to the system of the Second Age explained below.

Whatever this system was called, we see the innovations concerning the employment of the two new CH and QU-series, a new certh for h to replace the previous certh # which became ch. This certh was preferred for ch because its shape seemed to be between the shapes of the T and K cirth (8 T + e K > # CH), to represent how the ch sound also (phonologically) exist between t and c. There was also a new certh for nd, which as Tolkien notes, its form wasn’t much related to the dental cirth.

Some of the new letters were used for sounds of Quenya (and other tongues) not found in Sindarin. In that stage, the Angerthas reached its fullest extent, but for most forms of writing other than carving, the Tengwar were used.

Examples
The Angerthas was convenient for Quenya and alien languages, probably Mannish, and maybe the ancestor of the Common Speech. We can see how some archaic Mannish words that maybe were current, can be written.

9Dec@ 	Dûkan (Roh. dweller)

ecf8S 	Kastu (treasure)

Rnrl@ 	Rógin (Woses)

8Rc.ca9 	Trahald (Nor. Mannish: burrowing)

= Angerthas Moria = During the 2nd Age, or maybe its beginning, the Dwarves got accustomed with Angerthas of the Noldor and they modified it to suit Khuzdul, their language. This alphabet was spread further wherever the Dwarves went, hence the name Angerthas Moria, which is exemplified on the Balin's Tomb Inscription.

The Dwarves introduced various new cirth and some unsystematic minor changes to the values. The greatest of those changes, which resulted in major reorder, was the switch of the cirth for s and h (f and . ), and for unknown reasons, the abandonment of the cirth $, q for which they substituted R , T. Subsequently they used @ for r and subsequently u for n!

They used also ,, which was a simplified form of u. Following the relation of those two letters, they gave to w the value z to relate better with . , which as mentioned had now the value s.

Tolkien doesn’t mention any other cirth abandoned by the Dwarves but much must have been, as there are many that represent sounds not occurring in (at least our published words of) Khuzdul, like th, dh, hw etc. It is strange also to observe that some of the cirth they introduced represent sounds not occurring in their language, like nj, hy, ñ, y-, hy! Of course, our corpus of Khuzdul is very limited to judge the necessity or not, of these sounds.

Examples
The only Angerthas Moria inscription by Tolkien is Balin’s Tomb.

2calu 3SdluSa Sw2c9eVcwc99D6S

Balin Fundinul UzbadKhazadDûmu

From the documentation, the Dwarf battle-cry could be as written:

}2c@SeeVcwv9IeVcwv9cl6xuS}

''Baruk Khazâd. Khazâd ai-mênu!''

and some other words:

gcwvu ‘azân < `-Z-N (dimness, shadow)

gcwcuSa2lwc@ ‘Azanulbizar (Dimrill Dale)

uSaSeeVlw9lu 	Nulukkhizdin (caves of Nargothrond)

8Vc@eDu 	Tharkûn (Staff-man, the dwarves name for ‘Gandalf’)

glral%6xe 	‘iglishmêk (the gesture code / sign language of the Dwarves)

eVzaz9wv@c6 	Kheled-zâram < Kh-L-D, Z-R-M ('Mirrormere')

eVcwv9 Khazâd < Kh-Z-D (Dwarves)

Go to:

 * ../First Age/
 * ../Third Age/


text:
User talk:Jamesday~enwikibooks

How did you delete two history versions?
Hi Jamesday, I just noticed your comment on the revision history of IT bookshelf (Jan 16, 2005) ("despam. THE TWO VERSIONS OF THIS ARTICLE BEFORE THIS SPAM ARE MISSING DUE TO HUMAN ERROR BY ME. Sorry for the inconvenience."). How could this happen? I mean.. technically. I thought no page history can be deleted by a common user - or did you touch the database directly? Just curious... --Andreas Ipp 07:37, 16 Jan 2005 (UTC)
 * As James isn't here very often, I thought I'd let you know that he's a developer, which lets him do strange things. Gentgeen 08:08, 16 Jan 2005 (UTC)
 * Oh, then he might help me with a problem I just posted on Staff lounge:
 * "I'd like to add a box to my project, that does not show up on print, just on screen. I looked at the Wikibooks commonPrint.css but didn't find any generic class ".noPrint" or something like this. I could just use a class  to mimic this behavior, but it is not a clean solution, as top might in the future also have other stylistic properties that I don't want to inherit. Any idea, who could change the CSS file mentioned above? It would be a simple one line addition to the CSS file. (adding it to my private CSS file would not be of much help, since I want to use this property in a book for everybody)." --Andreas Ipp 09:47, 16 Jan 2005 (UTC)

Your account will be renamed
Hello,

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

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

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

Sorry for the inconvenience.

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

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

title: User talk:Jamesday~enwikibooks


text:
Wikibooks:Requests for deletion/Alchemy

Alchemy

 * This book passes off medieval pseudo-science as fact, offers baseless, ambiguous and contradictory claims (e.g. "This is an exercise in operative alchemy. That is the practical means of refinement. Speculative alchemy is what you are reading. Alchemy is the integration of knowledge into the practice or art of living. In this sense science is speculative. Technology is operative. Alchemy is the craft that combines the truth of science with the technology to enable that truth."). Ridiculous assertions and bald-faced lies are tossed off nonchalantly (e.g. "The agenda of alchemy has always been the furtherance of human knowledge and the integration and improvement of society. Alchemy has also been a technological system, interested in working operations and the preparation of material wealth, longevity and a big theory of everything now being attempted by modern physics.").

 * The book offers no prospect of being changed or improved to something of value (or even something not completely false).

 * The book is not a science textbook (it's listed in the science section), nor even a textbook of any kind. I see no compelling argument for its existence on Wikipedia.--24.103.207.38 22:16, 23 Oct 2004 (UTC)
 * Extraordinary as it may seem you do not have the ability to predict the potential of something to evolve. There are few things that are more able to generate correction than that which is completely false. According to your interpretation the book merely needs to be factual. Operative alchemy is partly based on paradox and multi leveled symbols - what you refer to as ambiguety and contradiction. It also uses ridiculous assertions to test the 'metal' and response of those who are easily swayed by such techniques. The alchemical term for such people is 'puffers'. If you know what is required to refine this book then please do so. However it may be that you belong to those who have always had a tendency to burn and flame what is beyond their certainties. I gather this is not your intention? 82.69.58.117 21:10, 4 Nov 2004 (UTC)
 * Please speak in plain English - I can't follow what you are saying. Are you saying that it's perfectly ok to right something that is not factual into an article? because if you I'm afraid that you are going against the whole ethos of wikibooks ans the wikimedia foundation. Theresa knott 09:59, 5 Nov 2004 (UTC)

 * Well maybe it should be moved to media studies? Are you seriously suggesting there are no textbooks on operative alchemy of this kind. Clearly one is required. 82.69.58.117 21:10, 4 Nov 2004 (UTC)

 * I agree it's not a science textbook, but that can be delt with by removing it from the science section. I'm not at all convinced that it needs to be delted outright though. The book needs serious amounts of work, but we since alchemy did lead to the science of chemistry we should have abook on this subject. Weak keep Theresa knott 09:59, 5 Nov 2004 (UTC)

 * Keep As long as the textbook does not pass itself off as fact (so it should have a clear warning at the top), it seems like something that somebody may want to find out about. Definitely needs quite a bit of work though.

 * Keep Just because the topic of the book is not part of mainstream science doesn't mean it doesn't deserve to exist. I would be very interested in reading about the history of alchemy, myself. However, I would suggest that the language, which seems particularly obfuscatory and murky (as may be the nature of such a topic), be clarified. --Chuck Hoffmann 13:32, 20 Nov 2004 (UTC)

Will start the History section for you Chuck 82.69.58.117 19:18, 30 Nov 2004 (UTC)

 * Keep- I think there could be a category for funny useless books, like Vandwelling, Time Travel Genius, and this. But if those others go, this should too. -- Tormod 04:56, 21 Nov 2004 (UTC)

 * Keep Alchemy is philosophy, and an ancient perspective on percieved manifested reality, identity and evolution WITHIN that context, using terms suited to the perspectives, and style of percieving, which have collectively formulated it. Arguments about the usefulness of an alchemy treatise are moot.  Consider that calling water an amino acid comprised of two atoms of hydrogen and one of oxygen is an conventional oversimplification for one who has learned to relate and identify with the subtle interactions of manifested reality, and an outright mistruth, a stunted truth, for one who percieves reality through the eyes of a physicist.  All these 'factual' entries are descriptions, not facts, behooving one to be true to topic.  Alchemy is philosophy, part of the rudiments of thought, of self-awareness.  It is only of use to one who would increase intimacy of self-awareness (including what one percieves and indentifies with as "thing", a necessary component of "self", being "not identified as self").  It is of practical significance (as a text); the applications of an understanding of alchemy ARE what's happening all around us and in us, and it is useless other than as a pathway to wisdom, which I will personally define as understanding in operation.  This is a call for clarity (and editing out the spurious content,) not censorship.

 * Keep Many things one person considers useless another finds of great value.  Let a thousand flowers bloom!! simontzu

BTW The sacred texts archive has excellent references in the public domain on alchemy. Subtle Truth, 04 Dec 2004

Thanks subtle - and thanks to all those who voted to keep - the vote for deletion will now be deleted - you are welcome to contribute Long live tmxxine (not in this dimension) Lobster 08:36, 8 Dec 2004 (UTC)

title: Wikibooks:Requests for deletion/Alchemy


text:
User:Niallj

Hi there, :) My name's Niall Jackson and I live in England in the UK. My interests involve PHP and web application development, as well as chatting on IRC. I'm also quite partial to wargames, such as hackthissite.

You can see my homepage at hellfresh.co.uk

I'm a member of the English language translation checkers: If necessary, e-mail sent to me through this page will be read, and responded to. :)

title: User:Niallj


text:
C Programming/Common practices

With its extensive use, a number of common practices and conventions have evolved to help avoid errors in C programs. These are simultaneously a demonstration of the application of good software engineering principles to a language and an indication of the limitations of C. Although few are used universally, and some are controversial, each of these enjoys wide use.

Dynamic multidimensional arrays
Although one-dimensional arrays are easy to create dynamically using malloc, and fixed-size multidimensional arrays are easy to create using the built-in language feature, dynamic multidimensional arrays are trickier. There are a number of different ways to create them, each with different tradeoffs. The two most popular ways to create them are:
 * They can be allocated as a single block of memory, just like static multidimensional arrays. This requires that the array be rectangular (i.e. subarrays of lower dimensions are static and have the same size). The disadvantage is that the syntax of declaration the pointer is a little tricky for programmers at first.  For example, if one wanted to create an array of ints of 3 columns and rows rows, one would do

 * (Note that here multi_array is a pointer to an array of 3 ints.)

 * Because of array-pointer interchangeability, you can index this just like static multidimensional arrays, i.e. multi_array[5][2] is the element at the 6th row and 3rd column.

 * Dynamic multidimensional arrays can be allocated by first allocating an array of pointers, and then allocating subarrays and storing their addresses in the array of pointers. (This approach is also known as an Iliffe vector). The syntax for accessing elements is the same as for multidimensional arrays described above (even though they are stored very differently). This approach has the advantage of the ability to make ragged arrays (i.e. with subarrays of different sizes). However, it also uses more space and requires more levels of indirection to index into, and can have worse cache performance. It also requires many dynamic allocations, each of which can be expensive.

For more information, see the comp.lang.c FAQ, question 6.16.

In some cases, the use of multi-dimensional arrays can best be addressed as an array of structures. Before user-defined data structures were available, a common technique was to define a multi-dimensional array, where each column contained different information about the row. This approach is also frequently used by beginner programmers. For example, columns of a two-dimensional character array might contain last name, first name, address, etc.

In cases like this, it is better to define a structure that contains the information that was stored in the columns, and then create an array of pointers to that structure. This is especially true when the number of data points for a given record might vary, such as the tracks on an album. In these cases, it is better to create a structure for the album that contains information about the album, along with a dynamic array for the list of songs on the album. Then an array of pointers to the album structure can be used to store the collection.

The index is slightly trickier than before, but can still be obtained by y*i+j. You then access the array with Some more examples with higher dimensions: Note that w*(x*(y*i+j)+k)+l is equal to w*x*y*i + w*x*j + w*k + l, but uses fewer operations (see Horner's Method). It uses the same number of operations as accessing a static array by dim4[i][j][k][l], so should not be any slower to use.
 * Another useful way to create a dynamic multi-dimensional array is to flatten the array and index manually. For example, a 2-dimensional array with sizes x and y has x*y elements, therefore can be created by

The advantage to using this method is that the array can be passed freely between functions without knowing the size of the array at compile time (since C sees it as a 1-dimensional array, although some way of passing the dimensions is still necessary), and the entire array is contiguous in memory, so accessing consecutive elements should be fast. The disadvantage is that it can be difficult at first to get used to how to index the elements.

Constructors and destructors
In most object-oriented languages, objects cannot be created directly by a client that wishes to use them. Instead, the client must ask the class to build an instance of the object using a special routine called a constructor. Constructors are important because they allow an object to enforce invariants about its internal state throughout its lifetime. Destructors, called at the end of an object's lifetime, are important in systems where an object holds exclusive access to some resource, and it is desirable to ensure that it releases these resources for use by other objects.

Since C is not an object-oriented language, it has no built-in support for constructors or destructors. It is not uncommon for clients to explicitly allocate and initialize records and other objects. However, this leads to a potential for errors, since operations on the object may fail or behave unpredictably if the object is not properly initialized. A better approach is to have a function that creates an instance of the object, possibly taking initialization parameters, as in this example:

Similarly, if it is left to the client to destroy objects correctly, they may fail to do so, causing resource leaks. It is better to have an explicit destructor which is always used, such as this one:

It is often useful to combine destructors with .

Sometimes it is useful to hide the definition of the object to ensure that the client does not allocate it manually. To do this, the structure is defined in the source file (or a private header file not available to users) instead of the header file, and a forward declaration is put in the header file:

Nulling freed pointers
As discussed earlier, after  has been called on a pointer, it becomes a dangling pointer. Worse still, most modern platforms cannot detect when such a pointer is used before being reassigned.

One simple solution to this is to ensure that any pointer is set to a null pointer immediately after being freed:

Unlike dangling pointers, a hardware exception will arise on many modern architectures when a null pointer is dereferenced. Also, programs can include error checks for the null value, but not for a dangling pointer value. To ensure it is done at all locations, a macro can be used:

(To see why the macro is written this way, see .) Also, when this technique is used, destructors should zero out the pointer that they are passed, and their argument must be passed by reference to allow this. For example, here's the destructor from  updated:

Unfortunately, this idiom will not do anything to any other pointers that may be pointing to the freed memory. For this reason, some C experts regard this idiom as dangerous due to creating a false sense of security.

Macro conventions
Because preprocessor macros in C work using simple token replacement, they are prone to a number of confusing errors, some of which can be avoided by following a simple set of conventions:
 * 1) Placing parentheses around macro arguments wherever possible. This ensures that, if they are expressions, the order of operations does not affect the behavior of the expression. For example:
 * 2) *Wrong:
 * 3) *Better:
 * 4) Placing parentheses around the entire expression if it is a single expression. Again, this avoids changes in meaning due to the order of operations.
 * 5) *Wrong:
 * 6) *Better:
 * 7) *Dangerous, remember it replaces the text in verbatim. Suppose your code is, after the macro invocation will x be incremented by 2
 * 8) If a macro produces multiple statements, or declares variables, it can be wrapped in a do { ... } while(0) loop, with no terminating semicolon. This allows the macro to be used like a single statement in any location, such as the body of  an if statement, while still allowing a semicolon to be placed after the macro invocation without creating a null statement.      Care must be taken that any new variables do not potentially mask portions of the macro's arguments.
 * 9) *Wrong:
 * 10) *Better:
 * 11) Avoiding using a macro argument twice or more inside a macro, if possible; this causes problems with macro arguments that contain side effects, such as assignments.
 * 12) If a macro may be replaced by a function in the future, considering naming it like a function.
 * 13) By convention, preprocessor values and macros defined by   are named in all uppercase letters.

title: C Programming/Common practices


text:
Japanese/Lessons/Where is it?

This lesson introduces the sentence structure and vocabulary to describe where things are.

Before you start, make sure you've read the module on pro-forms for an explanation of these prepositions, and learnt how to use the particles "は", "の", and "に" as well as the difference between "います" and "あります".

Asking "where"
To ask about the location of someone or something you ask:
 * 〜はどこにいますか
 * 〜はどこにありますか
 * Where is ～?

depending on whether the subject is animate or inanimate.

Sentence pattern

 * Note: ～の上に often means "on the ～".

 * ねこはテーブルの上にいます. — The cat is on the table.
 * 山田さんはビルの中にいます. — Mr. Yamada is inside the building.
 * ボールは箱の中にあります. — The ball is inside the box.

title: Japanese/Lessons/Where is it?


text:
Talk:Ada Programming/Tips

Private Types Can be Completed in the Unit's Body This is actually not true. Maybe the author was speaking about private types that are defined as access to a type declared in the private part and defined in the body. That is:

package Private_And_Body is  type Private_Type is private; private type Body_Type is private; type Private_Type is access Body_Type; end Private_And_Body;

The code samples in a tips section are mandatory so I'll add it to the page. ManuelGR 13:01, 16 Jan 2005 (UTC)

This is equivalent to C opaque pointers. I believed that it is used when in future versions the size of a data structure can grow, but I've only used it because is the sole rational approach to have real private types in C. Has someone used it? Is it interesting to add this info to the wikibook? - suruena 12:12, 7 Mar 2005 (UTC)

The following paragraph has been moved from the book to the discussion page since this feature alledged to Tucker Taft has been present in Ada since Ada 83.

These types are sometimes called "Taft types" —named after Tucker Taft, the main designer of Ada 95— because were introduced in the so-called Taft Amendment to Ada 83. In other programming languages, this technique is called "opaque pointers".

Quirks
I assume the described problem is caused by a bug of a particular GNAT version and maybe on a particular Windows version. Doesn't make sense to clarify this and add a link to the corresponding bug report? --ManuelGR (talk) 18:48, 10 June 2008 (UTC)

 * It seems like "delay 0.0" has been in wide spread use for tasking related issues (to do with synchronization points); comp.lang.ada usenet has reports on "delay 0.0" from as early as 1992. However, there is a hint in these messages that the expression was/is used to trigger a task switch, at least with a number of compilers. So maybe declaring this particular quirk a bug is less than could be done to improve the subsection. gb (talk) 11:18, 11 June 2008 (UTC)

title: Talk:Ada Programming/Tips


text:
Wi-Fi/Wardriving

War Driving (wôr dri'vin) v. Driving around looking for wireless networks. -term coined by Pete Shipley

The term wardriving generally covers the practice of discovering and mapping (with the help of GPS) the wireless networks available in a particular area. Useful statistics are gathered from this activity, including statistics on the encryption used in discovered networks. Wardriving does not include the unethical activity of unauthorised connection to wifi networks (encrypted or unencrypted).

'''WARNING: THE TECHNIQUES DESCRIBED ON THIS PAGE MAY BE ILLEGAL IN YOUR JURISDICTION. THIS PAGE IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. PLEASE CHECK WITH YOUR LAWYER FOR MORE INFORMATION'''

Equipment
To 'wardrive', you need the following equipment:
 * A computer (preferably a laptop or PocketPC, as they are far more portable)
 * A wifi card.
 * Transportation.
 * Software (Such as Netstumbler for Windows, Kismet for Linux, and KisMAC for Mac OS X)
 * A GPS receiver (optional but necessary to create a map)
 * External omnidirectional antenna, such as a ../Cantenna/ (optional)
 * External unidirectional antenna (optional)

How to Wardrive
After you have installed and started your sniffing software and have activated your wireless card, you should configure your GPS adapter. After that, drive to the area that you wish to investigate and pick up signals of the active wifi networks.

Links

 * Wardriving.com the latest changes in 2012

title: Wi-Fi/Wardriving


text:
User talk:67.115.107.84

oh my, lots of vandalism from a DSL user; any admin care to temporarily ban?

Jdstroy 21:17, 16 Jan 2005 (UTC)

title: User talk:67.115.107.84


text:
Talk:Conlang/Intermediate/History/Common sound changes

Untitled
How do you distinguish from Individual Sound Changes and General Sound Changes? It would be a nice thing to add. 81.84.137.181 21:51, 16 Jan 2005 (UTC) Sorry. That was me... Jotomicron 21:54, 16 Jan 2005 (UTC)

Japanese
Japanese has alveolopalatals and not postalveolars.

Reminder
It would be good at this point to remind the reader that allophones are indicated with square brackets. Also, tell us what the allophone [4] is as mentioned in the Lenition section (instead of forcing us to go searching for a link to the CXS page) Thanks! Westley Turner (discuss • contribs) 23:49, 6 November 2017 (UTC)

Grammar And Sound Changes
"Very important is also that sound change is grammatically unrestricted. This means in simpler terms, that a sound change can not only apply to verbs, it has to apply to all words in all inflections. Only phonological constraints are allowed."

This is false. Many Brazilian Portuguese varieties (such as Sulista and Paulista) delete final on verbs, but not on nouns. This yields different pronunciations for "poder" as a verb and "poder" as a noun. The verb is and the noun is. And this is only an example. — Preceding unsigned comment added by Brunoczim (talk • contribs) 21:17, 2 December 2020 (UTC)

 * I wonder if that passage was meant to refer to something different from what you're referring to, so that both can be right. I think I may have seen a similar remark somewhere else; possibly, if I can chase it down, the other reference will turn out to be clearer on the distinction. --Pi zero (discuss • contribs) 01:16, 3 December 2020 (UTC)