anchor.diff:  * need some sort of post_construct method for converter that receives document
     - inline convert methods can get called before init_pdf
     - monkeypatch?
  -* backport resize method from prawn-svg and use it in converter
  +* document nonfacing option more clearly (in README or theming guide)
   * create document that explains how built-in fonts are generated and what subsets are selected
     - I need instructions for myself so I know how to update/modify the fonts
     - document in theming guide what must be done to prepare fonts (old-style 'kern' table, optionally subset) (file issue!)
  +  - add note to README that Prawn will subset any fonts provided
   * consider supporting icon tag in parser to simplify how inline icons are stored; simpler use of passthrough content
   * cache stateless cell data resolved from theme (don't need to recalc each time; at least per table)
  -* autowidth on table doesn't work for multi-line content (prawn-table bases width calculation on normalized value)
  +* FILE ISSUE: autowidth on table doesn't work for multi-line content (prawn-table bases width calculation on normalized value)
     - table ends up being stretched even though it doesn't need to be
   * table logic: does the layout_table_caption have to be inside the table block? can we pre-calculate the actual width for the caption? does the table offer a callback we can use to keep the caption on the same page as the table?
   * introduce object to store/organize running content data and specs
   * QUESTION: should theme font handle hierarchical keys (either explicitly or implicitly)
   * need to support .canvas role on image so it isn't shrunk to fit inside top/bottom margins
     - perhaps .canvas, .canvas-x, .canvas-y
  +  - allow image to span width of page (role=canvas, role=canvas-x or role=canvas-y); if role is canvas or canvas-y, then it does not consume height
  +  - partially addressed by vw units
   * FILE ISSUE: when split source listing, add top padding to bounding box (or is it the line metrics top?)
     - perhaps this has to do with the a miscalculation in dry run when not starting from same y position?
  +  - separate theme control for listing vs literal block (and maybe source too)
   * should we print alt text if an error is caught when attempting to embed an image?
   * stroke and fill multi-page sidebar block (#259) and example block (#362)
   * support URL images in running content (need to delegate to resolve_image_path)
  
positive.code: * might be better to organize fragments of source chunks by lines (and pass that around) to simplify post-processing
  * support negative start value for list (#498)
    - need to count negative numbers in correct direction
  * margins/paddings at page boundaries are strange, fragile
  * implement margin collapsing (between blocks)
    - would eliminate need for negative padding for blockquote
  * SIMPLE: submit pastie theme for Rouge upstream
  * bw theme for CodeRay (or Rouge) to match output of Pygments bw
  * the nested? method on list isn't checking if nested inside a block inside a list
  * wrapped lines in source listing should be indented to account for line number gutter (#504)
  * add sample SVG to content of chronicles-example.adoc (we do already use one for title page)
  * inline images: allow built-in font family names for SVG to be remapped
  * inline images: should we be passing absolute image path in tag or something relative (or even a lookup id?)?
  * support zero-leading integers (use dedicated type like w/ roman numerals) in reversed order lists
  * large image runs into running footer (doesn't bottom margin need to be aligned with running footer height?)
  * should str_to_pt helper handle % and vw units?
  * allow style of visible link to be controlled by theme (similar to what we do in the manpage converter)
  * FILE ISSUE: should not wrap at formatting mark unless it is at a break opportunity
    - the problem here is that Prawn is allowing breaks at the boundaries of text fragments; it should only look at the contents
  * be more consistent with how examples are shown in theming-guide.adoc (do we show last segment only?)
  * allow top as alternative to margin_top for all elements on title page (#431)
  * swallowing exceptions! (any use of e.message in a string is dangerous)
  * allow ordered list marker to be prefixed by section number (a global setting?)
  
negative.code: * add /PageMode /UseOutlines
  * cli arguments
    - theme (pdf-style, pdf-stylesdir)
    - enable/disable writing pdfmark file
    - optimize-pdf
  * implement footnotes correctly (#73, #85)
  * flesh out outline more (in what way?)
  