---
if path of the resource processed by jinja2 contains non-ascii characters or if some template references some resource which contains non-ascii characters in its path hyde fails to generate site throwing jinjaUnicodeDecodeError.
So I replaced all regular strings I found in hyde sources with unicode ones. Now it generates site in described conditions correctly. All existing regression tests passed ok. So I think it is safe to include this changes into hyde.
Note that if you pull this request and some other requests introducing some new plugins youll have to look through their sources and replace str(...) occurences with unicode(...).
**update:**
Youll also have to remove .hyde_deps after applying this patch.
---
I have extended the starter layout with advanced topics, especially the sorter, grouper and tagger plugins. Content is updated. Navigation, code styling and text readability are improved.
---
Hi,
The support of Asciidoc block is gone in the new versions of hyde. This new code is inspired from the code that was present in the version 0.5.3 and the markdown filter already present in the current version. It is a pretty straightforward port of the previous code.
Regards,
Tony
---
I have extended the starter layout with advanced topics, especially the sorter, grouper and tagger plugins. Content is updated. Navigation, code styling and text readability are improved.
---
This is a plugin to use sphinx as a pre-processor for hyde. It lets you include sphinx files in the site source tree and have them processed and merged seamlessly into the rest of the site.
Im using it to do simple project websites for some of my python modules, having sphinx take care of auto-generated doc stuff and using hyde to handle the rest of the site. For example see http://packages.python.org/pyenchant/
---
Currently using some of plugins like JPEGOptimPlugin with equal type command line argument (for example --max=80) raises exception:
AttributeError: str object has no attribute append