Daniel Dunn's Personal Site!

Sidebar

Table of Contents

New Stuff!

The Wacker

He shouted orders with precision and clarity. He surveyed the area, predicted in his mind how the wind would drive the fire, made a plan, and confidently declared what had to be done, before quickly heading off to connect the hoses.

But nobody payed any mind. They all had real work to do and weren't about to take orders from some idiot who had only been there six months, four of which was just the training period. The prevailing thought was that it was helpful to have another man on the woefully understaffed team, but even then, opinions of John had been dropping by the day since he arrived.

Still, he was always first to respond to every call. He sometimes gave useful insight, even if not quite as often as he gave completely useless advice(A department so understaffed and underfunded that they needed him, did not have time to waste scouting the whole block during the beginnings of a house fire for “possible suspects”)

And then, there was the time that he saved that guy. The fire was only his second, and one of the worst they had faced that year, and the huge amount of spilled gasoline meant that the hoses just made things worse. But John charged right in and grabbed the guy; earning himself a week in the hospital, and the respect of the the rest of the crew for it.

So you kind of had to respect him, you kind of had to see that the station needed him, maybe; but it was very hard to like him. He just wasn't a likable guy.

For one thing, you got the feeling he really didn't care how things turned out, as long as he looked like a hero.

And for another, things didn't turn out well as often as they should have with his “heroism” in the mix.

For as much as he liked to talk about the guy he saved, he never did much like to talk about the time the chief almost died saving him, or all the times he wasted precious seconds with his useless drivel, or the fact that the six months he had been with the department was the longest he had ever held down a job in his life.

But one day the department got a call to a manufacturing facility. They didn't know where or even if there was a fire, as the building was evacuated when the first sensor tripped, but he was cool an confident.

The minute he saw the computer screen flash “Tuckland Mfg Sensor 15-89 trip sector X” his eyes lit up like nothing the crew had ever seen before.

Almost all the sensors had tripped, so John knew this would be a big one. It would have everything: Chemicals, Metal, Electricity, Confined spaces, unknown layouts, industrial robots possibly still in operation, millions of dollars on the line; It was just the challenge someone like him waits a lifetime for. And the rest of the crew could tell. They saw how exited he was and it made them nervous.

“Heroes don't live past 30” the chief would always say. “Use your head and you might tell your grandkids about this. Rush in and you aren't gonna be rushing out with your own legs”

None of this, of course, had any effect on him. It was just so much dramatic fluff, important only to set the stage for a grand spectacle. His ** grand spectacle.

The chief took charge, directing one of the other younger firemen away from John. John definitely knew how to talk. He could usually convince the newer hires that he had much more experience than he did.

But when the chief saw John talking a bit too confidently, he always just had to shut his mouth, and whoever was listening usually quickly saw the truth and walked away, embarrassed to be seen listening so intently to what amounted to a complete amateur.

The men gathered their gear, breathing equipment, hoses, and a brand new thermal camera, and put on their suits.

The chief stood by as they got into the truck, looking each one over to make sure they hadn't forgotten anything obvious. “Your hose is dragging” he said to one of the men, who quickly clipped it into place.

On the way there, John was slightly quieter than usual. He was studying the instructions for the thermal camera, and installing new batteries in a hand-held air quality analyzer he had bought with his own money. The rest of the crew were just happy to have a few minutes off from his incessant useless verbosity.

He was so quiet, in fact, one might even have thought he was starting to take this seriously. A look at his face told otherwise.

They arrived at the scene and exited, the chief getting out first and watching everyone get out in much the same way he watched when they got in, and they made their way across the dark parking lot to the main entrance.

Small groups of people were still onsite, mostly managers wearing steel-toed dress shoes and white hard hats, and looking very much upset at the whole affair.

But the building itself appeared to be perfectly normal. There was no smoke, no fire, and John did not see any excess heat through the new camera.

For a moment, He looked like he was going to open his mouth, or perhaps leave the group to go check out the other side, but the chief gave him an unmistakable look of disapproval and he went back to looking through the green-tinted eyepiece of the camera.

The chief walked up to one of the managers, while the rest stayed a safe distance so as not to crowd the already angered bosses. He showed the chief a clipboard, and he motioned for his crew to make their way in.

They moved in slowly and quietly almost as if they hoped any fire would not notice them. With as much as they had seen, nobody could fault them for thinking that way. A lot could go wrong in a place like that if you weren't careful.

But there was no fire in sight. No signal on John's air quality sensor or from the camera, and no sound except one ventilation fan in the ceiling that had not automatically shut down.

No sound, that is, until John turned around, assuming a much more indignant and aggressive stance than his fellows' humble and careful gait, and started walking back towards the exit.

“Hey!” shouted one of the more senior firemen. “Splitting up the group is how lives are lost”

He paused and crept back towards the group. The chief looked sadly towards the ground.

John was strong. He never missed a workout no matter what. He seemed to know how to handle things when everything was crashing down around him. But as soon as the disaster ended he couldn't help himself from causing another. It was where he felt at home.

The chief found himself lost in thought. Remembering the first few months with John, How he was the only one to notice when the air tanks were underfilled before the night when three buildings went up. How he always showed up exactly on time.

But more than anything, how happy he was when John had saved that man. Seeing such an act of selflessness filled him with pride.

He disobeyed orders, sure, but he had only been out of training for two weeks, and in time he would surely learn not to be so reckless. A hospital stay has a way of teaching most people. John was, after all, the chief's personal project in a way. John knew from the start he would be a hard case. But he saw potential in him and was not about to let that die.

For a moment he almost felt like he would have to hold back tears. But then he felt something he hadn't felt in a long time. Six months was far too long to still be pulling things like that. Walking out, deserting the rest of the crew in the middle of what was still a possible fire was unacceptable to him. He felt anger, betrayal, an disgust. He wasn't sure what to make of it all.

The rest of the crew were starting to move on to investigate the back of a stamping press by the time he snapped out of it. As expected, there was no fire behind the stamping press. There was no fire behind the milling machine. There was not even a fire in the janitor's closet, where oily rags had been piled in stereotypical fashion just waiting to become a blaze. They went over every square foot of the factory.

Eventually they gave up and went home. An unhappy night shift manager who had just arrived home got the call and headed straight back to work, along with those of the employees who didn't sleep right through the calls. Production carried on as normal.

But John didn’t seem as relieved as the rest. In fact, he seemed utterly agitated. Luke almost thought about asking what was wrong, but he already knew. It was disappointment. Disappointment that you could see in John’s eyes as soon as he saw that the fire of a lifetime was no fire at all.

All the members of the crew were real get-things-done kind of people. Nobody was sitting down and making performance reports. If things were going well, everyone knew it, and if they weren't, everyone usually knew who or what to blame.

But this time nobody was sure. Nobody knew if they were doing a good job. The only thing anyone knew is that something was not right. There were whisperings in the hallways, people wondering what to do, but the chief didn't say anything at all. He felt like he had completely lost control of everything.

If he kicked John out, people could die. Not many people were willing to do this job, and certainly not with as much enthusiasm as John had, even if it was all completely misdirected.

