ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Matthew Baker <Matthew.Baker@gmd.de>
Subject: germandbls and Palatino
Date: Fri, 15 Oct 1999 15:09:34 +0200 (MEST)	[thread overview]
Message-ID: <Pine.LNX.4.10.9910151429080.523-100000@ahania.gmd.de> (raw)
In-Reply-To: <14341.41723.332957.766202@PC709.wkap.nl>

Hi Taco, Hans, everyone,

Still no success with either ligatures or sharp s's.  I added the line
Taco suggested to enco-ec.tex but, as far as I can tell, it had no effect.
Switching to the win encoding causes "s and ß to switch to sans-serif
font.  I imagine this is because \SS switches to sans serif.  In
font-ini.tex there is the line

\let\SS=\ss

The comment above says this is to to make \SS produce the sharp s so that
\ss can safely be overridden with the sans-serif command.  If I comment
this line out and remake the format files, ß and "s no longer switch to
sans serif.  So it seems to me that, when font-ini.tex is loaded, \ss
already is set up to switch to sans-serif.

That's the ß problem.  I had a look in both my tfm and vf files and they
both contain 2 times 15 ligature lines.  Are there any switches in context
that can cause it to produce more output that will help in finding this
problem?

- Matt

--
Dr. Matthew Baker           matthew.baker@gmd.de
GMD - FIT.MMK               http://fit.gmd.de/hci/pages/matthew.baker.html


  parent reply	other threads:[~1999-10-15 13:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-13  8:15 Palatino Matthew Baker
1999-10-13  8:37 ` Palatino Taco Hoekwater
1999-10-14  6:19   ` Palatino Matthew Baker
1999-10-14  9:31     ` germandbls Taco Hoekwater
1999-10-14 11:01       ` germandbls Peter Willadt
1999-10-15 13:09       ` Matthew Baker [this message]
1999-10-15 15:32         ` germandbls and Palatino Taco Hoekwater
1999-10-14  9:40     ` Palatino Taco Hoekwater

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=Pine.LNX.4.10.9910151429080.523-100000@ahania.gmd.de \
    --to=matthew.baker@gmd.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).