Parameterized eml should now be compiled with Eml.compile in order to get a template. When writing eml that contains parameters, they will be rendered in a string representation. If the html reader encounters any of these strings while parsing html, they will be converted to strings. This means that it's now possible to write templates in html itself, if desired.
changed the interface of Eml.compile a bit
Instead of naming targets to read and write from dialects, name them languages. Dialects would imply that it's about some variant of eml, but that's obviously not the case. Simply calling them languages should cover what it's all about better.
replaced all dialect references with language in the readme
fixed bug where generated markup got their content and attributes reversed
added test for reading parameters from html
updated readme with new compile/write behaviour
updated readme with new pretty printing implementation
Major overhaul of the html writer: got rid of the arcane state macro's, lot's of fixes in attribute parameter handling and made sure templates are really a first class type in Eml. For example, parameters in templates can now even be bound to other templates. The bottom line is that it should be possible to use any Eml element anywhere, whether it makes sense or not.
Added an extra test for parameterized attribute rendering
fixed a bug when using templates as bounded values