text:
Talk:Medical Equipment/Peak Flow Meter

Contribution history from Peak flow meter

 * (cur) (last) 11:40, 3 September 2006 SB Johnny (Talk | contribs) (→Usage - readding usage section for transwiki to wikibooks, I will revert this in a few minutes.)
 * (cur) (last) 06:13, 28 August 2006 63.173.108.175 (Talk) (→See also)
 * (cur) (last) 22:28, 31 July 2006 Davidruben (Talk | contribs) (Ok removed "how to guide", but taking of best of three readings and ploting results/symptoms is standard practice as given by UK guideline link)
 * (cur) (last) 10:26, 31 July 2006 Xyzzyplugh (Talk | contribs) (removed Usage section, see talk page)
 * (cur) (last) 05:28, 6 July 2006 Santtus (Talk | contribs) (+howto tag)
 * (cur) (last) 12:49, 25 June 2006 Lkinkade (Talk | contribs) m (clean up using AWB)
 * (cur) (last) 19:09, 19 June 2006 Santtus (Talk | contribs)
 * (cur) (last) 15:39, 6 June 2006 Davidruben (Talk | contribs) (→Usage - see talk page re style of this section - patients often not taught or forget. Simplified info useful and highlights, in this an encyclopedia, that it involves some care to record)
 * (cur) (last) 15:33, 6 June 2006 Davidruben (Talk | contribs) (→Usage - add intro sentance to this section)
 * (cur) (last) 15:26, 6 June 2006 Davidruben (Talk | contribs) (→Scales - add ref to equations for predicted childrens PEFR, subseqnetly modified by charts for EU scale)
 * (cur) (last) 15:15, 6 June 2006 Davidruben (Talk | contribs) (→Scales - explain - in UK the Wright scale should be depreciated - although many patienst & doctors still have old Mini-Wright meters not calibrated to the new EU scale ! Add convertion link)
 * (cur) (last) 12:16, 6 June 2006 Davidruben (Talk | contribs) (add links to predictive normal-values charts Wright & EU scales. Also to UK British Thoracic Society PEFR recording chart)
 * (cur) (last) 11:03, 6 June 2006 Davidruben (Talk | contribs) (→Usage - change is not immediate and need give time for full effect (though patient may be improving within just few minutes).)
 * (cur) (last) 11:01, 6 June 2006 Davidruben (Talk | contribs) (These usage details consititute "Peak Flow" description (no need separate article) & are true for all devices (ie zero first), and patient delivers short fast full blow. Best 3 readings in UK)
 * (cur) (last) 10:05, 6 June 2006 Hooperbloob (Talk | contribs) (rm usage section, this will be on device itself and Wikipedia should not be providing tutorials on medical equipment)
 * (cur) (last) 09:58, 6 June 2006 Tom harrison (Talk | contribs) m (Reverted edits by 82.69.113.156 (talk) to last version by BlaiseFEgan)
 * (cur) (last) 09:56, 6 June 2006 82.69.113.156 (Talk) (→Scales)
 * (cur) (last) 09:54, 6 June 2006 82.69.113.156 (Talk) (→Usage)
 * (cur) (last) 09:53, 6 June 2006 82.69.113.156 (Talk) (→Scales)
 * (cur) (last) 09:48, 6 June 2006 82.69.113.156 (Talk) (→Scales)
 * (cur) (last) 16:00, 17 May 2006 BlaiseFEgan (Talk | contribs)
 * (cur) (last) 16:39, 16 April 2006 Hooperbloob (Talk | contribs) (+cat)
 * (cur) (last) 23:04, 6 April 2006 Roy da Vinci (Talk | contribs) m
 * (cur) (last) 17:06, 20 March 2006 Aapo Laitinen (Talk | contribs) m (further wikifying, +cat)
 * (cur) (last) 14:35, 25 February 2006 Trjumpet (Talk | contribs) (→Usage)
 * (cur) (last) 16:00, 5 January 2006 Heron (Talk | contribs) m (Reverted edits by Finejon (talk) to last version by 136.2.1.101)
 * (cur) (last) 09:40, 5 January 2006 Finejon (Talk | contribs) m (External Links section created and link added to page on peak flow meters.)
 * (cur) (last) 11:50, 20 October 2005 136.2.1.101 (Talk)
 * (cur) (last) 21:48, 21 August 2005 Davidruben (Talk | contribs) (→Peak Flow Meter - PEFR measures air flow and restriction, not lung capacity)
 * (cur) (last) 10:58, 3 May 2005 146.6.111.57 (Talk)

title: Talk:Medical Equipment/Peak Flow Meter


text:
Developing Genealogy Web-Pages/Common Questions

Do I Need To Be Connected
... to the Internet to create HTML Pages?

No, in fact you don't need to be connected to the Internet at all to create web-pages. If the pages are not ready for publication or the site is not ready ... the pages can be stored on your computer, a ZIP drive, a flash drive, wherever.

I have spent months generating entire web-sites offline prior to "publishing" them online.

Using a Macintosh Computer
If you are using TextEdit on a Macintosh computer, the steps for creating a web-page are a little different than when using Windows Notepad.

From the Format Menu, you must first select Make Plain Text and then change the preferences under the Saving header by unchecking the box for Append '.txt' Extension to Plain Text Files.

Also, the default preferences are set to show .html as they would appear in a browser, which will not allow you to edit them. To fix this, check the Ignore Rich Text Commands in HTML Files under the Rich Text Processing header.

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


text:
Wikijunior talk:How Things Work/Laser

What else does this page need? It's pretty basic right now. Does it need more technical detail? Thanks. — RJHall 17:41, 3 September 2006 (UTC)

Added a section about ruby laser
I added some illustrations of a ruby laser. I took some artistic license to make the pictures clearer and hopefully easier to understand. They need to be checked for accuracy. They might need to be resized (I left most of them about half their full size). Also need to know if the brightness/contrast is ok on other monitors.

I also added a description which needs to be checked for accuracy, without making it too technical. I wonder if the heading "How a Ruby Laser Works" might be deleted, and just mention in the introductory paragraph that the section describes the working of a ruby laser? Maybe there's no need for the sub-headings at all? --Mcgill 18:17, 23 September 2006 (UTC)

Hi, I think the technical level is appropriate for the wikijunior level-no problems there.

The section on the internals of the ruby rod/silvered vessel is maybe a little light on content-suggest that you make note of the highly silvered/reflective vessel that focusses the flash-tube energy into the rod, as well as the necessity for water cooling within the vessel-The laser is very hot when working.

Otherwise good explanation! --Richard 02:41, 26 September 2006 (UTC)

 * Thanks for the advice. I added your points to the text. Probably some omissions and errors remaining in the ruby laser section, if anyone wants to make corrections.  I think other sections need to be simplified if they're going to be understood by the average 8-year-old. --Mcgill 05:46, 26 September 2006 (UTC)

title: Wikijunior talk:How Things Work/Laser


text:
User:Digitalme/monobook.js

// function addlilink(tabs, url, name, id, title, key){ var na = document.createElement('a'); na.href = url; na.appendChild(document.createTextNode(name)); var li = document.createElement('li'); if(id) li.id = id; li.appendChild(na); tabs.appendChild(li); if(id) {       if(key && title) {           ta[id] = [key, title]; }       else if(key) {           ta[id] = [key, '']; }       else if(title) {           ta[id] = ['', title]; }   }    // re-render the title and accesskeys from existing code in wikibits.js    akeytt; return li; }

function tagnote(string) { if (!string){return;} var f = document.editform, t = f.wpTextbox1; t.value = "" + "\n" + t.value; f.wpSummary.value = "transwikied"; document.getElementById('wpMinoredit').checked=true; f.submit; }

$(dbtabs) function dbtabs { if (document.title.indexOf('Editing ') == -1){return;} var tabs = document.getElementById('p-cactions').getElementsByTagName('ul')[0]; addlilink(tabs, 'javascript:tagnote("m2wv")', 'transwikied', ''); } //

title: User:Digitalme/monobook.js


text:
User:Engram~enwikibooks

Æâ

title: User:Engram~enwikibooks


text:
Cookbook:Flapjacks (Traditional Scottish Recipe)

Scottish flapjacks are a type of baked bar dessert made with oats.

Ingredients

 * 75 g butter or margarine
 * 50–75 g light brown sugar
 * 1 tablespoon golden syrup
 * 175 g porridge oats

Procedure

 * 1) Put the butter or margarine, sugar, and golden syrup into a saucepan, and stir over a low heat until the fat and sugar have melted.
 * 2) Add the porridge oats and blend thoroughly.
 * 3) Press into a well-greased 18 cm square sandwich tin.
 * 4) Bake in the centre of a moderate oven at 180°C (350°F / gas mark 4) for 25 minutes or until evenly golden brown.
 * 5) Cut into rectangles in the tin whilst warm.
 * 6) Allow to become almost cold in the tin before removing.
 * 7) Enjoy!

Notes, tips, and variations

 * Replace the sugar and golden syrup with 75 g of honey.
 * Add 50 g of raisins.


text:
User:Seven-League Bot

Hello ; I'm guillom's bot. In fairy tales, seven-league boots are magic boots which allow the wearer to take great strides —seven leagues each step— resulting in great speed (this is precisely what a bot is asked).

