text:
Wikibooks:Reading room/Archives/2020/April

Help search
No offense intended but I'm baffled by the Help search. For example, suppose I want to know the general syntax for the TextBox template. I click on Help in the left margin and get a Help search dialogue. I observe that Help is checked. I uncheck Wikibooks. In the search bar I type "TextBox syntax". Then click on Search. The response is "Did you mean: textbook syntax" and a list of references. Of course I don't mean "textbook syntax". None of the references pertain to the syntax of a TextBox. Next try a search for "TextBox template". The result is "Did you mean: textbook templates" and another list of references. Again no help. I know the template is defined somewhere but finding the syntax is almost impossible. I don't mean this to be a harangue. Rather a report from a hapless user hoping that progress is possible. Regards, ... PeterEasthope (discuss • contribs) 19:13, 30 March 2020 (UTC)

 * Well, I just tried searching for "TextBox", myself. The top match I got back was this thread.  The second match was the Wikibooks sandbox.  The third match, though, was a section of a general page, Templates/General. --Pi zero (discuss • contribs) 19:53, 30 March 2020 (UTC)
 * Screenshot of different results here. http://easthope.ca/TextBoxHelpSearch.png Odd. Ideally the search would find Template:TextBox. ...

 * Did you mean Template:TextBox? It gives the options in the text below. Its basically a css div box, and you can read about them at https://www.w3schools.com/css/css_boxmodel.asp . -- Jules (Mrjulesd) 22:23, 30 March 2020 (UTC)
 * Yes, Template:TextBox explains the syntax ... but the search didn't find it ... unless it was way down the list. Anyways, thanks, ... PeterEasthope (discuss • contribs) 23:41, 30 March 2020 (UTC)
 * Looking at your screenshot above: you searched in the help pages, and basically there isnt a help page to explain its use. Usually with templates, to explain their use, you need to look at their template documentation, which shows up when view the template page. Very often they aren't explained otherwise in the help page system. For example Template:Chapter navigation is explained in its documentation, but not on a help page. So if you search there it will not show up at all. -- Jules (Mrjulesd) 23:58, 30 March 2020 (UTC)
 * For searches like that it's generally advisable to include project space as well as help space. --Pi zero (discuss • contribs) 00:59, 31 March 2020 (UTC)
 * You mean I should leave the Wikibooks box checked in the Help search? OK but it still fails to report Template:TextBox. That is the best documentation to me. I just need to remember the URL https://en.wikibooks.org/wiki/Template: . (Probably wishful thinking.) I'm afraid WikiMedia is falling into a common peril for software: experts want to improve by adding features whereas more features are more difficulty for non-experts. Simplify wherever possible. Of course you can never satisfy every requirement. This won't be my last submission to the Reading Room. =8~) Thanks for the help, ... PeterEasthope (discuss • contribs) 13:59, 31 March 2020 (UTC)

I agree that it is difficult remembering about templates. In fact I think its one of the toughest challenges of contributing to wikis, from a technical point of view. But I will make a few points: -- Jules (Mrjulesd) 22:22, 31 March 2020 (UTC)
 * Firstly be aware of Templates. It is an index of common templates you can look up on. It's a useful resource, but isn't comprehensive; not all templates are listed. But still many are: for example for box type templates are listed at Templates/General. If that doesn't work, try looking in Category:Templates, they should all listed there if you can find them.
 * If you search for templates, tick the,  , but also the   namespaces, as template documentation is usually the best place to find info on templates.
 * You can always ask here for help if you get stuck! So continue asking stuff if you have any queries.
 * Good. I've made a few notes. Thanks, ... PeterEasthope (discuss • contribs) 02:13, 1 April 2020 (UTC)

Details of format and style
Hello again, here are more questions for the experts. The old document for the Oberon-2 language is linked in this footnote. https://en.wikibooks.org/wiki/Oberon#cite_note-5 My current editing is in my sandbox. Here are some questions. In case you are interested to edit the sandbox, that's OK by me. Assuming you don't make it worse of course. Thanks! ... PeterEasthope (discuss • contribs) 16:56, 31 March 2020 (UTC)
 * 1) In the sandbox the section numbers should remain as they are in the Contents. Can they be included on the section headings throughout the document?
 * 2) I've used table markup to mimic the format under "Vocabulary and representation". Can the whole table be indented as in the original document?
 * 3) Can style="vertical-align:top; border:none" be specified more efficiently?  Ie. specified once rather than on every cell of the table.
 * 4) In the original document, "$ ident ..." and "x  scan ..." are in monospaced font; probably Courier. How can this be invoked in the MediaWiki representation?
 * Without access to the Mediawiki namespace this is tricky. But I have experimented a bit with templatestyles, and I believe now this is possible. My I edit your sandbox to add the necessary code, as it is a bit complicated to describe?
 * Indenting tables is easy. If you add colons before the open table markup, it will indent. e.g. use the code  to indent the table twice.
 * Without ready access to style sheets it is simplest just to repeat the inline css as necessary.
 * Try using the css font-family: monospace, monospace;, e.g.  will produce  Example . Or else the  property; if this is removed they go away.
 * But a better solution is to add the overflow:hidden; property, e.g. like . They then seem to disappear.
 * I think its some sort of Chrome or Mediwiki bug, can't see why non-functional scroll bars would appear. Tested it on Wikipedia and you get the same thing. But anyway my last point seems to be a workaround that can be used. -- Jules (Mrjulesd) 09:24, 13 April 2020 (UTC). Another comment: they seem to appear dependent on the level of zoom on the page, they otherwise disappear. -- Jules  (Mrjulesd) 09:38, 13 April 2020 (UTC)
 * I saw them last night in Firefox, but don't see them anymore now. --Pi zero (discuss • contribs) 16:23, 13 April 2020 (UTC)
 * Oh that's interesting. But you can't see them in the sandbox now the code has been changed. But the previous code was like:
 * Oh that's interesting. But you can't see them in the sandbox now the code has been changed. But the previous code was like:

 $ number  =  integer | real. $ integer  =  digit {digit} | digit {hexDigit} "H". $ real  =  digit {digit} "." {digit} [ScaleFactor]. $ ScaleFactor  =  ("E" | "D") ["+" | "-"] digit {digit}. $ hexDigit  =  digit | "A" | "B" | "C" | "D" | "E" | "F". $ digit  =  "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9".
 * I can't see them in firefox at all, whatever zoom level I have. But still on Chrome at certain zoom levels. Very odd, but there you go. -- Jules (Mrjulesd) 18:16, 13 April 2020 (UTC)

Technical problems encountered by Edit filter/URL requests
following on from the technical problems you're encountering at Edit filter/URL requests. Basically they're very curious and I no real understanding of what's going on here. But I would like to ask some questions.

Are you autoconfirmed? You can tell by going to Special:Preferences; under "Member of groups:" does it state "Autoconfirmed users"? See Autoconfirmed users for an explanation.

The reason I'm asking is that Ive looked at your account at https://xtools.wmflabs.org/ec/en.wikibooks.org/MarkJFernandes, and I've seem a curious thing; according to the log you were "2020-04-15 14:42 	autoconfirmed user Automatic". But looking at your "User groups" field it is blank. That shouldn't be the case; e.g. look at my one at https://xtools.wmflabs.org/ec/en.wikibooks.org/Mrjulesd.

Now I really don't understand why these should contradict each other, an I feel there may be a technical problem with your account. -- Jules (Mrjulesd) 12:54, 15 April 2020 (UTC)

 * thanks for looking into this in some detail. So I am not in the autoconfirmed group—I'm only in the Users group. I'm exceptionally new to Wikibooks, so perhaps `there are some hoops I need to jump through` before things start running more smoothly for me?
 * --MarkJFernandes (discuss • contribs) 13:33, 15 April 2020 (UTC)

 * OK thanks. I've been trying to work out the meaning of the xtools page. What it could mean is that you are going to be autoconfirmed at 14:42 GMT today (it is currently 13:52). Now if you get autoconfirmed it could mean that problems will decrease, as most edit filters don't apply to autoconfirmed users. So it might be worth waiting a while and see if you get autoconfirmed; if so you may find that it solves your problems.
 * Now I'm not saying that this will happen, but I think it would fit in with your en.wikibooks account, that was registered 14:42, 11 April 2020. Since it takes 4 days for autoconfirmed status, it all makes logic to me. -- Jules (Mrjulesd) 13:58, 15 April 2020 (UTC)

Editing news 2020 #1 – Discussion tools
Read this in another language • Subscription list for this multilingual newsletter

The Editing team has been working on the talk pages project. The goal of the talk pages project is to help contributors communicate on wiki more easily. This project is the result of the Talk pages consultation 2019.

The team is building a new tool for replying to comments now. This early version can sign and indent comments automatically. Please test the new Reply tool.

 * On 31 March 2020, the new tool was offered as a Beta Feature editors at four Wikipedias:  Arabic, Dutch, French, and Hungarian.  If your community also wants early access to the new tool, contact User:Whatamidoing (WMF).
 * The team is planning some upcoming changes. Please review the proposed design and share your thoughts on the talk page.  The team will test features such as:
 * an easy way to mention another editor ("pinging"),
 * a rich-text visual editing option, and
 * other features identified through user testing or recommended by editors.

