ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: kpfonts, math, type 1 font
Date: Tue, 7 Jan 2014 20:48:17 +0100	[thread overview]
Message-ID: <F08AA785-FD32-40F0-8BB7-25A7B9355514@gmail.com> (raw)
In-Reply-To: <CAGMMSTBJNrBeqN5yCWTm1rsLbLzuhcC6Vy1W_XXsryRSoD00FA@mail.gmail.com>


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


Am 07.01.2014 um 20:39 schrieb Elspeth McGullicuddy <elspethmcgullicuddy@gmail.com>:

> The files like tfm, afm, pfb,... seem to be found alright by "mtxrun
> --script fonts --reload" when they are in the ${HOME}/texmf/fonts/
> tree, so I think I can leave them there.

Yes but the tfm and vf files are only needed for the math fonts.

> So I should make a sort of copy of "mdugm-math.lgf" and call it
> "kpfonts-math.lgf", and put it in
> ${HOME}/context/tex/texmf-context/tex/context/fonts/.
> 
> [Do the same with a copy of "type-imp-mathdesign.mkiv", which
> contains: "\loadfontgoodies[mdugm-math]".] Or rather put a typescript
> in my document file as explained here:
> http://wiki.contextgarden.net/Math_fonts, and insert some
> "\loadfontgoodies[kpfonts-math]" in it.
> 
> Execute: "context --make en". And that should be it.

You can also put the goodies files and the typescript file in the same
folder as your test files which makes it easier to test them and to make
changes. When you’re finished you can let us take a look at them
and Hans can add them to the core.

> What is the "\s!" syntax for, as in "\s!Serif“?

Commands starting with \s! are used for language independent strings
to save memory, e.g. “\s!Serif” is for TeX only a single token while “Serif”
are 5 tokens. There exist more prefixes (e.g. \c! and \v!) but they are
only important for developers.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 2961 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:[~2014-01-07 19:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 18:56 Elspeth McGullicuddy
2014-01-06 23:09 ` Wolfgang Schuster
2014-01-07  3:35   ` Elspeth McGullicuddy
2014-01-07 15:32     ` Hans Hagen
2014-01-07 19:39       ` Elspeth McGullicuddy
2014-01-07 19:48         ` Wolfgang Schuster [this message]
2014-01-10  3:54           ` Elspeth McGullicuddy
2014-01-10 22:38             ` Elspeth McGullicuddy
2014-01-11 14:03               ` Wolfgang Schuster
2014-01-11 18:36                 ` Elspeth McGullicuddy
2014-01-11 19:48                   ` Elspeth McGullicuddy

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=F08AA785-FD32-40F0-8BB7-25A7B9355514@gmail.com \
    --to=schuster.wolfgang@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).