text:
Talk:XML - Managing Data Exchange

We will work on this soon. thank you, Viji
 * might also want to get rid of that leading space "XML: " - it looks weird and is destined to cause link errors. --IanCarter 00:18, 20 June 2006 (UTC)

This is coming real soon
 * 1) Should the contents maybe be organized into sections, e.g. Basic Concepts, Advanced Techniques, Real-World Examples?

there is a link - it is in real small size and it says => back to XML: Managing Data Exchange. If you know how to make it bigger let us know!
 * 1) Once I am in a chapter, there is no link to get back to the main book - There should be 'up' link?

Proper name
XML stands for "Extensible Markup Language", not "eXtensible Markup Language". You can consult the W3C site to verify.

Many of the examples in the book use tables to put line numbers to the left of code. The numbers do not line up properly with the lines of code in my browser, however (Mozilla). Might I suggest either leaving off the line numbers or including them inline, like I've done in the SVG chapter? I guess a better situation would be if the wiki software could automatically insert line numbers. I realise that the reason for putting the line numbers in a separate table cell is to avoid them being copied to the clipboard if the code is selected.

I thought one way might be to use an <ol> to automatically number the lines, but it seems that Mozilla will copy the numbers to the clipboard too.

 * -- Cam

 * I think it would help a lot if there was some way to have the wiki software format XML. Syntax highlighting and automatic line numbering would really help the readability of these pages. --- Sploo22 12:15, 30 Oct 2004 (UTC)

Goals and audience
I've just popped over here from the Wikipedia XML page. Can someone explain to me:
 * What is the goal, or focus, of this book? Is it basic tutorial? A reference manual? Guidance on advanced techniques?
 * Who is the intended audience? Beginners? Managers trying to get a flavor? Experience XML'ers trying to extend their knowledge?
 * What are the recommended pre-requisites? What knowledge should I have? I noticed a list of recommended software in the Preface.

It's useful to have this sort of information either on the first page, or with an explicit link on the first page.

Thanks.

DanielVonEhren 18:43, 1 Feb 2005 (UTC)

 * I agree yeah. Basically the problem is this book has a section /Introduction to XML, but no section called /Introduction. How about it? -- Harry Wood - 10:28, 2 August 2006 (UTC)

subchapters
I'm a little surprised to find "CSS" and "style sheets" as separate subchapters. IMHO it'd be better to understand when having the tweo subchapters "CSS style sheets" and "XSL style sheets and transformations". BTW why is CSS itself explained (it's not a language defined by XML) instead of the use of CSS within XML? (the "Learning objectives" lists "know how to implement and use CSS on a XML document" but there is mainly CSS for HTML but very few for XML in general) I don't get the point...but maybe there was a discussion earlier :) then please insert the power points into the introduction.

Naming convention
Current book naming convention is depreciated. I suggest changing it to slash convention. --Derbeth 16:37, 2 November 2005 (UTC)

 * I second this suggestion. --Kernigh 03:01, 5 November 2005 (UTC)

Domain-specific languages bookshelf
Hello,

would you please check the Domain-specific languages bookshelf. There are several books on the whish list for which your book has chapters. Do we need extra books or will the chapters be exhaustive enough once they are finished. If the later is true then please trim the whish list.

Many of the chapters are planned for revision. And will probably be revised in future classes. This cycle of revision will be over in June 2006, let see if they give a better picture then

Thank you.

--Krischik T 07:17, 30 November 2005 (UTC)

XML versus Programming:XML versus XML: Managing Data Exchange
The following is a chronology posted by Kernigh:

 * At the start, XML redirected to XML: Managing Data Exchange, and there was a separate book called Programming:XML.
 * At 5 November 2005, Kernigh ( contribs ) decided to propose the merger of Programming:XML, a short introduction to XML, into XML: Managing Data Exchange, general introduction to XML, by marking the two pages with mergeto and mergefrom respectively.
 * At 29 December 2005, 68.61.36.66 ( contribs ) made four edits. The first two edits changed other users' comments on this page (Talk:XML: Managing Data Exchange). Kernigh reverted these edits at 18 January 2006. The third edit replaced the redirect at XML with list linking XML to both XML: Managing Data Exchange and Programming:XML (see here. A post to Talk:XML said that XML should become a new book that is a general introduction to XML.
 * From 13 to 17 January 2006, 68.184.159.189 ( contribs ) made several edits to XML: Managing Data Exchange, mostly small changes to spelling and presentation format. During this process, 68.184.159.189 removed the merge tags of Kernigh, and 68.184.159.189 replied to 68.61.36.66 at Talk:XML.
 * At 16 January 2006, Derbeth ( contribs ) sent Programming:XML to Votes for deletion.

I have decided to again redirect XML to XML: Managing Data Exchange, and to vote to delete Programming:XML. Because I am redirecting Talk:XML here, you can view the posts of 68.61.36.66 and 68.184.159.189 through this permalink. --Kernigh 03:32, 18 January 2006 (UTC)

Orphaned pages
I've found Answers (XML) - will you merge it to this book or can it be deleted? Please mark useless pags with delete. --Derbeth talk 00:01, 23 January 2006 (UTC)

Speedy Deletion Candidate
I am confused with a couple of pages I've come across that seem to be related to this Wikibook. All I'm asking for is to have somebody try to explain the rationale for trying to delete these Wikibook modules and to note where the content may have been duplicated or some other editorial reason for trying to delete this stuff. For now, I'm removing the deletion template tags, but if the contributors here would like to remove this content, please make a clear note as to why you feel the content needs to go.

Something simple like: "This is a duplcate of XML: Managing Data Exchange/Introduction to XML" or "obsolete content no longer need for project" is all that I'm looking for. Leaving the reason out nor any discussion on the discussion page about why it needs to be deleted makes it hard for me as an administrator to understand why the content needs to go. Thank you for your work in this part of Wikibooks, however. The pages to review are the following:

 * XML: Managing Data Exchange/Single-Entity (Chapter 2)
 * XML: Managing Data Exchange/Introduction
 * XML: Managing Data Exchange/A single entity (Answers)

--Rob Horning 17:45, 23 January 2006 (UTC)

Thanks!
Hi everyone,

Thanks to everyone that is working on this. Great start. I am an instructor and am trying to create a series of free XML learning modules usable in Moodle and I would like to use/reuse as much work as possble.

I teach in the US and many of the organizations use ISO/IEC 11179 date element names (see the WikiPedia entries on ISO/IEC_11179. This uses an UpperCamelCase three part name.

My goal is to start with very simple re-usable teaching structures and build on them. I would also like to add quiz materials in some XML format for Moodle. I am looking into that now.

I put a sample of what I am working on here: XML Schema before I realized that some of the tables were part of your materials. I apologize for the duplication.

Also, please tell me more about yourselves, your background and objectives. Anyone build re-usable learning objects before? Leanrning Objects. I have not done this in the past. Everything was a one-off based on my library of over 3000 PowerPoint slides. It seems very hard to be able to design learning modules that can be re-used by many people.

- Dan User:dmccreary

Hi Dan !

Thanks for your interest! You have just stumbled upon a work in progress and you will probably see many changes in the coming months. We are students at the University of Georgia in the Management Information Systems department. This XML wikibook is a class project. We are learning, teaching, and revising together. Dr. Watson is our teacher and I am a member of the Editorial Board. Things are just getting started and may appear a bit messy, but we are working on organizing and cleaning up the book. Feel free to give us suggestions (we saw your post in the one to one relationship chapter). It is nice to have outside eyes. Also, you can just email me at viji@uga.edu

Thanks, Viji

Neat professional book
Good job. But dont forget the PDF Version when you have finished. See PDF versions. I have started a Print Version template to get you started. RobinH 20:42, 9 March 2006 (UTC)

Thanks for your input!

Rtw 18:39, 26 March 2006 (UTC) Thanks for the pdf

Warning
I am going to remove Image:Tree.PNG, Image:TreeBranch.PNG and perhaps other images without license information used in this book. I tried to contact the uploader of these images but did not get any answer. --Derbeth talk 08:46, 27 July 2006 (UTC)

Orphans
These pages are not linked to from anywhere in this book. Please either incorporate them into the text or mark them for deletion by typing on each page.

 * XML - Managing Data Exchange/Parsing
 * XML - Managing Data Exchange/Print version
 * XML - Managing Data Exchange/XSL from chapters
 * XML - Managing Data Exchange/C.3
 * XML - Managing Data Exchange/C.4
 * XML - Managing Data Exchange/C.5
 * XML - Managing Data Exchange/C.6

Thanks! --hagindaz 22:30, 28 July 2006 (UTC)

Idea
I haven't seen a chapter about in-line documentation in programming like C#. There is a recommendation for tags to be used in such comments:  It might we worth mention if it hasn't been already. --Stefán Örvarr Sigmundsson 02:01, 27 September 2007 (UTC)

PDF request!
Hi Folks,

Can i please ask for a PDF version of this XML manual? Thanks
 * Ditto -- Sj (talk) 02:34, 1 February 2009 (UTC)
 * I agree - a PDF would be very handy! -- MHCABI (talk) 22:40, 28 June 2009 (UTC)

Document Type Definitions
I think we should add a chapter on DOcument Type Definitons. While XML Shemas can be usful in certatin contexts, DTDs sould be mentioned I will add a chapter right after Data Schemas If there are any objections please say so Wolframalpha (talk) 02:09, 11 June 2009 (UTC)

Syntax Highlighting Extension
I've seen a lot of books using a Wiki extension called SyntaxHighlighting_GeSHi. I think it would be nice to have such highlighting around here. I'm just a beginner at WBooks but I may try to help with the syntax highlighting if you need, it may take a while for me to get all gears going but I'd love to contribute!

Congratulations for the good work you've dedicated to this book!

Hopugop (discuss • contribs) 18:51, 11 December 2011 (UTC)

Suggested IDE/editor for this textbook?
Should there be a recommended IDE or XML editor for this textbook? The preface recommends NetBeans, which is lovely (depending on how you feel about Oracle...), but then there's also a whole chapter near the end of the book about the proprietary Exchanger XML Lite editor, and the rest of the text is IDE-agnostic. It seems that the book could benefit from either referring to a consistent editor (e.g. all the examples being NetBeans-specific, with a YMMV note for those using other software), or from intentionally exposing the reader to a wide range of software. As it is, it's inconsistent and perhaps confusing to people new to markup languages and text editors. Sandbergja (discuss • contribs) 16:37, 8 September 2012 (UTC)

Reviewing page
Hello, can someone review this article edit: XML - Managing Data Exchange/SVG!? There are also some fixes in. Thanks in advance. (PS: I'm from the german SVG-WikiProject) -- Perhelion (discuss • contribs) 18:25, 23 February 2013 (UTC)

Hyphen in the title?
Any idea why the title of this book uses a hyphen (-) instead of the (arguably) more correct en dash (–)? — Ivan Shmakov (d ▞ c) 22:00, 29 January 2014 (UTC)

What is Markup?
XML is known as markup language, which defines some types of rules that can be easily understood by human or machine to encode XML document. So here, whatever information is added to the XML document, it can be kept with some rules that define different labels for information. We can also call the set of symbols that used to store information.

If you want more just look here. XML Tutorial

title: Talk:XML - Managing Data Exchange


text:
Cookbook:Cuisine of Denmark

| European cuisines

Danish traditional food reflects the northern agricultural climate, where recipes are made of grains, beef, pork, chicken and milk products.

 * Rye Bread (Rugbrød)
 * Øllebrød (Beer and Rye Bread Porridge)
 * Rødkål: Danish Braised Red Cabbage
 * Frikadeller: Small veal and pork meat patties traditionally served with boiled potatoes, gravy and rødkål
 * Æbleskiver: Small, rounded pancakes

South Jutland
South Jutland is the southern part of the Danish mainland which is connected to Germany. There is some special cuisine which is inspired by German cuisine, and is thus not common in the rest of Denmark.

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

title: Cookbook:Cuisine of Denmark


text:
Cookbook:Beer and Rye Bread Porridge (Øllebrød)

| Cuisine of Denmark | Breakfast

Øllebrød (Danish for Beer Bread) is a Danish bread porridge, easily made from (dry) rye bread using this very simple recipe. Together with salmon (and other fish), pork, rye bread, beer and potatoes, øllebrød was an important nutritional element of traditional Danish cuisine until the 1800s. A Danish family usually had a big pot on the stove in which they threw leftover bread and beer dregs. This was served as an everyday meal, morning and afternoon. The pot was seldom emptied, so it was a kind of continuous meal.

Ingredients

 * 1 loaf of day-old rye bread (preferably without whole grain)
 * Malt beer (preferably a sweet dark stout)
 * Sweetener, as desired (e.g. sugar or honey)
 * Lemon juice (optional)

Variant I

 * 1) Put the rye bread to soak in beer for 6–12 hours.
 * 2) Bring the mixture to a boil, and simmer slowly for about 1 hour. Add more beer if it's too dry; the consistency should be like that of oatmeal. If you want it sweet you can mix in some sweetener. For a fresher taste, add a touch of lemon.
 * 3) Serve with whipped cream if you're introducing this meal to someone who is not Danish.

