Table of Contents
Definition List Plugin
Compatible with DokuWiki
- 2022-07-31 "Igor" unknown
- 2020-07-29 "Hogfather" unknown
- 2018-04-22 "Greebo" unknown
- 2017-02-19 "Frusterick Manners" yes
This plugin adds support for definition lists to DokuWiki. Which is nothing more than creating two columns on a page: one column with the term, and another column with the definition. So it's a very simple plugin. Basically, the plugin adds some extra syntax to create the two columns.
It can be used with the Explain Plugin to make a glossary page for your site. How? You add some terms and definitions on a page, and you decide to call it a glossary. Then, with the explain plugin there is a configuration file that you upload via FTP, or your cPanel file manager (assuming Dokuwiki is running on a server and not locally).
There's no magic. You'll have to add the same information in two places: the explain configuration file, and the glossary page. The explain plugin provides a hover pop-up bubble for a term, which includes a definition and an option for an internal link. You point the internal link to whatever page you want to be the glossary where the definition-list-plugin-syntax is being used. The glossary can have the same definition that shows in the pop-up bubble (or whatever you want, for that matter).
I might not understand this fully, but people can just fix these paragraphs, or delete this line if I got it right. I won't be offended. Delete this paragraph. Do it.
The following image is a glossary using the definition list syntax. It's just a regular Dokuwiki page. The reason Tetrahydrocannabinol and THC appear red, is because the Explain Plugin is active. Hovering over these red words with the mouse will create a pop-up bubble with the contents of the conf/explain.conf file.
Well, it was my intent to show you a screenshot, but I can't upload a file.
A definition list is made up of one or more lines of the format shown below:
; term : definition ; term : definition
Note the two spaces at the beginning of each line.
The lines can be used in any order, the only requirements is that the first line must be one of the two lines commencing with a semi-colon “;” and the list is terminated by leaving a line completely blank.
In a slight change over standard DokuWiki lists, if you use new lines within the list the text on the new line is added to the end of the previous line when the definition list is displayed.
See the page in action
The plugin has two configuration settings. Where these configuration settings are, well, that's a mystery.
dt_fancy— on/off, default on. When on will float the term content to the left side of the wiki page, making a faux two column effect with the data content on the right.
classname— string, default “plugin_definitionlist”. The html classname given to the wrapping <dl> element, e.g. <dl class=“plugin_definitionlist”>. Can be used in conjunction with
userstyle.cssto vary how the definition is displayed. [ Forerunner for future enhancements providing multiple display styles with the plugin ].
The plugin is an evolution of the earlier plugins by Stephane Chamberland and Pavel Vitis.
At the time of original publication of this plugin there were two other definition list plugins:
Why use this plugin rather than one or other of the other two?
This plugin is very similar to definitions, it fixes a couple of problems with that plugin, other markup (e.g. formatting, links, etc) is allowed in the definition term and raw wiki data is properly filtered to maintain wiki security.
I like the simplicity of DokuWiki's markup. I believe this plugin keeps to that ideal, deflist is capable of handling more circumstances but I feel at the cost of some simplicity.
I have also added some configuration settings to allow more heavily styled lists and a choice of markup characters (it is set to MediaWiki's “
; term : definition” by default but can be changed to “
= term : definition” used by definitions). By turning
DL_FANCY on (default) the definition list will be output in a two column format, one column for the terms (
<dt>) and another for the definitions (
In 2013 the plugin was moved to Github, for easier collaborative development.
Recent changes in the Github repository:
- Upped version. by lpaulsen93 (2017-08-17 20:50)
- On ODT export assign dl CSS properties to table (to get a proper marg… by lpaulsen93 (2017-08-17 20:48)
- Improved layout: do not set margin for dl so it will get the same bot… by lpaulsen93 (2017-08-17 20:42)
- Fixed not working test code. by lpaulsen93 (2017-05-25 11:34)
- For querying CSS properties work on the current HTML stack of the ODT… by lpaulsen93 (2016-09-15 19:39)
- Minor code cleanup, upped version. by lpaulsen93 (2016-09-15 18:09)
- Merge pull request #2 from ssahara/dt_fancy by LarsGit223 (2016-09-15 17:59)
- Added/adjusted ODT support for ODT redesign branch. by lpaulsen93 (2016-09-04 19:10)
- 2008-08-13 — Update plugin URL, add OpenDocument renderer support, add generic rendering for unknown render formats
- 2005-09-21 — Style corrections, sources updated.
- 2005-09-17 — Released.
Please log all bugs and feature requests in the issue tracker on Github.
Blank line after list?
Can't create blank line after making a list.
please check this page (Korean) 2014/05/16
Syntax note; and anchor tag?
One caveat for usage and one suggestion:
CAVEAT The TERM line [;] need to be either right after the previous DEFINITION [;] or it needs to be separated by two blank lines.
If a single blank line is used, the markup is not triggered and the text, with the punctuation is shown.
This is no longer the case. It is important to make sure the intervening blank lines don't have a couple of blank spaces, which the editor might leave in place. These confuse the parser and result in it triggering dokuwiki's own preformatted code block
SUGGESTION What would be a nice addition to this plugin would be an ANCHOR tag wrapped around the TERM
— walter 2008-01-11 01:59