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 <amine.aboufirass@gmail.com> 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 <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@googlegroups.com.
> 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@googlegroups.com
> [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@googlegroups.com.
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-/JYPxA39Uh4Ykp1iOSErHA@public.gmane.orgm.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgNJjZ%3DJB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ%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 pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhCYFW%3Dk9fxM6eLM782V3%2BsQ7_X9eH_7LfxO69z%3DDwjONg%40mail.gmail.com.