public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Shepelev <anton.txt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Adjusting the indentation of nested numbered lists in docx
Date: Sun, 2 Aug 2020 19:31:28 +0300	[thread overview]
Message-ID: <20200802193128.c8aa7e41f80663d4980b7d89@gmail.com> (raw)
In-Reply-To: <m2wo2ixcq2.fsf@johnmacfarlane.net>

John MacFarlane to Anton Shepelev:

> > Which settings in the reference document define the
> > indentation of nested numbered lists in docx?  I have tried
> > modifying styles "List" and "List number" -- but to no
> > avail. In the rendered document, the elements of a numbered
> > list have style "Compact" and invariably a hanging indent of
> > 0.85 cm. How can I change that?
> This is hard-coded, I'm afraid.
> 
> We need to create the numbering.xml entries for ordered
> lists on the fly, since they depend on start numbers and
> list types.  When we generate them we use this fixed indent.

Hmmm, that is no good -- lack of flexibility in so basic a
functionality. Would you consider, for example, an option to use
the "List number" styles, sacrificing some advanced features such
as continuations, e.g. --use-list-styles. After all, that is the
purpose of list styles in MS Word, and those styles are present in
the default reference document.

> I suppose it might be possible to have pandoc read something
> from the style and use it instead of this fixed value.
> For example, we could include a style entry for ordered
> lists -- even though it would be overwritten by the autogenerated
> one we could still read a value from it and use it in the code.
> Feel free to submit an issue or PR.

Sounds possible too, but harder than using the style as is.
I cannot offer a PR, and will file an issue.

-- 
()  ascii ribbon campaign - against html e-mail
/\  http://preview.tinyurl.com/qcy6mjc [archived]


  reply	other threads:[~2020-08-02 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31 10:37 Anton Shepelev
2020-08-01 17:39 ` Anton Shepelev
     [not found] ` <20200731133752.86795023266c495b6a77dd4b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-01 21:44   ` John MacFarlane
2020-08-02 16:31     ` Anton Shepelev [this message]
     [not found]       ` <20200802193128.c8aa7e41f80663d4980b7d89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-03 20:34         ` John MacFarlane
2020-08-03 20:49           ` Anton Shepelev
2020-08-02 21:54     ` Anton Shepelev

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=20200802193128.c8aa7e41f80663d4980b7d89@gmail.com \
    --to=anton.txt-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).