ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: How to use PostScript font
Date: 20 Aug 2004 16:09:23 +0200	[thread overview]
Message-ID: <m2llg9vr3g.fsf@levana.de> (raw)
In-Reply-To: <4125AE5D.5050700@wxs.nl> (Hans Hagen's message of "Fri, 20 Aug 2004 09:55:09 +0200")

Hello Hans,

>>And the argument about being too LaTeXy: the encoding of these files
>>is not LaTeX specific (besides from the fact that LaTeX can only
>>handle T1/OT1 encoding right), so what is not generic about them?
>>  
> if you run afm2tfm on some files you get different results that the
> handcrafted' ones that come with distributions; (afm2pl for instance
> defaults to different metrics [esp spacing] than afm2tfm); many of
> these things are not really documented and done by people who use
> latex and know about latex internals (for instance how they deal with
> spacing); concerning generic ... 

Yes, but you stated that "different metrics, different subpaths, urw
instances either or not present". Different metrics? I can't see any
differences in metrics between differnent distributions on those
fonts! Can you? They come from one source, i.e psnfss. Different
subpaths? Perhaps, but what is the problem? Kpathsea is taking care of
this. URW or not to URW? Good question, lets get started on this
subject :-)) If we accept that there is such thing as "psnfss", which
is preinstalled on almost all TeX systems out there, we can let the
user decide: use "psnfss-metrics" or the ones generated by $TOOL. And
I can't see any problems with the spacing with those fonts being too
LaTeX related. We should be happy about those fonts, since we get
good fonts (in terms of encodings/spacing/finetuning) for free from
the LaTeX side.

You are right that there are many other things being to LaTeX related.
The situation is getting much better. A few years ago the distributions
only knew about LaTeX. I had major problems with old tetex (memory
problems for example), now most things work out of the box. 


[...]

> latex commands in entries) concerning fonts: if you want texnansi
> encoding, there are in most cases no tfm files etc. They are
> mentioned here and there, but often not on the system. It took me a
> while to find out that -because of that- i could not use precoockes
> metrics at all -)

Who needs texnansi anyway? (OK, perhaps there are few who really need
texnansi :-), but we might aks Mr. psnfss to generate texnansi metrics as
well). 

[...]

Patrick
-- 
ConTeXt wiki: http://contextgarden.net
texshow-web:  http://texshow.contextgarden.net
List archive: http://archive.contextgarden.net

  reply	other threads:[~2004-08-20 14:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 19:16 skhilji
2004-08-18 19:24 ` Patrick Gundlach
2004-08-19  8:07   ` Hans Hagen
2004-08-19 21:58     ` Patrick Gundlach
2004-08-20  7:55       ` Hans Hagen
2004-08-20 14:09         ` Patrick Gundlach [this message]
2004-08-20 15:52           ` Hans Hagen
2004-08-21  8:48             ` Patrick Gundlach
2004-08-22 23:26               ` Hans Hagen Outside
2004-08-24  9:56                 ` Siep Kroonenberg
2004-08-24 10:09                   ` Patrick Gundlach
2004-08-24 14:38                     ` Siep Kroonenberg
2004-08-18 19:28 ` Bill McClain
2004-08-18 21:16 ` Matt Gushee
2004-08-19 22:01 ` Patrick Gundlach
  -- strict thread matches above, loose matches on Subject: below --
2004-08-20 13:41 skhilji
2004-08-20 13:54 ` Patrick Gundlach
2004-08-20 15:04   ` Hans Hagen
2004-08-20 16:11     ` Patrick Gundlach
2004-08-20 16:27       ` Hans Hagen
2004-08-20 16:40         ` Patrick Gundlach
2004-08-22  5:39           ` Salman Khilji
2004-08-22  6:28             ` Salman Khilji
2004-08-22  6:23               ` Larry Stamm
2004-08-22 18:11                 ` Patrick Gundlach
2004-08-19 13:02 skhilji
2004-08-19 13:40 ` Mari Voipio
2004-08-20  0:06   ` Nigel King
2004-08-20  0:42     ` Steve Peter
2004-08-18  2:56 skhilji
2004-08-18 15:02 ` Hans Hagen
2004-08-18 16:13   ` Matt Gushee

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=m2llg9vr3g.fsf@levana.de \
    --to=patrick@gundla.ch \
    --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).