public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Breaking up image description into multiple lines in source file
Date: Mon, 26 Sep 2022 11:24:38 -0400	[thread overview]
Message-ID: <54372a12-dcdb-4172-e398-2652981b93ea@usa.net> (raw)
In-Reply-To: <CAMwawgNJjZ=JB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 9/23/22 9:41 AM, A A wrote:
> 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?

My one thought on that would be to put in some zero-width spaces at 
acceptable wrapping points.

However note that if someone were to copy-paste the output they'll have 
invisible character(s) that wouldn't really be part of the inline code.

Really, this isn't a Pandoc problem - it's a viewer issue.  You want to 
soft-wrap text that is longer than a specified length, not hard wrap it. 
  Some viewers will do that, some won't, some will only soft-wrap on 
spaces.  Pandoc will hard-wrap, but as it's not a viewer soft-wrapping 
isn't even something that applies to it.

Daniel T. Staal

-- 
---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------

-- 
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/54372a12-dcdb-4172-e398-2652981b93ea%40usa.net.


      parent reply	other threads:[~2022-09-26 15:24 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
2022-09-27 13:30                           ` Daniel Staal
2022-09-26 15:24             ` Daniel Staal [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=54372a12-dcdb-4172-e398-2652981b93ea@usa.net \
    --to=dstaal-jdbf3xikgs8@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).