© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
> 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-
Nice! Am I right, that your mappings 1...4) will be applied to links too?
So valid links are "Page#Chapter One" or Page#--
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.
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).