From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/1020 Path: main.gmane.org!not-for-mail From: Matthew Baker Newsgroups: gmane.comp.tex.context Subject: germandbls and Palatino Date: Fri, 15 Oct 1999 15:09:34 +0200 (MEST) Sender: owner-ntg-context@let.uu.nl Message-ID: References: <14341.41723.332957.766202@PC709.wkap.nl> Reply-To: Matthew.Baker@gmd.de NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035391863 29132 80.91.224.250 (23 Oct 2002 16:51:03 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:51:03 +0000 (UTC) Original-To: Context List In-Reply-To: <14341.41723.332957.766202@PC709.wkap.nl> Xref: main.gmane.org gmane.comp.tex.context:1020 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:1020 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