ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: mathew <meta@pobox.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: (RSFS) font installation
Date: Fri, 18 Mar 2011 09:40:31 -0500	[thread overview]
Message-ID: <AANLkTinNFsN=pehaALS4Yo4orDdWf85rPUCuo1Ue4hEG@mail.gmail.com> (raw)
In-Reply-To: <4D832E42.5010807@wxs.nl>

On Fri, Mar 18, 2011 at 05:04, Hans Hagen <pragma@wxs.nl> wrote:
> Also, I only consider a type 1 font okay when it has both an afm and a pfb
> file and mkiv can handle that quite well (even beyond the regular tex
> encodings). Personally I need it for fonts that I have bought and don't want
> to buy again.

Same here, but I found it easier to convert my fonts to OpenType by
loading them into fontforge and doing Save As...

I still have a mystery regarding the type 1 fonts installed with
GhostScript, though:

\definetypeface [dingbats][ss][sans][dingbats][default]
\starttext
{\dingbats \uchar{39}{7}\uchar{39}{13}\uchar{39}{42}}
\stoptext

produces no visible output, yet...

$ mtxrun --script fonts --list --all --pattern=dingbat*
dingbats         dingbats   /usr/share/fonts/type1/gsfonts/d050000l.afm
dingbatsnormal   dingbats   /usr/share/fonts/type1/gsfonts/d050000l.afm
$ ls /usr/share/fonts/type1/gsfonts/d050000l*
/usr/share/fonts/type1/gsfonts/d050000l.afm
/usr/share/fonts/type1/gsfonts/d050000l.pfb
/usr/share/fonts/type1/gsfonts/d050000l.pfm
$

This is with minimals and LuaTeX on Ubuntu. Get info on the PDF in
Okular shows no Type 1 fonts embedded.

(Also, is uchar intended to be a documented feature?)


mathew
___________________________________________________________________________________
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:[~2011-03-18 14:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 14:00 Stefan Müller
2011-03-16 15:58 ` mathew
2011-03-17  9:05   ` Stefan Müller
2011-03-17 12:40     ` Ulrike Fischer
2011-03-17 13:41       ` Stefan Müller
2011-03-17 16:12         ` Otared Kavian
2011-03-17 16:53           ` Stefan Müller
2011-03-17 15:04     ` mathew
2011-03-17 16:53       ` Stefan Müller
2011-03-18  2:42         ` mathew
2011-03-18  3:27           ` Khaled Hosny
2011-03-18 10:04             ` Hans Hagen
2011-03-18 14:40               ` mathew [this message]
2011-03-18 14:51                 ` Hans Hagen
2011-03-18 16:01                   ` mathew
2011-03-18 18:30                     ` Hans Hagen
     [not found]                       ` <AANLkTinWPdN-H6TPNato9PG7Fh0PzvfS0PkHXehzbt6J@mail.gmail.com>
2011-03-22 16:08                         ` mathew
2011-03-22 16:55                           ` Taco Hoekwater
2011-03-18 11:26           ` Stefan Müller
2011-03-18 11:39             ` Hans Hagen
2011-03-18 14:47               ` Stefan Müller

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='AANLkTinNFsN=pehaALS4Yo4orDdWf85rPUCuo1Ue4hEG@mail.gmail.com' \
    --to=meta@pobox.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).