public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: pascal Conil-lacoste <pascal.conil.lacoste-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: docx+styles to dokuwiki somehow ?
Date: Wed, 26 Apr 2023 07:14:20 -0700 (PDT)	[thread overview]
Message-ID: <16df0de5-a608-4e6e-9545-3fa338229d8fn@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1124 bytes --]

Hi everybody,

I've been using pandoc for some years to accomplish very straightforward 
conversions.
Now that what I plan to do is a little more complex, I struggle to find 
relevant information.

I need to convert docx to dokuwiki and retain Word custom styles. I thought 
I could use docx+styles to get custom-styles in dokuwiki files but they 
don't make it to the output and get stripped.

I would be happy with ::: {custom-style="myStyle"} my text here:::

If I could get something along these lines, I would be able to apply some 
other simple transformation to get to the final dokuwiki files and treat 
them with a plugin.

What is the best way to achieve this ? Filters ? Templates ?

Any help welcome!

-- 
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/16df0de5-a608-4e6e-9545-3fa338229d8fn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1569 bytes --]

             reply	other threads:[~2023-04-26 14:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 14:14 pascal Conil-lacoste [this message]
     [not found] ` <16df0de5-a608-4e6e-9545-3fa338229d8fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-26 13:16   ` Sigismond
     [not found]     ` <bdc377c4-3918-4f0f-a87e-a66f9d128cc2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-26 13:46       ` Bastien DUMONT
2023-06-26 14:04         ` Sigismond
     [not found]           ` <d22b9383-2891-44f7-8f4a-1867eef83fe2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-27  9:35             ` Sigismond
     [not found]               ` <f0b95670-24a3-4870-842f-fb6e7791a694n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-27  9:53                 ` Bastien DUMONT
2023-06-27 10:21                   ` Sigismond
     [not found]                     ` <a62eaa45-0126-4325-878e-4dae06aba21an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-28 15:00                       ` Sigismond
     [not found]                         ` <62b0db64-b7ab-48e8-9025-9c969304e1b6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-28 16:52                           ` Bastien DUMONT
2023-06-29 13:11                             ` Sigismond

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=16df0de5-a608-4e6e-9545-3fa338229d8fn@googlegroups.com \
    --to=pascal.conil.lacoste-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).