If I may help you doing a systematic or boring task, please let me know.

title: User:Seven-League Bot


text: User talk:Seven-League Bot

title: User talk:Seven-League Bot


text:
User:Guillom/Images without license

Statistics

 * Last 1000 untagged images
 * Untagged Images per User

Tools

 * User:Seven-League Bot
 * w:fr:User:Guillom/monobook/images.js
 * User:Seven-League Bot/monobook.js
 * User:Seven-League Bot/monobook/images.js

Image tagging
Templates:

 * Images without license which are used:
 * Images without license which are not used:
 * For the uploader: Image:name.png

When it comes to template used in user discussion, I think that you should use a modified version of it, without image name in section title and with list of images instead of a single image. You also should add a notice that the message was generated by a bot. --Derbeth talk 21:41, 3 September 2006 (UTC)

image tags
Hi Guillom,

This is waht we're looking for so far.

 * For the image page itself, use: No license
 * For the 3 users who have hundreds of images uploaded without tags, it might be better to use a modified template that adds them to their own separate category (e.g.: Images without copyright uploaded by )...if the bot can wait on those, that might be a good idea.

 * For the uploading user, use: Image copyright
 * If possible, it might be nice to add Imgd to pages using the image (after the cleanup is completed, this template will be altered to say that the images were deleted, and why)

Let me know what you think. -- SB_Johnny | talk 14:37, 7 October 2006 (UTC)

 * Hi johnny,
 * Everything's ok except the last part. Tagging all pages where there are tagged images will be really much work. I'll see if I can do it, but I can't promise for this part.
 * About the uploading user, do we agree on the fact I should warn him only once, even if there are several of his images tagged?
 * guillom 20:34, 9 October 2006 (UTC)

 * Ok, I figured that might not work too well.
 * I don't know about the once-warning thing... I'd like to make sure they know which images have problems. Though for the ones with 100s of images, obviously not (I think the bot should just leave those ones alone).
 * Another idea might be to have a dry run that just has the bot leave a notice on the talk page with a link to their list of untagged on the tolserver, so, for example, User:JamBam16 would recieve a warning and a link to this page (holy crap! look at his contribs!)
 * Going back to irc now... -- SB_Johnny | talk 22:17, 10 October 2006 (UTC)
 * About tagging pages containing images without license: I think we could avoid it by using the MediaWiki:Sitenotice to warn everybody.
 * About the once-warning: yes, I think the best solution is to provide the link to their untagged images. The question is: I don't know if the images « tagged as untagged » still appear in the list. We should try and see. Another solution is to provide a link to the upload log of the user.
 * Last thing: Where should I redirect people who have questions about licenses? I will add a message on my talk page to warn people I won't answer them, so I have to direct them to such a page. guillom 10:12, 13 October 2006 (UTC)

title: User:Guillom/Images without license


text:
User:Seven-League Bot/monobook.js

/*  */

var ajax = new objAJAX var cookies = new objCookies

//objAJAX function objAJAX { // AJAX taken from http://jibbering.com/2002/4/httprequest.html. Thanx :)       this.conn = false        /*@cc_on @*/        /*@if (@_jscript_version >= 5)        // JScript gives us Conditional compilation, we can cope with old IE versions.        // and security blocked creation of the objects.        try {                this.conn = new ActiveXObject("Msxml2.XMLHTTP")        } catch (e) {                try {                        this.conn = new ActiveXObject("Microsoft.XMLHTTP")                } catch (E) {                        this.conn = false                }        }        @end @*/        if (!this.conn && typeof XMLHttpRequest != 'undefined') {                try {                        this.conn = new XMLHttpRequest                } catch (e) {                        this.conn =false                }        }        if (!this.conn && window.createRequest) {                try {                        this.conn = window.createRequest } catch (e) { this.conn = false }       }

this.url = null this.requestType = "GET" this.unsync = true this.parser = new objHTMLparser }

