From: Anton Shepelev <anton.txt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: display list bullets
Date: Fri, 21 Aug 2020 12:58:02 +0300 [thread overview]
Message-ID: <20200821125802.792db804af242e8791bc42f1@gmail.com> (raw)
In-Reply-To: <8f57a099-8226-4caf-8c69-dbaf97287a89n@googlegroups.com>
Serg:
> - ::: {custom-style="List Bullet"}
> text;
> :::
>
> ```{=html}
> <!-- -->
> ```
> - ::: {custom-style="List Bullet 2"}
> text;
> :::
>
> - ::: {custom-style="List Bullet 3"}
> text;
> :::
>
> - ::: {custom-style="List Bullet 4"}
> text;
> :::
>
> - ::: {custom-style="List Bullet 5"}
> text.
> :::
>
> Bulleted lists are displayed as the same style
Your Markdown specifies different styles for each
list item, accordding to their nesting in the source
document. The resulting document (3_en.docx) retains
these styles, but for some reason the items have a
custom indetation that overrides the correct indents
specified in the "Bullet List" styles. If you click
on each item and reapply the correct style (which it
already has!) they receive the correct indent.
I don't know why this happens. The documentation
for `custom-style' says:
If you define a div or span with the attribute
custom-style, pandoc will apply your specified
style to the contained elements (with the excep-
tion of elements whose function depends on a
style, like headings, code blocks, block quotes,
or links).
Perhaps other readers can help us answer these ques-
tions:
1. Is it possible that lists styles are, too, an
exception?
2. What is an element of which the function de-
pends on a style?
3. What are the requirements for Pandoc to retain
the list hierarchy in Markdown instead of
putting them all on the same level?
next prev parent reply other threads:[~2020-08-21 9:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 12:19 Serg
2020-08-21 9:58 ` Anton Shepelev [this message]
[not found] ` <8f57a099-8226-4caf-8c69-dbaf97287a89n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-21 10:28 ` BPJ
2020-08-21 12:59 ` Anton Shepelev
[not found] ` <20200821155942.ffeb275a81d1dc390743cbc2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-21 13:24 ` Dmitriy Krasilnikov
2020-08-21 13:45 ` Anton Shepelev
2020-08-21 15:21 ` BPJ
[not found] ` <CADAJKhAOWrEfGg_AZHMuokEYpEQ4P34wHZ=OeND4kdHjHhWVSA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-21 15:58 ` Leonard Rosenthol
[not found] ` <CALu=v3LSYtiNjZqUucjkKGFeTOnTF0k=k2KPut1mZVYL3ioOYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-21 17:51 ` Serg
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=20200821125802.792db804af242e8791bc42f1@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).