ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Lutz Haseloff" <lutz.haseloff@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: urw-garamond with MKIV
Date: Mon, 21 Apr 2008 14:06:56 +0200	[thread overview]
Message-ID: <a09128560804210506l6a87ef8aie1cf1b90e07d0dca@mail.gmail.com> (raw)
In-Reply-To: <480C808A.5050407@wxs.nl>

2008/4/21, Hans Hagen <pragma@wxs.nl>:
> Lutz Haseloff wrote:
>  > Hi Hans, hi all,
>  >
>  > is there a way to get the type1 LucidaBright fonts working
>  > in LuaTeX/MKIV? I put the afm and pfb into the tree.
>  > ---------------
>  > \usetypescript [lucida] [texnansi]
>  > \switchtotypeface [lucida] [9pt]
>  > ---------------
>  > from showfont results in latinmodern.
>  >
>  > My try to use
>  > ---------------
>  > \font\test=lbr*default\test
>  > \starttext
>  >
>  > ABC
>  >
>  > abc
>  >
>  > 123
>  >
>  > \stoptext
>  > ---------------
>  > loads the afm, shows LucidaBright, but the same strange output in pdf
>  > as described in Wolfgang's mails.
>
>
> do you use the latest luatex?
>

This is LuaTeX, Version snapshot-0.25.3-2008042009

I tried both 0.25.3 from w32tex and from http://foundry.supelec.fr/,
my ConTeXt is ConTeXt  ver: 2008.04.18 14:17 MKIV  fmt: 2008.4.21
int: english/english

It's curious, if i copy and paste the strange text from the pdf into my
editor all glyphs are the right ones.

Greetings Lutz

>  Hans
>
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-04-21 12:06 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 [this message]
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

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=a09128560804210506l6a87ef8aie1cf1b90e07d0dca@mail.gmail.com \
    --to=lutz.haseloff@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).