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: Re: supporting dinkus in markdown to epub and pdf
Date: Sat, 26 Oct 2019 01:22:13 -0700 (PDT)	[thread overview]
Message-ID: <e6481d47-470a-4b5d-8a04-8ad3d0a35066@googlegroups.com> (raw)
In-Reply-To: <e119c11f-a1a0-4005-aec4-beaf76381aa1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

P.S., the &lowast; is really what I want, so final format is as follows:

`<p class="dinkus"> &lowast; &lowast; &lowast; </p>`{=html}
`\begin{center} ∗ ∗ ∗ \end{center}`{=latex}

On Saturday, October 26, 2019 at 3:06:27 PM UTC+7, Jeff Mcneill wrote:
>
> Aha, I've found a fix, referenced at: 
> https://stackoverflow.com/questions/48083724/pandoc-markdown-ignore-text-in-pdf-but-include-in-html-updated
>
> Here is what I put, and the epub ignores the latex content and the latex 
> ignores the epub (html) content. Magical indeed.
>
> `<p class="dinkus">&midast; &midast; &midast;</p>`{=html}
>> \begin{center} ∗ ∗ ∗ \end{center}
>
>
> Thanks for your help. Your suggestions are very useful. 
> --Jeff Mcneill
>
>
> On Saturday, October 26, 2019 at 2:24:17 PM UTC+7, Václav Haisman wrote:
>
>> On 26. 10. 19 9:09, Jeff Mcneill wrote:
>>
>> I suggest you add the following to your LaTeX preamble:
>>>
>>> \usepackage{newunicodechar}
>>> \newunicodechar{∗}{\textasteriskcentered}
>>>
>>> and then use the raw character in your document
>>>
>>> \begin{center}
>>> ∗ ∗ ∗
>>> \end{center}
>>>
>>> ​
>>>
>>>
>>> -- 
>>> VH
>>>
>>>
>> This indeed fixes my issue with latex in terms of producing the correct 
>> dinkus display (&midast;) when md->pdf, however this still is discarded by 
>> pandoc when producing an md->epub. The lines are simply removed (there is 
>> no dinkus and no additional space added between the separated sections). -- 
>>
>>
>> You will have to write a filter that will implement the dingus 
>> differently for each output format. Pandoc is not magical, it cannot 
>> translate everything.
>>
>> One more comment about the LaTeX dingus: I have found one more 
>> sophisticated implementation, see 
>> https://tex.stackexchange.com/a/101240/28495.
>> ​
>>
>>
>>
>> -- 
>> VH
>>
>>

-- 
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/e6481d47-470a-4b5d-8a04-8ad3d0a35066%40googlegroups.com.

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

  parent reply	other threads:[~2019-10-26  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  4:30 Jeff Mcneill
     [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 [this message]
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=e6481d47-470a-4b5d-8a04-8ad3d0a35066@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).