objAJAX.prototype.sendRequest = function (url, type, unsync, data) { if (!this.conn) return null if (this.conn.readyState != 0 && this.conn.readyState != 4) return "busy" if (url) this.url = url if (type) this.requestType = type if (unsync != null) this.unsync = unsync //alert(this.requestType + " ++ " + this.url + " ++ " + this.unsync) this.conn.open(this.requestType, this.url, this.unsync) this.conn.send(data) }

objAJAX.prototype.getResult = function { if (!this.conn) return null return this.conn.responseText }

objAJAX.prototype.abort = function { this.conn.onreadystatechange = null this.conn.abort }

//--ObjCookie

function objCookies { this.value = null this.name = null this.expires = null }

objCookies.prototype.get = function (which) { this.allcookies = document.cookie var start = this.allcookies.indexOf("; " + which + "=") if (start == -1) { start = this.allcookies.indexOf(which + "=") if (start != 0) return null } else start += "; ".length this.name = which var end = this.allcookies.indexOf(";", start) if (end == -1) end = this.allcookies.length this.value = this.allcookies.substring(start + which.length + 1, end) var arr = this.allcookies.substring(start, this.allcookies.length).split("; ") this.expires = null if (arr.length > 0) if (/expires=/.test(arr[1])) this.expires = arr[1].substring("expires=".length, arr[1].length) return this.value }

objCookies.prototype.set = function (name, value, expires) { document.cookie = name + "=" + value + ";" + (expires ? "expires=" + expires + ";" : "") + "path=/;" + "domain=fr.wikipedia.org;" this.allcookies = document.cookie }

objCookies.prototype.setWithDelay = function (name, value, delay) { // delay is in millisecond var d = new Date d.setTime(d.getTime + delay) this.set(name, value, d.toGMTString) }

objCookies.prototype.kill = function (which) { if (this.get(which)) this.set(which, null, "Thu, 01-Jan-70 00:00:01 GMT") }

//--objHTMLparser

function objHTMLparser(str) { this.html = str }

objHTMLparser.prototype.parse = function (elmt, str) { if (str !== null) this.html = str if (this.html.indexOf("<" + elmt) == -1 || this.html.indexOf("") == -1) return null var arr1 = this.html.split("<" + elmt) var elmts = new Array for (var cpt = 1 ; cpt < arr1.length ; cpt++) { var el = new Object el.innerHTML = arr1[cpt].substring(arr1[cpt].indexOf(">"), arr1[cpt].length).split("")[0].split(/\s/g) for (var cpt1 = 1 ; cpt1 < prop.length ; cpt1++) { if (prop[cpt1].indexOf("=") != -1) el[prop[cpt1]] = true else el[prop[cpt1].split("=")[0]] = prop[cpt1].substring(prop[cpt1].indexOf("="), prop[cpt1].length) }		elmts[cpt-1] = el	} this.elmts[elmt] = elmts }

function setSummary(str) {	document.editform.wpSummary.value = str }

function addToSummary(str) {	document.editform.wpSummary.value += " " + str }

function setTextarea (str) {	document.editform.wpTextbox1.value = str }

function getArticleName {       var strOut = document.title // case search if (strOut == "Rechercher - Wikipédia") return document.getElementById("lsearchbox").value // case article being modified strOut = strOut.replace("modification de ", "").replace(" - Modifier", "")

strOut = strOut.replace(" - Prévisualiser", "").replace(" - Wikipédia", "") return strOut }

function insertAfter(parent, node, referenceNode) {	parent.insertBefore(node, referenceNode.nextSibling) }

/* ================================================== CORRECTEUR ===================================================== */

document.write(' ');

/* ============================================== IMAGES SANS LICENCE ================================================= */

document.write(' ');

/* ================================================================================================================= */

/* */

title: User:Seven-League Bot/monobook.js


text:
User:Seven-League Bot/monobook/images.js

/* */

function addButtonLicenseInconnue { if (decodeURI(window.location.href).indexOf("Image:") > 0) { ul = document.getElementById("filetoc"); if (!ul) return; var a = document.createElement("a"); var uls = document.getElementsByTagName("ul"); var usr = null; for (var cpt = 0 ; cpt < uls.length && !usr ; cpt++) if (uls[cpt].getAttribute("class") == "special") usr = uls[cpt]; var lis = usr.getElementsByTagName("li"); var as = lis[lis.length -1].getElementsByTagName("a"); usr = null; for (var cpt = 0 ; cpt < as.length && !usr; cpt++) if (decodeURI(as[cpt].getAttribute("href")).indexOf("User:") > 0) usr = decodeURI(as[cpt].innerHTML); a.innerHTML = "No License"; a.href = "javascript: void(0);"; if (a.attachEvent) a.attachEvent("onclick", addLicenseInconnueImage); else a.setAttribute("onclick", "javascript: addLicenseInconnueImage"); var li = document.createElement("li"); li.appendChild(a); li.appendChild(document.createTextNode("   ")); var a1 = document.createElement("a"); a1.innerHTML = "Warn " + usr; a1.href = "javascript: void(0);"; if (a1.attachEvent) a1.attachEvent("onclick", addLicenseInconnueUser); else a1.setAttribute("onclick", "javascript: addLicenseInconnueUser"); li.appendChild(a1); li.id = "liAvertissement"; ul.appendChild(li); } //if }

addLoadEvent(addButtonLicenseInconnue);

function addLicenseInconnueImage { addMessage("Leaving No license template..."); var article = getArticleName; //on the image page var ajax2 = new objAJAX; ajax2.textBox = " ~"; ajax2.summary = "Warning: Image copyright problem"; ajax2.clearTextBox = false; ajax2.article = article; ajax2.newSection = true; ajax2.finishedMessage = ajax2.article + ": Template left"; editArticle(ajax2, article); }

function addLicenseInconnueUser { addMessage("Sending message to the uploader..."); //on the user page var uls = document.getElementsByTagName("ul"); var tmp = null; for (var cpt = 0 ; cpt < uls.length && !tmp ; cpt++) if (uls[cpt].getAttribute("class") == "special") tmp = uls[cpt]; var lis = tmp.getElementsByTagName("li"); var as = lis[lis.length -1].getElementsByTagName("a"); var article = null; for (var cpt = 0 ; cpt < as.length && !article ; cpt++) if (decodeURI(as[cpt].getAttribute("href")).indexOf("User:") > 0) article = decodeURI(as[cpt].innerHTML); var ajax2 = new objAJAX; ajax2.textBox = " ~"; ajax2.summary = "Images copyright problem"; ajax2.clearTextBox = false; ajax2.article = "User_talk:" + article; ajax2.newSection = true; ajax2.finishedMessage = article + ": user warned"; editArticle(ajax2); }

function editArticle(ajaxObject) { //first we read the time stamp var url = "/w/index.php?title=" + ajaxObject.article + "&action=edit" + (ajaxObject.newSection ? "&section=new" : ""); ajaxObject.conn.onreadystatechange = function { if (ajaxObject.conn.readyState == 4) { //getElementsByName doesn't work (??), let's get it manually var doc = ajaxObject.conn.responseXML; var ts = 0, token = 0; var inputs = doc.getElementsByTagName("input"); for (var cpt = 0 ; cpt < inputs.length && !ts; cpt++) { if (inputs[cpt].getAttribute("name") == "wpEdittime") ts = inputs[cpt].value; }                               var as = 0; for (var cpt = 0 ; cpt < inputs.length && !as; cpt++) { if (inputs[cpt].getAttribute("name") == "wpAutoSummary") as = inputs[cpt].value; }                               var st = 0; for (var cpt = 0 ; cpt < inputs.length && !st; cpt++) { if (inputs[cpt].getAttribute("name") == "wpStarttime") st = inputs[cpt].value; }                               if (ajaxObject.clearTextBox) var tb = ""; else var tb = doc.getElementById("wpTextbox1").value + String.fromCharCode(13, 13); for (var cpt = 0 ; cpt < inputs.length && !token; cpt++) { if (inputs[cpt].getAttribute("name") == "wpEditToken") token = inputs[cpt].value; }                               if (ts) { submitArticle(ajaxObject, ts, token, tb, as, st); }                       }                }        ajaxObject.conn.open("GET", url, true) ajaxObject.conn.overrideMimeType('text/xml'); ajaxObject.conn.send(null); }

function submitArticle(ajaxObject, ts, tk, tb, as, st) { //submit (save) the page var url = "/w/index.php?title=" + ajaxObject.article + "&action=submit"; var params = "wpEdittime=" + ts + "&wpTextbox1=" + tb + ajaxObject.textBox + "&wpSummary=" + ajaxObject.summary + "&wpEditToken=" + tk + "&wpAutoSummary=" + as + (ajaxObject.newSection ? "&wpSection=new" : "") + "&wpStarttime=" + st;

ajaxObject.conn.onreadystatechange = function { if (ajaxObject.conn.readyState == 4) { try { if (ajaxObject.conn.responseXML.getElementsByTagName("form").length == 1) addMessage(null, " Succès ! " + ajaxObject.finishedMessage); else addMessage("Failure: " + ajaxObject.article) } catch (e) { addMessage("Failure: " + ajaxObject.article) } }               }        ajaxObject.conn.open('POST', url, true); ajaxObject.conn.setRequestHeader("Content-Type", "application/x-www-form-urlencoded; charset=UTF-8"); ajaxObject.conn.setRequestHeader("Content-length", params.length); ajaxObject.conn.setRequestHeader("Connection", "close"); ajaxObject.conn.send(params); }

function addMessage(msg, innerHTML, clear) { var div = document.getElementById("messageUtilisateur"); if (!div) { div = document.createElement("div"); div.className = "messageUtilisateur"; div.id = "messageUtilisateur"; var bcont = document.getElementById("bodyContent"); try { bcont.insertBefore(div, bcont.getElementsByTagName("p")[0]); } catch (e) { try { bcont.insertBefore(div, bcont.getElementsByTagName("div")[0]); } catch(e) { } }       }        if (clear) div.innerHTML = ""; if (msg) { var txtNode = document.createTextNode(msg); div.appendChild(txtNode); } else if (innerHTML) { div.innerHTML += innerHTML; }       div.appendChild(document.createElement("br")); }

/* */


text:
User talk:Thiefxray~enwikibooks

Hi i play mapleSEA in server aquila IGN of aquila: lv 47 bowman Axedup(currently in ludibrium pq)

Your account will be renamed
Hello,

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

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

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

Sorry for the inconvenience.

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

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

title: User talk:Thiefxray~enwikibooks


text:
User:Thiefxray~enwikibooks

I play mapleSea aquila my ign is axedup

title: User:Thiefxray~enwikibooks


text:
Template:Wikijunior article stub

This template adds page to Category:Wikijunior Stubs. With no parameters, it produces the message Optional parameter describes what sort of page it is. For example,

would produce the message

title: Template:Wikijunior article stub


text:
GIMP/Create a Stone Texture

This tutorial describes the creation of stone textures.

 * 1: We start with Solid Noise (  Filters > Render > Clouds > Solid Noise). Remember to tick the Tileable check box.

You can modify this a bit, but its effect may appear negative in the final result. You will see a rather smooth texture.

If you plan to make your image seamless, perhaps for usage in a 3D application, you might want to do a Gaussian Blur (  Filters > Blur > Gaussian Blur) at 100 to make the texture more neutral.

-->

 * 2: Now you have to add some stony grit on it. This can be done with Scatter RGB (  Filters > Noise > Scatter RGB) with Independent RGB off and the values very low (Recommended around 0.05 per channel)

 * 3: Create a New Layer using the New Layer button [[Image:Newlayer.png]] on the layer window (If you don't have one, in The Gimp's main window, go to   File > Dialogs > Create New Doc > Layers, Channels, and Paths.) and do the Plasma filter (  Filter > Render > Clouds > Plasma). Try to get a good balance of black and white. Don't forget to set the Mode in the layer window to "Value" (not "Normal").

Moving the turbulence up just a little can also help if your aiming to make the texture seamless.

 * 4: Now you have to use Lighting Effects (  Filters > Light Effects > Lighting Effects), go to the bump map tab and choose the layer with the rendered Plasma. Place the light source as desired. Let the plug-in do the rest.

If you need to make your texture seamless, you probably want to do a Bump map instead, which has the same lighting for all pixels.

title: GIMP/Create a Stone Texture


text:
Category:Wikijunior Stubs

These are stubs from Wikijunior. To place an article on this list, put Wikijunior article stub at the top of the page.

ja:Category:ウィキジュニアのスタブ

title: Category:Wikijunior Stubs


text:
User:Eloquence

/bee

title: User:Eloquence


text:
User:Eloquence/bee

=Contents=
 * Preface - A Background of European History
 * Chapter 01 - The Crises of the Middle Ages
 * Chapter 02 - Renaissance Europe
 * Chapter 03 - Exploration and Discovery
 * Chapter 04 - Challenges to Spiritual Authority
 * Chapter 05 - Religious Wars in Europe
 * Chapter 06 - Absolutism in Europe
 * Chapter 07 - Scientific Revolution and Enlightenment
 * Chapter 08 - Revolution in France
 * Chapter 09 - Napoleon Bonaparte and the Rise of Nationalism
 * Chapter 10 - Age Of Revolutions
 * Chapter 11 - European Imperialism and Nationalism
 * Chapter 12 - World War I
 * Chapter 13 - Europe: 1918 to 1945
 * Chapter 14 - Europe: 1945 to Present
 * Glossary
 * A Brief Outline of European History
 * Authors
 * Bibliography
 * GNU Free Documentation License

=Preface - A Background of European History=

=Chapter 01. - The Crises of the Middle Ages=

=Chapter 02. - Renaissance Europe=

=Chapter 03. - Exploration and Discovery=

=Chapter 04. - Challenges to Spiritual Authority=

=Chapter 05. - Religious Wars in Europe=

=Chapter 06. - Absolutism in Europe=

=Chapter 07. - Scientific Revolution and Enlightenment=

=Chapter 08. - Revolution in France=

=Chapter 09. - Napoleon Bonaparte and the Rise of Nationalism=

=Chapter 10. - Age Of Revolutions=

=Chapter 11. - European Imperialism and Nationalism=

=Chapter 12. - World War I=

=Chapter 13. - Europe: 1918 to 1945=

=Chapter 14. - Europe: 1945 to Present=

=Glossary=

=A Brief Outline of European History=

=Authors=

=Bibliography=

=GNU Free Documentation License=

title: User:Eloquence/bee


text:
Technical Theatre/Lighting/Gobos

A Gobo (derived from Go Between or Goes Before Optics) is a thin piece of metal, wood, or glass used to used to modify the shape of the projected light. It is generally used with Ellipsoidal Reflector Spots, which normally provide a specific slot for gobo use. Old soda cans make a cheap replacement for custom made metal gobos, but don't last as long as professionally made gobos.

Plastic gobos—which are generally custom made—are available when a pattern is needed in color and glass does not suffice. However, these thin plastic films generally need to be used with special cooling elements to prevent melting them. A lapse in the cooling apparatus, even for just a few seconds, can cause an expensive gobo to be ruined.

Glass gobos can become very complex, and can make use of coloring, much like a stained glass window.

Most manufacturers produce a swatch book of their gobos, and like gels they are referred to by a number rather than name. For example, most manufacturers offer a gobo of a window, but they are all slightly different. So instead of calling it window, it would be identified as gobo 77143

title: Technical Theatre/Lighting/Gobos


text:
Category:Fermented recipes

Recipes prepared using fermentation.

ko:분류:발효 요리

title: Category:Fermented recipes


text:
Cookbook:Horse

Horse produce a meat that is sweet, tender, low in fat, and high in protein. Just like beef and pork, in some societies there is a taboo regarding the consumption of horse meat.

Horse meat has about 40% less calories than even the leanest beef, while supplying 50% more protein and up to 30% more iron.

title: Cookbook:Horse


text:
Talk:Nanotechnology

Please add comments about things you would like to have included or sections that should be improved! (KristianMolhave 15:46, 5 June 2006 (UTC))

Can someone expand upon Surface Enhanced Raman Spectroscopy (SERS)?
Particularly these questions taken from the Wikipedia article (which isn't so good either).

 * I would appreciate more visual aids to elaborate on both the electromagnetic explanation (physical explanation) and charge-transfer complex (chemical explanation). I barely understand what charge-transfer complex means, but I have no idea how that links to SERS.
 * I like the tennis ball + spring system analogy presented on the Raman spectroscopy page. It could be cleaned up and with a few diagrams could make this article much more approachable to newcomers like myself.
 * To what extent do you need to understand quantum mechanics to begin interpreting Raman data, specifically SERS? How about electromagnetics? Could these prerequisites be simply motivated and explained in this article?
 * I keep hearing about selection rules, are these related to quantum mechanics somehow?
 * I also hear that understanding group theory helps explain Raman and a lot of spectroscopic techniques in general. Can someone help explain why?
 * I know it has something to do with symmetry and all these methods have something to do with squishing and twisting and bending chemical bonds, but the math gets very boring and uninteresting and it's easy to lose sight of why I'm learning it.
 * Can someone perhaps fix up the article to include some more contextual information like where near-IR, mid-IR, far-IR, etc. methods fit in, perhaps with some nice animated GIFs showing what goes on in each? 68.126.191.150 (discuss) 21:44, 20 April 2012 (UTC)

Size of article
Much excellent work has gone into this article since April, and it is now 45 KB long. Perhaps it is time to begin splitting it into several articles? If not now, what criteria do we use to determine when it should be split? ~ Nanobug 13:39, 28 August 2006 (UTC)

 * Yes it seems to be about 'split-up' time. I have been waiting for more contributors to join, so we can settle on a structure of the material, and once thats settled, then split it up (and then I like the idea that the whole book could be printed out in one go - but as it stands now its not suitable for printing as its mainly links in many sections) KristianMolhave 19:52, 28 August 2006 (UTC)

I checked some of the other wikibooks, as we would probably want to structure it similar to those, and it appears they all have a front page which is basically a table of contents to several other pages, each of which is a subpage of the first one. e.g. Acoustics points to Acoustics/Fundamentals_of_Acoustics. So once we agree on the name of the top page, we can create subpages for each of the major sections in a similar way. ~ Nanobug 16:16, 31 August 2006 (UTC)

I have split the article into subsections - right now just 7 sections. As some of these will grow theý can be put on individual pages and get links directly from the the main table of contents as they have done in other books. KristianMolhave 22:28, 24 September 2006 (UTC)

Search engines
How is Google Desktop relevant as a Nanotechnology Related Search Engine? That is like saying Google is useful for searching about nanotechnology, which it is, but listing it here is still not very helpful. Plus, its only useful at all if you have documents about nanotechnology on your hard drive, which many of the readers of this article will not. ~ Nanobug 16:37, 28 August 2006 (UTC)

 * I agree completely, but it is such a nice program that I thought it deserved the PR :-) if you do have lots of nanotech files on your hdd, google desktop is a wonderful tool to find what you want and things you thought you didn't even have. KristianMolhave 19:52, 28 August 2006 (UTC)

Article name
Looking at the Physics bookshelf, the names of this article, and the one on Microwiki, appear to be inconsistent with all the others, such as Astronomy, Engineering Thermodynamics, and Special relativity. Is there some reason these names were picked rather than something like Nanotechnology and Microtechnology, which currently just redirect to these articles? Perhaps the names of these two articles should be changed to make them more obvious and straightforward? ~ Nanobug 16:49, 28 August 2006 (UTC)

 * It could also be nanoscience and microfabrication and ... there are so many variations over the micro/nano theme. that's why I made redirects to something simple that I can remember and fairly unique so it can be found through search engines easily (though there are some uses of microwiki and nanowiki on the net already). If its confusing we can change it. KristianMolhave 19:52, 28 August 2006 (UTC)

Personally I think Nanowiki is confusing. It confuses the technology with the tool we are using to document the technology. I think we should just keep it simple and name it Nanotechnology, the most commonly used and searched for term. The fact that it also includes a lot of Nanoscience is not confusing, it is just that the technology depends so much on the science, just like many other fields, such as Biotechnology. ~ Nanobug 16:16, 31 August 2006 (UTC)

 * I have moved both books (microwiki and nanowiki) - and now theres a bit of work to be done changing links in the wikimedia; wikibooks subject pages; and wikipedia - but they can stay for a while since nanowiki/microwiki redirects. Better to all that now before we start adding images etc...--KristianMolhave 08:42, 4 September 2006 (UTC)

Edit by User:213.249.155.238
This edit was made to the ---Search engines--- section at 09:50, 5 September 2006. The edit was lost when I redid the pagemove, I didn't put it back in because it seems to go against the format of the surrounding sections. Edit was as follows, completely replaced the search engines section as it is currently:

 * ISI - Web of Science Database contains peer reviewed journals, their references and citations. Very useful tools such as 'find related papers', searches for papers that share the same references. This is the database behind the compilation of the journal citation factors.
 * Knovel - Online Handbook Collection and Database is an extensive collection of handbooks and tables.
 * PROLA - the Physical Review Online Archive searches Physical Review journals.
 * Rubber Bible Online is a physical chemistry handbook which contains tables of physical and chemical data.
 * Spin AIP Scitation searches related journals.
 * Web of Science by ISI generates the impact factors (see journals below).
 * Virtual Journal of Nanotechnlogy collectins nanotech related papers from non-nano spcialized journals

-- SB_Johnny | talk 10:17, 8 September 2006 (UTC)

We'll take it ;-) it looks better than the table. KristianMolhave 14:38, 8 September 2006 (UTC)

Talk page history
FYI: due to the copy paste of this article to a new one, and the subsequent revert and move of the article, somehow the history on this talk page before Sept 4 was lost (or at least I cannot find it). Fortunately the history on the main article page was not lost. ~ Nanobug 13:14, 13 September 2006 (UTC)
 * yes, I was in doubt about how to make the move from nanowiki to nanotechnology and sb-johnny helped me to get it right for the main page. But all edits are still visible on the talk page, so nothing is really lost. KristianMolhave 19:29, 13 September 2006 (UTC)

'Chat' about the future of the Nanotechnology wikibook
KristianMolhave 21:23, 21 November 2006 (UTC): I'm asking several people to join and contribute specific sections I know they have written about. I also hope to set up an editorial board for the book.

Structure of the book
The section on nanomaterials is based on quick attempt to divide them. I'm not sure of some other division wouldn't be more suitable. The introduction describes various ways of classifying nanomaterials and it could be done in still more ways. Comments on ways to divide this chapter are very welcome! KristianMolhave 18:58, 10 December 2006 (UTC)

If you would you like to contribute:
On the subject of the future of Nanotechnology wikibook: I'm wondering if you would like my help? I've never contributed to anything on neither Wikipedia nor Wikibooks before and I am being Swedish, so I might need some help with editing texts I've written (like spell-checking and such). But I am studying nanoscience and I believe I could contribute in areas like perhaps electron microscopy or some applications, like nanowires etc. I mean - of course I can add anything I want - I just wonder if someone know something that is more urgent or wanted (or something that this person feel is too boring to write him/her-self). Deity 23:25, 9 December 2006 (UTC)

 * Hi Deity - you are very welcome to add and edit where ever you feel you can contribute! The book is still just starting and I think it would be nice to have small sections on all subjects to sort of cover the entire subject minimally for a start. I hope it will be more appealing for people to add more material to a page that already contains material than a blank page. So if there is a rather empty section where you feel you already have material, know a lot, or would find it fun to contribute then please go ahead! If you would like someone to proof read it, you can email it to me first - but the wiki users are generally very good at helping proof reading so i would just upload it and we can take it from there.

Material is in preparation for the section on environmental nanotechnology, but just add to these pages if you want to, then we'll edit it together when the off line material gets uploaded. 18:58, 10 December 2006 (UTC)

Intorduction - Origins and Background
I'm a newbie...was surfing by and noticed the Wikibook title.

Perhaps someone more qualified than myself can contribute information to the Introduction that gives background to lay readers about both the origins of the term "nanotechnology" and its earliest roots.

What I do know is that the late Navy Commodore Grace Hopper is generally considered to have coined the term as early as the 1940s, when she was heading up a mainframe computer project, in cooperation with IBM, in the bowels of the Pentagon. I heard her give a first-hand account of the work she had done on this project, which pioneered the way for nanotechnology, in a speech she gave on the topic at a trade association (American Logistics Association) conference--in the context of emerging information technologies, problems with slow government payments to vendors/suppliers, and the potential for using electronic funds transfer (EFT) to address the problem--in the mid-1980s.

People working or studying in the nanotechnology field will no doubt have heard of Grace Hopper and may be able to more readily fill in these blanks on the Introduction's canvas.--Alangray53 14:37, 23 December 2006 (UTC)Alan Gray

Nanomagnetizm
Its good but ı think there must be some information about nanomagnetizm because we can see most interesting changes in magnetizm when we go from bulk to nano size.

Printable Version
I suggest this book should be printable and downloadable as PDF because that will ease most low-budget people to take this book entirely in one attempt.Robin688 (discuss • contribs) 15:59, 2 January 2012 (UTC)

title: Talk:Nanotechnology


text:
Talk:Microtechnology

Please add any comments you feel like here!--KristianMolhave 16:26, 29 June 2006 (UTC)

=Status on the book= This book was started based on a few notes I had made - and the feeling that there was a need for such a resource. But it is a big project and it will take time to fill in the big gaps to make a complete book. The related book on Nanotechnology is taking most of my resources these days, while I hope to others will start adding to this one. It could also have been made as a 'bookshelf' in wikibooks - and if this book remains fragmented for too long, I suggest we cut it down to a couple of short notes/books.//KristianMolhave 20:27, 10 December 2006 (UTC)

=Comments=

Where can I find a book on how to design microchips? Would this fall under this booK? I've looked all around wikibooks and wikipedia and I cannot find anything on this - how to design chips - what programs to use... are there GNU programs to design chips? How to manufacture them... ie... you can't you need to have billion dollar fabs... or there are other less well known methods or companies that will homebrew or custom fab chips... Just some thoughts. Interesting book so far though. --anon user (some interested party on the west coast) 4 December 2006
 * See section Microtechnology/Overviews and the software section further down on the page - and hopefully this wikibook will end up having much material about all the microfabrication processes too. There are many foundry services where you can have custom made microfabrication done for you. I have addded a list of some foundry services to the above page as well -you are welcome to expand it! //KristianMolhave 20:27, 10 December 2006 (UTC)

=linking to microwiki= In wikipedia you can link to this book kby adding giving a little box as the one on the right which for some reason doesnt work very well in wikibooks...

= Missing step in fabrication (big one) =

What about the first step in the fabrication process- the growth of silicon crystals and then the use of lasers to cut the silicon into wafers so that they may later be etched with the various lithographic techniques? I have been unable to find a review on laser-cutting re: silicon, and it would be great if anybody could offer some links. Or add the content. :) -- Kanzure 15:46, 8 August 2007 (UTC)

Why is information about laser-cutting silicon is so difficult to find? Could it be that silicon isn't actually cut using lasers?

According to Wafer (electronics), the boule is actually cut into wafers using a diamond saw or diamond wire. --DavidCary (talk) 06:13, 19 December 2007 (UTC)

Media resources
Hello. For your information, I have added many photos to the Semiconductor devices fabrication category on Commons. They may be of interest to illustrate this book. guillom 10:12, 12 November 2007 (UTC)

title: Talk:Microtechnology


text:
User talk:Webaware

 ''Welcome to my talk page. Please sign and date your entries by inserting  -- ~  at the end. [ Start a new talk topic.]''

delete and clear pages
Still not happy with the need to, since sometimes its hard to remember to comply (I could be moving content about in large volumes), and nonobservance should not generate more work and be seen as an imposition on others.

Could you during a week or so refrain from looking into the "page as tagged" and just click on the dif. of the last edit ? I think that this practice will not only remove the problem of clear pages but will also intersect 2 edits at a time, and so it would be more productive. If this works for a time probably we could add the info somewhere or spread the method to other admits. Administrators are less in number, so failure to observe the "new" practice will be reduced, and any fault to observe it will affect the user himself (the acting admin). --Panic (talk) 05:01, 5 March 2008 (UTC)

 * Panic, do what you want to do. I only ask as a courtesy. I'll continue to examine pages as I have, and either you'll make it easier or you won't. There is no "new method", most people don't perpetually wipe pages clean. I only asked because you are doing a fair bit of merging / moving / tagging work and it would have been nice if you could work with us instead of at us. Whatever, just carry on in your own way and disregard - it's only our time, after all, so don't worry. Webaware talk 05:43, 5 March 2008 (UTC)

 * Is there a problem in using the dif. in place of looking directly to the page? Did any of the observations I made fail to illustrate the "change" of the validation method as a better solution to the problem in general? --Panic (talk) 06:32, 5 March 2008 (UTC)
 * Look. We're asking nicely to not replace the content. If you're going to do it, thanks. If not, fine. – Mike.lifeguard  | talk 07:25, 5 March 2008 (UTC)

 * Panic, I already do check the history and compare some versions. I prefer to at least know what I'm dealing with, however, and your page erasures and lack of edit comments confounds that. But again, it's my time, and that is apparently not important to you, so do whatever you prefer - as apparently you intend to anyway. No reply necessary, as I won't be wasting time on this thread any further. Webaware talk 08:53, 5 March 2008 (UTC)

 * What I'm attempting (but failing to) is providing an alternate solution that by a simple change on the first step will not only remove the problem but be more productive in general.
 * I presume that the pages tagged for deletion are shown to admins like the pages on patrol, does delete require one also to see the "current" status of the page to delete them ? (if so you could have saved us lots of time if you had explained this to me)
 * That would indeed remove the usefulness of starting the operation by the click of the dif., even if that is the case there is a very hight probability that 90% of the delete actions would require one to check not only the logs but major changes of content and even require one to see how and if content was moved to other pages by users (so to preserve the edit logs).
 * This is also a problem I have in the patrol option, it only shown the the option to validate the page on the first view, making it less useful to correct edits or even to tag pages since it will require a reloading of the page from the patrol view or back stepping into that view.
 * User:Mike.lifeguard I already stated that I would start to comply with the request, that doesn't bar me from asking questions or proposing a better solution. I'm not being difficult I just want to understand the why. At least I hope this time is not because of a buggy script :). --Panic (talk) 16:35, 5 March 2008 (UTC)
 * See for yourself next time you list one. Webaware talk 23:15, 5 March 2008 (UTC)
 * I have seen the deletion logs but can't remember if I saw any listed page before the action...
 * By this answer I take my assumption is correct, that means users can see the list of pages, but not the action option and that this is why you (admins) must use the last edit page view. (this is a bad design) --Panic (talk) 23:44, 5 March 2008 (UTC)

A friendly reminder for you this time. When adding tags to pages, please mark them patrolled to avoid duplication of work. To get the patrol link, you have to access the page from Special:Newpages (pending 12572). Also, I've been developing a script for NPP that I'd like to get tested more widely. If you'd be interested in trying it out, let me know. – Mike.lifeguard  | talk 02:45, 7 March 2008 (UTC)

 * IME, duplication of patrolling effort is a Good Thing. I certainly pick up things that others don't and assume it works vice versa. Besides, I'm trying to cut down on my work - have set up an RSS aggregator to watch some books, so that I can just watch RC@Cookbook: and RC. When patrolling works from RC, I'll consider it. (yes, I know, duplication vs cut down on work - I'm not cutting down on patrolling, just rationalising it so I can get through it faster without dropping any checks) Webaware talk 02:56, 7 March 2008 (UTC)

Merge
I have been working a bit on the US History book, and there are two short chapters on the same subject: US History/Contents/Secession and US History/Contents/Secession2. Is there a way to get both their histories onto the same page, or should I just copy and paste? Νεοπτόλεμος ( talk | email | contribs ) 22:16, 11 March 2008 (UTC)

 * Copy and paste the information, then tag the one you don't want to keep with now merged and one of the admins will merge the page histories. Webaware talk 22:26, 11 March 2008 (UTC)

 * Done. Νεοπτόλεμος ( talk | email | contribs ) 22:30, 11 March 2008 (UTC)

 * Looks great, thanks! Νεοπτόλεμος ( talk | email | contribs ) 23:20, 11 March 2008 (UTC)

Err
If you are around this makes me inclined to block? Certainly to watch & I am off out shortly. Hope all is good - cheers -- Herby talk thyme 09:50, 23 March 2008 (UTC)

 * Ta, I'm sort-of around. Will keep tabs on it, and agree. cheers, Webaware talk 09:59, 23 March 2008 (UTC)

Rationales
Thanks for your work on this; I'll be joining you this afternoon. Looks great so far! – Mike.lifeguard  | talk 16:23, 23 March 2008 (UTC)
 * Cool, it'll be easier with two (or more, if anyone else is reading this!) Webaware talk 22:15, 23 March 2008 (UTC)

Interesting one
With quite an interesting history. Hope all is good - cheers -- Herby talk thyme 09:22, 27 March 2008 (UTC)

 * Sadly, RR don't say much so one has to assume that it's an allocated IP:
 * network:Created:20080326
 * network:IP-Network:67.49.248.0/21
 * network:IP-Network-Block:67.49.248.0 - 67.49.255.255
 * Otherwise, I'd block it for longer. Webaware talk 09:27, 27 March 2008 (UTC)

Topology/Bases
Sorry, I wasn't quite clear. I just want those two sentences to be on seperate lines, and indented so that they look like a part of the problem, bulleting is not required. Thanks a lot for the help.

SPat (talk) 07:33, 30 March 2008 (UTC)

Thanks. That's perfect

SPat (talk) 08:08, 30 March 2008 (UTC)

Image copyright
Sorry for the breaching, but I still do not understand how to do with it. I upload this picture in terms of these two sentences from the website,http://www.windows.ucar.edu/tour/link=/image_linking.html and http://www.windows.ucar.edu/tour/link=/bibliography.html: If you are a student or teacher, we grant you permission to use images and text from our site for "educational" or "research" purposes (as long as you're not making any money from using our images or text!). If you do use our images throughout your project, please do put that each image is "Courtesy of Windows to the Universe,   http://www.windows.ucar.edu". Please use this page to include Windows to the Universe in your bibliography.

If you need to cite a page on our internet site in your bibliography for a project, please cite the page source as such: windows to the Universe team. Title of Specific Page Used. Boulder, CO: ©2000-04 University Corporation of Atmospheric Research (UCAR), ©1995-1999, 2000 The Regents of the University of Michigan, Date of last modification for that page. Online. Available: http://www.windows.ucar.edu. Date you accessed the page.

Can you please tell me what else I could do for not violating its copyright? Besides, If I can leave a message for explanation on the talk page, which comes from the following sentence "If permission is granted to use this material under the terms of our license (or a compatible license) please leave a message on the talk page explaining this," do I leave it on my own talk page? what should I explain? Thank you so much. --Yliang (talk) 02:12, 5 April 2008 (UTC)

Thank you very much for the suggestion. I will select one of those images instead. --Yliang (talk) 16:01, 5 April 2008 (UTC)

Upload
Cheers for the welcome. What do I have to do to be allowed to upload images for my contribution? 開 (talk)
 * Hello, 開. Let me answer for Webaware, as he does not appear to be online at the moment. Your account must be at least four days old, and then you will automatically have the ability to upload images here. However, it may be more beneficial if you upload these images to Commons, as they can then also be used on other Wikimedia projects such as Wikipedia, as well as here. Let me know if you need further assistance. Νεοπτόλεμος ( talk | email | contribs ) 13:49, 7 April 2008 (UTC)
 * G'day 開, what he said! cheers, Webaware talk 13:56, 7 April 2008 (UTC)
 * Cheers. 開 (talk)

License missing
Sorry for bothering you again. Since its license missed, yesterday I just deleted the link with it and followed "Please edit image descriptions pages directly to add a license template and source; ..." So my action must confuse you. --Yliang (talk) 18:02, 9 April 2008 (UTC)

 * OK, image now deleted, thanks. Webaware talk 23:19, 9 April 2008 (UTC)

Image:Sonar Principle EN.svg
You said that Image:Sonar Principle EN.svg had been re-done with non-garbled text, but it doesn't appear to be. Is it just my system, or have I done something wrong / stupid / etc.? Thanks --Sjlegg (talk) 10:26, 10 April 2008 (UTC)

 * Maybe you have a cached copy. Try refreshing your page, and see what comes. Let me know if pain persists :) Webaware talk 10:36, 10 April 2008 (UTC)

 * Pain does not persist. I've swapped my png for the svg, and changed the variable name in the chapter of the book. Good job and thanks. --Sjlegg (talk) 15:43, 10 April 2008 (UTC)

 * No worries, let me know if I can help you with anything else. Webaware talk 22:51, 10 April 2008 (UTC)

Image upload help
I wish to upload an image that I've created in MS Paint and so I have it available as a ".bmp" or ".doc" file. I don't know much about these things, so could you tell me how I can convert it to one of the acceptable formats? Thanks!

SPat (talk) 15:41, 12 April 2008 (UTC)

 * G'day SPat, .bmp aren't very web-friendly images and .doc are a no-no. I'm assuming you're running on Windows, so download IrfanView (a really handy, free graphics manipulation program). Open the .bmp in IrfanView, and save as a .png with maximum compression.
 * You might want to see if the image looks the same when you reduce the number of colours - e.g. many .bmp files use 24-bit colour, usually an overkill as they can often be reduced to 256 colours without loss of colour but with major reduction in size.
 * Now it is ready for upload to Wikibooks or the Wiki Commons. NB: Commons is generally a better place to host images, as they can then be shared with Wikibooks in other languages, and other Wiki projects. Be sure that the images you upload are licensed properly, or they will be deleted! Webaware talk 02:52, 13 April 2008 (UTC)

Thanks a lot. Due to time constraints, I have uploaded the image only to Wikibooks and not commons. I'll do something about it when I'm back in a fortnight.

SPat (talk) 10:30, 16 April 2008 (UTC)

 * No worries. You might want to check out what images are already available on Commons too - there's actually quite a bit up there. Also, if you need a hand with specific images (e.g. that one you uploaded), I can help either with transformations or rebuilding as vector graphics (SVG). cheers, Webaware talk 11:37, 16 April 2008 (UTC)

Regarding the pages on Physics for dummies
Regarding the speedy deletion candidatute, I'd like to clarify that those pages are NOT misplaced edits. Its just that I have used scanned notes as base modules. The text on geometrical opptics will be available within a few hours' time.

--Thewinster (talk) 10:36, 19 April 2008 (UTC)

 * Do you have a plan to develop text from these scanned images of handwritten notes? Webaware talk 04:33, 20 April 2008 (UTC)

 * Definitely! At present, I am doing whatever I can to write modules that can serve as templates for writing effective textbooks - you might want to check the Problems In Highschool Chemistry text for example. I abandoned it, because developing the text while publishing it online was very slow paced. The handwritten notes thus serve as texts for any readers till then and may as well fetch me some volunteers. If not, I'll wikify them someday anyways. Someday soon than later, because the texts need to be edited!--Thewinster (talk) 16:55, 20 April 2008 (UTC)

The IIT JEE QP Scans
My apologies for the mistake regarding the scans. They are NOT my work. The mistake occurred because I was repeatedly using the back button for the uploads. Also, the IIT JEE Question papers are recreated based on students' recollection of them by various tutors and hence are in the public domain.

My arguement miht be wrong, but it is a fact that the various publications here in India that provide the solutions to these Memory Based, Recreated papers have never been warned by any of the seven IITs for copyright infringement or similar legal constraints.

Only the solutions to the questions are the property of their publishers. Again, since the wikibooks solutions book is my work, it will be open source.

I hope that clears the concerns regarding source.--Thewinster (talk) 16:47, 20 April 2008 (UTC)

pickles
The information I added to the article was valuable, and I can't comprehend why you would take it off —Preceding unsigned comment added by 75.64.176.226 (discuss • contribs) 2008-04-23T08:53:10
 * It wasn't suitable for a cookbook. Webaware talk 02:45, 23 April 2008 (UTC)

.SVG images
G'day! I am currently working on Solved Question Papers IIT JEE which requires me to submit tones of figures as images. Earlier I used Jasc Paint Shop Pro to create images in .svg (a real LONG time ago) but i was not satisfied with the images particularly because there was nothing vector about them! There was no way I could draw Cartesian curves or LOGO [the fd 100 rt 90 logo ;)] figures with it. These are needed because I require scaled diagrams!

Effectively, I have zero experience in dealing with svg images. Can you recommend me some editor (preferably freeware) and some starter’s guide to svg images? I would have searched online if you would not have been experienced enough with .svg to give me just the right piece of info! --Thewinster (talk) 03:05, 24 April 2008 (UTC)

 * G'day, I use Inkscape on Linux - it's available on Windows as well, is free, and popular amongst other wiki contributors.
 * One thing you need to watch for is text - the wiki projects dynamically convert .svg to .png on the fly, resized to fit the image: tag, and the conversion often doesn't get the text flows right. To fix that, you need to convert text objects to paths before uploading to wiki.
 * I'm no expert with .svg, but am happy to give you a hand if you need one. cheers, Webaware talk 05:31, 24 April 2008 (UTC)

Embedded file help
G'day. I want to use this image, http://en.wikipedia.org/wiki/Image:CM_FrogCourtin.jpg, in wikibooks, but I cannot use it for which is not from Wikimedia Commons; thus, I would like to ask for your suggestion. Thank you. --Yliang (talk) 19:34, 24 April 2008 (UTC)
 * Because that image has a copyright license not compatible with Commons, it can't be loaded there. You could load it into Wikibooks if you can supply a fair use rationale, but you would need to demonstrate that it has a purpose other than just for decoration. Webaware talk 23:38, 24 April 2008 (UTC)
 * Thank you very much for replying. --Yliang (talk) 01:19, 26 April 2008 (UTC)

Picture heavy books...
I just saw this. Thank you for the reply. I am not sure what they will be about exactly. Perhaps inspiring the reader to learn or explore the world will be their intention. I am not sure. I may experiment some, and hopefully, that will be OK. World of work is geared quite nicely. : ) --Remi (talk) 19:48, 8 June 2008 (UTC)

 * G'day Remi, I reckon you have some good ideas there, and look forward to seeing what you come up with. cheers, Webaware talk 14:46, 11 June 2008 (UTC)

(How to post a recipe?)
Hi, I'm new to the wiki world and would like to contribute some of my recipes. I Have no idea how, I see no "post recipe here" no format pages(the format page I see is blank, no edit prompt ?????) I have no idea how to get started, can you help.--Mlpearc (talk) 18:37, 6 September 2009 (UTC)

 * G'day, sorry for delay in replying. Please check out Help:Starting a new page or book to find out how to add a page, and then read the Cookbook:Policy to see how the Cookbook formats pages. thanks, Webaware talk 01:53, 6 October 2009 (UTC)

Sign
About 8 years ago you edited the book "Using Ubuntu Linux" but still has not signed on its credits page. I request you to sign there. ഏത്തപഴം (discuss • contribs) 06:44, 9 May 2016 (UTC)

 * done, thanks. Webaware talk

title: User talk:Webaware


text:
Talk:European History/European Imperialism and Nationalism

In his book On the Origin of Species by Means of Natural Selection, Charles Darwin wrote that creatures experience genetic mutations prior to birth. Clarification of this sentence is required. Darwin was not aware of "genetic mutations". Mendel's work with hybrid crosses with peas was the door to understanding genetic mutations; but while he was conducting his experiments between 1856 and 1863, his research was not known until 1900 by de Vries and Corran. While this is a small point, it is a very important one, as it implies an understanding of meiotic processes (and thereby an understanding of biology) that was unknown before the rediscovery of Mendel's work.

Stealing maps...
...is copyright infringement and not fair usage. Please don't.

 * Where do you see any maps here? --Derbeth talk 10:01, 4 September 2006 (UTC)

 * They were removed; this Wikibook is full of maps ripped off from published books, falsely claiming "fair use". 62.25.106.209 14:12, 4 September 2006 (UTC)


text:
User talk:62.25.106.209

Hello,

Please don't remove images from wikibooks without justifying (use the edit summary). If you believe that the images are copyvio, please add the template nld to the image page, and follow the instructions as to warning the user who uploaded the image. If they prove to be copyvios, they will be deleted by an admin.

If you continue to remove images without justifying the removals, you will be blocked for disruption. -- SB_Johnny | talk 10:59, 4 September 2006 (UTC)

Thanks, but don't forget...
Thanks for tagging the images with the nld tag. Two things:

 * 1. when you use that tage, use (by using subst:, it autonatically fills in the date)
 * 2. Don't forget to warn the user (look at the tag, you will see on the bottom a template you can copy-and-paste on the uploader's talk page). Images won't be deleted if the person who uploaded it hasn't been warned!