Variant II

 * 1) In the evening, cut away the crust from the rye bread, and cut it into cubes.
 * 2) Put the bread in a pot and cover it with beer (or water) and a lid. Set aside.
 * 3) In the morning, add sweetener if using, then heat it all up.
 * 4) Stir until it steams vigorously, adding water if it gets too dry.
 * 5) Serve with milk for a warm, very solid breakfast.

Notes, tips, and variations

 * Feel free to use whatever beer that is the cheapest, as the alcohol is going to vaporise anyway. You can also substitute the beer with water, if you want.

Kookboek/Øllebrød


text:
Cookbook:Homemade Peanut Butter

Peanut butter is a food product usually consisting of roasted and ground peanuts, sometimes sweetened. It is commonly sold in grocery stores, but can be made at home. Many styles are available; the most popular are creamy (smooth) and crunchy, but honey-roasted or wholenut varieties can also be found. Creamy peanut butter is made by grinding all of the mixture very finely. The crunchier styles leave portions of the mixture with a coarser grind, resulting in larger pieces of peanut interspersed with the creamier fine ground mixture.

Used in sandwiches (particularly the classic peanut butter and jelly sandwich), candy (for example, Reese's Pieces), and pastry, it is a good source of protein, and is popular with children. For people with nut allergies, the intense concentration of nuts in peanut butter can cause fatal anaphylactic shock. Peanut butter is often contaminated with aflatoxin.

Ingredients

 * 2 cups raw shelled peanuts
 * 1½ teaspoon vegetable oil, peanut oil or canola oil
 * 1½ tablespoon olive oil
 * ½ teaspoon white sugar (optional)
 * 2 teaspoon honey (optional)
 * 1 pinch of salt

Procedure

 * 1) Combine the peanuts and vegetable oil (peanut oil or canola oil) in a bowl.
 * 2) Place tinfoil on a baking pan, and bake the peanuts at 200–350 °F for about 10 minutes.
 * 3) Let peanuts cool.
 * 4) Mix with olive oil. Process or blend for a while.
 * 5) Add in sugar, honey and salt. Process or blend until you are satisfied.

title: Cookbook:Homemade Peanut Butter


text:
Talk:Compiler Construction

organization
I'm not sure this is the best organization for a book on compilers. It's missing a lot of important detail in areas (regular vs. context-free languages, SSA intermediate representation, etc). Plus, there's a lot of room devoted to stuff that is not really compiler related (garbage collection and IDEs for instance).

I think a better organization would be:

 * Introduction
 * What is a compiler
 * History of compilers
 * Brief background in language theory (chomsky hierarchy)
 * Frontend
 * Parsing regular languages
 * Regular expressions
 * Lex
 * Parsing context free languages
 * shift-reduce
 * recursive-decent
 * packrat?
 * Yacc
 * Putting it together
 * Simple lex/yacc toy language
 * Intermediate Representations
 * Parse Trees
 * Semantic Analaysis
 * Abstract Syntax Trees
 * Advanced Representations
 * RTL
 * Single Statement Assignment (SSA) Form
 * Hashed SSA Form
 * Optimizers
 * Dataflow Analysis
 * In-depth on optimizations (dead-code, common subexpression, etc.)
 * Alias Analysis
 * Backends (Code Generators)
 * Various BURGS
 * Hand Generation

I'll leave this here for a bit to see what others think and then start refactoring.

--AnthonyLiguori 03:36, 27 May 2005 (UTC)

what language to use
It may be more informative for an intro text to use a language like Scheme, which can be easily presented with and without lex and yacc.

--Matt 15:26, 9 May 2004 (UTC)

 * We do not want to be beholden to just one programming language. Dysprosia 23:15, 9 May 2004 (UTC)

Oh, I wasn't suggesting the book should be "Constructing a Compiler for Scheme." Typically, a text on compilers has alternating theory/practice sections. I was merely suggesting that Scheme be used in the practice sections.

What language would you use?

--Matt 16:45, 17 May 2004 (UTC)

I have limited experience in compiler writing (interactive Basic compiler written in assembler, Pascal-like high level language written in itself, plus a slight aquaintance with flex and bison c.f. lex and yacc). Fluent in Fortran, C, Algol 60, Basic, Pascal, some experience with C++, PL/1, fluent in assembler for 6 different computer architectures (not x86 infortunately), expect to learn Java this year. I'm willing to have a stab at this wikibook over the next year, but would probably need to redo the existing outline, and would prefer to use C or simple C++ as the implementation language for any examples.

--Murray Langton 22:00 14 Nov 2004 (UTC)

 * Can you elaborate why the old outline needs to be redone? I think we should start from a small book, so it can be manageable to us. The current outline seems to be too much. Also, I disagree to use C++. We expect that the textbook is used mostly in college, and nowadays students learn Java to write code, and many don't know C/C++. Also, the fact that java is generally machine-independent is quite nice to us. -- TakuyaMurata 23:39, 15 Apr 2005 (UTC)

I don't think there's any need for "implementation examples." Languages should be described in the appropriate notation (regular expressions or EBNF), optimizations should be described via dataflow equations, and so on. Compilers have a rich set of domain specific languages and this shouldn't be hidden.

--AnthonyLiguori 03:39, 27 May 2005 (UTC)

3000 lines?
In the first section, we have the following:

"Note that a compiler is a non-trivial computer program; when written completely by hand a non-optimising compiler for a simple source language is likely to be upwards of 3000 lines long. Some compiler-writing tools are available which can reduce this size."

That 3000 is somewhat misleading, especially for a simple source language.

For instance:

Wirth's famous PL/0 (Pascal subset) has been implemented in many different languages - C and Pascal versions usually run around 1000 lines or less.

A Pascal subset, powerful enough to compile itself, has been implemented in less than 1500 lines of Pascal.

Another Pascal subset, Tiny-Pascal, is around 1100 lines of code, and can also compile itself.

At least two C compilers, with enough of the language implemented to self-compile, have been implemented in less than 1000 lines of code each.

Various Basic's (with strings and arrays) can be implemented in 1000 lines or less.

All of these are hand-written.

While it can and does take many thousands of lines of code to implement a compiler for a more complicated language (full ANSI-C, C++, Java, etc.), compilers for simple (but useful) languages can easily be implemented in less than 1500 lines of hand-written code.

I realize this is being very picky, but there is no need to make compilers appear to be even more complicated than they already are :-)

--Sam 16:30, 6 July 2005 (UTC)

donation
I have had a small book/large paper on writing compilers on my web site for ten years or so. [http://pages.prodigy.net/j_alan/hitech/compiler/compmain.html]

Feel free to make any use of it, including direcly copying and pasting (everybody does it anyway!)

I would especially encourage you to make use of the sections on theory, including using Chomsky Normal Formal and Extended Backus-Naur Form to design languages, and converting such forms to recursive-descent parsers.

If you use the code examples, they should probably be converted to a more modern language as I'm not sure how much Pascal is used anymore.

j_alan@prodigy.net

--JamesAlanFarrell 11:55, 28 July 2005

 * Has anything been done about this? Any volunteers? -- Jonmmorgan 00:28, 9 March 2006 (UTC)

theory
the opening paragraph of this wikibook claims that theory is kept to a minimum. I dont think this is a good tactic. Theory should be included and sufficiently explained. It is reasonable, however, to separate the "non-essential" theory into optional subsections. for instance, each section could have "Introduction", "main ideas", "theory", and "examples" subsections. --Whiteknight 05:27, 24 August 2005 (UTC)

implementation language
the subject of which language to use is an important one, and i think it deserves it's own section. I think, that it would be short-sighted to limit this book to any single existing language, because languages come in and out of favor relatively quickly. a book written 10 years ago in C would probably be rewritten today in VB or Java. unfortunately, a book written exclusively in language X exclude people who dont use language X. I have 2 recommendations: 1) all code examples be written in at least 2 different languages, possibly more for important examples, or 2) all code examples be written in Pseudocode (or even wikicode). --Whiteknight 05:21, 24 August 2005 (UTC)

 * My understanding is that most compiler books have a bunch of "toy" languages as examples.
 * But then they have a long chapter on a language powerful enough to write a Self-hosting compiler.
 * There seems to be a tradeoff between a "powerful" language that can describe any particular toy language in a few lines (but the compiler for that language is long and complex), vs. a "simple" language that takes many more lines to describe that toy language (but the compiler for that language is much shorter and easier to understand).

 * Will one of our code examples be one of these mind-bending "self-hosted" compilers? If so, an alternate implementation in some other language will help avoid the ChickenAndEggProblem.
 * --DavidCary 19:00, 24 February 2007 (UTC)

output language

 * What output language should the compilers in this wikibook spit out? --68.0.124.33 (talk) 00:00, 6 January 2009 (UTC)

 * Some options are:
 * * C-- is a "portable machine language" specifically designed for high-level compilers to generate (C--).
 * * MMIX is a fictional machine language specifically designed to be easy to learn (MMIX).
 * * ARM is the machine language used in most 32 bit CPUs (ARM).

so much for organization
I don't think it is time for us to discuss the organization of the book. The book, as of this writing, has almost no stuff yet but some just outline. I think it works just fine if we simply write more by adding examples, explaining theories, constructing exercise problems etc. We can easily reorganize those materials later on after gaining more sense of what the book should be. In other words, the book should be what it turned out to be and not necessarily what was planned initially. People have different views in mind about what the book should be and it would be the best if people simply add what they know. -- 219.168.92.42 11:52, 15 November 2005 (UTC)

Very Tiny Basic Lex/Yacc interpreter
I am currently writing an interpreter in C, using Lex/Yacc and Make. The language is that defined in the current Case Study 1. I feel we need an example of a Lex/Yacc project, since it is a common approach. Also since interpreting Very Tiny Basic is pretty straightforward, we could write interpreters for it in many languages/ways to demonstrate the differences in technique (and try to underline the similarities). Anyway, I plan to make it Compiler Construction:Case Study 1B, although it belongs in a much latter place than Case Study 1. I hope to write a useful article with it. Any suggestions would be appreciated. Matt73 03:01, 6 February 2006 (UTC)

 * I think that is a good idea. Maybe it's not necessary to do it in many languages so much as many techniques.  A few that come to mind are domain specific languages (eg. Yacc/Lex), recursive-descent parsers and regexp driven lexers (which is what Yacc and Lex compile to), parser combinators (though I think you might need a declarative language to do those properly) and DCGs (Definitive Clause Grammars, used in languages like Prolog and Mercury).

 * I also notice that, while VTB is defined in Bachus-Naur form, I don't see anywhere that BNF is actually defined. I also think that a few sample VTB programs are needed, as that shows a language better than BNF.

 * Jonmmorgan 00:26, 9 March 2006 (UTC)

 * I've written a couple of sample programs, but I haven't done any BASIC programming for a long time (which is a good thing). Could someone please review them?

 * Jonmmorgan 23:39, 23 March 2006 (UTC)

About size of hand written and table-driven compiler. Both type of compilers may have less then 700-1000 lines of code and it may compile itself. To do that only limited language subset must be umplemented (one-dimension arrays, functions without arguments, if, while, call and assign stmts) and some checks may be omitted.

 * avhohlov, 20 March 2006

 * Avhohlov, I'm not sure who/what you are replying to? Regardless, your note is very interesting.             Do you have an example?  Thanks --

 * 72.145.148.76 13:34, 20 March 2006 (UTC)

Here [] you may see small compiler (less then 1000 lines, DOS) and modified Wirth's Pascal-S (less then 2000 lines but much more expressive, P-CODE) both self-compiled. There are no differences to translate small compiler to any widespread languages (for example C or Pascal). DOS are obsolete now and P-CODE may have some benefits but it requires virtual machine compiled by other compiler or assembler. Generation of Linux/ELF file may be relatively simple (see next link).

Also you may see OTCC (Obfuscated Tiny C Compiler) at []. Very small but it's a hacker's code.

 * avhohlov, 20 March 2006

Lex/Yacc
I am writing an outline for a proposed book on Lex/Yacc (and Flex/Bison). These two programs are certainly worth writing about, and they can be used for more then just compilers. here is my proposed outline. If we have a book dedicated to these programs, we won't need to waste time trying to explain them here in the compiler book. Also, I think that some of the contributers here would make good contributers to this new book. Any feedback would be appreciated. --Whiteknight (talk) (current) 22:16, 25 April 2006 (UTC)

It's a very good idea, and would certainly help this book. I feel that this should be a more general book than "How to make a compiler using X technique&tools" and it would be good to be able to give theory and simple examples then refer to the Flex/Yacc book (and hopefully others). Of course, the eventual direction of this book will be decided by whoever ends up writing it (not me, I don't know enough theory). I intend to finish my VTB interpreter, it just needs the interpreting code, finishing and some article writing. The reason I chose to write it was so that it flows on from the 1st case study. Hopefully when my exams are over I'll be able to finish it. Good luck with Flex/Yacc, and maybe I'll be able to help out. Matt73 13:49, 10 June 2006 (UTC)

 * If we had a good book here on wikibooks about automata theory, and context-free languages, writing a general book about compilers and theory would be a sinch. Maybe I will get to work on an outline for a book like that as well. --Whiteknight (talk) (projects) 15:15, 11 June 2006 (UTC)

Automata Theory
I have decided to create a new book on the subject of Automata Theory. This way, we can have a wikibooks-based resource for the background information, and then this book can use that resource to cover the ground-work behind compilers, computer languages, etc. I have posted a preliminary outline for this new book HERE on my user page. Any comments or suggestions are welcome. --Whiteknight (talk) (projects) 00:27, 12 June 2006 (UTC)

Safety optimization
What are "safety [optimizations] reducing the possibility of data structures becoming corrupted" ?

While I've certainly seen many optimizations that are "not re-entrant", "less safe", "non-volatile-safe", or otherwise "unsafe", I am unfamiliar with optimizations that make the code *more* safe than non-optimized code.

Please enlighten me. --DavidCary 20:25, 25 October 2006 (UTC)

Probably things dealing with stuff like this ( http://lambda-the-ultimate.org/node/1579 )--Panic 23:05, 25 October 2006 (UTC)

title: Talk:Compiler Construction


text:
User:Wfg

Wfg Radiologe Deutschland

title: User:Wfg


text:
General Mechanics/Many Particles

The uneven dumbbell consisted of just two particles. These results can be extended to cover systems of many particles, and continuous media.

Suppose we have N particles, masses m1 to mN, with total mass M. Then the centre of mass is

 * $$\mathbf{R}=\frac{\sum_n m_n \mathbf{r}_n}{M}$$

Note that the summation convention only applies to numbers indexing axes, not to n which indexes particles.

We again define

 * $$\mathbf{r}^*_n=\mathbf{r}_n-\mathbf{R}$$

The kinetic energy splits into

 * $$T=\frac{1}{2}M V^2 + \frac{1}{2} \sum_n m_n {v^*_n}^2$$

and the angular momentum into

 * $$\mathbf{L}=M \mathbf{R} \times \mathbf{V} +

\sum_n m_n \mathbf{r}^*_n \times \mathbf{v}^*_n$$

It is not useful to go onto moments of inertia unless the system is approximately rigid but this is still a useful split, letting us separate the overall motion of the system from the internal motions of its part.

title: General Mechanics/Many Particles


text:
General Mechanics/Rigid Bodies

If the set of particles in the previous chapter form a rigid body, rotating with angular velocity ω about its centre of mass, then the results concerning the moment of inertia from the penultimate chapter can be extended.

We get

 * $$I_{ij}=\sum_n m_n (r_n^2\delta_{ij}-{r_n}_i {r_n}_j)$$

where (rn1, rn2, rn3) is the position of the nth mass.

In the limit of a continuous body this becomes

 * $$I_{ij}=\int_V \rho(\mathbf{r})(r^2\delta_{ij}-r_i r_j) \, dV$$

where ρ is the density.

Either way we get, splitting L into orbital and internal angular momentum,

 * $$L_i=M\epsilon_{ijk}R_j V_k+ I_{ij}\omega_j$$

and, splitting T into rotational and translational kinetic energy,

 * $$T=\frac{1}{2} M V_i V_i + \frac{1}{2} \omega_i I_{ij} \omega_j$$

It is always possible to make I a diagonal matrix, by a suitable choice of axis.

=Mass Moments Of Inertia Of Common Geometric Shapes=

The moments of inertia of simple shapes of uniform density are well known.

Spherical shell
mass M, radius a
 * $$I_{xx} = I_{yy} = I_{zz}=\frac{2}{3}Ma^2$$

Solid ball
mass M, radius a
 * $$I_{xx} = I_{yy} = I_{zz}=\frac{2}{5}Ma^2$$

Thin rod
mass M, length a, orientated along z-axis
 * $$I_{xx} = I_{yy} = \frac{1}{12}Ma^2 \quad I_{zz}=0$$

Disc
mass M, radius a, in x-y plane
 * $$I_{xx} = I_{yy} = \frac{1}{4}Ma^2 \quad

I_{zz}=\frac{1}{2}Ma^2$$

Cylinder
mass M, radius a, length h orientated along z-axis
 * $$I_{xx} = I_{yy} = M\left( \frac{a^2}{4}+\frac{h^2}{12} \right) \quad

I_{zz}=\frac{1}{2}Ma^2$$

Thin rectangular plate
mass M, side length a parallel to x-axis, side length b parallel to y-axis
 * $$I_{xx}=M\frac{b^2}{12} \quad I_{yy}=M\frac{a^2}{12} \quad

I_{zz}=M \left( \frac{a^2}{12}+\frac{b^2}{12} \right)$$

title: General Mechanics/Rigid Bodies


text:
XML - Managing Data Exchange/XPath/Answers

XPath Chapter => XPath

XPath Exercises => Exercises

XML

Exercises
In this exercise, you will modify the xsl-tree.xsl file we saw in chapter 8 XPath to...

 * 1) Print the name attribute of every bigBranch element with thickness set as ‘thick’.
 * 2) Print the name of the parent of each bigBranch.
 * 3) Print the color of all leaves with a color attribute.

1. Print the name attribute of every bigBranch element with thickness set as ‘thick’
xsl-tree1.xsl

Output

2. Print the name of the parent of each bigBranch
xsl-tree2.xsl

Output

3. Print the color of all leaves with a color attribute
xsl-tree3.xsl

Output

XPath Chapter => XPath

XPath Exercises => Exercises


text:
User:Glenn Willen

I'm a Computer Science undergraduate student at Carnegie Mellon University. I've noticed that one of the missing books on your site that has been requested is a computer science textbook, and I'm thinking of doing some work to start one. This page is here for no particular reason, since I doubt anyone will click on my name. :-)

Oh but they do Glenn! Write your book! :Þ

/Broken Links/

title: User:Glenn Willen


text:
Using GNOME/Run Application

Run application lets you run an Application by its command name directly, rather than selecting it from the menu.

To use "run application".
 * Select "Run Application" from the menu (Note: this menu item is now gone as of Gnome 2.12)
 * Press Alt+F2 keys.

Options
 * Run in terminal runs the program in the terminal. This is used when running terminal based programs.

