Fixed class methods with same selector as existing property.

Thanks to Jason Gavris!
Implemented better Xcode integration for warnings and errors. Closes #105.

By using special log format `--logformat xcode`, appledoc formats warnings and errors related to source files in a way that Xcode is able to catch them and display them in build results. Currently only warnings are using that format (there is no error log message related to source files).

*Implementation details:* Note that implementation required tweaking Cocoa Lumberjack source. Specifically, it required passing in original source code filename and line number to log message. Although logging macros pick up source file and line automatically through `__FILE__` and `__LINE__`, these belong to appledoc sources. But for Xcode warnings making sense, we need to write the file name and line of the context being parsed. To reuse existing macros, I added both values to DDMessage and additional class method to DDLog which needs to be called prior to logging. The method will simply store info to static vars. Then logging method will pick up stored values, write them to message and reset static vars. When emitting log messages, Xcode formatter will check if these values are set and emit specially formatted logs, otherwise it will revert to message only.

*Additional note:* Although I searched for all occurrences of `GBLogWarn` and `GBLogError` in the project and updated those that seemed relevant, some may have been left out - let me know about exact messages and I will check it. Also note that parsing code currently doesn't emit warnings, if something goes wrong, exceptions are raised, which doesn't log the file and line. Didn't take much time to go into this as these usually indicate parsing code needs to be refined.
Fixed Xcode integration warnings and errors full paths handling. Fixes #105.

To allow Xcode properly open the file after selecting the warning in build list, it requires full path to it in the output, so I had to add full path to GBSourceInfo and use that when generating Xcode compatible log.

Note that I had appledoc crashed inside `[GBLog logFormatterForLogFormat]` when using standard log formats. The problem was with sending the given format instance `lowercaseString` however in case numerical value was used, the actual instance was `NSNumber`. To compensate, additional check was added to make sure the instance is indeed a `NSString`. Strange no one reported this as I didn't touch this code since last pushing to GitHub (or everyone was hardly waiting for Xcode compatibility and are now using that mode :).

Also added `xcode` log format option to help output and increased build number to 701.
Added html so that all generated pages have the same header as Apples documentation.
Fixed some HTML5 stuff.
Addressing `&` and `&token;` issues when indexing documentation set, partially easing #107.

Note: unfortunately it wasn't possible to continue indexing remaining files after encountering an error - docsetutil takes path to docset bundle, not individual files. So all symbols in the offending file AND all symbols in subsequent files will not be indexed.

Also note that appledoc will log a warning and hence exit with code 1 in case it gets these errors! You'll probably want to use `--exit-threshold 2` or more if you're running from Xcode build script.

For the moment, the only "workaround" is to stay clear of using these symbols in your own documentation. If you're using third party libraries or frameworks containing these symbols and only running them through appledoc to get similar looking docs encountering issues, you can only pass it through `--create-html` phase. If you want to have it integrated in Xcode, then go ahead and experiment to see how much of it is usable...
Fixed method merging for cases when instance method is merged on a class method. Closes #90.

This was working when instance method was registered first and class method with the same name was merged on it later on. But it didn't handle the other ordering. Hopefully this will allow handling all cases. Note that there might still be cases when merging properties and class methods - keep in mind if the issue get's re-opened.

Also updated build number to 703.
Fixed typo in log message.
Updated readme file with new online documentation now hosted on the appledoc's home page.
Added support for availability comment.
Using @since or @available comment in a method description will generate a new section in the method doc. called "Availability". The content of that section will be the text following the @since or @available tag.
Updated Discount markdown parser to last version (2.0.9)
Added support for UTF8 documentation

Fix appledoc #122 ( https://github.com/tomaz/appledoc/issues/122 )
The issue was that the string sent to Discount was relying on the [str length] method which return the number of characters instead of returning the number of bytes in the UTF8 string. After that, the converted markdown string was converted back to obj-c string using ASCII encoding which was breaking everything.

- Add a test case for UTF8 string handling
Merge branch 'feature/html-template' of https://github.com/rastersize/appledoc
Added h2 style for general html documentation
Improved HTML template generation

- Improved the different templates with the standard appledoc header (merged from rasterize/appledoc).
- Added the projectCompany and projectName template variable to all template document
Added print style

Added a stylesheet to allow printing the doc.
Fixed a crash when trying to append a nil value.
Added support for excluding paths from the output.

This is useful if you only want to generate documentation for certain
sources but those sources depend on other sources that should not have
documentation generated for them.  With this feature, you add all
sources as input and exclude certain sources from output generation.  It
will hide warnings on excluded sources, not generate output for them,
but they will be used for merging with your included sources (eg.
inheritance etc.)
Merge pull request #133 from lhunath/master

Added support for excluding paths from the output. Use `--exclude-output` option for entering all paths that should be parsed, but excluded from generated output.

Although this is similar to `--ignore`, there's one important difference: Ignore option will simply prevent any parsing happening over specified files or folders, hence it will result in warnings in case symbols from these paths are referenced in documentation that gets parsed. Exclude parses specified files or folders, but it simply doesn't output them, therefore you get no warnings. It's somewhat slower on the other hand due to having to parse extra files.
Fixed dorset indexing for categories. Closes #120.

The problem was in tokens.xml files which used only class name when composing identifier strings for categories and their members.

Note: My quick testing confirms this working, but if anyone experiences issues with category members, let me know - either comment this issue or create a new one.