public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Docx > mediawiki : losing color
Date: Wed, 07 Dec 2022 11:07:03 +0100	[thread overview]
Message-ID: <87edtbttik.fsf@zeitkraut.de> (raw)
In-Reply-To: <32bdcff7-7794-4952-98e3-73916ace1a2an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Kevin <koromire69-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> When i'm converting some docx file to mediawiki.txt file, only the
> basic style (like <strong>) remain. All my colouring disapear. 

As the manual says: "Pandoc attempts to preserve the structural elements
of a document, but not formatting details […]." Colours are not
considered part of the document structure, so pandoc does not attempt to
preserve those in the conversion.


-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124

-- 
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/87edtbttik.fsf%40zeitkraut.de.


  parent reply	other threads:[~2022-12-07 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  9:58 Kevin
     [not found] ` <32bdcff7-7794-4952-98e3-73916ace1a2an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-07 10:07   ` Albert Krewinkel [this message]
     [not found]     ` <87edtbttik.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-12-07 10:19       ` Kevin
     [not found]         ` <61823eaa-0788-4f75-965c-3c2fa5b3d728n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-07 11:34           ` Albert Krewinkel

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=87edtbttik.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).