Missing functionality in the formatter interface

[GoogleCodeExporter]

The formatter interface places some formatting functionality outside of the 
interface via VolumeContentFormatter. The implementation creates new formatters 
and passes to them information that the main formatter already has. This has 
resulted in:
 * an incomplete formatter interface
 * duplication of data structures
 * code that is difficult to maintain

Instead, the formatter interface should contain methods to add volume-templates 
and toc-data. This way, the formatter functionality would be in the formatter 
component only, and not also in the parser as it is now.

Separation between core formatting tasks and additional formatting tasks should 
probably be maintained, perhaps through different interfaces.

Original issue reported on code.google.com by joel.hak...@mtm.se on 21 Nov 2013 at 1:53

• Blocking: #70, #61, #62

[GoogleCodeExporter]

Original comment by joel.hak...@mtm.se on 21 Nov 2013 at 1:54

• Now blocking: #70

[GoogleCodeExporter]

Original comment by joel.hak...@mtm.se on 21 Nov 2013 at 1:54

• Now blocking: #61

[GoogleCodeExporter]

Original comment by joel.hak...@mtm.se on 21 Nov 2013 at 2:14

• Changed title: Missing functionality in the formatter interface

[GoogleCodeExporter]

Original comment by joel.hak...@mtm.se on 21 Nov 2013 at 2:14

• Added labels: Priority-High
• Removed labels: Priority-Critical

[GoogleCodeExporter]

Original comment by joel.hak...@mtm.se on 21 Jan 2014 at 8:17

• Now blocking: #62

[GoogleCodeExporter]

Original comment by joel.hak...@mtm.se on 27 Jan 2014 at 1:25

• Changed state: Started

[GoogleCodeExporter]

Original comment by joel.hak...@mtm.se on 28 Jan 2014 at 3:54

• Changed state: Fixed