This page has been removed from search engines' indexes.

Scratch edit

Phabricator tasks edit

AWB-2017-02-12


Timeless-2017-11-30


Quick tests edit

Classical and flamenco guitar templates edit

Welcome table edit


Citation templates edit

Citation templates
Citation Style 1 templates
{{Cite arXiv}}arXiv preprints
{{Cite AV media}}audio and visual media
{{Cite AV media notes}}AV media liner notes
{{Cite bioRxiv}}bioRxiv preprints
{{Cite book}}books and chapters
{{Cite CiteSeerX}}CiteSeerX papers
{{Cite conference}}conference papers
{{cite document}}short, stand-alone, offline documents
{{Cite encyclopedia}}edited collections
{{Cite episode}}radio or TV episodes
{{Cite interview}}interviews
{{Cite journal}}academic journals
{{Cite magazine}}magazines, periodicals
{{Cite mailing list}}public mailing lists
{{Cite map}}maps
{{Cite medRxiv}}medRxiv preprints
{{Cite news}}news articles
{{Cite newsgroup}}online newsgroups
{{Cite podcast}}podcasts
{{Cite press release}}press releases
{{Cite report}}reports
{{Cite serial}}audio or video serials
{{Cite sign}}signs, plaques
{{Cite speech}}speeches
{{Cite SSRN}}SSRN papers
{{Cite tech report}}technical reports
{{Cite thesis}}theses
{{Cite web}}web sources not covered by the above
See alsoSpecific-source templates
Citation Style 1 wrapper templates

Testing cite book template edit

Feel free to add examples

Using the cite book template edit

<ref>{{cite book | title=The Art of Tea | pages=34, 44, 56–67}}</ref> renders: [1]

<ref>{{cite book | title=The Art of Tea | pages=34}}</ref> renders: [2]

<ref>{{cite book | title=The Art of Tea | at=5–6, 34, 44}}</ref> renders: [3]

<ref>{{cite book | title=The Art of Tea | at=5}}</ref> renders: [4]

<ref>{{cite book | title=The Art of Tea | page=34}}</ref> renders: [5]

<ref>{{cite book | title=The Art of Tea | page=5–6}}</ref> renders: [6]

<ref>{{cite book | title=The Art of Tea | at=page 5, figure 6}}</ref> renders: [7]

<ref>{{cite book | title=The Art of Tea | at=p. 5, fig. 6, slide 2}}</ref> renders: [8]

<ref>{{cite book | title=The Art of Tea | pages=5–6 | page=123}}</ref> renders: [9]

<ref>{{cite book | title=The Art of Tea | pages=5–6 | page=123 | at=fig. 6}}</ref> renders: [10]

<ref>{{cite book | title=The Art of Tea | pages=5–6 | at=slide 9}}</ref> renders: [11]

References using only plain text (no citation template) edit

<ref>The Art of Tea, Lady Corinne, 1776, p. 6, at fig. 3</ref> renders: [12]

<ref>The Art of Tea, Lady Corinne, 1776, page 6, at figure 3</ref> renders: [13]

References

  1. ^ The Art of Tea. pp. 34, 44, 56–67.
  2. ^ The Art of Tea. p. 34.
  3. ^ The Art of Tea. 5–6, 34, 44.
  4. ^ The Art of Tea. 5.
  5. ^ The Art of Tea. p. 34.
  6. ^ The Art of Tea. p. 5–6.
  7. ^ The Art of Tea. page 5, figure 6.
  8. ^ The Art of Tea. p.5, fig. 6, slide 2.
  9. ^ The Art of Tea. p. 123. {{cite book}}: More than one of |pages= and |page= specified (help)
  10. ^ The Art of Tea. p. 123. {{cite book}}: More than one of |pages=, |at=, and |page= specified (help)
  11. ^ The Art of Tea. pp. 5–6. {{cite book}}: More than one of |at= and |pages= specified (help)
  12. ^ The Art of Tea, Lady Corinne, 1776, p. 6, at fig. 3
  13. ^ The Art of Tea, Lady Corinne, 1776, page 6, at figure 3
  1. Note: pages=34 still properly renders as: p. 34 (not the expected pp. 34)
  2. Note: at= renders without p. or pp.
  3. Note: at= may be used with a single page, random pages separated by commas, or a page range by using a hyphen separator‍—‌or more correctly by using an en dash separator

Practice tables edit

Feel free to edit this section, preview your edits, cancel your edits, or save your edits.

Without border edit

