well that looks like a bug to me, I’ll investigate and open an issue either in Earmark or EarmarkParser