This page is intended for verifying that upgrades of DokuWiki did not break our existing plugins and customizations. Every change that matters should be sampled on this page.

Remember that you have to edit this page in order to force a cache refresh.

just use the amazon tag providing an ASIN as shown below

{{amazon>0596529686}}

Karim Yaghmour, Jon Ma…

Building Embedded Linu…

ISBN 0596529686

Indeed, the purpose of an encyclopedia is to collect knowledge disseminated around the globe; to set forth its general system to the men with whom we live, and transmit it to those who will come after us, so that the work of preceding centuries will not become useless to the centuries to come; and so that our offspring, becoming better instructed, will at the same time become more virtuous and happy, and that we should not die without having rendered a service to the human race.

Denis DiderotEncyclopédie, Vol. 5 (1755), pp. 635–648A

Definitions.

You can apply normal wiki syntax to the definition list.

Pizza

Food

Delicious

Mausi

Curry

Korma

kasmiri

fruity

ceylonese

coconutty

Bhoona

If you want to make additional information available that is folded or hidden by default, you have two options

This is example text with some of it only shown when you unfold it. And after that the text just continues to flow in the same paragraph.

This is example text.

Title

This can create directed and non-directed graph images from a textual description language called “dot” using the Graphviz program. graphviz.

Allows you to include different wiki pages in the current page. Simply enclose the ID of the page to be included in double curly brackets:

