public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How to suppress title attribute in a CommonMark image link?
Date: Fri, 13 Oct 2017 11:48:53 -0700	[thread overview]
Message-ID: <20171013184853.GD32136@protagoras> (raw)
In-Reply-To: <d32e07da-beac-4710-b65e-7a02d9f76d43-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Hm.  Don't know what RMarkdown is doing with this.

+++ Jennifer Bryan [Oct 13 17 11:16 ]:
>   My problem is occurring at arm's length inside an R Markdown workflow
>   (.R or .Rmd --> .md --> .html). I guess there's something else we're
>   doing that causes ?URL encoding? of the image link. This is the pandoc
>   error I ultimately see at the conversion to html stage for the affected
>   image links:
>pandoc: Could not fetch fooabcdefghijklmnopqrstuvwxyz_files/figure-markdown_stri
>ct/unnamed-chunk-1-1.png%20%22fig:%22
>fooabcdefghijklmnopqrstuvwxyz_files/figure-markdown_strict/unnamed-chunk-1-1.png
> "fig:": openBinaryFile: does not exist (No such file or directory)
>Error: pandoc document conversion failed with error 67
>
>   On Friday, October 13, 2017 at 11:05:11 AM UTC-7, John MacFarlane
>   wrote:
>
>     +++ Jennifer Bryan [Oct 13 17 10:57 ]:
>     >   From my narrow view of the world, changing the CommonMark writer
>     to
>     >   match the rest here would be great!
>     Done.
>     >   In my real problem, the presence of this "fig:" makes image
>     links
>     >   vulnerable to breakage via the insertion of a hard line break at
>     the
>     >   space before "fig:". Therefore I have to also manipulate text
>     wrapping,
>     >   i.e. set --wrap=none or --wrap=preserve to protect the links.
>     I don't get that.  This is a perfectly valid image in
>     CommonMark:
>     ![](foo.png
>     "fig:")
>     >   On Friday, October 13, 2017 at 10:31:12 AM UTC-7, John
>     MacFarlane
>     >   wrote:
>     >
>     >     It's a kludge we use to distinguish images that should be
>     >     treated as figures.  You can turn off the extension
>     >     entirely using
>     >         -f markdown-implicit_figures
>     >     I can also change the CommonMark writer so that the "fig:"
>     >     prefix is removed, as it is in the other Markdown writers.
>     >     +++ Jennifer Bryan [Oct 13 17 09:44 ]:
>     >     >   Why does the title "fig:" get inserted into this image
>     link and,
>     >     more
>     >     >   importantly, how can I prevent that?
>     >     >   $ echo '![](foo.png)' | pandoc -f markdown -t commonmark
>     >     >   ![](foo.png "fig:")
>     >     >   It appears to be fairly specific to CommonMark, i.e. it's
>     not
>     >     there for
>     >     >   other flavours of markdown.
>     >     >   $ echo '![](foo.png)' | pandoc -f markdown -t
>     markdown_github
>     >     >   ![](foo.png)
>     >     >
>     >     >   --
>     >     >   You received this message because you are subscribed to
>     the
>     >     Google
>     >     >   Groups "pandoc-discuss" group.
>     >     >   To unsubscribe from this group and stop receiving emails
>     from
>     >     it, send
>     >     >   an email to [1][1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     >     >   To post to this group, send email to
>     >     >   [2][2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     >     >   To view this discussion on the web visit
>     >     >   [3][3][1]https://groups.google.com/d/msgid/pandoc-discuss/
>     >     892c5a25-086a-4e19-
>     >     >   b4c1-8975cea8df0f%[4][2]40googlegroups.com.
>     >     >   For more options, visit [4][5][3]https://groups.google.
>     com/
>     >     d/optout.
>     >     >
>     >     >References
>     >     >
>     >     >   1. mailto:[6][4]pandoc-discuss+
>     unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>     >     >   2. mailto:[7]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>     >     >   3. [8][5]https://groups.google.com/d/msgid/pandoc-discuss/
>     892c5a25-
>     >     [6]086a-4e19-b4c1-8975cea8df0f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=
>     >     email&utm_source=footer
>     >     >   4. [9][7]https://groups.google.com/d/optout
>     >
>     >   --
>     >   You received this message because you are subscribed to the
>     Google
>     >   Groups "pandoc-discuss" group.
>     >   To unsubscribe from this group and stop receiving emails from
>     it, send
>     >   an email to [10][8]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     >   To post to this group, send email to
>     >   [11][9]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     >   To view this discussion on the web visit
>     >   [12][10]https://groups.google.com/d/msgid/pandoc-discuss/
>     3dcce503-9815-4a2d
>     >   -aad9-b884f0e023aa%[11]40googlegroups.com.
>     >   For more options, visit [13][12]https://groups.google.com/
>     d/optout.
>     >
>     >References
>     >
>     >   1. javascript:/
>     >   2. javascript:/
>     >   3. [13]https://groups.google.com/d/
>     msgid/pandoc-discuss/892c5a25-086a-4e19-
>     >   4. [14]http://40googlegroups.com/
>     >   5. [15]https://groups.google.com/d/optout
>     >   6. javascript:/
>     >   7. javascript:/
>     >   8. [16]https://groups.google.com/d/
>     msgid/pandoc-discuss/892c5a25-086a-4e19-b4c1-8975cea8df0f@
>     googlegroups.com?utm_medium=email&utm_source=footer
>     >   9. [17]https://groups.google.com/d/optout
>     >  10. mailto:[18]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>     >  11. mailto:[19]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>     >  12. [20]https://groups.google.com/d/
>     msgid/pandoc-discuss/3dcce503-9815-4a2d-aad9-b884f0e023aa@
>     googlegroups.com?utm_medium=email&utm_source=footer
>     >  13. [21]https://groups.google.com/d/optout
>
>   --
>   You received this message because you are subscribed to the Google
>   Groups "pandoc-discuss" group.
>   To unsubscribe from this group and stop receiving emails from it, send
>   an email to [22]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [23]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [24]https://groups.google.com/d/msgid/pandoc-discuss/d32e07da-beac-4710
>   -b65e-7a02d9f76d43%40googlegroups.com.
>   For more options, visit [25]https://groups.google.com/d/optout.
>
>References
>
>   1. https://groups.google.com/d/msgid/pandoc-discuss/
>   2. http://40googlegroups.com/
>   3. https://groups.google.com/
>   4. javascript:/
>   5. https://groups.google.com/d/msgid/pandoc-discuss/892c5a25-
>   6. http://086a-4e19-b4c1-8975cea8df0f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org/?utm_medium=
>   7. https://groups.google.com/d/optout
>   8. javascript:/
>   9. javascript:/
>  10. https://groups.google.com/d/msgid/pandoc-discuss/3dcce503-9815-4a2d
>  11. http://40googlegroups.com/
>  12. https://groups.google.com/d/optout
>  13. https://groups.google.com/d/msgid/pandoc-discuss/892c5a25-086a-4e19-
>  14. http://40googlegroups.com/
>  15. https://groups.google.com/d/optout
>  16. https://groups.google.com/d/msgid/pandoc-discuss/892c5a25-086a-4e19-b4c1-8975cea8df0f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>  17. https://groups.google.com/d/optout
>  18. javascript:/
>  19. javascript:/
>  20. https://groups.google.com/d/msgid/pandoc-discuss/3dcce503-9815-4a2d-aad9-b884f0e023aa-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>  21. https://groups.google.com/d/optout
>  22. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>  23. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>  24. https://groups.google.com/d/msgid/pandoc-discuss/d32e07da-beac-4710-b65e-7a02d9f76d43-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>  25. https://groups.google.com/d/optout


      parent reply	other threads:[~2017-10-13 18:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 16:44 Jennifer Bryan
     [not found] ` <892c5a25-086a-4e19-b4c1-8975cea8df0f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-13 17:31   ` John MACFARLANE
2017-10-13 17:57     ` Jennifer Bryan
     [not found]       ` <3dcce503-9815-4a2d-aad9-b884f0e023aa-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-13 18:05         ` John MACFARLANE
2017-10-13 18:16           ` Jennifer Bryan
     [not found]             ` <d32e07da-beac-4710-b65e-7a02d9f76d43-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-13 18:48               ` John MACFARLANE [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171013184853.GD32136@protagoras \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).