Martin Mitáš

> Void elements as described in the HTML spec should not start a CommonMark HTML block, because void elements cannot have any content. But the HTML block is not just...

> I'm wondering whether this could be handled by modifying the spec as follows. > ``` > [Paragraph continuation text](@) is text that >+ is >- will be > parsed...

Maybe that is also key how to (re)define the continuation line if we decide to keep the current behavior. I.e. that it is more or less merging of two paragraphs,...

I would agree. What made me yesterday think it *might* be a hard break is that: 1. Paragraph may start with a hard break (at least cmark currently allows it):...

And also this inconsistency: ``` $ printf '\\\nfoo' | ./cmark foo $ printf ' \nfoo' | ./cmark foo ```

Why is the hard break allowed at the beginning of a paragraph but not at its end? Why is the hard break disallowed at the beginning of a paragraph if...

Thanks for the report. @boronine Alex, could you please put some light into this? What are the real bounds for the HPLuv colorspace? To be honest, to a substantial degree...

@boronine Can the application reasonably verify whether the RGB triplet falls into the valid subspace, either before the call or after it, e.g. by checking the resulted HPLuv triplet falls...

@boronine And what can app do if the transformation fails? I mean, if the caller "rounds" the saturation outside the range to 0 or 100, whatever is closer, is it...

For now, I've added the note. But I'll keep this issue open as it is imho still sub-optimal, as commented in https://github.com/hsluv/hsluv/issues/74. Most importantly, the expression "**may** generate invalid HPLuv...