From 74a8f50b47e759e3545c672ff2d78cedb2ce52a3 Mon Sep 17 00:00:00 2001 From: chrysn Date: Tue, 20 Mar 2012 12:56:52 -0400 Subject: note discount's definition list capabilities --- doc/todo/internal_definition_list_support.mdwn | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'doc') diff --git a/doc/todo/internal_definition_list_support.mdwn b/doc/todo/internal_definition_list_support.mdwn index f41f4d8a2..c5df74201 100644 --- a/doc/todo/internal_definition_list_support.mdwn +++ b/doc/todo/internal_definition_list_support.mdwn @@ -38,3 +38,15 @@ If there are no objections to that concept, I may try to start coding patches. O > Have you looked at the [[plugins/contrib/field]] plugin? This gives you the infrastructure, and all you need is to write a plugin that parses the definition list format. Then you could use [[plugins/contrib/getfield]], [[plugins/contrib/ftemplate]] and/or [[plugins/contrib/report]] to do what you like with the data. > --[[KathrynAndersen]] + +> ---- + +> with the recent inclusion of discount to the [[plugins/mdwn]] module, definition lists can be used by default (instead of, as with multimarkdown, after an option is enabled), and look like this: +> +> =Apple= +> Apple is a fruit. +> Apple is also a company. +> =Orange= +> Orange is a fruit. +> +> (indented with four spaces). this makes definition lists a bit more attractive for definition harvesting. personally, i'd prefer a solution that works from the markup instead of plugins, as it integrates more naturally in the flow of designing a document, even though a plugin for explicitly stating invisible facts certainly has its purpose too. (think [[!wikipedia RDFa]] here ;-) ) --[[chrysn]] -- cgit v1.2.3