title: Using GNOME/Run Application


text:
Cookbook:Rice and Lentils (Mejadra)

| Palestinian Cuisine

Extremely simple to cook, mejadra is a fundamental component of Middle Eastern cuisine. It provides carbohydrates, proteins, and a full stomach. It also tastes great. The most common recipe uses rice. Bulgur can be substituted for rice, using the exact same procedure. When cooked with rice, this recipe is gluten-free. It isn't gluten free when cooked with bulgur (wheat).

Ingredients

 * 1 cup (100 g / 3.5 oz) dry lentils
 * Olive oil
 * Salt
 * Baharat
 * Cumin
 * Ground cardamom
 * 4 cups (1 L / 1.1 qt) water, divided
 * 1 cup (80 g / 2.8 oz) uncooked rice or bulgur
 * Ground pepper
 * 1 medium sized onion

Procedure

 * 1) Fry the lentils in oil for 3–4 minutes, stirring continuously, until the first beans show signs of scorching.
 * 2) Add salt, baharat, cumin, and ground cardamom to taste.
 * 3) Add 2 cups water and cover. Bring to a boil, lower to a simmer. Cook for 20 minutes or until all the water is absorbed by the lentils.
 * 4) Fry the rice in oil for 3–4 minutes, stirring continuously, until the grains change colour.
 * 5) Add salt, black or white pepper, and ground cardamom.
 * 6) Add 2 cups water and cover. Bring to a boil, lower to a simmer. After 5 minutes turn the heat off, and leave standing for another 10 minutes.
 * 7) Cut the onion into thin strips (about 0.5x4 cm / 0.2x1.6 in).
 * 8) Fry the onion in olive oil until crisp and deeply golden brown (this may take a while but will result in much fuller flavor).
 * 9) Mix the lentils and rice, and top with the fried onion. Use 2 parts lentils to 1 part rice for a moist consistency.

title: Cookbook:Rice and Lentils (Mejadra)


text:
Cookbook talk:Middle Eastern cuisines

Aren't most of these countries in the Near East, rather than Middle East?

Hi. Israel needs its own separate entry. It is a country of immigrants from all over the world, and the foods that have become popular - while many are Middle Eastern - many others are quite certainly not. Do Palestinians eat Kubana? Jahnun? Gefilte fish? Osem chocolate spread? Even the Middle Eastern ones have taken on their own Israeli flavor.
 * While I don't disagree with your position, you have de-linked an existing page, and replaced it with non existant links to two pages. If possible, please look at Cookbook:Cuisine of Israel / Palestine and determine where it should go, then let a logged in user know, so they can move the page to the correct title.  Thanks, Gentgeen 23:37, 16 May 2004 (UTC)

 * I can't find the reason why Arab cuisine was deleted. I have a few recipes that are wide-spread throughout the Arab countries like Khubz (pita bread) and Ful (fava bean stew).
 * BTW, I think that Israeli cuisine does belong in the correct geographic area. —The preceding unsigned comment was added by David Cheater (talk • contribs) 2007-06-19T01:40:36.

 * The logs show that "Arab cuisine" was deleted because it was empty. I don't know anything further than that. Perhaps you should take this up on the Cookbook talk page, where it will be seen by more Cookbook editors.
 * BTW, ful just means fava bean; there are many recipes using ful, so perhaps you might like to call your ful recipe something other than just "ful", e.g. ful medames. Webaware talk 03:30, 19 June 2007 (UTC)

title: Cookbook talk:Middle Eastern cuisines


text:
Cookbook talk:Lentils and Rice (Mjeddrah)

I just posted a recipe for Mejadra, and when I went to list it on the index, I found this. Now, what do we do? The two are not-quite-the-same.

I'll list mine next to this one, and we'll see what others think...


text:
User:Glenn Willen/Broken Links

I'm not sure what the protocol on broken links is around here (i.e. where they should be listed), but the quantity of them, especially on administrative pages and such, is frustrating, so I'm listing them here as I find them. The top level is the pages linked from; the sublists are the broken links on each page. Feel completely free to add links to this list yourself, or tell me where the official list is (Perhaps one needs to be created.)

 * Image use policy
 * Image description page
 * Sound help
 * Alternate text for images
 * GFDL {This one seems pretty important... maybe it should be GFDL instead?}
 * Orphan
 * [[Image:Image_Policy_scalebar02.png]] {Missing image...}
 * Red, Pixel, Yellow, Green {Why are these even links? Reminds me of the Everything2 style of linking anything that moves.}
 * Non-local images

I think I've seen the intended targets of some of these links before; if I can find them again I'll correct those I can.

 * Vandalism in progress
 * Wikibooks:Module

 * Please do not bite the newcomers
 * NPOV {Should probably be NPOV or Neutral point of view}
 * Be_bold_in_updating_pages {This looks like a guessed link; I doubt it ever had a target.}

 * NPOV dispute
 * Wikibooks:Module {That's twice now. Looks like it existed, once...}

 * Wikibooks:Glossary
 * Why is the glossary full of broken linkage? That's a sure way to discourage newcomers...
 * Wikibooks:What is a module {Probably intended for the same content as Wikibooks:Module, also broken}
 * Wikibooks:Edit war
 * Wikibooks:Edit conflict
 * Orphan

title: User:Glenn Willen/Broken Links


text:
Cookbook talk:Homemade Peanut Butter

This module uses text adapted from the Wikipedia article Peanut butter. The page history, at the time the text was copied, is included below.

* (cur) (last). . 07:23, 14 Apr 2004. . Darac (Several clarifications/expansions.) * (cur) (last). . 13:36, 4 Apr 2004. . Bkonrad (rephrase a bit) * (cur) (last). . m 13:20, 4 Apr 2004. . Dmn (Earth's rotation) * (cur) (last). . 19:44, 25 Mar 2004. . Bkonrad (I don't think so) * (cur) (last). . m 18:05, 25 Mar 2004. . Dmn * (cur) (last). . m 20:20, 17 Mar 2004. . Modeha (ja:) * (cur) (last). . 08:15, 17 Mar 2004. . Ellywa * (cur) (last). . 11:58, 12 Mar 2004. . Bkonrad (Kellogg and Battle Creek connection) * (cur) (last). . 11:41, 12 Mar 2004. . Bkonrad (Kellogg and Battle Creek connection) * (cur) (last). . m 13:33, 22 Feb 2004. . Minesweeper (Reverted edits by 205.188.209.165 to last version by Marj Tiefert) * (cur) (last). . 13:28, 22 Feb 2004. . 205.188.209.165   * (cur) (last). . 11:52, 30 Dec 2003. . Marj Tiefert (mouse bait, too) * (cur) (last). . m 11:29, 30 Dec 2003. . Infrogmation * (cur) (last). . m 11:04, 30 Dec 2003. . Robertb-dc (Not the Charlie Brown kind) * (cur) (last). . 19:02, 8 Dec 2003. . 216.68.14.87 (Peanut butter) * (cur) (last). . m 22:05, 4 Oct 2003. . Branddobbe (typo) * (cur) (last). . m 19:39, 11 Aug 2003. . Maximus Rex (aflatoxin) * (cur) (last). . 12:20, 5 Aug 2003. . Xj14y (link fix. again.) * (cur) (last). . 12:18, 5 Aug 2003. . Xj14y * (cur) (last). . m 12:17, 5 Aug 2003. . Wfeidt * (cur) (last). . 12:16, 5 Aug 2003. . Wfeidt (sentences) * (cur) (last). . m 12:15, 5 Aug 2003. . Wfeidt (Peanut Butter => Peanut butter) * (cur) (last). . 12:06, 5 Aug 2003. . Xj14y (surprised I had to add this one.)

title: Cookbook talk:Homemade Peanut Butter


text:
Internet Technologies/Search engine

A search engine is a type of computer software used to search data in the form of text or a database for specified information.

Search engines normally consist of spiders (also known as bots) which roam the web searching for links and keywords. They send collected data back to the indexing software which categorizes and adds the links to databases with their related keywords. When you specify a search term the engine does not scan the whole web but extracts related links from the database.

Please take note that this is not a simple process. Search engines literally scan through millions of pages in its database. Once this has taken place all the results are put together in order of relevancy. Remember also not to get a search engine and directory mixed up. Yes they are used interchangeably, but they do in fact perform two different tasks!

Before 1993 the term search engine never existed. From then until now that has changed drastically, and almost everyone knows what it is. Since the Internet is used by millions of Americans daily, a search engine sees a lot of visitors especially ones such as Google and Yahoo. Almost all of us use one of the two if we have the Internet. By simply typing words into the engine, we get several results which gives us a list of sites. (Seigel)

Usually a search engine sends out a spider which fetches as many documents as possible. An index is then created by what is called an indexer that reads the documents and creates it. Only meaningful results are created for each query though, a process called proprietary algorithm. (Webopedia)

Work Cited
Boswell, Wendy. "How do search engines work?" What is a search engine? 19 September 2008. http://websearch.about.com/od/enginesanddirectories/a/searchengine.htm

title: Internet Technologies/Search engine


text:
User:Advanet~enwikibooks

Hi, contact me at: peczek@yahoo.com

title: User:Advanet~enwikibooks


text:
User talk:CzarnyZajaczek

I translate from english to polish Wikibooks (actually Programming:C).

title: User talk:CzarnyZajaczek


text:
Using GNOME/Force Quit

< ../Applets

Force Quit is an action applet that it used to deal with crashed and non-responding applications by forcing them off the screen. It allows you to deal with them in just two clicks. This is often useful when beta testing applications and it crashes on you.

To add to the panel, select Add (Some systems use "Add to Panel..."), Actions, Force Quit. It will appear as a Window icon with a large red cross on it.

To use.
 * 1) Click the "Force Quit" button.
 * 2) Click the Application to wish to quit.

title: Using GNOME/Force Quit


text:
User talk:Glenn Willen/Broken Links

Broken links
Hi and welcome to wikibooks. Most of the links you have listed as "broken" are in fact as yet uncreated links. Many of them have adapted names from wikipedia. So to fix the articles we need to go there, find the relavent page, copy and paste it over here then go through the text and fix the various references to wikpedia by chaning them to wikibooks. Theresa knott 12:48, 10 May 2004 (UTC)

Ahhh, I see. OK, will do. Glenn Willen 21:02, 10 May 2004 (UTC)

title: User talk:Glenn Willen/Broken Links


text:
Talk:XML - Managing Data Exchange/XUL

Why is the text in this page in tags? It makes for a less than beautiful page. Will there be host if I remove them? (218.128.116.44 zeimusu on 'pedia)

Luxor XUL link
I removed the link to "luxor xul", as it is not related to Mozilla XUL, other than in concept. People from "Open XUL Alliance" have been trolling around for quite a long time already, posting links to their "xul" projects on various Mozilla-related sites. --195.146.72.90 11:19, 13 September 2005 (UTC)

Various comments

 * The ‘id’ attribute is important in that it is the way to identify the window so that scripts can refer to it.

Not really. Scripts can use  to refer to the window element. The id is used for binding icons to the window, and sometimes in the overlays.

 * All events and attributes must be written in lowercase.

Actually it's just that XUL is case-sensitive, as is XML. Attributes that have special meaning in XUL happen to be all-lowercase. This doesn't stop you from using mixed-case attributes for your own needs.

 * All strings must be double quoted.

Attributes must be in quotes, just as in XML. It doesn't mean that "all strings must be double quoted".

 * Save it anywhere but be sure to give the file the .xul extension. Now just double click on it and it should open in your Mozilla or Netscape browser.

.xul files are not associated with Mozilla by default

--195.146.72.90 11:37, 13 September 2005 (UTC)

revision suggestions
Karl Strength 16:42, 29 March 2006 (UTC)
 * Bold key words and start with clear definition after each.
 * Follow author guidelines to revise chapter.
 * Show more widgets and some user created widgets.
 * Change the first example -perhaps use an example that we have been using through out the class.(movie, professor)
 * Create an assignment and place it at the bottom of the page. Use XUL and widgets to create a page that displays information about UGA.
 * Edit the conclusion section. (Try to make is sound less like a Firefox employee wrote it.)
 * Place Learning objectives in a box to set them apart from the rest of the text (as done in previous chapters.)

Editorial Board
Moussa Mané
 * You can move the "written by" part as a reference at the bottom, so the chapter stays consistent with the rest of the book
 * If you notice there is too much text, like whole block. The reader can even find a specific information. Try to break everything down. You may need to change the structure a little with more sub-sections
 * Example: first a section on widget where you explain what they are, then how to use them and add them
 * One for Events...then sub section would be Event handlers and another Responding to Events.
 * Fell free to change the title of the sections (The basics, A first example, Adding Widgets...) I find them inconsistent. (let me know if you need clarification on this)
 * A shorter introduction. the rest of the info can be added as a new section
 * The example can be movie, professor or any other simple one
 * Give a summary.
 * Add Exercises and answers link

Professor
Rtw 19:38, 1 April 2006 (UTC)
 * Karl and Moussa's suggestions will help improve the chapter considerably
 * Try to use a tourism example to stick with the themes covered in other chapters. Maybe cities and attractions :)
 * Change sample code to fit with author guidelines
 * Change so that reference browser is Firefox rather than Mozilla or Netscape
 * Correct labeling of code (eg figure should not be within the code)
 * Check all the references are still valid

XUL's ≠ HTML's   tag!
The article states that the  tag of XUL is like the   tag of HTML — wich is not true. the  tag is more like the   tag (they're both the root tags) and XUL can for example also have the    and    root tags. More information at MDC XUL hub.

title: Talk:XML - Managing Data Exchange/XUL


text:
General Chemistry/Units

SI Fundamental Units
These are the seven basic SI units from which all other units are constructed.

SI Derived Units
All other units are derived units. They are built from fundamental units. This is a small selection of units that may be found in General Chemistry.

SI Prefixes
A prefix appears before a unit's symbol when expressing very large or very small quantities. For example: 0.001 kg = 1 g = 1000 mg.

Temperature
One degree Celsius is equal to one Kelvin (in magnitude).

* Notice it is not "degrees Kelvin".

title: General Chemistry/Units


text:
User:Blades

See Wikipedia home.

title: User:Blades


text:
Wikibooks talk:Information technology bookshelf

Let's start some books or topics today to address these issues
I do NOT believe this is the place for technical support for programming and hardware "issues."

This form of support is provided by an enormous collection of well established and documented resources. There are countless mailing lists and news groups and IRC channels that you can subscribe to if you need support, developer information, get answers to your questions or hear the latest news.

To address some of these issues:

Let's go for it. I have started two books below that I believe may help.

Book of Technical Support

Forms of Technical Support
Technical support for hardware and software issues are provided by an enormous collection of well established and documented resources. There are countless mailing lists and news groups and IRC channels that you can subscribe to if you need support, developer information, get answers to your questions or hear the latest news.

Mailing lists provide users and interested parties support and communication through the use of email. Anyone can join a mailing list and as a member you will automatically recieve and be able to send questions, comments or news on any topic that the group supports. To join any of the known mailing lists below, visit the link indicated, follow the simple instructions to join and have fun! The requirements to join a list are generally as obtrusive a joining wikipedia.com.

IRC channels provide support by means of "live" chat.

News Groups provide support in a manner similar to "Mailing List." To subscribe to a news group.....

The following list of software support resources are organized alphabetically by the common name of the application or programming language.

My suggestion is lets make like as simple to begin, like keep it alphabetically. As the size of the lists grow, we can re-group, sort, as needed.

I suggest a list of external links are created in the wiki tradition as follows...

where,

 is the url of the mail subscribe page, news server, or IRC channel as required by our wiki.  is the name common name of the software title or programming language.  := email | news | irc  := active | inactive | archive

C Programming Language
SNIPPETS C programming conference email [ FidoNet  SNIPPETS C programming conference C_Echo Gateway to the FidoNet ]

Python List
Python List email large, active list for the discussion of all issues related to Python Programming

Doc-SIG -- Python Documentation Special Interest Group email active list for the discussion of issues related to ...

--

Book of IT Software Standards

Part 1 - Software Standards
A list of the known industry or community standards and where copies of these standards can be located and/ or reviewed. For example:

RFC - 1 RFC - 2 ASCII ANSI - help me out XML ANSI C FORTRAN Common Lisp HTML 3.0 ISO Standards

Book of Hardware

I have a very related concern to the one expressed below. Namely I think there should be a kind of project in wikibooks devoted to technical support for hardware and software. I am not sure if this is the place to talk about this but if anyone knows a better place could they please direct me or just copy my post to that place. Right now I usually debug problems I have with my computer by going on google and doing searches. This method is usually effective but sometimes it is problematic because the solution to problems is often stored within support forums and google sometimes does not do a good job searching these forums. Anyways I think there should be a bookshelf within IT devoted to technical support of any hardware/software. This technical support should be organized by books devoted to pieces of software or hardware. They should include extensive list of problems, error messeges and reasons for the problems as well as proposed solutions.

--Assman 06:28, 4 Apr 2005 (UTC)

I'm not sure if this would be a good place, but it's closest I got so far. What I have been thinking about is the ever-repeated question of "will work or be worth anything" that nags especially non-windos people. It would be nice to have a large-ish wiki that has a net of descriptions of manufacturers, devices, drivers and standards & interfaces and descriptions and relations where possible.

Particularly sought-after is information like "Is the Foocorp Idlemaster 2000 an usb storage device that will work everywhere or a proprietary protocol doorstop whose support will be buried in half-a year when the company goes under and/or I update my OS?" or "Will this phone eat Hayes/AT over IR or EIA-[24]32? OBEX?" etc. Likewise for things that appear as serial devices, support changer commands etc.

Manufacturers are obscenely bad at producing this information and with the customer base they have, they don't have to. There is also little incentive for them to support aging hardware.

As for the wiki, for example under usb-storage, you would have a list of devices that appear as usb storage devices. It might have a link to Linux usb-storage.o and equivalent drivers on other systems. Each would have a list of devices that have been confirmed to work.

This could also contain parts lists for "special" manufacturers, eg Sun or IBM part numbers, what they are, what they fit in and what drivers or os versions they work with etc. Many user groups (like TUHS) might also be interested in getting something more than scattered personal repositories for their objects of interest.

The wiki could be as coherent or fragmented, as large or focused as people manage to make it. Databases are just too heavy and often specialized.

--Blades 22:00, 10 May 2004 (UTC)

Disorganization
Why is there no hardware and software umbrella categories in the Information Technology bookshelf? --Lordscissorhand 14:58, 21 Dec 2004 (UTC)

Reorganisation of IT Bookshelf
I've given the subject some more thought. I'm thinking that the separation of the monolothic 'IT bookshelf' into three (below) might aid navigability.
 * Computer Science - All topics related to the research of computer use and technology.
 * Programming - Language guides, framework guides, software design guides, patterns etc.
 * IT/IS - All software guides, technology guides, certification etc.

The problem would then be catagorising books. It is sometimes hard to make a distinction between computer science and the other two catagories. The question is - do we want to make as general a distinction as possible at the 'bookshelf' level (i.e only have two (see below)), or try to define clearly several new IT related bookshelves?

Robcowie 12:30, 9 Mar 2005 (UTC)

 * It'd be fine with that. I've already been standardizing true CS books to be put in the namespace "Computer Science:". The defintion is: if a university would teach a course on the subject in their computer science department, then it belongs as a Computer Science book. I wouldn't make the defintion so narrow to be "research of computer use and technology". To me, Computer Science is "the study of the creation, analysis, and limits of computations; for different computational models". An algorithms book covers both the analysis and creation of computations, while an intro to programming book would only cover the creation. Theorhetical computer science studies the limits.

 * Whatever the case, Computer Science does seem a bit out of place with the IT books. MShonle 01:15, 12 Mar 2005 (UTC)

 * (Also, I like the three categories: Programming, Computer Science, and IT. An intro to the MFC classes isn't an IT book, but it certainly isn't computer science (and thus it's "programming" instead). MShonle)

I agree that a reorganization should take place. I think that the horizontal listing of books at the top of the page doesn't quite match the organization of books once it gets organized below, which is kind of disorienting. It seems that the horizontal listing is what people first encounter when visiting the bookshelf pages, but the breakdown that occurs later in the IT page is how people seem to want to organize it as books become more developed or as more books are added. jotaboca 02:36, 7 Mar 2005 (UTC)

It seems to me that the IT bookshelf has outgrown itself. There are many books that could be more easily found if moved to new sections. For example, there is a 'Computer Science' bookshelf within the IT bookshelf. However, some of its books should perhaps not be in it. It is also not directly linked to from within the IT bookshelf. There are therefore several books that do not appear in the IT bookshelf list and con only be located by searching.

I suggest that - as well as a reorganisation of the topics within the IT bookshelf, it should be split into two bookshelves:
 * 'Computing' - for non-academic books such as software guides, certification books and Linux install guides.
 * 'Information Science' - for more technical, advanced topics such as Programming, software design, hardware design etc.

I'm new to the wiki so I don't yet fully understand the concept of moving books, or the difference between modules, books and pages. Consequently, I haven't figured out the best way to proceed should this idea be accepted by users.

Any thoughts would be gratefully recieved.

Robcowie 17:23, 20 Feb 2005 (UTC)

 * Shouldn't we create the subcategory Computer Science/Logic to put there Logic for Computer Scientists and 21 Century Math Method? (In the future these books should share some content either by inclusion or reference.) What to do with the template (Template:IT bookshelf) regarding CS logic topic? What's about refering 21 Century Math Method from there? -- Porton (Apr 22, 2005), you can reply at User_talk:Porton

 * I think Computer Science related books could all go under the umbrella of Computer Science for now: there's aren't too many true CS books (most are Programming or IT books), so there isn't much need for finer grained categories. As for sharing information, this seems to be a tough problem: What we've been doing with the Data Structures and Algorithms books is to let some of the content just be copies. It makes the books stand out on their own better, and creates more opportunities. (Also, keeping a tight integration of chapters in the same book makes it a better book. Having to keep a couple of chapters independent is more of a headache than having two similar, but not the same, portions of text out there). Because it's all GFDL anyway copying poses no real problems and a little redundancy can be good. MShonle 00:31, 4 May 2005 (UTC)

I vote for the split in some manner. Any of the above suggestions work for me. I'm not fond of the partial listing plus the full listing below. But, I'm too lazy to do much about it so I won't complain. :-) liblamb 04:44, 1 May 2005 (UTC)

The IT Bookshelf has been massacred! Books are missing and whole sections are gone. I'm going to try and clean it up a little bit, but I need another set of eyes to try and figure out what happened. I'm not talking just stuff moved to the new Computer Science bookshelf, but stuff that was supposedly moved there has not been moved but simply deleted. I'll see what can be done, and somebody else check over what I've done Rob Horning 20:38, 1 Jul 2005 (UTC)
 * I found out where everything went. There was a separate bookshelf just for Computer Science.  I was trying to find where some of the books went that were previously on the front page for the IT bookshelf, and somewhat legitimately it was missing.  I created a template for the front page that deals with just Computer Science, and put back some of the books that were there, as well as the broad categories that were previously deleted due to the reorganization.  On the whole, I think it has turned out pretty well, and something long overdue.  Thanks is due to User Darklama for doing most of the heavy lifting.  I did, however, put Computer Programming languages back into this bookshelf, at least until it legitimately deserves its own totally separate spot on the front page... or until a substantial reorganization of the front page occurs somehow.Rob Horning 06:00, 2 Jul 2005 (UTC)

why all the computer sections
Why all the computer sections? I would like to contribute some of my knowledge, but the whole situation seems far too disorganized.

Is there a good reason why there are three? Computing bookshelf, Computer Science bookshelf and IT bookshelf. (unknown)

 * I'm wondering about the same myself. What about merging them? --Orderud 10:58, 9 October 2005 (UTC)

I don't think we need to merge the three book shelves. Here's what an ideal organization would be: That's just my two cents, but the differences between CS and IT are so great that they shouldn't belong on the same shelf.
 * 1) Computer Science -- the more "math-like" stuff you would get in college
 * 2) Programming -- language guides, library tutorials, programming tips and recipies
 * 3) IT -- about computer programs, using them, set up of networks, so long as you aren't writing much "code"

