This commit replaces a regular expression lookup with a simple
String/indexOf substring search.
It addresses pathological cases in which re-find took several
seconds to process contents of a blog post. An example of such
a case was a post with 16kB of nested HTML tags in a single line.
Add an enclosure tag to a post's metadata to let a podcast client
to deliver your audio content. It should look like this:
:enclosure [{:url "<full-url>"}]
Without the brackets, you end up with NullPointerExceptions, so
make sure you have that.
The URL should be the full location of where the audio file is
hosted (not relative), so for example:
:enclosure [{:url "http://www.example.com/01_episode_IV.mp3"}]
I created a bunch of markdown files with just the enclosure and
info about the audiobook with the following bash snippet:
find -L books -type f -iname "*mp3" | sort | while read mp3; do name=$(basename $mp3 .mp3); book=$(basename "$(dirname $mp3)"); echo "{:title \"$name\"\n:layout :post\n:tags [\"audiobooks\" \"$book\"]\n:enclosure [{:url \"http://clashthebunny.mason.ch/blog/$mp3\"}]}\n $book - $name\n==================" > md/posts/"$(date "+%Y-$name").md"; done
Each book was in it's own subdirectory of books:
books/Dracula/1-01-Chapter1_part01.mp3
books/Dracula/1-02-Chapter1_part02.mp3
books/Dracula/2-01-Chapter2_part01.mp3
Note that the above script requires the prefix of the episode to
be "date-like". It should be fairly easy to work out a way to get
your podcast up and running.
Add the book names to your rss-filters array, e.g.:
["Dracula" "Pride & Prejudice"]
Most podcasting clients support authentication, so just password
protect those directories and you should be good to go, even
if you are hosting copyrighted content.
For certain pages a key with a boolean value is added to the config map which can then be used in templates to determine if it is the page being rendered. Not all pages have this key and boolean value. Instead of adding additional keys for every page a new generic key, 'active-page', has been added and its value is the page name, ex: 'home', 'archives', 'tags', etc. The default value is 'home'. This key can then be used in any template to check the page which is currently being rendered.
As the filename extensions given by the render plugins are also used as
regex for replacing them with .html to generate URIs, the dot in front of
the extension was interpreted as an arbitrary character for the regex.
Also, it matched in the middle of a string. Now dots get quoted and a $
added to only match at the end of the filename.
Fix#16
1. create markup namespace to hold Markup protocol and its Markdown and
Asciidoc implementations.
2. Update compiler ns to iterate through available Markups and pass
Markup to fns that need Markup info.
3. Refactor compiler ns parse fns to be more granular.
