-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linkify regression #70
Comments
Confirming 12851a0 renders
<a href="https://golang.org">https://golang.org/</a>
<a href="https://golang.org">https://golang.org</a>
<a href="https://golang.org/">https://golang.org</a>
<a href="https://golang.org/">https://golang.org/</a> |
As I wrote in #74, I think this is also an undefined and ambiguous behavior about GFM. But there was nothing else to do, so I've changed goldmark to closer to GFM implementation . Instead of resolving this issue, you will see other strange rendering in GFM. [ a b http://www.google.com is not autolinked now(You can try this in github comment editor) Do you think this is a correct behavior? Can you explain why this is not autolinked? This is why I do not agree with 'defined by program works'. Behavior should be defined by specifications. |
@yuin I agree with you about the specification part. But in this case, the specification is obviously missing some important bits to handle the ambiguity introduced by GFM. That is unfortunate as everyone who implements this has had to have this discussion. To me, this is a simple as:
|
@bep, Yes you are right. [ a b http://www.google.com is not autolinked also looks obviously wrong.(But GFM works like it)
CommonMark defines that autolink should be surrounded with '<' '>' . So I think GFM autolink should be more defensive. GFM autolink parses URL aggressively(including most punctuations). This causes many problems like above. |
Produces
gohugoio/hugo#6649
The text was updated successfully, but these errors were encountered: