User:Dubiousjim/Markup notes

(not displayed)

While "display: none" produces nothing, "visibility: hidden" produces blank spaces replacing the content; its opposite is "visibility: visible". {| class="collapsible wikitable" style="width:34em" ... |} Can I make transparent borders and rules on a table? I think the easiest way to write this is using wiki table notation with a different background for the table and for each row. {|style="background:white" |- style="background:lightgrey;" | abc || def ||ghi |- style="background:lightgrey;" | jkl || mno || pqr |} <ol style="list-style-type:lower-roman"> <pre> Indented ordered lists: <ul> #abc #def </ul> or, to use different starting value: <ul> <ol start=3>  <li>abc <li value=40>def </ol> </ul> </pre> {{TALKPAGENAME}} [[wikipedia:Sunflower]] {{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAMEE}}|action=raw}} {{fullurl:pagetitle|action=edit}} The reserved name [[#top]] always links to the top of a page. On page A:B/c/d, where A is a namespace with the subpage feature enabled, {{BASEPAGENAME}} gives B/c and {{SUBPAGENAME}} gives d : [[../]] links to the parent of the current subpage, e.g., on A/b it links to A, on A/b/c it links to A/b : [[../s]] links to a sibling of the current subpage, e.g., on A/b, it links to A/s : [[/s]] links to a subpage, e.g. on A it is the same as [[A/s]]. Because of this, linking from a namespace where the subpage feature is enabled to a page in the main namespace with a name starting with "/", requires a workaround: put a colon before the pagename. : Linking to an anchor of an ancestor in these forms does not work. The first letter of articles is automatically capitalized, so wikipedia goes to the same place as Wikipedia. Capitalization matters after the first letter. Writing a symbol over another one: <span style="position:absolute;">o</span>x before a box? <div style="clear: both;"></div> {{localurl:foo|printable=yes}} ~~> /w/index.php?title=foo&printable=yes {{fullurl:...}} includes http://{{SERVERNAME}}{{localurl:...} {{urlencode:string|WIKI}} (uses _ and %C3) or |QUERY (uses + and %C3) or |PATH (uses %20); default was WIKI, became QUERY {{anchorencode:string}} for #section_anchors {{ns:0}} ~~> "" {{lc:StRing}} {{lcfirst:StRing}} {{plural:2|is|are}} {{nowrap|text}} ~~> <span style="white-space:nowrap">{{{1}}}</span> {{inlinepre|text}} ~~> <span style="padding:2px; background:#F9F9F9; border:1px dashed #2F6FAB; font:0.9em monospace;">{{{1}}}</span> {{right|text}} ~~> <div align="right">{{{1}}}</div> {{rightcolumn|text}} ~~> <div style="float:right; clear:right;">{{{1}}}</div> ;; stacks with anything else floated in rightcolumn {{border|text}} ~~> <span style="display:inline"><span style="display:table-cell; border-collapse:collapse; border: solid 1px #ddd;">{{{1}}}</span></span> {{center|text}} ~~> <div align="center">{{{1}}}</div> {{hidden|header|content|fwl=bold|bg1=transparent|ta1=center|headercss=|fw2=normal|bg2=transparent|ta2=left|contentcss=}} ~~> <div class="NavFrame" style="border:none;"><div class="NavHead" style="font-weight:{{{fw1|bold}}};background-color:{{{bg1|transparent}}};text-align:{{{ta1|center}}};{{{headercss|}}}">{{{header|{{{1}}}}}} </div><div class="NavContent" style="display:none;font-weight:{{{fw2|normal}}};background-color:{{{bg2|transparent}}};text-align:{{{ta2|left}}};{{{contentcss|}}}">{{{content|{{{2}}}}}}</div></div> {{tag|ref|content=hello}} ~~> <ref>hello</ref> {{tag|font|open|content=hello}} ~~> <font>hello {{tag|ref|open|params=group=note}} ~~> <ref group=note> {{tag|br|single}} ~~> <br /> ==> <code style="white-space:nowrap;">{{#switch:{{{2|pair}}} |c|close =  |s|single |o|open |p|pair = <{{{1|tag}}}{{#if:{{{params|}}}| {{{params}}}}} }}{{#switch:{{{2|pair}}} |c|close = {{{content|}}} |s|single = /> |o|open = >{{{content|}}} |p|pair = >{{{content|...}}} }}{{#switch:{{{2|pair}}} |s|single |o|open =  |c|close |p|pair = </{{{1|tag}}}> }}</code> The Table of contents can be forced onto a floating table on the right hand of the screen with the code below: {| align="right" | __TOC__ |} Search is case-insensitive Search for a phrase by enclosing it in double quotation marks. You can use a wildcard *, at the end of a search term only. If a word appears in a page with single quotes, you can only find it if you search for the word with quotes. Since this is rarely desirable it is better to use double quotes in pages, for which this problem does not arise. An apostrophe is identical to a single quote, therefore Mu'ammar can be found searching for exactly that (and not otherwise). A word with apostrophe s is an exception in that it can be found also searching for the word without the apostrophe and the s. PageHistory ----------- [Compare selected versions] (<cur> | last) [x] 11:35, 8 March 2012 Dubiousjim (Talk | contribs) (226 bytes) (Removed A B) (undo) ( cur | last) [x] 11:35, 8 March 2012 Dubiousjim (Talk | contribs) (232 bytes) (added B, removed NavFrame) (undo) ( cur | last) [ ] 11:34, 8 March 2012 Dubiousjim (Talk | contribs) (563 bytes) (Added A) (undo) ( cur | last) [ ] 08:43, 8 March 2012 Dubiousjim (Talk | contribs) (560 bytes) (undo) "last" shows diff between that edit and the one preceding it. "cur" shows diff between that edit and the current page (which may be newer than any edit shown, if the displayed history is stale). The "cur" and "last" features are similar to those in Enhanced Recent Changes, except for "cur" in the first line: it is not linked in the revision history, while in the Enhanced Recent Changes it gives the differences corresponding to the last edit. RecentChanges ------------- 8 March 2012 m 11:37 Contribute‎ (diff | hist) . . (-5) . . Fab (Talk | contribs) > N 11:35 User:Dubiousjim/Sandbox‎‎ (18 changes | hist) . . (+226) . . [Dubiousjim‎ (18×)] v N 10:43 Talk:Site improvements‎‎ (7 changes | hist) . . (+4,062) . . [Dubiousjim‎ (7×)] 10:43 (cur | last) . . (+129) . . Dubiousjim (Talk | contribs) (Suggest more editing help links) 10:39 (cur | last) . . (+62) . . Dubiousjim (Talk | contribs) (Privacy policy/copyright link) 10:37 (cur | last) . . (+124) . . Dubiousjim (Talk | contribs) (suggest link to Special:Version) 10:35 (cur | last) . . (+230) . . Dubiousjim (Talk | contribs) (Add some more wiki suggestions) m 10:32 (cur | last) . . (-33) . . Dubiousjim (Talk | contribs) (markup error) 10:31 (cur | last) . . (+857) . . Dubiousjim (Talk | contribs) (Add some more wiki suggestions) N 10:19 (cur | last) . . (+2,693) . . Dubiousjim (Talk | contribs) (Create page) The "diff" and "last" links here works like "last" in PageHistory. The "cur" links work like "cur" in PageHistory, except that in RecentChanges it's also enabled for the topmost edit. The "n changes" link (for non-New pages) shows a diff of original state vs all the grouped changes together. {{Codeline|text}} ~~> <span style="font-family:monospace; color:#000055; white-space:nowrap">{{{1}}}</span> How do I use a template as a signature? When you look at your preferences, you see a check box for "raw signature." But the field will only take a certain number of characters. What if you want more? You will need to create two pages, possibly in your userspace. Create the first page (FIRST PAGE) Go to your preferences, check "raw signature" and put {{FIRST PAGE}} in the signature. Save Create a second page (SECOND PAGE) (possibly a sub-page of the first) Go back to the first page (FIRST PAGE) and do {{SECOND PAGE}} Go to the second page (SECOND PAGE) and place the code you wish to have for your signature. If you don't have this structure, you will still be inserting all your signature code into the raw code wherever your signature is used, because the software will insert "SUBST" in your preferences. You may not mind this, in which case you only need one page. If you want the raw code to only display {{FIRST PAGE}}, which looks a lot cleaner, then you need to use the two-page structure. How to move a page (Wikipedia) A common example: moving a userspace draft into place. The intended article name is entered without any prefixes. A move will fail if a page already exists at the target name, unless it is simply a redirect to the present name that has never been modified (check the edit history). The steps for moving a page are as follows: With the page to be moved displayed, choose the "move" option near the top of the page. In the default Vector skin, this is in a drop-down menu to the right of the screen, after "History" and the "Watchlist" star (see picture). In the Monobook skin, it is a tab at the top. You'll be asked for a new name for the page, and given the option to also move the page's talk page (this box should usually be left checked). Complete the "Reason for move" field (which is like an edit summary). Although filling out the "Reason" field isn't required, you should state a reason for the page move. When ready, click the move button and, if successful, the page will be renamed to the new title. The old title will become a redirect page, so any links to the old title will still go to the new page. However, note that double redirects (pages that redirect to the original page), will not automatically follow to the new page, so you will have to refer them manually (as explained at How to fix a double redirect and Checking for double redirects). However, if you're an administrator, you can move pages without leaving a redirect behind. Open the what-links-here for that page (there may be a shortcut link on the page-moved summary screen to let you do this, but the what-links-here link will in any case be in the toolbox, which is near the bottom of the sidebar unless you've customized your skin away from the default Vector). In the section of that page marked filters, click on the button labeled "Hide links". This will result in the page only showing redirects to the prior name. Open each of the redirect pages (best to do so in new tabs), click edit this page for each one, and change their target to the name of the page to which you have moved the page. Though this is an important cleanup step, if you miss some, they will normally be fixed by a bot shortly afterwards. If there are more than 50 redirects listed (rare) on the "what links here" page, don't forget to navigate to all parts of the list using the "next 50" or other links available. Since the article name is reflected in the lead section, that section may need to be updated to be consistent with the new name. If you moved an article which contains any non-free content (such as images or sound clips), you will need to edit the files' own Wikipedia page, changing the non-free use rationale to refer to the new article title. This is to ensure continued compliance with the non-free content criteria (part 10c), which if not followed, may result in the file's speedy deletion. Once the page has been moved, this will be recorded in the Move Log and a "move has succeeded" message will be displayed. Console and Text browsers Warning: Many console browsers will convert text in edit boxes to the encoding in use by your terminal (or what the browser thinks is your terminal's encoding which may not be the same thing) either at page load time (links and lynx) or when editing a field (w3m). If your terminal encoding is UTF-8 this is not a problem but if your terminal is using a legacy encoding (or is using UTF-8 but your browser thinks it's using a legacy encoding) then this is likely to destroy characters that are not present in the encoding your terminal is using when you save the page after editing. ELinks Text only, but renders tables and frames. Supports HTTP authentication. Users can use their text editor of choice to edit textarea fields. Problems with editing UTF-8; set "User-agent identification" (in setup->option manager->protocols->http) to something like "Lynx/elinks/%v (textmode; %s; %t-%b)" to get non-ascii characters as hex codes. View is enhanced (especially of diffs) by using the following user.css and lua hook file (place in ${HOME}/.elinks and enable via option manager) user.css: /* 1. place in ~/.elinks 2. set user css to be "user.css" (no path, relative to ~/.elinks) 3. use document colors: use 1 or 2 */ .diffchange { color: red; font-weight: bold; } .diff-deletedline { color: green; } .diff-addedline { color: cyan; } a.new { color: cyan; font-weight: bold; } hooks.lua: --[[ lua preformatting function 1. lua has to be installed before compiling elinks; if this is the case, it is used by default 2. place this file in ~/.elinks this file does: show <del> and <ins> element, make <s> more evident preformatting for wikipedia pages: since elinks ignores the class attribute of <td> tags, we move it into the inner <div> element ]] testing=false function pre_format_html_hook (url, html) -- formatting for <s> <del> <ins> html = string.gsub(html, '<[sS]>', '<s>[S:') html = string.gsub(html, '</[sS]>', ':S]</s>') html = string.gsub(html, '<[dD][eE][lL]>', '<s>[DEL:') html = string.gsub(html, '</[dD][eE][lL]>', ':DEL]</s>') html = string.gsub(html, '<[iI][nN][sS]>', '<s>[INS:') html = string.gsub(html, '</[iI][nN][sS]>', ':INS]</s>') -- diff-addedline and diff-deletedline classes if string.find(url, "diff=", 1, 1) or testing then html = string.gsub(html, '<td class="diff[-]addedline"><div>', '<td><div class="diff-addedline">') html = string.gsub(html, '<td class="diff[-]deletedline"><div>', '<td><div class="diff-deletedline">') end return html end Links In old versions the login may be broken. (Try to check referrer sending and cookie handling. If everything fails try to use ELinks, and check the same settings.) Lynx Users can use their text editor of choice to edit textarea fields (this feature needs to be enabled at compile time) Forces wrapping of very long lines in a textarea, which is a problem in editing some articles. Display options for non-ASCII characters affect editing. Most tables are rendered as simple text. Viewing of diffs and redlinks can be improved by adding the following to the lynx.lss configuration file: span.diffchange:bold:brightred td.diff-deletedline:bold:green td.diff-addedline:bold:cyan a.new:bold:cyan