<?xml version="1.0" encoding="utf-8"?><!DOCTYPE article  PUBLIC '-//OASIS//DTD DocBook XML V4.4//EN'  'http://www.docbook.org/xml/4.4/docbookx.dtd'><article><articleinfo><title>HelpOnProcessingInstructions</title></articleinfo><para><ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/HelpForUsers#">HelpForUsers</ulink> &gt; <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/HelpOnEditing#">HelpOnEditing</ulink> &gt; HelpOnProcessingInstructions </para><para><ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/MoinMoin#">MoinMoin</ulink> processing instructions have the same semantics as in XML: they control the paths taken when processing a page. Processing Instructions (PIs) are lines that start with a &quot;<code>#</code>&quot; character followed by a keyword and optionally some arguments; the keyword is always handled case-insensitive. Two consecutive hash marks at the start of a line are a comment that won't appear in the processed page. </para><para>All PIs must appear at the very start of a page. An exception are comment PIs, those may appear anywhere within a  page using &quot;wiki&quot; format, but not in pages using other formats. </para><para>For more information on the possible markup, see <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/HelpOnEditing#">HelpOnEditing</ulink>.  </para><para>Processing instructions MoinMoin knows of: <!--The macro TableOfContents doesn't work with the DocBook formatter.--> </para><section><title>## comment</title><screen><![CDATA[## a comment, any text here is ignored]]></screen><para><anchor id="format"/> </para></section><section><title>#format</title><para>Defines the input format for this page.  </para><screen><![CDATA[#FORMAT format-specifier optional-arguments]]></screen><para>format-specifier can be: </para><itemizedlist><listitem><para><emphasis role="strong">wiki</emphasis>: default <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/MoinMoin#">MoinMoin</ulink> wiki markup (see <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/HelpOnMoinWikiSyntax#">HelpOnMoinWikiSyntax</ulink>) </para></listitem><listitem><para><emphasis role="strong">creole</emphasis>: alternative wiki syntax (see <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/HelpOnCreoleSyntax#">HelpOnCreoleSyntax</ulink>) </para></listitem><listitem><para><emphasis role="strong">plain</emphasis>: normal plain text </para></listitem><listitem><para><emphasis role="strong">python</emphasis>: colored Python code </para></listitem><listitem><para><emphasis role="strong">rst</emphasis>: reStructuredText markup (see <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/HelpOnParsers/ReStructuredText#">HelpOnParsers/ReStructuredText</ulink>) </para></listitem><listitem><para>Any other installed parser name. See <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/HelpOnParsers#">HelpOnParsers</ulink> for additional parsers available and <ulink url="http://moinmo.in/ParserMarket#">ParserMarket</ulink> for user provided parsers. </para></listitem></itemizedlist><para>Some parsers can accept optional arguments. Check the documentation of the parser for the possible options. </para></section><section><title>#redirect</title><para>Redirect to a different page (see <ulink url="http://www.usemod.com/cgi-bin/mb.pl?PageRedirect#">PageRedirect</ulink><emphasis role="strong"/>) </para><screen><![CDATA[#REDIRECT pagename]]></screen></section><section><title>#refresh</title><para>Redirect to a different page (or an external URL or just refresh the same page, if left out) </para><itemizedlist><listitem><para>Needs to be enabled in the server configuration, see <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/HelpOnConfiguration#">HelpOnConfiguration</ulink> </para></listitem></itemizedlist><screen><![CDATA[#REFRESH delay target]]></screen><para>target can be either a page name, or a fully qualified url. Here are two examples: </para><screen><![CDATA[#refresh 0 FrontPage
#refresh 5 http://example.com/]]></screen></section><section><title>#pragma</title><para>Sets processing modes for this page: </para><screen><![CDATA[#PRAGMA mode arguments]]></screen><para>Mode names are not case-sensitive.  </para><para>MoinMoin knows few pragmas, and you may add more and use them for your own themes or macros. Here are the known pragmas: </para><section><title>section-numbers</title><para>Switches automatic numbering of section headers. </para><screen><![CDATA[#pragma section-numbers off]]></screen><para><code>off</code> or <code>0</code> disable numbering, <code>on</code> or <code>1</code> enables numbering. The default mode is set by the <code>show_section_numbers</code> config option. </para><para>When enabling numbering, its possible to use specific heading level: </para><screen><![CDATA[#pragma section-numbers 2]]></screen><para>Only displays section numbers for headings of level 2 and up (similarly for 3 to 6). </para></section><section><title>keywords</title><para>adds a <code>&lt;meta&gt;</code> tag with keywords which tells search engines what you can find on the particular page. </para><screen><![CDATA[#pragma keywords Cars, Vehicles, Foo]]></screen></section><section><title>description</title><para>adds a <code>&lt;meta&gt;</code> tag which contains the description of the particular page. </para><screen><![CDATA[#pragma description This page is about cars.]]></screen></section><section><title>supplementation</title><para>is used to enable or disable a supplementation for the current page e.g. a discussion page </para><screen><![CDATA[#pragma supplementation-page on]]></screen><para><code>off</code> disables the supplementation for the current page. See also <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/HelpOnConfiguration/SupplementationPage#">HelpOnConfiguration/SupplementationPage</ulink> for more. </para></section></section><section><title>#deprecated</title><para>Mark this page as deprecated. </para><screen><![CDATA[#DEPRECATED]]></screen><para>Further changes to the page will create no backup versions and using it will cause the current revision to show along with the revision previous to the deprecation. This allows you to remove all of the page's content, insert #deprecated, and then write a short message explaining the reason behind this action. By doing this you are effectively freezing the last version of the page and reducing its rank in search results, but you are keeping the content available for viewing. </para><itemizedlist><listitem><para>Removing the PI from the page will store <emphasis role="strong">no</emphasis> backup of the deprecation warning. </para></listitem><listitem><para>In comparison to <code>#REDIRECT</code> this PI gives the ability to give the user a reason why this page is no longer of use and why they should go to a new one, while <code>#REDIRECT</code> will throw them to the new page without any reason. </para></listitem><listitem><para>Not removing the page's content when adding #deprecated will cause the page to render twice. </para></listitem></itemizedlist></section><section><title>#language</title><para>Set page language and direction. </para><screen><![CDATA[#language language-name]]></screen><para>Set page language and direction. Language name is the iso-639-1 code. <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/MoinMoin#">MoinMoin</ulink> ignore languages that does not have a translation file in <code>MoinMoin/i18n/</code>. See also <ulink url="https://wiki.helsinki.at/HelpOnProcessingInstructions/HelpOnLanguages#">HelpOnLanguages</ulink>. </para></section></article>