From: Anton Shepelev <anton.txt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How to control indentation of lists in docx with Pandoc?
Date: Tue, 11 Aug 2020 12:01:21 +0300 [thread overview]
Message-ID: <20200811120121.958dff2b6a07c4537e6f399b@gmail.com> (raw)
In-Reply-To: <575de665-9241-4c1b-86a2-a20c5fd4dd7bn@googlegroups.com>
Mikhail Matrosov:
> I convert AsciiDoc to Word via DocBook. The
> db->docx conversion is done with Pandoc and is the
> most interesting.
>
> I provide a reference file with --reference-doc. I
> specified indentation for the Body Text style in
> the reference file. Now text is indented. But
> lists are not.
>
> While digging through the contents of the generat-
> ed docx I discovered that you cannot control in-
> dentation of list items directly. [...]
I have the same problem, but did not dig into it so
deep. Thanks for the research.
My problem has been discussed here in a thread ti-
tled:
Adjusting the indentation of nested numbered lists in docx
( https://groups.google.com/forum/#!topic/pandoc-discuss/F9MaKcb5xZo )
where the experts told be the indentation is cur-
rently hardcoded(!). I created a Github issue with
some proposals of how to fix it (in terms of outward
behavoir, not implementation):
Support customisable indentation of nested lists in .docx output
( https://github.com/jgm/pandoc/issues/6586 )
I far as I understand, it is somewhat hard to do and
requires extra coupling between the general pandoc
engine and the DOCX renderer. Yet is not a reason to
leave the indentation hardcoded.
A similar difficulty arises when putting code blocks
and lists inside definitions. If the definition
style has an indent, the code and lists are still
unindented, which is of course unintended.
--
Please, do not forward replies to the list to my e-mail.
next prev parent reply other threads:[~2020-08-11 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 8:09 Mikhail Matrosov
2020-08-11 9:01 ` Anton Shepelev [this message]
[not found] ` <20200811120121.958dff2b6a07c4537e6f399b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-11 13:09 ` Mikhail Matrosov
[not found] ` <575de665-9241-4c1b-86a2-a20c5fd4dd7bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-11 9:09 ` Tomáš Kruliš
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=20200811120121.958dff2b6a07c4537e6f399b@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).