{
  "$type": "site.standard.document",
  "canonicalUrl": "https://frankhecker.com/2004/12/25/markdown-patch-for-link-id-bug/",
  "path": "/2004/12/25/markdown-patch-for-link-id-bug/",
  "publishedAt": "2004-12-25T07:46:00.000Z",
  "site": "at://did:plc:77mn3ult3b72tpvtqqva6tat/site.standard.publication/3mpfmfpu4u72n",
  "tags": [
    "blosxom"
  ],
  "textContent": "_UPDATE 2023-03-27: This page is obsolete, as it refers to a prior version of this blog.  However, it may be of historical interest._\n\nIn using [Markdown][] I found one problem, one I’m surprised hasn’t been reported before.  (I looked through the [Markdown mailing list archive][Markdow02] briefly, but didn’t see anything on this; perhaps people consider the current behavior a feature, not a bug?)\n\nI make extensive (really, almost exclusive) use of reference-style links, and noticed problems when I word-wrapped my paragraphs, so that the resulting text looked something like the following:\n\nIn both the above cases Markdown 1.0 doesn’t recognize the presence of a link.\n\nThe fix is pretty simple (I think): Just convert newlines in the link id to spaces before checking to see if a given link id has been defined; see my [Markdown 1.0 patch][] for the diffs from Markdown 1.0.  Note that the bug is still present in the [Markdown 1.0.1][] release, so I’ve made a [Markdown 1.0.1 patch][] available as well.\n\n[Markdown 1.0 patch]: /blosxom/plugins/Markdown-10-link-id.patch \"Markdown 1.0 patch for link ids wrapped across two lines\"\n[Markdown 1.0.1]: http://daringfireball.net/2004/12/markdown_101\n[Markdown 1.0.1 patch]: /blosxom/plugins/Markdown-101-link-id.patch \"Markdown 1.0.1 patch for link ids wrapped across two lines\"\n[Markdown]: /blosxom/markdown\n[Markdow02]: http://six.pairlist.net/pipermail/markdown-discuss/",
  "title": "Markdown patch for link id bug"
}