-- SB_Johnny | talk 14:24, 4 September 2006 (UTC)

Stop reverting
This is your last warning. The next time you vandalize a page you will be blocked from editing Wikibooks.

The copyright issues will be looked into. Stop reverting. -- SB_Johnny | talk 15:44, 4 September 2006 (UTC)

title: User talk:62.25.106.209


text:
User talk:195.92.40.49

Hello,

Please don't remove images from wikibooks without justifying (use the edit summary). If you believe that the images are copyvio, please add the template nld to the image page, and follow the instructions as to warning the user who uploaded the image. If they prove to be copyvios, they will be deleted by an admin.

If you continue to remove images without justifying the removals, you will be blocked for disruption. -- SB_Johnny | talk 11:00, 4 September 2006 (UTC)

Thanks, but don't forget...
Thanks for tagging the images with the nld tag. Two things:

 * 1. when you use that tage, use (by using subst:, it autonatically fills in the date)
 * 2. Don't forget to warn the user (look at the tag, you will see on the bottom a template you can copy-and-paste on the uploader's talk page). Images won't be deleted if the person who uploaded it hasn't been warned!

-- SB_Johnny | talk 14:25, 4 September 2006 (UTC)

Stop, now.
This is your last warning. The next time you vandalize a page you will be blocked from editing Wikibooks.

