Comment 20 for bug 380844

>> Unique id is a nice solution for implicit anchors. I should be generated
>> from the text of the heading, e.g. "Chapter One: To be or not to be?
>> → #chapter-one-to-be-or-not-to-be-3
>
> Nice! Am I right, that your mappings 1...4) will be applied to links too?
> So valid links are "Page#Chapter One" or Page#--To__bE--oR__nOt--

Valid link is "Page#chapter-one-to-be-or-not-to-be-3". However, the
Insert link dialog will provide list of headings and create the proper
id automatically when user hits OK.

When user types "Page#" the list of headings "Introduction, Chapter
One, ..." appears. The user selects "Chapter One" and hits OK button.
The source code contains "[[Page#chapter-one|mylink]]" not
"[[Page#Chapter One|mylink]]".

> I talked with a zim-using friend about anchors. Using # to separate link
> and anchor is intuitive. But #AnchorName to define an explicit anchor
> could interfere with sourcecode comments. It might lead to unwanted
> anchors like #!/bin/bash (at least in non-verbatim text blocks) . Near
> solutions could be #AnchorName# or [#Anchorname] which would also allow
> Spaces within anchor names.

Verbatim paragraph should be used for code blocks. Generally, it's the
only way how to avoid interferences.

> Another question (perhaps there is already a solution that I don't
> know): how do we refer the current page? With anchors it could be worth
> to have a syntax that does not include the pagename, like "+#chapter-
> one" or ".#chapter-one" to refer "chapter one" on the same page (ATM my
> favorite is the +#first).

Simply "#chapter-one".