From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Breaking up image description into multiple lines in source file
Date: Tue, 27 Sep 2022 11:50:03 +0000 [thread overview]
Message-ID: <YzLjazFN3XiFNy7X@localhost> (raw)
In-Reply-To: <CAMwawgMCNfawhZ6jegTyt9j1kCDeOj_EhJeeFREcbdyRRT1dUQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
So you want the inline to be hard-wrapped in the input md file, but not necessarily in the output, the only problem being that Pandoc converts the newline as a space in the output file? I fear that you have to use a filter suppressing all SoftBreaks between RawInlines in the AST, so that you could use the following syntax:
`veryLongClassNameWhichShouldBreak`
`ALineInOutputFile`
You could also restrict this behaviour to some spans:
[`veryLongClassNameWhichShouldBreak`
`ALineInOutputFile`]{.nospace}
In that case, you could also remove all spaces from RawInlines inside some spans, removing the need to split the RawInline in two objects:
[`veryLongClassNameWhichShouldBreak
ALineInOutputFile`]{.nospace}
However, given the sample class name you provide, I am not sure to understand your intent correctly.
Le Tuesday 27 September 2022 à 09:34:15AM, A A a écrit :
> To Bastien:
>
> Would splitting the inline code in two inlines be acceptable for you?
>
> No, because a new line in the source won’t necessarily coincide with a new line
> in the rendered output.
>
> To Daniel:
>
> You want to soft-wrap text that is longer than a specified length, not hard
> wrap it.
>
> I disagree. Most programming and markup languages typically have strict
> conventions for hard wrapping. The reason for this is quite simple, as you
> mention yourself, soft wrapping is viewer dependent, and hard wrapping is not.
>
> My one thought on that would be to put in some zero-width spaces at
> acceptable wrapping points.
>
> Interesting, how can I do that in Vim?
>
>
>
> On Mon, 26 Sept 2022 at 15:26, Bastien DUMONT <[1]bastien.dumont@posteo.net>
> wrote:
>
> Would splitting the inline code in two inlines be acceptable for you?
> `veryLongClassNameWhichShouldBreak`\
> `ALineInOutputFile`.
>
> Le Monday 26 September 2022 à 02:44:32PM, A A a écrit :
> > You can always break the line before and after the code span.
> >
> > I’m aware of that. My question is about how I can break the line within
> the
> > code span.
> >
> > Do you really have inline code spans, let alone class names, which
> are
> > longer than ca 70-80 characters
> >
> > I just happen to be using 78 characters as maximum column count in my
> source
> > file in Vim. Different situations arise where the inline code needs to be
> > broken up into multiple lines. Long file paths, inline code that occurs
> at the
> > end of a line, long class names or commands exceeding 78 characters, you
> name
> > it.
> >
> > In such a case I would express things differently so that I can use a
> code
> > block
> >
> > I don’t like that reasoning at all. Long inline code can and will occur
> in a
> > variety of use cases. Just because one can circumvent the problem by
> replacing
> > with a code block doesn’t mean they should. Please trust that for the
> purposes
> > of my question I really do need inline code and really do need to break
> it up
> > at the end of a line.
> >
> > I would be very surprised if this wasn't supported in the current
> > implementation of Pandoc's Markdown.
> >
> >
> >
> >
> > On Fri, 23 Sept 2022 at 16:40, BPJ <[1][2]bpj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org> wrote:
> >
> > You can always break the line before and after the code span. Do you
> really
> > have inline code spans, let alone class names, which are longer than
> ca
> > 70-80 characters, or very short lines? In such a case I would express
> > things differently so that I can use a code block. Or is it in a
> table? You
> > can use code blocks in a grid table.
> >
> > Den fre 23 sep. 2022 15:42A A <[2][3]amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> skrev:
> >
> >
> > 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 <[3][4]
> amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > wrote:
> >
> > It works. Thanks.
> >
> > On Fri, 23 Sept 2022 at 12:23, Bastien DUMONT <[4]
> > [5]bastien.dumont@posteo.net> 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][5][6]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> .
> > > To view this discussion on the web visit [2][6]https://
> > [7]groups.google.com/d/msgid/
> > > pandoc-discuss/
> > > CAMwawgOpaV0jvJccC3zhnSWprWQ8d0qbvH1W8TRF1KObFYH9fA%[7]
> > [8]40mail.gmail.com.
> > >
> > > References:
> > >
> > > [1] mailto:[8][9]
> pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > > [2] [9][10]https://groups.google.com/d/msgid/
> pandoc-discuss/
> > CAMwawgOpaV0jvJccC3zhnSWprWQ8d0qbvH1W8TRF1KObFYH9fA%[11]
> 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 [10]
> > [12]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [11]https://
> > [13]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 [12][14]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [13][15]https://
> groups.google.com/
> > d/msgid/pandoc-discuss/
> > CAMwawgNJjZ%3DJB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ%[16]
> 40mail.gmail.com.
> >
> > --
> > 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 [14][17]pandoc-discuss+unsubscribe@googlegroups.com.
> > To view this discussion on the web visit [15][18]https://
> groups.google.com/d/
> > msgid/pandoc-discuss/
> > CADAJKhCYFW%3Dk9fxM6eLM782V3%2BsQ7_X9eH_7LfxO69z%3DDwjONg%[19]
> 40mail.gmail.com.
> >
> > --
> > 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 [16][20]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [17][21]https://
> groups.google.com/d/msgid/
> > pandoc-discuss/
> > CAMwawgOjpuNWqcFg7CAYansucXhp%2BF_mk2rdLCJ7K3-8Yzd_bQ%[22]
> 40mail.gmail.com.
> >
> > References:
> >
> > [1] mailto:[23]bpj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org
> > [2] mailto:[24]amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> > [3] mailto:[25]amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> > [4] mailto:[26]bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org
> > [5] mailto:[27]pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [6] [28]https://groups.google.com/d/msgid/
> > [7] [29]http://40mail.gmail.com/
> > [8] mailto:[30]pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [9] [31]https://groups.google.com/d/msgid/pandoc-discuss/
> CAMwawgOpaV0jvJccC3zhnSWprWQ8d0qbvH1W8TRF1KObFYH9fA%40mail.gmail.com?
> utm_medium=email&utm_source=footer
> > [10] mailto:[32]pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [11] [33]https://groups.google.com/d/msgid/pandoc-discuss/
> Yy2JG50GVYKtHDsA%40localhost
> > [12] mailto:[34]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [13] [35]https://groups.google.com/d/msgid/pandoc-discuss/
> CAMwawgNJjZ%3DJB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ%40mail.gmail.com?
> utm_medium=email&utm_source=footer
> > [14] mailto:[36]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [15] [37]https://groups.google.com/d/msgid/pandoc-discuss/
> CADAJKhCYFW%3Dk9fxM6eLM782V3%2BsQ7_X9eH_7LfxO69z%3DDwjONg%40mail.gmail.com?
> utm_medium=email&utm_source=footer
> > [16] mailto:[38]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [17] [39]https://groups.google.com/d/msgid/pandoc-discuss/
> CAMwawgOjpuNWqcFg7CAYansucXhp%2BF_mk2rdLCJ7K3-8Yzd_bQ%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 [40]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [41]https://groups.google.com/d/
> msgid/pandoc-discuss/YzHEkBq9r46iJAFG%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 [42]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [43]https://groups.google.com/d/msgid/
> pandoc-discuss/
> CAMwawgMCNfawhZ6jegTyt9j1kCDeOj_EhJeeFREcbdyRRT1dUQ%40mail.gmail.com.
>
> References:
>
> [1] mailto:bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org
> [2] mailto:bpj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org
> [3] mailto:amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> [4] mailto:amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> [5] mailto:bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org
> [6] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [7] http://groups.google.com/d/msgid/
> [8] http://40mail.gmail.com/
> [9] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [10] https://groups.google.com/d/msgid/pandoc-discuss/
> [11] http://40mail.gmail.com/
> [12] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [13] http://groups.google.com/d/msgid/pandoc-discuss/
> [14] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [15] https://groups.google.com/
> [16] http://40mail.gmail.com/
> [17] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [18] https://groups.google.com/d/
> [19] http://40mail.gmail.com/
> [20] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [21] https://groups.google.com/d/msgid/
> [22] http://40mail.gmail.com/
> [23] mailto:bpj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org
> [24] mailto:amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> [25] mailto:amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> [26] mailto:bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org
> [27] mailto:pandoc-discuss%252Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [28] https://groups.google.com/d/msgid/
> [29] http://40mail.gmail.com/
> [30] mailto:pandoc-discuss%252Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [31] https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgOpaV0jvJccC3zhnSWprWQ8d0qbvH1W8TRF1KObFYH9fA%40mail.gmail.com?utm_medium=email&utm_source=footer
> [32] mailto:pandoc-discuss%252Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [33] https://groups.google.com/d/msgid/pandoc-discuss/Yy2JG50GVYKtHDsA%40localhost
> [34] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [35] https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgNJjZ%3DJB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ%40mail.gmail.com?utm_medium=email&utm_source=footer
> [36] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [37] https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhCYFW%3Dk9fxM6eLM782V3%2BsQ7_X9eH_7LfxO69z%3DDwjONg%40mail.gmail.com?utm_medium=email&utm_source=footer
> [38] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [39] https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgOjpuNWqcFg7CAYansucXhp%2BF_mk2rdLCJ7K3-8Yzd_bQ%40mail.gmail.com?utm_medium=email&utm_source=footer
> [40] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [41] https://groups.google.com/d/msgid/pandoc-discuss/YzHEkBq9r46iJAFG%40localhost
> [42] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [43] https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgMCNfawhZ6jegTyt9j1kCDeOj_EhJeeFREcbdyRRT1dUQ%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/YzLjazFN3XiFNy7X%40localhost.
next prev parent reply other threads:[~2022-09-27 11:50 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
[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 [this message]
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=YzLjazFN3XiFNy7X@localhost \
--to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).