The copyright issues will be looked into. Stop reverting. -- SB_Johnny | talk 15:43, 4 September 2006 (UTC)

title: User talk:195.92.40.49


text:
A-level Applied Science/Investigating Science at Work/Resources

Research
Using this internet-based textbook, it is easy to forget about other sources of information.

 * Books (including telephone directories).
 * Personal contact (phone, letter, e-mail).
 * Local knowledge.
 * Friends and family.
 * Journals and newspapers.
 * Careers advisors.
 * Advertising.
 * ThomsonLocal.com
 * yell.com

Health and safety regulations
Health & Safety Executive (HSE).

INCO
Main INCO website.

Wikipedia article on INCO.

Mond nickel-refining process.

Data on nickel carbonyl.

2004 environmental report.

2004 social responsibility report.

2003 Summary of Clydach production facilities.

2002 Speech by Scott Hand, Deputy Chairman and Chief Executive Officer.


text:
Battery Power/Lithium Ion Batteries

Lithium ion batteries (sometimes abbreviated Li-Ion) are a type of rechargeable battery commonly used in consumer electronics. They are currently one of the most popular types of battery, with one of the best energy-to-weight ratios, no memory effect and a slow loss of charge when not in use. They can be dangerous if mistreated, however, and unless care is taken they may have a shorter lifespan compared to other battery types. A more advanced lithium-ion battery design is the lithium polymer cell.