For example, a programming guide to the Python language would not be considered "computer science" unless perhaps it was really an intro book teaching programming (that just happened to use Python) or it was actually an advanced book teaching some other CS concept. Thus, there is a need to split CS with Programming (because, similarly, a guide to the MFC library is not a computer science topic either, in as much as a manual for repairing a car does not count as Physics). Further, a guide to using Photoshop wouldn't be considered programming nor computer science, so we need an IT shelf. --MShonle 18:56, 9 October 2005 (UTC)

Merging with Programming:Serial Data Communications

 * This discussion was copied to here from Talk:Serial communications bookshelf.

See also Talk:Programming:Serial Data Communications

This is a bookshelf, not a Wikibook. It isn't my fault that the rest of the Wikibooks on this bookshelf are dead and not making any progress. IMHO, get rid of the merge request and let this bookshelf stay quiet or merge it somehow into the Computer Science bookshelf. This is just a Wikibook organizational tool. Considering that this bookshelf has stayed more stable for the past several months while the Computer Science bookshelf has been heavily modified and broken off from the Information Technology bookshelf with other massive reorganizations goes to show that perhaps this bookshelf is needed anyway. --Rob Horning 04:09, 5 November 2005 (UTC)

 * Oops... I admit not reading enough of the material to check if this was a good merge. I only assumed that all pages called "Serial Programming:..." were part of Programming:Serial Data Communications because Serial Programming is currently a redirect there. I forgot that some stuff is not using WB:NC/WB:NP.

 * It seems that this page is a list of books, like Physics. So merging the books into another book (even if that book has chapters starting with "Serial Programming:...") is a bad idea. I will be removing the merge notices soon. --Kernigh 03:19, 6 November 2005 (UTC)

 * I would like to suggest instead that someone changes the Serial Programming redirect to go to this module. --Kernigh 03:24, 6 November 2005 (UTC)

Merged into IT bookshelf
I decided to put these books in a "Serial Communications" section of the existing "Hardware" section of the IT bookshelf. These books are about programming (so they could be put on Computer Science bookshelf too) but they are also about hardware. --Kernigh 21:29, 1 December 2005 (UTC)


text:
Talk:Linux Guide/Archive 1

Freezes
I edited the freezes pages a lot to make it better

Criticism - Kernel Guide or System Guide
It is of course rather strange to want to make a book about a kernel that contains "installation" and "for users". It probably comes from what makes people somehow unable to grasp that the huge vague collection of entities that they are trying to call by name does not have one.

The Book of Linux would be about a kernel, Book of GNU would be about a project, vision and a sort of a toolkit, Book of Debian would be about an organization, a view, a software distribution and the policy that looms over them, Book of Redhat would be about a company and its product family etc. Trying to cram fragments of each and more under a single umberella will most likely not result in anything very good. Better than nothing, perhaps, but possibly something damaging. --Blades 23:06, 10 May 2004 (UTC)

 * Hardly. Linux is commonly used to refer to Linux systems, i.e. computing environments based on the Linux kernel. Not that difficult to understand, or that new a concept. And certainly a book about Linux would be useful, as essentially everything one would write in it would apply to all distros, as well as other UNIXes. Have you been to a bookstore recently? You'll find plenty of titles on "Linux," and very very few of them are about a kernel. Maybe you should take up your point with all the world's publishers, or every Linux user — I don't think you'll change many minds.

 * Of course, I think this Wikibook needs reorganizing, but your essential point is nonsense.
 * --Daniel 09:58, 11 May 2004 (UTC)

 * Of course there are. And people doing things in a stupid or false way does not make those ways any bit less stupid or wrong. My last sentence, quite especially is the essential point. I repeat: Trying to cram fragments of each and more under a single umberella will most likely not result in anything very good. Better than nothing, perhaps, but possibly something damaging.

 * Book of Unix and GNU environments would make sense, though, and there should be a good one. Something like an old Altos SysV manual I have that explains what a user will experience, needs to understand, and will be able to do with a ready Unix system. It describes logins, files, file system, services available and the main tools, editors and finally sh, awk, and sed. These would have much in common in Unix and GNU systems. It would be both correct and very useful.

 * Of course there is also the slightly better aimed term of "Linux distribution" which is also covers a staggering variety of wildly different concepts and units. Still, the essential point above remains.

 * This is of course merely an informed opinion and not a mandate or complaint or anything such. Here appears to be a chance to do either something correct or something incorrect. By all means do create more incorrect books and justify it with following market lemmings. Many people will quite possibly be happy about it. Other could not care less. Some people will meet both the possible good and the possible bad results of people using this text.

 * I just believe this point did need to be brought up, so I did. --Blades 12:06, 11 May 2004 (UTC)

 * The core Linux developers, active for well over a decade, have always used "Linux" as it is commonly used by book publishers today. They do not subscribe to the political nonsense being forced down our throats by Richard Stallman via his bloated uname and autoconf tools. It is tradtional for the kernel name and operating system name to be one and the same. This situation is not unusual in the English language. AlbertCahalan 03:39, 7 October 2005 (UTC)

 * While I must concur with Blades, I think that most "Linux" users know the signficance and distinction between the output of `uname -o` and `uname -s`. Frankly, I think this book (at least in its current form) serves to benefit beginning users or those considering GNU/Linux, who likely are only aware of "Linux".  I'd make a comment about this in the article, but I'd retain the title given the name recognition.

 * Lastly, given a target audience of beginning users or those still in consideration, the multifaceted nature of the current page is acceptable; however it should be noted that this is a mere generalized introduction targeted to those users. The article in its current form is hardly a "compendium", but that may be rectified with time.
 * --Eibwen 18:20, 20 Nov 2004 (UTC)

 * Note that "uname -o" was created to push Richard Stallman's political ideas. It serves no other purpose. It is not part of any standard. The latest UNIX and POSIX standard (IEEE, Open Group, and ISO) has "uname -s" though, which is required to report "the name of the implementation of the operating system". So, let there be no doubt, "Linux" is "the name of the implementation of the operating system". AlbertCahalan 03:39, 7 October 2005 (UTC)

 * More than a year later, Wikibooks has books about Linux system installation (Installing Linux) and new users (Linux For Newbies), but not much for the kernel (Updating the Linux kernel, Guide to UNIX/Linux). Some other stuff about the Linux and GNU environments is in Guide to UNIX. --Kernigh 01:34, 7 October 2005 (UTC)

 * Of course not. The kernel is a fast-moving target that is documented already in the source itself, in the Documentation directory included with the source, in BitKeeper and git change log entries, and in release announcement emails. Mailing lists, searchable via Google, fill in the rest. No wikibooks project could ever hope to keep up with the kernel as it changes. AlbertCahalan 03:39, 7 October 2005 (UTC)

 * GNU is an operating system and not a project, vision or a sort of a toolkit as Blades assumes. --Mms 11:58, 14 August 2007 (UTC)

Orphaned Wikibook module
The following is an orphaned Wikibook module that appears to belong with this Wikibook. Please place it where it would be appropriate, and rename:

 * File Compression

 * Because Linux Guide was not using it, I decided that File Compression is an appropriate submodule for the Guide to UNIX, specifically the Guide to UNIX commands. Kernigh 21:10, 2 October 2005 (UTC)

Guide to Unix
What's the point of having this when there's the Guide to Unix?

