From: Federer Fanatic <nafdef-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Processing the wedge ∧ in mediawiki is unviewable in pdf output using xelatex...
Date: Tue, 17 Oct 2017 13:32:20 -0400 [thread overview]
Message-ID: <CAAwvWVrk0OX4TM8O8jVCZjXib684srmDrz-cZQ4unxb4+GP_Mg@mail.gmail.com> (raw)
In-Reply-To: <87shehk9zn.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
Thanks! That worked. How would I determine other possible fonts that
would also render things
visibly? Is there an underlying method?
FF
--------------------------------------------------------------
Roger Federer Fanatic Extraordinaire :-)
On Tue, Oct 17, 2017 at 12:35 PM, Joost Kremers
<joostkremers-97jfqw80gc6171pxa8y+qA@public.gmane.org> wrote:
>
> On Tue, Oct 17 2017, Federer Fanatic wrote:
>>
>> Example: (see attached PDF and wedge.tex, full file)
>>
>> I used the command: pandoc -f mediawiki -s -t latex -i wedge.mediawiki -o
>> wedge.tex
>
>
> This seems to be related to the use of
> \usepackage{lmodern}
>
> in your file. I'm not sure of the details, but it seems that you'll need to
> set an appropriate font. Pandoc will then make sure that this line isn't
> added to your template.
>
> The Linux Libertine fonts work fine and IMHO opinion look quite good. Add
> the following:
>
> --variable=sansfont:"Linux Biolinum O" --variable=mainfont:"Linux Libertine
> O"
>
> to your pandoc invocation and, provided you have the Libertine fonts, it
> should work.
>
> HTH
>
>
> --
> Joost Kremers
> Life has its moments
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pandoc-discuss/EAOd0hyckfw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/87shehk9zn.fsf%40fastmail.fm.
> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2017-10-17 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 12:33 Federer Fanatic
[not found] ` <237dcd67-2755-4a0d-852f-2b239c076b4a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-17 16:35 ` Joost Kremers
[not found] ` <87shehk9zn.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2017-10-17 17:32 ` Federer Fanatic [this message]
[not found] ` <CAAwvWVrk0OX4TM8O8jVCZjXib684srmDrz-cZQ4unxb4+GP_Mg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-17 18:38 ` Joost Kremers
[not found] ` <87r2u1k4bg.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2017-10-25 21:56 ` Rik
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=CAAwvWVrk0OX4TM8O8jVCZjXib684srmDrz-cZQ4unxb4+GP_Mg@mail.gmail.com \
--to=nafdef-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).