From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: fonts fonts and fonts
Date: Tue, 13 Mar 2001 10:25:08 +0100 [thread overview]
Message-ID: <3.0.6.32.20010313102508.0196aea0@server-1> (raw)
In-Reply-To: <01K156WYRVOU9AS7ZF@wkap.nl>
At 12:11 AM 3/13/01 +0100, you wrote:
>Hi!
>
>On Mon, Mar 12, 2001, Hans Hagen wrote:
>
>> Fonts is still one of the more complicated areas in tex. I have written a
>> perl script that can do some of the tasks needed to install a 'commercial'
>> font under context.
>
>Are you using fontinst for this? This should imho be the best way to do
>it, because you can also use the font for tex/latex.
i've given up on fontinst long ago, i just use the fonts out of the box and
only generate tfm's
>> There are several issues that need to be taken care of:
>>
>> - copying fonts the right location in the texmf-local tree
>
>tetex keeps all font-related files in subdirs foundry/fontname, e.g.
>fonts/tfm/adobe/minion.
i currently di that as well, but i keep all fonts on the local tree, i even
use the tir times fonts instead of the funny named ones
>create a new map file for dvips and pdftex.
i must admit that i only looked at pdftex and dvipsone, is dvips already in
tune with pdftex with regardd to the map file?
>A repository for what?
the tfm files that i use + the map files that i use for fonts that i bought
/ use
>Imho it's better to stay with fontinst. But this certainly needs
>an easy-to-use frontend. If you tell the user, after fontinst has
>completed, that he can now use Minion by \setupbodyfont [minion], then
>he won't see anything of the "tex font mess". So the user should use the
>real name of the font, but the software the kb names.
I only wished that the kb named were more verbose which should not be a
problem today. [i also want as less tfm files on my machine as possible;
actually, it's near to impossible to explain to organization that we work
for to explain what those names are]
minion/myriad are very special cases; i'm playing with myriad now, and
adobe does not even provide the files it says is provides [that's a real mess]
>I have used the standard pdf fonts, Lucidabright, Utopia, Charter and
>the Microsoft Core Fonts. All in texnansi encoding, because I still
>don't understand how this encoding stuff works... :-( But I never
>had problems with this. Except that some symbols are taken from
>the Computer Modern Math fonts.
texnansi is good (i use it here) but i'm not sure how it matches ec, i just
installed the informal math and helvetica math; seems to work ok too [but
it's hard to find a match for myriad]
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-03-13 9:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 23:11 Christoph Dreyer
2001-03-13 9:25 ` Hans Hagen [this message]
[not found] <C21706811338D411A0130090273D20B291AD48@msgmarbio02.bio.dfo .ca>
2001-03-13 14:54 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2001-03-13 13:38 White, George
2001-03-13 9:05 siep.kroonenberg
[not found] <pragma@wxs.nl>
2001-03-12 16:50 ` Hans Hagen
2001-03-12 17:07 ` Frans Goddijn
2001-03-12 23:11 ` Christoph Dreyer
2001-03-13 9:33 ` S2P development
2001-03-13 10:12 ` Han The Thanh
2001-03-13 10:35 ` Hans Hagen
2001-03-14 21:32 ` H. Ramm
2001-03-13 7:12 ` Steve Lumos
2001-03-13 9:13 ` Hans Hagen
2001-03-14 0:29 ` Uwe Koloska
2001-03-13 14:35 ` Ed L Cashin
2001-03-14 0:18 ` Uwe Koloska
2001-03-15 21:55 ` H. Ramm
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=3.0.6.32.20010313102508.0196aea0@server-1 \
--to=pragma@wxs.nl \
--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).