And what would become of him outside the department? The chief's wife had showed him a magazine article about psychopathy one time, and he was beginning to wonder more and more just who this John was. Would he become a criminal? He clearly needed excitement in his life, and he was going to find it any way he could.

The chief wanted to believe in John. He hoped that somewhere John really did care about the lives at stake every time they suited up and started the old truck. But now he didn't even know how he felt or what he wanted.

So he poured himself a glass of strong bourbon, put three ice cubes in, turned on the news for background noise, drank it down, and fell asleep in his chair.

Time went on and John slowly learned to show a little more respect. Ever so often, he would spot something nobody else did, or be there just in time when nobody else could.

He wasn't rushing in without his gear anymore, or disobeying orders as often; but every now and again he would make some callous remark or obnoxious mistake that had the whole crew doubting why they tolerated him. Nobody could really tell if he was really learning and improving, or just learning to pretend. Could he ever be trusted with any real responsibility? Or would the rest of the crew just have to spend the rest of their careers keeping tabs on him?

I don't know the answers. I don't know what you do with a person like John. I don't know what's going to happen to him or that department or the chief. I don't even know if there are any good answers to questions like these. I don't even know if he's still there at the department.

But maybe we can at least learn from this story. Maybe we will never be firemen and women, but when an important decision comes up, maybe we can remember that it's not always just about us. Maybe we can remember that being a hero isn't just wearing a costume, and that villains have capes too.

Maybe we can stop spending so much time chasing power and recognition and pretending to be things that we aren't. Maybe some of us need to step back and remember the person next to us is a real person too, and not just some anonymous member of our own private audience.

And maybe if we can learn that from John’s story, maybe it really was worth keeping him around at the firehouse.

2020/12/19 09:05

Why We Wait

Do you ever feel like you are waiting for something, but you aren't sure what? Like you should be doing something, but are not sure what?

Long ago in an village by a tall cliff, there was once a story the wise ones told of this. Though I don't know if it is still told now, it is still found on the pages of dusty old books, that, too, wait. I will translate it here as best I can.

For three days the prince waited by the cliff, and for three days she did not come.

For the first day he laughed. She was the playful sort. Surely she was simply distracted.

For the second day he worried, for a day was a long time, and he knew few things could keep her attention.

For the third day he cried, for he knew she loved him too much to stay away for so long.

But still he stayed. For he could do nothing else.

Until one day, a woman came and asked him to come with him to the edge. She made him look down below where he saw the body of his love.

“Now we can finally be together” she said. But the prince had learned much of magic, and spoke something like these words:

“As I have waited here, so to shall you wait, and so shall your daughters and their sons wait, until not one man can tell who it is you wait for.”

And so it was that he had grabbed the woman's mother, and hurled himself to his death, for there never was a woman so intent to see her daughter wed to a prince as her.

And so it is that until this day, there are some that wait, and have waited, and some that shall wait until they are too old to know they are waiting.

And still you will here the older people in that village warn the children to remember who waits for them, lest they find themselves the ones waiting.

2020/12/19 09:05

New Stuff!

The Wacker

He shouted orders with precision and clarity. He surveyed the area, predicted in his mind how the wind would drive the fire, made a plan, and confidently declared what had to be done, before quickly heading off to connect the hoses.

But nobody payed any mind. They all had real work to do and weren't about to take orders from some idiot who had only been there six months, four of which was just the training period. The prevailing thought was that it was helpful to have another man on the woefully understaffed team, but even then, opinions of John had been dropping by the day since he arrived.

Still, he was always first to respond to every call. He sometimes gave useful insight, even if not quite as often as he gave completely useless advice(A department so understaffed and underfunded that they needed him, did not have time to waste scouting the whole block during the beginnings of a house fire for “possible suspects”)

And then, there was the time that he saved that guy. The fire was only his second, and one of the worst they had faced that year, and the huge amount of spilled gasoline meant that the hoses just made things worse. But John charged right in and grabbed the guy; earning himself a week in the hospital, and the respect of the the rest of the crew for it.

So you kind of had to respect him, you kind of had to see that the station needed him, maybe; but it was very hard to like him. He just wasn't a likable guy.

For one thing, you got the feeling he really didn't care how things turned out, as long as he looked like a hero.

And for another, things didn't turn out well as often as they should have with his “heroism” in the mix.

For as much as he liked to talk about the guy he saved, he never did much like to talk about the time the chief almost died saving him, or all the times he wasted precious seconds with his useless drivel, or the fact that the six months he had been with the department was the longest he had ever held down a job in his life.

But one day the department got a call to a manufacturing facility. They didn't know where or even if there was a fire, as the building was evacuated when the first sensor tripped, but he was cool an confident.

The minute he saw the computer screen flash “Tuckland Mfg Sensor 15-89 trip sector X” his eyes lit up like nothing the crew had ever seen before.

Almost all the sensors had tripped, so John knew this would be a big one. It would have everything: Chemicals, Metal, Electricity, Confined spaces, unknown layouts, industrial robots possibly still in operation, millions of dollars on the line; It was just the challenge someone like him waits a lifetime for. And the rest of the crew could tell. They saw how exited he was and it made them nervous.

“Heroes don't live past 30” the chief would always say. “Use your head and you might tell your grandkids about this. Rush in and you aren't gonna be rushing out with your own legs”

None of this, of course, had any effect on him. It was just so much dramatic fluff, important only to set the stage for a grand spectacle. His ** grand spectacle.

The chief took charge, directing one of the other younger firemen away from John. John definitely knew how to talk. He could usually convince the newer hires that he had much more experience than he did.

But when the chief saw John talking a bit too confidently, he always just had to shut his mouth, and whoever was listening usually quickly saw the truth and walked away, embarrassed to be seen listening so intently to what amounted to a complete amateur.

The men gathered their gear, breathing equipment, hoses, and a brand new thermal camera, and put on their suits.

The chief stood by as they got into the truck, looking each one over to make sure they hadn't forgotten anything obvious. “Your hose is dragging” he said to one of the men, who quickly clipped it into place.

On the way there, John was slightly quieter than usual. He was studying the instructions for the thermal camera, and installing new batteries in a hand-held air quality analyzer he had bought with his own money. The rest of the crew were just happy to have a few minutes off from his incessant useless verbosity.

He was so quiet, in fact, one might even have thought he was starting to take this seriously. A look at his face told otherwise.

They arrived at the scene and exited, the chief getting out first and watching everyone get out in much the same way he watched when they got in, and they made their way across the dark parking lot to the main entrance.

Small groups of people were still onsite, mostly managers wearing steel-toed dress shoes and white hard hats, and looking very much upset at the whole affair.

But the building itself appeared to be perfectly normal. There was no smoke, no fire, and John did not see any excess heat through the new camera.

For a moment, He looked like he was going to open his mouth, or perhaps leave the group to go check out the other side, but the chief gave him an unmistakable look of disapproval and he went back to looking through the green-tinted eyepiece of the camera.