To hear more about Editing Team updates, please add your name to the "Get involved"  section of the project page. You can also watch these pages: the main project page, Updates, Replying, and User testing.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk) 19:28, 8 April 2020 (UTC)

How to tag words and phrases in a book, such that Wikibooks can then automatically generate an index using such tags?
If you read the text at https://en.wikibooks.org/wiki/Help:Local_manuals_of_style#Navigation, you'll see that Wikibooks says that a navigation template can be used to create an index. However, after clicking the related hyperlink, I can't seem to find information about how to do this. Can someone point me in the right direction?

--MarkJFernandes (discuss • contribs) 17:37, 17 April 2020 (UTC)

 * My best guess —which of course could be quite wrong— is that the reference you're asking about, where it says a navigation template can be used to create an index, doesn't mean there's any way to automatically create an index, it just means that if you do want to create an index, you can use a navigation template as a way of making it available throughout the book. I have put some thought into this sort of thing myself, and have lately developed an extensive glossary for the Conlang wikibook (Conlang/Appendix/Glossary), but I'm continually thinking about ways to improve it.  Part of my idea there is that, since we don't really like to have links in the middle of a book that go out of the book altogether, all the "outward" links in the body of the book could go to the glossary, and then only at the end of each glossary entry would there be links out of the book.  (Likely at some point I'll construct some sort of semi-automated assistant to help with that glossary, based on the dialog tools, and perhaps then I can generalize that... but that's not all going to happen tomorrow.) --Pi zero (discuss • contribs) 19:13, 17 April 2020 (UTC)

 * thanks for your reply. Not sure whether I agree that external links should only be in the glossary. I'm quite happy for external links to be in the main body of the work.
 * Coming back to the idea of tagging key words and phrases for automatic index generation, I think such a facility would be great. When using online reading resources, I often use any indexes in such resources. I have some coding skills—just wondering whether I could code the template for such a facility. Perhaps someone could point me in the right direction for creating such a template?

 * --MarkJFernandes (discuss • contribs) 07:34, 18 April 2020 (UTC)

 * Two miscellaneous thoughts.
 * As an alternative to an index as-such, you might consider book search (you can see it used on the main page of Conlang, at the top of the right-hand panel).
 * Minimizing (but not completely eliminating) links outgoing from a book is just usual in Wikibooks culture, as part of the coherence of a book (part of what makes a book a book). Avoiding outgoing links entirely in the book body is something I'm experimenting with, partly because the Conlang book has so many outgoing links.  It allows providing commentary on each outgoing link, that will be encountered by each reader following that link as they pass through its glossary entry, provided some effort is put into offering brief-but-valuable perspective in each glossary entry.
 * --Pi zero (discuss • contribs) 11:32, 18 April 2020 (UTC)

 * thanks for some useful advice/guidance. In regard to the search box, I did think about whether indexes were really needed given that you can just use a search box to search for specific words/phrases. It should be noted that many modern online reading resources (such as manuals) still do include indexes perhaps pointing to them adding value over simply having a search box. Indexes give a good overview of different important elements found in the narrative of a book, beyond what you get with just a table of contents. Because semantic relations in language often are alphabetical (such as for example 'computer software' coming just after 'computer platform' with both being associated [because both are about computers]), alphabetical indexes can be extra helpful. To be honest, adding an index isn't essential for my book, but it is on the wish list.

 * I'm very much new to Wikibooks, so I may make a few mistakes in my thinking related to Wikibooks books. However, the book I'm working on has very many external links mostly to Wikipedia articles, and I feel that this is the right thing to do. The idea is to provide users with an easy way to learn about highlighted terms and phrases. It's just about extra information that I believe shouldn't be in the book, but is usefully linked-to, to provide extra and sometimes essential explanations about things. In respect to book coherence, my opinion is that if I put the linked-to material in the book, the book would lose its coherence, because it would become over-bloated and also because it would be out-of-date due to the otherwise linked-to material being updated more frequently than the book. I'll concede that including a glossary is perhaps another good way to provide such extra information, but then you still have the issue about material becoming quickly out-of-date.

 * --MarkJFernandes (discuss • contribs) 13:41, 18 April 2020 (UTC)

 * While we're on the subject(s),
 * I'm a big believer in manually processed indices and glossaries and such, rather than mere automatic searches. Yes, automatic searches can be a useful tool.  I learned my way around libraries pre-internet, though, when they had physical card catalogs, thousands upon thousands of index cards all carefully crafted with individual thought; and when those were replaced by on-line catalogs, at most (not all) libraries the quality of searches went down by quite a lot.  Turns out the software for those on-line catalogs allowed all the nuanced information from the old physical cards to be put in, and if you did that you could produce a really awesome on-line search system, which a few libraries actually did with excellent results; but most libraries just had somebody type in the minimal information, and almost all the deep information in the old cards was just thrown away.  So, like I said, I really favor indices and glossaries with a lot of customized thought gone into them.  This also means that if an index were to be generated, I would favor some means of guaranteeing that hand-crafted information goes into it, both when it is first set up, and in however it is maintained.  As an example to think about, we have on Wikibooks a hierarchical arrangement of "shelves", starting at Wikibooks Stacks/Departments; all the sorting and listing is handed semi-automatically, but human beings decide how to hierarchically order the shelves, and human beings decide, for each book, what shelves it should be placed on.  Thus, the individual decisions that go into forming the shelves are distributed to where the users are who have the knowledge to inform those decisions.
 * Regarding links out of a book. Part of what makes a book a book is that it is, to a significant extent, self-contained.  Usually there is a particular order in which the modules are meant to be read; a relatively few books aren't exactly linear in that sense, but then the modules within them are generally of a specialized sort (like Wikijunior:Solar System, or Wikijunior:The Elements).  Links going out of the book are less intensive than, say, the cross-links between articles on Wikipedia.  There is also a difference between the projects in depth: a wikibook can go very much further into the details of its subject than a Wikipedia article would.  There is, in effect, a hierarchy of how a book module is linked:  we're most casual about linking to elsewhere in the same book, a bit more reluctant to link to (or into) another wikibook, a bit more hesitant still to link to a page on another project in the wikimedia sisterhood (such as Wikipedia), and decidedly more cautious about "external links", i.e. links to outside the wikimedia sisterhood, since that involves a definite drop in trust/privacy of the server.  (All of the wikimedia sisterhood prefers to set off external links so readers are especially aware before clicking one of those.) Which said, although it's clearly desirable to minimize links out of a book, it's not always clear how best to go about it.  What sort of measures make sense depends on the character of each individual book.  I'm hoping, with the thing I'm trying for the Conlang glossary, to add to our vocabulary of techniques for this sort of thing.  It seems to work quite well for that particular book, but I only offer it as food for thought, as the circumstances of your particular book are unlikely to exactly duplicate those of Conlang.
 * --Pi zero (discuss • contribs) 15:58, 18 April 2020 (UTC)

👍🏽  👤

Book search that lists more than one result per page
I've tried out the book search and the search box templates on the book on which I'm working. They work as they were intended. However, for my book, I would like for more than one result found in a page to be returned, when more than one match is found in a page. As far as I can tell, these templates, and the standard Wiki search functionality across the Wiki Foundation sites, do not have this functionality.

I would like more than one result to be returned, because each chapter (some of which are quite long) is contained each on its own page. I feel this is better than splitting the chapter up into several web pages—it makes browser searches (, etc.) easier and also makes following the narrative that runs through any one chapter easier (IMHO).

Can anyone give me any pointers on how I can satisfactorily resolve these issues?

My thoughts on a solution:
 * 1) create a directory/folder for each sub-section of the chapters;
 * 2) proceed to create one wiki page for each subsection (in the directory), that on-the-fly extracts (via something like an 'includes' statement) the subsection from its source chapter page;
 * 3) on each of these subsection pages, have a link that links back to the subsection as present on the corresponding chapter page;
 * 4) now when book search is performed, each of these sub-section pages can return a hit, potentially resulting in more than one result per chapter, which whilst not always providing a perfect correspondence to matches, perhaps is acceptable at least for my particular book.

The above solution seems okay but I don't know how to implement the 'includes' functionality—anyone have any ideas?

