X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/890863679fea395172c247877579d391563c3b5e..fc4c1b7ec819cf8e73f2efba05606e575eaf47a5:/doc/plugins/contrib/sourcehighlight.mdwn?ds=inline

diff --git a/doc/plugins/contrib/sourcehighlight.mdwn b/doc/plugins/contrib/sourcehighlight.mdwn
index b34f41b3c..b48fd1a16 100644
--- a/doc/plugins/contrib/sourcehighlight.mdwn
+++ b/doc/plugins/contrib/sourcehighlight.mdwn
@@ -4,10 +4,18 @@ I have copied otl.pm and am wrapping source-highlight (why this instead of vim h
 version on 
 [my wiki](http://www.cs.unb.ca/~bremner/wiki/software/sourcehighlight.pm)
 
-In the tradition of publish early and often, this just supports java 
-at the moment. I will add more languages soon.
-You can add more languages by cutting and pasting the hook line; I want to add a configuration option to allow the user to specify.
+you must specify a highlight_lang=>"foo,bar" in your setup file.
+where foo and bar are the (source-supported) languages you want to
+highlight
+# Issues
 
-One outstanding problem is that I would like to have a link to the raw source; I'm not quite sure how to manage this at them moment.
+- I would like to have a link to the raw source; using will_render() and then copying the file 
+may work. 
+The discussion in [[plugins/contrib/texinfo]] seems relevant.
 
+- the common case of foo.c and foo.h breaks
+because they both generate page working/dir/foo. 
+It looks to me like ikiwiki is hardcoded to strip the extension in `pagename()` (IkiWiki.pm).
+This problem with sourcehighlight needs to be fixed before it is very useful.
 
+[[DavidBremner]]