The chief walked up to one of the managers, while the rest stayed a safe distance so as not to crowd the already angered bosses. He showed the chief a clipboard, and he motioned for his crew to make their way in.

They moved in slowly and quietly almost as if they hoped any fire would not notice them. With as much as they had seen, nobody could fault them for thinking that way. A lot could go wrong in a place like that if you weren't careful.

But there was no fire in sight. No signal on John's air quality sensor or from the camera, and no sound except one ventilation fan in the ceiling that had not automatically shut down.

No sound, that is, until John turned around, assuming a much more indignant and aggressive stance than his fellows' humble and careful gait, and started walking back towards the exit.

“Hey!” shouted one of the more senior firemen. “Splitting up the group is how lives are lost”

He paused and crept back towards the group. The chief looked sadly towards the ground.

John was strong. He never missed a workout no matter what. He seemed to know how to handle things when everything was crashing down around him. But as soon as the disaster ended he couldn't help himself from causing another. It was where he felt at home.

The chief found himself lost in thought. Remembering the first few months with John, How he was the only one to notice when the air tanks were underfilled before the night when three buildings went up. How he always showed up exactly on time.

But more than anything, how happy he was when John had saved that man. Seeing such an act of selflessness filled him with pride.

He disobeyed orders, sure, but he had only been out of training for two weeks, and in time he would surely learn not to be so reckless. A hospital stay has a way of teaching most people. John was, after all, the chief's personal project in a way. John knew from the start he would be a hard case. But he saw potential in him and was not about to let that die.

For a moment he almost felt like he would have to hold back tears. But then he felt something he hadn't felt in a long time. Six months was far too long to still be pulling things like that. Walking out, deserting the rest of the crew in the middle of what was still a possible fire was unacceptable to him. He felt anger, betrayal, an disgust. He wasn't sure what to make of it all.

The rest of the crew were starting to move on to investigate the back of a stamping press by the time he snapped out of it. As expected, there was no fire behind the stamping press. There was no fire behind the milling machine. There was not even a fire in the janitor's closet, where oily rags had been piled in stereotypical fashion just waiting to become a blaze. They went over every square foot of the factory.

Eventually they gave up and went home. An unhappy night shift manager who had just arrived home got the call and headed straight back to work, along with those of the employees who didn't sleep right through the calls. Production carried on as normal.

But John didn’t seem as relieved as the rest. In fact, he seemed utterly agitated. Luke almost thought about asking what was wrong, but he already knew. It was disappointment. Disappointment that you could see in John’s eyes as soon as he saw that the fire of a lifetime was no fire at all.

All the members of the crew were real get-things-done kind of people. Nobody was sitting down and making performance reports. If things were going well, everyone knew it, and if they weren't, everyone usually knew who or what to blame.

But this time nobody was sure. Nobody knew if they were doing a good job. The only thing anyone knew is that something was not right. There were whisperings in the hallways, people wondering what to do, but the chief didn't say anything at all. He felt like he had completely lost control of everything.

If he kicked John out, people could die. Not many people were willing to do this job, and certainly not with as much enthusiasm as John had, even if it was all completely misdirected.

And what would become of him outside the department? The chief's wife had showed him a magazine article about psychopathy one time, and he was beginning to wonder more and more just who this John was. Would he become a criminal? He clearly needed excitement in his life, and he was going to find it any way he could.

The chief wanted to believe in John. He hoped that somewhere John really did care about the lives at stake every time they suited up and started the old truck. But now he didn't even know how he felt or what he wanted.

So he poured himself a glass of strong bourbon, put three ice cubes in, turned on the news for background noise, drank it down, and fell asleep in his chair.

Time went on and John slowly learned to show a little more respect. Ever so often, he would spot something nobody else did, or be there just in time when nobody else could.

He wasn't rushing in without his gear anymore, or disobeying orders as often; but every now and again he would make some callous remark or obnoxious mistake that had the whole crew doubting why they tolerated him. Nobody could really tell if he was really learning and improving, or just learning to pretend. Could he ever be trusted with any real responsibility? Or would the rest of the crew just have to spend the rest of their careers keeping tabs on him?

I don't know the answers. I don't know what you do with a person like John. I don't know what's going to happen to him or that department or the chief. I don't even know if there are any good answers to questions like these. I don't even know if he's still there at the department.

But maybe we can at least learn from this story. Maybe we will never be firemen and women, but when an important decision comes up, maybe we can remember that it's not always just about us. Maybe we can remember that being a hero isn't just wearing a costume, and that villains have capes too.

Maybe we can stop spending so much time chasing power and recognition and pretending to be things that we aren't. Maybe some of us need to step back and remember the person next to us is a real person too, and not just some anonymous member of our own private audience.

And maybe if we can learn that from John’s story, maybe it really was worth keeping him around at the firehouse.

2020/12/19 09:05

Why We Wait

Do you ever feel like you are waiting for something, but you aren't sure what? Like you should be doing something, but are not sure what?

Long ago in an village by a tall cliff, there was once a story the wise ones told of this. Though I don't know if it is still told now, it is still found on the pages of dusty old books, that, too, wait. I will translate it here as best I can.

For three days the prince waited by the cliff, and for three days she did not come.

For the first day he laughed. She was the playful sort. Surely she was simply distracted.

For the second day he worried, for a day was a long time, and he knew few things could keep her attention.

For the third day he cried, for he knew she loved him too much to stay away for so long.

But still he stayed. For he could do nothing else.

Until one day, a woman came and asked him to come with him to the edge. She made him look down below where he saw the body of his love.

“Now we can finally be together” she said. But the prince had learned much of magic, and spoke something like these words:

“As I have waited here, so to shall you wait, and so shall your daughters and their sons wait, until not one man can tell who it is you wait for.”

And so it was that he had grabbed the woman's mother, and hurled himself to his death, for there never was a woman so intent to see her daughter wed to a prince as her.

And so it is that until this day, there are some that wait, and have waited, and some that shall wait until they are too old to know they are waiting.

And still you will here the older people in that village warn the children to remember who waits for them, lest they find themselves the ones waiting.

2020/12/19 09:05

Welcome to your new DokuWiki

Congratulations, your wiki is now up and running. Here are a few more tips to get you started.

Enjoy your work with DokuWiki,

– the developers

Create your first pages

Your wiki needs to have a start page. As long as it doesn't exist, this link will be red: New Stuff!.

Go on, follow that link and create the page. If you need help with using the syntax you can always refer to the syntax page.

You might also want to use a sidebar. To create it, just edit the sidebar page. Everything in that page will be shown in a margin column on the side. Read our FAQ on sidebars to learn more.

Please be aware that not all templates support sidebars.

Customize your Wiki

Once you're comfortable with creating and editing pages you might want to have a look at the configuration settings (be sure to login as superuser first).

You may also want to see what plugins and templates are available at DokuWiki.org to extend the functionality and looks of your DokuWiki installation.

Join the Community

DokuWiki is an Open Source project that thrives through user contributions. A good way to stay informed on what's going on and to get useful tips in using DokuWiki is subscribing to the newsletter.

The DokuWiki User Forum is an excellent way to get in contact with other DokuWiki users and is just one of the many ways to get support.

