ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thad Heltemes <theltemes@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: selecting font by (file) name
Date: Fri, 12 Jun 2015 13:13:10 -0500	[thread overview]
Message-ID: <CAHU6HU9X22+uGVqrPz6BOpVGPoOM2aLMCMc8q9i1PZ6C3twvGw@mail.gmail.com> (raw)
In-Reply-To: <557B1E66.5070102@gmx.es>


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

Pablo,

I had a similar problem with the IM Fell fonts, here's what I had in my
file to get ConTeXt to see them:

\definefontfamily[mainface][serif][IMFellEnglishProRoman][tf=file:IMFEENRM29C.otf,
it=file:IMFEENIT29C.otf]

so I think you just need to add a "tf=" in front of the file declaration.

On Fri, Jun 12, 2015 at 1:01 PM, Pablo Rodriguez <oinos@gmx.es> wrote:

> Dear list,
>
> I have the following sample:
>
>     \definefontfamily
>         [mainface]
>         [rm]
>         [TeX Gyre Pagella]
>
>     \definefontfamily
>         [mainface]
>         [tt]
>         %~ [file:lmmonoproplt10-regular.otf]
>         [name:lmmonoproplt10regular]
>
>     \setupbodyfont
>         [mainface]
>
>     \starttext
>     \type{monospace font}
>     \stoptext
>
> Either by file or name, I’m not able to select the font.
>
> I get the following list from mtxrunjit:
>
> $ mtxrunjit --script font --list --file --pattern=lmmonoproplt10regular
>
> latinmodernmonoproplight   light   normal   normal   normal
> lmmonoproplt10regular   lmmonoproplt10-regular.otf
>
> What am I doing wrong here?
>
> Many thanks for your help,
>
>
> Pablo
> --
> http://www.ousia.tk
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
>
> ___________________________________________________________________________________




-- 
Thad Heltemes, Ph.D.

http://theltemes.net

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

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2015-06-12 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 18:01 Pablo Rodriguez
2015-06-12 18:13 ` Thad Heltemes [this message]
2015-06-12 18:57   ` Pablo Rodriguez
2015-06-13  7:16 ` Wolfgang Schuster

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=CAHU6HU9X22+uGVqrPz6BOpVGPoOM2aLMCMc8q9i1PZ6C3twvGw@mail.gmail.com \
    --to=theltemes@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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).