public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Mcneill <jeffmcneill-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: supporting dinkus in markdown to epub and pdf
Date: Tue, 22 Oct 2019 21:30:05 -0700 (PDT)	[thread overview]
Message-ID: <c65ec88e-4c98-4fb1-8c9e-46a3553293ff@googlegroups.com> (raw)


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

In markdown, I markup a dinkus as such:

<p class="dinkus">&lowast; &lowast; &lowast;</p>

The class simply centers the text. 

However, for pdf output, I have to mark up in latex as:

\begin{center}
* * *
\end{center}

This is not a true dinkus, as it uses an asterisk rather than a &lowast;. 

I've got two issues here:

1. How do I make latex (and pdflatex) suppor the dinkus html or unicode 
entity?

2. Does anyone know a clever way of marking up the pandoc markdown so that 
I can use a single source to properly generate both epub and pdf dinkus?

Note that if I leave the latex text in, the dinkus is not displayed in 
epub, and if I leave only the markdown in, then the literal `<p 
class="dinkus">&lowast; &lowast; &lowast;</p>` is displayed in pdf.

Any thoughts are deeply appreciated.

Note: because of some issues I am experiencing with xelatex and images in 
pdf (they don't display), I cannot use that to solve any of these issues.

-- 
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/c65ec88e-4c98-4fb1-8c9e-46a3553293ff%40googlegroups.com.

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

             reply	other threads:[~2019-10-23  4:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  4:30 Jeff Mcneill [this message]
     [not found] ` <c65ec88e-4c98-4fb1-8c9e-46a3553293ff-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-23  6:30   ` Václav Haisman
     [not found]     ` <1850e0db-100f-7d36-f338-6ad3379e8c00-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-10-24  3:10       ` Jeff Mcneill
     [not found]         ` <b23a3ec0-229d-43c5-be5e-235eacf5bbd9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-25 22:55           ` Václav Haisman
     [not found]             ` <8f36859b-536b-51b4-1c3c-e3e339becea3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-10-26  7:09               ` Jeff Mcneill
     [not found]                 ` <9818aeda-5d0a-456d-9129-0fb746f39008-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-26  7:24                   ` Václav Haisman
     [not found]                     ` <6ca8408c-b797-3007-647f-9ea939666067-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-10-26  8:06                       ` Jeff Mcneill
     [not found]                         ` <e119c11f-a1a0-4005-aec4-beaf76381aa1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-26  8:22                           ` Jeff Mcneill
2019-10-26  9:37                           ` Václav Haisman

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=c65ec88e-4c98-4fb1-8c9e-46a3553293ff@googlegroups.com \
    --to=jeffmcneill-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).