Christian Neumanns

> consider introducing a precedence modifier Good point. > I imagine that ultimately the nodes tree will be something like: ``` -+- [doc + +- [metadata +- [options/settings + ......

> inability to use images stored on the web, or provide links that use relative paths, or protocols others than those accepted by PMLC Fixed in version 3.0.0. Moreover, a...

This bug appears whenever a node has more than one attribute starting with `html_`, e.g. [div (html_a=a html_b=b) ] The bug was located in [pp-libs](https://github.com/pdml-lang/pp-libs) (not in PMLC), and has...

> Are the pp-libs a left-over from PPL? No > or just some custom helper libraries? pp-libs are general purpose libraries used in PDML, PML, and other projects. They were...

> I hope the above helped defining the "general problem", which has more to do with the heritage of lightweight markup syntaxes, and how this might affect end users expectations...

Bug fixed in version 4.0.0. Not closed, but label changed from `Bug` to `Enhancement` because of the suggested list enhancements.

I changed the title from "HTML Attribute Crash Error" to "List Enhancements". We should open a new issue "List Enhancements", copy/paste relevant comments from this issue, and then close this...

> We need either: > > 1. A new parameter for the PMLC p2h option, allowing end users to bypass the CSS-copying stage by having PMLC simply link to the...

> Ideally, end users should be able to have total control over individual CSS files, both in terms of which ones get just linked and which ones are also copied...

> I like your proposal Thanks. > But how is PMLC going to validate a CSS file? PMLC does not validate CSS files. > It's the responsibility of the user...