See the Doe site.
``` Both names in the braces landed on the `a` element as attributes, in the order they were typed. No brace characters were left in the paragraph text. Pandoc broke the output line between the two attributes, and the quote above keeps that break. ## When link_attributes is turned off To see the braces without the extension, the next run was `pandoc -f markdown-link_attributes -t html lnt.md`. Its output holds non-ASCII characters, so it is shown here ASCII-normalized: pandoc wrote U+201C (left double quotation mark) where each value opens and U+201D (right double quotation mark) where it closes, and both appear below as a straight double quote. ```htmlSee the Doe site{target="_blank" rel="noopener"}.
``` Only the `href` stayed on the `a` element. The braces remained as plain words just past the closing ``, and the quote marks inside them changed shape. A count agrees: `pandoc -f markdown-link_attributes -t html lnt.md | grep -c 'target="_blank"'` printed 0, while the same pipe with `grep -c '_blank'` printed 1. ## Two commonmark reader runs With no extension switched on, `pandoc -f commonmark -t html lnt.md` returned: ```htmlSee the Doe site{target="_blank" rel="noopener"}.
``` Here too the braces stayed as text after the link, and the straight quotes came through as typed. That matches the spec rule quoted above: the link ends at its closing parenthesis. With pandoc's `attributes` extension switched on, the answer changed. `pandoc -f commonmark+attributes -t html lnt.md` returned: ```htmlSee the Doe site.
``` That is the same HTML the `markdown` run produced. A plain text count can mislead at this point. `pandoc -f commonmark -t html lnt.md | grep -c 'target="_blank"'` printed 1, since the leftover brace text holds those characters too. Matching the end of the address plus the attribute name splits the two cases: `pandoc -f commonmark -t html lnt.md | grep -c 'com" target='` printed 0; with `commonmark+attributes` instead, it printed 1. ## Braces on a reference definition In `lnt-ref.md`, the braces move onto a definition line: ```markdown See the [Doe site][doe]. [doe]: https://example.com {target="_blank"} ``` Pandoc's output for that file under `markdown` was: ```htmlSee the Doe site.
``` The `commonmark+attributes` run returned those same two lines. With the extension removed, `pandoc -f markdown-link_attributes -t html lnt-ref.md` folded the braces into the address: ```htmlSee the Doe site.
``` The space, the braces and the quote marks turned up inside `href` as `%20`, `%7B`, `%22` and `%7D`, and the element got no `target` attribute. Plain `commonmark` made neither a link nor a definition: ```htmlSee the [Doe site][doe].
[doe]: https://example.com {target="_blank"}
``` Both lines printed as paragraphs of text. That fits the spec's rule that no further character may follow the destination and title. The [reference link walkthrough](markdown-reference-links.md) covers label matching and the other definition rules. ## An a element typed by hand Another test file, `lnt-raw.md`, skips the braces and writes the element out: ```markdown See the Doe site. ``` Both readers returned the same lines, first via `pandoc -f markdown -t html lnt-raw.md` and then via `pandoc -f commonmark -t html lnt-raw.md`: ```htmlSee the Doe site.
``` Pandoc passed the tag through with its `target` attribute intact. A filtered listing, `pandoc --list-extensions=commonmark | grep raw_html`, printed `+raw_html`. Where typed HTML may sit in a file, and the blank lines around it, are explained in the [post on typed HTML](raw-html-in-markdown.md). For braces after an image, see the [image sizing post](markdown-image-size.md). ## Check a link's attributes with pandoc Pick the reader you mean to keep and test the file with it. 1. Run `cat lnt.md` and find where the braces sit. Here they came right after the link's closing parenthesis. 2. Convert it once, for instance through `pandoc -f markdown -t html lnt.md`, and check the line that opens the `a` element. 3. Count the attribute on the element itself. `pandoc -f markdown -t html lnt.md | grep -c 'com" target='` printed `1` here. Swap in `-f commonmark` and it printed `0`. 4. Count `rel` next. `pandoc -f markdown -t html lnt.md | grep -c 'rel="noopener"'` printed `1`, and under `-f markdown-link_attributes` it printed `0`. 5. Run the step 3 count on `lnt-ref.md` to check a reference link. It printed `1` under `commonmark+attributes` and `0` under plain `commonmark`. 6. Scan the `href` for `%7B`. That string appeared here when `markdown-link_attributes` read `lnt-ref.md`, and the braces had become part of the address. ## Where Sashmark fits If the v1 plan holds, Sashmark would let a person retype words right on the page in its rendered form. Saving would then run through the clean Round-Trip that is planned, with each untouched line coming back as identical bytes. Spotting whatever differs from your prior reading of the file would be the planned work of a Changes View, with git left out of that job. It is in development and has not been released. The app itself has no AI features. See the [planned features](/features), the [help pages](/help) and the [roadmap](/roadmap) for where each part stands. More at [sashmark.com](https://www.sashmark.com/).