History
Gilbert N. Lewis a prominent American chemist, researched lithium batteries beginning in 1912, but the first non-rechargeable (primary) cells were not commercially produced until the early 1970s. The rechargeable (secondary) lithium-ion battery required nearly 20 years of research and development before being produced on a mass market scale; the first commercial version being produced by Sony in 1991, following initial discoveries by a team at Oxford University led by John B. Goodenough.

Advantages
Lithium ion batteries can be formed into a wide variety of shapes and sizes, so as to efficiently fill available space in the devices they power.

The batteries are also lighter than equivalents in other chemistries — often much lighter. This is because lithium ions have an extremely high charge density — the highest of all known naturally occurring ions. Li ions are small and mobile, but more readily stored than hydrogen. Thus a battery based on lithium is smaller than one with hydrogen elements, such as nickel metal hydride, and with fewer volatile gases. The ions need fewer storage intermediaries, so more battery weight is usable as charge, instead of overhead.

Li-ion batteries do not suffer from the memory effect. They also have a low self-discharge rate of approximately 5% per month, compared with over 30% per month and 20% per month in nickel metal hydride batteries and nickel cadmium batteries, respectively.

According to one manufacturer, Li-Ion cells (and, accordingly, "dumb" Li-Ion batteries) do not have any self-discharge in the usual meaning of this word. What looks like a self-discharge in these batteries is a permanent loss of capacity, described in more detail below. On the other hand, smart Li-Ion batteries do self-discharge, due to the small constant drain of the built-in voltage monitoring circuit. This drain is the most important source of self-discharge in these batteries.

