public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: almaghfuur lahu <budikusasi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Apologize if not really pabdoc but instead rst
Date: Wed, 13 Jul 2022 17:16:05 -0700 (PDT)	[thread overview]
Message-ID: <e63b0064-87dd-431a-b346-de9e4c220785n@googlegroups.com> (raw)


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



This's, just now, the result of Github 
issue https://github.com/jgm/pandoc/issues/8172

Now after leading steps getting solved, next step is need to fix a 
imperfection on some lines overrun the right alignment margin

How actually is the rst's width and margin alignment setting command to 
correctly have the max column number laid out, or that is determined 
implicitly by pandoc on the run when trying accomplishing it by:

pandoc -f rst -t pdf -o manual.pdf manual.rst

?  improper line is e.g:

*These keywords are also operators: and or not xor shl shr div mod in notin 
is isnot of as from.*

... notin <= longer than it

Real PDF document being viewed:

*These keywords are also operators: and or not xor shl shr div mod in notin 
is isnot of as from.*

Needed wrapped/broken to:
* These keywords are also operators: and or not xor shl shr div mod in 
notin*
* is isnot of as from. *

Please show the logical way to solve correctly so that can be done in batch 
by find-replace regex tool

the rst:
https://drive.google.com/file/d/19DJ8at1Fze8-HEEzg3n9xLrSB9tIaqW5/view?usp=sharing

-- 
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/e63b0064-87dd-431a-b346-de9e4c220785n%40googlegroups.com.

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

             reply	other threads:[~2022-07-14  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  0:16 almaghfuur lahu [this message]
     [not found] ` <e63b0064-87dd-431a-b346-de9e4c220785n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-14  8:47   ` William Lupton
     [not found]     ` <CAEe_xxi=4ZT+RyhGPAtWiWFE1phYgshYubzA-+G7B2mESXJrpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-14  8:57       ` Bastien DUMONT
2022-07-17  5:29         ` almaghfuur lahu
     [not found]           ` <a2c95871-daca-41e5-a971-deb1f3085eb4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-17  8:11             ` Bastien DUMONT

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=e63b0064-87dd-431a-b346-de9e4c220785n@googlegroups.com \
    --to=budikusasi-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).