Chinese Study Resources

audio_video_resources - Consolidated video link content from another of my wikis

Stephan Hodges — Thu, 21 Jan 2010 04:36:16 -0600

Audio Resources

Links to good quality websites for audio resources. Many of these links are from personal bookmark collections. Will be adding some downloads here also.

Popup Chinese A great set of audio, transcriptions, notes, newsletter, etc.

Chinese Pronunciation Tool Also has other free online tools.

Video Study Resources

Here are links to various videos in Chinese about non-fiction topics. That is, these are not links to popular movies, etc. but rather to non-fictional items. The purpose would be to improve vocabulary within specialized areas by listening in context.

News

http://www.chinadaily.com.cn/

TV

http://beelinetv.com/chinese_tv/ 27 channels (2009/01/31) of free streaming TV in Chinese. “CCTV-9” is mostly an English Channel broadcast in China.

Daily Living

How to Manage Money
http://so.youku.com/search_video/q_%E9%B2%81%E8%B1%AB%E6%9C%89%E7%BA%A6 Interviews
http://so.youku.com/search_video/q_%E8%AE%BF%E8%B0%88 Interviews
http://so.youku.com/search_video/q_%E6%BC%94%E8%AE%B2/cateid_105 Presentation
http://so.youku.com/search_video/q_%E8%BE%A9%E8%AE%BA/cateid_105 Oral debate
http://so.youku.com/search_video/q_%E6%BC%94%E8%AF%B4/cateid_105 Talk

Animals

http://www.tudou.com/playlist/id/478861/ shows about animals
http://space.tv.cctv.com/act/schedule.jsp?scheduleId=SCHE1213585514597966 Nature
http://space.tv.cctv.com/act/platform/view/page/composePage.jsp?pageId=PAGE1213600890505980 discovery I
http://space.tv.cctv.com/act/schedule.jsp?scheduleId=SCHE1220529331100288 discovery

Geography

http://www.youku.com/playlist_show/id_328280.html shows how to be a great country
http://www.kjy.cn/class.asp?lx=big&anid=79 geography, but you have to create an account to log in

Culture

History

http://so.youku.com/search_video/q_%E5%8E%86%E5%8F%B2/cateid_105 History

Science

Experiments

China News (English)

http://www.chinadaily.com.cn/

How to Manage Money

http://v.youku.com/v_show/id_XMjEyNzU3NzI=.html

a title

http://v.youku.com/v_show/id_XNTc3NzU5NDA=.html

100 shows about animals

http://www.tudou.com/playlist/id/478861/

汉语学习网站

Chinese Study Websites (added English translation for index-ability)

FLV Players

YouTube Downloaders

Direct Link Download Sites

There are several sites that can convert a YouTube video link into a download link for you.

http://freeyoutubedownloader.net/
http://www.youtubecatcher.com/
http://metatuber.com/ Website: Give it your YouTube URL and it will return a download link.
http://www.downloadfromyoutube.com/ Website: Give it a URL, and it returns a download link
http://www.techcrunch.com/get-youtube-movie/
http://keepvid.com/

Articles

MakeUseOf Article on YouTube downloaders with several links and suggestions.
Mashable Article

Sofware

There are also downloadable software packages and plug-ins for Firefox, etc.

http://youtubedownload.altervista.org/ Downloadable software

Video Recovery

http://www.nirsoft.net/utils/video_cache_view.html This software is free, and will locate cached (stored in a temporary location) video files that you watch with your web browser. (If the link seems to never finish loading, try viewing the page source and scroll down to the download link in the source. When writing this, the direct download link was http://www.nirsoft.net/utils/videocacheview.zip

Misc

Lifehacker article on getting movies onto hard drive

start

Stephan Hodges — Mon, 04 Jan 2010 05:55:47 -0600

A Chinese Study Resources Wiki

Welcome to this site, and we hope you find it useful. Most content currently is oriented towards using Pleco, but additional content/resources are planned. Much of the Pleco user manual contents are copyright 2008 Pleco company

