public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joost Kremers <joostkremers-97jfqw80gc6171pxa8y+qA@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
Subject: Re: Custom styles in docx to markdown conversion.
Date: Fri, 10 Dec 2021 20:39:06 +0100	[thread overview]
Message-ID: <877dcckzsu.fsf@fastmail.fm> (raw)
In-Reply-To: <m235n04cw4.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>


On Fri, Dec 10 2021, John MacFarlane wrote:
> "Joost Kremers" <joostkremers-97jfqw80gc6171pxa8y+qA@public.gmane.org> writes:
>> I'm trying to convert some MS Word documents to markdown, which works
>> surprisingly well, except for two issues I'm wondering about:
>>
>> 1. Section headings aren't converted to `## ...`. This, I assume, is due to
>> the fact that they have a custom style.
>
> Hard to say without an example. Can you post a sample docx?

No, unfortunately not, it's confidential material. When I convert with `-f
docx+styles` I get things like:

```
::: {custom-style="XYZ Minor Head (1.1)"}
Lorem ipsum
:::

::: {custom-style="XYZ Body Text"}
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
> quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
> consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
> cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
> proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
:::
```

Etc., etc.

Does that help?

Thanks,

Joost


-- 
Joost Kremers
Life has its moments


  parent reply	other threads:[~2021-12-10 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 12:07 Joost Kremers
     [not found] ` <a1fcb30f-4d0d-449b-b02e-b375f8e38abe-jFIJ+Wc5/Vo7lZ9V/NTDHw@public.gmane.org>
2021-12-10 16:56   ` John MacFarlane
     [not found]     ` <m235n04cw4.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-12-10 19:39       ` Joost Kremers [this message]
     [not found]         ` <877dcckzsu.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2021-12-11  0:07           ` John MacFarlane
     [not found]             ` <yh480ka6h8t35a.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-12-15  9:47               ` Joost Kremers
2021-12-16 12:28               ` Joost Kremers
     [not found]                 ` <87czlwhel7.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2021-12-16 14: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=877dcckzsu.fsf@fastmail.fm \
    --to=joostkremers-97jfqw80gc6171pxa8y+qa@public.gmane.org \
    --cc=jgm-TVLZxgkOlNX2fBVCVOL8/A@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).