Comment 12 for bug 380844

@Jiri: Great to hear that you will work on this!!

I fully agree with most points of the previous comment. I have an other idea to define anchors: so called "implicit anchors" could simply refer a slice of a heading. E.g. if there is a heading "1. My Nice Introductory Chapter" on MyPage, an valid anchor would be "MyPage#Intro". This works without a separate definition of the anchor, and would still be more robust than referring the full heading text. My idea is meant to supplement yours.

A heading with implicit anchor would not need to be marked somehow, nor should it appear in an anchor list button in the status bar (which is a nice idea for explicit anchors). Relating to your last point "Issues" I would change the foreground color of anchors to red if they are invalid or ambiguous (not unique). Invalid anchors would lead to the top of the page, ambiguous anchors to their first match.

Furthermore the command line interface could make use of anchors: zim <notebook> <page#anchor> would place the cursor to the target of the given anchor.

Open Issues:
* should an anchor match case-insensitive to make it even more robust? Case-sensitivity in titles may change, especially on English pages.