Main Areas

Pleco 2 User Manual (beta) removed because no longer relevant.
Vocabulary User contributed word lists.
Reader Texts Some texts that can be used with Pleco's Document Reader
Radical Dictionary for use with 2.0
Audio and Video Resources and links which can be used with web browsers or downloaded
Links and Chinese Study Resources
Blog Links Links to interesting (or boring in my case) blogs related to China or studying Chinese.

Guidelines

There is a special area called a ”playground” which you can use to practice editing.

Please feel free to send feedback or register and improve/change it yourself. Links are “no follow”, and we don't index with search engines, so there's no advantage to adding spam to the site.

ebooks.html

Andrew Thorburn — Thu, 14 May 2009 03:00:15 -0600

Texts

Here are some Chinese texts. They can be used with Pleco 2 software, or any other software with the text versions of the files.

If you came directly to this page, you can go to the main page start to see the table of contents for this wiki.

Notes

All files are encoded using UTF-8. For additional usage notes (if you need them), please click here.

How to Make Text Files

Notes on how to make your own reader files is here.

How to use the Pleco 2 reader software can be found here.

Experiment in OCR by Google

The Four Great Novels

These are the four great novels of Chinese Literature. For more information, see the Wikipedia entry here.

These were originally converted from HTML as I was interested in having them on my PDA, but with the coming of PlecoDict 2.0 and it's document reader I figured I'd put these out there for those that are interested.

Name	Name	Western	PalmDoc	Text
Simplified	Traditional	Title	Format	Format
红楼梦	紅樓夢	Dream of the Red Chamber	PalmDoc	Text
三国演义	三國演義	Romance of the Three Kingdoms	PalmDoc	Text
水浒传	水滸傳	Outlaws of the Marsh	PalmDoc	Text
西游记	西遊記	Journey to the West	PalmDoc	Text

Lu Xun's Short Stories and Essays

I apologize for not having English translations of the names, but these are not as well known, and I myself am unable to translate them. Please feel free to translate the titles if you are familiar with the work.

Download Links
Name	PalmDoc Format	Text Format	Title
二心集	PalmDoc	Text	title
而已集	PalmDoc	Text	title
坟	PalmDoc	Text	title
古籍序跋集	PalmDoc	Text	title
故事新编	PalmDoc	Text	title
花边文学	PalmDoc	Text	title
华盖集	PalmDoc	Text	title
华盖集续编	PalmDoc	Text	title
华盖集续编的续编	PalmDoc	Text	title
汉文学史纲要	PalmDoc	Text	title
集外集	PalmDoc	Text	title
集外集拾遗	PalmDoc	Text	title
集外集拾遗补编	PalmDoc	Text	title
呐喊	PalmDoc	Text	title
南腔北调集	PalmDoc	Text	title
彷徨	PalmDoc	Text	title
且介亭杂文	PalmDoc	Text	title
且介亭杂文附集	PalmDoc	Text	title
且介亭杂文末编	PalmDoc	Text	title
热风	PalmDoc	Text	title
三闲集	PalmDoc	Text	title
文序跋集	PalmDoc	Text	title
伪自由书	PalmDoc	Text	title
野草	PalmDoc	Text	title
准风月谈	PalmDoc	Text	title
中国小说史略	PalmDoc	Text	title
朝花夕拾	PalmDoc	Text	title

NPCR Flashcards

I've gone through and created flashcard lists for the vocab in each chapter of the NPCR books (currently from books 1 to 3), including supplementary words, and including traditional characters. These are intended to be used with PlecoDict, and are formatted as such.

Installation

Pleco 2.0

There's a new method for Pleco 2.0, and should be much easier to use. Simply download this XML file, copy it to your SD Card, and tell Pleco to import a UTF-8 XML File. It might take a while, but it will eventually work. I would not advise anything past chapter 50 at the moment, as they're not complete and are missing, for example, their traditional headwords. I may put up a file for Book 5 at some point, but I can't make any guarantees about it.