Disadvantages
A unique drawback of the Li-ion battery is that its life span is dependent upon aging from time of manufacturing (shelf life) regardless of whether it was charged, and not just on the number of charge/discharge cycles. This drawback is not widely publicized.

At a 100% charge level, a typical Li-ion laptop battery that is full most of the time at 25 degrees Celsius or 77 degrees Fahrenheit, will irreversibly lose approximately 20% capacity per year. However a battery stored inside a poorly ventilated laptop, may be subject to a prolonged exposure to much higher temperatures than 25 °C, which will significantly shorten its life. The capacity loss begins from the time the battery was manufactured, and occurs even when the battery is unused. Different storage temperatures produce different loss results: 6% loss at 0 °C/32 °F, 20% at 25 °C/77 °F, and 35% at 40 °C/104 °F. When stored at 40% charge level, these figures are reduced to 2%, 4%, 15% at 0, 25 and 40 degrees Celsius respectively.

This makes Li-Ion batteries unsuitable for back-up applications compared to lead-acid batteries, and even to Ni-MH batteries.

Because the maximum power that can be continuously drawn from the battery depends on its capacity, in high-powered (relative to C, battery capacity in A·h) applications, like portable computers and video cameras, rather than showing a gradual shortening of the running time of the equipment, Li-Ion batteries may often just abruptly fail.

Low-powered cyclical applications, like mobile phones, can get a much longer lifetime out of a Li-Ion battery.

A stand-alone Li-Ion cell must never be discharged below a certain voltage to avoid an irreversible damage. Therefore all systems involving Li-Ion batteries are equipped with a circuit that shuts down the system when the battery is discharged below the predefined threshold. It should thus be impossible to "deep discharge" the battery in a properly designed system during normal use. This is also one of the reasons Li-Ion cells are not normally sold as such to consumers, but only as finished batteries designed to fit a particular system.

