By using syntax rule like the one below, you can format a block in a different way from Wiki.
{{{ processor_name parameter1 parameter2 pass block content }}}
If you omit the processor name, it will be automatically discriminated by this processor. That said, currently there are only two types.
If the block begins with #!, which is a shebang, it is passed to code, and everything else is passed to pre.
Intentionally, if you don't want to pass to this processor (although that is unlikely to happen), all you have to write is auto.
You can output pre format text.
{{{ pre what you have written will be outputted the way you have written. < > and the likes will be HTML escaped. }}}
what you have written will be outputted the way you have written. < > and the likes will be HTML escaped.
{{{ comment comment block. It will only be shown on the edit display. You can use this, for example, when you want to draw attention while editing. }}}
Highlights the source code.
Currently, you can use the language name of the enscript as it is. (The supported languages are: ada, asm, awk, bash, c, changelog, cpp, csh, delphi, diff, diffs, diffu, dylan, eiffel, elisp, erlang, forth, fortran, fortran_pp, haskell, html, icon, idl, inf, java, javascript, ksh, lua, m4, mail, makefile, matlab, nroff, oberon2, objc, outline, oz, pascal, perl, postscript, pyrex, python, rfc, ruby, scheme, sh, skill, Smalltalk, sml, sql, states, synopsys, tcl, tcsh, tex, vba, verilog, vhdl, vrml, wmlscript, zsh )
{{{ code ruby def initialize @compiler = ERuby::Compiler.new end def check_request(r) if r.method_number == M_OPTIONS r.allowed |= (1 << M_GET) r.allowed |= (1 << M_POST) return DECLINED end end }}}
Try to use this block processor as less as possible.
You can freely write HTML to a certain extent. You can use this when you need to create things that general wiki format isn't capable of expressing, like creating complicated tables.
Script and style factors and properties that are related to events, such as onClick, are filtered and will not be outputted. Also, they will be outputted even without the tag correspondence, so you have to be extra careful not to destroy the expression.
Example:
{{{ html <span style="color: #000081; background: #D0FFE8; border: 1px solid #4B78EE;"> Now you can use style properties. </span> <font color="#810000">You can of course use font factors as well.</font> <table width="50%" border="1"> <tr><th colspan="2">I want to use Colspan</th></tr> <tr> <td aling="center" width="50%">Table like this</td> <td align="right" bgcolor="yellow">Could only be....by HTML</td> </tr> </table> }}}
Expressed as:
Now you can use style properties. You can of course use font factors as well.I want to use Colspan | |
---|---|
Table like this | Could only be....by HTML |
Expressed as a writable template, it will add postscripts by embedding contents that are written by users. Just like LineComment, anyone, without minding about authority setting, can write in the enter box.
/%[0-9]*(x[0-9]+)?[imcutdz]/ is the format string text. Each letter has a meaning.
Example:
{{{ template ||name|| %u (%d %t %z)|| ||title|| %60i|| ||details|| %60x3m|| || || || }}}
What is within the block will be formatted as Markdown.
Example:
{{{ markdown #### Hello Markdown! What is within _the block_ will be interpreted as [Markdown syntax](https://daringfireball.net/projects/markdown/syntax). }}}
Expressed as:
What is within the block will be interpreted as Markdown syntax.
[ページ情報]
更新日時: 2021-03-03 06:59:05, 更新者: sado
[ライセンス]
GNU Free Documentation License
[権限]
表示:無制限, 編集:メンバー, 削除/設定:メンバー