ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Peter Münster" <pmlists@free.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: urw-garamond with MKIV
Date: Mon, 21 Apr 2008 21:38:49 +0200	[thread overview]
Message-ID: <20080421193849.GA19898@gaston.couberia.bzh> (raw)
In-Reply-To: <480C4ECC.3070009@wxs.nl>

On Mon, Apr 21 2008, Hans Hagen wrote:

> % works ok
> 
> \starttypescript [serif] [urwgaramond]
>    \definefontsynonym [Garamond-Regular]      [file:GaramondNo8-Reg] 
> [features=complete]
>    \definefontsynonym [Garamond-Medium]       [file:GaramondNo8-Med] 
> [features=complete]
>    \definefontsynonym [Garamond-Italic]       [file:GaramondNo8-Ita] 
> [features=complete]
>    \definefontsynonym [Garamond-MediumItalic] [file:GaramondNo8-MedIta] 
> [features=complete]
> \stoptypescript
> 
> \starttypescript [urwgaramond]
>    \definetypeface [\typescriptone] [rm] [serif] [urwgaramond] [default]
> \stoptypescript
> 
> \usetypescript[urwgaramond]
> \setupbodyfont[urwgaramond]

Hello Hans,

What exactly works ok?
I tried the above lines, but I get the lm-font in the pdf. And when
replacing "Garamond-Regular" with "Serif" and so on, luatex crashes here
too. 2 messages that are perhaps helpful:
report >> load otf: loading: /opt/TeX-live/texmf-local/fonts/truetype/public/urw/GaramondNo8-Ita.ttf
report >> load otf: warning: Glyph 632 is called ".notdef", a singularly inept choice of name (only glyph 0 may be called .notdef)

Cheers, Peter

-- 
http://pmrb.free.fr/contact/

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      parent reply	other threads:[~2008-04-21 19:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12  7:44 Peter Münster
2008-04-13  9:38 ` Taco Hoekwater
2008-04-13 11:37   ` Peter Münster
2008-04-13 18:53     ` Henning Hraban Ramm
2008-04-14  7:13 ` Wolfgang Schuster
2008-04-14  7:18   ` ConTeXt Document with SVN Info Included Michael Hallgren
2008-04-14 12:38     ` Peter Münster
2008-04-14 19:42       ` Michael Hallgren
2008-04-14 22:30     ` Stephan Hennig
2008-04-20 19:38   ` urw-garamond with MKIV Peter Münster
2008-04-21  6:25     ` Wolfgang Schuster
2008-04-21  7:17       ` Hans Hagen
2008-04-21  7:41         ` Wolfgang Schuster
2008-04-21  8:05           ` Hans Hagen
2008-04-21  8:25             ` Wolfgang Schuster
2008-04-21  8:22           ` Hans Hagen
2008-04-21 11:05             ` Lutz Haseloff
2008-04-21 11:54               ` Hans Hagen
2008-04-21 12:06                 ` Lutz Haseloff
2008-04-21 17:47                   ` Taco Hoekwater
2008-04-22  6:07                     ` Wolfgang Schuster
2008-04-22  6:52                       ` Taco Hoekwater
2008-04-22 10:43                         ` Taco Hoekwater
2008-04-23 10:36                           ` Lutz Haseloff
2008-04-23 12:34                             ` Taco Hoekwater
2008-04-21 19:38             ` Peter Münster [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=20080421193849.GA19898@gaston.couberia.bzh \
    --to=pmlists@free.fr \
    --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).