public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Docx reader and numbered customized styles
Date: Thu, 26 Oct 2023 15:36:08 +0000	[thread overview]
Message-ID: <ZTqHaARLokXDwEvf@localhost> (raw)
In-Reply-To: <53f12b55-0d77-42de-bba2-b88e91f59eecn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

I think that the “styles” extension may help you (you can enable it with the `-f docx+styles` option).

Le Thursday 26 October 2023 à 08:27:31AM, Ioan Muntean a écrit :
> I use a Word document in which a customized style is numbered. I will convert
> this document from docx to latex in Pandoc and then redefine the style in latex
> with its own format. What I want is to avoid converting the numbering of the
> style in pandoc. I want to retain only the text of the style and its name in
> markdown, not the numbering. Is there a command for the docx reader that can
> completely ignore numbering? 
> Thanks!
> Ioan M.
> 
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [2]https://groups.google.com/d/msgid/
> pandoc-discuss/53f12b55-0d77-42de-bba2-b88e91f59eecn%40googlegroups.com.
> 
> References:
> 
> [1] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [2] https://groups.google.com/d/msgid/pandoc-discuss/53f12b55-0d77-42de-bba2-b88e91f59eecn%40googlegroups.com?utm_medium=email&utm_source=footer

-- 
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/ZTqHaARLokXDwEvf%40localhost.


  parent reply	other threads:[~2023-10-26 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 15:27 Ioan Muntean
     [not found] ` <53f12b55-0d77-42de-bba2-b88e91f59eecn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-26 15:36   ` Bastien DUMONT [this message]
2023-10-26 16:24     ` Ioan Muntean
     [not found]       ` <6bc0ec42-4f2b-4832-8b08-827b913669cen-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-26 16:48         ` Bastien DUMONT
2023-10-31 15:09           ` Ioan Muntean
2023-11-14 21:55           ` Ioan Muntean
     [not found]             ` <5652a76c-59ab-4056-ac00-92732e13698en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-14 22:12               ` Bastien DUMONT
2023-11-15  5:32                 ` Ioan Muntean
     [not found]                   ` <SN7PR15MB5635AB592F88C9B03F88840DF9B1A-xz2k8ToKDo8Cw+E34yPvHod3EbNNOtPMvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2023-11-15  8:06                     ` Bastien DUMONT

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=ZTqHaARLokXDwEvf@localhost \
    --to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).