ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: Re: Fonts again in ConTeXt
Date: Wed, 12 Mar 2003 20:35:55 +0100	[thread overview]
Message-ID: <20030312203555.33fb7c93.morawski@gmx.net> (raw)
In-Reply-To: <87fzps615f.fsf@gundla.ch>

On Wed, 12 Mar 2003 16:43:40 +0100
Patrick Gundlach <pg@levana.de> wrote:


> > At 03:05 PM 3/12/2003 +0100, you wrote:
> >
> >>Well, in my opinion, the berry typesript is sub-optimal, since it
> >>maps to the urw variants that are a) shipped with a few TeX systems only
> >>and b) (even worse) the urw variant helvetica (nimbus sans) is of no
> >>real use for the german people out there (broken germandbls).
> >
> > then, how many people do have the adobe palatino's?
> 
> None that I know of. But this is IMHO irelevant: the current TeX
> practice is:

No. No.
 
> 1) TeX macro package (aka LaTeX ;-) asks for "Adobe Helvetica", it
>    gets the font metrics from "phv....tfm". Then, in the map files
>    the users decides whether to use the original adobe fonts or the
>    substitues. 

the MAP-file is a nice place for the real font selection. How should
i tell "normal" users that their font-selection from the document is
overwriten since some stupid and wrong decisions have been made
in the past.

> 2) TeX macro package (aka ConTeXt ;-) asks for "URW Nimbus Sans"
>    a) on TeXlive (and perhaps any other I don't kown of) it gets the
>       metrics from "uhv....tfm". Then, in the map files the user has
>       no choice; the dvi/pdf driver should take Nimbus Sans.

that's correct, since *it is* URW...

> I think it is wrong behaviour to explicitly ask for the substitution

it's no substitution, it is the font that is ask for. You asks for
URW and you get URW. Simple, isn't it?
The way the psnfss works is wrong, since one asks for Adobe and gets
URW. Please read some threads in the PDFTeX-ML and you can see what
confusion this creates.

> and leave the user no choice about which variant (adobe, urw) to use.

The choice is made with a new typescript. This is the common procedure
when a new font is installed. So, if you have Adobe Palatino then
install it as you did for other fonnts too. But, stop! Sorry, there
are always entries in the current pdfTeX MAP-file that map your Adobe
fonts back to URW variants. So, first you to have  edit the MAP-file.
No, no you cannot use \loadmapfile since it does not overwrite the
wrong psnfss settings. Nice way to fool many users. Many thanks. ;)

Thus, include a new typescript in the ConTeXt core that maps to the
Adobe names, but please don't support these wrong decisions of
the past. Additionally, please don't name the typescript "Adobe....",
since it is only Adobe if you have the fonts installed. "psnfss" is
a good name: PS-Names-Fooling-Suitable-Setup. For real Adobe fonts
everybody should be able to write proper typescripts.

Regards,
  Jens

  reply	other threads:[~2003-03-12 19:35 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 16:25 Displayed material, again Giuseppe Bilotta
2003-03-10 16:50 ` Bruce D'Arcus
2003-03-10 20:22   ` Re[2]: " Giuseppe Bilotta
2003-03-10 22:15     ` s-mag-01 Bruce D'Arcus
2003-03-11  8:00       ` s-mag-01 Hans Hagen
2003-03-11 14:11         ` s-mag-01 Bruce D'Arcus
2003-03-11 14:31           ` s-mag-01 Hans Hagen
2003-03-11 14:34         ` s-mag-01 Bruce D'Arcus
2003-03-11 14:46           ` Fonts again in ConTeXt Patrick Gundlach
2003-03-11 15:10             ` Bruce D'Arcus
2003-03-12 13:04               ` Maarten Sneep
2003-03-12 13:23                 ` Bruce D'Arcus
2003-03-12 13:26                   ` Maarten Sneep
2003-03-12 14:05                     ` Patrick Gundlach
2003-03-12 15:11                       ` Hans Hagen
2003-03-12 15:43                         ` Patrick Gundlach
2003-03-12 19:35                           ` Jens-Uwe Morawski [this message]
2003-03-13  8:31                             ` Patrick Gundlach
2003-03-14  8:27                               ` Hans Hagen
2003-03-12 20:26                           ` Hans Hagen
2003-03-13  8:54                             ` Patrick Gundlach
2003-03-13 12:37                               ` Hans Hagen
2003-03-13 15:07                                 ` John Culleton
2003-03-13 15:52                                   ` Hans Hagen
2003-03-21 18:05                                 ` Patrick Gundlach
2003-03-22 11:10                                   ` Hans Hagen
2003-03-14 21:34                             ` Henning Hraban Ramm
2003-03-14 21:24                           ` Henning Hraban Ramm
2003-03-21 18:06                             ` Patrick Gundlach
2003-03-12 15:09                 ` Hans Hagen
2003-03-11 15:02           ` s-mag-01 Adam Lindsay
2003-03-11 20:52             ` s-mag-01 Hans Hagen
2003-03-11  9:13       ` s-mag-01 Patrick Gundlach
2003-03-10 17:00 ` Displayed material, again Hans Hagen
2003-03-10 23:24 ` Hans Hagen
2003-03-11 10:08   ` Re[2]: " Giuseppe Bilotta
2003-03-11 10:52     ` Hans Hagen
2003-03-11 11:47       ` Re[3]: " Giuseppe Bilotta
2003-03-11 14:57         ` Hans Hagen
2003-03-11 17:04           ` Re[4]: " Giuseppe Bilotta
2003-03-12 20:36             ` Hans Hagen
2003-03-13  9:36               ` Re[5]: " Giuseppe Bilotta
2003-03-13 12:23                 ` Hans Hagen
2003-03-11 15:12         ` Re[3]: " Hans Hagen
2003-03-12 21:07         ` Hans Hagen
2003-03-13  9:38           ` Re[4]: " Giuseppe Bilotta

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=20030312203555.33fb7c93.morawski@gmx.net \
    --to=morawski@gmx.net \
    --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).