Is it any good?
Hi there i am just wondering what is linux like i have never actually used linux before i am just wondering is it good or not because like i say i have never actually used the system before????? —Preceding unsigned comment added by 202.169.201.17 (discuss • contribs) 2008-01-30T17:08:49

 * Perhaps you should have a read of this book: A Neutral Look at Operating Systems. Or simply download a couple of the more popular Live CDs and try Linux for yourself - a Live CD doesn't need to be installed, so it won't affect your existing computer system. Webaware talk 07:17, 30 January 2008 (UTC)
 * Virtualization is another option. It is basically running an operating system inside another. Vmware's products, Virtualbox, Xen, Qemu are all examples of software that does this. Slightly more technical, though. Searching Wikibooks, Wikipedia, and Google will provide useful info.--Jats (talk) 03:12, 28 February 2009 (UTC)
 * 'Is it any good?' well, for what? It probably isn't going to help you get a tire changed on the side of a mountain. Cordon Bleu isn't very good as rocket fuel either. I know people who won't run Linux anywhere that they are aware of, and others who won't run anything but Linux anywhere they can. If you're looking for a computer operating system that supports a wide variety of hardware, though possibly not everything in your current computer, then Linux is pretty good. If you're looking for something else, then you probably want to look somewhere else as well. I'm personally quite happy to use Linux for most of my computing needs. But that's me. Where your needs differ, Linux may not be a good match. Try, take a look at the things that are available, that perhaps you never even considered using your computer for, look through the equivalences pages and who knows you might find yourself happy with it. If you don't, most of us are OK with that too.--Rusty

title: Talk:Linux Guide/Archive 1


text:
Perl Programming/Modifiers

In addition to the basic control structures, Perl allows the use of statement modifiers. The statement modifier is placed at the end of the statement that it modifies. Note that the do {…} until (…) and do {…} while (…) loop constructs are actually statement modifiers. The complete list of modifiers is:

Unlike BASIC-PLUS, statement modifiers in Perl cannot be stacked.

title: Perl Programming/Modifiers


text:
Talk:Interlingua/Basic Interlingua English Dictionary

Untitled
You'd best contribute this to the WIKTIONARY www.wiktionary.org

It is a copy of Basic Interlingua English Dictionary
It is a copy of Basic Interlingua English Dictionary

Introducing Interlingua — A Short Course for Beginners (F. P. Gopsill). Isn't it a copyright violation? Why not to put only a link to that on line book?

Words requests
--Jondel 02:35, 31 October 2005 (UTC)

 * return, go back.
 * hero
 * size? amplitudo?
 * battle
 * war
 * excluding
 * push? pulsus? promoveo?
 * ab +by? Troy was conquered by Greece. Troy esseva conquite/vencite? ab Grecia?
 * charge (with electricity)
 * plate  => placa?  (existing in www.interlingua.com)
 * dry(existing in www.interlingua.com)
 * aire
 * vel ?
 * sive?
 * lamina?
 * point
 * of course => clara, certo
 * no matter
 * suppose
 * legendary
 * lips
 * teeth /tooth

 * tusk (elephant)

 * grasp or hold

 * (hunger) strike

Not added but in use

 * tamben :also
 * olim: formely already existing
 * attacar:attack

New ones

 * realise  (perficar?)
 * besoniar (to need)


text:
Visual Language Interpreting/Teams

There may be a need for a team interpreter due to length of assignment, complexity of material, pacing of speaker, multiple speakers, working with a Deaf-Blind consumer, or a need to copy sign questions from the audience. Ideally you should choose an interpreter you have worked with before, feel comfortable with and supported by. Prepare with your team mate before the event, if possible, or meet at some point to compare notes. If you are the interpreter for the general deaf audience and there is an Deaf interpreter for a Deaf-Blind consumer, you or your team mate may have to keep an eye on the Deaf interpreter's need for a repetition or clarification.

Preparation

How much preparation you do for an assignment will depend on the challenges it presents to you personally, as well as the realistic time constraints and the nature of the assignment, Decide how to split up the prep and share what each of you have found out later. To get accustomed to the style of the presenter, the following options are open to you in descending order of preference. If the presenter is deaf: (1) watch a videotape of the presenter on the same topic, (2) watch a videotape of the presenter on a different topic, (3) watch a videotape of a different deaf presenter on the same topic. If the presenter is hearing; (1) listen to a tape (audio or video) of the presenter on the same topic, (2) listen to a tape of the presenter on a different topic, (3) listen to a tape of a different hearing presenter on the same topic.

If no tapes are available, or if the assignment is an ongoing one, you may wish to find something written on the topic, especially by the presenter you will interpret for. Other written resources are encyclopedia articles, glossaries, articles from periodicals, or information from the World Wide Web. If an article is too lengthy, reading only the topic sentences (first sentence of every paragraph) may be helpful. Hearing and deaf people that are knowledgeable about the topic can supply you with good sign/word choices for the target language, as well as explain the meaning of the concepts in the source language. If this is an ongoing event, notes from the previous sessions will give clearer context.

Even a brief meeting between the principal speaker and the team interpreters, if at all possible, will give needed information and build trust with the presenter. Request copies of any handouts, overheads, or lecture notes. Find out what media will be used (movies, videotapes, PowerPoint, and so one) to determine placement and lighting needs. If you don't have time to read them, at least your team mate can feed you and prepare for her/his turn. Ask the presenter what the overall goal and major points are. Do any consumer education you feel is warranted. The team interpreters should also meet 10-15 minutes before the event. Your situation may not require all of the items below. However, be aware of them and keep them in mind when you are teaming.

Placement - English to ASL

You the interpreter will stand in a place that allows the Deaf audience to see the information: overheads, PowerPoint presentations, films, maps, and other media. Where will your team mate be? Some people have the team mate sit side-by-side, even for English to ASL. It seems to me that there should be some distance between the two so that your team mate can see what you are signing and feed you short bits of information without too much distraction. However the deaf people's eyes will naturally turn to whoever is signing, so perhaps a philosophy of open processing would be appropriate.

Open processing means that if the team mate understands what was said but you don't or have misunderstood and consequently missigned a large portion of what was said, the team mate chimes in and takes over for that short portion. You might even want your team mate to continue if you find that you don't understand because of topic change, the audience member has a thick accent, or some other factor. If everyone is sitting at a table, the interpreters could sit almost side-by-side, with perhaps one seat in between for them to see each other comfortably. When it comes time to switch, no one has to move. The deaf person merely switches his/her gaze.

Placement - ASL to English

You no longer need to stand close to the visual information and will now sit. It makes sense to sit side-by-side, since your team mate does not need to see you and can also whisper the feed (chucotage or sotte voce). It is now possible for there to be long feeds that are taken up by you and said in normal volume. You can always turn the interpretation over to your team mate if you feel that the feed will be lengthy, or they seem to have a better handle on the signer. I wonder how this works for the hearing audience. Deaf people have become so tolerant of the needs of interpreters to switch off, wait for full understanding of a text, and even interpret what the interpreter is trying to say, that these sorts of bumps in the interpretation hardly jar them any more. I know if I were listening to a spoken interpretation of, say, a Russian speaker and another voice chimed in, I would be thrown off, but maybe we all have to get used to such a thing. When there is no microphone but the room is fairly large, it may be beneficial for the interpreters to stand behind the entire audience so that the audience can hear them.

Signaling

How will you signal when you need help? How will your partner signal? Some ways to signal are: eye gaze (I tell my team mate I will never look at them unless I need help), puzzled look, raised eyebrows/wide eyes for teamed English to ASL; whispered need, touch on your partner's shoulder or arm (check first), or leaning towards your partner for ASL to English. Some things an interpreter may need to signal for: missed a word/sign, what was that fingerspelling, I know the word but how do you spell it, what does that word/sign/phrase/sentence/concept mean, something non-verbal just happened that I missed, or what's the sign/word for that? Plan quick and unobtrusive ways to ask your partner for these things.

Feeding

Some "team" interpreters think they are just there to wait for their turn. I have been guilty myself of trying to work on projects while being part of a team. Make sure that your team mate says s/he is fine without feeding before you bring out that book or laptop. Where will each of you be to allow for ease of feeding and smooth turn-taking? How do you want your partner to feed you missed information? How does your partner want to be feed? Can you volunteer missed or misunderstood information, even if not asked for it? Some ways to feed: in ASL, in English-influenced ASL (contact language), or with mouthing. What do you want your partner to be particularly attentive to, that is, what do you generally need help with? Some examples: fingerspelled information, numbers, proper names, or the big picture (the text or gestalt).

Team mate's responsibilities

There are many names for the team interpreter who is not at present signing or speaking the interpretation: feed interpreter, down interpreter, off interpreter, cold-seat interpreter, the non-working interpreter (if things are going properly that is a misnomer!). All of these have advantages and drawbacks. For the purposes of this paper, I will simply say your team mate and "you" will mean the on interpreter, working interpreter, up interpreter, hot-seat interpreter, what have you, unless otherwise specified.

Your team mate may need to take care of various things that come up, besides feeding you. These may include: fixing the lighting, changing a distracting background, getting the handouts, bringing water, adjusting the microphone, or what to do about audiovisuals. (Help! They just turned off all the lights!)

Continuity and turn-taking

What happens when one interpreter's style/language variation is markedly different from the others? Suppose you choose one way of expressing a concept and your team mate believes there's a better way to handle it or that the interpretation needs to be more English or more ASL. Do you both continue to interpret without making any adjustments to your style or choices? How often will you replace each other? It's important to negotiate. Try to use what your team mate has set up in terms of spatialization and sign negotiations. The method of spelling or replacement is an issue that will also allow for continuity if it is done properly. The best method is to decide on the approximate time that you will replace each other, such as every 20 minutes. When the time arrives, the team mate should let you know that it is time, because you will be too busy interpreting to check your watch and it looks rather tacky to check your watch anyway.

If the interpreters are positioned very close to one another, the team mate can simply walk up to the interpreter when it seems that an idea has been completed or when it seems there will be a considerable pause. The interpreter can stand up or move out of place if already standing and the team mate can take her/his place. If it is hard to tell when the speaker will pause because they don't tend to pause in their speech, the team mate can signal to the interpreter TIME+ and then the interpreter will simple leave when they feel they can or simply at some random time if there never is a "good time". In a formal stage event, the team mate can come up behind the interpreter from the wings, tap the interpreter on the back and move back slightly, remaining behind the interpreter and wait for the interpreter to walk away.

Turn-taking can become more complex if there are many deaf people and they are interacting with each other. This is because we need to see each person fully and can't rely on our hearing to jump from one speaker to another. If there will be a lot of this, it is better for the interpreters to take every other speaker. This allows the hearing audience to hear that there has been a change of speakers and allows the interpreters to see the full comment even when the next signer is far away or interrupting. If there is someone who is doing most of the signing, one interpreter can take this person during their "turn" and the team mate will take the next signer who will presumably not take as much time. If a third signer chimes in before the leader responds, the teacher's interpreter will also have to interpret this signer. It can be somewhat confusing but simply identify a change of speaker's if one interpreter ends up doing two people in a row.

Debriefing during the assignment and after

