[Booki-dev] changes to booki-zip format

[Aleksandar Erkalovic]

On Thu, Nov 19, 2009 at 9:45 AM, Douglas Bagnall
<douglas at paradise.net.nz> wrote:
> info.json TOC
> =============
>
> The TOC (Table of Contents) specifies navigation points with the book.
> It uses a nested structure, with less significant divisions being
> contained within the "children" attribute of greater division.
>
> The "TOC" element itself is a list of objects with the following
> structure:
>
>  {
>   "nav_id":   identifier,
>   "title":    division title (optional),
>   "url":      filename and possible fragment ID,
>   "type":     string indicating division type (optional),
>   "role":     epub guide type (optional),
>   "children": list of TOC structures (optional)
>  }
>
> *nav_id* is a unique identifier for this navigation point.  It uses a
>  different namespace than manifest identifiers and need have no
>  relationship to them.
>
> *title* is a free string giving the divisions title. It may be omitted.
>
> *url* points to the start of the division.  It should consist of a
>  filename as found in the manifest, optionally followed by a '#' and a
>  fragment identifier.

ah, did not think about this one. sure, link in the TOC can easily
point to some mirko.html#intro ?!
is it correct? kind of problematic for the html editor then. hmmmm.

-- 
 http://www.binarni.net/