Name of the Ara Degree of happiness Duration of Ara Average height of people Average lifespan of people
Sukhama-sukhamā Utmost happiness and no sorrow 400 trillion sāgaropamas Six miles tall Three palyopama years
Sukhamā Moderate happiness and no sorrow 300 trillion sāgaropamas Four miles tall Two palyopama Years
Sukhama-dukhamā Happiness with very little sorrow 200 trillion sāgaropamas Two miles tall One palyopama years
Dukhama-sukhamā Happiness with little sorrow 100 trillion sāgaropamas 1500 meters 705.6 quintillion years
Dukhamā Sorrow with very little Happiness 21,000 years 6 feet 130 years maximum
Dukhama- dukhamā Extreme sorrow and misery 21,000 years 2 feet 16–20 years

With border edit

Name of the Ara Degree of happiness Duration of Ara Average height of people Average lifespan of people
Sukhama-sukhamā Utmost happiness and no sorrow 400 trillion sāgaropamas Six miles tall Three palyopama years
Sukhamā Moderate happiness and no sorrow 300 trillion sāgaropamas Four miles tall Two palyopama Years
Sukhama-dukhamā Happiness with very little sorrow 200 trillion sāgaropamas Two miles tall One palyopama years
Dukhama-sukhamā Happiness with little sorrow 100 trillion sāgaropamas 1500 meters 705.6 quintillion years
Dukhamā Sorrow with very little Happiness 21,000 years 6 feet 130 years maximum
Dukhama- dukhamā Extreme sorrow and misery 21,000 years 2 feet 16–20 years

Portal thumbnails edit

{{Portal|Molecular and cell biology}} (the main portal name) renders this:

{{Portal|Molecular and cellular biology}} (the redirect portal name) renders this:

Ideally, both would show the correct portal thumbnail, but as a workaround the main portal name should show the correct portal thumbnail.


Patents edit

U.S. patent 5,807,309


Dashes edit

|‐| (hyphen)
|‑| (nobreak hyphen)
|-| (from my laptop keyboard to the right of the zero key, below the F12 key)
|−| (inserted from the Wikipedia text editor window widget)

The first two are using the following HTML markup:
|&#8208;| (hyphen)
|&#8209;| (nobreak hyphen)

Oddly, #3 and #4 look the same width as each other in the edit PREVIEW window but when processed #4 is wider than #3

I observe that #3 is narrower than #1 and #2, that #1 and #2 are the same width, and that #4 is wider than all of them.

I put pipes on either side of them to make it easier to gauge their respective width.

