public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Dmitriy Krasilnikov <dmitriy.krasilnikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Finn Mathisen <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: display list bullets
Date: Fri, 21 Aug 2020 16:24:35 +0300	[thread overview]
Message-ID: <CALZUCcAPjiCYTHUT+8Jotxs8_+Q7heBCgsWENqrcy4P2P1gYww@mail.gmail.com> (raw)
In-Reply-To: <20200821155942.ffeb275a81d1dc390743cbc2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Look into the 1_en.docx thoroughly. There is no multilevel list there
— there's a single-level list where each element is bound to different
style. So Pandoc reasonably puts every element on the same level. Then
the resulting single level markdown list is transformed to a list of
paragraphs with a style each. It works correctly (you can see each
list item is bound to a style), but built-in list styles override
paragraph styles until paragraph style is reapplied. So Serg will have
to right click the style, select all paragraphs marked by this style
and apply the style.

It's worth noting that list style is only about indentations. If you
make Level4 list bold in a 1_en.docx, you will see the last 2 levels
of 3_en.docx will become bold, since these two paragraph styles will
inherit boldness from a paragraph style, but the indentation will come
from a built in single level list style.

пт, 21 авг. 2020 г. в 15:59, Anton Shepelev <anton.txt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
>
> BPJ:
>
> > Pandoc's  internal  representation does not retain
> > information on which bullet list markers were used
> > in  the  original. Try converting from Markdown to
> > Markdown: you will see that all list markers  come
> > out as hyphens.
>
> I  think  Serge's problem is not the specific bullet
> marker but the flattening of  an  originally  nested
> list.  He wrote:
>
> > Bulleted lists are displayed as the same style
>
> In   the  resulting  document  the  items  different
> styles, but the indent is overridden in all so  that
> the  list looks flat, *as if* its items had the same
> style.
>
> --
> 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/20200821155942.ffeb275a81d1dc390743cbc2%40gmail.com.

-- 
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/CALZUCcAPjiCYTHUT%2B8Jotxs8_%2BQ7heBCgsWENqrcy4P2P1gYww%40mail.gmail.com.


  parent reply	other threads:[~2020-08-21 13:24 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
     [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 [this message]
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=CALZUCcAPjiCYTHUT+8Jotxs8_+Q7heBCgsWENqrcy4P2P1gYww@mail.gmail.com \
    --to=dmitriy.krasilnikov-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).