Of course we'd be more than happy to have you getting involved with DokuWiki.

2020/12/19 08:39

Formatting Syntax

DokuWiki supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing “Edit this page”. If you want to try something, just use the playground page. The simpler markup is easily accessible via quickbuttons, too.

Basic Text Formatting

DokuWiki supports bold, italic, underlined and monospaced texts. Of course you can combine all these. 

DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts.
Of course you can **__//''combine''//__** all these.

You can use subscript and superscript, too. 

You can use <sub>subscript</sub> and <sup>superscript</sup>, too.

You can mark something as deleted as well. 

You can mark something as <del>deleted</del> as well.

Paragraphs are created from blank lines. If you want to force a newline without a paragraph, you can use two backslashes followed by a whitespace or the end of line.

This is some text with some linebreaks
Note that the
two backslashes are only recognized at the end of a line

or followed by
a whitespace \\this happens without it. 

This is some text with some linebreaks\\ Note that the
two backslashes are only recognized at the end of a line\\
or followed by\\ a whitespace \\this happens without it.

You should use forced newlines only if really needed.

DokuWiki supports multiple ways of creating links.

External

External links are recognized automagically: http://www.google.com or simply www.google.com - You can set the link text as well: This Link points to google. Email addresses like this one: andi@splitbrain.org are recognized, too. 

DokuWiki supports multiple ways of creating links. External links are recognized
automagically: http://www.google.com or simply www.google.com - You can set
link text as well: [[http://www.google.com|This Link points to google]]. Email
addresses like this one: <andi@splitbrain.org> are recognized, too.
Internal

Internal links are created by using square brackets. You can either just give a pagename or use an additional link text. 

Internal links are created by using square brackets. You can either just give
a [[pagename]] or use an additional [[pagename|link text]].

Wiki pagenames are converted to lowercase automatically, special characters are not allowed.

You can use namespaces by using a colon in the pagename. 

You can use [[some:namespaces]] by using a colon in the pagename.

For details about namespaces see namespaces.

Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to this Section. 

This links to [[syntax#internal|this Section]].

Notes:

  • Links to existing pages are shown in a different style from nonexisting ones.
  • DokuWiki does not use CamelCase to automatically create links by default, but this behavior can be enabled in the config file. Hint: If DokuWiki is a link, then it's enabled.
  • When a section's heading is changed, its bookmark changes, too. So don't rely on section linking too much.
Interwiki

DokuWiki supports Interwiki links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: Wiki. 

DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis.
For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].
Windows Shares

Windows shares like this are recognized, too. Please note that these only make sense in a homogeneous user group like a corporate Intranet. 

Windows Shares like [[\\server\share|this]] are recognized, too.

Notes:

  • For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the “local zone”).
  • For Mozilla and Firefox it can be enabled through different workaround mentioned in the Mozilla Knowledge Base. However, there will still be a JavaScript warning about trying to open a Windows Share. To remove this warning (for all users), put the following line in conf/lang/en/lang.php (more details at localization):
    conf/lang/en/lang.php
    <?php
/**
 * Customization of the english language file
 * Copy only the strings that needs to be modified
 */
$lang['js']['nosmblinks'] = '';

You can also use an image to link to another internal or external page by combining the syntax for links and images (see below) like this: 

[[http://php.net|{{wiki:dokuwiki-128.png}}]]

Please note: The image formatting is the only formatting syntax accepted in link names.

The whole image and link syntax is supported (including image resizing, internal and external images and URLs and interwiki links).

Footnotes

You can add footnotes 1) by using double parentheses. 

You can add footnotes ((This is a footnote)) by using double parentheses.

Sectioning

You can use up to five different levels of headlines to structure your content. If you have more than three headlines, a table of contents is generated automatically – this can be disabled by including the string ~~NOTOC~~ in the document.

Headline Level 3
Headline Level 4
Headline Level 5
==== Headline Level 3 ====
=== Headline Level 4 ===
== Headline Level 5 ==

By using four or more dashes, you can make a horizontal line:

Media Files

You can include external and internal images, videos and audio files with curly brackets. Optionally you can specify the size of them.

Real size:

Resize to given width:

Resize to given width and height2):

Resized external image:           

Real size:                        {{wiki:dokuwiki-128.png}}
Resize to given width:            {{wiki:dokuwiki-128.png?50}}
Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}}
Resized external image:           {{https://secure.php.net/images/php.gif?200x50}}

By using left or right whitespaces you can choose the alignment. 

{{ wiki:dokuwiki-128.png}}
{{wiki:dokuwiki-128.png }}
{{ wiki:dokuwiki-128.png }}

Of course, you can add a title (displayed as a tooltip by most browsers), too.

This is the caption 

{{ wiki:dokuwiki-128.png |This is the caption}}

For linking an image to another page see Image Links above.

Supported Media Formats

DokuWiki can embed the following media formats directly.

Image gif, jpg, png
Video webm, ogv, mp4
Audio ogg, mp3, wav
Flash swf

If you specify a filename that is not a supported media format, then it will be displayed as a link instead.

By adding ?linkonly you provide a link to the media without displaying it inline 

{{wiki:dokuwiki-128.png?linkonly}}

dokuwiki-128.png This is just a link to the image.

Fallback Formats

Unfortunately not all browsers understand all video and audio formats. To mitigate the problem, you can upload your file in different formats for maximum browser compatibility.

For example consider this embedded mp4 video: 

{{video.mp4|A funny video}}

When you upload a video.webm and video.ogv next to the referenced video.mp4, DokuWiki will automatically add them as alternatives so that one of the three files is understood by your browser.

Additionally DokuWiki supports a “poster” image which will be shown before the video has started. That image needs to have the same filename as the video and be either a jpg or png file. In the example above a video.jpg file would work.

Lists

Dokuwiki supports ordered and unordered lists. To create a list item, indent your text by two spaces and use a * for unordered lists or a - for ordered ones.

  • This is a list
  • The second item
    • You may have different levels
  • Another item
  1. The same list but ordered
  2. Another item
    1. Just use indention for deeper levels
  3. That's it
  * This is a list
  * The second item
    * You may have different levels
  * Another item

  - The same list but ordered
  - Another item
    - Just use indention for deeper levels
  - That's it

Also take a look at the FAQ on list items.

Text Conversions

DokuWiki can convert certain pre-defined characters or strings into images or other text or HTML.

The text to image conversion is mainly done for smileys. And the text to HTML conversion is used for typography replacements, but can be configured to use other HTML as well.

Text to Image Conversions

DokuWiki converts commonly used emoticons to their graphical equivalents. Those Smileys and other images can be configured and extended. Here is an overview of Smileys included in DokuWiki:

  • 8-) 8-)
  • 8-O 8-O
  • :-( :-(
  • :-) :-)
  • =) =)
  • :-/ :-/
  • :-\ :-\
  • :-? :-?
  • :-D :-D
  • :-P :-P
  • :-O :-O
  • :-X :-X
  • :-| :-|
  • ;-) ;-)
  • ^_^ ^_^
  • :?: :?:
  • :!: :!:
  • LOL LOL
  • FIXME FIXME
  • DELETEME DELETEME