I have also categorized the cards according to chapter and book, so no more duplicate flashcards! If you see an error, please tell me. I've fixed the ones I can remember, but there are surely more.

The difference between the two master files is that the first is something Pleco can import on its own, if you really need it to. The second master file is designed to be used with the application I've provided below, which allows for easier creation of deeply-layered categories. It's not something that you need to worry about, by and large.

The XML file contains all the cards from lessons 1 - 53 (51+ aren't finished). Each word has been assigned a category related to the chapter it's in, and the text it appears in. That is, you'll see many words with categories like NPCR/NPCR Book 1/NPCR Chapter 1/NPCR Text One. What that means is that it appears in the NPCR series, in Book 1 Chapter 1, and in the first text. Books 1 - 4 have 3 texts: Text One, Text Two and Supplementary Words. I've also 'tagged' each flashcard with one of NPCR Text One, NPCR Text Two or NPCR Supplementary Words, depending on which of those it has appeared in. Note that many words will have two or three of these tags. The general idea I had for using them was that you would study, say, chapters 10 - 12 quickly, and you might not need to learn the supplementary words, so you would say “All words except those which are in the category NPCR Supplementary Words”. You can remove the categories if you prefer - all the flashcards are in other categories, so you won't loose anything by removing them.

Name	Download Format
Master File - Lessons 1 - 53	Text
Master File - Lessons 1 - 53 (Custom Categories)	Text
Converted Master File	XML
Transformation App	tar.gz
Transformation App Source Code	tar.gz

The two tar.gz files contain the program that I used to convert from the second Master File (with custom categories) to the XML file. They're not really intended for public use, as they're not well documented and are command-line only. The first archive contains everything you need to run the project, the second contains everything you need to build the project.

Pleco 1.0.3

There's a few choices here. The first, and the one that I use, is to do the following:

Synch the file NPCR.pdb to your PDA. Internal or External doesn't matter. It should show up in PlecoDict as NPCR, under C→E. If it doesn't, make sure you're using the correct version (currently 1.3), and if that doesn't work, then email me. Contact details below.
Put the stripped (NPCRStrip) files relating to the book(s) you want onto your SD card. It doesn't matter where, but I'd recommend some place very close to the bottom, like /[file] or /flashcards/[file]. These files are lacking definition, and use only traditional characters. They still show up as simplified in the testing though, don't worry!
Open up PlecoDict and CHANGE TO THE NPCR DICT. This is quite important, otherwise it will not work as expected.
Open the menu, select 'Manage Flashcards' and 'Import'. Enter the location of your flashcards (like /flashcards/[file], where you should replace [file] with the filename for the cards. Make sure the encoding is set as UTF-8.
Congratulations! You should now have all the flashcards you wanted. Be aware that there are some duplicates…
Note: While I prefer this way, it does mean that the flashcards can't be updated. If I make changes to the database you'll have to delete then re-import your flashcards, likely losing statistics in the process :(. Hopefully this will change when Pleco 2.0 arrives.

The other method is to not use the stripped file, but rather to grab one with the definitions already in it. I dislike this approach as it fills up your user-created DB with a huge number of flashcards, and has even more duplicates than the above method (and makes them harder to tell apart…)

Downloads

Name	Download Format

Master File (Chapters 1 through 41, full definitions, still a work in progress)	Text File
Dictionary File	PDB File
Stripped File for Lessons 1 to 38 (inclusive)	Text File
Stripped File for Book 1 (Lessons 1 to 14)	Text File
Stripped File for Book 2 (Lessons 15 to 26)	Text File
Stripped File for Book 3 (Lessons 27 to 38)	Text File
Merged File for Lessons 1 to 38 (inclusive)	Text File
Merged File for Book 1 (Lessons 1 to 14)	Text File
Merged File for Book 2 (Lessons 15 to 26)	Text File
Merged File for Book 3 (Lessons 27 to 38)	Text File

Classical Chinese Function Words

Flashcards: Text File

See the Pleco Forums Thread for more information.

Contact Details

First, I'm “ipsi” off of the PlecoDict forums (and most other forums, to be honest). I did this purely because I figured it'd be cool to wander around with these on my PDA. And I figured someone else might find them useful. I can be contacted at Temporarily unavailable for contact.

Also, the original PlecoDict thread about this stuff can be found here.

People interested in the UniAdso dictionary for Pocket PC can go here. NOTE This page has not been migrated into the wiki yet, but will be, so please don't bookmark that page.

ocr_by_google

Stephan Hodges — Fri, 13 Feb 2009 04:32:14 -0600

OCR by Google

This is an experiment to see how well Google will convert Chinese image text into readable text. You can read more about it by searching for “Convert Scanned PDF Documents to Text with Google OCR”. I also mention it on my blog at Poor Man's OCR

Chapter 16 : http://china.panlogicsoftware.com/ocr/Chapter16.pdf

syntax:local_syntax_ext - created

Stephan Hodges — Wed, 04 Feb 2009 04:27:50 -0600

Local Syntax Extensions

These are extensions to wiki syntax from plugins that have been added. There may be additional plugins not documented here.

This documentation has been copied from plugin sites, and therefore might not always be accurate.

Charting

Acknowledgements

The charter plugin bundles the pChart library and the Bitstream Vera font family. Credit goes to the respective authors.

Updates

Last updated: 2008/12/21

2008/12/21:
- Initial release

Syntax

Graph definitions are enclosed in <charter>...</charter> blocks. These blocks consist of two parts: parameters and data, which is separated from the parameters by an empty line. Parameters are name/value pairs separated by an =. Data has to be CSV formatted¹⁾. Example:

<charter>
param1 = value
param2 = value

1, 2, 3, 4, 5
2, 3, 4, 5, 1
3, 4, 5, 1, 2
</charter>

Using parameters, one can customize the generated graph, including size, title, type, colors and a multitude of other settings. You do not have to use all these settings though, the internal default values are very suitable for the generation of quick nice looking graphs already.

Below you can find a detailed list of all settings available. For examples of the application of these settings, please see the examples section further down.

Generated graphs are automatically saved as media files (PNG images to be exact) in the same namespace as the page they belong to. The chosen filename is either ”chart-<title>.png” or ”chart-notitle_<md5sum of the chart definition>.png”, depending on whether a title was defined for the chart or not. It thus is important to make sure to not have more than one equally titled chart per namespace.

Basic setup

These are the only settings you should set on any graph you generate.

Parameter	Description
title	The title of the graph to be displayed. Defaults to an empty string.
size	The size of the generated graph. Format is `<width>x<height>`. Defaults to 600px width and 300px height.
align	Alignment of the generated graph image. Can be either of `left`, `right` or `center`. Defaults to `left`.
type	Type of the graph to generate. Supported types are `line`, `lineFilled`, `cubic`, `cubicFilled`, `bar`, `barStacked`, `barOverlayed`, `pie`, `pie3d`, `pieExploded`. Defaults to `line`.

Font settings

All font settings must be formatted as <fontfile>@<size> where fontfile is the case sensitive name of a truetype font file located at charter/lib/fonts and size an unsigned integer denoting the size of the font in pixels.

Parameter	Description
fontTitle	The font to use for the title. Format is <fontfile>@<size>. Defaults to Bitstream Vera Sans Bold, size 10.
fontLegend	The font to use for legends and graph labels. Format is <fontfile>@<size>. Defaults to Bitstream Vera Sans, size 8.
fontDefault	The font to use for everything else (axis labels, tick labels, …). Format is <fontfile>@<size>. Defaults to Bitstream Vera Sans, size 8.

Color settings

All color settings except the gradients must be formatted as HTML RGB specification, e.g. #RRGGBB or #RGB. The leading # is optional.

Parameter	Description
bgcolor	Background color of the whole graph. Defaults to `#fafafa`
legendColor	Background color of legend box. Defaults to `#fafafa`
graphColor	Background color of the graph area. Defaults to `#ffffff` (transparent, not white!).
titleColor	Foreground color of the title. Defaults to `#000000`
scaleColor	Foreground color of the scale. Defaults to `#969696`
shadowColor	Color of the drop shadow. Defaults to `#c8c8c8` (suitable for pie charts, for line or curve shadows i recommend `#333333`)
bggradient	Gradient definition of the gradient to use as background for the whole chart. Format ist `<RGB>@<shades>` where `RGB` is once again an HTML RGB color definition and `shades` the number of color steps for the gradient to generate based on this color. Defaults to not set.
graphGradient	Gradient definition of the gradient to use as background for the graph area. Format ist `<RGB>@<shades>` where `RGB` is once again an HTML RGB color definition and `shades` the number of color steps for the gradient to generate based on this color. Defaults to not set.

Descriptional settings

In settings in which you refer to your declared data rows, you can do so by their number. The first row is 1, the second is 2 etc. This is important for labelSerie and graphLabels.

Parameter	Description
XAxisName	Sets the name of the X-Axis. Defaults to not set.
XAxisUnit	Sets the unit of the X-Axis, which gets automatically appended to each tick's labels. Defaults to not set.
XAxisFormat	Sets the format of the X-Axis. This can be any of `number`, `date`, `time`, `metric` or `currency` – see below for a description of those. Defaults to `number`.
YAxisName	Sets the name of the Y-Axis. Defaults to not set.
YAxisUnit	Sets the unit of the Y-Axis, which gets automatically appended to each tick's labels. Defaults to not set.
YAxisFormat	Sets the format of the Y-Axis. This can be any of `number`, `date`, `time`, `metric` or `currency` – see below for a description of those. Defaults to `number`.
labelSerie	Which data row to use for X-Axis tick labels. I recommend to always use the last row for this purpose, as the underlying pChart library seems to have an issue when using the first. Defaults not not set.
legendEntries	Descriptions of the plotted data rows to be used in the legend. Formatted as a comma separated list. Should be as many entries as there are rows plotted. Defaults to not set.
graphLabels	A comma separated list of labels you wish to add to your graph to let important data points stand out. Each item has to be of the format `<Serie-No>\|<X-Value>\|<Description>` where `Serie-No` is the number of the data row to which to attach the label (starting at 1), `X-Value` is the value on the X-Axis to which to attach the label (starting at 0, or if you defined a `labelSerie` the corresponding value from this row) and `Description` is the description to show in the label. Defaults to not set.

Documentation for axis formats:

number – used by defaults
time – amount of seconds will be displayed as HH:MM:SS
date – unix timestamp will be displayed as a date
metric – number that will be displayed with k/m/g units
currency – currency with custom unit

<cite>pChart documentation</cite> </blockquote>

Pie chart settings

Special settings only applying to pie charts. Boolean values can be true, on, 1 for true and false, off, 0 for false.

Parameter	Description
pieLabels	Boolean value setting whether to show labels in the pie chart. Defaults to `true`.
piePercentages	Boolean value setting whether to show percentages in the pie chart. Defaults to `true`.
pieExploded	Boolean value setting whether to draw the pie chart in exploded state. Defaults to `false`.

When drawing pie charts, there must be only one data serie, or two if one of them is declared as labelSerie.

Other settings

Boolean values can be true, on, 1 for true and false, off, 0 for false.

Parameter	Description
thresholds	Thresholds to plot into the diagram. Format is a comma-separated list of numeric values denoting the Y-value at which to draw the threshold. Defaults to not set.
palette	Color palette to use for the graph. Format is a string containing the filename of a palette file in `charter/lib/palettes` without the trailing `.txt` extension. Defaults to not set (and thus the use of the internal palette).
legend	Boolean value setting whether to show the legend. Defaults to `true`.
grid	Boolean value setting whether to draw the grid. Defaults to `true`.
alpha	Alpha value to use for drawing grid, bar charts and filled line and curve diagrams. Defaults to `50`.
dots	Size of circles to use to plot the given data points. Defaults to false (= not plotted).
shadow	Boolean value setting whether to draw shadows. Defaults to `false`.
ticks	Boolean value setting whether to draw ticks on the axis of the diagram. Defaults to `true`.
decimals	Decimals to display on axis labels and in pie chart percentages. Defaults to `0`.

Examples

Simple line chart

<charter>
title = Simple line chart
size = 700x230
align = center
bgcolor = #eeeeee
type = line
dots = 3
legendEntries = January, February

0,70,70,0,0,70,70,0,0,70
0.5,2,4.5,8,12.5,18,24.5,32,40.5,50
</charter>

Simple bar chart

<charter>
title = Simple bar chart
size = 700x230
align = center
alpha = 90
bgcolor = #eeeeee
type = bar
legendEntries = January, February, March
thresholds = 0

1,4,-3,2,-3,3,2,1,0,7,4
3,3,-4,1,-2,2,1,0,-1,6,3
4,1,2,-1,-4,-2,3,2,1,2,2
</charter>

Simple 3D pie chart

<charter>
title = Simple 3D pie chart
size = 400x300
align = center
bgcolor = #eeeeee
type = pie3d
labelSerie = 2
pieExploded = on

10,2,3,5,3
Jan, Feb, Mar, Apr, May
</charter>

Fancy cubic curve

<charter>
title = Fancy cubic curve
size = 700x230
align = center
type = cubicFilled
legendEntries = January, February
XAxisName = Items
YAxisName = Values
shadow = on
dots = 3
titleColor = #efefef
scaleColor = #efefef
shadowColor = #000
bggradient = #333@50
graphGradient = #666@50
fontLegend = VeraMono.ttf@8
graphLabels = 1|1|Point A, 2|3|Point B

100,320,200,50,63
50,432,79,153,234
</charter>

Keyboard Icons

This documentation section is only local to this wiki. Original documentation can be found at http://foosel.org/snippets/dokuwiki/keyboard

Syntax

Enclose the name of a key, or a combination of keys, separated by a dash (-), in a key tag, like this:

 <key>Key</key> or <key>C-x</key>

The text inside the key tag is split at the occurrences of - (dash).
Each part is trimmed (surrounding whitespace removed) and known shortcuts or key names are substituted. E.g. C becomes Ctrl, Left becomes ← etc.
The substitutions are language specific. So, e.g. in German, C becomes Strg and Del becomes Entf. Only English and German are supported at the moment. Feel free to write additional language files and send them in for inclusion.
If no substitution was found, the first letter is capitalized and special HTML chars are replaced with entities.
The substitution table only has key aliases that begin with a capital letter. So lower letters will not be substituted, only capitalized and, for example, C-c becomes Ctrl-C
If you want to express the dash (-) key, use Minus.
If you don't want any trimming, alias or language substitution, or capitalization, enclose your key name in single quotes.

Examples

Ctrl+Alt+Del to reboot. (<key>C-A-del</key>)
Ctrl+C to copy text to the clipboard. (<key>C - c</key>)
Ctrl+X to cut text and put it into the clipboard. (<key>C-x</key>)
Ctrl+V to paste text from the clipboard. (<key>C-v</key>)
Ctrl+Enter to insert a page break. (<key>C-enter</key>)
Ctrl+Shift+→) to select from current cursor position to end of a word. (<key>C-S-Right</key>)
Ctrl+Shift+← to select from current cursor position to the beginning of a word. (<key>C-S-Left</key>)
Ctrl+Page↑ to go one screen page up. (<key>C-PageUp</key>)
Ctrl+− (<key>C-Minus</key>)
any keyany key to exit. (<key>'any key'</key>)
Fn Function (Fn) Key

Additional Smiley images

DANGERRED
DANGERYELLOW
DELETERED
DELETEYELLOW
REDFIXME
YELLOWFIXME
NEWSTAR
NOTERED
NOTEYELLOW
TODOQUESTION
TODORED
TODOYELLOW
WARNINGRED
WARNINGYELLOW

¹⁾ the charter plugin only understands very basic CSV, with the only accepted delimiter being a comma and no support for quoted values exists

wiki:syntax - Move local syntax to new file

Stephan Hodges — Wed, 04 Feb 2009 04:27:48 -0600

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 the Edit this page button at the top or bottom of the page. If you want to try something, just use the playground page. The simpler markup is easily accessible via quickbuttons, too.

Additional (local site) syntax extensions can be found here.

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.

Alignment

This documentation section is only local to this wiki. Original documentation can be found at http://www.dokuwiki.org/plugin:divalign

Syntax

Align Left:

 #;;
 This would be aligned left.
 #;;

This would be aligned left.

Align Right:

 ;;#This is aligned right.;;#

This is aligned right.

Align Center:

 ;#;
 This is aligned center.
 ;#;

This is aligned center.

Align Justify (both left and right):

 ###
 **Justify this paragraph**\\
 Notice how you can still use other Wiki __syntax__ within the paragraph 
 being justified. The justification should automatically wrap when you change 
 the width of the browser. As shown in the syntax above, you can do it all 
 in one line or you can break it up. It just creates a big div around 
 it so you could nest other things in it whatever.
 ###

Justify this paragraph
Notice how you can still use other Wiki syntax within the paragraph being justified. The justification should automatically wrap when you change the width of the browser. As shown in the syntax above, you can do it all in one line or you can break it up. It just creates a big div around it so you could nest other things in it whatever.

Notes

The justify doesn't seem to work (at least in Firefox), but I think that's just because the browser doesn't support the style=“text-align: justify” or maybe I'm doing it wrong–who knows.
As shown in the syntax above, you can do it all in one line or you can break it up. It just creates a big div around it so you could nest other things in it… whatever.

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 Linknames, too: 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
Linknames, too: [[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 wiki:pagename or use an additional Title Text. Wiki pagenames are converted to lowercase automatically, special characters are not allowed.

Internal links are created by using square brackets. You can either just give
a [[pagename]] or use an additional [[pagename|Title Text]]. Wiki pagenames
are converted to lowercase automatically, special chars are not allowed.

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

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

For details about namespaces see wiki: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 behaviour can be enabled in the wiki: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>wiki:interwiki|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 homogenous 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 the config option security.checkloaduri but this is not recommended.
See 151 for more info.

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://www.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 ¹⁾ 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:

Images and other files

You can include external and internal wiki:images with curly brackets. Optionally you can specify the size of them.

Real size:

Resize to given width:

Resize to given width and height:

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:           {{http://de3.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.

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

If you specify a filename (external or internal) that is not an image (gif, jpeg, png), then it will be displayed as a link instead.

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

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

The same list but ordered
Another item
1. Just use indention for deeper levels
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

Smileys

DokuWiki converts commonly used emoticons to their graphical equivalents. More smileys can be placed in the smiley directory and configured in the conf/smileys.conf file. Here is an overview of Smileys included in DokuWiki.

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

Typography

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

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

Please note: These conversions can be turned off through a config option and a pattern file.

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 2 Col 2	Row 2 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 2 Col 2     | Row 2 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        |

Note: Vertical spans (rowspan) are not possible.

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 |

Non-parsed Blocks

You can include non-parsed 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 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.

To let the parser ignore an area completely (ie. do no formatting on it), 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.

See the source of this page to see how to use these blocks.

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 is the same like in the code block in the previous section, but this time the name of the used language is inserted inside the tag. Eg. <code 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: abap actionscript-french, actionscript, ada, apache, applescript, asm, asp, autoit, bash, basic4gl, blitzbasic, bnf, caddcl, cadlisp, cfdg, cfm, c_mac, c, cpp, cpp-qt, csharp, css, delphi, diff, div, dos, dot, d, eiffel, fortran, freebasic, genero, gml, groovy, haskell, html, idl, ini, inno, io, java5, java, javascript, latex, lisp, lua, m68k, matlab, mirc, mpasm, mysql, nsis, objc, ocaml-brief, ocaml, oobas, oracle8, pascal, perl, per, php-brief, php, plsql, python, qbasic, rails, reg, robots, ruby, sas, scheme, sdlbasic, smalltalk, smarty, sql, tcl, text, thinbasic, tsql, vbnet, vb, vhdl, visualfoxpro, winbatch, xml, xpp, z80

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
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.

Example:

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

Programming the Commodore 64: the Definitive Guide by timothy (2010/03/13 17:42)
Former Astronauts Call Obama NASA Plans "Catastrophic" by timothy (2010/03/13 16:35)
GPS Log Analysis Uncovers Millions In NYC Taxi Overcharges by timothy (2010/03/13 15:33)
Brinksmanship Continues In Google-China Row Over Censorship by timothy (2010/03/13 14:28)
Why Are Digital Hearing Aids So Expensive? by timothy (2010/03/13 13:30)

Embedding HTML and PHP

You can embed raw HTML or PHP code into your documents by using the html or php tags like this:

<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 <span style="color:red;font-size:150%;">inline HTML</span>

<p style="border:2px dashed red;">And this is some block HTML</p>

<php>
echo 'A logo generated by PHP:';
echo '<img src="' . $_SERVER['PHP_SELF'] . '?=' . php_logo_guid() . '" alt="PHP Logo !" />';
echo '(generated inline HTML)';
</php>
<PHP>
echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
echo '<td><img src="' . $_SERVER['PHP_SELF'] . '?=' . php_logo_guid() . '" alt="PHP Logo !" /></td>';
echo '</tr></table>';
</PHP>

echo 'A logo generated by PHP:'; echo '<img src="' . $_SERVER['PHP_SELF'] . '?=' . php_logo_guid() . '" alt="PHP Logo !" />'; echo '(inline HTML)';

echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
echo '<td><img src="' . $_SERVER['PHP_SELF'] . '?=' . php_logo_guid() . '" alt="PHP Logo !" /></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.

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:

Charter Plugin (syntax component) 2008-12-21 by Gina Haeussge
Renders customized charts using the pChart library
Note Plugin 2006-03-29 by Olivier Cortès / Eric Hameleers / Christopher Smith / Aurélien Bompard
Add Note/Important/Tip/Warning Capability (DIV+CSS box)
Discussion Plugin (threads component) 2008-08-08 by Gina Häußge, Michael Klier, Esther Brunner
Displays a list of recently active discussions
Pagelist Plugin 2008-08-08 by Gina Häußge, Michael Klier, Esther Brunner
lists pages
Linkback Plugin 2008-04-06 by Gina Haeussge
Enables/disables linkback features.
Folded Plugin – Inline 2008-08-13 by Fabian van-de-l_Isle
Enable inline folded text.
Syntax: ++title|folded content++
Box Plugin 2008-11-11 by Christopher Smith
Boxes with titles, colour and rounded corners.
Syntax: <box width class colours|title> ... </box|caption>
width, class, colours title & caption are optional.
The title can include some wiki markup, the box
contents can include almost any wiki markup.
S5 Slideshow Plugin 2008-06-20 by Andreas Gohr
Display a Wiki page as S5 slideshow presentation
Hidden Comment Plugin 2008-02-11 by Gina Häußge, Michael Klier, Esther Brunner
allows hidden comments in the wiki source
divalign 2008-03-29 by Jason Byrne
Add alignment
columns Plugin 2007-10-22 by Michael Arlt
Arrange information in multiple columns
Info Plugin 2008-09-12 by Andreas Gohr
Displays information about various DokuWiki internals
Filelist Plugin 2008-04-04 by Gina Haeussge
Lists files matching a given glob pattern.
Keyboard Syntax Plugin 2008-05-04 by Gina Haeussge
Marks text as keyboard key presses. Enhancements by Christopher Arndt.
Google Adsense Plugin 2007-08-14 by Dirk Moeller
Plugin to embed your Google Adsense code in your site. Based on code from Bernd Zeimetz and Terence J.

¹⁾ This is a footnote