{{page>[id]#[section]&[flags]}}

Example:

  
{{page>:start&firstseconly&footer}}

provides the first section of the start page

analog devices
blackfin.uclinux.org
digikey
O'Reilly
docs.blackfin.uclinux.org

There are some special internal links which have icons associated with them:

• Software/Tools
• Linux drivers

<m size>...mathematical formulae...</m>

size (optional) the base glyph size in pixels - default value: 12.

alignment can be controlled in the same way as DokuWiki images, one space to the left to right align, one to the right to left align, one on each side to centre.

syntax can be found in the math page.

Notes have changed recently -- please use the new format. With the new format, comes new options! You can control the corners (square [default] or round), if it has an icon or not, and the width. See the examples below.

<WRAP info>
text which you want in the box
</WRAP>

<WRAP tip>text which you want in the box</WRAP>

<WRAP important>text which you want in the box</WRAP>

<WRAP alert>text which you want in the box</WRAP>

<WRAP round help>text which you want in the box</WRAP>

<WRAP round 50% download>
  * list of files to download
</WRAP>

<WRAP todo>
  * list of things todo, or that are in progress
</WRAP>

Safety Notes:

<WRAP danger>
//**DANGER**// - normal text is white.
</WRAP>

<WRAP warning>
//**warning**// - normal text is black.
</WRAP>

<WRAP caution>
//**caution**// - normal text is black.
</WRAP>

<WRAP round notice>
//**notice**// - normal text is white
</WRAP>

<WRAP round safety>
//**safety**// - normal text is white
/WRAP>

You can use notes and boxes also inside text with paragraphs like this (the key thing to notice is the case of the WRAP or wrap keyword): <wrap info>info</wrap>, text between help, text between alert, text between important, text between tip, text between download, text betweentodo and round box and danger, warning, caution, notice, safety.

<wrap info>info</wrap>, <wrap help>help</wrap>, ...

shows a number of stars to represent the level of skill needed to understand and use the page content. plugin:skill

You should see 5 out of 7 stars here:

7

source is used to grap source code from the svn or git repositories. Since you may want to grab different parts of the file, it accepts lots of different options, but the main flavour is:

<source path:part language repository>

where part can be, numeric, two regular expressions (no spaces - it's a bug I haven't cared about - complain if it is a big deal to you), or function names.

 /1-3/         : captures from lines 1 to 3
 /foo/-/bar/   : captures from the first occurrence of "foo",
                  to the next occurrence of "bar"
 /foo/2-/bar/  : captures from the 2nd occurrence of "foo,
                  to the next occurrence of "bar"
 /foo/12-3/^$/ : captures from the 12th occurrence of "foo",
                  to the 3rd next blanks line
 /foo/-EOF     : captures from the first occurrence of "foo",
                  to the end of file
 foo{}         : functions
 foo[]         : arrays
 foo()         : scopes

If your regular expressions are a little rusty - check out a short reference

path can also have globs in it - it help pick the latest version in a branch. for example, this uses latest busybox version in trunk (sometimes there is more than one)

<source master/cf_lib/edk/pcores/axi_adc_2c_v1_00_a/regmap.txt:/REGISTER/-/0x02/ txt fpgahdl_xilinx> 

/* line 38 to 47 */
// REGISTER MAP
// ***************************************************************************
// ***************************************************************************
// ---------------------------------------------------------------------------
// Address
// QW     Byte   Bits     Description
// ---------------------------------------------------------------------------
// 0x00   0x00   [31: 0]  version[31:0]         32'h00010063  (1.0a)
// ---------------------------------------------------------------------------

For example:

<source trunk/README:0-5 text linux-kernel>

        Linux kernel release 3.x <http://kernel.org/>
 
These are the release notes for Linux version 3.  Read them carefully,
as they tell you what this is all about, explain how to install the
kernel, and what to do if something goes wrong. 

<source trunk/arch/blackfin/mm/isram-driver.c:IADDR2DTEST() c linux-kernel>

#define IADDR2DTEST(x) \
	({ unsigned long __addr = (unsigned long)(x); \
		((__addr & (1 << 11)) << (26 - 11)) | /* addr bit 11 (Way0/Way1)   */ \
		(1 << 24)                           | /* instruction access = 1    */ \
		((__addr & (1 << 15)) << (23 - 15)) | /* addr bit 15 (Data Bank)   */ \
		((__addr & (3 << 12)) << (16 - 12)) | /* addr bits 13:12 (Subbank) */ \
		(__addr & 0x47F8)                   | /* addr bits 14 & 10:3       */ \
		(1 << 2);                             /* data array = 1            */ \
	})

$ this is a shell prompt

xterms within <WRAP box> tags, to give things different colours/titles:

test:~ #> whoami
root
test:~ #>

Linux:~ $> whoami
username
Linux:~ $>

An uppercase <WRAP> (or alternatively <block> or <div>) creates a div and should be used for “big” containers, surrounding paragraphs, lists, tables, etc.

<WRAP classes width :language>
"big" content
</WRAP>

or
<block classes width :language>
"big" content
</block>

or
<div classes width :language>
"big" content
</div>

A lowercase <wrap> (or alternatively <inline> or <span>) creates a span and should be used for “small” containers, inside paragraphs, lists, tables, etc.

<wrap classes width :language>"small" content</wrap>

or
<inline classes width :language>"small" content</inline>

or
<span classes width :language>"small" content</span>

Please note, some things won't work with lowercase spans:

• alignments (including alignments generated by changing the text direction)
• multi-columns
• and widths

if the according wrap isn't floated as well.

You can have columns easily by adding the class column and a width, e.g.

<WRAP column 30%>...content...</WRAP>

//**__Emulated Big Headline__**//

//**Emulated Small Headline**//

**//No Headline//**

After using any of the float classes, you might come across something like this, where the following text protrudes into the space where only the floating containers should be …

… to prevent that, you should simply add

<WRAP clear></WRAP>

after your last column.

You can use the same options with spans (as each element that floats is automatically a block level element), but it probably doesn't make too much sense. Widths on spans normally do not work (by design), but can make sense, when it is floating.

Attention: Widths can cause problems and will often look different and break in some browsers. If you're not a web developer, you might not understand any problems regarding the box model. Just try to test your columns in all major browsers and make your widths smaller than you initially think they should be.

All of those options will also work in the boxes and notes wraps (see below).

You can use these different text alignments:

• leftalign
• rightalign
• centeralign
• justify

<WRAP centeralign>
Center aligned text ...
</WRAP>

<WRAP rightalign>
... and right aligned.
</WRAP>

You cannot add alignments to spans.

<WRAP info></WRAP>

<WRAP tip></WRAP>

<WRAP important></WRAP>

<WRAP alert></WRAP>

<WRAP round help></WRAP>

<WRAP download></WRAP>

<WRAP todo></WRAP>

Safety Notes:

<WRAP danger></WRAP>

<WRAP warning></WRAP>

<WRAP caution></WRAP>

<WRAP round notice></WRAP>

<WRAP round safety></WRAP>

You can use notes and boxes also inside text with spans like this: info, help, alert, important, tip, download, todo and round box and danger, warning, caution, notice, safety.

<wrap info>info</wrap>, <wrap help>help</wrap>, ...

You can mark text as highlighted, less significant and especially emphasised.

You can mark text as <wrap hi>highlighted</wrap>, <wrap lo>less significant</wrap> and <wrap em>especially emphasised</wrap>.

This might look ugly in some templates and should be adjusted accordingly.

This text will appear indented.

<wrap indent>This text will appear indented.</wrap>

This text will appear “outdented”.

<wrap outdent>This text will appear "outdented".</wrap>

Inside this code block the words will wrap to a new line although they are all in one line.

<WRAP prewrap 250px>
<code>
Inside this code block the words will wrap to a new line although they are all in one line.
</code>
</WRAP>

Here follows a spoiler: Darth Vader is Luke's father.

Here follows a spoiler: <wrap spoiler>Darth Vader is Luke's father.</wrap>

Just select the text in the spoiler box to be able to read its content.

The following text is hidden: John, please revise that sentence.

The following text is hidden: <wrap hide>John, please revise that sentence.</wrap>

Warning: The text will still appear in the source code, in non-modern browsers and is searchable. Do not hide any security risky secrets with it!

The following will add a pagebreak:

The following will add a pagebreak: <WRAP pagebreak></WRAP>

This has no effect on the browser screen. A pagebreak will force a new page in printouts.

The following will try to avoid a pagebreak:

The following will try to avoid a pagebreak: <WRAP nopagebreak>much content, belonging together (like a long table)</WRAP>

This also has no effect on the browser screen. It will try to avoid a page break in printouts.

This text appears on the screen, but not in print.

<wrap noprint>This text appears on the screen, but not in print.</wrap>

This text does not appear on the screen, but only in print.

<wrap onlyprint>This text does not appear on the screen, but only in print.</wrap>

I advise against using the following typography classes. It's better to create semantic classes that reflect their meaning instead.

• font family: sansserif, serif, monospace
• font size: bigger, muchbigger, smaller
• font colour: fgred, fggreen, fgblue, fgcyan, fgviolet, fgyellow, fggrey, fgwhite, fgblack
• background colour: bgred, bggreen, bgblue, bgcyan, bgviolet, bgyellow, bggrey, bgwhite, bgblack

You can combine and nest all classes and types of boxes, e.g.

<WRAP box bggreen fgblack 350px right :en>
//**__Outer green box floats right__**//

<WRAP 165px left>
Inner nested box floats left and is partly <wrap em hi>__em__phasized and __hi__ghlighted with nested <wrap bigger>__bigger__ text</wrap> inside</wrap>.
</WRAP>

Text inside outer right box, but beneath inner left box.

<WRAP clear></WRAP>

<WRAP round tip>
Round tip box underneath, after a ''clear''.
</WRAP>

</WRAP>

You can change the language and the reading direction of a wrap container by simply adding a colon followed by the language code, like this:

<WRAP :he>
זוהי עברית. ((<wrap :en>This means "This is Hebrew.", at least according to [[http://translate.google.com/|Google Translate]].</wrap>))
</WRAP>

The text direction (rtl, right to left or ltr, left to right) will get inserted automatically and is solely dependent on the language. The list of currently supported languages is taken from: http://meta.wikimedia.org/wiki/Template:List_of_language_names_ordered_by_code (If you specify a language not listed there, it simply won't do anything.)

 {{analogTV>983688886001}}