<?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>PomocPrzyFormatowaniu</title></articleinfo><section><title>Zasady formatowania tekstu</title><para>Pozostaw puste linie pomiędzy akapitami. Użyj <code>&lt;&lt;BR&gt;&gt;</code> żeby wstawić łamanie linii wewnątrz akapitu. </para><para>You can render text in <emphasis>italics</emphasis> or <emphasis role="strong">bold</emphasis>. To write italics, enclose the text in double single quotes. To write bold, enclose the text in triple single quotes. <emphasis role="underline">Underlined text</emphasis> needs a double underscore on each side. You get <superscript>superscripted text</superscript> by enclosing it into caret characters, and <subscript>subscripts</subscript> have to be embedded into double commas. If you need something <!--"~-smaller-~" is not applicable to DocBook-->smaller or <!--"~+bigger+~" is not applicable to DocBook-->larger you can get that by writing <code>~-smaller-~</code> or <code>~+larger+~</code>. </para><para>Możesz wstawiać tekst <emphasis>pochylony</emphasis> lub <emphasis role="strong">wytłuszczony</emphasis>. Pochylenie uskasz poprzez otoczenie tekstu <code>''podwójnymi apostrofami''</code>. Wytłuszczenie uzyskasz poprzez otoczenie tekstu <code>'''potrójnymi apostrofami'''</code>. <emphasis role="underline">Podkreślony tekst</emphasis> wymaga dwóch znaków podkreślenia po obydwu stronach. Można uzyskać <superscript>indeks górny</superscript>, otaczając go znakami &quot;daszka&quot;: <code>^</code>, natomiast <subscript>indeks dolny</subscript> powinien być otoczony dwoma przecinkami po każdej stronie. Jeżeli potrzebujesz napisać fragment tekstu <!--"~-smaller-~" is not applicable to DocBook-->mniejszą lub <!--"~+bigger+~" is not applicable to DocBook-->większą czcionką, możesz uzykać to pisząc <code>~-mniejsze-~</code> lub <code>~+większe+~</code>. </para><para>Żeby wstawić kod proramu czcionką o <code>stałej szerokości</code> bez przetwarzania formatowania, użyj trzech nawiasów klamrowych: </para><screen><![CDATA[10 PRINT "Witaj świecie!"
20 GOTO 10]]></screen><para>Note that within code sections, both inline and display ones, any wiki markup is ignored. An alternative and shorter syntax for <code>inlined code</code> is to use backtick characters (note that this can be disabled by the site's configuration, but is enabled by default). </para><para>For more information on the possible markup, see <ulink url="http://clip.ipipan.waw.pl/PomocPrzyFormatowaniu/HelpOnEditing#">HelpOnEditing</ulink>. </para><section><title>Example</title><screen><![CDATA[__Mixing__ ''italics'' and '''bold''':
 * '''''Mix''' at the beginning''
 * '''''Mix'' at the beginning'''
 * '''Mix at the ''end'''''
 * ''Mix at the '''end'''''
]]><![CDATA[
You might recall ''a''^2^ `+` ''b''^2^ `=` ''c''^2^ from your math lessons, unless your head is filled with H,,2,,O.
]]><![CDATA[
An { { {inline code sequence} } } has the start and end markers on the same line. Or you use `backticks`.
]]><![CDATA[
A code display has them on different lines: { { {
'''No''' markup here!
} } }]]></screen><para> <inlinemediaobject><imageobject><imagedata depth="15" fileref="http://clip.ipipan.waw.pl/wiki_static/mandarin_clip/img/alert.png" width="15"/></imageobject><textobject><phrase>/!\</phrase></textobject></inlinemediaobject> In the above example, we &quot;escaped&quot; the markers for source code sequences by inserting spaces between the curly braces. </para></section><section><title>Display</title><para><emphasis role="underline">Mixing</emphasis> <emphasis>italics</emphasis> and <emphasis role="strong">bold</emphasis>: </para><itemizedlist><listitem><para><emphasis><emphasis role="strong">Mix</emphasis> at the beginning</emphasis> </para></listitem><listitem><para><emphasis role="strong"><emphasis>Mix</emphasis> at the beginning</emphasis> </para></listitem><listitem><para><emphasis role="strong">Mix at the <emphasis>end</emphasis></emphasis> </para></listitem><listitem><para><emphasis>Mix at the <emphasis role="strong">end</emphasis></emphasis> </para></listitem></itemizedlist><para>You might recall <emphasis>a</emphasis><superscript>2</superscript> <code>+</code> <emphasis>b</emphasis><superscript>2</superscript> <code>=</code> <emphasis>c</emphasis><superscript>2</superscript> from your math lessons, unless your head is filled with H<subscript>2</subscript>O. </para><para>An <code>inline code sequence</code> has the start and end markers on the same line. Or you use <code>backticks</code>. </para><para>A code display has them on different lines: </para><screen><![CDATA['''No''' markup here!]]></screen></section><section><title>Colorized code displays</title><para>There are several ways to get colorized formatting of code<footnote><para>There is currently only support for limited number of languages, see HelpOnParsers.</para></footnote>: </para><orderedlist numeration="arabic"><listitem><para>start a code display with a line only containing &quot;#!PARSERNAME&quot; </para></listitem><listitem><para>embed a file attachment bearing a &quot;.py&quot; extension via &quot;inline:&quot; </para></listitem><listitem><para>start a page with a format processing instruction (&quot;#format PARSERNAME&quot;) </para></listitem></orderedlist><para>Example: </para><programlisting format="linespecific" language="python" linenumbering="numbered" startinglinenumber="1"><token><![CDATA[from]]></token><![CDATA[ ]]><methodname><![CDATA[colors]]></methodname><![CDATA[ ]]><token><![CDATA[import]]></token><![CDATA[ ]]><methodname><![CDATA[palette]]></methodname>
<methodname><![CDATA[palette]]></methodname><![CDATA[.]]><methodname><![CDATA[colorize]]></methodname><![CDATA[(]]><phrase><![CDATA[']]></phrase><phrase><![CDATA[python]]></phrase><phrase><![CDATA[']]></phrase><![CDATA[)]]>
</programlisting></section></section></article>