Rainer, thank you for your answer.
Am 13.11.2016 um 18:55 schrieb Dr Rainer Woitok: > ... > The good thing is that Bitbucket also correctly interprets header ident- > ifiers without the "markdown-header-" prefix in Markdown sources, so we > can keep the "markdown-header-" prefix out of the Markdown sources in > order to satisfy both, users reading the documentation via Bitbucket and > users running "make doc" and reading the documentation offline. This is > done -- among other things -- by script "DocFix.sh" which is executed > when you locally run "make nav" against the repository. I'm not sure if I understand this correctly. I tried a link without the "markdown-header-" part. Loading a Bitbucket Wiki page with this link I clicked the link - nothing happens (more precisely: it opens the correct Wiki page but at the top, not at the correct location (some header line)). The reason for this is certainly the HTML source code (sent by Bitbucket?) of the Wiki page displayed in the browser. Here the link without the "markdown-header-" prefix can't find its counterpart which has the "markdown-part-" prefix. > So the bottom line is: you can use either variant of header identifiers, > provided you run "make nav" afterwards (which you should do anyway). > But if you can't run "make nav" yourself, just don't use the "markdown- > header-" prefix at all. > This means: I can use both forms of the link when editing a MD file. Running DocFix.sh/make nav then removes the "markdown..." part. Loading the MD file into the repository brings me in the situation described in my previous phrase. The link target (I assume it is your "header identifier") in my case has the form <h2 id="markdown-header-...">...</h2> and is automatically created when rendering the Bitbucket Wiki MD page. It is not part of the MD file stored in the Wiki. I can't modify it. Could you please help me to understand where I am wrong? Sincerely WolfgangTh ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
