public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "B. T." <blautanne0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Convert markdown <span> to docx hidden text
Date: Wed, 21 Aug 2019 07:26:51 -0700 (PDT)	[thread overview]
Message-ID: <48ac7c8c-49f7-465f-a2d9-acbdc1e17f6a@googlegroups.com> (raw)


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

Hello pandoc-Community,

I would appreciate some help how to convert some hidden text that I 
included in markdown to hidden text in Microsoft Word. In my markdown file, 
I use <span> and a custom data attribute to mark specific parts of the 
text. This marking serves as a reference to a standard. 

Example:
- <span data-aspice="v3.1 SWE.1.BP4">are analyzed regarding their impact on 
the operating environment;</span> and

When converting to html, these labels are preserved, but are not displayed 
in a browser. Perfect. But the final format should be docx. In the docx I 
also want to hide the text using a character style with hidden attribute 
set. So It should look like this, with green marking the hidden text.

- [data-aspice="v3.1 SWE.1.BP4"are analyzed regarding their impact on the 
operating environment;] and


I already started with lua filters (using Span and RawInline) but without 
success. Can anyone give me a hint. 

Thanks
B.T.


-- 
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/48ac7c8c-49f7-465f-a2d9-acbdc1e17f6a%40googlegroups.com.

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

                 reply	other threads:[~2019-08-21 14:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=48ac7c8c-49f7-465f-a2d9-acbdc1e17f6a@googlegroups.com \
    --to=blautanne0-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).