Maintenance script: Created page with " == Wiki Processors == Processors are WikiMacros designed to provide alternative markup formats for the [TracWiki Wiki engine]. Processors can be thought of as ''macro functi..."

2015-08-26T12:29:30Z

Created page with " == Wiki Processors == Processors are WikiMacros designed to provide alternative markup formats for the [TracWiki Wiki engine]. Processors can be thought of as ''macro functi..."

New page

== Wiki Processors ==

Processors are WikiMacros designed to provide alternative markup formats for the [TracWiki Wiki engine]. Processors can be thought of as ''macro functions to process user-edited text''.

Wiki processors can be used in any Wiki text throughout Trac,
for various different purposes, like:
- [#CodeHighlightingSupport syntax highlighting] or for rendering text verbatim,
- rendering [#HTMLrelated Wiki markup inside a context],
like inside <div> blocks or <span> or within <td> or <th> table cells,
- using an alternative markup syntax, like [[WikiHtml| raw HTML]] and
[[WikiRestructuredText| Restructured Text]],
or [http://www.textism.com/tools/textile/ textile]

=== Using Processors ===

To use a processor on a block of text, first delimit the lines using
a Wiki ''code block'':
<pre>
<pre>
The lines
that should be processed...
</pre>
</pre>

Immediately after the <tt><pre></tt> or on the line just below,
add <tt>#!</tt> followed by the ''processor name''.

<pre>
<pre>
#processorname
The lines
that should be processed...
</pre>
</pre>

This is the "shebang" notation, familiar to most UNIX users.

Besides their content, some Wiki processors can also accept ''parameters'',
which are then given as <tt>key=value</tt> pairs after the processor name,
on the same line. If <tt>value</tt> has to contain space, as it's often the case for
the style parameter, a quoted string can be used (<tt>key="value with space"</tt>).

As some processors are meant to process Wiki markup, it's quite possible to
''nest'' processor blocks.
You may want to indent the content of nested blocks for increased clarity,
this extra indentation will be ignored when processing the content.

=== Examples ===

{| border=1 class="simple"
!= Wiki Markup =
!= Display =
|}

<pre>#td colspan=2 align=center style="border: none"

<u>Example 1</u>: Inserting raw HTML
</pre>
|-----------------------------------------------------------------
<pre>#td style="border: none"
<pre>
<pre>
<h1 style="color: grey">This is raw HTML</h1>
</pre>
</pre>
</pre>
<pre>#td valign=top style="border: none; padding-left: 2em"
<pre>
#html
<h1 style="color: grey">This is raw HTML</h1>
</pre>
</pre>
|-----------------------------------------------------------------
<pre>#td colspan=2 align=center style="border: none"

<u>Example 2</u>: Highlighted Python code in a <div> block with custom style
</pre>
|-----------------------------------------------------------------
<pre>#td style="border: none"
<pre>
<pre>#div style="background: #ffd; border: 3px ridge"

This is an example of embedded "code" block:

<pre>
#python
def hello():
return "world"
</pre>

</pre>
</pre>
</pre>
<pre>#td valign=top style="border: none; padding: 1em"
<pre>#div style="background: #ffd; border: 3px ridge"

This is an example of embedded "code" block:

<pre>
#python
def hello():
return "world"
</pre>

</pre>
</pre>
|-----------------------------------------------------------------
<pre>#td colspan=2 align=center style="border: none"

<u>Example 3</u>: Searching tickets from a wiki page, by keywords.
</pre>
|-----------------------------------------------------------------
<pre>#td style="border: none"
<pre>
<pre>
#html
<form action="/query" method="get">
<input type="text" name="keywords" value="~" size="30">
<input type="submit" value="Search by Keywords">

</form>
</pre>
</pre>
</pre>
<pre>#td valign=top style="border: none; padding: 1em"
<pre>
#html
<form action="/query" method="get">
<input type="text" name="keywords" value="~" size="30">
<input type="submit" value="Search by Keywords">

</form>
</pre>
</pre>
=== Available Processors ===

The following processors are included in the Trac distribution:

<tt>#default</tt> :: Present the text verbatim in a preformatted text block.
This is the same as specifying ''no'' processor name
(and no <tt>#!</tt>)
<tt>#comment</tt> :: Do not process the text in this section (i.e. contents exist
only in the plain text - not in the rendered page).

==== HTML related ====

<tt>#html</tt> :: Insert custom HTML in a wiki page.
<tt>#htmlcomment</tt> :: Insert an HTML comment in a wiki page (''since 0.12'').

Note that <tt>#html</tt> blocks have to be ''self-contained'',
#e. you can't start an HTML element in one block and close it later in a second block. Use the following processors for achieving a similar effect.

<tt>#div</tt> :: Wrap an arbitrary Wiki content inside a <div> element
(''since 0.11'').
<tt>#span</tt> :: Wrap an arbitrary Wiki content inside a <span> element
(''since 0.11'').

<tt>#td</tt> :: Wrap an arbitrary Wiki content inside a <td> element (''since 0.12'')
<tt>#th</tt> :: Wrap an arbitrary Wiki content inside a <th> element (''since 0.12'')
<tt>#tr</tt> :: Can optionally be used for wrapping <tt>#td</tt> and <tt>#th</tt> blocks,
either for specifying row attributes of better visual grouping
(''since 0.12'')

See WikiHtml for example usage and more details about these processors.

==== Other Markups ====

<tt>#rst</tt> :: Trac support for Restructured Text. See WikiRestructuredText.
<tt>#textile</tt> :: Supported if [http://cheeseshop.python.org/pypi/textile Textile]
is installed.
See [http://www.textism.com/tools/textile/ a Textile reference].

==== Code Highlighting Support ====

Trac includes processors to provide inline syntax highlighting:
<tt>#c</tt> (C), <tt>#cpp</tt> (C++), <tt>#python</tt> (Python), <tt>#perl</tt> (Perl),
<tt>#ruby</tt> (Ruby), <tt>#php</tt> (PHP), <tt>#asp</tt> (ASP), <tt>#java</tt> (Java),
<tt>#js</tt> (Javascript), <tt>#sql (SQL)</tt>, <tt>#xml</tt> (XML or HTML),
<tt>#sh</tt> (Bourne/Bash shell), etc.

Trac relies on external software packages for syntax coloring,
like [http://pygments.org Pygments].

See TracSyntaxColoring for information about which languages
are supported and how to enable support for more languages.

Note also that by using the MIME type as processor, it is possible to syntax-highlight the same languages that are supported when browsing source code. For example, you can write:
<pre>
<pre>
#text/html
<h1>text</h1>
</pre>
</pre>

The result will be syntax highlighted HTML code:
<pre>
#text/html
<h1>text</h1>
</pre>

The same is valid for all other [TracSyntaxColoring#SyntaxColoringSupport mime types supported].

For more processor macros developed and/or contributed by users, visit:
*[trac:ProcessorBazaar]
*[trac:MacroBazaar]
*[th:WikiStart Trac Hacks] community site

Developing processors is no different from Wiki macros.
In fact they work the same way, only the usage syntax differs.
See WikiMacros#DevelopingCustomMacros for more information.

----
See also: WikiMacros, WikiHtml, WikiRestructuredText, TracSyntaxColoring, WikiFormatting, TracGuide

{{TracNotice|{{PAGENAME}}}}

WikiProcessors - Revision history

Maintenance script: Created page with " == Wiki Processors == Processors are WikiMacros designed to provide alternative markup formats for the [TracWiki Wiki engine]. Processors can be thought of as ''macro functi..."