public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Serg <hudrid-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: display list numbers
Date: Fri, 21 Aug 2020 12:47:15 -0700	[thread overview]
Message-ID: <m2k0xrbx30.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <d1992e34-4787-4957-bd4d-149ac045d496n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Thanks for this and your other posts.

You can help diagnose what is going on, to save the developers'
time.

The most basic question to resolve is whether it's an issue with
the docx reader, the docx writer, the markdown reader, or the
markdown writer.

If the document features you're interested in are represented
in the intermediate markdown file but not the final docx,
then the problem is either in the markdown reader or the
docx writer.  If they're not represented in the intermediate
markdown file, then the probelm is either in the docx reader
or the markdown writer.

To narrow it down further, you can inspect the "native"
representation of the document pandoc uses, e.g.

pandoc -f docx+styles -t native -s

If the document features you're interested in it are not represented
there, you know the issue is with the docx reader.

Anything you can do to help narrow down the issues will be helpful.


Serg <hudrid-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Hello!
>
>  I use pandoc *2.10.1*.
>
>  There are three documents in the attachment, in this way the result of the 
> conversion is "1.docx- > 2.md- > 3.docx".
>
>  I perform the сonversion with assistance by next commands:
>
>  *1.docx- > 2.md*:
>
> *pandoc -s 1_en.docx -f docx+styles -t markdown -o 2_en.md -s*
>
>  *2.md- > 3.docx*:
>
> *pandoc --reference-doc 1_en.docx 2_en.md -f markdown -t docx -o 3_en.docx*
>
>  
>
> As a result, I get the following problems in output file *3.docx*:
>
> Numbered lists are displayed as the same style (1_en.docx = yes.png; 
> 3_en.docx = no.png)
>
>  
>
> -- 
> 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/d1992e34-4787-4957-bd4d-149ac045d496n%40googlegroups.com.
> **List Numbers:**
>
> 1.  ::: {custom-style="List Number"}
>     Number.
>     :::
>
> 2.  ::: {custom-style="List Number"}
>     Number.
>     :::
>
> 3.  ::: {custom-style="List Number 2"}
>     Number.
>     :::
>
> 4.  ::: {custom-style="List Number 3"}
>     Number.
>     :::
>
> 5.  ::: {custom-style="List Number 4"}
>     Number.
>     :::
>
> 6.  ::: {custom-style="List Number 5"}
>     Number.
>     :::

-- 
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/m2k0xrbx30.fsf%40johnmacfarlane.net.


  parent reply	other threads:[~2020-08-21 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 12:19 Serg
     [not found] ` <d1992e34-4787-4957-bd4d-149ac045d496n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-21 19:47   ` John MacFarlane [this message]
     [not found]     ` <m2k0xrbx30.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-21 19:59       ` 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=m2k0xrbx30.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=hudrid-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).