issue-b745c7b1ada3a584dd4c4d50f72077c665cba2d2.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: add id links to all headings
desc: ""
type: :task
component: duk
release: v0.9
reporter: sva <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2013-12-17 21:19:08.878509 Z
references: []

id: b745c7b1ada3a584dd4c4d50f72077c665cba2d2
log_events: 
- - 2013-12-17 21:19:09.038397 Z
  - sva <sami.vaarala@iki.fi>
  - created
  - ""
- - 2013-12-17 21:50:17.305469 Z
  - sva <sami.vaarala@iki.fi>
  - commented
  - |-
    Subheadings with names like "Example" are a problem: should they get some
    odd looking names (like "example", "example_", "example__" etc)?
    
    Cumulating header names to get names like "foo_example", "bar_example"
    would cause very long ID names.
    
    Another approach is to take the given IDs as known names and then use
    automatic numbering underneath.  For instance, if h2 level id is
    "coroutines", the first h3 inside it would be "coroutines_1" and
    the third h4 inside that would be "coroutines_1_3".  These would not be
    stable IDs but wouldn't pollute the ID space randomly.
    
    Finally, headings could have multiple anchors.  They cannot have multiple
    IDs so it's perhaps better to use anchors anyway for autogenerated names.
- - 2013-12-18 15:20:05.283656 Z
  - sva <sami.vaarala@iki.fi>
  - assigned to release v0.9 from v0.8
  - ""
- - 2013-12-19 17:08:42.281594 Z
  - sva <sami.vaarala@iki.fi>
  - changed status from unstarted to in_progress
  - ""
- - 2013-12-19 22:50:02.604643 Z
  - sva <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - ""