ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Patrick Gundlach <pg@levana.de>
Subject: Re: texfont and type-tmf.dat
Date: Thu, 09 Oct 2003 11:00:45 +0200	[thread overview]
Message-ID: <m24qyipyyq.fsf@levana.de> (raw)
In-Reply-To: <6.0.0.22.2.20031009000409.02e13780@server-1> (Hans Hagen's message of "Thu, 09 Oct 2003 00:04:46 +0200")

Hi,


Hans Hagen <pragma@wxs.nl> writes:

>>So what is wrong with adobekb.tex? It is now included in ConTeXt, so
>>with \usetypescript[adobekb][someencoding] your psnfss fonts should
>>work fine.
>
> i can make a default for that but only when i can be absolutely sire
> that the metrics are there that i want there to be -)

According to to the statements from Walter Schmidt, a TeX font expert
(perhaps I should say *the* TeX font expert?) in
http://tug.daimi.au.dk/archives/tex-fonts/msg01328.html


\quote{% ....
Note, however, that embedding of URW's fonts, while using the 
(PSNFSS) Adobe Base35 metrics, will _not_ lead to any bugs!  
The character metrics are matching!  Differences in the 
"character bounding boxes" are irrelevant for the advance widths!  
The only drawback is, that you cannot access those glyphs that 
are in the URW fonts, but not in the Adobe fonts.  Indeed, this 
could be overcome by providing particular metrics and VFs for 
the URW fonts -- see below. }


Patrick
-- 
You are your own rainbow!

  reply	other threads:[~2003-10-09  9:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BAA1DC4D.ECA9%king@dircon.co.uk>
2003-08-06 20:21 ` Nigel King
2003-08-06 22:05   ` Gerben Wierda
2003-08-07  6:42     ` Nigel King
2003-08-08  0:31       ` darnold
2003-08-08  1:14         ` Trouble with updated Context darnold
     [not found]       ` <1591.209.209.17.128.1060305294.squirrel@webmail.inreach.co m>
2003-08-08  7:47         ` Hans Hagen
     [not found]     ` <1516.209.209.15.183.1060302710.squirrel@webmail.inreach.co m>
2003-08-08  7:48       ` texfont and type-tmf.dat Hans Hagen
2003-08-11 13:00     ` Hans Hagen
2003-10-08 17:14       ` Nigel King
2003-10-08 17:32         ` Patrick Gundlach
2003-10-08 17:59           ` Nigel King
2003-10-08 18:13             ` Patrick Gundlach
2003-10-08 22:04               ` Hans Hagen
2003-10-09  9:00                 ` Patrick Gundlach [this message]
2003-10-09  9:23                   ` Hans Hagen
2003-10-09 10:15                     ` Patrick Gundlach
2003-10-09 17:31                       ` Nigel King
2003-10-09 18:52                         ` Patrick Gundlach
2003-10-14 21:48                           ` Nigel King
2003-10-14 22:14                             ` Patrick Gundlach
2003-10-14 22:58                               ` Nigel King
2003-10-14 23:04                                 ` Patrick Gundlach
2003-10-14 23:27 George N. White III
2003-10-14 23:46 ` Patrick Gundlach
  -- strict thread matches above, loose matches on Subject: below --
2003-10-10 17:38 George White
2003-10-10 20:21 ` Patrick Gundlach
2003-08-03  5:37 Matthew Huggett
2003-08-03  5:57 ` David Arnold
2003-08-04  8:14 ` Hans Hagen

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=m24qyipyyq.fsf@levana.de \
    --to=pg@levana.de \
    --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).