X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/0d19125b229e7e0f545d309e62b95ac8689e4ab8..e71622d233660b5ba305d68e586d7d14ff2124e6:/doc/todo/internal_definition_list_support.mdwn

diff --git a/doc/todo/internal_definition_list_support.mdwn b/doc/todo/internal_definition_list_support.mdwn
index 9b2a1689c..f87dc653f 100644
--- a/doc/todo/internal_definition_list_support.mdwn
+++ b/doc/todo/internal_definition_list_support.mdwn
@@ -36,7 +36,7 @@ Then for us running the humongous [[koumbit wiki|https://wiki.koumbit.net/]], it
 
 If there are no objections to that concept, I may try to start coding patches. Otherwise this is really just a [[wishlist]]. --[[anarcat]]
 
-> 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.
+> 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]]
 
 > ----
@@ -49,4 +49,6 @@ If there are no objections to that concept, I may try to start coding patches. O
 >     =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]]
+> (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'ed plain text instead of invisible directives, 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]]