--MarkJFernandes (discuss • contribs) 08:54, 28 April 2020 (UTC)

 * ADDENDUM NOTE: it appears that the Wiki transclusion functionality can probably implement the 'includes' functionality mentioned (see Transclusion). --MarkJFernandes (discuss • contribs) 06:34, 29 April 2020 (UTC)

 * Some thoughts. Well, okay, I've ended up writing rather a lot, below; it's all reasonably brief and to-the-point until I start talking about dialog; well... half-sorry about that, but it is relevant.
 * The essential problem is that the wiki-search feature provided by the wiki platform is, conceptually, separate from the string-search provided by the user's web-browser. They don't actually complement each other as one might hope they would; it's more like, they awkwardly divide up the task into separate domains, and each of them insists on handling only one half of the task, while the user is obliged to switch from one mode to the other halfway through their search.  That is, the on-wiki search imitates internet search engines (and probably uses one), which have pages as their end targets; while the browser string-search locates occurrences of that string on the particular page that is being viewed.  If these are the tools available to you, and you want to find all the occurrences of a string on all the various pages of the book where the string occurs, you have to use the two successively, finding the pages with the first tool and then using string search on each page.  A compounding problem is that both these tools are blind to semantics: they search for a string mechanically, without regard to the actual meaning of things.  Taking meaning into account is the function of a humanly-constructed index.  Sometimes one will see a really sophisticated index in a book, under a particular keyword, distinguish somehow between one or more primary/major references to the keyword, and a bunch of secondary/minor allusions.
 * If you had a really good index, what would you like to be its targets?
 * Btw: The standard terminology set out for Wikibooks long ago calls the content pages of a book "modules"; it never really caught on, perhaps because it's neither standard enough to come naturally to users as they arrive at the project, nor gets used heavily enough once the user arrives to make an impression on them. As an illustration of the latter, on Wikinews the term "lede" is so ubiquitous that pretty much everyone ends up knowing what it means.
 * Would it be satisfactory for an index to target section-headings within modules? This is what I did with the Conlang glossary, though rarely have I wanted to link a single keyword to more than one section within the same module.
 * The problem is then how to assemble such an index. There are some devices I think could be useful for this, some of which are more ready-for-prime-time than others.
 * There may be ways to accomplish a great deal without relying too heavily on the parts that are less developed atm. For instance, the Wikibooks Stacks get along, more or less, with less tooling than I would imagine eventually bringing to bear on them.  An index-building device might work from embedded meta-information in each section of each module, specifying what index entries ought to target that section.  One would then want to extract this meta-information from each module and collate it all to generate an index; and there are a range of different levels of semi-automation that might be employed for that.
 * I should perhaps explain about the overall plan that surrounds the "dialog tools", because this has to do with what the parts are, how they are meant to be used together, and which parts are more ready-for-prime-time that others. (And this, alas, is where the length of this comment gets away from me...)
 * It all starts with the notion that wikis could become vastly more powerful, wholly transforming the nature of the medium, if only they could have interactive elements freely placed on them: imagine a wiki page with a variety of text input fields (along with perhaps occasional drop-down menus and checkboxes), and a bunch of buttons one could click each of which would take data from the input fields and send it somewhere to have something done with it.  With a small number of simple templates that would allow specifying elements of these kinds, so they could be placed on the wiki page via wiki markup (things like, say, dialog/text, dialog/checkbox, dialog/button, etc.).  The good news is, that can be done, and I basically have done that and it's available on Wikibooks now.  But there are some caveats.  To make these simple primitive elements practical to use, you need about three additional things.  (I'd always figured that, once you had the primitive elements, there'd be a long process of learning idioms for how to use them, details of which would be inherently impossible to anticipate before one had the tools available to actually work with.)  You can read about the simple primitive elements, btw (I mentioned this once earlier, I see), at Help:Dialog.
 * You need a way to organize sets of pages into coherent "semi-automated assistants"; these assistants are, more-or-less, "wizards" for performing particular tasks. I've set up a way of grouping the pages of an assistant together that's inspired by the way Wikibooks groups the pages of a book together.  (The primitive-tool development, btw, is happening on Wikinews, because the license there is more permissive than other sisters, so the tools can be exported from there to, say, Wikibooks.  The latest version of things hasn't been ported over to Wikibooks yet; I'm waiting for the latest improvements to be just a bit more stable before tangling with that.)
 * The main example of an assistant that I already have working is Breadboard. (Basically, it lets you write wiki markup that depends on template-parameters and test it by specifying what the values of the template-parameters should be; actually those aren't template parameters, they're dialog parameters, but, close enough for most purposes.)
 * You need some peripheral tools to help with doing, e.g., complicated transformations on the contents of web pages that the wiki platform isn't good at but that you also do not want to have to build into the dialog tools (because it's logically separate from the native function of the dialog tools). I explicitly want users to specify everything in wiki markup, which I consider essential to the reason wikis are a successful concept (I'm actually rather passionate about this); I believe the Wikimedia Foundation has been shooting itself in the foot, for many years now, by trying to migrate away from wiki markup to other languages, like Lua.  I only use Lua, or even javascript, to build tools whose purpose is to help users not have to use anything but wiki markup.
 * The primary peripheral tool I've created is evalx (mostly an interface, as it happens, for Lua Module:Wikilisp). And evalx I've found immensely useful.  It should be able to do things like combing through a module of a wikibook to extract meta-information from it that specifies how to build index entries targeting sections of that module, or using that extracted information to update an index page.  With... some careful thought about how best to arrange those things.  And perhaps a bit of dialog to direct the input to, and output from, the evalx template.
 * Ideally, ordinary users would contribute to assistants in the same way they contribute to ordinary wiki documents (such as wikibooks), and so assistants would be "grown" by crowdsourcing. Likely this ideal should be striven for but won't ever be perfectly achieved.  But, whenever a wiki task is performed over and over and is tedious or tricky requiring some expertise, it's a good candidate for an assistant.  And here's the thing: building and maintaining assistants is a task that's tedious and tricky requiring some expertise.  So it's an obvious choice to build an assistant for building-and-maintaining assistants; a "meta-assistant".  This would probably go a very long way toward making assistants more practical.  Can that even be done?  I think so, yes; but I expect it to be fiendishly tricky to tease out just how to do it.  I'm working on it; but right now that's the number-one cause of slow development of the whole dialog-based-assistant concept, and it's nothing to shake a stick at.
 * --Pi zero (discuss • contribs) 14:28, 28 April 2020 (UTC)

👍🏽  👤

Book-like features Wikibooks could use
Hi there,

I'd like to use some of the features of Wikisource here, if people thought it appropriate. For instance:

 * Layouts that feel like pages (narrow columns, serif fonts, titles without underlines)
 * Automatic epub exports (available by default as a link at Wikisource)

This would let people build books here that are aimed at export to epub and use on devices. This doesn't have to be every book of course, but would certainly provide some opportunities for me that I am currently cautious about attempting here.

Does this seem practical or does it seem like too much to try to do? JimKillock (discuss • contribs) 12:17, 20 April 2020 (UTC)
 * JackPotte (discuss • contribs) 19:59, 20 April 2020 (UTC)


text:
A-level Mathematics/CIE/Pure Mathematics 1/Trigonometry

Sine
The sine of an angle is defined as the ratio between the opposite and the hypotenuse. For a given angle, this ratio will always be the same, even if the triangle is scaled up or down.

$$\sin(\theta) = \frac{opposite}{hypotenuse}$$

Cosine
The cosine of an angle is defined as the ratio between the adjacent and the hypotenuse.

$$\cos(\theta) = \frac{adjacent}{hypotenuse}$$

Tangent
The tangent of an angle is defined as the ratio between the opposite and the adjacent.

$$\tan(\theta) = \frac{opposite}{adjacent}$$

The Unit Circle
The unit circle is a circle of radius 1. It can be used to provide an alternate way of looking at trigonometric functions.

In the unit circle, a right-angled triangle can be drawn with the radius as its hypotenuse. Thus, the hypotenuse is 1 and the sine and cosine functions refer to the coordinates of a point on the unit circle.

Graphing Trigonometric Functions

A sine graph starts at $$(0,0)$$, then oscillates with a period of $$2\pi$$ and an amplitude of $$1$$.

A cosine graph is like a sine graph in that it oscillates with a period of $$2\pi$$ and an amplitude of $$1$$, but it starts at $$(1,0)$$

A tangent graph starts at $$(0,0)$$, goes to infinity as it approaches $$x = \frac{\pi}{2}$$, emerges from negative infinity after $$x = \frac{\pi}{2}$$, then repeats this at $$(\pi,0)$$. The tangent graph has a period of $$\pi$$.

Exact Values
It is useful to know the following exact values of trigonometric functions:

Inverse Trigonometric Functions
The inverse trigonometric functions are functions that reverse the trigonometric functions, just like any other inverse function. The inverse trigonometric functions are: $$\sin^{-1}$$, which is the inverse of $$\sin$$; $$\cos^{-1}$$, which is the inverse of $$\cos$$; and $$\tan^{-1}$$, which is the inverse of $$\tan$$.

Trigonometric Identities
An identity is a statement that is always true, such as $$a + b \equiv b + a$$. A trigonometric identity, therefore, is a trigonometric statement that is always true.

It is helpful to know the following identities:

 * $$\sin(x) \equiv \cos(\frac{\pi}{2} - x)$$
 * $$\cos(x) \equiv \sin(\frac{\pi}{2} - x)$$
 * $$\frac{\sin(x)}{\cos{x}} \equiv \tan(x)$$
 * $$\sin^2(x) + \cos^2(x) \equiv 1$$

These identities can be used to prove other identities.

e.g. Prove that $$\frac{\sin(x)\cos^2(x)}{\cos(x)} \equiv \tan(x) - \sin^2(x)\tan(x)$$

$$\begin{align} \frac{\sin(x)\cos^2(x)}{\cos(x)} &\equiv \frac{\sin(x)(1 - \sin^2(x))}{\cos(x)} \\ &\equiv \tan(x)(1 - \sin^2(x)) \\ &\equiv \tan(x) - \sin^2(x)\tan(x) \end{align}$$

Solving Trigonometric Equations
When solving a trigonometric equation, it is important to keep the interval in mind.

e.g. Solve $$\sqrt{3}\tan 2x - 1 = 0$$ for $$-\frac{\pi}{2} < x < \frac{\pi}{2}$$.

$$\begin{align} \sqrt{3}\tan 2x - 1 &= 0 \\ \sqrt{3}\tan 2x &= 1 \\ \tan 2x &= \frac{1}{\sqrt{3}} \\ &\text{The interval is }-\frac{\pi}{2} < x < \frac{\pi}{2}\text{ so} -\pi < 2x < \pi \\ 2x &= \{-\frac{5\pi}{6},\frac{\pi}{6}\} \leftarrow \text{We need to include all possible values that are in the interval}\\ x &= \{-\frac{5\pi}{12},\frac{\pi}{12}\} \end{align}$$

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


text:
Talk:Create Vampires/Original Fictional Creations

From: Creative Writing 101: A Beginners Guide to Creative Writing: "Rather than only giving information, or inciting the reader to make an action beneficial to the writer, creative writing is written to entertain or educate someone, to spread awareness about something or someone, or to express one's thoughts." -Idrees Patel [Link http://www.writerstreasure.com/creative-writing-101/] This seems lai-ca a good beginning. I hope this quote helps, and can be used in the Create Vampires: Original Fictional Creations section. Critical readers are welcomed, although I do caution you, this is only the introduction [it will probably change]. Thanks Peyton09 (discuss • contribs) 11:53, 21 May 2020 (UTC)


text:
Create Vampires/Original Fictional Creations

Original Fictional Creations
 HISTORY AND FOLKLORE

History, meaning inquiry, or knowledge acquired from the past by investigation, may stem from Greek historia, according to Wikipedia. https://en.wikipedia.org/wiki/Portal:History History is related to folklore, yet is essentially different. Folklore are stories about a particular culture, yet Folklore, and similar legends, are told from a subjective perspective, and are not validated by external sources. Folklore and legends are classified as cultural heritage. History is not myth, mainly for reasons that involve telling a story about events that have happened in the past, and then gathering supporting evidence used to validate one's history. The study of History is a major discipline in academic fields.

The nature of the vampire shifted from folklore stories, that often contained warnings, to mutated stories about pale monsters and occult-ish blood lettings.

It is as if the horrific stories about the tragic events that happened to some people, horror stories that were traditionally passed orally from person to person, started to pass culturally from one region to another region, finally emerging from the author's imagination in tangible, written form, vastly distorted, yet eerily relevant, with the mysterious ability to capture the imagination of young readers.

Imaginative young readers today, could greatly benefit from Creative Writing classes offered in many Public High Schools. Creative writing classes are controversial classes in academia, yet in general, helpful to students in public schools. Creative writing programs are developing. In many public schools, creative writing classes are related to Language classes, and Art classes. Creative writing is not a discipline in academic fields.  Create Vampire  is a free wikibook intended as a guide, and as a non-fictional resource for people fascinated by vampires and similar monsters! TIP: Before creating a vampire character, you could ask yourself if you want your vampire to reflect stories based in Folklore, gathered from events that happened to actual people, or you may prefer to create a vampire from your imagination. Perhaps a imaginary creation who possesses non-human traits?

 Create Vampires ? In a world where people desire to make a lot of money, in the shortest amount of time. In a world where bank robbery is illegal, yet grave-robbery is not...? In a world populated by individuals who seemed ruled by greed, vampires and other monsters are sometimes spoken into some tangible, often frightening existence. If we exist in a world where characters could be spoken into existence, and allowed to linger in unusual fields bound and un-bound... If characters could linger, losing human characteristics and form, linger like ghost populating flat white spaces, if characters could attain atypical motion, yet exist like zombies without the ability to reason, or exist like demons without kindness, or exist like vampires, with constant hunger, sharing kindness with the hungry ghost who linger with desires to be fed, if such empty planes were populated by hungry, unreasoning, lingering atypical creations, mere works of the imagination, would their monster's tale be worthy of note? Link: Create Vampires/Why Create Vampires?

Link: Create Vampires /Vam-Pai-Yer "How do you spell vampire?"


text:
Talk:End-user Computer Security/Main content/Miscellaneous notes

On 31.3.2020, I 'raked' the entire National Cyber Security Centre (NCSC) website.....
On 31.3.2020, I 'raked' the entire National Cyber Security Centre (NCSC) website (www.ncsc.gov.uk) for material relevant to this book. Hyperlinks to all relevant material have now been appropriately incorporated into this book.

MarkJFernandes (discuss • contribs) 14:18, 21 May 2020 (UTC)

== Using unrepeatable-patterns security and deep-fake-resistant videos, to induce user trust regarding the manufacture of an acquired unit ==

Unrepeatable-patterns security can be leveraged, together with `deep-fake-resistant video` technologies (see talk-page note here regarding security ideas concerning deep-fake-resistant-video technologies) to induce such trust. What would happen, is that the manufacturer would use 'unrepeatable patterns'-security patterns in the workshop/factory during the manufacturing of the said unit. The patterns could be in the equipment, as well as on the walls and floor. They should though, importantly be on the unit being constructed. The whole manufacturing process of the unit would then be videoed using deep-fake-resistant technologies. The final video could additionally be cryptographically signed by the manufacturer, perhaps additionally with an 'authentication cryptocurrency coinage' blockchain to increase trust even more. The video would be securely sent to the receiver of the unit. Such video would serve as some amount of proof of the integrity of the manufacturing process used in the manufacture of the particular unit received by the receiver.

JTAG might help in overcoming deep hardware hacking; mention it in §⟪Deep hardware hacking?⟫ ?
According to Wikipedia, JTAG is an industry standard for testing PCBs post manufacture and for verifying designs. It seems that it might be possible to leverage the standard to detect when certain microchips are not what they should be (especially in respect of the JTAG boundary scan technology), and so to overcome certain deep-hardware-hacking attacks. So it may in fact be advantageous for JTAG technology to be present in a computer system, so as to be able potentially to do such verification. In such regard, using a motherboard/mainboard that has a JTAG port may in fact be a good idea. In regard to the security risks associated with being able to inject malware into firmware via a JTAG port, perhaps the firmware can just be wiped and then reinstalled via the JTAG port (thereby overcoming any pre-existing malware).

In respect of the aforementioned, mention of JTAG should perhaps be made in §⟪Deep hardware hacking?⟫.

Perhaps mention IEC 61508 in §⟪Cybersecurity standards⟫?
Raspberry Pi Forums user karrika implied that studying the IEC 61508 standard, might be good in respect of establishing security. Perhaps mention it in §⟪Cybersecurity standards⟫? Not sure whether the standard is already adequately covered through the link to the Wikipedia page on cybersecurity standards.


text:
User:Dilpreet Singh01/sandbox

Day Night

Cp1.

How they meet

Ye kahaani hai Day aur Night ki dono 24 ghanto me Sirf do baar milte the ek subha hoti thi tab aur jab raat hoti thi tab.

Cp2.

Whats happened when they meet .

Jb wo milte the to Charo trf ek umid si jaag jaati thi Charo trf khushiya hi khushiya hoti thi insaan se lekr jaanvar tak panchiyo se lekr peido tak nadiyo se lekr jharno tak khushiya hi khushiya hoti thi.

Cp3.

But why they separate from each other

Lekin kismat unhe hamesa ek dusre se alg krti rehti hai. Ye sb ishwar ki hi maaya hai. Aisi rachna hai ki dono ko aalag hona hi padta hai.

Writer : : PARDEEP SHARMA SONIPAT

hi if you enjoy plz rate us. And comment on talk page.

title: User:Dilpreet Singh01/sandbox


text:
A-level Mathematics/CIE/Pure Mathematics 1/Series

The Binomial Theorem
Before we discuss the binomial theorem, we need to discuss combinations. In order to discuss combinations, we need to discuss factorials.

Factorials
The factorial of a number is the product of all numbers from 1 to that number. It is represented by the symbol $$!$$ after the number.

e.g. $$4! = 4\times 3\times 2\times 1 = 24$$

The factorial can be formally defined as:

$$n! = \begin{cases} 1, &\text{if }n = 0 \\ n\times(n-1)!, &\text{otherwise} \end{cases}$$

Combinations

Combinations are a way of calculating how many ways a set of items with a given size can be selected from a larger set of items. It is typically represented either by the column notation $$\binom{n}{k}$$ or by the notation $$nCk$$.

Combinations can be calculated using factorials: $$\binom{n}{k} = \frac{n!}{k!(n-k)!}, n \geq k $$.

e.g. $$\binom{5}{3} = \frac{5!}{3!2!} = \frac{120}{6(2)} = \frac{120}{12} = 10$$

The Binomial Theorem
The binomial theorem is used when we need to raise a binomial, an expression consisting of two terms, to the power of a given $$n$$, e.g. $$(x+2)^3$$.

The binomial theorem states that $$(a+b)^n = \binom{n}{0}a^n + \binom{n}{1}a^{n-1}b + \binom{n}{2}a^{n-2}b^2 + \dots + \binom{n}{n}b^n$$

e.g.

$$\begin{align} (x+2)^3 &= \binom{3}{0}x^3 + \binom{3}{1}x^2(2) + \binom{3}{2}x(2^2) + \binom{3}{3}(2^3) \\ &= (1)x^3 + (3)(2)x^2 + (3)(4)x + (1)(8) \\ &= x^3 + 6x^2 + 12x + 8 \end{align}$$

The binomial theorem is sometimes summarised as $$(a+b)^n = \sum_{k=0}^n \binom{n}{k}a^{n-k}b^k$$

Arithmetic Progressions
An arithmetic sequence is a progression in which the numbers increment by a fixed quantity from one term to the next.

e.g. $$6, 8, 10, 12, 14, \dots$$ is an arithmetic sequence (the fixed quantity is $$2$$)

The nth term
The nth term of an arithmetic sequence can be determined using $$a_n = a_1 + (n-1)d$$ where $$a_n$$ is the nth term, $$a_1$$ is the first term, and $$d$$ is the difference between two consecutive terms in the progression.

e.g. The sequence $$4, 7, 10, 13, \dots$$ has a difference of $$7-4 = 3$$. So the nth term of this sequence can be determined by $$a_n = 4 + 3(n-1) = 4 + 3n - 3 = 1 + 3n$$. Thus, if we wanted to find the 1000th term of the progression, we can use the nth term formula: $$a_{1000} = 1 + 3(1000) = 3001$$.

Sum of the first n terms
The sum of the first n terms of an arithmetic progression can be found using the formula: $$S_n = \frac{n(a_1 + a_n)}{2}$$

e.g. Find the sum of the first 50 terms of the sequence $$23, 27, 31, 35, \dots$$

$$\begin{align} d &= 27 - 23 = 4 \\ a_1 &= 23 \\ a_{50} &= 23 + (50-1)(4) = 23 + 49(4) = 23 + 196 = 219 \\ S_{50} &= \frac{50(23+219)}{2} = 25(242) = 6050 \end{align}$$

Geometric Progressions
A geometric progression is like an arithmetic progression except that instead of adding a constant from one term to the next, we multiply each term by a constant to get the next term.

e.g. $$3, 6, 12, 24, 48, \dots$$ is a geometric sequence.

The nth term
The nth term for a geometric progression is given by $$a_n = a_1r^{n-1}$$ where $$a_n$$ is the nth term, $$a_1$$ is the first term, and $$r$$ is the ratio between two consecutive terms.

Sum of the first n terms
The sum of the first n terms of a geometric series can be found using $$\frac{a(1-r^n)}{1-r}$$.

e.g. The sum of the first 10 terms of the sequence $$3, 6, 12, 24, 48, \dots$$ is $$\frac{3(1-2^{10})}{1-2} = \frac{3(-1023)}{-1} = 3(1023) = 3069$$.

Convergence
A convergent geometric progression is one where the terms get smaller and smaller, meaning that as $$n$$ approaches infinity, the $$n$$th term approaches zero. An important consequence of this is that the progression will have a defined sum to infinity.

We can tell if a sequence is convergent if the ratio $$r$$ is less than $$1$$ and more than $$-1$$. If this condition is not satisfied, the sequence is divergent.

Sum to Infinity
The sum to infinity of a geometric progression is the value that the sum of the first $$n$$ terms as $$n$$ approaches infinity. If a progression is convergent, its sum to infinity will be finite.

The sum to infinity is given by $$S_{\infty} = \frac{a(1-r^{\infty})}{1-r}$$ which is equivalent to $$S_{\infty} = \frac{a}{1-r}$$ if $$-1 < r < 1$$.

e.g. The sum to infinity of the sequence $$1, \frac{1}{2}, \frac{1}{4}, \frac{1}{8}, \dots$$ is $$\frac{1}{1-\tfrac{1}{2}} = \frac{1}{\tfrac{1}{2}} = 2$$


text:
Using Ubuntu Linux/Introduction for users of other operating systems

Welcome to Ubuntu. You have made a good choice by trying it.


text:
User:Valerio Bozzolan/Website UI customization

Footer
Visit.


text:
User talk:Davy2323

python3 ./trytond-admin --all --database=health i have some problem at this step

title: User talk:Davy2323


text:
Talk:End-user Computer Security

Policies, guidelines, and guiding principles established for this Wikibooks book

 * Whenever you add non-text media to the book, remember to CATEGORISE the media in an appropriate book sub-category under Category:Book:End-user_Computer_Security/Non-text_media. To do this, first obtain the name of the media that is used in the book. Then go to the URL:
 * that begins with ,
 * that then has the name you obtained following that beginning text, and
 * that then finally ends with the text.
 * In the file description page that appears, add the text  to the page, with the three question marks replaced with the path dictating the exact sub-category of the "Non-text media" book category, under which the media is appropriately categorised.

 * For the time being, the book deliberately does not have a downloadable version as the book's material is very much liable to change (including change classed as correction).
 * The book is moving towards a goal of not being "the book authored by MarkJFernandes", and instead of being "the world's book" (presumably like many of the other books hosted on Wikibooks).
 * Mostly, new ideas should be added to the different talk/discussion tabs of the book's main content. When ideas are associated with a particular chapter, those ideas should be in the talk/discussion tab of the particular chapter. MarkJFernandes may be able to do this work for you; in this regard, it is helpful for you to give him general copyright permission to facilitate this.
 * When readers read the book's sections, they should see up-vote and down-vote icons just next to the section headings. Readers can click those icons to up-vote and down-vote different sections, with the option of being able to add extra information pertaining to their up-vote or down-vote. Using those 'buttons' just after reading a section is perhaps a good idea in the case that a reader has clear sentiments regarding the section just read.
 * The book is more based in ongoing, never-ending, democratic collaborative research, than a treatise on an established subject. Particularly because of such, it is encouraged that entities that are in some way linked to parts of the book (which could simply be by way of the entity being mentioned), contribute to the work, even if that be just through peer review, and especially in respect of the parts connected to them.
 * In the book, there is the tendency to focus on principles rather than implementation-specific things. Naming a particular implementation is fine (for example, the Qubes implementation and the Google password manager are named), but probably such naming should be used for examples of concepts, rather than as the nuts-and-bolts of a concept. The Google password manager is documented in a little detail, but the underlying concepts could be applied to a variety of password managers (in theory).
 * The book does touch upon some theoretical ideas. For example, there is mention that the cross-signing of certificates might be a way to strengthen the current TLS-certificate-based security system.
 * With respect to the mentioning of implementations, often they should only be mentioned in the main body of the work if they are 'par excellence' instances of the related theories/principles put into practice. When the relationship to an implementation is not one of the implementation being a 'par excellence' instance, it is then perhaps better to mention the implementation in the Appendix, and then just link to the Appendix from the related section in the main body of the book. Alternatively, using footnotes might also be appropriate in such cases. It should also be considered whether it is perhaps better to completely leave out from the book (including from the Appendix) mention of an implementation connected with a particular theory/principle.
 * 'New security inventions requiring a non-trivial investment in new technology', should be documented in the Appendix, in the "New security inventions requiring a non-trivial investment in new technology" section.
 * Sometimes it is unclear as to how to integrate precisely certain ideas into the book, perhaps because the ideas haven't 'solidified' as definite nuggets of knowledge/understanding/information worthy of inclusion in the main content of the book. In such instances, it is perhaps better to build-up some more information on the related issues, before doing any such integration. If following this guideline, you can still record such ideas and notes, by simply adding them to the talk/discussion tabs of the book's pages.
 * It's important to add insights gathered from the practice of security concepts. The book is written tilted towards theory, mostly because MarkJFernandes didn't possess the practical experience for the various security ideas. This is perhaps a weakness of the first versions of the book but should hopefully be ironed-out through time, as the insights from practical experiences are more and more added to the book. The book was written out of necessity, mostly because there appeared to be a dearth of information on the issues covered.
 * The first versions of the book probably didn't focus that much on privacy issues, except in the sense of privacy of security credentials. MarkJFernandes wasn't so concerned with other privacy issues. Whether this should form an ongoing policy, or instead just be statements about the first versions of the book, is unclear.
 * MarkJFernandes is of the opinion that the general lack of meaningful resources for end-user computer security, is likely a hidden way for various groups to be able to spy on, and interfere with, people with ease (see the "Stop funding the spies and hackers" section).
 * There is an attempt to make the book unique (you might say with a "unique selling point" {USP} ) in that it deals with inexpensive security. That's what MarkJFernandes wanted for himself, and what he believed would also be very much helpful to users all over the world (especially those who are not so wealthy).
 * Part of the original philosophy behind book:
 * There should be a transfer of sovereignty to citizens. Robust secure computing is likely integral to this. Computing is so important these days, that its general compromise is a threat to peace, democracy, education, and probably lots of other things. Legitimate policing organisations should probably be encouraged to be open and honest in their interrogations of suspected criminals, rather than allowing compromised technology to be prevalent as some kind of means for detecting and/or preventing crime. Honesty and integrity are vital. Lies and deceptions are generally not good. Lies and deceptions might be able to convict more criminals for longer sentences, but honesty and integrity might help to turn people away from crime in the first place.
 * Having democratic resources like wikis are good for involving people at the grass-roots level from different backgrounds, so that people's voices can be heard.
 * Computer technology is something of a fashion, and people adopt it because it is fashionable but not necessarily because it helps situations. It's acceptance is almost dogmatic. But the reality is, is that less tech is sometimes better.
 * MarkJFernandes tried not to get very much into politics in the book. He tended to follow the principle that a user should be able to use digital technologies safely and securely, regardless of their political opinions. In contrast, privacy rights are often violated by governments using the rhetoric that they need to be able to detect terrorism. The book goes for more of a human-rights, bottom-up perspective, where the government is instituted to protect human rights, instituted by the individual persons making up a people, and where persons in the messiness of everyday living can work out issues (such as terrorism issues) as they go along (they can help each other come to better thinking through means such as dialogue, dialogue facilitated by degrees of freedom in communication and thought).
 * MarkJFernandes generally favours things like social media, where grassroots opinions can come to the fore. He considers that social media is sometimes a good way to overcome propaganda.
 * Paranoia can be an effective tool and motivator for security development. The accusations of paranoia perhaps fail to see this: turn negative paranoia into positive security development.
 * Book was mostly originally written in respect of security for MarkJFernandes as a self-employed individual needing to use digital technologies. Partly it's a wiki because he knew how limited his knowledge and experience was, and because he wasn't an expert in the area of computer security. Still, he was quite shocked at how poor the prevailing advice on computer security seemed to be (almost as though there was something underhand in it).
 * Getting the opinions of people from widely differing backgrounds is good. A person having special circumstances, even those of being marginalised, can mean that their advice is particularly unaffected by the conflicts of interest often surrounding security advice.

Possible improvements

 * Possible improvement is to remove repetition in footnotes such as the footnote `as detailed later on in the section entitled “user randomly selecting unit from off physical shelves”.`
 * Possible improvement is to lighten photographs so that they stand out less. this may make reading such parts easier as the photos can otherwise potentially visually intrude too much.
 * Originally, wanted to keep each chapter on its own page, probably because I had thought that going back and forth between sections within a chapter was important for understanding material. Now am thinking that there is too much content on some chapter pages. Instead, probably is a good idea to have each gold-headed section on its own page (this would be more in line with how other Wikibooks books are structured). If doing such rearrangement, should be mindful that I have sent messages (such as to the Qubes mailing list) with links to sections in the present book structure, that may fail if I do such restructuring without establishing appropriate link redirects. Therefore, should remember that establishing such link redirects may be the right thing to do if doing such restructuring.
 * Headings beneath the level of gold-coloured headings, do not appear conspicuous enough, and the related sections don't appear distinguished enough. Adding extra formatting to improve this, is probably a good idea, where such formatting may include using different font colours, different fonts, bigger font sizes, indenting text beneath headings more than their headings, and using more vertical space between sections.
 * The vertical spacing between contents-page entries, on the contents page, could be improved. For the sub-section entries, the entries are too close to each other (not distinguished enough), and the contents page could do with greater grouping together of sub-section entries and sub-sub-section entries that fall within the same parent, along with greater distinction of the groupings from each other (they're too close to each other).
 * The blue colour used for hyperlinks, makes reading the text slightly difficult (perhaps the text becomes a bit ugly). This is partly because I have opted to use many hyperlinks (to provision better further additional reading related to the text). To improve this, it might be a good idea to use a colour for hyperlinks that is only slightly different from the colour used for un-hyperlinked text, or perhaps instead to add a very slight colour highlight to hyperlinks that then have a font colour that is the same as un-hyperlinked text. It should be noted that users may use book-reading skins, such that the colour used for un-hyperlinked texts may not simply be black. An alternative approach might be to warn users that there are many hyperlinks in the text, and that to find them they will have to hover their mouse pointer over text to see whether there is a hyperlink there; if there is a hyperlink, hovering over it will likely underline the link, display some hover text indicating the presence of a hyperlink, and display the hyperlink address in the web-browser status rectangle (often at the bottom of the window).
 * It might be a good idea not to incrementally change the main contents of the book for the next group of updates, but instead to lump all the updates together into one new version update of the book (version 2 of the book), and then to make all the updates together. This probably would make sense as there are corrections/improvements to be made that span much of the breadth of the book rather than being localised just to individual pieces of text. This may require saving proposed page changes in cloud storage, and then when ready, committing the page changes to the book all in one go.
 * The book doesn't make much use of images, partly because I was more interested in making sure the important ideas were in the book in at least some form, rather than providing extra inessential illustrations that to some extent beautify the text, and that has the aspect of improving the form of the ideas (rather than the substance). Looking at other Wikibooks books and other Wiki Foundation material, and also based on other thoughts about how to improve the content, I am now thinking that adding more images would be a good idea.

Wish list

 * Would be good if turtle link on each page (other than book-cover page) for navigating to the navigation controls at the bottom of each page, were animated when hovering the mouse pointer over it, such that the turtle appeared to be swimming forward. It looks like this can be done by simply animating from the current unicode string to a different unicode string. The following animation transition might be good:

 * --MarkJFernandes (discuss • contribs) 14:24, 27 April 2020 (UTC)

 * Would like to convert all gold-coloured headings into collapsible blocks, that are collapsed by default. I feel this would really make the book more usable. I can do this, but then the problem is that hyperlinks that link to anchors within such collapsible blocks, do not work when the blocks are collapsed (which is undesirable). It does look like that Javascript code can be used to expand such collapsible blocks before such hyperlinks are executed. However, I don't have specific guidance on how to do this for Wiki pages (for conventional websites, I could probably fairly easily do this). It does seem possible to do this for Wiki pages, perhaps with the use of some kind of book-wide `common.js` file however, it will likely take a while for me to figure out how to do this. It's best to leave this for now, and have it on the book's wish list.
 * --MarkJFernandes (discuss • contribs) 14:24, 27 April 2020 (UTC)

 * Would be good to have a hover-over Wikipedia page preview, for all Wikipedia page links (like how they have on Wikipedia). Have made a feature request regarding this here. It seems likely that this functionality is already available, but it appears it may take a while to figure out how to use it. Best to place it on the ongoing wish list for the time being.
 * --MarkJFernandes (discuss • contribs) 14:24, 27 April 2020 (UTC)

 * Book search currently doesn't return more than one result when more than one match occurs on a page. Such functionality is desirable for this book, where each chapter is stored on its own page. Have asked in the Technical Assistance reading room for help. Also would be good if icon and/or text for book search, matched colour scheme of book.
 * --MarkJFernandes (discuss • contribs) 08:58, 28 April 2020 (UTC)
 * The Wiki transclusion functionality might be helpful in the implementation of such book search functionality.
 * --MarkJFernandes (discuss • contribs) 08:28, 29 April 2020 (UTC)
 * The idea of restructuring chapter pages so that each section is on its own page, and then using transclusion to pool all chapter sections together so that a chapter can also be viewed on a single page, appears to be a good idea for implementing the book search functionality. With such in place, hopefully it would be possible to return several search hits for some search, even though the different hits be all for the same chapter. Another advantage of this approach, is that the page categorisation can be more refined. At the moment, a page containing much content, may be categorised into a category where there is only one small section on the page applying to the category. With this new approach, such course-grained categorisation can be avoided, with the knock-on effect of improving the categorisation system of the whole book.

 * Probably would be better to use paths indicating chapter number within total number of chapters, so that at top of page, this information is seen clearly in a large font size. For example, perhaps a path such as:
 * can be used. Probably best not to use folder names for this as users may get the impression that more than one page is contained in each chapter. Also, on each chapter page, the heading of 'Chapter n' where n is the chapter number, should probably be changed to 'Chapter n of 10'. A concrete example: 'Chapter 5 of 10'. This helps readers to get an idea of how far through the book they are, as well as how large the book is based on the amount of content that is on the page they are reviewing.
 * can be used. Probably best not to use folder names for this as users may get the impression that more than one page is contained in each chapter. Also, on each chapter page, the heading of 'Chapter n' where n is the chapter number, should probably be changed to 'Chapter n of 10'. A concrete example: 'Chapter 5 of 10'. This helps readers to get an idea of how far through the book they are, as well as how large the book is based on the amount of content that is on the page they are reviewing.

--MarkJFernandes (discuss • contribs) 11:28, 28 April 2020 (UTC)
 * Upon reflection, might be best not to change path such that chapter number information is included in it. The reason is if the number of chapters change, or the chapter ordering changes, the URLs may then have to change again resulting in any links to the old URLs becoming broken (which is undesirable). Instead, see whether the pages can be customised so as to either suppress or shrink the path shown at the top of each page (for this page, the path text is currently 'User talk:MarkJFernandes/End-user Computer Security'). I think this is likely possible seeing as the table of contents on pages can be customised.

--MarkJFernandes (discuss • contribs) 11:35, 1 May 2020 (UTC)

 * Would be good to have up-vote and down-vote buttons displayed next to each section heading, or similar web 2.0 features, so that users can easily indicate whether they like, dislike, agree, or disagree with a section. Has now been implemented in "Upvote_downvote_section_links" template.
 * --MarkJFernandes (discuss • contribs) 15:20, 28 April 2020 (UTC)

See here for wish list related to up-voting and down-voting sections. --MarkJFernandes (discuss • contribs) 14:13, 30 April 2020 (UTC) --MarkJFernandes (discuss • contribs) 10:32, 1 May 2020 (UTC) MarkJFernandes (discuss • contribs) 15:08, 1 May 2020 (UTC)
 * In the navigation controls in the footer of each page (module), a likely improvement is to have a re-sizeable  HTML element that displays (via linking) the contents of the 'Preliminaries' page. This would be an improvement because users would then not need to navigate back to the Preliminaries page each time, when wanting to access the contents, index, or foreword.
 * Make greater use of book-specific templates, by creating them just for this book, especially for the banner and footer of each page/module (the code of which is mostly duplicated for each page).

 * It is possible to use CSS files for styling and it is not that it is only possible to use CSS in the style attributes of the Wikitext. Therefore, it would be a very good idea to use CSS classes for the different styles used in the book—it would reduce code duplication to make it just better code. The way that such CSS files can be used, is exampled in the Template:End-user_Computer_Security/Upvote_downvote_section_links. The  tag has a   attribute that can be set, so that in the final page rendered to users, all   elements with their class attribute set to some value you set, have the related CSS-file styling applied to their contents. See Extension:TemplateStyles for more about this.

 MarkJFernandes (discuss • contribs) 09:30, 28 May 2020 (UTC)

MarkJFernandes (discuss • contribs) 10:13, 5 May 2020 (UTC)  MarkJFernandes (discuss • contribs) 15:26, 26 May 2020 (UTC)
 * Perhaps replace texts like 'section entitled' with the section symbol ( § ) for conciseness and perhaps better readability? If doing this, remember to add hover text so that user can hover over symbol to get some explanation as to what it means (HTML title attribute can be used for this).
 * As indicated at Reading_room/Technical_Assistance, in order to facilitate section-sensitive search results, a chapter can be split into its constituent sections where each section is stored on its own page, and then through transclusion, the chapter can be reconstructed onto a single page. I mooted this idea about a month ago (as can be seen at the just-mentioned link) and no one has given me particular feedback on it. I'm inclined to believe that the idea would work in practice because it hasn't yet received any negative feedback. Additionally, If the chapters are split up in such ways, Wikibook CATEGORIES categorising can be performed in a section-sensitive way, which seems like a really good idea. Therefore, doing such chapter conversions is on this wish list. When a section is placed on its own 'standalone' page, it should also contain a link that takes the user to the section as transcluded on its chapter page; this way, when users traverse links taking them to such 'standalone' pages, they can easily get to how the section should properly be read on its chapter page. In fact, automatic redirects to the parent chapter page may be even better than such links.

Userboxes on main page?
Hello!

I just noticed that userboxes on the main page of this Wikibook have caused it to be included in at least one userbox category. Is there a way to make it so the userboxes appear, but are not added to the category?

Thanks! --Mbrickn (discuss • contribs) 14:34, 23 June 2021 (UTC)

title: Talk:End-user Computer Security


text:
Adventist Youth Honors Answer Book/Outreach/Christian Citizenship (India)

6. Have an interview with a local, regional, or national official of your country, and learn about his duties.
It is generally easier to get a local official to agree to an interview, though it is often more exciting to interview a more prominent person. The interview can be accomplished during a club meeting, and multiple Pathfinders can ask questions. Invite your guest well ahead of time, and make sure everyone in the club is on time. A visit by an official would be a very good reason to have everyone in the club wear their class A uniforms. If desired, you can make up several questions ahead of time, writing them on index cards, and distributing them to the members of your club. But do not be so rigid as to not allow them to ask spontaneous questions. Having questions prepared ahead of time on index cards are a good way to get things rolling. Here are some suggested questions:
 * Could you describe a typical day at work?
 * What is the most difficult part of your job?
 * What is the most satisfying aspect of your job?
 * To whom do you report?
 * How did you get your position? Were you elected, appointed, or hired?
 * How should a young person prepare for a life of public service?

7. Write a one-page essay or give a two-minute oral report about a famous person in your country. Mention what he has done to gain his recognition.
This would be an excellent opportunity to present a worship during the opening exercises of a regular club meeting. Encourage your Pathfinder to choose a person they are personally interested in. If they cannot think of anyone themselves, have a list of suggested persons at hand and encourage them to choose from the list. Famous people might be historical figures, politicians, actors, sports stars, or anyone else. It would be preferable to choose a person who has been a positive influence on the country.

Although the requirement asks that you "mention what he has done to gain his recognition," this should not be interpreted as excluding women. Men are not the only famous people in a country.

Note that just because the requirement suggests that the famous person should be male (his recognition), the Pathfinder should in no way feel constrained to limit the selection to just men.

9. Describe what you can do as a citizen to help your church and country.
The best way to help either your church or your country is by getting involved. Edmund Burke, an English philosopher summed this up when he said "The only thing necessary for the triumph of evil is for good men to do nothing."

In your church, this means that you will show up for services on a regular basis. It also means you will support it with your tithes and offering, show up for business meetings, and not wait to be asked before you volunteer your services. If you see something that needs done, do it. If you do not have the skill to do it, or you think that you need permission first, talk to your pastor, an elder, deacon, or deaconess. Find your ministry!

For your country, it is much the same. Show up for public meetings, stay informed about the issues of the day, vote if you are eligible, and pay your taxes fairly and promptly.

12. Explain the meaning of this statement Jesus made in Matthew 22:21: "Render therefore unto Caesar the things which are Caesar's, and unto God the things that are God's.
This verse teaches that governmental authority is to be respected, as long as it does not conflict with the moral obligations of being a Christian. Government serves a holy purpose; preserving social order, promoting the well-being of its citizens, and protecting their safety. If you believe that this does not apply today because you see the government as corrupt, you are urged to research the Roman government of the first century A.D. when these words were spoken by Jesus. Was Herod corrupt? Was Pilate just?


text: Irish/Vocabulary/Insults

title: Irish/Vocabulary/Insults


text: Irish/Vocabulary/Fruit

title: Irish/Vocabulary/Fruit


text: Irish/Vocabulary/School subjects

title: Irish/Vocabulary/School subjects


text: Irish/Vocabulary/Vegetables

title: Irish/Vocabulary/Vegetables


text: Irish/Vocabulary/House

title: Irish/Vocabulary/House


text:
Irish/Vocabulary/Animals

This lesson is part of Unit 3 of WikiBooks Irish, a comprehensive open-source course in the Irish language. Lessons in Unit 3 are intended for the advanced Irish learner and contain specialized vocabulary and language notes for specific subject areas.

Talking About Animals
When discussing ainmhí (animals) as gaeilge, bear in mind the following:

Pronouns
Because Irish has no neutral pronouns, animals take the pronoun appropriate to the grammatical gender of the word in question. Most general names for animal species are masculine.

Eating Animals
As in English, in some cases different words are used for the animal's meat when used as food than when discussing the living animal. These words will be considered separately in the Unit 3 lesson on food.

title: Irish/Vocabulary/Animals


text:
Talk:The Church of Jesus Christ of Latter-day Saints/Church Service

Deletion of Church Meetings?
Should this page be merged with "Church Meetings". The information in "Church Meetings" could be easily added to "Church Service" seeing as it only has three sentences. The other page talks about the length of the meetings and nothing else. I have put a Request for Deletion on the page, so that people can go and discuss it on the proper page. PeanutHat (discuss • contribs) 06:33, 24 May 2020 (UTC)


text:
User talk:PeanutHat

Hey guys, welcome to my talkpage!

Welcome
Welcome, PeanutHat!

If you have any questions, you can ask in the assistance reading room or possibly contact me personally. -- Jules (Mrjulesd) 17:08, 29 May 2020 (UTC)

title: User talk:PeanutHat


text:
User:PeanutHat

Hey, welcome to my userpage. I'm currently helping with The Church of Jesus Christ of Latter-day Saints but I'm also a science nerd, and Dungeons and Dragons Dungeon Master.

title: User:PeanutHat


text:
User:Benjamin J. Burger/sandbox

testing testing testing this is a test...

title: User:Benjamin J. Burger/sandbox


text:
User:SEAN ANDILE 25

Hiii💦⚡ My name is SEAN I use wikipedia because its fun and u get to gain more knowledge..

title: User:SEAN ANDILE 25


text:
History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Australasian Radio World

Australasian Radio World was an early radio periodical which circulated primarily in Australia but also to a lesser extent in New Zealand. It commenced publication in April 1936 and its content was initially focused on the amateur and broadcast listener community with a variety of technical articles as well of reports of amateur radio activities and details of recent loggings of amateur and broadcast (medium wave and shortwave) stations.

Publishers, Owners and Editors
Australasian Radio World was a relatively small publication and throughout its print run the roles of ownership, publisher and editor were mostly commonly held and driven by a single passionate individual, often with little additional support. At its commencement in May 1936, it was published by Alfred Earl "Earl" Read, an expatriate New Zealander and former editor of the New Zealand Radio Times. From the December 1936 issue, the publisher formally became Trade Publications Proprietary Limited, but that firm had been behind the publication from its outset. The company was formed in April 1936 as printers and publishers, with initial subscribers Edward Marriott, Alfred Earl Read, Frederick S. Wales, Archie N. A. Wales, John C. L. Driver, Doris Wood and Clive B. Mellor. First directors were Frederick S. Wales and Archie N. A. Wales. Frederick S. Wales, Archie N. A. Wales and John C. L. Driver also had major interests in the magazine's printers Bridge Printery Pty. Ltd. From the April 1939 issue, with the magazine in financial difficulties, the publisher transitioned to Read Publications, a partnership solely between Alfred Earl Read and Frederick Stephen Wales. The rights to the publication were acquired by Allan Galbraith "Braith" Hull, with the first issue under his proprietorship being March 1940.

Publishers
The magazine was initially published by Trade Publications of Sydney, with A. Earl Read as Editor (he was an expatriate New Zealander). Allen Galbraith Hull (brother of the more widely known Ross Hull) purchased the magazine in 1940 and resigned his editorship of Radio and Hobbies. Hull became editor of Australasian Radio World and continued in that capacity until he sold the publication in November 1950. The new owner was Radio and Electronics (N.Z.) Ltd.

Notes prepared to develop this portion of the article (including transcriptions of publication notes from each magazine issue) can be found here:

Australasian Radio World - Publication Notes - all available issues complete

Printers
Printing of the magazine was undertaken by Bridge Printery from the initial issue in May 1936 until February 1949 and there was a close relationship between this printer and the two publishers of the period. At commencement the printer was located at 214 George St, Sydney, but in January 1940 the firm relocated to 117 Reservoir St., Sydney. Bridge Printery's period of responsibility for production was almost 13 years, including all but the final two years of the magazine's print run. In the magazine's tenth anniversary issue on May 1946, Braith Hull paid tribute to Bridge Printery's service in glowing terms, noting that production was personally supervised by the principal Fred Wales and his son Noel. As well as the actual printing, the firm took responsibility for magazine wrapping and bulk postage. Publisher Hull had relocated to Melbourne in the mid 1940s to assist with the war effort and struggled with liaison with a Sydney printer. Hull's plan was to establish his own printshop at his Mornington mansion. As an interim measure, Crusader Press of Auburn, Victoria printed two issues in early 1949. The following ten issues till March 1950 were printed by Hull's local newspaper, the Mornington Post. As a result of post World War 2 problems with paper supply and printshop capacity, there were no issues produced for April and May of 1950. Hull again reallocated the placement of printing to The Clyde Press of Thornbury and that firm produced the remaining magazine issues for 1950. However, the magazine was sold late 1950 with transfer of ownership commencing 1 December 1950. The new owners Cranch / Radio & Electronics (NZ), returned printing to Sydney, commencing January 1951. Printing was undertaken by R. V. Byers (an ARW advertiser) of North Lidcombe for the first half of 1951. When Cranch's own company Radio & Electronics (Aust.) assumed control, printing was undertaken by Acacia Press of Annandale, New South Wales. However Cranch's financial difficulties resulted in cessation of production, with the last issue being October 1951.

Notes prepared to develop this portion of the article (including transcriptions of statements as to printer from each magazine issue) can be found here:

Australasian Radio World - Printers - all available issues transcribed

Editorials
There were three editors over the lifetime of the magazine: Read, Hull and Cranch. Read only chose to include editorials sporadically, while both Hull and Cranch rarely missed an editorial each month.

For ease of reference, a complete set of the text-corrected editorials is being progressively developed here:

Australasian Radio World - Editorials (all available issues complete)

Issues
An almost complete set of magazines (primarily links to the AmericanRadioHistory webpages) can be found here, a small number have text cut and pasted from the OCR'd PDF, and an even smaller number have been fully text corrected:

Australasian Radio World - Issues

Contents
The contents pages of each issue have been amalgamated here as an index and finding aid to specific articles and authors:

Australasian Radio World - Contents - A brief start

Issue List
For ease of reference, to supplement the transcriptions of each monthly issue, particular types of magazine content have been brought together in single pages (eg. publication notes, printer statements, editorials etc.). To assist the creation of this type of content a list of issues has been prepared for use as an initial proforma:

Australasian Radio World - List of Issues ARW

Guide to Editing
Several sections of ARW changed little in format and even content from month to month. To assist in achieving greater consistency of presentation in this Wikibook, a proforma approach has been developed:

Australasian Radio World - Guide to Editing ARW


text:
SPARQL/FAQ

The most popular questions-and-answers can be obtained through external links:

 * Most popular SparQL questions
 * Most popular Wikidata questions

title: SPARQL/FAQ


text:
User:Benjamin J. Burger

Benjamin J. Burger is a geologist and paleontologist who earned his Masters of Science degree in 1999 at Stony Brook University in New York and Doctorate in 2009 at the University of Colorado in Boulder, and spent five years working at the American Museum of Natural History in New York City. He has also worked as a professional geologist in the states of Utah, Colorado, and Wyoming. He joined the Utah State University faculty in 2011 and continues to teach and conduct research as an Associate Professor in the Department of Geoscience at the Uintah Basin – Vernal Campus of Utah State University located in northeastern corner of Utah. Many of his course lectures and educational content can be found on YouTube or on his website at www.benjamin-burger.org

Benjamin J. Burger is currently working on an Open Educational Resource textbook entitled "The Essential Guide to Planet Earth" which is will be available as a Creative Commons textbook, via wikibooks in 2020.

title: User:Benjamin J. Burger


text:
Planet Earth

Wikibook-Cover.gif

Front Matter

 * Introduction
 * About the Book

Section 1: EARTH’S SIZE, SHAPE, AND MOTION IN SPACE

 * a. Science: How do we Know What We Know?
 * b. Earth System Science: Gaia or Medea?
 * c. Measuring the Size and Shape of Earth
 * d. How to Navigate Across Earth using a Compass, Sextant, and Timepiece
 * e. Earth's Motion and Spin
 * f. The Nature of Time: Solar, Lunar and Stellar Calendars
 * g. Coriolis Effect: How Earth’s Spin Affects Motion Across its Surface
 * h. Milankovitch cycles: Oscillations in Earth’s Spin and Rotation
 * i. Time: The Invention of Seconds using Earth’s Motion

Section 2: EARTH’S ENERGY

 * a. Energy and the Laws of Thermodynamics
 * b. Solar Energy
 * c. Electromagnetic Radiation and Black Body Radiators
 * d. Daisy World and the Solar Energy Cycle
 * e. Other Sources of Energy: Gravity, Tides, and the Geothermal Gradient

Section 3: EARTH’S MATTER

 * a. Gas, Liquid, Solid (and other states of matter)
 * b. Atoms: Electrons, Protons and Neutrons
 * c. The Chart of the Nuclides
 * d. Radiometric dating, using chemistry to tell time
 * e. The Periodic Table and Electron Orbitals
 * f. Chemical Bonds (Ionic, Covalent, and others means to bring atoms together)
 * g. Common Inorganic Chemical Molecules of Earth
 * h. Mass spectrometers, X-Ray Diffraction, Chromatography and Other Methods to Determine Which Elements are in Things

Section 4: EARTH’S ATMOSPHERE

 * a. The Air You Breathe
 * b. Oxygen in the Atmosphere
 * c. Carbon Dioxide in the Atmosphere
 * d. Green House Gases
 * e. Blaise Pascal and his Barometer
 * f. Why are Mountain Tops Cold?
 * g. What are Clouds?
 * h. What Makes Wind?
 * i. Global Atmospheric Circulation
 * j. Storm Tracking
 * k. The Science of Weather Forecasting
 * l. Earth’s Climate and How it Has Changed

Section 5: EARTH’S WATER

 * a. H2O: A Miraculous Gas, Liquid and Solid on Earth
 * b. Properties of Earth’s Water (Density, Salinity, Oxygen, and Carbonic Acid)
 * c. Earth’s Oceans (Warehouses of Water)
 * d. Surface Ocean Circulation
 * e. Deep Ocean Circulation
 * f. La Nina and El Nino, the sloshing of the Pacific Ocean
 * g. Earth‘s Rivers.
 * h. Earth’s Endangered Lakes and the Limits of Freshwater Sources
 * i. Earth’s Ice: Glaciers, Ice Sheets, and Sea Ice

Section 6: EARTH’S SOLID INTERIOR

 * a. Journey to the Center of the Earth: Earth’s Interior and Core
 * b. Plate Tectonics: You are a Crazy Man, Alfred Wegener
 * c. Earth’s Volcanoes: When Earth Goes Boom!
 * d. You Can’t Fake an Earthquake: How to Read a Seismograph
 * e. The Rock Cycle and Rock Types (Igneous, Metamorphic and Sedimentary)
 * f. Mineral Identification of Hand Samples
 * g. Common Rock Identification
 * h. Bowen’s Reaction Series
 * i. Earth’s Surface Processes: Sedimentary Rocks and Depositional Environments
 * j. Earth’s History Preserved in its Rocks: Stratigraphy and Geologic Time

Section 7: EARTH’S LIFE

 * a. How Rare is Life in the Universe?
 * b. What is Life?
 * c. How did Life Originate?
 * d. The Origin of Sex
 * e. Darwin and the Struggle for Existence
 * f. Heredity: Gregor Mendel’s Game of Cards
 * g. Earth’s Biomes and Communities
 * h. Soil: Living Dirt
 * i. Earth’s Ecology: Food Webs and Populations

Section 8: EARTH’S HUMANS AND FUTURE

 * a. Ötzi’s World or What Sustainably Looks Like
 * b. Rise of Human Consumerism and Population Growth
 * c. Solutions for the Future
 * d. How to Think Critically About Earth's Future

title: Planet Earth