Hi Rainer,

I tested you script.  I see two caveats that needs to be solved.

1) You append all links by .html. This might be necessary for a standalone 
version. But it breaks the wiki if I commit the changes to the Wiki 
repository. The Bitbucket wiki seems to escape on the missing extension, 
kicking in the Markdown compiler with the *.md version of the filename. 

It's a bit of a pitty, becaue the automated navigation menu and sanitizing 
actions would be quite nice to have. Therefore I would appreciate a solution 
that solves that conflict. 

2) You dump all results right between the source files. This is voodoo from 
the old days ;) Today we do out of source builds. It would be nice to have a 
configurable target path that includes all html files as well as all images. 

This is not just for esthetic reasons or to keep you busy. As compiling the 
documentation needs Python, an additional Python package and a shell, it would 
be quite inconvenient to force this in the normal build process. Therfore I 
would like to commit the ready made offline documentation in the source 
repository. By that installation simply has to copy it into the correct 
location without bothering anyone to install Python or to fight with a Widows 
Shell.

We do the same for the icons already, because creating the icons needs 
Inkscape and I don't want to tell everyone to install Inkscape.


Maybe for later improvement: An"up" link next to each sub-heading would be 
quite convenient, too.

Thanks for the work

Oliver


Am Freitag, 8. April 2016, 18:38:27 schrieben Sie:
> Oliver,
> 
> On Friday, 2016-04-08 15:17:02 +0200, you wrote:
> > ...
> > afaik BitBucket has no mechanism to fork the Wiki repository. As it is
> > publicly accessible for read and write it's not really necessary.
> 
> Ok.  Meanwhile I've managed to push the following  two changesets to the
> repository:
> 
> 2ac33e8afe33 2016-04-07 15:29:41 +0200 Rainer@tablet
> 
> Make the "Markdown" files usable locally:
> 
> 1. Add an ".hgignore" file so the "*.html" files as well as the "*.time"
>    files used by "make" are ignored.
> 
> 2. Remove old script "Markdown.pl" dating back to 2004 which no longer
>    is up to the task due to the use of various more recent extensions to
>    the "Markdown" language.
> 
> 3. Add makefile "Makefile" plus the three scripts "DocFix.sh",
> "HtmlMake.py", and "NavBar.sh" used by it.
> 
> 4. Add file "README.txt".
> 
> f18a6e9f39fc 2016-04-08 17:52:10 +0200 rainer.woi...@gmail.com
> 
> Minor modifications to file "README.txt":
> 
> - Specify a minimum version for "Markdown".
> 
> - Add two remarks about committing the changes introduced by running
>   the "make" command.
> 
> - Minor other editorial changes.
> 
> (Sorry for the   "Rainer@tablet" email address  in the  first changeset.
> But for my local repositories it's normally more interesting on what box
> I did a change than what my email address is :-)
> 
> Please clone locally, read file "README.txt :-),  investigate the script
> files, test thoroughly, and contact me, if you find any problems.
> 
> Sincerely,
>   Rainer


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532
_______________________________________________
Qlandkartegt-users mailing list
Qlandkartegt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users

Reply via email to