ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Piotr Kopszak <kopszak@mnw.art.pl>
To: ntg-context@ntg.nl
Subject: Delicious - I'm still confused
Date: Mon, 18 Aug 2008 15:09:38 +0200	[thread overview]
Message-ID: <20080818130938.GA5607@mnw.art.pl> (raw)

Hello list, 


Sorry for being boring, but I still can't figure out whether Delicious font can or cannot 
be used with latest beta. It still does not work for me. Strangely 

mtxrun --script font --list|grep deli

gives 

deliciousbold                    Delicious-Bold                    Delicious-Bold.otf
deliciousbolditalic              Delicious-BoldItalic              Delicious-BoldItalic.otf
deliciousheavy                   Delicious-Heavy                   Delicious-Heavy.otf
deliciousheavymedium             Delicious-Heavy                   Delicious-Heavy.otf
deliciousitalic                  Delicious-Italic                  Delicious-Italic.otf
deliciousmedium                  Delicious-Roman                   Delicious-Roman.otf
deliciousroman                   Delicious-Roman                   Delicious-Roman.otf
delicioussmallcaps               Delicious-SmallCaps               Delicious-SmallCaps.otf
delicioussmallcapsmedium         Delicious-SmallCaps               Delicious-SmallCaps.otf

but 

texexec --lua --pdf delicious-test

has problems:

define font | forced type otf of Delicious-Roman not found
define font | font with name Delicious-Roman is not found
define font | unknown font Delicious-Roman, loading aborted
! Font \*delicious12ptsstfss*:=Delicious-Roman.otf at 12pt not loadable: metric data not found or bad.

Piotr




-- 
--

  Piotr Kopszak, Ph.D.
  Polish Art Gallery, National Museum in Warsaw
  ----------------------------->    http://kopszak.mnw.art.pl/
  http://okle.pl

___________________________________________________________________________________
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-08-18 13:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 13:09 Piotr Kopszak [this message]
2008-08-18 13:16 ` Wolfgang Schuster
2008-08-18 13:36 ` Hans Hagen
2008-08-18 13:51   ` Piotr Kopszak
2008-08-18 16:33   ` Mohamed Bana
2008-08-18 14:02 ` Taco Hoekwater
2008-08-18 19:55   ` Piotr Kopszak
2008-08-18 20:14     ` Hans Hagen
2008-08-18 20:32       ` Piotr Kopszak
2008-08-19  7:50         ` Hans Hagen
2008-08-19 10:28           ` Piotr Kopszak
2008-08-19 10:36             ` Wolfgang Schuster
2008-08-19 10:58               ` Piotr Kopszak
2008-08-19 11:10                 ` Wolfgang Schuster
2008-08-19 11:42                   ` Piotr Kopszak
2008-08-19 11:30               ` Piotr Kopszak

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=20080818130938.GA5607@mnw.art.pl \
    --to=kopszak@mnw.art.pl \
    --cc=kopszak@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).