public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Jennifer Bryan <jenny.f.bryan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to suppress title attribute in a CommonMark image link?
Date: Fri, 13 Oct 2017 11:16:46 -0700 (PDT)	[thread overview]
Message-ID: <d32e07da-beac-4710-b65e-7a02d9f76d43@googlegroups.com> (raw)
In-Reply-To: <20171013180518.GD27286@protagoras>


[-- Attachment #1.1: Type: text/plain, Size: 5646 bytes --]

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_strict/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]https://groups.google.com/d/msgid/pandoc-discuss/ 
> >     892c5a25-086a-4e19- 
> >     >   b4c1-8975cea8df0f%[4]40googlegroups.com. 
> >     >   For more options, visit [4][5]https://groups.google.com/ 
> >     d/optout. 
> >     > 
> >     >References 
> >     > 
> >     >   1. mailto:[6]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org 
> <javascript:> 
> >     >   2. mailto:[7]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org 
> >     >   3. [8]https://groups.google.com/d/msgid/pandoc-discuss/892c5a25- 
> >     086a-4e19-b4c1-8975cea8df0f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium= 
> >     email&utm_source=footer 
> >     >   4. [9]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]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org 
> <javascript:>. 
> >   To post to this group, send email to 
> >   [11]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >   To view this discussion on the web visit 
> >   [12]
> https://groups.google.com/d/msgid/pandoc-discuss/3dcce503-9815-4a2d 
> >   -aad9-b884f0e023aa%40googlegroups.com. 
> >   For more options, visit [13]https://groups.google.com/d/optout. 
> > 
> >References 
> > 
> >   1. javascript:/ 
> >   2. javascript:/ 
> >   3. 
> https://groups.google.com/d/msgid/pandoc-discuss/892c5a25-086a-4e19- 
> >   4. http://40googlegroups.com/ 
> >   5. https://groups.google.com/d/optout 
> >   6. javascript:/ 
> >   7. javascript:/ 
> >   8. 
> https://groups.google.com/d/msgid/pandoc-discuss/892c5a25-086a-4e19-b4c1-8975cea8df0f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer 
> >   9. https://groups.google.com/d/optout 
> >  10. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> >  11. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> >  12. 
> https://groups.google.com/d/msgid/pandoc-discuss/3dcce503-9815-4a2d-aad9-b884f0e023aa-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer 
> >  13. 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 pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d32e07da-beac-4710-b65e-7a02d9f76d43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 14372 bytes --]

  reply	other threads:[~2017-10-13 18:16 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 [this message]
     [not found]             ` <d32e07da-beac-4710-b65e-7a02d9f76d43-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-13 18:48               ` John MACFARLANE

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=d32e07da-beac-4710-b65e-7a02d9f76d43@googlegroups.com \
    --to=jenny.f.bryan-re5jqeeqqe8avxtiumwx3w@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).