From: A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Breaking up image description into multiple lines in source file
Date: Fri, 23 Sep 2022 15:41:14 +0200 [thread overview]
Message-ID: <CAMwawgNJjZ=JB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ@mail.gmail.com> (raw)
In-Reply-To: <CAMwawgPSp=ZKiT31wsV-viJG6gWHLt=mHE++BtJa-YU9yaEYTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 3478 bytes --]
Hello,
I’d like to do the same for inline code. I’ve found that going from
`veryLongClassNameWhichShouldBreakALineInOutputFile`
to
`veryLongClassNameWhichShoul
dBreakALineInOutputFile`
Will actually introduce a space at the linebreak in the output, something
which I do not want.
Any ideas on how to break up long lines like that without compromising the
output?
Regards,
Amine
On Fri, 23 Sept 2022 at 12:54, A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> It works. Thanks.
>
> On Fri, 23 Sept 2022 at 12:23, Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
> wrote:
>
>> Thus (but it is not so pretty):
>>
>> ![Data binding button default conversion](
>> data-binding-button-default-conversion.png
>> ){#fig:data-binding-button-default-conversion}
>>
>> (Beware the curly brackets for the classes and attributes.)
>>
>> Le Friday 23 September 2022 à 11:52:00AM, A A a écrit :
>> > Hello,
>> >
>> > I have the following markdown:
>> >
>> > ![Data binding button default
>> conversion](data-binding-button-default-conversion.png)(#fig:data-binding-button-default-conversion)
>> >
>> > I’d like to break this up into multiple lines in the markdown source to
>> keep
>> > everything clean and organized. So I tried that:
>> >
>> > ![Data binding button default conversion]
>> > (data-binding-button-default-conversion.png)
>> > (#fig:data-binding-button-default-conversion)
>> >
>> > Unfortunately it looks like Pandoc doesn’t recognize the above as an
>> Image in
>> > the AST but rather just a string of text.
>> >
>> > How can I break up a long image description into multiple lines without
>> > compromising the markdown?
>> >
>> > Thanks for your consideration.
>> >
>> > Regards,
>> >
>> > Amine Aboufirass
>> >
>> > --
>> > 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]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To view this discussion on the web visit [2]
>> https://groups.google.com/d/msgid/
>> > pandoc-discuss/
>> > CAMwawgOpaV0jvJccC3zhnSWprWQ8d0qbvH1W8TRF1KObFYH9fA%40mail.gmail.com.
>> >
>> > References:
>> >
>> > [1] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>> > [2]
>> https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgOpaV0jvJccC3zhnSWprWQ8d0qbvH1W8TRF1KObFYH9fA%40mail.gmail.com?utm_medium=email&utm_source=footer
>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/pandoc-discuss/Yy2JG50GVYKtHDsA%40localhost
>> .
>>
>
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgNJjZ%3DJB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 7658 bytes --]
next prev parent reply other threads:[~2022-09-23 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 9:52 A A
[not found] ` <CAMwawgOpaV0jvJccC3zhnSWprWQ8d0qbvH1W8TRF1KObFYH9fA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-09-23 10:23 ` Bastien DUMONT
2022-09-23 10:54 ` A A
[not found] ` <CAMwawgPSp=ZKiT31wsV-viJG6gWHLt=mHE++BtJa-YU9yaEYTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-09-23 13:41 ` A A [this message]
[not found] ` <CAMwawgNJjZ=JB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-09-23 16:40 ` BPJ
[not found] ` <CADAJKhCYFW=k9fxM6eLM782V3+sQ7_X9eH_7LfxO69z=DwjONg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-09-26 14:44 ` A A
[not found] ` <CAMwawgOjpuNWqcFg7CAYansucXhp+F_mk2rdLCJ7K3-8Yzd_bQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-09-26 15:26 ` Bastien DUMONT
2022-09-27 9:34 ` A A
[not found] ` <CAMwawgMCNfawhZ6jegTyt9j1kCDeOj_EhJeeFREcbdyRRT1dUQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-09-27 11:50 ` Bastien DUMONT
2022-09-27 13:30 ` Daniel Staal
2022-09-26 15:24 ` Daniel Staal
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='CAMwawgNJjZ=JB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ@mail.gmail.com' \
--to=amine.aboufirass-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).