ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco.hoekwater@wkap.nl>
Cc: ntg-context@ntg.nl
Subject: Re: germandbls and Palatino
Date: Fri, 15 Oct 1999 15:32:00 +0000 (GMT)	[thread overview]
Message-ID: <14343.18672.856807.515073@PC709.wkap.nl> (raw)
In-Reply-To: <Pine.LNX.4.10.9910151429080.523-100000@ahania.gmd.de>

Hi Matthew,

Looks like (at least) your context distrib is broken. The format
generation log might help, but if not than my guess would be: delete
all context-related stuff from your harddisk and re-install.

This does not really explain the missing ligs though. Another thing
that might help is a very small input file + log + dvi:

\setupbodyfont[ber,ppl]\useencoding[win]{\tracingall"s---ß? finally?}\bye

(please send all that junk directly to me, not to the list)

Greetings and good luck,

Taco
>>>>> "Matthew" == Matthew Baker <Matthew.Baker@gmd.de> writes:

    Matthew> Hi Taco, Hans, everyone,

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

    Matthew> \let\SS=\ss

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

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

    Matthew> - Matt

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

-- 
Taco Hoekwater                                 taco.hoekwater@wkap.nl
Kluwer Academic Publishers                            -- Pre Press --
Achterom 119, 3311 KB Dordrecht, The Netherlands  tel.  31-78-6392550
---------------------------------------------------------------------


  reply	other threads:[~1999-10-15 15:32 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       ` germandbls and Palatino Matthew Baker
1999-10-15 15:32         ` Taco Hoekwater [this message]
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=14343.18672.856807.515073@PC709.wkap.nl \
    --to=taco.hoekwater@wkap.nl \
    --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).