ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [OT] creating-a-style-file-in-context
Date: Sun, 25 Oct 2009 10:37:52 +0100	[thread overview]
Message-ID: <D86F10DF-C232-4367-BA1A-BD928B102FA1@googlemail.com> (raw)
In-Reply-To: <4AE41A04.9070501@elvenkind.com>


Am 25.10.2009 um 10:27 schrieb Taco Hoekwater:

> On top of that:
>
> In type-exljbris, you should use the first column of the output of  
> mtxrun --script fonts --list, if you use the name: prefix.

type-exlbjbris.mkiv:

% Museo, Museo Sans

\starttypescript [serif] [museo]
     \definefontsynonym [Museo-300] [name:museo300] [features=default]
     \definefontsynonym [Museo-500] [name:museo500] [features=default]
     \definefontsynonym [Museo-700] [name:museo700] [features=default]
\stoptypescript


Terminal:

rover:~ wolf$ mtxrun --script fonts --list museo*
museo               Museo 300 Regular      Museo300-Regular.otf
museo300            Museo 300              Museo300-Regular.otf
museo300regular     Museo 300 Regular      Museo300-Regular.otf
museo500            Museo 500              Museo500-Regular.otf
museo500medium      Museo 500 Medium       Museo500-Regular.otf
museo700            Museo 700              Museo700-Regular.otf
museo700bold        Museo 700 Bold         Museo700-Regular.otf
museoregular        Museo 300 Regular      Museo300-Regular.otf

Wolfgang

___________________________________________________________________________________
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:[~2009-10-25  9:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21  9:05 luigi scarso
2009-10-25  9:15 ` Jan-Erik Hägglöf
2009-10-25  9:23   ` Wolfgang Schuster
2009-10-25  9:27     ` Taco Hoekwater
2009-10-25  9:37       ` Wolfgang Schuster [this message]
2009-10-25 10:27         ` Jan-Erik Hägglöf
2009-10-25 10:40           ` Wolfgang Schuster
2009-10-25 11:05           ` Aditya Mahajan
2009-10-25 12:09             ` Jan-Erik Hägglöf
2009-10-25 12:17               ` Aditya Mahajan
2009-10-25 12:28                 ` Jan-Erik Hägglöf
2009-10-25 12:32                 ` Jan-Erik Hägglöf
2009-10-25 12:45 ` Wolfgang Schuster
2009-10-25 14:17   ` Jan-Erik Hägglöf
2009-10-25 14:29     ` Wolfgang Schuster
2009-10-25 14:53       ` Jan-Erik Hägglöf
2009-10-26  5:42   ` Aditya Mahajan
2009-10-26  7:43     ` Wolfgang Schuster
2009-10-26 16:13       ` Aditya Mahajan
2009-10-26 21:20         ` Wolfgang Schuster
2009-10-27  6:13           ` Aditya Mahajan
2009-10-27  8:45             ` Wolfgang Schuster
2009-10-27  8:50               ` Hans Hagen
2009-10-27  8:56                 ` Wolfgang Schuster
2009-10-27  9:11                   ` Hans Hagen
2009-10-27  9:13                     ` luigi scarso
2009-10-27 13:38               ` Aditya Mahajan
2009-10-27 22:08                 ` 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=D86F10DF-C232-4367-BA1A-BD928B102FA1@googlemail.com \
    --to=schuster.wolfgang@googlemail.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).