When the voltage monitoring circuit is built inside the battery (so called "smart battery") rather than equipment, and continuously draws a small current from the battery even if it is not in use, the battery further must not be stored fully discharged for prolonged periods of time, to avoid damage due to deep discharge.

Li-ion batteries are not as durable as nickel metal hydride or nickel-cadmium designs and can be extremely dangerous if mistreated. They are usually more expensive.

Li-ion chemistry is not safe as such, and a Li-ion cell requires several mandatory safety devices to be built in, before it can be considered safe for use outside of a laboratory. These are: shut down separator (for overtemperature), tear away tab (for internal pressure), vent (pressure relief), thermal interrupt (overcurrent/overcharging). The devices take away useful space inside the cells, and add an additional layer of unreliability. Typically, their action is to permanently and irreversibly disable the cell.

Despite these safety features, Li-ion batteries are subject of frequent recalls (see ).

The number of safety features can be compared with that of a w:nickel metal hydride: cell, which only has a hydrogen/oxygen recombination device (preventing damage due to mild overcharging) and a back-up pressure valve.

There is an ongoing research to develop alternative Li-ion chemistries, which would be safe with fewer or no safety devices, such as.

Specifications and design

 * Specific energy density: 150 to 200 W·h/kg (540 to 720 kJ/kg)
 * Volumetric energy density: 250 to 530 W·h/L (900 to 1900 J/cm3)
 * Specific power density: 300 to 1500 W/kg (@ 20 seconds and 285 W·h/L)

A typical chemical reaction of the Li-ion battery is as follows: $$\mathrm{Li}_{\frac12} \mathrm{Co} \mathrm{O}_2 + \mathrm{Li}_{\frac12}\mathrm{C}_6 \leftrightarrow \mathrm{C}_6 + \mathrm{Li}\mathrm{Co}\mathrm{O}_2 $$

Lithium-ion batteries have a nominal open-circuit voltage of 3.6 V and a typical charging voltage of 4.2 V. The charging procedure is one of constant voltage with current limiting. This means charging with constant current until a voltage of 4.2 V is reached by the cell and continuing with a constant voltage applied until the current drops close to zero. (Typically the charge is terminated at 7% of the initial charge current.) In the past Lithium-ion batteries could not be fast-charged and typically needed at least two hours to fully charge. Current generation cells can be fully charged in 45 minutes or less; some reach 90% in as little as 10 minutes.

Lithium ion internal design is as follows. The anode is made from carbon, the cathode is a metal oxide, and the electrolyte is a lithium salt in an organic solvent. Since the lithium metal which might be produced under irregular charging conditions is very reactive and might cause explosion, Li-ion cells usually have built-in protective electronics and/or fuses to prevent polarity reversal, over-voltage and over-heating.

Solid electrolyte interphase
A particularly important element for activating Li-ion batteries is the solid electrolyte interphase (SEI). Liquid electrolytes in Li-ion batteries consist of solid lithium-salt electrolytes, such as LiPF6, LiBF4, or LiClO4, and organic solvents, such as ether. A liquid electrolyte conducts Li ions, which act as a carrier between the cathode and the anode when a battery passes an electric current through an external circuit. However, solid electrolytes and organic solvents are easily decomposed on anodes during charging, thus preventing battery activation. Nevertheless, when appropriate organic solvents are used for electrolytes, the electrolytes are decomposed and form a solid electrolyte interface at first charge that is electrically insulating and high Li-ion conducting. The interface prevents decomposition of electrolytes after the second charge. For example, ethylene carbonate is decomposed at relatively high voltage, 0.7 V vs. Li, and forms a tight and stable interface. This interface is called an SEI.

See uranium trioxide for some details of how the cathode works. While uranium oxides are not used in commercially made batteries, the way in which uranium oxides can reversibly insert cations is the same as the way in which the cathode in many lithium ion cells work.

Guidelines for prolonging Li-ion battery life

 * Unlike NiCad batteries, lithium-ion batteries should be charged early and often. However, if they are not used for a longer time, they should be brought to a charge level of around 40%. Lithium-ion batteries should never be "deep-cycled" like NiCd batteries.
 * Li-ion batteries should be kept cool. Ideally they are stored in a refrigerator. Aging will take its toll much faster at high temperatures. The high temperatures found in cars cause lithium-ion batteries to degrade rapidly.
 * Lithium-ion batteries should never be depleted to empty (0%).
 * According to one book, lithium ion batteries should not be frozen. Note that most lithium-ion battery electrolytes freeze at approximately −40 °C, which is much colder than the lowest temperature reached by most household freezers.
 * Li-ion batteries should be bought only when needed, because the aging process begins as soon as the battery is manufactured.
 * When using a notebook computer running from fixed line power over extended periods, the battery can be removed and stored in a cool place so that it is not affected by the heat produced by the computer. (However, a notebook computer's battery prevents sudden loss of the data in memory during power failures and brownouts. Reasonable alternatives are the use of an older lithium ion battery or an external uninterruptible power supply.)

Storage temperature and charge
Storing a Li-ion battery at the correct temperature and charge makes all the difference in maintaining its storage capacity. The following table shows the amount of permanent capacity loss that will occur after storage at a given charge level and temperature.

It is significantly beneficial to avoid storing a lithium-ion battery at full charge. A Li-ion battery stored at 40% charge will last many times longer than one stored at 100% charge, particularly at higher temperatures.

If a Li-ion battery is stored with too low a charge, there is a risk of allowing the charge to drop below the battery's low-voltage threshold, resulting in an unrecoverably dead battery. Once the charge has dropped to this level, recharging it can be dangerous. An internal safety circuit will therefore open to prevent charging, and the battery will be for all practical purposes dead.

In circumstances where a second Li-ion battery is available for a given device, it is recommended that the unused battery be discharged to 40% and placed in the refrigerator to prolong its shelf life. Batteries should be allowed to completely warm to room temperature over up to 24 hours before any discharge or charge.

Safety concerns
Lithium-ion batteries can easily rupture, ignite, or explode when exposed to high temperatures, or direct sunlight. They should not be stored in a car during hot weather. Short-circuiting a Li-ion battery can also cause it to ignite or explode. Never open a Li-ion battery's casing. Li-ion batteries contain safety devices that protect the cells inside from abuse. If damaged, these can cause the battery to ignite or explode.

Internal contaminants inside the cells can defeat these safety devices. The mid-2006 recall of 4.1 million Sony batteries used in Dell laptops was a consequence of internal contamination with metal particles. Under some circumstances, these can pierce the separator rapidly converting all of the energy in the cell to heat. See example: Dell laptop "explodes" at Japanese conference

Kuzhikalail M. Abraham, a lithium battery consultant with E-Kem Sciences, says the computer industry's drive to increase battery capacity can test the limits of sensitive components such as the membrane separator, a polyethylene or polypropylene film that is only 20-25 µm thick. He points out that the energy density of lithium-ion batteries has more than doubled since they were introduced in 1991. "When you pack the battery with more and more material, the separator can undergo stress," he says.

The mid-2006 Dell laptop battery recall isn't the first of its kind, but it is the largest. During the past decade there have been numerous recalls of lithium-ion batteries in cellular phones and laptops owing to overheating problems. Last December, Dell pulled about 22,000 batteries from the U.S. market. In 2004, Kyocera Wireless recalled about 1 million batteries used in phones.

"It is possible to replace the lithium cobalt oxide cathode material in li-ion batteries with lithiated metal phosphate cathodes that don’t explode and even have a longer shelf life. But for the moment these safer li-ion batteries seem mainly destined for electric cars and other large-capacity applications, where the safety issues are more critical... The fact is that lithiated metal phosphate batteries hold only about 75 percent as much power...." (ref: http://www.nytimes.com/2006/09/01/opinion/01cringely.html)

New technology
In February 2005, Altair NanoTechnology, a small firm based in Reno, announced a nano-sized electrode material for lithium-ion batteries. Its prototype battery has three times the power of existing batteries and can be fully charged in six minutes.

In March of 2005, Toshiba announced another fast charging lithium-ion battery, based on new nano-material technology, that provides even faster charge times, greater capacity, and a longer life cycle. The battery may be used in commercial products in 2006 or early 2007, primarily in the industrial and automotive sectors.

In November 2005, A123Systems announced a new higher power, faster recharging Li-Ion battery system based on research licensed from MIT. Their first cell is in production (1Q/2006) and being used in DeWalt power tools and Hybrids Plus Prius PHEV conversions.

All these formulations involve new electrodes. By increasing the effective electrode area — thus decreasing the internal resistance of the battery — the current can be increased during both use and charging. This is similar to developments in ultracapacitors. Therefore, the battery is capable of delivering more power (Watts); however, the battery's capacity (Amp-hours) is increased only slightly.

In April 2006, a group of scientists at MIT announced that they had figured out a way to use viruses to form nano-sized wires that can be used to build ultrathin lithium-ion batteries with three times the normal energy density. Science Express (preprint)

As of June 2006, researchers in France have created nanostructured battery electrodes with several times the energy capacity, by weight and volume, of conventional electrodes.

title: Battery Power/Lithium Ion Batteries