That's interesting. I didn't even know about the code for the first one. I only make a hyphen with the key to the right of zero on my keyboard (your #3). However, #3 looks wider than either #1 or #2, which look the same to me. That would match what I said on your talk page, that the hyphen made with the key on the keyboard is wider than the no-break hyphen (#2). I'm really surprised that it looks narrower to you. To me, #1 and #2 are quite narrow, approaching a dot. #3 looks intermediate between #1/#2 and #4. What are all those "Tips of the day"? Corinne (talk) 16:14, 13 January 2016 (UTC)
Hi, Corinne. #3 is narrower than #1 or #2 for me. Running Windows 7 Professional on Firefox both with the latest updates. I'll look at it with Chrome and with Internet Explorer in a minute. The tip of the day versions down below I need to conjoin in to one version. The tip of the day library is here: [[[WP:Tip of the day]]]. Cheers! PS: By enabling the wikEd text editor gadget in my Preferences I get a tooltip so when I hover on dashes in the edit window it tells me what kind of dash it is. It puts a blue letter over each dash but it is too small to read without the hover. {{u|Checkingfax}} {Talk} 19:35, 13 January 2016 (UTC)
Corinne. Wow. On Chrome: 1, 2, and 3 are the same width, and 4 is much wider, but 3 is thicker in the sense that the hyphen is taller from top to bottom!
On Internet Explorer: 1 and 3 are about the same width but 3 is thicker (taller from top to bottom) and 2 and 4 are super wide but the same width as each other but with 4 being thicker (taller from top to bottom) than 2.
Yowsa! Cheers! {{u|Checkingfax}} {Talk} 19:46, 13 January 2016 (UTC)
Interesting. However, I am using Chrome. Because I'm using a small laptop, I have the resolution at 150%, so that might make a difference. Are you sure that, in Chrome, #3 is not wider (left-to-right) than #1 and #2? Can you increase the resolution somewhat and then look at it again? It's a slight difference, but noticeable. I think the slightly greater top-to-bottom width in #3 is because it is proportionately thicker due to its (in my screen) slightly greater left-to-right width. Corinne (talk) 22:45, 13 January 2016 (UTC)
Hi, Corinne. 3 is the slightest touch wider than 1 or 2, but 4 is insanely wider‍—‌in Chrome on Windows 7 Pro 64-bit. I have it magnified so they are taking up my whole screen (I hold down Ctrl and press the + key until it gets too big then back it off with Ctrl and the – key. To reset to normal view it's Ctrl+0 (the zero key). Cheers! {{u|Checkingfax}} {Talk} 12:50, 14 January 2016 (UTC)
I agree. That's what I had been saying. I like #3. To me, it is the right width. #1 and #2 are so narrow (left-to-right) that they look at a glance almost like dots. So I was wondering whether whoever designed the no-break hyphen would consider making it the same width as the keyboard hyphen (#3). (Also, if you look at the edit I made that started this discussion, don't you think that the no-break hyphen is closer to what follows it than a regular hyphen would be? It seems to be right up against the following word (number? Now I don't remember.) – a bit too close, I think. What do you think?) I think you'll agree that there are many times when it would be advisable to use the no-break hyphen so that the hyphen stays at the end of a line instead of going to the beginning of the next line, or stays completely between the numbers or number+word, but I hesitate to use it because of what it looks like. To me, #4 looks almost like an en-dash. Corinne (talk) 17:28, 14 January 2016 (UTC)
Hi, Corinne. I don't get pinged automatically from subpages. Those HTML escape codes are universal and then the operating system companies like Microsoft and browser companies like Google integrate the resulting font in to their operating system or in to their browser. So, Wikipedia does not have any control over it as far as I know. It's a computer/operating system/browser thing. Within the Wikipedia text editor the dashes look different than when they appear in the browser. I am not sure what kind of code the keyboard sends to the OS/browser. Cheers! {{u|Checkingfax}} {Talk} 03:03, 15 January 2016 (UTC)
O.K. Thanks. (We're probably the only people on WP fussing over the widths of hyphens.) Corinne (talk) 03:16, 15 January 2016 (UTC)

Conjoining tip of the day edit

Wikipedia:Tip of the day/June 30 edit

Custom signatures

Signatures in Wikipedia are identifying information that you put after writing a comment on a talk page. They tell other editors who wrote the comment and when. This can be done by writing ~~~~.

Signatures can optionally be spruced up with colors. To add color to your signature, go to the Preferences link at the top of the page. In the nickname box, enter [[User:MYUSERNAME|<font color="MYCOLOR">MYUSERNAME</font>]]. Replace "MYCOLOR" with a color you like, such as "red" or "green". Replace MYUSERNAME with your username. Finally, check the "raw signature" box, and save your preferences. Now, when you type four tildes ~~~~ in a talk page, your new signature will appear.

The color names that can be used in standard HTML are given in the standards document here. Using the hexadecimal RGB-style colors (such as #008000) you can choose any color you like from about sixteen million, not just the 140 colors that have names in standard HTML.

More complex signatures are possible; however, your signature as typed into the box above should not be unnecessarily long. Long signatures make pages larger and harder to edit, and are discouraged.

Read more:

Wikipedia:Tip of the day/November 6 edit

Advanced signatures

It is good Wikiquette to sign your messages on talk pages. This is done by typing ~~~~ (four tildes). Do not sign article pages.

Some users have fancy signatures with lots of colors and links. Here are 3 different ways to do that:

  1. Edit directly in the signature box
    1. Go to your preferences and type some wiki-markup code (and/or HTML markup code) into the signature box to augment your stock signature
    2. Check the box that says "Treat the above as Wiki markup"
    3. Press the "Save" button. Or...
  2. Use an HTML editor
    1. Open an HTML editor (e.g. Adobe Dreamweaver or Microsoft Expression Web)
    2. Design how you want your signature to look, putting links in it by adding brackets [[ ]]
    3. Select it and click the HTML tab and copy the code of your text into the signature box mentioned above.
    4. Be sure not to copy the tags at the beginning and end of the code that say <p> </p>. Or...
  3. Adapt someone else's signature
    1. Find a signature you like
    2. Click edit this page
    3. Copy and paste the signature into your signature box (see #1 above), but change all the links to your links: you don't want your signature leading to someone else's user page!

Do not use images, templates, or external links in your signature. Please ensure your custom signature complies with the relevant guideline. Use special code for displayed pipe character.

Read more:



Wikipedia:Tip of the day/December 5 edit

How to customize your signature

There is an input field in your user Preferences (in the Signature section, down the page). You can use that to specify a unique nickname to be displayed as your signature instead of your registered account name. This field may also be used to custom design your signature with wiki markup (check the box labeled Treat the above as Wiki markup).

Whenever you sign a post with ~~~ (nickname only), or ~~~~ (includes nickname and timestamp), your new nickname or wiki-markup will be used. Bonus tip #1: ~~~~~ (timestamp only).

Bonus tip #2: To display a nickname, the software adds [[User:Name| to the beginning of the nickname, and ]] to the end. So, by entering something like Klaaus Meieer]] [[User talk:Klaaus Meieer|(talk), you can "trick" the software into adding another link at the end, in this case, to your talk page, which will look like this: Klaaus Meieer (talk).


Hybrid version for publication incorporates all of the above versions edit

Advanced signatures

Some users have fancy signatures with lots of colors and links. Here are 3 different ways to do that:

  1. Edit directly in the signature box
    1. Go to your preferences and type some wiki-markup code (and/or HTML markup code) into the signature box to augment your stock signature
    2. Check the box that says "Treat the above as Wiki markup"
    3. Press the "Save" button. Or...
  2. Use an HTML editor
    1. Open an HTML editor (e.g. Adobe Dreamweaver or Microsoft Expression Web)
    2. Design how you want your signature to look, putting links in it by adding brackets [[ ]]
    3. Select it and click the HTML tab and copy the code of your text into the signature box mentioned above.
    4. Be sure not to copy the tags at the beginning and end of the code that say <p> </p>. Or...
  3. Adapt someone else's signature
    1. Find a signature you like
    2. Click edit this page
    3. Copy and paste the signature into your signature box (see #1 above), but change all the links to your links: you don't want your signature leading to someone else's user page!

Do not use images, templates, or external links in your signature. Please ensure your custom signature complies with the relevant guideline. Use special code for displayed pipe character. The color names that can be used in standard HTML are given in the standards document here. Using the hexadecimal RGB-style colors (such as #008000) you can choose any color you like from about sixteen million, not just the 140 colors that have alphabetic names in standard HTML.

Whenever you sign a post with ~~~ (nickname only), or ~~~~ (includes nickname and timestamp), your new nickname or wiki-markup will be used. Bonus tip #1: ~~~~~ (timestamp only).

Bonus tip #2: To display a nickname, the software adds [[User:Name| to the beginning of the nickname, and ]] to the end. So, by entering something like Klaaus Meieer]] [[User talk:Klaaus Meieer|(talk), you can "trick" the software into adding another link at the end, in this case, to your talk page, which will look like this: Klaaus Meieer (talk).



Hybrid version for publication - Alternative-A edit

Advanced signatures - Part one (July 17)

Some users have fancy signatures with lots of colors and links. Here are 3 different ways to do that:

  1. Edit directly in the signature box
    1. Go to your preferences and type some wiki-markup code (and/or HTML markup code) into the signature box to augment your stock signature
    2. Check the box that says "Treat the above as Wiki markup"
    3. Press the "Save" button. Or...
  2. Use an HTML editor
    1. Open an HTML editor (e.g. Adobe Dreamweaver or Microsoft Expression Web)
    2. Design how you want your signature to look, putting links in it by adding brackets [[ ]]
    3. Select it and click the HTML tab and copy the code of your text into the signature box mentioned above.
    4. Be sure not to copy the tags at the beginning and end of the code that say <p> </p>. Or...
  3. Adapt someone else's signature
    1. Find a signature you like
    2. Click edit this page
    3. Copy and paste the signature into your signature box (see #1 above), but change all the links to your links: you don't want your signature leading to someone else's user page!

For more details, Next tip below.


Advanced signatures - Part two (July 18)

A continuation of Prior tip...

Do not use images, templates, or external links in your signature. Please ensure your custom signature complies with the relevant guideline. Use special code for displayed pipe character. The color names that can be used in standard HTML are given in the standards document here. Using the hexadecimal RGB-style colors (such as #008000) you can choose any color you like from about sixteen million, not just the 140 colors that have alphabetic names in standard HTML.

Whenever you sign a post with ~~~ (nickname only), or ~~~~ (includes nickname and timestamp), your new nickname or wiki-markup will be used. Bonus tip #1: ~~~~~ (timestamp only).

Bonus tip #2: To display a nickname, the software adds [[User:Name| to the beginning of the nickname, and ]] to the end. So, by entering something like Klaaus Meieer]] [[User talk:Klaaus Meieer|(talk), you can "trick" the software into adding another link at the end, in this case, to your talk page, which will look like this: Klaaus Meieer (talk).


* Proposal: – Divide the combined/consolidated 3 tips into two in sequence TOTD, i.e., Day1, Day2. Regards, JoeHebda • (talk) 18:27, 6 May 2016 (UTC)