Text to HTML Conversions

Typography: DokuWiki can convert simple text characters to their typographically correct entities. Here is an example of recognized characters.

→ ← ↔ ⇒ ⇐ ⇔ » « – — 640×480 © ™ ®
“He thought 'It's a man's world'…” 

-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
"He thought 'It's a man's world'..."

The same can be done to produce any kind of HTML, it just needs to be added to the pattern file.

There are three exceptions which do not come from that pattern file: multiplication entity (640×480), 'single' and “double quotes”. They can be turned off through a config option.

Quoting

Some times you want to mark some text to show it's a reply or comment. You can use the following syntax: 

I think we should do it

> No we shouldn't

>> Well, I say we should

> Really?

>> Yes!

>>> Then lets do it!

I think we should do it

No we shouldn't
Well, I say we should
Really?
Yes!
Then lets do it!

Tables

DokuWiki supports a simple syntax to create tables.

Heading 1 Heading 2 Heading 3
Row 1 Col 1 Row 1 Col 2 Row 1 Col 3
Row 2 Col 1 some colspan (note the double pipe)
Row 3 Col 1 Row 3 Col 2 Row 3 Col 3

Table rows have to start and end with a | for normal rows or a ^ for headers. 

^ Heading 1      ^ Heading 2       ^ Heading 3          ^
| Row 1 Col 1    | Row 1 Col 2     | Row 1 Col 3        |
| Row 2 Col 1    | some colspan (note the double pipe) ||
| Row 3 Col 1    | Row 3 Col 2     | Row 3 Col 3        |

To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators!

Vertical tableheaders are possible, too.

Heading 1 Heading 2
Heading 3 Row 1 Col 2 Row 1 Col 3
Heading 4 no colspan this time
Heading 5 Row 2 Col 2 Row 2 Col 3

As you can see, it's the cell separator before a cell which decides about the formatting: 

|              ^ Heading 1            ^ Heading 2          ^
^ Heading 3    | Row 1 Col 2          | Row 1 Col 3        |
^ Heading 4    | no colspan this time |                    |
^ Heading 5    | Row 2 Col 2          | Row 2 Col 3        |

You can have rowspans (vertically connected cells) by adding ::: into the cells below the one to which they should connect.

Heading 1 Heading 2 Heading 3
Row 1 Col 1 this cell spans vertically Row 1 Col 3
Row 2 Col 1 Row 2 Col 3
Row 3 Col 1 Row 2 Col 3

Apart from the rowspan syntax those cells should not contain anything else. 

^ Heading 1      ^ Heading 2                  ^ Heading 3          ^
| Row 1 Col 1    | this cell spans vertically | Row 1 Col 3        |
| Row 2 Col 1    | :::                        | Row 2 Col 3        |
| Row 3 Col 1    | :::                        | Row 2 Col 3        |

You can align the table contents, too. Just add at least two whitespaces at the opposite end of your text: Add two spaces on the left to align right, two spaces on the right to align left and two spaces at least at both ends for centered text.

Table with alignment
right center left
left right center
xxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxx

This is how it looks in the source: 

^           Table with alignment           ^^^
|         right|    center    |left          |
|left          |         right|    center    |
| xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx |

Note: Vertical alignment is not supported.

No Formatting

If you need to display text exactly like it is typed (without any formatting), enclose the area either with <nowiki> tags or even simpler, with double percent signs %%.

This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
The same is true for //__this__ text// with a smiley ;-). 

<nowiki>
This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
</nowiki>
The same is true for %%//__this__ text// with a smiley ;-)%%.

Code Blocks

You can include code blocks into your documents by either indenting them by at least two spaces (like used for the previous examples) or by using the tags <code> or <file>. 

This is text is indented by two spaces.
This is preformatted code all spaces are preserved: like              <-this
This is pretty much the same, but you could use it to show that you quoted a file.

Those blocks were created by this source: 

  This is text is indented by two spaces.
<code>
This is preformatted code all spaces are preserved: like              <-this
</code>
<file>
This is pretty much the same, but you could use it to show that you quoted a file.
</file>
Syntax Highlighting

DokuWiki can highlight sourcecode, which makes it easier to read. It uses the GeSHi Generic Syntax Highlighter – so any language supported by GeSHi is supported. The syntax uses the same code and file blocks described in the previous section, but this time the name of the language syntax to be highlighted is included inside the tag, e.g. <code java> or <file java>. 

/**
 * The HelloWorldApp class implements an application that
 * simply displays "Hello World!" to the standard output.
 */
class HelloWorldApp {
    public static void main(String[] args) {
        System.out.println("Hello World!"); //Display the string.
    }
}

The following language strings are currently recognized: 4cs 6502acme 6502kickass 6502tasm 68000devpac abap actionscript3 actionscript ada aimms algol68 apache applescript apt_sources arm asm asp asymptote autoconf autohotkey autoit avisynth awk bascomavr bash basic4gl batch bf biblatex bibtex blitzbasic bnf boo caddcl cadlisp ceylon cfdg cfm chaiscript chapel cil c_loadrunner clojure c_mac cmake cobol coffeescript c cpp cpp-qt cpp-winapi csharp css cuesheet c_winapi dart dcl dcpu16 dcs delphi diff div dos dot d ecmascript eiffel email epc e erlang euphoria ezt f1 falcon fo fortran freebasic freeswitch fsharp gambas gdb genero genie gettext glsl gml gnuplot go groovy gwbasic haskell haxe hicest hq9plus html html4strict html5 icon idl ini inno intercal io ispfpanel java5 java javascript jcl j jquery julia kixtart klonec klonecpp kotlin latex lb ldif lisp llvm locobasic logtalk lolcode lotusformulas lotusscript lscript lsl2 lua m68k magiksf make mapbasic mathematica matlab mercury metapost mirc mk-61 mmix modula2 modula3 mpasm mxml mysql nagios netrexx newlisp nginx nimrod nsis oberon2 objc objeck ocaml-brief ocaml octave oobas oorexx oracle11 oracle8 oxygene oz parasail parigp pascal pcre perl6 perl per pf phix php-brief php pic16 pike pixelbender pli plsql postgresql postscript povray powerbuilder powershell proftpd progress prolog properties providex purebasic pycon pys60 python qbasic qml q racket rails rbs rebol reg rexx robots roff rpmspec rsplus ruby rust sas sass scala scheme scilab scl sdlbasic smalltalk smarty spark sparql sql sshconfig standardml stonescript swift systemverilog tclegg tcl teraterm texgraph text thinbasic tsql twig typoscript unicon upc urbi uscript vala vbnet vb vbscript vedit verilog vhdl vim visualfoxpro visualprolog whitespace whois winbatch wolfram xbasic xml xojo xorg_conf xpp yaml z80 zxbasic

There are additional advanced options available for syntax highlighting, such as highlighting lines or adding line numbers.

Downloadable Code Blocks

