Cœur
Cœur
Bah... I did multiple passes already for CodeEscaping... so I guess I can do it for reference-style links. Let me try to work on it for version 3.0.0.
Will release it this weekend.
I'm so sorry. As you noticed, I didn't work for a few months.
If someone wants to help, the goal is to recode `stringByAddingPercentEscapesUsingEncoding:` to work on a string which isn't recognized by `URLWithString:`
@uaremad, thank you, but it's a bit more complex: URL is multi parts (host `/` path `?` query `#` anchor), so it needs various escapes. And default Apple character sets...
Note that 4 spaces before a '+' sign could be interpreted as a code block in some popular Markdown implementations. So implementing this feature should not allow for an arbitrary...
Sublists with spaces (like here on github) are something contextual and might be tricky to parse using regex. See https://en.wikipedia.org/wiki/Chomsky_hierarchy. But then, some NSRegularExpressionAnchorsMatchLines together with look-ahead syntax might help...
Thank you @stephanheilner. As [DaringFireball is effectively supporting this combination](https://daringfireball.net/projects/markdown/dingus), I'll accept this workaround for branch 2.x. Note that branch 3.x will work differently, with traits.
Ah, well, sadly, it doesn't work for iOS 6 and macOS, so it's better to wait for TSMarkdownParser 3.0, as it will give proper support for it.
Yes, I'll release version 3 this weekend. Beware, it will have breaking changes.