ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl, Jerzy.Ludwichowski@uni.torun.pl,
	v.r.w.Schaa@gsi.de, Karl Berry <karl@freefriends.org>
Subject: Re: Fleurons
Date: Thu, 02 Jun 2005 00:10:09 +0200	[thread overview]
Message-ID: <429E3241.8030603@wxs.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0506012246220.8043-100000@re86.internetdsl.tpnet.pl>

Staszek Wawrykiewicz wrote:

>   AFM and PFM files are supplied here for the sake of
>   completeness only.  They are normally not required for use
>   with TeX.

this is not true, you need the afm's when you use them to make graphics in other 
progs that will then be used by tex; also, you need them in order to generate 
metrics for encodings other than teh shipped ones

> In fact, nobody knows how the *old* mess with tfm, vf etc. fits
> to more *new* urw pfb which are of better quality then the older ones. 
> Anyway both distributions cannot be mixed. Not to say about packaging, etc.
> So I introduced "urw35vf" (#3416) which contains all (historical) stuff
> for those using urw fonts directly (.vf, .tfm, .fd, .sty files).
> Everybody has freedom using them from TL. Thomas removed such stuff
> from teTeX as simply garbage.

he's free to do that but it sounds strange and dangerous to me

>>Meanwhile, the afm and pfb are under just urw/.  It seems odd, though I
>>can imagine how it could happen.
> 
> 
> ??? Everything is OK: fonts/afm/urw/ and fonts/type1/urw/
> 
> 
>>Clearly the URW fonts are not 100% identical to the Adobe fonts, but in
>>practice we have to accept the URW Type 1's under the p* names, because
>>the p* names are what most documents have historically used.  We can't
>>suddenly make those documents unusable, that would be disastrous.

indeed, so we should ship duplicates

>>For that matter, the Adobe fonts themselves have changed over the
>>years.  Nothing is perfect.
>  
> Right.

sure, but we can try to reach robustness by redundancy

>>    but context (users) expect the whole set of urw (afm & pfb) to be
>>    present because they generate other encodings and such;
>>
>>uzdr.afm and uzdr.pfb are both in the current TL sources, and always
>>have been.  I know of no reason or suggestion to delete them.
>  
> They are as well present in teTeX. 
>  
>>  i think that we need to get rid of the urw mappings in the aliases file
>>
>>I agree.  I have now deleted the aliases file altogether from the TL
>>sources.  We'll see how that flies.  I don't know if that will change
>>anything wrt gwTeX, though.
>  
> Ahh, I see! aliases could cause problems. Thanks for deleting that file.

-)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2005-06-01 22:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 19:35 Fleurons Keith McKay
2005-05-30 21:52 ` Fleurons Hans Hagen
2005-05-30 23:39   ` Fleurons Adam Lindsay
2005-05-31  6:37     ` Fleurons Hans Hagen
2005-05-31  7:59       ` Fleurons Adam Lindsay
2005-05-31 10:14         ` Fleurons Hans Hagen
2005-05-31 11:15           ` Fleurons Adam Lindsay
2005-05-31 20:43           ` Fleurons Karl Berry
2005-06-01 21:27             ` Fleurons Staszek Wawrykiewicz
2005-06-01 22:10               ` Hans Hagen [this message]
2005-06-01 23:31                 ` Fleurons Staszek Wawrykiewicz
2005-06-01 23:53                   ` Fleurons Hans Hagen
2005-06-02  7:39                     ` Fleurons John R. Culleton
2005-06-02 22:25                       ` Fleurons Hartmut Henkel
2005-06-02 23:06                         ` Fleurons Stuart Jansen
2006-07-23 17:52                         ` Fleurons John R. Culleton
2005-06-11 20:48                       ` Fleurons Patrick Gundlach

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=429E3241.8030603@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=Jerzy.Ludwichowski@uni.torun.pl \
    --cc=karl@freefriends.org \
    --cc=ntg-context@ntg.nl \
    --cc=v.r.w.Schaa@gsi.de \
    /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).