Myron, Thankyou. As you know we are now using epub for OpenCPN documentation, having found it much easier to work with.
I am trying to find an easy way to create the hard coded pages that epub requires. Perhaps you have some suggestions.
From this TOC User Manual namespacee
https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:toc&s[]=user&s[]=manual
if I look at the page source we have all the information needed (plus the excess html)
This has been generated by Indexmenu and we are using this format
%%{{indexmenu>:opencpn#4|msort nsort nojs skipns=/(^opencpn:developer_manual$|^opencpn:supplementary_software$|^opencpn:supplementary_hardware$|^opencpn:user_corner$|^opencpn:opencpn_user_manual:charts:advanced_chart_work$|^opencpn:opencpn_user_manual:charts:pilot_charts$|^opencpn:opencpn_user_manual:editors$|^opencpn:opencpn_user_manual:edit_user_manual$|^opencpn:opencpn_user_manual:gallery_boats$)/}}%%
The relevant part of the page source looks like this:
<li class="open"><div class="li"><a href="/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:getting_started" class="indexmenu_idx_head">Getting Started</a></div>
Do you know of an easy way to get it formatted like this for epub?
[[opencpn:opencpn_user_manual:getting_started|Getting Started]]
Maybe IndexMenu would be able do that in it's output, by having a trigger that would show the path & title in that format? Then I could just highlight and copy the screen output and a special epub file would not have to be maintained through all the documentation changes. This list of pages could be made when we are going to publish.
What I actually need is something like to old dos "dir > filename.txt"
Who would I talk to about this possibility? It would dovetail nicely with epub.
BTW we have just released OpenCPN version 5.0 and everyone is hard a work answering user questions and fixing bugs, but the Dokuwiki documentation is still for v4.8.8. When the dust settles we are going to have to update the manual and hopefully package it differently.
One of the goals is to package separate smaller epub modules for documentation, and the second goal is to have a very stripped down "Basic Manual" that will ship with the software. To do this we need to place html on a github page (it will just be one, for the purpose of packaging). Is there a reasonable way to accomplish that from the Dokuwiki? IE convert it to html and then publish to github?
Thank you for all your help and advice. It has always been right on the mark!
PS I've been using Sigil, but I understand the best process is to use Calibre and clean up the html and then bring it into Sigil and use their tools for html and epub, including the Table of Contents feature. I've found what I think are recent Calibre changes to be more confusing but perhaps that will go away as I get back into it.