Italic - put two single quotes at each end of the text you want to be italic, ''like this'', or use HTML <i>like this</i>
Bold - put three single quotes at each end of the text you want to be bold, '''like this''', or use HTML <b>like this</b>
Monospace - start the line with a space, or enclose the text in <pre> .. </pre> tags.
Bullet lists - start the line with one or more *s. Each star starts a nested bullet list. This list is an example.
Numbered lists - start the line with one or more #s.
Headings - start and finish the line with one or more =s.
Horizontal lines - four dashes and nothing else on a line.
Indented paragraphs - start the line with a colon.
Labelled paragraphs - start the line with a semicolon, type the label text, type a colon, type the paragraph text.
Turning off formatting - use <nowiki> .. </nowiki> tags.
Links to other wiki pages - just type the name of the page. Wiki page names are made by running two or more CapitalisedWords together into a single word.
Links to other sites - just type the URL.
Inline images - type the URL of the image, and it'll get pulled in. If you don't have your own webspace to host images, you can upload images for use in the wiki to the /ImageServer (anyone can edit them, though - it's a wiki!)
Link labels: [(target URL or InterWiki) (name)] creates a link going to the target location with the label (name): for instance, link.
Linking to headings: every heading (in theory) generates an anchor which starts at the start of the heading, ends at the first nonalphanumeric character, and has spaces converted to _'s. You can create a link to this by appending #anchor name to a link to the page. (todo: rewrite in English)
#REDIRECT OtherPage?, as the first line of a page and with no leading whitespace, will create a redirectiction to OtherPage?.
$$CONTENTS, with no leading whitespace, will insert an autogenerated table-of-contents.
This does bad bad things in preview mode. Specifically, clicking on the links tends to lose the current edit. --Vitenka
Oh, I see. Presumably the part of the generated link up to the # isn't identical to the URL the browser used to get to the preview page. Hm. Actually, there's probably no particular reason to specify that part at all. *checks code* Wait, I am, in fact, actually *not* specifying that part at all! Um - could you run up a test case somewhere to confirm that your browser generally preserves the contents of a textarea you've edited when you navigate a # link? If so, can you suggest alterations to the HTML I currently generate, or at least tell me where I can find some HTML that contains textareas and # links that works for you that I can examine? FWIW, I can confirm that I can follow the generated TOC links in a preview window here (FireFox 1.0) without losing edited textarea contents, though TBH it's not something I was expecting to work. Ta.. - MoonShadow
Ah. Chalk it up to outdated browser then. It's probably because the page contents were generated - it thinks it wants to reload /wiki.pl - which of course destroys the text. I really ought to get FireFox working the way I want and leave Opera behind some day. --Vitenka (Maybe when I stop preferring Netscape2 to it.)
GRRRRRR! The HTML would be <EM>italics</EM> and <STRONG>bold</STRONG> (and only that by convention) Well, at least those work as well. Guess I can forgive that. --Vitenka <I> and <B> are travesties!
Hmm. Well. Actually, if you specifically want italics or bold themselves, then <I> or <B> would be what you'd use. I agree that if you want emphasis, then EM or STRONG tags would be what you'd use. But the paragraph as phrased above is accurate: the HTML to put some text into italics is the I tag, and the HTML to put some text into bold is the B tag. Whether that's what people should be trying to do is a different matter. --AlexChurchill, being [pedantic]
Except that <I> and <B> are only present as of some horrible bastardised version of html. Stay pure! Emphasise! --Vitenka
The wiki is not the place for HTML, certainly not for common formatting. HTML is not intuitive to read or write. People find it scary. Admittedly, apostrophes are not intuitive to write either, but at least they are not composed of letters and so are less distracting to read. Part of the goal is that common formatting does not make text in the edit box hard to read. If I wanted the wiki to use HTML, I'd just make a public FTP area. Limited HTML support is present for those that find it more intuitive, but its use shouldn't be pushed on those that don't. I have not meant it to be a general-public-use thing, more a something that gets mentioned in passing in the advanced detailed documentation for those that care. - MoonShadow
PeterTaylor finds long strings of apostrophes a lot worse to read - especially in fonts where ';;' is indistinguishable from ". Such as the default font on the default browser on the machine he uses most.
Could be worse - the default mod wiki has things like seven ' meaning what we have double [ for. --Vitenka
AlexChurchill suggests that a more readable-in-the-edit-box alternative might be /italics/ and *bold*. Unfortunately the latter would clash with both list notation and the common *emote* convention. I think _bold_ would be perverse (people would expect _underline_), although %bold% or $bold$ are possiblities. But I don't think there's enough problem with the apostrophe-strings to be worth changing things.
*bold* wouldn't clash - bulleted lists look for (beginning of line, star(s), space) whereas *bold* would look for (star, nonwhitespace character, any character(s), nonwhitespace character, star). I would probably retain the stars in the output, and just make the entire lot bold. /italics/, however, unless restricted to being used for single words delimited by whitespace, would clash with URLs, subpages, pseudo-HTML tags and probably other things too. -- MoonShadow
I don't see a clash with emotion - make *emote* into emote (instead of bold) and it stays pretty much the same. $ would annoy leet people, so that's a good idea too. --Vitenka
Does anyone find the ' use for bold and italic that annoying? It seems to work for me. Please don't use star for anything, as I would be really annoyed to have to nowiki every action/emotion I wrote out and I don't think italics would work as an equivalent - Kazuhiko
I agree with Kazuhiko, I'm afraid. Seven ' might be irritating but two or three is no problem (as long as I can remember which is which :), and less fuss than <i> or <em>. I'd rather keep * free, since I use them to emote, and the feeling is very different from an italicised word - SunKitten
Summarised above discussion in "no action planned" section of ToothyWikiInternals/WikiFeatures. Will shortly summarise the rest of it in HTML/Discussion or some such, then remove this lot unless someone makes a strong argument for keeping it.
Fair enough, I can certainly agree with the intent - so how about a more intuitive < nowiki > ? --Vitenka (or even just a symbol that becomes square brackets)
Yes, suggestions for non-HTMLized versions of < nowiki > and < pre > are gratefully accepted. Such markup probably needs to contain brackets (something like ((( ... )))?), since it can be multiline and one therefore *really* wants to imply a strong need to remember to close it off. - MoonShadow