Use a notebook or piece of paper to communicate to each other during the assignment. Your team mate can write down comments while you are up and vice versa. You can comment on items that this paper identifies if you forgot to mention something during your pre-meeting that you would like your team mate to do. Remember to also give each other a pat on the back for things that were done especially well. Remember to share the total interpretation, rather than play the game of one-upmanship. Don't feel insulted if you are being feed something; that's why your team mate is there. If you are the feeder and the interpreter doesn't accept your feed, don't feel rejected. Perhaps they weren't able to incorporate it, or weren't sure what you meant. Do work together. One of the stickiest problems is what you do if you are in an on-going assignment that you find does not need two interpreters because there is so much unexpected down-time due to independent student work? The ideal would be if each of you could take every other class or one person take the whole thing because the other is confident of finding other work. I leave this as a moral exercise for the reader.

Have a post-meeting, even if it's short, to sum up how things went. It's important to find out what worked and didn't work for you and your partner. I'm sure you have had the experience of coming up with just the right thing to say or do after it's too late. This doesn't have to be a frustration. Brainstorm solutions for problems that occurred and use them next time you encounter a similar situation. Use the same tact you would use with your consumers to deal with differences of opinion.

Deaf-Hearing teams

Don't forget to consider a Deaf interpreter (CDI) as a team mate, especially in such situations as: (1) ASL-English if the CDI's voice is sufficiently understandable, (2) Deaf-Blind, (3) legal, (4) mental health, (5) High Visual Orientation (previously called Minimal Language Skills), (6) International Gesture, and (7) shadow interpreting for audience visibility. Some Hearing interpreters feel funny if they have a Deaf interpreter with them, because it looks like they can't do their job alone, and they may feel the Deaf person is looking them over. Well, sometimes we can't do our job alone and that's okay. We should strive to be able to survive scrutiny by CDIs or other interpreters.

Interpreters need to feel a part of the team. The CDI should not take the tact of "Oh, that interpreter doesn't understand you. Let's talk and then I'll tell them what you said." Instead the CDI should act as a facilitator of communication and allow the Hearing interpreter to be "in on" the communication. It's true that the hearing interpreter still won't feel the client rapport that would exist if s/he was working alone. Maybe that's life.

The most interesting Deaf-Hearing team I have worked on is one where I did very little and yet benefitted markedly. I went to a Deaf Shabbaton where many Deaf people came to a Hearing synagogue and participated in a Jewish Shabbat (Sabbath) service. Afterwards there was a dinner mainly for the Deaf guests with interested hearing people also attending. For the service, one of the Deaf participants was a Deaf Israeli who knew English, ASL, and Shasi (Israeli Sign Language). The Jewish service is scripted, that is everyone reads from the siddur (prayerbook), sometimes aloud, sometimes to oneself. I sat in the congregation and signed the beginning of each new section to the Deaf interpreter, who then read the Hebrew and interpreted it into ASL. I would still sign the beginning of new sections to the interpreter so he could keep pace with the sh'lach tsibbur (prayer leader). I benefited greatly because I got to see someone who was fluent in Hebrew give his take on how the ideas of the text could be communicated into ASL. Hope your career will also team (teem) with blessings!

title: Visual Language Interpreting/Teams


text:
Canadian History/Preface

The following is a Wikibook textbook on Canadian history. It is comprised of information compiled from various sources listed within the Bibliography by individuals like yourself. A Wikibook can be edited by anyone who wants to expand the usability and correctness of the work, however, please do not contribute any works that you do not hold the copyright to.

If you find that this textbook is incomplete, feel free to fill in the blanks.

Continue to the Introduction ›

title: Canadian History/Preface


text:
Canadian History/Precolonial

‹ Back to the Introduction

Upon reaching North America these newcomers found an abundance of prey and land and spread across the continent ...

Discuss how they spread, then in the next chapter talk about the various "Native" people.

Forward to the People of the Lands ›

title: Canadian History/Precolonial


text:
General Chemistry/Constants

Useful Physical/Chemical Constants
These constants were obtained from The NIST Reference on Constants, Units and Uncertainty.

Chimica generale/Costanti

title: General Chemistry/Constants


text:
General Chemistry/Overview of bonding

Introduction to Bonding
Put simply, chemical bonding join atoms together to form more complex structures (like molecules or crystals). Bonds can form between atoms of the same element, or between atoms of different elements. There are several types of chemical bonding which have different properties and give rise to different structures.

In many cases, atoms try to react to form valence shells containing eight electrons. The octet rule describes this, but it also has many exceptions

Chemical bonding is one of the most crucial concepts in the study of chemistry. In fact, the properties of materials are basically defined by the type and number of atoms they contain and how they are bonded together.

So far, you have seen examples of intramolecular bonds. These bonds connect atoms into molecules or whole crystals. There are also intermolecular bonds that connect molecules into large substances. These are also called intermolecular forces, or IMF. IMF are weaker than intramolecular bonds, and as they do not permanently join two molecules or ions, it is generally considered incorrect to refer to them as bonds. Sometimes, a substance will not have both IMF and intramolecular bonds. In the case of ionic crystals (like salt) or covalent networks (like diamond), the solid is made out of a network of intramolecular bonds connecting all the component atoms or ions in a repeating pattern, with no separate units to be attracted to each other by IMF. In the case of metallic bonding, the atoms are all interconnected into one large piece of metal, but the electrons move freely rather than being confined to the static bonds of a crystal lattice or covalent network.

title: General Chemistry/Overview of bonding


text:
General Chemistry/Ionic bonding

What are ions?
Ions are atoms or molecules which are electrically charged. Cations are positively charged and anions carry a negative charge. Ions form when atoms gain or lose electrons. Since electrons are negatively charged, an atom that loses one or more electrons will become positively charged; an atom that gains one or more electrons becomes negatively charged.

Description of Ionic Bonding
Ionic bonding is the attraction between positively- and negatively-charged ions. These oppositely charged ions attract each other to form ionic networks (or lattices). Electrostatics explains why this happens: opposite charges attract and like charges repel. When many ions attract each other, they form large, ordered, crystal lattices in which each ion is surrounded by ions of the opposite charge. Generally, when metals react with non-metals, electrons are transferred from the metals to the non-metals (this is because metals tend to have relatively low ionization energy and non-metals tend to have high electron affinity). The metals form positively-charged ions and the non-metals form negatively-charged ions. The smallest unit of an ionic compound is the formula unit, but this unit merely reflects that ratio of ions that leads to neutrality of the whole crystal, e.g. NaCl or MgCl2. One cannot distinguish individual NaCl or MgCl2 molecules in the structure.

It is however possible that the stacking consists of molecular ions like NH4+ and NO3- in ammonium nitrate. In such structures, the ions are charged molecules rather than charged atoms.

Ionic bonding may also be referred to as electrovalent bonding.

Characteristics
Example ionic compounds: Sodium chloride ($$NaCl$$), potassium nitrate ($$KNO_3$$).

Ionically bonded substances typically have the following characteristics.

In general the forces keeping the lattice together depend on the product of the charges of the ions it consists of. A comparison e.g. of NaCl (+1)*(-1) to MgO (+2)*(-2) shows that magnesium oxide is kept together much more strongly -roughly 4 times- than sodium chloride. This is why sodium chloride has a much lower melting point and also dissolves much more easily in a solvent like water than magnesium oxide does.
 * High melting point (solid at room temperature)
 * Hard but brittle (can shatter)
 * Many dissolve in water
 * Conductors of electricity when dissolved or melted

Solubility
Most ionic compounds are soluble in polar solvents. Polar solvents are simply solvents that have molecules with positive and negative poles. The most common example of a polar solvent is water (H2O).

The reason that they are soluble in polar solvents is because the positive ions are attracted to the negative pole of the solvent and the negative ions are attracted to the positive pole of the solvent. Due to this, the ionic compound dissociates or splits in the solvent into its constituent ions.

For example, H2O is composed of relatively more positive hydrogen atoms and relatively more negative oxygen atoms. When an ionic compound like NaCl is added to the water, the positive ions will be attracted to the more negative oxygen atoms and negative ions will be attracted to the more positive hydrogen atoms.

This is a very useful property of many ionic compounds, but not all, as there are exceptions where certain compounds cannot be dissolved in certain polar solvents.

Conduction
For a substance to conduct electricity, there must be some carrier of charge. For example, in metals, what transports the charge is the mobile electrons surrounding the positive ions.

However, in the solid state, ionic compounds lack any mobile particle capable of carrying charge as the ions cannot move within the lattice because the electrostatic force holding them in place is extremely strong. This changes when the compound is dissolved or molten. When dissolved, the ions dissociate and are capable of moving around. The same is true for molten ionic compounds. Which is why molten and dissolved ionic compounds can conduct electricity, while solid ionic compounds cannot.

Formation
Ionic bonding occurs when metals and non-metals chemically react. As a result of its low ionization energy, a metal atom is not destabilized very much if it loses electrons to form a complete valence shell and becomes positively charged. As its affinity is rather large, a non-metal is stabilized rather strongly by gaining electrons to complete its valence shell and become negatively charged. When metals and non-metals react, the metals lose electrons by transferring them to the non-metals, which gain them. The total process -a small loss plus a large gain- leads to a net lowering of the energy. Consequently, ions are formed, which instantly attract each other leading to ionic bonding.

For instance, in the reaction of Na (sodium) and Cl (chlorine), each Cl atom takes one electron from a Na atom. Therefore each Na becomes a Na+ cation and each Cl atom becomes a Cl- anion. Due to their opposite charges, they attract each other and are joined by millions and millions of other ions to form an ionic lattice. The lattice energy that results from this massive collective stacking further stabilizes the new compound. The formula (ratio of positive to negative ions) in the lattice is NaCl, i.e. there are equal numbers of positive and negative charges ensuring neutrality.

The charges must balance because otherwise the repulsion between the majority charges would become prohibitive. In the case of magnesium chloride, the magnesium atom gives up two electrons to become stable. Note that it is in the second group, so it has two valence electrons. The chlorine atom can only accept one electron, so there must be two chlorine ions for each magnesium ion. Therefore, the formula for magnesium chloride is MgCl2. If magnesium oxide were forming, the formula would be MgO because oxygen can accept both of magnesium's electrons.

It should also be noted that some atoms can form more than one ion. This usually happens with the transition metals. For instance Fe (iron) can become Fe2+ (called iron(II) or -by an older name- ferrous). Fe can also become Fe3+ (called iron(III) or -sometimes still- ferric).

Common Ions
Ionic bonding typically occurs in reactions between a metal and non-metal, but there are also certain molecules called polyatomic ions that undergo ionic bonding. Within these polyatomic ions, there can be covalent (or polar) bonding, but as a unit it undergoes ionic bonding. There are countless polyatomic ions, but you should be familiar with the most common ones. You would be well advised to memorize these ions.

Introdução à Química/Ligação iônica

title: General Chemistry/Ionic bonding


text:
Talk:General Chemistry/Ionic bonding

A couple of images you may want to pinch here ionic bond Theresa knott 15:27, 11 May 2004 (UTC)

title: Talk:General Chemistry/Ionic bonding