| Formatting Command: | Example: You write: | You get: | |||||||||||||||||||||||||
|
Paragraphs: Blank lines will create new paragraphs. |
1st paragraph 2nd paragraph | 1st paragraph 2nd paragraph | |||||||||||||||||||||||||
|
Headings: At least three dashes at the beginning of a line, followed by plus signs and the heading text. One plus creates a level 1 heading (most important), two pluses a level 2 heading; the maximum is level 6. Note: A Table of Content can be created automatically with the %TOC% variable, see TWikiVariables. Any heading text after !! is excluded from the TOC; for example, write ---+!! text if you do not want to list a header in the TOC.
|
---++ Sushi ---+++ Maguro |
SushiMaguro |
|||||||||||||||||||||||||
|
Bold Text: Words get bold by enclosing them in * asterisks.
|
*Bold* | Bold | |||||||||||||||||||||||||
|
Italic Text: Words get italic by enclosing them in _ underscores.
|
_Italic_ | Italic | |||||||||||||||||||||||||
|
Bold Italic: Words get _bold italic by enclosing them in _ double-underscores.
|
__Bold italic__ | Bold italic | |||||||||||||||||||||||||
|
Fixed Font: Words get shown in fixed font by enclosing them in = equal signs.
|
=Fixed font= |
Fixed font
|
|||||||||||||||||||||||||
|
Bold Fixed Font: Words get shown in bold fixed font by enclosing them in double equal signs.
|
==Bold fixed== |
Bold fixed
|
|||||||||||||||||||||||||
Note: Make sure there is no space between the text and the bold, italic, or other indicators (* _ __ = ==).
|
_This works_, _this not _ |
This works, _this not _ |
|||||||||||||||||||||||||
|
Verbatim Mode: Surround code excerpts and other formatted text with <verbatim> and </verbatim> tags. Note: Use <pre> and </pre> tags instead if you want the HTML code to be interpreted. Note: Each tag must be on a line by itself. |
<verbatim>
class CatAnimal {
void purr() {
<code here>
}
}
</verbatim>
|
class CatAnimal {
void purr() {
<code here>
}
}
|
|||||||||||||||||||||||||
|
Separator: At least three dashes at the beginning of a line. |
------- |
|
|||||||||||||||||||||||||
|
List Item: Three spaces, an asterisk, and another space. Note: If you don't want to cram long text onto one line, wrap it and align continuation lines with leading spaces. |
* bullet item
* another
bullet
item
* last bullet item
|
|
|||||||||||||||||||||||||
|
Nested List Item: Six, nine, ... spaces, an asterisk, and another space. |
* level 1
* level 2
|
|
|||||||||||||||||||||||||
|
Ordered List: Three spaces, a number, a dot, and another space. Several types are available besides a number:
|
1. Sushi 1. Dim Sum A. Sushi A. Dim Sum i. Sushi i. Dim Sum |
|
|||||||||||||||||||||||||
|
Definition List: Three spaces, a dollar sign, the term, a colon, a space, followed by the definition. Deprecated syntax: Three spaces, the term with no spaces, a colon, a space, followed by the definition. |
$ Sushi: Japan $ Dim Sum: S.F. |
|
|||||||||||||||||||||||||
|
Table: Any number of lines of text. Each line is one row of the table consisting of one or more cells. Each cell starts and ends with a vertical bar '|'. Any spaces at the beginning of a line are ignored. Notes: • | *bold* | cells are displayed as table headers.• | center-spaced | cells are displayed center aligned.• | right-spaced | cells are displayed right aligned.• | 2 colspan || cells are displayed as multi-span columns (i.e., a cell with no text spans a column).• |^| cells with a caret indicate follow-up rows of multi-span rows (this functionality is provided by TablePlugin).• If a row contains a large amount of text, and you want it to be more readable while editing the table, split the row into multiple text lines by ending each line with a backslash character '\'.• Table cells wrap automatically as determined by the browser. |
| *L* | *C* | *R* | | A2 | 2 | 2 | | A3 | 3 | 3 | | multi span ||| | A4-6 | four | four | |^| five | five | |^| six | six | |
|
|||||||||||||||||||||||||
|
WikiWord Links: CapitalizedWordsStuckTogether (or WikiWords) will produce a link automatically if preceded by whitespace or parenthesis. Note: In case you want to link to a topic in a different TWiki web write Otherweb.TopicName. (The link label is the the name of the web in case the is WebHome, else it is the topic name)
|
WebNotify Main.TWikiUsers | WebNotify TWikiUsers | |||||||||||||||||||||||||
|
Forced Links: You can create a forced internal link by enclosing words in double square brackets. Note: Text within the brackets may contain optional spaces; the topic name is formed by capitalizing the initial letter and by removing the spaces; for example, [[text formatting FAQ]] links to topic TextFormattingFAQ. You can also refer to a different web and use anchors.
Note: To "escape" double square brackets that would otherwise be a correct link, prefix the leading left square brackets with an exclamation point, that is, begin with ![[....
|
[[wiki syntax]] [[Main.TWiki users]] escaped: ![[wiki syntax]] | wiki syntax Main.TWiki users escaped: [[wiki syntax]] | |||||||||||||||||||||||||
|
Specific Links: Create a link where you can specify the link text and the link reference separately, using nested square brackets like [[reference][text]]. Internal link references (e.g. WikiSyntax) and external link references (e.g. http://TWiki.org/) are supported.
Note: The same Forced Links rules apply for internal link references. Note: For external link references, you can simply use a space instead of ][ to separate the link URL from the descriptive text.
Note: Anchor names can be added as well, like [[WebHome#MyAnchor][go home]] and [[http://gnu.org/#Action][GNU Action]].
|
[[WikiSyntax][syntax]] [[http://gnu.org][GNU]] [[http://xml.org XML]] | syntax GNU XML | |||||||||||||||||||||||||
|
Anchors: You can define a link reference inside a TWiki topic (called an anchor name) and link to that. To define an anchor write #AnchorName at the beginning of a line. The anchor name must be a WikiWord of no more than 32 characters. To link to an anchor name use the [[MyTopic#MyAnchor]] syntax. You can omit the topic name if you want to link within the same topic.
|
[[WikiWord#NotThere]] [[#MyAnchor][Jump]] #MyAnchor To here | WikiWord#NotThere Jump To here | |||||||||||||||||||||||||
|
Prevent a Link: Prevent a WikiWord from being linked by prepending it with an exclamation point. |
!SunOS | SunOS | |||||||||||||||||||||||||
|
Disable Links: You can disable automatic linking of WikiWords by surrounding text with <noautolink> and </noautolink> tags.
Note: Each tag must be on a line by itself. Note: This also works for TWiki tables, but only if you add a blank line between the end of the table and the closing </noautolink> tag (known issue of the TablePlugin).
|
<noautolink> RedHat & SuSE </noautolink> | RedHat & SuSE | |||||||||||||||||||||||||
|
Mailto: Links: To create 'mailto:' links that have more descriptive link text, specify subject lines or message bodies, or omit the email address, you can write [[mailto:user@domain descriptive text]].
|
[[mailto:a@z.com Mail]] [[mailto:?subject=Hi Hi]] | Mail Hi | |||||||||||||||||||||||||
<strike>deleted text</strike> to get <p /> paragraph tags on empty lines, which causes problems if done between tags that do not allow paragraph tags, like for example between table tags.
<...> - of an HTML tag must be on the same line, or the tag will be broken. <, ex: a < b
<pre> tags:
<script type="text/javascript"> <!-- Hide JavaScript and <pre> escape TWiki rendering ... put your JavaScript code here... // Stop hiding and stop </pre> escaping TWiki rendering --> </script>
http://..., https://..., ftp://..., gopher://..., news://..., file://..., telnet://... and mailto:...@... are linked automatically.
name@domain.com are linked automatically.
[[Square bracket rules]] let you easily create non-WikiWord links. [[http://yahoo.com Yahoo home page]] as an easier way of doing external links with descriptive text for the link, such as Yahoo home page.
% that are expanded on the fly.
%TOC% : Automatically generates a table of contents based on headings in a topic - see the top of this page for an example.
%WEB% : The current web, is TWiki.
%TOPIC% : The current topic name, is TextFormattingRules.
%ATTACHURL% : The attachment URL of the current topic. Example usage: If you attach a file to a topic you can refer to it as %ATTACHURL%/image.gif to show the URL of the file or the image in your text.
%INCLUDE{"SomeTopic"}% : Server side include, includes another topic. The current TWiki web is the default web. Example: %INCLUDE{"TWiki04x03.SiteMap"}%
%SEARCH{"sushi"}% : Inline search showing the search result embedded in a topic. FormattedSearch gives you control over formatting, used to create web-based applications.
%BR% to start a new line.
%RED% Red %ENDCOLOR% and %BLUE% blue %ENDCOLOR% colors to get: Red and blue colors.
%H% Help, %T% Tip, %X% Alert to get: !%SOMEVARIABLE% to get: %SOMEVARIABLE%.
%PLUGINDESCRIPTIONS%:
"$SUM( $ABOVE() )" to TWiki tables and other topic text %GAUGE{}% variables. ExternalSite:Page text to external sites based on aliases defined in a rules topic
for :-) or
for :eek: <filename> is not displayed. How can I show it as it is? '<' and '>' characters have a special meaning in HTML, they define HTML tags. You need to escape them, so write '<' instead of '<', and '>' instead of '>'. 'prog <filename>' to get 'prog <filename>'.
'&' character sometimes not displayed? '&' character has a special meaning in HTML, it starts a so called character entity, i.e. '©' is the © copyright character. You need to escape '&' to see it as it is, so write '&' instead of '&'. 'This & that' to get 'This & that'.
edit*.tmpl templates' launchWindow routine, or perhaps use a smaller font. We should target 800x600 screens since those are still quite common according to browser stats sites, so IMO the smaller font is the way to go, although perhaps parameterisable sizes for the pop-up windows would also be a good idea (see CVS:templates/edit.iejs.tmpl for an example of parameterising JavaScript using TWikiVariables.)
Perhaps if we put a common %STYLESHEET% variable in all templates that includes an optional CSS reference, which can then include a suitable font setup?
I have also temporarily removed the %TOC%, because (1) it was generating a '*' after the TOC, due to a bug, and (2) it takes up a lot of space and doesn't seem that useful since most of the content of the page is in a table. Without a TOC, the pop-up window shows the top part of the table, which is the most useful part IMO. However, others may disagree
-- RichardDonkin - 05 Apr 2002
I'd de-TOC TWikiShorthand instead! It's pretty similar to this page, but I was gonna edit it down for the simple user's guide version. And you don't want all that in a popup window. Makes even more sense with NewContents even sharper divisions of doc type/detail, if that goes anywhere!
-- Main.MikeMannix - 04 May 2002
Just knew from support that there is a tag for preventing a link for sections of text -rather than a single WikiWord- and it is not documented above: You must surround the text with <noautolink> ... </noautolink> tags. Hope this to be of some help.
-- AntonioVega - 12 Apr 2002
Hi, Antonio: I looked around. <noautolink> is over a year old, and was briefly documented, then undocumented because people didn't like - found confusing and inconsistent - the HTML style of the tag. . <verbatim> snuck in there, and <nop> is HTML-like - I can see how these would confuse. Then again, what good's an undocumented feature (if it's useful)? Thanks for the tip - I won't add it now, but will ask. If you think it should be docced - or the brackets changed - weigh in on the See DisableWikiWordLinks... page where the discussion still goes on.
RedHat and SuSE are GNU-Linux distributors.
Useful, but the tags are too long...
-- Main.MikeMannix - 04 May 2002
Has anyone else noticed that the TWiki Editing Shorthand table has these unbalanced HTML end tags at the end of the table?
</td></tr> </table>I removed them....they tend to mess up table-based skins. -- GladeDiviney - 04 May 2002 I tweaked the text so that the table is more narrow. This is needed because the popup window when getting text formatting help is small. -- PeterThoeny - 01 Feb 2003 According to TelnetURLSupport, "(http|ftp|gopher|news|file|https|telnet)" are all supported. So I've added them to the External Links section. -- JohnRouillard - 01 Feb 2003 The
noautolink tags can't be used inline, but must be on a line by themself. I think noautolink should always work, inline and otherwise.
I also think it is rather unwiki-like to use html-style code for this, but can't think of a suitable alternative right now.
-- MattWilkie - 06 Feb 2003
I've been unable to find any notes on what the ---# style of heading is for (I saw it in one of the standard TWiki pages) and was expecting to find some notes on here. Is it any different to ---+ ?
-- GrahamAshton - 25 Jun 2003 ---# is the same as ---+ but we need confirmation from gurus. Be patient
-- PeterMasiar - 10 Jul 2003
---# is reserved for auto-numbered headings.
<, ex: a > b
I've changed it display the proper less than entity.
-- BasilJamesWhitehouseIII - 10 Jul 2003
There seems be something wrong in linking to local files. Various typo are rendered corretly in the source page, ex. a href="file://C:/... or a href="file:///C|/..., but clicking the link has no effect. It is in Win 2k Prof. Apache, Cygwin, Perl.
-- AndrzejGoralczyk - 11 Jan 2004
Mozilla file:// links are disabled by the browser. The gory details are at MozillaBug:84128. Scroll down to comment #20 for a workaround (and the http://preferential.mozdev.org/ extension for an easier way to implement it).
If you are not using Mozilla, something else is happening and you should go to Support (ie: file:// links should work fine).
-- MattWilkie - 13 Jan 2004
Thank You, Matt. Now Mozilla works.
-- AndrzejGoralczyk - 01 Feb 2004
I found myself in the awkward situation that I wanted to use JavaScript to embed a form with some dynamic properties on a wiki page. While I would be the first one to condemn this practice :-) it would be nice if there was a way to say "this is magical, don't touch". What I need to happen is for stuff like "if (number > 1000)" to get through to the JavaScript interpreter correctly, i.e. the larger-than sign should not be converted to an entity. (Of course I had to use > here to make it through.)
-- EraEriksson - 03 Mar 2004
I removed the reference to "You need TablePlugin for multi-span rows to work." since this Plugin is preinstalled in the latest Beta.
-- PeterThoeny - 17 Mar 2004
It might be wise to leave in something like "(multi-span rows provided by TablePlugin)" just in case it is uninstalled. It could also help someone visiting this site who is running an earlier version.
-- SamHasler - 22 Mar 2004
Era: I added doc on how to escape JavaScript.
Sam: Good suggestion, done.
-- PeterThoeny - 30 Mar 2004
Explained continuation lines in lists. Please check my suggested wording.
-- DanielKabs - 23 Aug 2005
Thanks Daniel, it's descriptive.
-- PeterThoeny - 24 Aug 2005
I would like to know if there is any format code that would make any given text look like it has been crossed over (I want to show for everybody to see in a explicit way what was corrected or erased in the last revision of a page)
-- JaimeCaamanoRuiz - 25 Aug 2005
You can use HTML for that, see updated docs above (under "Using HTML" section)
-- PeterThoeny - 25 Aug 2005
It was right there and I didn't see it. Sorry and thanks!
-- JaimeCaamanoRuiz - 25 Aug 2005
You didn't see it because I just added it
-- PeterThoeny - 25 Aug 2005
Moved question about attaching files to HowDoIAttachFiles. This area is for commenting on TextFormattingRules documentation.
-- LynnwoodBrown - 13 Oct 2005
This topic is important. It should be promoted to WebHome
-- ZhengShao - 23 Jan 2006
Just noticed it's already on WebHome
-- ZhengShao - 23 Jan 2006
I couldn't find an existing topic for the html methods of displaying special characters. Since I had to create one for my own TWiki installation, I'm sharing the love.
Check out SpecialCharacters which has a very long list of multiple methods of displaying special symbols and characters.
-- AmandaSmith - 20 Feb 2006
I want to put a <verbatim> code snippet in a table cell, but the presence of the <verbatim> tag seems to invalidate all table-related formatting in the line where it appears. Is it possible to do have a formatted snippet in a cell?
-- NickPollitt - 10 Mar 2006
Use either HTML (<table>) or try the RecursiveRenderPlugin.
-- FranzJosefSilli - 11 Mar 2006
Is there any way to collapse and expand the different %TOC% levels so that you can view just the main general headings and then drill down into each for greater detail? (i.e. Click on a heading in the TOC and have it expand to show and sub headings. Then click on any sub headings to show further sub-sub-headings, etc)
-- PatSchmidt - 30 Mar 2006
TWiki does not have collabsable TOC entries. That is a good candidate for a Plugin. (Please ask support questions in the Support web.)
-- PeterThoeny - 30 Mar 2006
Oops...sorry about that!
-- PatSchmidt - 31 Mar 2006
When making tables--using
|
||||||||||
!%INCLUDE{ "heading name" section="content" }%
-- CarlMcKinney - 22 Aug 2006
Please ask support questions in the Support web. You can use the ! escape character only if preceeded by whitespace. An alternative escape is <nop>, e.g. %<nop>INCLUDE{ ... }%
-- PeterThoeny - 23 Aug 2006
I'd recommend updating the comment on Anchors:
from The anchor name must be a WikiWord.
to The anchor name must be a WikiWord of no more than 32 characters.
Thanks,
-- GregoryWalden - 17 Jan 2007
Fixed. This is a wiki, by all means please feel free to update the documentation directly!
-- PeterThoeny - 18 Jan 2007
Can anyone explain what differences and similarities exists within TWiki and MediaWiki formatting rules? - Nashev
-- IlyaNenashev - 29 Mar 2007
See MediaWiki, MediaWikiSyntaxPlugin, EditSyntaxPlugin, MediaWikiTablePlugin. And please ask support questions in the Support web.
-- PeterThoeny - 29 Mar 2007
Is the feature of the "automatic anchor" to a heading considered an undocumented feature (and thus, subject to change)?
(The feature to which I'm referring is that there is automatically an anchor to every heading in a document, initially or primarily used for the TOC feature, but also usable by anyone who is aware of the feature to create a link to that heading. Further, that anchor is constructed by taking the text of the heading and: #CommonEditingErrors ---++ Common Editing Errors-- PeterThoeny - 18 Mar 2008 Peter, Thanks! Is it worth documenting the undocumented feature? I mean, something like the following; or, if not in the official documentation, maybe by just leaving the note here? There is an undocumented feature which automatically creates an anchor for every heading in a document to support the TOC (Table of Content) feature. This is intentionally undocumented because the details may change and you should not rely on it. Instead, create your own anchor:
#CommonEditingErrors ---++ Common Editing Errors-- RandyKramer - 18 Mar 2008 The code for anchors on my twiki causes the link to affix two '.pl's to the view script in the hyperlink. ie. all anchors break because there is a "view.pl.pl" call in the link. is there a way I can manually change this or is there a likely point of error in my configuration? -- StevenMoncada - 05 Sep 2008 I have the same problem (.pl.pl) with TWiki-4.2.3, Wed, 06 Aug 2008, build 17396, Plugin API-Vversion 1.2. Please help. -- BernhardGonitianer - 05 Oct 2008 It appears that unusual link protocols are not supported. For example, we use an application that has URLs like "doors://froggy:36677/?version=1,prodID=0,dbid=3b0430a148c5136f,container=00003484". We'd like to create an ordinary hyperlink for such URLs, but TWiki currently rejects the possibility that "doors://" could be a protocol. -- ByronHawkins - 06 Jan 2009 You can add uncommon protocols to the
{linkProtocolPattern} setting in configure.
Alternatively, add a new rule to your InterwikiPlugin.
-- PeterThoeny - 06 Jan 2009