When you use the <code> or <file> syntax as above, you might want to make the shown code available for download as well. You can do this by specifying a file name after language code like this: 

<file php myexample.php>
<?php echo "hello world!"; ?>
</file>
myexample.php
<?php echo "hello world!"; ?>

If you don't want any highlighting but want a downloadable file, specify a dash (-) as the language code: <code - myfile.foo>.

Embedding HTML and PHP

You can embed raw HTML or PHP code into your documents by using the <html> or <php> tags. (Use uppercase tags if you need to enclose block level elements.)

HTML example: 

<html>
This is some <span style="color:red;font-size:150%;">inline HTML</span>
</html>
<HTML>
<p style="border:2px dashed red;">And this is some block HTML</p>
</HTML>

This is some inline HTML

And this is some block HTML

PHP example: 

<php>
echo 'The PHP version: ';
echo phpversion();
echo ' (generated inline HTML)';
</php>
<PHP>
echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
echo '<td>'.phpversion().'</td>';
echo '</tr></table>';
</PHP>

echo 'The PHP version: '; echo phpversion(); echo ' (inline HTML)'; 

echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
echo '<td>'.phpversion().'</td>';
echo '</tr></table>';

Please Note: HTML and PHP embedding is disabled by default in the configuration. If disabled, the code is displayed instead of executed.

RSS/ATOM Feed Aggregation

DokuWiki can integrate data from external XML feeds. For parsing the XML feeds, SimplePie is used. All formats understood by SimplePie can be used in DokuWiki as well. You can influence the rendering by multiple additional space separated parameters:

Parameter Description
any number will be used as maximum number items to show, defaults to 8
reverse display the last items in the feed first
author show item authors names
date show item dates
description show the item description. If HTML is disabled all tags will be stripped
nosort do not sort the items in the feed
n[dhm] refresh period, where d=days, h=hours, m=minutes. (e.g. 12h = 12 hours).

The refresh period defaults to 4 hours. Any value below 10 minutes will be treated as 10 minutes. DokuWiki will generally try to supply a cached version of a page, obviously this is inappropriate when the page contains dynamic external content. The parameter tells DokuWiki to re-render the page if it is more than refresh period since the page was last rendered.

By default the feed will be sorted by date, newest items first. You can sort it by oldest first using the reverse parameter, or display the feed as is with nosort.

Example: 

{{rss>http://slashdot.org/index.rss 5 author date 1h }}

Control Macros

Some syntax influences how DokuWiki renders a page without creating any output it self. The following control macros are availble:

Macro Description
~~NOTOC~~ If this macro is found on the page, no table of contents will be created
~~NOCACHE~~ DokuWiki caches all output by default. Sometimes this might not be wanted (eg. when the <php> syntax above is used), adding this macro will force DokuWiki to rerender a page on every call

Syntax Plugins

DokuWiki's syntax can be extended by Plugins. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation:

2020/12/19 08:39

<< Newer entries | Older entries >>

2020/12/19 08:40

Welcome to your new DokuWiki

Congratulations, your wiki is now up and running. Here are a few more tips to get you started.

Enjoy your work with DokuWiki,

– the developers

Create your first pages

Your wiki needs to have a start page. As long as it doesn't exist, this link will be red: New Stuff!.

Go on, follow that link and create the page. If you need help with using the syntax you can always refer to the syntax page.

You might also want to use a sidebar. To create it, just edit the sidebar page. Everything in that page will be shown in a margin column on the side. Read our FAQ on sidebars to learn more.

Please be aware that not all templates support sidebars.

Customize your Wiki

Once you're comfortable with creating and editing pages you might want to have a look at the configuration settings (be sure to login as superuser first).

You may also want to see what plugins and templates are available at DokuWiki.org to extend the functionality and looks of your DokuWiki installation.

Join the Community

DokuWiki is an Open Source project that thrives through user contributions. A good way to stay informed on what's going on and to get useful tips in using DokuWiki is subscribing to the newsletter.

The DokuWiki User Forum is an excellent way to get in contact with other DokuWiki users and is just one of the many ways to get support.

Of course we'd be more than happy to have you getting involved with DokuWiki.

2020/12/19 08:39

Formatting Syntax

DokuWiki supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing “Edit this page”. If you want to try something, just use the playground page. The simpler markup is easily accessible via quickbuttons, too.

Basic Text Formatting

DokuWiki supports bold, italic, underlined and monospaced texts. Of course you can combine all these. 

DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts.
Of course you can **__//''combine''//__** all these.

You can use subscript and superscript, too. 

You can use <sub>subscript</sub> and <sup>superscript</sup>, too.

You can mark something as deleted as well. 

You can mark something as <del>deleted</del> as well.

Paragraphs are created from blank lines. If you want to force a newline without a paragraph, you can use two backslashes followed by a whitespace or the end of line.

This is some text with some linebreaks
Note that the
two backslashes are only recognized at the end of a line

or followed by
a whitespace \\this happens without it. 

This is some text with some linebreaks\\ Note that the
two backslashes are only recognized at the end of a line\\
or followed by\\ a whitespace \\this happens without it.

You should use forced newlines only if really needed.

Links

DokuWiki supports multiple ways of creating links.

External

External links are recognized automagically: http://www.google.com or simply www.google.com - You can set the link text as well: This Link points to google. Email addresses like this one: andi@splitbrain.org are recognized, too. 

DokuWiki supports multiple ways of creating links. External links are recognized
automagically: http://www.google.com or simply www.google.com - You can set
link text as well: [[http://www.google.com|This Link points to google]]. Email
addresses like this one: <andi@splitbrain.org> are recognized, too.

Internal

Internal links are created by using square brackets. You can either just give a pagename or use an additional link text. 

Internal links are created by using square brackets. You can either just give
a [[pagename]] or use an additional [[pagename|link text]].

Wiki pagenames are converted to lowercase automatically, special characters are not allowed.

You can use namespaces by using a colon in the pagename. 

You can use [[some:namespaces]] by using a colon in the pagename.

For details about namespaces see namespaces.

Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to this Section. 

This links to [[syntax#internal|this Section]].

Notes:

  • Links to existing pages are shown in a different style from nonexisting ones.
  • DokuWiki does not use CamelCase to automatically create links by default, but this behavior can be enabled in the config file. Hint: If DokuWiki is a link, then it's enabled.
  • When a section's heading is changed, its bookmark changes, too. So don't rely on section linking too much.

Interwiki

DokuWiki supports Interwiki links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: Wiki. 

DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis.
For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].

Windows Shares

Windows shares like this are recognized, too. Please note that these only make sense in a homogeneous user group like a corporate Intranet. 

Windows Shares like [[\\server\share|this]] are recognized, too.

Notes:

  • For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the “local zone”).
  • For Mozilla and Firefox it can be enabled through different workaround mentioned in the Mozilla Knowledge Base. However, there will still be a JavaScript warning about trying to open a Windows Share. To remove this warning (for all users), put the following line in conf/lang/en/lang.php (more details at localization):
    conf/lang/en/lang.php
    <?php
/**
 * Customization of the english language file
 * Copy only the strings that needs to be modified
 */
$lang['js']['nosmblinks'] = '';

Image Links

You can also use an image to link to another internal or external page by combining the syntax for links and images (see below) like this: 

[[http://php.net|{{wiki:dokuwiki-128.png}}]]

Please note: The image formatting is the only formatting syntax accepted in link names.

The whole image and link syntax is supported (including image resizing, internal and external images and URLs and interwiki links).

Footnotes

You can add footnotes 3) by using double parentheses. 

You can add footnotes ((This is a footnote)) by using double parentheses.

Sectioning

You can use up to five different levels of headlines to structure your content. If you have more than three headlines, a table of contents is generated automatically – this can be disabled by including the string ~~NOTOC~~ in the document.

Headline Level 3

Headline Level 4
Headline Level 5
==== Headline Level 3 ====
=== Headline Level 4 ===
== Headline Level 5 ==

By using four or more dashes, you can make a horizontal line:

Media Files

You can include external and internal images, videos and audio files with curly brackets. Optionally you can specify the size of them.

Real size:

Resize to given width:

Resize to given width and height4):

Resized external image:           

Real size:                        {{wiki:dokuwiki-128.png}}
Resize to given width:            {{wiki:dokuwiki-128.png?50}}
Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}}
Resized external image:           {{https://secure.php.net/images/php.gif?200x50}}

By using left or right whitespaces you can choose the alignment. 

{{ wiki:dokuwiki-128.png}}
{{wiki:dokuwiki-128.png }}
{{ wiki:dokuwiki-128.png }}

Of course, you can add a title (displayed as a tooltip by most browsers), too.

This is the caption 

{{ wiki:dokuwiki-128.png |This is the caption}}

For linking an image to another page see Image Links above.

Supported Media Formats

DokuWiki can embed the following media formats directly.

Image gif, jpg, png
Video webm, ogv, mp4
Audio ogg, mp3, wav
Flash swf

If you specify a filename that is not a supported media format, then it will be displayed as a link instead.

By adding ?linkonly you provide a link to the media without displaying it inline 

{{wiki:dokuwiki-128.png?linkonly}}

dokuwiki-128.png This is just a link to the image.

Fallback Formats

Unfortunately not all browsers understand all video and audio formats. To mitigate the problem, you can upload your file in different formats for maximum browser compatibility.

For example consider this embedded mp4 video: 

{{video.mp4|A funny video}}

When you upload a video.webm and video.ogv next to the referenced video.mp4, DokuWiki will automatically add them as alternatives so that one of the three files is understood by your browser.

Additionally DokuWiki supports a “poster” image which will be shown before the video has started. That image needs to have the same filename as the video and be either a jpg or png file. In the example above a video.jpg file would work.

Lists

Dokuwiki supports ordered and unordered lists. To create a list item, indent your text by two spaces and use a * for unordered lists or a - for ordered ones.

  • This is a list
  • The second item
    • You may have different levels
  • Another item
  1. The same list but ordered
  2. Another item
    1. Just use indention for deeper levels
  3. That's it
  * This is a list
  * The second item
    * You may have different levels
  * Another item

  - The same list but ordered
  - Another item
    - Just use indention for deeper levels
  - That's it

Also take a look at the FAQ on list items.

Text Conversions

DokuWiki can convert certain pre-defined characters or strings into images or other text or HTML.

The text to image conversion is mainly done for smileys. And the text to HTML conversion is used for typography replacements, but can be configured to use other HTML as well.

Text to Image Conversions

DokuWiki converts commonly used emoticons to their graphical equivalents. Those Smileys and other images can be configured and extended. Here is an overview of Smileys included in DokuWiki:

  • 8-) 8-)
  • 8-O 8-O
  • :-( :-(
  • :-) :-)
  • =) =)
  • :-/ :-/
  • :-\ :-\
  • :-? :-?
  • :-D :-D
  • :-P :-P
  • :-O :-O
  • :-X :-X
  • :-| :-|
  • ;-) ;-)
  • ^_^ ^_^
  • :?: :?:
  • :!: :!:
  • LOL LOL
  • FIXME FIXME
  • DELETEME DELETEME

