Nicolás Ojeda Bär

> I've started work on this, and opened a _very_ rough WIP PR, just to explore some directions and get the lay of the land, in #211. As I've poked...

> What's the purpose of the non-tyxml HTML backend apart from "does not use tyxml" ? Markdown can embed arbitrary content which is supposed to be quoted verbatim inside the...

> That's not particularly a problem no, it just mean using `Html.Unsafe` to build those parts (since the well-formedness guarantee clearly doesn't apply). Thanks, I didn't know about the `Unsafe`...

> After poking around a bit, I had the same thought as @Drup. If we are not opposed to the tyxml dependency in principle, I think it would appealing to...

Currently, `omd` is byte-based so it will take (and spit back out) arbitrary byte sequences, including UTF-8.

"Proper" UTF-8 support would enforce the encoding and also take that into account when case or other normalization is needed.

Strictly speaking, this is not a blocker. The current byte-based approach is good enough for the vast majority of cases. I'll see if we can plug in a UTF-8 decoder...

Actually we supported this before and I removed it because I thought it was not useful. But I'm planning to put it back since it turns out it is useful...

@jfrolich On further thought could you say a few words on what use-case you have in mind for this?

You mean `{e text}`, `{b text}` and `{i text}` ?