Escape HTML also when type definition parsing fails.
Proper string parsing in default values and type definitions.

The strings can now contain the ] or } char without causing the
parsing to end at that point.  For example:

    @cfg {String} [foo="]"]
Generate full paths for images in guides

Suppose we're using JSDuck to generate guides from the following directory
structure:

somedir/
  guides.json
  guides/
    getting_started/
      README.md
      some-image.png
    nested/
      first_guide/
        README.md
        one.png
      second_guide/
        README.md
        one.png

In JSDuck's generated HTML, image tags in the Getting Started guide will point
to the correct path relative to the page (e.g.
'guides/guide_getting_started/some-image.png'). However, the nested guides will
specify the wrong paths to images: JSDuck will write
'guides/first_guide/one.png' instead of the correct
'guides/guide_nested_first_guide/one.png'.

This patch fixes the issue by generating the image's path based on the full
name of the guide, instead of using 'File.basename' to incorrectly crop the
path.
Merge pull request #286 from scottrobertwhittaker/fixImagePaths

Generate full paths for images in guides
Cheer to Scott in README.
Point download link in README to SourceForge.

Github no more provides hosting for downloads. So switching over
to SourceForge.net.
Depend on therubyracer beta8.

The offical 0.11.0 seems to have some problems compiling.
So stick with the latest beta instead.

For windows we also use the 0.11.0beta1, so that's ceartanly
a better option than defining 0.10.1 as dependency.
Switch back to therubyracer 0.10.

Let's stay on the 0.10.x until the problems with 0.11.x get resolved.
This time though, don't specify exactly 0.10.1 but a range of versions.

With the 0.11.x therubyracer is attempting to use the system libv8,
and you have to install the libv8 gem by yourself when the system doesn't
have the libv8 available.  Additionally the compilation of libv8 is
quite time-taking and on some systems (like those with old Python)
will fail.  So lets hope these things get sorted out.

Although that somewhat complicates the install on Windows, as for it
only a 0.11.x version is available - so I need to generate a special
gem depending on 0.11.x from which I'll then build the executable.
Automatically close unclosed HTML tags.

Fixes an old problem with some unclosed <b> or <div> messing up
the layout of docs.

In addition to automatically closing the tags, a warning gets printed.
Extract HtmlStack class from DocFormatter.
Implement --ignore-html option.

Allows for ignoring additional HTML tags which otherwise would get
closed down by the new automatic tag closing mechanism.

Useful for ignoring ExtJS preprocessor directives: <debug>, <locale>.
Fix HtmlStack#open? method.

A silly mistake.
Improve wording of 404 page.

Don't direct people right away to JSDuck issue tracker - most likely
it's just a fault of a broken link and it's the authors of the
documentation who should fix it.
Display title text on loading screen.

Instead of using hardcoded image with text "Sencha Docs".
Default to Object when no type specified by @return.

This fixes the issue of return value docs being completely missing
in case @return wasn't followed by {TypeDef}.
Remove WebKit restriction from --touch-examples-ui.

No more does using this option restrict viewing of inline examples
to WebKit based browsers.  This check is now moved over to
eg-iframe.html in Sencha Touch codebase.
Check circular dependencies before resolving @inheritdoc.

Otherwise the documentation inheriting process will run into infinite
loop.

For example the following code cause a problem:

    /**
     * @class
     * @extends B
     */
    A = {};

    /**
     * @class
     * @extends A
     */
    B = {c: 'd'};

That's fixed now.
Up version to 4.6.0.
Mention Timo Tijhof in README thanks list.
Fix markup conflict in builtin RegExp class docs.

The "|" is used as table cell separator and inside a table cell
needs to be escaped with HTML entity.