Text to HTML Conversions

Typography: DokuWiki can convert simple text characters to their typographically correct entities. Here is an example of recognized characters.

→ ← ↔ ⇒ ⇐ ⇔ » « – — 640×480 © ™ ®
“He thought 'It's a man's world'…” 

-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
"He thought 'It's a man's world'..."

The same can be done to produce any kind of HTML, it just needs to be added to the pattern file.

There are three exceptions which do not come from that pattern file: multiplication entity (640×480), 'single' and “double quotes”. They can be turned off through a config option.

Quoting

Some times you want to mark some text to show it's a reply or comment. You can use the following syntax: 

I think we should do it

> No we shouldn't

>> Well, I say we should

> Really?

>> Yes!

>>> Then lets do it!

I think we should do it

No we shouldn't
Well, I say we should
Really?
Yes!
Then lets do it!

Tables

DokuWiki supports a simple syntax to create tables.

Heading 1 Heading 2 Heading 3
Row 1 Col 1 Row 1 Col 2 Row 1 Col 3
Row 2 Col 1 some colspan (note the double pipe)
Row 3 Col 1 Row 3 Col 2 Row 3 Col 3

Table rows have to start and end with a | for normal rows or a ^ for headers. 

^ Heading 1      ^ Heading 2       ^ Heading 3          ^
| Row 1 Col 1    | Row 1 Col 2     | Row 1 Col 3        |
| Row 2 Col 1    | some colspan (note the double pipe) ||
| Row 3 Col 1    | Row 3 Col 2     | Row 3 Col 3        |

To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators!

Vertical tableheaders are possible, too.

Heading 1 Heading 2
Heading 3 Row 1 Col 2 Row 1 Col 3
Heading 4 no colspan this time
Heading 5 Row 2 Col 2 Row 2 Col 3

As you can see, it's the cell separator before a cell which decides about the formatting: 

|              ^ Heading 1            ^ Heading 2          ^
^ Heading 3    | Row 1 Col 2          | Row 1 Col 3        |
^ Heading 4    | no colspan this time |                    |
^ Heading 5    | Row 2 Col 2          | Row 2 Col 3        |

You can have rowspans (vertically connected cells) by adding ::: into the cells below the one to which they should connect.

Heading 1 Heading 2 Heading 3
Row 1 Col 1 this cell spans vertically Row 1 Col 3
Row 2 Col 1 Row 2 Col 3
Row 3 Col 1 Row 2 Col 3

Apart from the rowspan syntax those cells should not contain anything else. 

^ Heading 1      ^ Heading 2                  ^ Heading 3          ^
| Row 1 Col 1    | this cell spans vertically | Row 1 Col 3        |
| Row 2 Col 1    | :::                        | Row 2 Col 3        |
| Row 3 Col 1    | :::                        | Row 2 Col 3        |

You can align the table contents, too. Just add at least two whitespaces at the opposite end of your text: Add two spaces on the left to align right, two spaces on the right to align left and two spaces at least at both ends for centered text.

