public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Rik <amphiboly-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Processing the wedge ∧ in mediawiki is unviewable in pdf output using xelatex...
Date: Wed, 25 Oct 2017 17:56:15 -0400	[thread overview]
Message-ID: <osr19q$ecv$1@blaine.gmane.org> (raw)
In-Reply-To: <87r2u1k4bg.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>

On 2017-10-17 14:38, Joost Kremers wrote:
> 
> On Tue, Oct 17 2017, Federer Fanatic wrote:
>> Thanks! That worked. How would I determine other possible fonts that
>> would also render things
>> visibly? Is there an underlying method?
> 
> Other than trying, I'm afraid not. I tend to use LibreOffice for that 
> sort of thing, because it's easy to select some text and change its font.
> 
> 
> 

BabelMap (http://www.babelstone.co.uk/Software/BabelMap.html) is a free 
Windows GUI program with a font coverage utility that will inform you 
which of your fonts covers a specified Unicode character. It has many 
other uses as well.

-- 
Rik


      parent reply	other threads:[~2017-10-25 21:56 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
     [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 [this message]

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='osr19q$ecv$1@blaine.gmane.org' \
    --to=amphiboly-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).