Handling of link title syntax gets confused

[RichMorin]

I have discovered a situation where Earmark's handling of link title syntax gets confused. I've boiled it down to two very similar input strings. One succeeds; the other fails:

iex(1)> s = "The [Foo](/dash 'foo') page in \"bar\"\n" 
"The [Foo](/dash 'foo') page in \"bar\"\n"
iex(2)> Earmark.as_html(s)                            
{:ok, "<p>The <a href=\"/dash\" title=\"foo\">Foo</a> page in “bar”</p>\n", []}

iex(3)> s = "The [Foo](/dash 'foo') page (in \"bar\")\n"
"The [Foo](/dash 'foo') page (in \"bar\")\n"
iex(4)> Earmark.as_html(s)                              
{:ok, "<p>The <a href=\"/dash\" title=\"bar\">Foo</a> page (in “bar”)</p>\n", []}

In boiling down the example, I ran across assorted peculiar behavior, so fixing the failing case above may or may not resolve all the problems. However, it seems like a good place to start.

[RobertDober]

Which case is failing? I feel the output is correct.

See also

https://babelmark.github.io/?text=The+%5BFoo%5D(%2Fdash+%27foo%27)+page+(in+%5C%22bar%5C%22)

[RichMorin]

Sorry; I thought about pointing out the difference, but didn't get around to doing so. In the first case, the requested title (foo) is present in the HTML title attribute. In the second case, "bar" shows up as the title. The only difference in the input Markdown is the presence of parentheses around "<<in “bar”>>.

[RobertDober]

I apologize, as I am on leave I did not look at it as well as I should have.

I will take care of it as soon as I have time to do it correctly.

Thank you for your understanding.

[RichMorin]

No problem; enjoy your leave!

…

On Mar 16, 2019, at 2:02 AM, Robert Dober ***@***.***> wrote: I apologize, as I am on leave I did not look at it as well as I should have. I will take care of it as soon as I have time to do it correctly. Thank you for your understanding. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[RichMorin]

I edited my mix.exs file as follows and the problem seems to have gone away:

  { :earmark, override: true,
      git: "https://github.com/pragdave/earmark.git" },

[RobertDober]

@RichMorin I just released https://hex.pm/packages/earmark/1.3.2