Don't link inline-code to anything if triple backticks are used.

This is useful if the code word is a keyword elsewhere, but is used
in a very local context, like a function parameter name.
Use triple backticks in generated markdown to avoid linking.

Attribute names and input options are code, but not keywords, even
though they might have the same string as keywords.
Create link to section with ambiguous link.
Remove newline before right-side hashes
Autocommit: libraries changed 2014-06-14-01:58:59
Update link map after macros have added content.
Terminate link correctly in footer
New left navigation.
Hard limit to 2 levels, do not include top level
Merge pull request #112 from dmitry84/master

New left navigation. (do not merge before confitrmation from Kevin)
Update JSON files from master branch of masterfiles.
Build JSON files for 3.7 content.
Hashes on right hand side of library elements to avoid double-linkage.
Support level 4 in the left navigation
Experimental - remove base_url
Merge pull request #113 from dmitry84/master

support 4 level in the left navigation and remve base_url
Use a regular expression to try to detect unresolved links.

The naive grep'ing for ][ produces too many false positives from
code blocks using arrays.
Include link to symas.com/mdb for LMDB keyword.
Print warning if unexpanded macros are encountered.
Use search instead of match to find unresolved links.

Warn for unexpanded macros.
If function has no attributes, replace macro with empty line.

Returning an empty list of lines from a macro function indicates
error and leaves the macro unexpanded for diagnostics.
Using function_attributes for functions with no parameters is not
wrong, so allow it by returning a single empty line.