Table with alignment
right center left
left right center
xxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxx

This is how it looks in the source: 

^           Table with alignment           ^^^
|         right|    center    |left          |
|left          |         right|    center    |
| xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx |

Note: Vertical alignment is not supported.

No Formatting

If you need to display text exactly like it is typed (without any formatting), enclose the area either with <nowiki> tags or even simpler, with double percent signs %%.

This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
The same is true for //__this__ text// with a smiley ;-). 

<nowiki>
This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
</nowiki>
The same is true for %%//__this__ text// with a smiley ;-)%%.

Code Blocks

You can include code blocks into your documents by either indenting them by at least two spaces (like used for the previous examples) or by using the tags <code> or <file>. 

This is text is indented by two spaces.
This is preformatted code all spaces are preserved: like              <-this
This is pretty much the same, but you could use it to show that you quoted a file.

Those blocks were created by this source: 

  This is text is indented by two spaces.
<code>
This is preformatted code all spaces are preserved: like              <-this
</code>
<file>
This is pretty much the same, but you could use it to show that you quoted a file.
</file>

Syntax Highlighting

DokuWiki can highlight sourcecode, which makes it easier to read. It uses the GeSHi Generic Syntax Highlighter – so any language supported by GeSHi is supported. The syntax uses the same code and file blocks described in the previous section, but this time the name of the language syntax to be highlighted is included inside the tag, e.g. <code java> or <file java>. 

/**
 * The HelloWorldApp class implements an application that
 * simply displays "Hello World!" to the standard output.
 */
class HelloWorldApp {
    public static void main(String[] args) {
        System.out.println("Hello World!"); //Display the string.
    }
}

The following language strings are currently recognized: 4cs 6502acme 6502kickass 6502tasm 68000devpac abap actionscript3 actionscript ada aimms algol68 apache applescript apt_sources arm asm asp asymptote autoconf autohotkey autoit avisynth awk bascomavr bash basic4gl batch bf biblatex bibtex blitzbasic bnf boo caddcl cadlisp ceylon cfdg cfm chaiscript chapel cil c_loadrunner clojure c_mac cmake cobol coffeescript c cpp cpp-qt cpp-winapi csharp css cuesheet c_winapi dart dcl dcpu16 dcs delphi diff div dos dot d ecmascript eiffel email epc e erlang euphoria ezt f1 falcon fo fortran freebasic freeswitch fsharp gambas gdb genero genie gettext glsl gml gnuplot go groovy gwbasic haskell haxe hicest hq9plus html html4strict html5 icon idl ini inno intercal io ispfpanel java5 java javascript jcl j jquery julia kixtart klonec klonecpp kotlin latex lb ldif lisp llvm locobasic logtalk lolcode lotusformulas lotusscript lscript lsl2 lua m68k magiksf make mapbasic mathematica matlab mercury metapost mirc mk-61 mmix modula2 modula3 mpasm mxml mysql nagios netrexx newlisp nginx nimrod nsis oberon2 objc objeck ocaml-brief ocaml octave oobas oorexx oracle11 oracle8 oxygene oz parasail parigp pascal pcre perl6 perl per pf phix php-brief php pic16 pike pixelbender pli plsql postgresql postscript povray powerbuilder powershell proftpd progress prolog properties providex purebasic pycon pys60 python qbasic qml q racket rails rbs rebol reg rexx robots roff rpmspec rsplus ruby rust sas sass scala scheme scilab scl sdlbasic smalltalk smarty spark sparql sql sshconfig standardml stonescript swift systemverilog tclegg tcl teraterm texgraph text thinbasic tsql twig typoscript unicon upc urbi uscript vala vbnet vb vbscript vedit verilog vhdl vim visualfoxpro visualprolog whitespace whois winbatch wolfram xbasic xml xojo xorg_conf xpp yaml z80 zxbasic

There are additional advanced options available for syntax highlighting, such as highlighting lines or adding line numbers.

Downloadable Code Blocks

When you use the <code> or <file> syntax as above, you might want to make the shown code available for download as well. You can do this by specifying a file name after language code like this: 

<file php myexample.php>
<?php echo "hello world!"; ?>
</file>
myexample.php
<?php echo "hello world!"; ?>

If you don't want any highlighting but want a downloadable file, specify a dash (-) as the language code: <code - myfile.foo>.

Embedding HTML and PHP

You can embed raw HTML or PHP code into your documents by using the <html> or <php> tags. (Use uppercase tags if you need to enclose block level elements.)

HTML example: 

<html>
This is some <span style="color:red;font-size:150%;">inline HTML</span>
</html>
<HTML>
<p style="border:2px dashed red;">And this is some block HTML</p>
</HTML>

This is some inline HTML

And this is some block HTML

PHP example: 

<php>
echo 'The PHP version: ';
echo phpversion();
echo ' (generated inline HTML)';
</php>
<PHP>
echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
echo '<td>'.phpversion().'</td>';
echo '</tr></table>';
</PHP>

echo 'The PHP version: '; echo phpversion(); echo ' (inline HTML)'; 

echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
echo '<td>'.phpversion().'</td>';
echo '</tr></table>';

Please Note: HTML and PHP embedding is disabled by default in the configuration. If disabled, the code is displayed instead of executed.

RSS/ATOM Feed Aggregation

DokuWiki can integrate data from external XML feeds. For parsing the XML feeds, SimplePie is used. All formats understood by SimplePie can be used in DokuWiki as well. You can influence the rendering by multiple additional space separated parameters:

Parameter Description
any number will be used as maximum number items to show, defaults to 8
reverse display the last items in the feed first
author show item authors names
date show item dates
description show the item description. If HTML is disabled all tags will be stripped
nosort do not sort the items in the feed
n[dhm] refresh period, where d=days, h=hours, m=minutes. (e.g. 12h = 12 hours).

The refresh period defaults to 4 hours. Any value below 10 minutes will be treated as 10 minutes. DokuWiki will generally try to supply a cached version of a page, obviously this is inappropriate when the page contains dynamic external content. The parameter tells DokuWiki to re-render the page if it is more than refresh period since the page was last rendered.

By default the feed will be sorted by date, newest items first. You can sort it by oldest first using the reverse parameter, or display the feed as is with nosort.

Example: 

{{rss>http://slashdot.org/index.rss 5 author date 1h }}

Control Macros

Some syntax influences how DokuWiki renders a page without creating any output it self. The following control macros are availble:

Macro Description
~~NOTOC~~ If this macro is found on the page, no table of contents will be created
~~NOCACHE~~ DokuWiki caches all output by default. Sometimes this might not be wanted (eg. when the <php> syntax above is used), adding this macro will force DokuWiki to rerender a page on every call

Syntax Plugins

DokuWiki's syntax can be extended by Plugins. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation:

2020/12/19 08:39

<< Newer entries | Older entries >>

1) , 3)
This is a footnote
2) , 4)
when the aspect ratio of the given width and height doesn't match that of the image, it will be cropped to the new ratio before resizing
start.txt · Last modified: 2021/01/05 17:31 by admin

Page Tools