public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: TOC overwrites entry in TOC for chapters > 99 and subchapters > 9 (eg ddd.dd)
Date: Fri, 22 Jul 2022 07:31:53 +0000	[thread overview]
Message-ID: <YtpSaX1zYx/UzOYj@localhost> (raw)
In-Reply-To: <9a7c9f39-c4ba-4f7b-a81d-e9b29a09ceabn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

This can be solved by adding some LaTeX instructions (e.g. using header-includes) to enlarge the space assigned to the section numbers in your TOC. The document class you use should provide a way to do that: see its documentation.

Le Thursday 21 July 2022 à 01:18:13PM, Gareth Smith a écrit :
> Sorry, I am calling pandoc with
> 
> pandoc --from markdown-markdown_in_html_blocks+raw_html --number-sections
> --toc-depth=2 --top-level-division=chapter -V documentclass=extreport -V
> mainfont="Arev" -V font="Arev" -V fontsize=8pt allrpt.md -o report.pdf
> 
> On Friday, July 22, 2022 at 4:15:16 AM UTC+8 Gareth Smith wrote:
> 
>     I am assembling a large programatically generated engineering document and
>     it has more than 100 chapters and and some of them have more than 10
>     sub-chapters.
> 
>     I get some overwriting, see below, can anyone help?
> 
>     I am guessing there is a formatting string of some kind I can alter, but I
>     am new to pandoc and I haven't had time to try much myself, it is a big doc
>     and I am late....
> 
> 
>     screen01.jpg
> 
> --
> 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/9a7c9f39-c4ba-4f7b-a81d-e9b29a09ceabn%40googlegroups.com.
> 
> References:
> 
> [1] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [2] https://groups.google.com/d/msgid/pandoc-discuss/9a7c9f39-c4ba-4f7b-a81d-e9b29a09ceabn%40googlegroups.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/YtpSaX1zYx/UzOYj%40localhost.


      parent reply	other threads:[~2022-07-22  7:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 20:15 Gareth Smith
     [not found] ` <3b5d4d27-1c27-4d52-a94b-cdd89973dbb0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-21 20:18   ` Gareth Smith
     [not found]     ` <9a7c9f39-c4ba-4f7b-a81d-e9b29a09ceabn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-22  7:31       ` Bastien DUMONT [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=YtpSaX1zYx/UzOYj@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).