ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Pascal de Bruijn" <pmjdebruijn@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Installing Type 1 fonts into ConTeXt
Date: Fri, 11 Jan 2008 23:22:33 +0100	[thread overview]
Message-ID: <36121a670801111422q41b8d84dm69dec66fb911c5cf@mail.gmail.com> (raw)
In-Reply-To: <op.t4r7zagdnx1yh1@your-b27fb1c401>


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

On Jan 11, 2008 9:17 PM, Idris Samawi Hamid <ishamid@colostate.edu> wrote:

> Hi Pascal,
>
> On Fri, 11 Jan 2008 12:38:00 -0700, Pascal de Bruijn
> <pmjdebruijn@gmail.com> wrote:
>
> > On Jan 11, 2008 8:25 PM, Taco Hoekwater <taco@elvenkind.com> wrote:
> >
> >> Pascal de Bruijn wrote:
> >> >
> >> > Does anybody have a clue why the first define went sour? Which tool
> is
> >> used
> >> > to extract the metadata from the .pfb files?
> >>
> >> Looks like a typing error in the pfb rename of  0018a___.pfb: it should
> >> be named zhum601bi.pfb (note the 'm').
> >
> >
> > Is renaming required?  I got the fonts from a CorelDRAW cdrom. I used
> the
> > files as is.
> >
> > Anyway other font collections also have deviating filenames, and they
> > work
> > just fine.
>
> In my experience, you have to get the coordination between pfb and tfm
> exactly right. Things are case sensitive etc... I'm sure there's just a
> typo or mismatch somewhere


I renamed all the fonts according to:
http://www.tug.org/fontname/html/Bitstream-fonts.html#Bitstream-fonts

I did this using a script, so there very little chance of error.

>>> Also, I'm currently installing in ~/texmf, however, say I'd want to
> >>> makethese fonts available system-wide, what would be the correct place
> >>> to movethem?
>
> Better to put them in texmf-local or, even better, texmf-project (may have
> to edit setuptex.bat in that case). I NEVER install anything in texmf if I
> can help it.
>
> See also the MyWay I wrote on this topic, maybe something in there will
> help.
>

I'll take a look at it tomorrow.

Regards,
Pascal de Bruijn

[-- Attachment #1.2: Type: text/html, Size: 2474 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2008-01-11 22:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11 18:58 Pascal de Bruijn
2008-01-11 19:25 ` Taco Hoekwater
2008-01-11 19:38   ` Pascal de Bruijn
2008-01-11 19:50     ` Taco Hoekwater
2008-01-11 20:17     ` Idris Samawi Hamid
2008-01-11 22:22       ` Pascal de Bruijn [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=36121a670801111422q41b8d84dm69dec66fb911c5cf@mail.gmail.com \
    --to=pmjdebruijn@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).