-
-
Notifications
You must be signed in to change notification settings - Fork 321
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
Complicated case with link titles with parenthesis #526
Comments
Martin Mitáš <[email protected]> writes:
I suppose the "matching parentheses" language isn't so clear.
We could say: "a sequence of zero or more characters between
an unescaped open parenthesis and the first unescaped close
parenthesis to follow."
I don't have a strong view about disallowing `(`.
… A link title, variant in parenthesis, is described as follows in the spec. 0.28:
> a sequence of zero or more characters between matching parentheses (`(...)`), including a `)` character only if it is backslash-escaped.
That makes me wonder whether allowing un-escaped `(` is good idea or whether it would be better to have some symmetry here.
Also cmark currently transforms
```
[link](url ((title))
```
into
```
<p><a href="url" title="(title">link</a></p>
```
Note the title contents having `(` not matched with any `)`, escaped or not.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#526
|
robinst
added a commit
to commonmark/commonmark-java
that referenced
this issue
Apr 12, 2019
robinst
added a commit
to commonmark/commonmark-java
that referenced
this issue
Apr 12, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A link title, variant in parenthesis, is described as follows in the spec. 0.28:
That makes me wonder whether allowing un-escaped
(
is good idea or whether it would be better to have some symmetry here.Also cmark currently transforms
into
Note the title contents having
(
not matched with any)
, escaped or not.The text was updated successfully, but these errors were encountered: